2.1.4-2-1 Ensure negotiated contract configuration management sections for completeness in regards to Statement of Work and deliverables are assessed |
Phase A |
|
Ensure contractor generates a configuration management plan which describes the programs planned processes and practices for configuration management.
|
NA
|
Request for Proposal (RFP); Integrated Master Plan (IMP)
|
Space Vehicle Systems Engineering Handbook, TOR-2006(8506)-4494; Mission Assurance Guide, TOR-2007(8546)-6018, Rev B; EIA IS-649, National Consensus Standard for Configuration Management; MilStd-973 SMC Standard SMC-S-002, Configuration Management or equivalent
|
2.1.4-2-2 Ensure negotiated contract includes government access to contractor data |
Phase A |
|
Ensure all contractor data, including test failures, anomaly data, deign documentation, reports and related material are made available for analysis and long-term archival, for use to support the customer organizations and that any restrictions do not adversely affect program execution and mission assurance.
|
NA
|
Statement of Work (SOW); Request for Proposal (RFP); Integrated Master Plan (IMP)
|
Mission Assurance Guide, TOR-2007(8546)-6018, Rev B, Integration, Test and Evaluation chapter
|
2.1.4-2-3 Ensure Configuration Management Plan, Release Plan, and Control Board procedures are adequate and complete |
Phase A |
Phase B |
|
Ensure configuration management plan meets intent of contractual requirements. Ensure compliance to the Configuration Management Plan and the Release Plan as accepted.
|
NA
|
Configuration Management Plan (CMP)
|
Space Vehicle Systems Engineering Handbook, TOR-2006(8506)-4494; Mission Assurance Guide, TOR-2007(8546)-6018, Rev B; EIA IS-649, National Consensus Standard for Configuration Management; MilStd-973 SMC Standard SMC-S-002, Configuration Management or equivalent
|
2.1.4-2-4 Ensure establishment and implementation of the Engineering Review Board /Configuration Control Board procedures and Engineering Change Proposal processes |
Phase A |
Phase B |
Phase C |
Phase D1 |
|
Ensure the board is composed of technical and administrative representatives who recommend approval or disapproval of proposed engineering changes to the configuration items current approved and baseline configuration documentation. The board should also recommend approval or disapproval of proposed deviations from a current approved configuration item and baseline configuration documentation. Ensure that a rigorous systems engineering process is implemented to provide analytical evidence to justify proposed system or support item changes.
|
AFMAN 63-119 A18.1; AFMAN 63-119 A18.1.1
|
Program Management Plan; Systems Engineering Management Plan (SEMP)
|
Space Vehicle Systems Engineering Handbook, TOR-2006(8506)-4494; Mission Assurance Guide, TOR-2007(8546)-6018, Rev B; EIA IS-649, National Consensus Standard for Configuration Management; MilStd-973 SMC Standard SMC-S-002, Configuration Management; AFMAN 63-119 or equivalent
|
2.1.4-2-5 Ensure technical documentation is generated that identifies and defines the configuration items functional and physical configuration |
Phase A |
Phase B |
Phase C |
Phase D1 |
|
Ensure configuration documentation is develop, approved, and maintained. The three levels of configuration documentation are the functional configuration documentation, the allocated (Design to) configuration documentation, and the product (As built) configuration documentation are maintained.
|
NA
|
NA
|
Space Vehicle Systems Engineering Handbook, TOR-2006(8506)-4494; Mission Assurance Guide, TOR-2007(8546)-6018, Rev B; EIA IS-649, National Consensus Standard for Configuration Management; MilStd-973 SMC Standard SMC-S-002, Configuration Management or equivalent
|
2.1.4-2-6 Ensure compliance with waiver and deviation process |
Phase B |
Phase C |
Phase D1 |
|
Ensure all configuration management and data management waivers are in place for all products before product development commences.
|
SFWC 2.1.4.2
|
NA
|
Space Vehicle Systems Engineering Handbook, TOR-2006(8506)-4494; Mission Assurance Guide, TOR-2007(8546)-6018, Rev B; EIA IS-649, National Consensus Standard for Configuration Management; MilStd-973 SMC Standard SMC-S-002, Configuration Management or equivalent
|