| 2.3.17-1-1 Ensure customer requirement(s) for a dead bus recovery are documented and consistent with the mission classification |
Phase 0 |
Phase A |
Phase B |
Phase C |
|
Ensure Class A and B missions have dead bus recovery capabilities. Class C and D missions may have limited or no dead bus recovery capability.
|
NA
|
NA
|
TOR-2018-00316TOR-2018-00319
|
| 2.3.17-1-2 Ensure dead bus recovery requirement(s) are properly documented in System Specification |
Phase A |
Phase B |
Phase C |
|
Ensure all requirements are documented with the word "shall". A dead bus recovery capability description with words "will", "may", "should", "could", etc. are not sufficient since they might not require verification. Note that some contractors' internal command media have their own DBR requirements. Applicability of these internal requirements to the program should be documented.
|
NA
|
NA
|
TOR-2018-00316TOR-2018-00319
|
| 2.3.17-1-3 Ensure TOR-2018-00316 is included as a compliance document |
Phase 0 |
Phase A |
|
Ensure TOR-2018-00316 is part of the compliance document for classes A and B missions. For classes C and D missions, a trade study or cost/benefit analysis might be needed.
|
NA
|
NA
|
TOR-2018-00316TOR-2018-00319
|
| 2.3.17-1-4 Ensure tailoring of TOR-2018-00316 is consistent with mission classification and contractual requirements |
Phase 0 |
Phase A |
|
Ensure tailoring of TOR-2018-00316 is consistent with the mission classification.
|
NA
|
NA
|
TOR-2018-00316TOR-2018-00319
|
| 2.3.17-1-5 Ensure trade studies are performed to identify dead bus recovery capability versus constraints |
Phase A |
Phase B |
Phase C |
|
Ensure all the necessary capabilities for DBR are determined. Identify and document the DBR constraints.
|
NA
|
NA
|
TOR-2006(8506)-4494
|
| 2.3.17-1-6 Ensure dead bus recovery CONOP is consistent with the defined dead bus recovery functions and constraints |
Phase A |
Phase B |
Phase C |
|
Ensure DBR CONOP (Concept of Operation) is consistent with the satellite's design capability.
|
NA
|
NA
|
TOR-2006(8506)-4494
|
| 2.3.17-1-7 Ensure dead bus recovery requirements are properly flowed down to lower levels |
Phase A |
Phase B |
Phase C |
|
Ensure DBR system level requirements are allocated down to the relevant components/units.
|
NA
|
NA
|
TOR-2006(8506)-4494
|
| 2.3.17-1-8 Ensure dead bus recovery requirements are coordinated between the Space Segment and Ground Segment |
Phase 0 |
Phase A |
Phase B |
Phase C |
|
Ensure the Space Segment to Ground Segment Interface Control Document includes specific interface requirements after a dead bus event. These dead bus interface requirements might not be the same as the nominal operational interface requirements.
|
NA
|
NA
|
TOR-2006(8506)-4494
|
| 2.3.17-1-9 Ensure dead bus recovery requirements are verifiable |
Phase A |
Phase B |
Phase C |
|
Ensure DBR requirements are verifiable by analysis or demonstration at system level. Since DBR is a capability, inspection of lower level verification results is usually not applicable at system level. If the capability is not demonstrated, then analysis is needed showing how lower level verification results combines to achieve system level DBR capability.
|
NA
|
NA
|
TOR-2006(8506)-4494
|