GOES-R MANAGEMENT CONTROL PLAN (MCP)

At Level II, the MCP outlines management processes required to execute programmatic responsibilities.
Requirements from the MCP are used to create and execute project plans at Level III. The Program level
technical Mission Requirements Document (MRD P417-R-MRD-0070) translates Level I requirements
into Level IIa requirements used to acquire the GOES-R Series System. The MRD is the primary
requirements document for the system PDRR and A&O contracts.
At Level III, The MRD is used to create Level IIIa requirements, which are subsystem and interface level
requirements documents. They are maintained and controlled by the Flight and Ground Segment
Projects. Level IIIa requirements documents become contractual documents provided to development
contractors for the GOES-R system.
At Level IV, Level IIIa requirements are used to create Level IV requirements by the development
contractors. Level IV requirements become the contractor’s system and subsystem specifications for the
design, development, and testing of the GOES-R systems and subsystems.
7 DOCUMENT AND CONFIGURATION MANAGEMENT
7.1 Configuration Management (CM)
The Configuration Management (CM) process is the disciplined approach used to control the baseline by
imposing requirements for configuration identification, change control, status accounting, and audits.
Program/Project documentation will be controlled under CM; however, requirements are particularly
important. The requirements are contractually binding to all development contractors and their sub
contractors, and they serve as the foundation upon which the contractors will design and build GOES-R.
CM Process for the GOES-R Program is outlined in P-417-R-PLN-0035.
The basic objectives of the GOES-R CM program are:
• Implements and maintains a CM system covering all of GOES-R Series
• The GOES-R ISSO shall be a mandatory voting member of the CCB.
• Establishes GOES-R baselines through all phases of the GOES-R Program
• Manages GOES-R configurations and program data
• Establishes configuration identification and control of all GOES-R baseline items
• Establishes a method of configuration status accounting for all approved changes to GOES-R Series
baselines
• Establishes procedures and conditions for performing configuration audits
• Establishes an GPO Configuration Control Board (CCB)
• Coordinates GOES-R GPO CM activities with the Flight Project, Operation Project and the
implementation contractor’s CM functions
Page 55 of 75