Command Center¶
Command Center is the shared starting point for SLApulse.
Use it as the admissions board for your SLA ICU: it shows which projects are configured, which are live, which are still collecting source statuses, and which need setup attention before the rest of the operating views can be trusted.
Both Members and Admins can use Command Center. Members use it to understand current project pressure. Admins also use it to identify setup work that belongs in the Setup area.
Portfolio metrics¶
The top metrics summarize project readiness:
| Metric | Meaning |
|---|---|
| Configured projects | Active tenant projects in scope. Archived projects are not included. |
| Live monitoring | Projects ready for operational monitoring in Health Monitor, Triage Board, and ICU Ward. |
| Collect mode | Projects that are gathering source statuses before SLA tracking is activated. |
| Setup incomplete | Projects that need configuration before reliable monitoring. |
Use these metrics before reviewing individual issues. A project that is still collecting or incomplete may not yet provide a reliable ICU signal.
Project Command Grid¶
The Project Command Grid sorts projects by required attention.
Each project card includes:
- project key and name
- current readiness status
- measured compliance for the rolling report window
- sample size and period
- live counts for critical, at-risk, breached, and paused work
- setup/readiness checks
- next action and a link to the relevant page
The grid is project-first because SLA pressure should not be averaged across unlike contracts. A support project with urgent response targets and an internal engineering project can both be healthy or unhealthy for different reasons.
Measured compliance¶
Measured compliance comes from report summary data for the rolling window. It is not the same as live risk.
Use measured compliance to understand recent historical performance. Use live counts to decide what needs action now.
Live risk counts¶
Live counts are built from active and paused monitor issues:
| Count | Meaning |
|---|---|
| Critical | Highest urgency issues, typically T1/T2 pressure. |
| At risk | Issues deteriorating toward breach. |
| Breached | Issues that already missed a current target. |
| Paused | Issues where SLA time is currently paused, but follow-up may still matter. |
If a project has good measured compliance but a rising critical count, treat the project as operationally fragile even if reports still look healthy.
Readiness checks¶
Readiness checks show whether the project has the setup needed for reliable monitoring.
Typical checks include source connection, workflow mapping, SLA policy, project state, and whether the project is still in collect mode.
If Command Center points to setup work, complete that before relying on Health Monitor or Reports for the project.
Next action¶
Each project card recommends the next practical action.
Examples:
| Situation | Likely next action |
|---|---|
| Setup incomplete | Open Projects and finish configuration. |
| Collect mode | Review observed statuses and map workflow meanings. |
| Live pressure | Open Health Monitor, Triage Board, or ICU Ward. |
| Healthy project | Continue monitoring or review Reports. |
Projects and mapping changes are Admin-only. If a Member sees a setup-related next action, they should ask an Admin to update the Setup area.
How Command Center relates to ICU Operations¶
Command Center answers:
Which projects need attention?
Operations answers:
Which issues need attention?
Start in Command Center when you need the portfolio view. Move to ICU Operations when you need live issue-level triage. Move to Analysis when you need the issue chart, report math, or export.