The OpsCon sets out how the proposed system will affect the operations of users, suppliers and operations and maintenance organizations, and the temporary impacts while it is developed, installed or trained, so that affected organizations can prepare (A.2.8.1): operational impacts such as interfaces with primary or alternate operating centres, procedure changes, new data sources, changes in input data quantity, type and timing, data retention changes, new emergency, disaster or accident modes, alternative input methods, operational budget and operational risks (A.2.8.2); organizational impacts such as changed responsibilities, added or removed positions, training or retraining, changes in staff numbers, skills, identifiers or locations, and staffing for contingency operation at alternate sites (A.2.8.3); and impacts during development such as pre-contract involvement, user participation in reviews and demonstrations, parallel operation of old and new systems and operational effects of system testing (A.2.8.4).
The graph holds this control, the 0 it maps to, and the evidence behind each claim, over MCP and REST.