The OpsCon describes the proposed system resulting from the desired changes at a high level, indicating operational features without design specifications; examples of design strategies may clarify operation, and any actual design constraint that must be included is explicitly identified as required (A.2.6.1). It covers the background, objectives and scope of the proposed system (A.2.6.2); its operational policies and constraints (A.2.6.3); a description of its environment, major elements and interconnections, external interfaces, capabilities, data and process flows from the user's view, operating cost, operational risk factors, performance characteristics, quality attributes, and the arrangements for safety, security, privacy, integrity and keeping operations going in an emergency (A.2.6.4); its modes of operation including degraded, backup and emergency modes, related to processes and functions (A.2.6.5); its user classes with their organization, profiles (operators, maintainers and trainers included), interactions, and the other people involved (A.2.6.6); and its support environment (A.2.6.7).
The graph holds this control, the 0 it maps to, and the evidence behind each claim, over MCP and REST.