Table of Contents

Search

  1. Preface
  2. Document Processing
  3. Operation Console
  4. Partners and Profiles
  5. On-Boarding Checklists
  6. Managed File Transfer Web Users
  7. Managed File Transfer Connections
  8. Endpoints
  9. Events
  10. Event Monitors
  11. Reconciliations
  12. Event Resubmission
  13. Audit and Authorization
  14. Advanced Exception Handling
  15. Dashboard and Reports
  16. Service Level Agreement Management
  17. Glossary

Service Level Agreement Violations

Service Level Agreement Violations

The SLA violation detector searches the operational data store for violations of service level agreements.
The operational data store event loader collects aggregated event information from the run-time B2B Data Exchange repository and loads the information to the operational data store. At the end of the event load process, the SLA violation detector searches the aggregated event information for violations based on the SLA rules that you defined.
The SLA violation detector reports violations for events that reached a final state. Violations for events that processed during multiple time frames appear only in the time frame on which the event processing started. For example, if the SLA violation detector finds a violation for an event that started processing on Sunday and reached a final state on Monday, you will see the violation when you select violations for Sunday but not for Monday.
The SLA violation detector reports most violation types at the end of the time frame. For example, if you define an SLA rule in which the error rate for a single day does not exceed 20%, the SLA violation detector searches the events for the violation only at the end of the day.
The SLA violation detector reports violations immediately when the value of the following default key performance indicators is greater than the value that you define in the rule:
  • Number of events
  • Number of errors
  • Event processing time
For example, if you define an SLA rule in which the maximum number of events for a single partner and account must not exceed 50 events in a day, the SLA violation detector reports the violation as soon as it finds event number 51 for that partner and account and the event reached a final state.
The SLA violation detector reports violations for custom key performance indicators immediately when you define the following conditions in the rule:
  • The key performance indicator count is greater than the rule value
  • The maximum key performance indicator value is greater than the rule value
  • The minimum key performance indicator value is less than the rule value
  • The calculation level period for the rule is
    Per Single Event
For example, if you define a rule in which each purchase order that a partner sends must have a value of at least 5,000 dollars, the SLA violation detector reports the violation as soon as it finds a purchase order with a lower value and the event reached a final state.

0 COMMENTS

We’d like to hear from you!