| 4.4.10-4-1 Ensure subsystem design including units, assemblies, sub-assemblies and parts meets the mission performance requirements |
Phase A |
Phase B |
Phase C |
|
Pre-Phase A, as applicable, ensure the design satisfies the requirements under the conditions specified by the Design Reference Mission. There should be a realistic worst-case scenario to show that the requirements can be met with margin. Phase A onward, the derived CONOPS should be in a particular document (Flight Requirements and Ops documents) or operations working group products. Some mission concepts may not be directly translated to subsystem requirements in terms of the overall mission operability. The subsystem must be validated against how the components will be used for that particular application.
|
NA
|
NA
|
Space Vehicle Systems Engineering Handbook, TOR-2006(8506)-4494; Mission Assurance Guide, TOR-2007(8546)-6018, Rev B
|
| 4.4.10-4-2 Ensure trade studies were conducted and the design baseline satisfies mission requirements and the analysis of alternatives has identified the baseline as the best value |
Phase A |
Phase B |
Phase C |
|
Ensure that all trade studies are realizable in terms of technology used and conform to system requirement and physical constraints. Check that viable candidates received appropriate consideration.
|
NA
|
NA
|
Space Vehicle Systems Engineering Handbook, TOR-2006(8506)-4494
|
| 4.4.10-4-3 Ensure subsystem technology readiness and risk burn-down plan have been assessed |
Phase A |
Phase B |
Phase C |
|
Ensure subsystem technologies, including manufacturing, supplier readiness and programmatic readiness, are mature enough to support the development timeline. Check that the risk mitigation plans are sufficient, funded and conclude at the right time.
|
NA
|
NA
|
Space Vehicle Systems Engineering Handbook, TOR-2006(8506)-4494
|
| 4.4.10-4-4 Ensure subsystem hardware and software (as applicable) functions are described in the subsystem specification |
Phase A |
Phase B |
Phase C |
|
Ensure that descriptive functions for subsystems and units (including software) are detailed enough for new personnel to understand how the unit or subsystem behaves both individually and within the system.
|
NA
|
NA
|
Space Vehicle Systems Engineering Handbook, TOR-2006(8506)-4494
|
| 4.4.10-4-5 Ensure subsystem hardware and software (as applicable) is identified as heritage, modified, or new |
Phase B |
Phase C |
|
Ensure heritage qualification adequacy is documented by analysis and test.
|
NA
|
NA
|
Objective Criteria for Heritage Hardware Reuse, TOR-2010(8591)-19; Reuse of Hardware and Software Products, TOR-2009(8546)-8604
|
| 4.4.10-4-6 Ensure all defined contract deliverables and relevant contractor data are complete and accurate to support design reviews |
Phase A |
Phase B |
Phase C |
|
Ensure all relevant data is readily available and delivered to support design reviews and design forums.
|
NA
|
NA
|
Space Vehicle Systems Engineering Handbook, TOR-2006(8506)-4494
|
| 4.4.10-4-7 Ensure architecture is documented and explained in sufficient detail to confirm that associated requirements could be satisfied and to enable interface and lower-level developments |
Phase A |
|
SDR: This may include block diagrams, state diagrams, command, telemetry and other data item lists, data transfer capabilities, computational throughput estimates, typical and fault condition data flows
|
NA
|
NA
|
Space Vehicle Systems Engineering Handbook, TOR-2006(8506)-4494
|
| 4.4.10-4-8 Ensure subsystem components' mechanical designs are adequate including any alignment issues |
Phase B |
Phase C |
|
For PDR, ensure the environmental levels, estimate maximum displacement, tolerance issues, etc are provided. Provide mitigation plan for any issues. Provide updates at CDR.
|
NA
|
NA
|
Space Vehicle Systems Engineering Handbook, TOR-2006(8506)-4494
|
| 4.4.10-4-9 Ensure subsystem components' thermal designs are adequate |
Phase B |
Phase C |
|
Ensure provision of analysis which shows heat flux is within limits and piece parts meet electrical stress derating limits during test and mission. PDR - describe why unit thermal models are correct. Provide preliminary estimates with mitigation plans for any issues. For CDR, ensure final estimates with approved waivers for any deviations.
|
NA
|
NA
|
Space Vehicle Systems Engineering Handbook, TOR-2006(8506)-4494
|
| 4.4.10-4-10 Ensure Product Design is adequate to fit all piece parts within layout and manufacturing rules |
Phase B |
Phase C |
|
For PDR, ensure provision of preliminary board layouts, demonstrating that piece-parts fit within layout rules. For CDR, ensure update with final design.
|
NA
|
NA
|
Space Vehicle Systems Engineering Handbook, TOR-2006(8506)-4494
|
| 4.4.10-4-11 Ensure subsystem design meets survivability requirements |
Phase B |
Phase C |
|
For PDR, ensure provision of preliminary shielding estimates, part capabilities. Provide plan to address any inadequate margins. CDR - update.
|
NA
|
NA
|
Space Vehicle Systems Engineering Handbook, TOR-2006(8506)-4494
|
| 4.4.10-4-12 Ensure EMC requirements are addressed and a control plan is generated |
Phase B |
Phase C |
|
Ensure that MA EMC spec are flowed down and that the EMC control plan is generated for the CDH subsystem with emphasis on EMC design and verification at the lowest level of build. Ensure EMC issues are identified and have appropriate mitigation plans.
|
NA
|
NA
|
Space Vehicle Systems Engineering Handbook, TOR-2006(8506)-4494
|
| 4.4.10-4-13 Ensure harnessing, fusing, mounting, etc with the rest of the system is appropriate |
Phase B |
Phase C |
|
Show harness layout, accessibility. Show how harnesses cannot be miss-mated. Show panel layout with units identified. Ensure fusing has appropriate margin. For PDR, ensure provision of preliminary design meets constraints/envelope provide by the rest of the system. Provide mitigation for any issues. CDR - update and show compliance.
|
NA
|
NA
|
Space Vehicle Systems Engineering Handbook, TOR-2006(8506)-4494
|
| 4.4.10-4-14 Ensure that all authorized commands and specific telemetry formats are allocated to specific operational states and verify their operation in unit and subsystems |
Phase B |
Phase C |
Phase D1 |
|
Ensure unauthorized commands have no effect. Ensure that critical commands, that could affect SV health and Safety, cannot be accidentally invoked without multiple failures or errors. PDR - provide preliminary list and verification approach. CDR - provide final list and evidence that design supports requirements.
|
NA
|
NA
|
Space Vehicle Systems Engineering Handbook, TOR-2006(8506)-4494
|
| 4.4.10-4-15 Ensure design limitations and constraints are clearly documented for test verification, SV Integration and for Launch and Operations purposes |
Phase B |
Phase C |
Phase D1 |
|
Ensure that the limitations and constraints are considered in the ground station required operational procedures (ROPs). For PDR, ensure any limitation/constraint still meets requirements and cannot be eliminated. For CDR - Ensure all items are captured. D1, ... revise documentation as necessary.
|
NA
|
NA
|
Space Vehicle Systems Engineering Handbook, TOR-2006(8506)-4494
|
| 4.4.10-4-16 Ensure fault modes and detection planning are clearly defined, and reasonable |
Phase B |
Phase C |
Phase D1 |
|
Ensure that faults are isolated and reported to the level of replaceable component. Ensure that Subsystem requirements applied to Ground Support or to Fault Management can be implemented and verified. For PDR, ensure preliminary list of reportable faults and requirements for FM or Ground. Identify verification approach and resources. Ensure final at CDR
|
NA
|
NA
|
Space Vehicle Systems Engineering Handbook, TOR-2006(8506)-4494
|
| 4.4.10-4-17 Ensure ASIC and FPGA developments apply sound development practices and standards |
Phase B |
Phase C |
|
For PDA, ensure ASIC/FPGA parent item requirements are documented and that they are traced to ASIC/FPGA requirements. Ensure that the ASIC/FPGA architecture and circuit module partitioning is solidified, and that the device floor plan, packaging, and I/O characteristics are defined. CDA - ensure complete ASIC/FPGA requirement compliance, final timing margin sufficiency, device packaging sufficiency, and for ASICs also ensure sufficient grounding provisions and foundry checklist compliance.
|
NA
|
NA
|
Space Vehicle Systems Engineering Handbook, TOR-2006(8506)-4494, ASIC/FPGA Dev STD (TOR-2010(8591)-10)
|
| 4.4.10-4-18 Ensure that any potentially systemic design issues are considered for a Design Advisory |
Phase B |
Phase C |
Phase D1 |
Phase D2 |
Phase D3 |
|
Any design or architecture issue that has severe, systemic, or widespread consequences is a potential candidate for a Design Advisory. Design Advisories provide the community with timely and interim notification of an important design issue which may ultimately be captured in a specification or standard.
|
NA
|
NA
|
NA
|