| 2.2.5-8-1 Ensure process in place whereby elements are combined functionally and physically to form and perform as a complete system |
Phase B |
Phase C |
Phase D1 |
|
Ensure integration process is documented and reviewed at PDR and CDR. Ensure planning for major systems integration activities are completed.
|
SFWC 4.4
|
NA
|
Mission Assurance Guide, TOR-2007(8546)-6018, Rev B, ITE Chapter
|
| 2.2.5-8-2 Ensure systems of systems integration planning activities are completed |
Phase A |
Phase B |
Phase C |
|
Ensure the build up process of the System of System (SoS) operational (flight and ground ops) equipment, test support, handling, calibration, transportation and protection equipment from lower levels of integration (assembly) to that required for testing SoS maintains equipment integrity. Ensure that the integration process minimizes equipment risk and that the test support equipment are fully serviceable at all levels of integration and locations.
|
NA
|
NA
|
Mission Assurance Guide, TOR-2007(8546)-6018, Rev B
|
| 2.2.5-8-3 Ensure planned verification method addresses requirements and validates system performance with sufficient rigor |
Phase B |
Phase C |
Phase D1 |
|
Ensure a plan and a process are in place that proves the as-built item complies with the requirements baseline as determined by test, analysis, demonstration, inspection and/or similarity, and performed at all levels from the lowest level configuration item to the system. Ensure the verification method is appropriate, adequate and documented. Ensure test objectives are not compromised by schedule, budget or requirement changes.
|
AFMAN 63-119 A11.1.6
|
NA
|
Mission Assurance Guide, TOR-2007(8546)-6018, Rev B, ITE Chapter; Space Systems Verification Program and Management Process, AIAA-S-117 -2010; AFMAN 63-119 or equivalent
|
| 2.2.5-8-4 Ensure disciplined test configuration control plan is documented |
Phase C |
Phase D1 |
|
Ensure a formal process is in place to control and track system configuration during government testing that will support dedicated operational testing.
|
AFMAN 63-119 A14.5
|
NA
|
Mission Assurance Guide, TOR-2007(8546)-6018, Rev B; Space Systems Verification Program and Management Process, AIAA-S-117 -2010; AFMAN 63-119 or equivalent
|
| 2.2.5-8-5 Ensure assembly, test and checkout procedures are evaluated |
Phase C |
Phase D1 |
|
Develop an assembly, test and checkout review matrix which categorizes procedures as to criticality and significance. (Cat 1, Cat 2, Cat 3). Review and participate in all cat 1 processing procedures and data reviews. Participate and review procedures inline with the contractor's procedure development/change process. Monitor for changes.
|
NA
|
NA
|
Mission Assurance Guide, TOR-2007(8546)-6018, Rev B
|
| 2.2.5-8-6 Ensure special test facilities and equipment for integration and test verification are identified, reserved and or acquired |
Phase A |
Phase B |
Phase C |
Phase D1 |
|
Ensure that access to shared facilities (e.g. radiation, acoustics, thermal vacuum) that requires advance planning, (e.g., radiation facilities) is considered. Ensure use of government facilities is considered in test planning.
|
AFMAN 63-119 A13.4
|
NA
|
Mission Assurance Guide, TOR-2007(8546)-6018, Rev B, ITE Chapter; AFMAN 63-119 or equivalent
|
| 2.2.5-8-7 Ensure that a loading assessment for an appropriate number of internal shared equipment, such as test beds and engineering units to accommodate the baseline schedule, including multiple items/space vehicles in flow is considered |
Phase A |
Phase B |
Phase C |
Phase D1 |
|
Perform a study to ensure shared equipment items can support the usage of multiple test articles from within the program and all other programs, and any scheduled maintenance or upgrades as required.
|
NA
|
NA
|
Mission Assurance Guide, TOR-2007(8546)-6018, Rev B, ITE Chapter
|
| 2.2.5-8-8 Ensure test realism is assessed, especially operational testing |
Phase A |
Phase B |
Phase C |
|
Ensure that preliminary Integration and Test Plan, from unit to system level, is of acceptable risk and credible schedule with reasonable margins. Ensure testing is performed with operationally relevant components and scenarios as much as possible.
|
AFMAN 63-119 A13.2.3
|
NA
|
Mission Assurance Guide, TOR-2007(8546)-6018, Rev B; SDR exit criteria per TOR-2004(3909)-3360, Systems Engineer's Major Reviews for National Security Space System Programs; AFMAN 63-119 or equivalent
|
| 2.2.5-8-9 Ensure long lead planning and procurement issues are identified |
Phase A |
Phase B |
|
Ensure long lead items are addressed early in the acquisition and develop a plan. Long-lead includes permissions and agreements as well as materials.
|
NA
|
NA
|
Mission Assurance Guide, TOR-2007(8546)-6018, Rev B
|
| 2.2.5-8-10 Ensure scientific test and analysis techniques are employed |
Phase C |
Phase D1 |
|
Ensure tests and evaluations/analyses are effective, efficient, and appropriate factors and conditions are selected to produce the data required to characterize system capabilities.
|
AFMAN 63-119 A11.1.7
|
NA
|
Mission Assurance Guide, TOR-2007(8546)-6018, Rev B; AFMAN 63-119 or equivalent
|
| 2.2.5-8-11 Ensure LV/SV integrated test plans are evaluated |
Phase A |
Phase B |
Phase C |
Phase D1 |
|
Assess adequacy of contractor's plans for testing LV/SV interfaces and mission unique requirements
|
NA
|
NA
|
Mission Assurance Guide, TOR-2007(8546)-6018, Rev B
|
| 2.2.5-8-12 Ensure adequate planning for on-time delivery and integration of Government Furnished Equipment (GFE) |
Phase A |
Phase B |
Phase C |
Phase D1 |
|
Ensure planning includes early testing at contractor facilities, and identification of obsolescence issues of potentially outdated equipment.
|
NA
|
NA
|
Mission Assurance Guide, TOR-2007(8546)-6018, Rev B
|
| 2.2.5-8-13 Ensure interface control plan is integrated with the integration and test plan |
Phase A |
Phase B |
Phase C |
Phase D1 |
|
Contractor should establish and maintain an interface control plan (ICP) and it will be submitted to MDA for approval. Control plan development should be developed with the assistance of the government to identify the roles and responsibilities of the contractor in interface management with the following elements: identify external and internal interface requirements; identify all interface documentation; define the methods for flowing interface documentation into Technical Data Packages (TDP); verification Process. The contractor should have in-place a formal process to develop, maintain and control interface documentation to include Interface Control Drawings (ICDs) and documents, interface requirements specifications, and interface design descriptions. The SPO and the prime contractor should develop an Interface Control Working Group to manage interfaces to ensure compatibility and integration within contractor system and to external systems--composed of contractors, vendors and government agencies.
|
NA
|
NA
|
Mission Assurance Guide, TOR-2007(8546)-6018, Rev B
|
| 2.2.5-8-14 Ensure Systems Engineering has responsibility for implementation of System-to-Unit level requirement verification |
Phase A |
Phase B |
Phase C |
Phase D1 |
|
Ensure that verification plans are generated from unit to system according to MA TOR requirements. Ensure That all requirements are verified by analyses and test and documented in a verification ledger type summary with supporting documentation paced in an appropriate file for potential review. Ensure a complete system level assembly and integration plan is implemented that conforms to program scheduling, system requirement verification, roll up of lower level analysis and test results and Test as You Fly methodology to guarantee that all requirements are verified. Ensure Operational Test and Evaluation Requirements are defined . Ensure LV/SV Integrated Verification Plans for physical. functional performance are generated for ICD verification.
|
NA
|
NA
|
Mission Assurance Guide, TOR-2007(8546)-6018, Rev B
|
| 2.2.5-8-15 Ensure Test and Evaluation Master Plan (TEMP) and System Verification Test Plan are evaluated |
Phase A |
Phase B |
Phase C |
Phase D1 |
|
Using past experience, assure that an efficient DT&E/OT&E program is being planned that provides high fidelity data as to System of System's E2E effectiveness, suitability and operability. Verify that the proper measures of effectiveness have been identified and that element interfaces are tested in a high fidelity system environment. Assure that needed major test resources have been fully identified. Assure that appropriate roles and responsibilities have been identified for participating organizations.
|
NA
|
NA
|
Mission Assurance Guide, TOR-2007(8546)-6018, Rev B
|
| 2.2.5-8-16 Ensure operational concepts and requirement margin suitability are evaluated |
Phase A |
Phase B |
Phase C |
Phase D1 |
|
Ensure that operational requirements and Operations Concepts adequately capture nominal and worst case environmental conditions and desired system operating modes. Ensure that nominal and off-nominal (worst case) conditions are adequately treated within proposed test plans and test scenarios. Ensure that the full scope for the final System performance demonstration, System acceptance test, and System qualification test is fully coordinated with the Space System designers, the test teams, and the hardware and software suppliers.
|
NA
|
NA
|
Mission Assurance Guide, TOR-2007(8546)-6018, Rev B
|
| 2.2.5-8-17 Ensure need for simulations, models, and test-beds is assessed |
Phase A |
Phase B |
Phase C |
Phase D1 |
|
Ensure test and test threat systems and related support resources, including validated models and simulator assets, are identified and programmed, and scheduled as early as possible.
|
AFMAN 63-119 A32.3.1; AFMAN 63-119 A32.4; AFMAN 63-119 A32.5; AFMAN 63-119 A32.7
|
NA
|
Mission Assurance Guide, TOR-2007(8546)-6018, Rev B; AFMAN 63-119 or equivalent
|
| 2.2.5-8-18 Ensure Accelerated Life Test Program is assessed |
Phase A |
Phase B |
Phase C |
Phase D1 |
|
Establish and maintain an Accelerated Life Testing program throughout spiral development to detect and correct any inherent design and manufacturing flaws and determine product robustness.
|
NA
|
NA
|
Mission Assurance Guide, TOR-2007(8546)-6018, Rev B
|
| 2.2.5-8-19 Ensure COTS and heritage hardware test requirements are evaluated |
Phase A |
Phase B |
Phase C |
Phase D1 |
|
Perform due diligence to ensure that all COTS, Open Source Software (OSS), and heritage design hardware have been rigorously examined for the specific application they are intended for. Ensure COTS, OSS, and heritage design hardware will be tested using simulated ground test environments that will meet program needs. Ensure that all worst case test and accumulated fatiguing environments have been included in the test conditions including worst case cumulative environments. Avoid qualification by similarity when possible and ensure objective testing to certify COTS, OSS, and heritage design hardware meet program needs in the intended application and environments.
|
NA
|
NA
|
Mission Assurance Guide, TOR-2007(8546)-6018, Rev B
|
| 2.2.5-8-20 Ensure COTS , Open Source Software, and heritage software test requirements are evaluated |
Phase A |
Phase B |
Phase C |
Phase D1 |
|
Perform due diligence to ensure that all COTS, Open Source Software (OSS), and heritage design software have been rigorously examined for the specific application they are intended for. Ensure COTS, OSS, and heritage design software will be tested using simulated ground test environments that will meet program needs. Ensure that all worst case test and accumulated fatiguing environments have been included in the test conditions including worst case cumulative environments. Avoid qualification by similarity when possible and ensure objective testing to certify COTS, OSS, and heritage design software meet program needs in the intended application and environments.
|
NA
|
NA
|
Mission Assurance Guide, TOR-2007(8546)-6018, Rev B
|
| 2.2.5-8-21 Ensure system integration planning is evaluated |
Phase A |
Phase B |
Phase C |
Phase D1 |
|
Ensure preliminary Segment integration planning. Ensure the build up process of the Space Vehicle segment from lower levels of integration (assembly) to the system level and beyond to system of systems maintains equipment integrity. Ensure that the integration process minimizes equipment risk and that the flight articles are fully serviceable at all levels of integration.
|
NA
|
NA
|
Mission Assurance Guide, TOR-2007(8546)-6018, Rev B
|
| 2.2.5-8-22 Ensure test planning adequately covers all operating modes and mission phases |
Phase B |
Phase C |
Phase D1 |
|
Ensure Test-like-you-fly process is implemented and like-you-fly tests are allocated to the unit/component level as appropriate.
|
NA
|
Integration and Test Plans; System Test Plan
|
Space Vehicle Systems Engineering Handbook, TOR-2006(8506)-4494
|
| 2.2.5-8-23 Ensure unit test plans are complete, objectives are clear and test success criteria are defined |
Phase A |
Phase B |
Phase C |
Phase D1 |
|
Ensure design and manufacturing principles are in place that will result in minimum returns and rework at the payload system level. Ensure testing performed to verify unit functionality and performance in an appropriate environments to include electromagnetic.
|
SFWC 2.4.2.3.4
|
NA
|
Space Vehicle Systems Engineering Handbook, TOR-2006(8506)-4494
|
| 2.2.5-8-24 Ensure Measures of Effectiveness are defined in system performance requirements, and can be tested and verified |
Phase A |
Phase B |
Phase C |
Phase D1 |
|
Ensure performance criteria are linked directly to system performance thresholds and requirements. Ensure these criteria are tracked and reviewed throughout program development. Ensure all stakeholders are involved in performance criteria changes and approvals. Ensure CBRD or equivalent contains sufficient definition to develop measures of effectiveness.
|
AFMAN 63-119 A3.3.1; AFMAN 63-119 A3.3.2; AFMAN 63-119 A4.8
|
NA
|
AFMAN 63-119 or equivalent; Mission Assurance Guide, TOR-2007(8546)-6018, Rev B, Requirements Analysis and Validation Chapter
|
| 2.2.5-8-25 Ensure all system functions are tested during developmental testing, prior to starting operational tests |
Phase D1 |
|
Ensure the system is mature and stable before entering operational test. Ensure functionality and performance are assessed throughout development test. If the system has interoperability requirements (with other systems), ensure developmental test takes place at the system-of-systems level.
|
AFMAN 63-119 A14.6.5; AFMAN 63-119 A15.1
|
NA
|
AFMAN 63-119 or equivalent; Mission Assurance Guide, TOR-2007(8546)-6018, Rev B, Integration, Test, and Evaluation Chapter
|