The OpsCon describes the current system or situation, automated or manual, or the situation motivating the proposed system if none exists: its background, mission, objectives and scope with the goals and the methods used to reach them (A.2.4.2); its operational policies and constraints, such as limits on hours, personnel, hardware or facilities (A.2.4.3); a description covering the operational environment, major elements and interconnections, external interfaces, capabilities and functions, charts of inputs, outputs and data and control flows, cost of operations, operational risk factors, performance characteristics, quality attributes, arrangements for safety, security, privacy, integrity and keeping operations going in an emergency, and logistics, written in the users' terms with graphical tools (A.2.4.4); the modes of operation for all user classes, notably degraded, backup and emergency modes (A.2.4.5); the user classes, organizational structure, user-class profiles, interactions among them and other involved personnel (A.2.4.6); and the support concepts and environment (A.2.4.7).
The graph holds this control, the 0 it maps to, and the evidence behind each claim, over MCP and REST.