Operational health, in one decision-ready view.
Track service disruption, root-cause progress, change execution, and release risk across the portfolio.
How Portfolio Health is calculatedDeterministic engine · criticality-weighted service scores · synthetic demonstration69/100
At Risk · 1 open P1 incident
Watch · 1 overdue RCA
Watch · 1 overdue RCA
At Risk · 2 overdue RCAs
Watch · 1 incident at SLA risk
Healthy · 1 high-risk release in the next 14 days
Healthy · No open P1s, overdue RCAs, SLA-risk incidents, or high-risk releases
Healthy · No open P1s, overdue RCAs, SLA-risk incidents, or high-risk releases
Each service starts at 100 with deductions: open P1 −20, SLA-risk incident −8, overdue RCA −12, 30-day change success below 85% −10 (below 70% −20), and each high-risk release in the next 14 days −10. An open P1 or two overdue RCAs force At Risk. The portfolio score weights service scores by criticality (Tier 0 ×3, Tier 1 ×2, Tier 2 ×1). Deterministic synthetic demo — recalibrate to an organization's targets before production use.
Flow and outcomes
Problems
Changes
Service health and accountability
Trading Platform
Market Data
- Incidents
- 1
- SLA risk
- 1
- RCA due
- 1
- Change success
- 0%
Client Identity
IAM Engineering
- Incidents
- 1
- SLA risk
- 1
- RCA due
- 1
- Change success
- —
Clearing & Settlement
Batch Services
- Incidents
- 1
- SLA risk
- 1
- RCA due
- 1
- Change success
- 0%
Integration Gateway
API Platform
- Incidents
- 1
- SLA risk
- 1
- RCA due
- 2
- Change success
- 100%
Opened vs. closed month over month
Volume trend through Jul 9, 2026. Closure lines above intake indicate backlog burn-down.
Incident flow
July intake outpaced closures after five months of near-parity or burn-down.
Problem flow
Problem creation is accelerating while overdue RCA volume remains concentrated in identity and digital services.