Organisations should combine their inventories, asset characteristics and risk response scenarios to place each asset in a maintenance group: assets that share characteristics and have broadly the same maintenance needs for each scenario, covering patch schedule, testing needs, outage restrictions, impact if compromised and alternative mitigations. Groups are defined at whatever granularity suits and reassessed periodically. Assets that cannot or should not be patched get their own groups rather than being treated as exceptions, because they still need maintenance.
The graph holds this control, the 0 it maps to, and the evidence behind each claim, over MCP and REST.