| 2.2.5-2-1 Ensure integration and test requirements are documented and complete in the RFP and/or contract |
Phase 0 |
Phase A |
|
Ensure the requirements for planning integration and verification testing are defined in the RFP. Ensure the contractor plan includes test strategy for various level of testing, requirements verification and validation approach, test products development process, test environments, test readiness review, test witness, and acceptance criteria. Ensure modeling and simulation requirements are identified early, and updated/funded throughout the program's lifecycle.
|
AFMAN 63-119 A4.5.1; AFMAN 63-119 A13.2.2
|
Statement of Work (SOW); Request for Proposal (RFP)
|
Space Vehicle Systems Engineering Handbook, TOR-2006(8506)-4494; AFMAN 63-119 or equivalent
|
| 2.2.5-2-2 Ensure integration compliance documents are on contract and tailoring meets intent of mission requirements |
Phase 0 |
Phase A |
|
Ensure compliance documents address all interfaces with payloads, space and launch vehicles, test equipment, and hardware/software.
|
NA
|
Statement of Work (SOW); Design Review Data Package
|
Space Vehicle Systems Engineering Handbook, TOR-2006(8506)-4494; Mission Risk Planning and Acquisition Tailoring Guidelines for National Security Space Vehicles, TOR-2011(8591)-5
|
| 2.2.5-2-3 Ensure Contract Data Requirements Lists (CDRLs) requested are complete and have the correct approvals, delivery schedule and data rights |
Phase 0 |
Phase A |
|
Ensure requested CDRLs are complete and meet contractual requirements.
|
NA
|
Design Review Data Package; Request for Proposal (RFP)
|
Space Vehicle Systems Engineering Handbook, TOR-2006(8506)-4494
|
| 2.2.5-2-4 Ensure the contract requirements are consistent in defining the level of government program oversight required for the test and evaluation program |
Phase 0 |
Phase A |
|
Ensure the contract requirements are consistent in defining the level of government program oversight required for the integration and verification activates.
|
NA
|
Statement of Work (SOW); Mission Assurance Plan (MAP); System Requirements Document
|
Space Vehicle Systems Engineering Handbook, TOR-2006(8506)-4494
|
| 2.2.5-2-5 Ensure integration requirements are validated and appropriately allocated and flowed down |
Phase A |
Phase B |
Phase C |
|
Ensure all integration requirements are appropriately allocated among subsystems and contracts.
|
NA
|
System Requirements Document; System Verification and Validation Plan
|
Space Vehicle Systems Engineering Handbook, TOR-2006(8506)-4494
|