| 2.3.4-2-1 Ensure accurate execution of command and telemetry database to the flight space vehicle system |
Phase C |
Phase D1 |
|
Ensure the command and telemetry (C&T) databases are useable on the space vehicle, ground segment and test sets. This necessitates the C&T database definition to be consistent to all three platforms. Integration and test will test the interface between the command and telemetry database and the flight system.
|
NA
|
Command and Telemetry Database(s)
|
TOR-2006(8506)-4494, Space Vehicle Systems Engineering Handbook, Design & Payload Integration chapter, EDI Section
|
| 2.3.4-2-2 Ensure command and telemetry changes are controlled |
Phase C |
Phase D1 |
|
Ensure a change control process exists and implemented. This is usually documented in the Configuration Control Plan.
|
NA
|
Configuration Management/Audit Processes and Products; Command and Telemetry Database(s)
|
TOR-2006(8506)-4494, Space Vehicle Systems Engineering Handbook, Design & Payload Integration chapter, EDI Section
|
| 2.3.4-2-3 Ensure all Electrical Ground Support Equipment (GSE) interfaces to flight hardware have been reviewed for electrical design integration (EDI) concerns |
Phase C |
Phase D1 |
|
Ensure the review of the interface between the test set and flight hardware such that the test set operation or its failure will not damage the flight hardware. Interface compatibility analysis has to be evaluate to ensure the safety of the flight hardware. Besides ensuring no failure propagation from EGSE to flight vehicle, physical mating compatibility needs to be reviewed (connector type, pin/socket).
|
NA
|
Intra-Segment ICDs
|
TOR-2006(8506)-4494, Space Vehicle Systems Engineering Handbook, Design & Payload Integration chapter, EDI Section
|
| 2.3.4-2-4 Ensure electrical design integration (EDI) has reviewed and approved electrical test procedures |
Phase C |
Phase D1 |
|
Ensure the feasibility of the space vehicle test by reviewing test plans and test procedures. In certain case EDI will need to review test requirement documents to ensure the validity and feasibility of the test. EDI needs to ensure the test setup and test environment would not invalidate the test results.
|
NA
|
NA
|
TOR-2006(8506)-4494, Space Vehicle Systems Engineering Handbook, Design & Payload Integration chapter, EDI Section
|
| 2.3.4-2-5 Ensure the power budget accuracy through unit, subsystem and system power measurement data as well as all operation modes |
Phase C |
Phase D1 |
|
Ensure the unit, subsystem and system test results are consistent with their power budget in the power allocation document.
|
NA
|
NA
|
TOR-2006(8506)-4494, Space Vehicle Systems Engineering Handbook, Design & Payload Integration chapter, EDI Section
|
| 2.3.4-2-6 Ensure all contractor anomalies are analyzed and evaluated, including contractor anomaly resolution and process during contractor integration and test activities |
Phase C |
Phase D1 |
|
Ensure the anomaly resolution and process (i.e., Deficiency Report Reviews, Failure Review Board Participation, Test Procedure and Plan Reviews, Test Data Reviews, Mission Readiness Review, Test Readiness Review, etc.) is implemented and captures EDI anomalies during contractor integration and test activities.
|
NA
|
NA
|
TOR-2006(8506)-4494, Space Vehicle Systems Engineering Handbook, Design & Payload Integration chapter, EDI Section
|