Process measurement exists to feed a maturity assessment of a process as actually run (the target process), carried out with whatever maturity model the organization picks (CMMI, TPI and EFQM are the examples). Such a model names the characteristics to look at, qualitative or quantitative, and says how their values show maturity. The approach first works out how to produce suitable measured values and then applies rules to translate them into the model's characteristics, so it works with any kind of maturity model. To assess, an organization needs an inspection plan whose measurement stacks pick out the measured values that suit the chosen model (Figures 2 and 3; the activities A1 to A4 refer to the model in Figures 7 to 11). A plan belongs to one or more named processes, whose purpose, outcomes and activities underlie its stacks, and it lists the measurements the intended assessment needs. When the organization decides to assess a running process it raises an inspection order from the plan, sets timing and resources in the light of earlier inspections, and uses the order as the checklist of every measurement the assessment requires.
The graph holds this control, the 0 it maps to, and the evidence behind each claim, over MCP and REST.