| 2.3.4-1-1 Ensure contractor electrical interface requirements flow down properly and are accurate |
Phase B |
Phase C |
|
Ensure all interface requirements are properly defined and allocated to all systems/segments, subsystems and units such that all components will work together to achieve desired mission purposes. The purpose of this requirement is to ensure system power requirements are properly allocated to all units, to ensure proper command and telemetry definition for units, subsystems and system, and ensure interfaces compatibility between units, subsystems and systems/segments. Ensure Interface Control Documents/Drawings (ICD) and Interface Requirements Documents (IRD) are complete and configuration controlled.
|
NA
|
Intra-Segment ICDs; System/Segment Specification (SSS)
|
TOR-2006(8506)-4494, Space Vehicle Systems Engineering Handbook, Design & Payload Integration chapter, EDI Section
|
| 2.3.4-1-2 Ensure contractor power control plan includes power racking process, system and unit margin definition as function of major program milestones, and addresses reporting format |
Phase B |
Phase C |
Phase D1 |
|
Ensure the power control plan defines and anticipates, based on the heritage experience, the power growth throughout the design life of a unit based on the heritage status of the hardware such as new design, modified design from other spacecraft or use as is.
|
NA
|
Design Review Data Package
|
TOR-2006(8506)-4494, Space Vehicle Systems Engineering Handbook, Design & Payload Integration chapter, EDI Section
|
| 2.3.4-1-3 Ensure space vehicle power allocation and margin depletion is evaluated and assessed |
Phase B |
Phase C |
Phase D1 |
|
Ensure the sources for the power allocation is updated and documented for each unit (theoretical estimate, heritage value, actual measured value from EM or Flight unit).
|
NA
|
Design Review Data Package
|
TOR-2006(8506)-4494, Space Vehicle Systems Engineering Handbook, Design & Payload Integration chapter, EDI Section
|
| 2.3.4-1-4 Ensure contractor command and telemetry requirements and allocation documents to assess accuracy and margin depletion as function of unit development and program milestones, as well as command implementation analyses and approaches are evaluated for completeness |
Phase A |
Phase B |
Phase C |
|
Ensure command and telemetry allocations are consistent with all unit and ICD/IRD requirements. Ensure the data traffic model for the data bus show sufficient margin.
|
NA
|
Design Review Data Package
|
TOR-2006(8506)-4494, Space Vehicle Systems Engineering Handbook, Design & Payload Integration chapter, EDI Section
|
| 2.3.4-1-5 Ensure command and telemetry changes are controlled |
Phase A |
Phase B |
Phase C |
|
Ensure a change control process exists and is implemented.
|
NA
|
Configuration Management Plan (CMP)
|
TOR-2006(8506)-4494, Space Vehicle Systems Engineering Handbook, Design & Payload Integration chapter, EDI Section
|
| 2.3.4-1-6 Ensure contractor data format interface document and command and telemetry database are assessed to ensure the completion and consistency of command and telemetry database field definition across space and ground segments |
Phase A |
Phase B |
Phase C |
|
Ensure the Data Format Interface Document is configuration controlled. Command and telemetry database are used by the space vehicle, ground and test set to control and status the health of space vehicle. Therefore the command and telemetry database has to be useable on all three platforms. This necessitates the C&T database definition to be consistent to all three platforms.
|
NA
|
Command and Telemetry Database(s)
|
TOR-2006(8506)-4494, Space Vehicle Systems Engineering Handbook, Design & Payload Integration chapter, EDI Section
|
| 2.3.4-1-7 Ensure proper documentation and coordination of command and operation constraints, as well as sufficiency of telemetry for proper monitor of space vehicle system health and command execution |
Phase A |
Phase B |
Phase C |
|
Ensure the Command and Constraints Document is configuration controlled.
|
NA
|
Command and Telemetry Database(s)
|
TOR-2006(8506)-4494, Space Vehicle Systems Engineering Handbook, Design & Payload Integration chapter, EDI Section
|
| 2.3.4-1-8 Ensure the accuracy of space vehicle system and subsystem functional block diagrams, as well as End-to-End signal diagram for the purpose of failure investigation and system integrity |
Phase B |
Phase C |
Phase D1 |
|
Ensure accurate system, subsystem and unit block diagrams are available for anomaly investigation.
|
NA
|
Reliability Model and Block Diagrams
|
TOR-2006(8506)-4494, Space Vehicle Systems Engineering Handbook, Design & Payload Integration chapter, EDI Section
|
| 2.3.4-1-9 Ensure system interface requirement to allow for proper system implementation, and test points are available such that requirements can be tested/verified at system level when necessary |
Phase B |
Phase C |
|
Ensure properly defined telemetry and test points to allow efficient anomaly investigation in the system test and monitoring execution of commands.
|
NA
|
Command and Telemetry Database(s)
|
TOR-2006(8506)-4494, Space Vehicle Systems Engineering Handbook, Design & Payload Integration chapter, EDI Section
|
| 2.3.4-1-10 Ensure proper documentation of system fusing requirements, standards, analyses and design approaches |
Phase B |
Phase C |
|
Ensure sufficient engineering of fuse implementation.
|
NA
|
Reliability Model and Block Diagrams
|
TOR-2006(8506)-4494, Space Vehicle Systems Engineering Handbook, Design & Payload Integration chapter, EDI Section
|
| 2.3.4-1-11 Ensure contractor interface compatibility analyses are reviewed and any assumptions made in performing the analyses are validated |
Phase B |
Phase C |
Phase D1 |
|
Ensure for each interface that the sending and receiving sides of the interface are compatible.
|
NA
|
NA
|
TOR-2006(8506)-4494, Space Vehicle Systems Engineering Handbook, Design & Payload Integration chapter, EDI Section
|