The OpsCon explains what is wrong with the present system or situation that prompts a new or changed system (A.2.5.1); summarizes the new or changed user needs, missions, objectives, environments, interfaces or personnel, the deficiencies that stop the current system responding, and why a new or changed system is justified, whether to seize an opportunity, improve an operation or add a capability (A.2.5.2); summarizes the desired changes in capabilities, processing, interfaces, personnel, environment, operations, support and other areas (A.2.5.3); classifies each change or new feature as essential (with the impact if not provided), desirable or optional, prioritizing within classes with reasons, to guide decisions when budgets or schedules are cut (A.2.5.4); records changes considered but not included with the rationale (A.2.5.5); and states the assumptions and constraints that will bear on users throughout the life of the system that replaces or changes the current one (A.2.5.6).
The graph holds this control, the 0 it maps to, and the evidence behind each claim, over MCP and REST.