Viewing service or operational level targets for a record
When you select a service, the SLAs or OLAs that match the service and the account of a record are applied to it.
The following topics are provided:
To view service or operational level targets
- Click the Remedyforce Console tab.
- From the View menu, select the appropriate module, such as Incidents.
- From the list of records, click the record for which you want to view the targets.
From the Agent Tools menu click
.Note
If there are applicable service or operational targets, this toolbar button is enabled only after you save the record and BMC Helix Remedyforce creates the target transactions for the record.
In the Targets window, view the target transactions of the current record. The Targets window displays the information for each target transaction. For more information, see Columns in the Service or Operational Targets window.
- (Optional) To view updates to target transactions for the current record. click the Refresh toolbar button.
Columns in the Service or Operational Targets window
The Targets window displays the following information for each target transaction.
Column | Description |
|---|---|
Status | Displays an icon that indicates the status of the target. The status can be: OK, Warning, Missed, Canceled, or Met. For more information, see States and statuses of service target transactions. |
State | Displays the state of the target. The state can be: Attached, In-Process, Pending, Canceled, or Completed. For more information, see States and statuses of service target transactions. |
Clock | Displays the status of the clock of the target. The clock conditions are defined in the Measurement tab of the target. When a clock condition is met, the status of the Clock is updated. The clock of the target can be: Not Started, Running, Paused, or Stopped. The Clock is in the Not Started condition when the Start Clock conditions of the target have not been met, but the target is applied to a record. |
Target Type | Displays the type of the target. |
Time Remaining | Displays the amount of time remaining to complete the target. It is the difference between the current date and the Target End Date. BMC Helix Remedyforce uses the Support Hours of the target to calculate this value. If the Support Hours are not defined for the target, BMC Helix Remedyforce uses the default business hours of the organization. |
Target End Date | Displays the end date of the target depending on the Support Hours of the target. If the Support Hours are not defined for the target, BMC Helix Remedyforce uses the default business hours of the organization. If the Pause Clock conditions were met, the duration for which the clock was paused is added to Target End Date. |
Agreement | Displays the name of the applicable agreement. |
Target Title | Displays the title of the applicable target. |
Start Date | Displays the date and time when the status of the incident, service request, task, problem, or change request met the Start Clock conditions of the applied target. Notes:
|
Elapsed Time | Displays the amount of time that is spent on completing the target depending on the Support Hours of the service target. It is the difference between the Start Date and the current date. If the Pause Clock conditions were met, the duration for which the clock was paused is subtracted from the Elapsed Time. If the Support Hours are not defined for the target, BMC Helix Remedyforce uses the default business hours of the organization. If the Clock was in the Running status and the Pause Clock conditions were met, the duration for which the clock was paused is added to Elapsed Time when the clock starts again. |
Note
To track the time that is spent on completing a service target, you can use the Elapsed Time field of the Incident Service Target object in reports. However, the Elapsed Time field value is saved in the database only when the service target is closed. For open service targets, the Elapsed Time field value is calculated and displayed in the Targets window but not saved in the database.
To track the total time for which staff members are actively working on an incident during your organization's business hours, you can use the Total Work Time field of the Incident object in reports. To start calculating the total work time spent on incidents, you must configure the appropriate status records as work status. For more information, see Creating status records.
States and statuses of target transactions
The following table describes the states of target transactions and the possible statuses of each state.
| State | Description of the state | Status | Description of the statuses for each state |
|---|---|---|---|
| Attached | The service target transaction is in the Attached state because the service target qualifies for the record, but the Start Clock conditions of the service target have not been met. | OK
| The service target transaction has the status of OK because a Warning condition has not been met and the service target is not past the Target End Date. |
| In-process | The service target transaction is in the In-process state because the Start Clock conditions were met and the clock is running. | OK
| The service target transaction has a status of OK because a Warning condition has not been met and the service target is not past the Target End Date. |
| In-process | The service target transaction is in the In-process state because the Start Clock conditions were met and the clock is running. | Warning
| The service target transaction has a status of Warning because a Warning condition has been met. The service target transaction needs attention because there is a warning that time is running out for the service target and a service target breach needs to be avoided. |
| In-process | The service target transaction is in the In-process state because the Start Clock conditions were met and the clock is running. | Missed
| The service target transaction has a status of Missed because there is no time remaining for the service target. The service target is past the Target End Date. |
| Pending | The service target transaction is in the Pending state because the Pause Clock conditions were met and the clock is paused. | OK
| The service target transaction has a status of OK because a Warning condition has not been met and the service target is not past the Target End Date. |
| The service target transaction is in the Pending state because the Pause Clock conditions were met and the clock is paused. | Warning
| The service target transaction has a status of Warning because a Warning condition has been met. The service target transaction needs attention because there is a warning that time is running out for the service target and a service target breach needs to be avoided. | |
| The service target transaction is in the Pending state because the Pause Clock conditions were met and the clock is paused. | Missed
| The service target transaction has a status of Missed because there is no time remaining for the service target. The service target is past the Target End Date. | |
| Canceled | The service target transaction is in the Canceled state because of any of the following reasons:
| Canceled
| The service target transaction has a status of Canceled because of any of the following reasons:
|
| Completed | The service target transaction for an incident, service request, task, problem, or change request is in the Completed state when the following conditions are met before Target End Date:
If the Target Type is Response Time and you select Actions > Responded and click Save in the Incident or Change Request form, the status of the Clock changes to Stopped. Note: The Stop Clock When section does not appear in the Measurement tab of a service target when you select Response Time as the Target Type. You cannot configure Stop Clock conditions for service targets with Response Time as the Target Type. | Met
| The service target transaction has a status of Met because it was completed before Target End Date. |
The service target transaction for an incident, service request, task, problem, or change request is in the Completed state when the following conditions are met before Target End Date:
If the Target Type is Response Time and you select Actions > Responded and click Save in the Incident or Change Request form, the status of the Clock changes to Stopped. Note: The Stop Clock When section does not appear in the Measurement tab of a service target when you select Response Time as the Target Type. You cannot configure Stop Clock conditions for service targets with Response Time as the Target Type. | Missed
| The service target transaction has a status of Missed because it was completed after the Target End Date. |
Related topics
Comments