Makes sure accurate, dependable information about how services are configured, and about the configuration items that support them (any component whose management is needed for an IT service to be delivered), including how each CI is set up and how CIs relate, can be reached at the time and place it is needed. This is done through a configuration management system that may draw on several federated sources, with effort kept in line with the value of the information. Activities are: finding and recording new CIs; updating configuration data as changes are deployed; checking records; and auditing applications and infrastructure for anything not documented, ideally automated using discovery and deployment tools. It supports the planning of new services; is itself measured and improved according to how other practices use its data; shares data with partners, suppliers, consumers and regulators; documents in design and transition how assets work together; creates records during build (at times acting as the artefact's source); and is vital for resolving incidents and problems.
The graph holds this control, the 0 it maps to, and the evidence behind each claim, over MCP and REST.