Planning worksheets
In this stage, the service level management process is initiated with the business, operational level agreements (OLAs) and underpinning contracts (UCs) are validated, and service level agreements (SLAs) are defined and implemented.
The following worksheets are available:
- Signatories worksheet
- Contracts worksheet
- Agreements worksheet
- Service targets worksheet
- Implementation considerations worksheet
Signatories worksheet
Complete the following worksheet for signatories:
Signatory information |
---|
This agreement remains valid until superseded by a revised agreement mutually endorsed by the following signatories. The agreement is reviewed annually. Name___________________________Position__________________Date____________ Name___________________________Position__________________Date____________ |
Contracts worksheet
Complete the following worksheet to help you plan the information for your contracts:
Contract information |
---|
Contract name_________________________________________________________________ Contract type (length)__________________________________________________________ |
Customer information |
---|
With which customers, users, line of business, or group of employees is the agreement made? Customer name:_______________________________________________________________ Organization__________________________________________________________________ Department:__________________________________________________________________ |
Permissions |
---|
Group or Role who can access the information:____________________________________ |
Agreements worksheet
Complete the following worksheet to help you plan the information for your agreements.
General agreement information |
---|
|
Compliance target information |
---|
The performance target used to track how well the service organization is performing since the effective date of the SLA. Compliance target____percent Define the level at which you consider the compliance target to be At Risk. Compliance target At Risk____percent |
Review period information |
---|
Periodic review periods: smaller periods of time over which performance is also monitored and reviewed; for example, daily, weekly, monthly, or quarterly. Periodic review periods: (1) ___________________________________________________________________________ (2) ___________________________________________________________________________ (3) ___________________________________________________________________________ (4) ___________________________________________________________________________ |
Penalties and rewards information |
---|
Determine the penalties for missed compliance targets and the rewards for meeting or exceeding these targets. Use the following table to complete the penalties and rewards information. |
Penalties and rewards
Review period | Penalty or Reward | Compliance % range to incur penalty/reward | Amount |
---|---|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Service targets worksheet
Complete the following worksheet to help you plan the information for your service targets.
General service target information |
---|
|
Terms and conditions and Key Performance Indicator (KPI) information |
---|
Terms and conditions (request-based, availability, and compliance-only service targets) |
To which types of incidents, requests, assets, or services does this service target apply? |
Goals and costs |
---|
You can choose a single goal and cost if the service target is missed, or you can set up a schedule for different costs to be applied on different days and times. For example, the cost for a business for a server to be out of commission might be less from midnight to 5:00 a.m. on a Sunday morning, than it is from 9:00 a.m. to 5:00 p.m. on a weekday. |
Request-based goals |
What is the goal or targeted commitment? For example, for request-based commitments, the time required for a user to receive a response after reporting an incident to the service desk is 4 hours and the cost when this requirement is not met is $50.00 per minute. Important: For request-based commitments, both incident response and resolution times can be based upon whatever incident impact/priority codes are used. Enter the impact/priority codes as part of the Terms and Conditions section.
|
Day__________________Start time_____End time__________Cost_____ Schedule 2 Day__________________Start time_____End time__________Cost_____ Schedule 3 Day__________________Start time_____End time__________Cost_______ Repeat the goal and cost schedule for as many schedules as you need.|
Availability and CI Outage commitments |
What is the cost when the asset or CI is not available?
|
Day__________________Start time_____End time__________Cost_____ Schedule 2 Day__________________Start time_____End time__________Cost_______ Repeat the goal and cost schedule for as many schedules as you need.|
Business time information |
---|
Determine the business times that the service target is in effect. |
Workdays: The hours that customers can expect the service to be available (for example, 7 x 24, 08:00 to 18:00 - Monday to Friday). ______________________________________________________________________________ |
Holidays: List the holidays or exceptions when service is not provided. ______________________________________________________________________________ |
Maintenance Establish the times that the measurements should not take place, for example, during regular maintenance schedules: Schedule 1_______________________________________________________________ Schedule 2______________________________________________________________ Schedule 3___________________________________________________________________ |
Measurement criteria |
---|
Request-based service targets |
When do you start measuring? For example: when each incident is submitted (Status=New) Start When____________________________________________________ When do you stop? For example: when each incident is resolved (Status=Resolved) Stop When_____________________________________________ Do you ever pause the measurement? For example, if the service desk is pending information from the customer (Status=Pending) Exclude________________________________________________ Specify a group in which you want data to be inherited if the request is passed from one person to another within this group. Group_____________________________________________________ |
Availability service targets |
How do you know when the asset is available? (Status=Deployed) Available When__________________________________________________________ How do you know when the asset is unavailable? (Status=Down or Status=In Repair) Unavailable When____________________________________________________________ |
CI Outage service targets |
Specify the outage condition that must be satisfied before the outage measurements for the CI are started. For example, Unavailability Type=Unscheduled Full Enter a lifecycle interval: Lifecycle Interval______________________________________________________________ |
Dependencies |
---|
In some cases, it might be appropriate to see internal operational level agreements (OLAs) or external underpinning contracts (UCs). If there is a dependency on another agreement, such as an OLA or a UC, make a note of the dependencies here. (For example, if the incident management team needs another internal service organization to resolve an issue before it can meet the resolution time for this SLA, note the dependency on the OLA with this other organization.) ______________________________________________________________________________ |
Milestones |
---|
Define your escalation procedures and actions to take if a certain amount of time has passed. These proactive milestones and actions allow you to prevent lagging performance. |
Milestones for request-based commitments |
As you approach the goal, describe the actions that should occur, and when. Title of Milestone______________________________________________________________ Execute the milestone (choose one):
|
____________________________________________________________________________ Repeat the previous milestone section for each additional milestone you would like to perform.|
Milestones for availability and CI outage commitments |
How often would you like the system to calculate the availability of each asset, CI or service that applies to this service target? (Select the number of days between 1 and 7, where 1 means daily, 2 means every 2 days, and so on.)
|
Implementation considerations worksheet
The following information describes other items to consider when planning your implementation.
Change management procedures |
---|
Reference the organization's change management procedures that must be followed to support compliance. ______________________________________________________________________________ |
IT service continuity |
---|
Reference the organization's IT Service continuity plans, together with details of how the agreement might be affected. Details of any specific responsibilities (for example, data back-up, off-site storage). ______________________________________________________________________________ |
Follow the Sun |
---|
If your company has offices in different countries, create business entities for each office, specifying the business hours. This configuration allows cumulative calculations of an operational level agreement (OLA) service target across business entities. Business Entity 1 Name_______________________________________________________________________ Business hours_______________________________________________________________ Business Entity 2 Name_______________________________________________________________________ Business hours_______________________________________________________________ Business Entity 3 Name_______________________________________________________________________ Business hours_______________________________________________________________ |
Security |
---|
Brief mention of and reference to the organization's security policy (covering issues such as password controls, security violations, unauthorized software, viruses, and so on). Include details of any specific responsibilities (that is, virus protection, firewalls). |
Reliability |
---|
The maximum number of service breaks that can be tolerated within an agreed period (can be defined as number of breaks, for example, four per year, or as a mean-time-between-failure (MTBF)). Definition of what constitutes a "break" and how these are monitored and recorded. ______________________________________________________________________________ |
Charging (if applicable) |
---|
Details of any charging formulas used, or reference to charging policy document. Include details describing invoicing and payment conditions, and so on. Also include details describing any financial penalties or bonuses that are paid if service targets do not meet expectations. What are the penalties or rewards and how are they be calculated, agreed to, and collected or paid? ______________________________________________________________________________ |
Service reviews |
---|
Details of how and when the service targets are reviewed. Include details of reporting to take place, of formal review meetings, and so on. Also include details describing who will be involved and in what capacity. ______________________________________________________________________________ |
Customer support |
---|
Details of how to contact the service desk, the hours it will be available, and what to do outside these hours to obtain assistance (for example, on-call support, third-party assistance and so on). It might include reference to internet/intranet self help and incident logging. ______________________________________________________________________________ |