🚧 Under construction — VoTechWorks is being built. A free tech program — complimentary, as our commitment to get America working.
voTechWorksGrade 13 · a vocational technology learning center, by urbanicity
newSchoolWorks.com › VoTechWorks › Technology & Design › Data Center Facilities & Operations Management › Vendor & SLA Management for Data Center Operations › Lesson 5
TEC-DATA83-07 · Lesson 5 · 14 clock hours · practice

Drafting SLAs: Writing Measurable Commitments

Objective. Students will write SLA sections for at least three data center service categories that contain SMART (Specific, Measurable, Achievable, Relevant, Time-bound) performance commitments and enforceable remedy clauses.

⚠ Pending professional review

This lesson, its worked examples and its practice questions has not yet been verified by an industry-certified professional or by a certification or approval body. It is a study draft and may contain errors. Do not use it as instructions for work on a job site or on live equipment. Always follow your instructor, your supervising professional, and current official references and regulations.

VoTechWorks program approval and accreditation are still in progress. Credentials are issued only by the certifying bodies named in each program, after their own exams.

Why SLAs Must Be Measurable

A Service Level Agreement (SLA) is a contract section that defines exactly what a vendor must deliver, how performance is measured, and what happens when the vendor falls short. In data center operations, vague language such as "the vendor will respond promptly" creates disputes, delays repairs, and leaves the operator with no legal remedy. A well-drafted SLA protects the facility, the clients it serves, and the continuity of critical IT systems.

The standard framework for writing strong performance commitments is the SMART criteria: Specific, Measurable, Achievable, Relevant, and Time-bound. Every commitment in an SLA must satisfy all five criteria before it can be considered enforceable.

The SMART Framework Applied to SLAs

Specific means the clause names the exact service, the exact metric, and the parties responsible. "Network carrier uptime" is too broad; "99.99% monthly availability of the dedicated 10 Gbps fiber circuit between Meet-Me Room A and the carrier POP" is specific.

Measurable means the clause states a numeric target and explains how that number is collected and verified. Availability is typically measured as the percentage of total minutes in the reporting period during which the service was operational. Always specify whether measurement is continuous or sampled, who holds the monitoring data, and how disputes are resolved.

Achievable means the target is realistic given equipment capabilities and industry norms. Promising 100% uptime for any mechanical system is not achievable; 99.9% or 99.99% may be, depending on design. Setting unachievable targets benefits no one because vendors either refuse to sign or price the risk into the contract.

Relevant means the metric directly reflects the impact on data center operations. For a CRAC (computer room air conditioning) unit service response, measuring technician arrival time is relevant because prolonged equipment downtime raises intake temperatures and risks hardware failure.

Time-bound means every commitment specifies the reporting period (monthly, quarterly) and any time windows within which action must occur (e.g., four-hour on-site response).

Key Metrics You Must Define

Before writing a clause, choose the correct metric and define it in the SLA itself or in an attached definitions annex.

Structure of an SLA Section

Each SLA section should contain four elements:

1. Service description — what is being delivered and by whom.

2. Performance commitment — the numeric target, the metric definition, and the measurement method.

3. Reporting obligation — how often the vendor reports performance data and in what format.

4. Remedy clause — what the vendor owes the operator if the commitment is missed (typically a service credit calculated as a percentage of the monthly fee).

Writing Enforceable Remedy Clauses

A remedy clause must specify the trigger (which metric missed, by how much), the calculation method for the credit or penalty, the cap on total credits, and the process for claiming the remedy. Example of a weak clause: "Vendor will compensate customer for outages." Example of a strong clause: "For each calendar month in which availability falls below 99.9%, vendor will credit customer 5% of the monthly recurring charge for each 0.1 percentage point below the threshold, up to a maximum of 30% of the monthly recurring charge. Customer must submit a credit request within 30 days of the affected month's close."

Safety Considerations

When drafting SLA sections that involve physical maintenance—such as UPS battery replacement or CRAC unit service—include language requiring the vendor to follow applicable lockout/tagout (LOTO) procedures in accordance with OSHA standards before working on electrical or mechanical equipment. SLAs for electrical maintenance vendors should require technicians to wear appropriate arc-flash PPE as determined by an arc-flash hazard analysis. Requiring vendors to provide proof of safety training and compliance documentation before beginning work protects both workers and the facility.

Drafting Process Summary

1. Identify the service category and the metric that best represents acceptable performance.

2. Set a numeric target supported by equipment specs or industry benchmarks.

3. Define how the metric is measured and who owns the data.

4. State the reporting period and reporting format.

5. Write the remedy: trigger, calculation, cap, claim deadline.

6. Review every clause against the SMART criteria before finalizing.

Key terms8

SLA (Service Level Agreement)A contractual section that defines the service to be delivered, the measurable performance standard, the reporting method, and the remedy if the standard is not met.
SMART CriteriaA framework requiring commitments to be Specific, Measurable, Achievable, Relevant, and Time-bound so they can be objectively enforced.
AvailabilityThe percentage of total scheduled time during which a service or system is operational; calculated as (uptime ÷ total time) × 100.
MTTR (Mean Time to Repair)The average elapsed time from failure notification to full service restoration, used as a vendor responsiveness and capability metric.
MTBF (Mean Time Between Failures)The average operating time between successive failures of a system or component; a higher value indicates greater reliability.
RTO (Recovery Time Objective)The maximum acceptable duration for restoring a service after an outage; when written into an SLA it becomes a binding commitment.
RPO (Recovery Point Objective)The maximum acceptable age of data that must be recoverable after a failure, which drives backup frequency requirements.
Remedy ClauseThe SLA provision that specifies what the vendor owes the customer when a performance commitment is missed, including the trigger, credit calculation, cap, and claim process.

Worked examples4

1. Calculate the maximum allowable downtime per month for a network carrier SLA that commits to 99.9% monthly availability. Assume the month has 30 days.
  1. Find total minutes in the month: 30 days × 24 hours × 60 minutes = 43,200 minutes.
  2. Find the allowed downtime percentage: 100% − 99.9% = 0.1%.
  3. Convert to minutes: 43,200 × 0.001 = 43.2 minutes.
  4. Round to two decimal places: 43.20 minutes of allowable downtime in a 30-day month.
Answer: A 99.9% availability commitment in a 30-day month allows a maximum of 43.20 minutes of downtime.
2. A vendor's SLA promises 99.99% monthly availability for a dedicated circuit. The month has 31 days. How many minutes of downtime are permitted?
  1. Total minutes in 31 days: 31 × 24 × 60 = 44,640 minutes.
  2. Allowed downtime percentage: 100% − 99.99% = 0.01%.
  3. Convert to minutes: 44,640 × 0.0001 = 4.464 minutes.
  4. Round to two decimal places: 4.46 minutes.
Answer: A 99.99% availability commitment in a 31-day month permits approximately 4.46 minutes of downtime.
3. A CRAC unit vendor missed its 99.9% monthly availability SLA in a month with 30 days. The circuit was down for 60 minutes. The monthly recurring charge is $4,000. The remedy clause states: '5% credit per 0.1 percentage point below threshold, capped at 30% of the monthly recurring charge.' Calculate the credit.
  1. Allowed downtime for 99.9% in a 30-day month: 43,200 × 0.001 = 43.20 minutes.
  2. Excess downtime: 60 − 43.20 = 16.80 minutes.
  3. Actual availability: ((43,200 − 60) ÷ 43,200) × 100 = (43,140 ÷ 43,200) × 100 = 99.861%.
  4. Shortfall below 99.9%: 99.9% − 99.861% = 0.039 percentage points.
  5. Number of 0.1 percentage-point increments (round down as is typical unless contract states otherwise): 0.039 ÷ 0.1 = 0.39; apply 0 full increments — re-read: many contracts credit each partial increment as one full increment. Using that interpretation: 1 increment.
  6. Credit: 1 × 5% × $4,000 = $200.
  7. Check cap: 30% of $4,000 = $1,200; $200 is below the cap.
  8. Credit owed: $200.
Answer: The vendor owes a $200 service credit. (Note: the exact number of increments depends on contract language; always confirm whether partial increments count as full increments.)
4. Over a 90-day quarter, a UPS maintenance vendor had 3 failure events with total repair time of 9 hours. What is the MTTR?
  1. Convert total repair time to a consistent unit: 9 hours.
  2. Divide total repair time by the number of incidents: 9 hours ÷ 3 = 3 hours.
  3. MTTR = 3 hours per incident.
Answer: The vendor's MTTR for that quarter was 3 hours.

The math in this lesson1

Learners compute allowed downtime minutes in a 30-day month for a 99.9% commitment.
7.RP.3
Brush up in the math halls at newSchoolWorks.com:
In class: Students draft three SLA sections—covering network carrier uptime, UPS maintenance response, and CRAC unit service response—using a provided SLA section template and a bank of acceptable metric definitions. · Instructor-led critique: one student's draft is projected anonymously; class identifies vague or unenforceable language and rewrites problem clauses collaboratively on the whiteboard. · Students finalize their three SLA sections incorporating feedback and submit for instructor grading using a rubric that scores measurability, enforceability, and technical accuracy.
Materials: SLA section template; metric-definition bank (availability, MTTR, MTBF, RTO, RPO); whiteboard; rubric; word processor
Check: Each SLA section scores 80% or higher on the rubric; all performance commitments must include a numeric target, measurement method, reporting period, and remedy.

Practice check8

Answer each question, then check it. Nothing is recorded; this is your own practice.

Vendor & SLA Management
1. Which element is required in every SLA performance commitment to satisfy the 'Measurable' criterion of the SMART framework?
SLA Metrics & Calculations
2. A network carrier SLA commits to 99.95% monthly availability. A month has 30 days (43,200 minutes). What is the maximum allowable downtime?
Data Center Operations Fundamentals
3. In a data center SLA, RTO refers to:
Vendor & SLA Management
4. Which of the following remedy clause examples is most enforceable?
Safety & Compliance
5. When drafting an SLA section for a UPS maintenance vendor that requires physical work on energized electrical systems, which safety requirement should be included in the contract language?
SLA Metrics & Calculations
6. A vendor had 4 repair incidents in a month with a total repair time of 12 hours. What is the MTTR?
Vendor & SLA Management
7. Which SMART criterion is violated by the clause: 'The vendor will restore CRAC unit operation as soon as possible after a reported failure'?
Data Center Operations Fundamentals
8. RPO is most directly relevant to which SLA service category in a data center?
Record this lesson on my transcript. Sign in with your key and enrollment email to record lessons (enroll free if you have no key). This page stays open to read and practise.