Overview of the service target wizard
You can create and manage service targets in the Service Level Management Console using the Service Target wizard. To create service targets, follow these general steps:
- Log on to the Service Level Management Console.
- In the navigation pane, select the folder in which you want your service target to reside or create a folder.
- Click the Service Targets tab.
- Click Create.
- On each tab, click either Basic (default) or Advanced.
- The Basic option allows you to only access a limited number of fields. The remaining fields that are hidden are auto-completed when you use the templates.
- The Advanced option allows you to go through all four steps (tabs) and modify all of the fields.
- Follow the Service Target wizard.
Four steps are required to create your service target using the wizard.
Step 1 – General information
In this tab (or Step 1), you set the title and optional description for the service target as well as specifying the data source (performance-monitoring and compliance-only service targets) or application (request-based, CI Outage, and availability service targets). In this tab you set the terms and conditions under which the service target operates, or the or the Key Performance Indicators used as the data source.
Every service target within a service target group must have unique terms and conditions.
For more details on defining general service target information, see the following sections:
- Defining general information for request-based service targets
- Defining general information for availability service targets
- Defining general information for CI Outage service targets
Step 2 – Goals, costs, and business schedules
In this tab, you can set up a goal to determine whether the service target was met or missed and set the financial impact to the business if the goal is not met. You can set a single goal or define a goal schedule with different goals for each day of the week. If you are creating a service target to be used in an OLA, typically no costs are involved.
For more details on defining goals, costs, and business schedules, see the following sections:
- Defining goals and business schedules for request-based service targets
- Defining goals and business schedules for availability service targets
- Defining costs for CI Outage service targets
Step 3 – Measurement criteria (or rules for missing data for performance-monitoring service targets only)
For request-based service targets, measurement criteria defines the circumstances under which your measurements start, stop and pause. The measurement options define the group to which the service target belongs so that information can be inherited by other service targets of the same group. They also define whether the service target can be reopened, and whether the service target measurements should be reset to zero. You can also set the percentage of goal when the service target status changes to a warning.
For asset availability service targets, the measurement criteria is based on whether the asset is available and unavailable. The measurement option you have is to set the life cycle.
For performance-monitoring service targets, you see a different tab for rules for missing data in the data sources. This tab only applies to performance-monitoring service targets and allows you to set the rules for what happens when data is missing from the data sources. It also enables you to set how often you want the data to be processed by the Collector.
For more details on defining measurement criteria or for defining rules for missing data in data sources, see the following sections:
- Defining measurement criteria for request-based service targets
- Defining measurement criteria for availability service targets
- Defining measurement criteria for CI Outage service targets
Step 4 – Milestones and actions
This step is optional. Milestones and actions provide a mechanism for a service target to automatically initiate a particular action to avoid missing a commitment. As the service target progresses towards its goal, milestones can be defined to trigger at predetermined points that execute an associated action. For example, you can create a milestone that will trigger once a service target has reached 50 percent of its goal which automatically executes an action to notify a manager.
For more details on defining milestones and actions, see the following sections: