| 4.5.6-1-1 Ensure government involvement with design implementation and verification process that considers all disciplines involved, and all interface organizations |
Phase A |
Phase B |
Phase C |
Phase D1 |
|
Ensure contractor schedule has reasonable allotted timeframes to accomplish tasks (based on historical data from similar programs) plus margin for unexpected events. If historical data inappropriate due to procurement type, provide maturity decision basis and risk margins to demonstrate readiness to proceed on commitment of resources and schedule for the next cycle of the development/integration build.
|
NA
|
NA
|
Mission Assurance Guide, TOR-2007(8546)-6018, Rev B, Program Assurance Chapter
|
| 4.5.6-1-2 Ensure schedule for design, build and test is provided and is reasonable |
Phase A |
Phase B |
Phase C |
Phase D1 |
|
Ensure contractor has identified appropriate resources, risks and mitigation plans that make schedule feasible within budget constraints.
|
NA
|
NA
|
Space Vehicle Systems Engineering Handbook, TOR-2006(8506)-4494
|
| 4.5.6-1-3 Ensure system engineering responsibility is defined at contractor in sufficient detail for program execution |
Phase A |
Phase B |
Phase C |
Phase D1 |
|
Ensure contractor has allocated resources for tasks, including tailoring and execution of the mission assurance standards.
|
NA
|
NA
|
Mission Assurance Guide, TOR-2007(8546)-6018, Rev B, Program Assurance Chapter
|
| 4.5.6-1-4 Ensure lessons learned are reviewed for applicability to payload and incorporated into design, manufacture/build, test and operations |
Phase A |
Phase B |
Phase C |
Phase D1 |
Phase D2 |
Phase D3 |
|
Ensure lessons learned databases are reviewed and applied, as appropriate. Ensure interface exists to problem alerting databases, including a surveillance process for relevant alerts.
|
NA
|
NA
|
Space Vehicle Systems Engineering Handbook, TOR-2006(8506)-4494; Why Satellites Fail: Lessons for Mission Success, TOR-2009(8617)-8704
|
| 4.5.6-1-5 Ensure impact of any critical issue associated with the payload is addressed with a timely execution plan |
Phase B |
Phase C |
Phase D1 |
|
Ensure tracking and resolution activities are documented for any critical issues, as defined by the program. Ensure issues have closeout mitigation plans with schedules and resources that show acceptable closing for successful program execution within cost and schedule constraints.
|
NA
|
NA
|
Space Vehicle Systems Engineering Handbook (TOR-2006(8506)-4494)
|
| 4.5.6-1-6 Ensure that the program executability methodology incorporates independent analysis and/or reviews to validate design, build and final product |
Phase B |
Phase C |
Phase D1 |
|
Ensure that independent reviews be considered for manufacturing issues, parts issues, and issues involving Functional Configuration Audits, Physical Configuration Audits. Ensure that independent reviews be considered for: Like-you-fly tests and exceptions, critical qualification margins, single point failures, first flight items, nonconformance items, anomalies, escapes, unverified failures, out of sequence work, extensive redesign, out-of-family measurements, general supplier issues in manufacturing, new design implementations, schedule and performance concerns, etc.
|
NA
|
NA
|
Space Vehicle Systems Engineering Handbook, TOR-2006(8506)-4494
|
| 4.5.6-1-7 Ensure problem identification, failure review and corrective action processes are adequate |
Phase A |
Phase B |
Phase C |
Phase D1 |
Phase D2 |
Phase D3 |
|
Ensure the Parts, Materials, Processes Control Board and Failure Review Board processes are in place and implemented. Ensure anomaly resolution is addressed and resolved. Ensure all anomaly identification and resolution packages and sell-off packages are documented and filed. Ensure that failure and corrective action processes include interface to problem alerting processes.
|
NA
|
NA
|
Space Vehicle Systems Engineering Handbook, TOR-2006(8506)-4494, TOR-2011(8591)-19, Failure Review Board Guidance Document
|