Skip to Content
Information
This documentation supports the 20.02 version of BMC Service Level Management. To view an earlier version, select the version from the Product version menu.

Request-based and availability service target processing

Service target processing is done at two places:

  • AR System for AR System data sources
  • Collector for the non-AR System, metric data sources

For request-based and availability service targets, processing is performed using filters on the application form and the SLM:Measurement form. The auto-generated filters on the application form create and update the record in the SLM:Measurement form. Filters on the measurement form perform further calculations.

When an AR System-based data source is configured to work with SLM, the SLM engine creates a set of shared filters that are used to capture events for SLM processing. These events contain a date and time element that allows SLM to track the duration of tasks to ensure that you keep your contractual level of service. The SLM:Measurement form takes these events and tracks the progress of the service targets. When a user submits a request in the application form, such as HPD:HelpDesk, the auto-generated associate filter executes and a measurement entry is created. The measurement status is set to "Attached."

  • The Start filter executes when the Start When qualification is met. It sets the OverallStartTime with the current time, and sets the MeasurementStatus to "In Process". If a user is using the start reference time option, the start time is set to a user defined date and time field on the application form.
  • When OverallStartTime is populated with current time, service target DueDate is calculated by adding the GoalSchedGoalTime to the OverallStartTime, using the business time functions.
  • Exclude filter executes if the Exclude When qualification is met. It sets the DownStartTime field with the current time, and sets the MeasurementStatus to Pending.
  • NotExclude filter executes when NOT (Exclude When) qualification is met. It will set the DownStopTime with current time, and MeasurementStatus to "In Process."
  • When DownStopTime is populated with current time, DownElapsedTime is calculated by getting the difference between the DownStopTime and the DownStartTime. This time is then added to the previous DownElapsedTime. When you change the status of the Service target measurement from Detached to In Progress, the duration for which the record was in Detached status is also added to the DownElapsedTime.
  • When UpStopTime is populated with current time, UpElapsedTime is calculated by getting the difference between the UpStopTime and UpStartTime. Then it is accumulated with the previous UpElapsedTime.
  • The Stop filter executes when the Stop When qualification is met. It sets the OverallStopTime with current time.
  • When OverallStopTime is populated with the current time, OverallElapsedTime is calculated by getting the difference between OverallStopTime and OverallStartTime. UpTime is the same value as the accumulated UpElapsedTime value.
  • MetMissedAmount is calculated by getting the difference between GoalSchedGoalTime and UpTime. MeasurementStatus is set to "Met" if UpTime is less than or equal to GoalSchedGoalTime. MeasurementStatus is set to "Missed" if UpTime is greater than to GoalSchedGoalTime. MeasurementDone is set to Yes.
Warning

Important

An entry placed in SLM:EventSchedule executes when the service target DueDate time is passed to set MeasurementStatus to "Missed Goal" to signify that the goal of the service target has not been satisfied. However, the Measurement record is not completed until the Stop Measuring condition is satisfied.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*

BMC Service Level Management 20.02