The project identifies the transition constraints that influence requirements, architecture or design, makes the enabling systems available, prepares the site, confirms that the installed system can deliver its specified functions, trains the operators, users and other stakeholders needed for use and support, identifies transition results and anomalies, activates the installed system and establishes traceability of the transitioned elements; for software this includes recurring deployments between environments, patches and fixes, moves between organisations and data migration from a retiring system. Activities: prepare for transition, perform the transition, manage the results.
The graph holds this control, the 0 it maps to, and the evidence behind each claim, over MCP and REST.