| 2.1.4-6-1 Ensure configuration management control process for subcontractors is assessed |
Phase A |
Phase B |
Phase D1 |
|
Ensure that prime contractor has configuration management plan with a good definition of how baselines are established and what constitutes the baselines and how configuration items are defined. If needed document release plans should be defined along with how changes to the baselines are controlled based of the class of change. Look for data on how functional configuration audits (FCA's) and physical configuration audits (PCA's) will be conducted and by whom.
|
NA
|
Configuration Management/Audit Processes and Products
|
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-6-2 Ensure effectiveness of engineering review boards /configuration control boards are evaluated |
Phase A |
Phase B |
Phase C |
Phase D1 |
|
Ensure all changes to product baseline are reviewed using a systematic change process and include all parties affected by the change. Configuration control boards CCB should have minutes and most contractors today have electronic tools to maintain a data base of all changes. Ensure classification is employed to distinguish significance of changes that the Board reviews. Ensure the customer is fully involved in the review/approval process. Note, class I changes require government approval.
|
NA
|
Configuration Management/Audit Processes and Products
|
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-6-3 Ensure all Class I changes are approved by the government program office |
Phase A |
Phase B |
Phase C |
Phase D1 |
|
Ensure all changes that change form, fit or function are approved by the government customer.
|
AFMAN 63-119 A18.3.1
|
Configuration Management/Audit Processes and Products
|
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-6-4 Ensure all Class II changes are reported to the government program office |
Phase A |
Phase B |
Phase C |
Phase D1 |
|
Minor documentation changes that do not affect factors associated with Class I changes should still be reported to the government customer
|
NA
|
Configuration Management/Audit Processes and Products
|
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-6-5 Ensure interface control documentation changes are formally coordinated with affected parties |
Phase A |
Phase B |
Phase C |
Phase D1 |
|
Ensure an interface control plan is generated and approved by the governing agency that documents any changes to the interfacing features identified in the design
|
NA
|
Configuration Management/Audit Processes and Products
|
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-6-6 Ensure configuration status accounting process is assessed |
Phase A |
Phase B |
Phase C |
Phase D1 |
|
Ensure the recording and reposting of information needed to manage configuration items effectively to include the following: record of the approved configuration documentation identification number; status of proposed changes and deviations to the configurations; implementation status of approved changes; and the configuration of all units of the configuration item in the operational inventory.
|
NA
|
Configuration Management Plan (CMP); Program Management Plan; Configuration Management/Audit Processes and Products
|
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-6-7 Ensure the Configuration Management Plan provides for traceability throughout the program, for all reviews through development and production |
Phase A |
Phase B |
Phase C |
Phase D1 |
|
Ensure the government has control and oversight of the configurations through the entire program, including operational test. Ensure that the baseline system configuration and all baseline modifications are tracked and recorded to provide traceability from the to-be to the as-built production system.
|
AFMAN 63-119 A18.2; AFMAN 63-119 A18.2.1; AFMAN 63-119 A18.2.2; AFMAN 63-119 A22.5.3
|
NA
|
AFMAN 63-119 or equivalent; Mission Assurance Guide, TOR-2007(8546)-6018, Rev B, Program Assurance Chapter
|