Calculator Inputs
Example Data Table
This sample shows how one service period can be scored with weights, penalties, and a final index.
| Service | Period | Base SPI | Critical Penalty | Outage Penalty | Final SPI | Grade |
|---|---|---|---|---|---|---|
| Customer API | Sprint 12 | 103.83 | 2.50 | 3.33 | 97.99 | Healthy |
| Billing Gateway | February | 96.40 | 5.00 | 4.80 | 86.60 | Needs Attention |
| Search Platform | Release 5.4 | 101.15 | 0.00 | 1.20 | 99.95 | Healthy |
Formula Used
The calculator blends six service metrics into one weighted index. Metrics with stronger business importance can receive larger weights.
- Higher-is-better metrics: Metric Score = min(Actual ÷ Target, Bonus Cap) × 100
- Lower-is-better metrics: Metric Score = min(Target ÷ Actual, Bonus Cap) × 100
- Base SPI: Sum of each Metric Score × Normalized Weight
- Critical Incident Penalty: Critical Incidents × Penalty Per Critical Incident
- Outage Penalty: min((Outage Minutes ÷ Outage Threshold) × Outage Penalty Cap, Outage Penalty Cap)
- Final SPI: max(Base SPI − Critical Penalty − Outage Penalty, 0)
- Attainment Ratio: Final SPI ÷ 100
A score around 100 means the service is meeting its expected performance level after penalties. Values above 100 indicate strong performance, while lower values highlight service risk or missed expectations.
How to Use This Calculator
- Enter the service name and reporting period.
- Fill in actual and target values for availability, SLA response, SLA resolution, CSAT, change failure rate, and defect leakage rate.
- Assign weights that reflect the business importance of each metric.
- Set the bonus cap if you want to limit exceptional outperformance.
- Add critical incident count, outage minutes, and penalty rules.
- Press Calculate SPI to display the result above the form.
- Review the strongest and weakest metrics, then export the result as CSV or PDF.
Frequently Asked Questions
1. What does the service performance index measure?
It summarizes service quality into one weighted score. The calculator combines reliability, SLA attainment, satisfaction, and quality leakage, then subtracts incident and outage penalties.
2. Why are some metrics higher-is-better and others lower-is-better?
Availability, SLA compliance, and satisfaction improve when values rise. Change failure and defect leakage improve when values fall, so the formula reverses those ratios.
3. What is the bonus cap multiplier?
The bonus cap limits how much one exceptional metric can lift the total score. This keeps the index balanced and prevents distortion from a single standout metric.
4. How should I assign metric weights?
Give more weight to outcomes that matter most for customers or revenue. For example, customer-facing APIs often prioritize availability and response compliance over internal metrics.
5. What score is considered good?
Scores near 100 suggest expected performance. Scores above 100 show strong delivery. Scores below 90 usually deserve review, while scores below 75 indicate elevated service risk.
6. Why do critical incidents and outages use penalties?
Penalties make serious reliability problems visible even when SLA percentages still look acceptable. This prevents healthy averages from hiding damaging customer impact.
7. Can this calculator compare teams or releases?
Yes. Use the same targets, weights, and penalty logic across teams, products, or release periods. That creates a fair benchmark for trend and cross-service comparison.
8. When should I update the targets?
Review targets when service tiers change, customer expectations shift, or the system matures. Stable targets improve trend analysis, but stale targets weaken decision value.