Every commissioning organisation measures something. Far fewer measure readiness. The Commissioning (Cx) Readiness Maturity Model maps the distance between the two. Five tiers describe how a program's measurement capability grows: from counting the work performed to orchestrating readiness across an entire facility.
A maturity model is useful for one reason. You cannot improve what you cannot locate. Place your program on these tiers honestly and two things become clear: how much of your current confidence rests on activity rather than readiness, and the single most valuable move available to you next. The tiers are cumulative: each builds on the data and discipline of the one below. In our experience across data center programs, most operate at Tiers 1 and 2.
Fig. 1. The five tiers of the Cx Readiness Maturity Model, with the decisive jump between Tier 3 and Tier 4.
The five tiers of commissioning maturity
A note on names before the detail: these are measurement maturity tiers, not the commissioning Levels (L1 to L5) used in data center commissioning execution. A program running its Level 5 tests flawlessly can still sit at Tier 1 in how it measures readiness.
| Tier | What it looks like | Metrics it relies on | Limitations | Outcomes |
|---|---|---|---|---|
T1 Activity TrackingHow much have we done? |
Work logged as discrete items: scripts, issues, documents, milestones. Reporting rolls up counts and percentages. | Scripts completed, percent complete, issues opened and closed, documents submitted, milestones achieved. | Cannot see dependencies, severity, or integration state. Systematically overstates readiness. The Readiness Gap is invisible. | False confidence. Readiness surprises at integrated testing. Go/no-go rests on instinct and heroics. |
T2 Status ReportingWhere do we stand against plan? |
Activity organised into structured status: red-amber-green ratings, dashboards, schedule and earned-value views. | Tier 1 metrics plus schedule variance, earned value, status colours, completion trend curves. | Still item-based. Earned value forecasts cost and schedule, not readiness. Colours encode judgement. Dependencies implicit. | Better visibility, faster detection of slippage. Readiness still inferred; the Gap persists behind green status. |
T3 Dependency VisibilityWhat depends on what, and what is blocking? |
The dependency and prerequisite structure between systems and tests is made explicit. Blocking chains mapped and tracked. | Dependency completeness, prerequisite satisfaction, blocking-issue counts on critical paths, turnover status. | Shows where readiness is constrained but does not quantify probability of success. Descriptive, not predictive. | Constraints visible and actionable. Sequencing improves. The causes of the Gap are exposed, not yet measured. |
T4 Readiness IntelligenceWill the next execution succeed, and where will readiness fall short first?The decisive jump |
Readiness computed continuously from dependencies, resources, quality and risk. The model forecasts the Gap and recommends the fastest close. | Composite readiness per system and facility. Priority-weighted issues. Probability-of-success forecasts, completion velocity, contractor reliability. | Requires disciplined, structured data and an agreed readiness model. Forecasts calibrate as outcome history accumulates. | Readiness assessed before execution. Fewer failed tests. Defensible go/no-go. Effort aimed at the binding constraint. |
T5 Readiness OrchestrationCan readiness be orchestrated across the whole program? |
Closed-loop: the system senses program state, predicts the Gap, and orchestrates the response. People supervise exceptions. | Orchestrated Gap-closure rate. Share of recommended actions accepted. Readiness gained per unit effort. Cross-program learning. | Demands mature, trusted data, strong governance, and human oversight. The frontier, beyond current practice. | Readiness managed forward continuously and largely autonomously. The program optimises itself for probability of success. |
How to read the model
The jump that matters is Tier 3 to Tier 4: the transition from seeing dependencies to computing readiness from them. Tiers 1 through 3 are increasingly well-structured descriptions of the present and the past. Tier 4 is the first tier that produces a forward-looking measure: a probability of success.
That is the threshold at which an organisation crosses from activity tracking into Readiness Intelligence. Tiers 1 to 3 make the Readiness Gap progressively more visible. Tier 4 is the first that measures, manages, and forecasts it. Tier 5 closes the loop, orchestrating readiness across the program.
Mapping organisational maturity to readiness measurement
The tiers describe a capability, but they do not by themselves explain why an organisation sits where it does, or why two teams running the same software land on different tiers. For that, the maturity model has to be mapped onto the organisational capabilities that enable it. We call this conceptual framework the Readiness Measurement Map. It ties the readiness-measurement tier an organisation can sustain to its maturity across five enabling dimensions. The first is the most unforgiving: you cannot compute what you have not structured.
The framework has one governing rule, and it mirrors how readiness itself behaves. The tier an organisation can sustain is capped by its weakest enabling dimension, not its strongest. A team with excellent tooling but no explicit dependency model cannot rise above Tier 2, however good its dashboards look.
A team with a strong dependency map but siloed data and an instinct-driven culture stalls at Tier 3. And a team computing readiness on stale, self-reported evidence is producing confident fiction, not measurement, however advanced its model. Readiness measurement gates on the weakest dimension exactly as readiness gates on the weakest layer.
Used as a quick diagnostic, the Map turns the maturity model from a picture into a move. Rate each of the five dimensions honestly (item-level, relational, or computed), take the lowest, and that is the readiness-measurement tier you can actually sustain today. The dimension you scored lowest is your next investment.
How to climb, without new field work
Moving up the tiers is not a leap in field technology. It is a new layer of interpretation over data that disciplined programs already generate. Five concrete moves take a program from Tiers 1-2 toward Tier 4.
- Make the dependency and prerequisite structure between systems and tests explicit: this is the Tier 3 foundation everything else builds on.
- Replace raw open-issue counts with a priority-weighted view tied to blocking status and the next test.
- Track completion velocity against the velocity required to hit committed dates, not just cumulative percent-complete.
- Score contractor and vendor reliability from the closure history you already hold.
- Treat schedule feasibility (compression, float, look-ahead reliability) as a readiness input, not a separate report.
Frequently asked questions
What are the five tiers of the Cx Readiness Maturity Model?
Tier 1 Activity Tracking, Tier 2 Status Reporting, Tier 3 Dependency Visibility, Tier 4 Readiness Intelligence, and Tier 5 Readiness Orchestration. The tiers are cumulative, and most data center programs we work with operate at Tiers 1 and 2.
How do I locate my commissioning program on the model?
Rate the five enabling dimensions of the Readiness Measurement Map honestly: data foundation, dependency modelling, process, gates and evidence integrity, system integration, and decision culture. The lowest score sets the tier you can actually sustain, and that weakest dimension is your next investment.
What is the decisive jump in the maturity model?
Tier 3 to Tier 4: the move from seeing dependencies to computing readiness from them. Tier 4 is the first tier that produces a forward-looking measure: a probability that the next execution succeeds.
Do I need new field technology to advance a tier?
No. Climbing is a new layer of interpretation over data that disciplined programs already generate: make dependencies explicit, priority-weight open issues, track completion velocity, score contractor reliability, and treat schedule feasibility as a readiness input.
Where does your program sit? Take the five-question self-assessment to locate your tier, or see how CxSTAT IQ computes readiness at Tier 4.
