![](media/image1.png){width="8.409722222222221in"
height="6.497222222222222in"}

![](media/image2.png){width="8.248611111111112in"
height="6.4944444444444445in"}

  -------------- -------------------------------------------------------------- ----
  Introduction                                                                  6

  Standards,                                                                    7
  Processes, and                                                                
  Rules                                                                         
  Hierarchy                                                                     

  Goddard Open                                                                  8
  Learning                                                                      
  Design                                                                        
  (G.O.L.D)                                                                     
  Standard                                                                      
  Architecture                                                                  

  GSFC Project                                                                  9
  Lifecycle                                                                     

  User\'s Guide                                                                 10

  GSFC Rules                                                                    

  1.0 Systems                                                                   
  Engineering                                                                   

  1.01           Requirements Management                                        11

  1.02           Development & Implementation of Mission Operations Concept     12

  1.03           Verification of Mission Requirements                           13

  1.04           System Modes                                                   14

  1.05           Single Point Failures                                          15

  1.06           Resource Margins                                               16

  1.07           End-to-End GN&C Phasing                                        18

  1.08           End-To-End Testing                                             19

  1.09           Test Like You Fly                                              20

  1.10           Logistics and Spares                                           21

  1.11           Qualification of Heritage Flight Hardware                      22

  1.12           Units of Measurement                                           23

  1.13           Performance Demonstration During Qualification Testing         24

  1.14           Mission Critical Telemetry                                     25

  1.15           GSE Use at Launch Site                                         26

  1.16           Ground Systems Configuration                                   27

  1.17           Safe Hold Mode                                                 28

  1.18           Physically Co-Located Redundant Elements                       29

  1.19           Initial Thruster Firing Limitations                            30

  1.20           Manifold Joints of Hazardous Propellants                       31

  1.21           Overpressurization Protection in Liquid Propulsion Systems     32
  -------------- -------------------------------------------------------------- ----

  ------------ -------------------------------------------------------------- ----
  1.22         Purging of Residual Test Fluids                                33

  1.23         Spacecraft \'OFF\' Command                                     34

  1.24         Propulsion System Safety Electrical Disconnect                 35

  1.25         Redundant Systems                                              36

  1.26         Safety Inhibits & Fault Tolerance                              37

  1.27         Propulsion System Overtemp Fuse                                38

  1.28         Unintended Propellant Vapor Ignition                           39

  1.29         Leakage of Hazardous Propellant                                40

  1.30         Controller Stability Margins                                   41

  1.31         Actuator Sizing Margins                                        42

  1.32         Thruster and Venting Impingement                               43

  1.33         Polarity Checks of Critical Components                         44

  1.34         Closeout Photo Documentation of Key Assemblies                 45

  1.35         Maturity of New Technologies                                   46

  1.36         Block-Redundant Component Failure                              47

  1.37         Stowage Configuration                                          48

  1.38         Configuration Command Confirmation                             49

  2.0                                                                         
  Electrical                                                                  

  2.01         Flight Electronic Hardware Operating Time                      50

  2.02         EEE Parts Program for Flight Missions                          51

  2.03         Radiation Hardness Assurance Program                           52

  2.04         Dedicated Hardware ETU and EGSE                                53

  2.05         System Grounding Architecture                                  54

  2.06         System Fusing Architecture                                     55

  2.07         End-to-End Test of Release Mechanism for Flight Deployables    56

  2.08         Secondary Circuit Failure                                      57

  2.09         Spectrum Allocation Considerations                             58

  2.10         Electronic Design for Flight Missions                          59

  2.11         EMI/EMC Design for Flight Missions                             60

  2.12         Printed Circuit Board Coupon Analysis                          61
  ------------ -------------------------------------------------------------- ----

  ------------ -------------------------------------------------------------- ----
  2.13         Electrical Connector Mating                                    62

  2.14         Capping of Test Point and Plugs                                63

  2.15         Flight and Ground Electrical Hardware                          64

  2.16         Solar Arrays                                                   65

  2.17         I&T Development Input                                          66

  2.18         Redundant Functions                                            67

  2.19         Multiple Circuit Power Bus Loss                                68

  2.20         Single Point Failure Dependency in Active-Redundant            69
               Cross-Strapped Architectures                                   

  2.21         Gross Failure of Integrated Circuits                           70

  2.22         Corona Region Testing of High Voltage Equipment                71

  3.0 Software                                                                

  3.01         Verification+Validation Program for Mission Software Systems   72

  3.02         Elimination of Dead Software/Code                              73

  3.03         High Fidelity Interface Simulation Capabilities                74

  3.04         T&C System Selection Trade Study for Operations Ground System  75

  3.05         Flight / Ground System Test Capabilities                       76

  3.06         Dedicated ETU for Flight Software (FSW) Testing                77

  3.07         Flight Software Margins                                        78

  3.08         Reserved                                                       

  3.09         Software Development Approach                                  82

  3.10         Flight Operations Preparations and Team Development            83

  3.11         Long Duration and Failure Free System Level Test of Flight     84
               Software                                                       

  3.12         Visibility of Spacecraft State                                 85

  3.13         Operational Software Redundant Element                         86

  3.14         Command Procedure Changes                                      87

  3.15         Test and GSE Software Interfaces                               88

  4.0                                                                         
  Mechanical                                                                  

  4.01         Contamination Control, Planning, and Execution                 89

  4.02         Reserved                                                       

  4.03         Structural Analysis and Design Factors of Safety               90

  4.04         Reserved                                                       

  4.05         Reserved                                                       

  4.06         Validation of Thermal Coatings Properties                      91

  4.07         Solder Joint Intermetallics Mitigation                         92

  4.08         Space Environment Effects on Material Selection                93
  ------------ -------------------------------------------------------------- ----

  ------------- -------------------------------------------------------------- -----
  4.09          Mechanical Test Factors and Duration                           94

  4.10          Minimum Workmanship                                            95

  4.11          Testing in Flight Configuration                                96

  4.12          Structural Proof Testing                                       97

  4.13          Modal Survey Characterization                                  98

  4.14          Structural Qualification                                       99

  4.15          Torque Margin                                                  100

  4.16          Reserved                                                       

  4.17          Reserved                                                       

  4.18          Deployment and Articulation Verification                       101

  4.19          Reserved                                                       

  4.20          Fastener Locking                                               102

  4.21          Reserved                                                       

  4.22          Precision Component Assembly                                   103

  4.23          Life Test                                                      104

  4.24          Mechanical Clearance Verification                              105

  4.25          Thermal Design Margins                                         106

  4.26          Thermal Design Margins - Unplanned Conditions                  107

  4.27          Test Temperature Margins                                       108

  4.28          Thermal Design Margin Verification                             109

  4.29          Thermal-Vacuum Cycling                                         110

  5.0                                                                          
  Instruments                                                                  

  5.01          Reserved                                                       

  5.02          Reserved                                                       

  5.03          Reserved                                                       

  5.04          Instrument Testing for Multipaction                            111

  5.05          Fluid Systems GSE                                              112

  5.06          Flight Instrument Characterization Standard                    113

  5.07          Reserved                                                       

  5.08          Laser Development Contamination Control                        114
  ------------- -------------------------------------------------------------- -----

  ---------- -------------------------------------------------------------- -----
  5.09       Cryogenic Pressure Relief                                      115

  Glossary                                                                  116

  Change                                                                    126
  History                                                                   
  ---------- -------------------------------------------------------------- -----

**INTRODUCTION**

Goddard Space Flight Center (GSFC) Rules are a high-level subset of all
the design rules required for safety and mission success for all space
flight products. These rules spell out the technical or design
requirements that every Goddard project shall meet regardless of its
implementation approach. GSFC Rules are not replacements for existing
Goddard Procedural Requirements (GPRs) or NASA Procedural Requirements
(NPRs). NPRs and GPRs are specific, detailed procedures for implementing
NASA and Goddard policies, and as such they often address project
management requirements per NASA Procedural Requirement (NPR) 7120.5
that do not fall within the scope of the GSFC Rules. Figure 1 provides a
hierarchy of where the GSFC Rules fit within the Center's larger
collection of rules. Figure 2 illustrates the role the GSFC Rules play
in the Goddard Open Learning Design (G.O.L.D.) approach to knowledge
management. GSFC Rules are not intended to serve as a "cookbook" or
"how-to" guide, but rather as another tool for assessing overall project
risk and assuring mission success.

GSFC Rules are defined and apply in relation to the lifecycle of a
mission or project. (See Figure 3.) All products shall be designed,
developed, verified and operated in accordance with the GSFC Rules.
Exceptions shall be permitted only by formal waiver or deviation,
processed and approved in accordance with GPR 8070.4, or by virtue of
the requirement's non-applicability to the product, as explicitly stated
in the rule. Figure 4 defines the rule structure and explains the
difference between the rule principle and rule activities, with respect
to project compliance. The Principle states the requirement of each
rule, and a formal waiver or deviation is required for non-compliance.
Activities are best practices, identified across lifecycle phases.
Non-compliance with activities does not require waivers or deviations,
but may generate a request for action.

The Office of Mission Success (OMS) shall develop and maintain the GSFC
Rules for the Design, Development, Verification, and Operation of Flight
Systems. GSFC Rules shall adhere to the following criteria:

a\) It is a high-value principle to establish the methodology necessary
to consistently and efficiently achieve safety and mission success;

b\) It is important enough to require compliance, or formal waivers, for
all GSFC projects;

c\) The rationale is based on sound engineering practice, systems
management principles, or lessons learned; and

d\) A system engineering product or other objective verification method
is identified at one or more milestones in the project life cycle.

GSFC Rules shall be configuration-controlled and accessible to all GSFC
employees. A technical authority designated for each rule will be
responsible for validating the principle, rationale, verification
requirements, related guidance and lessons learned, and participating in
the evaluation of proposed changes, waivers and deviations.

![](media/image3.jpeg){width="7.927777777777778in"
height="6.149305555555555in"}

***Figure 1***

\* Mission risk classification will be addressed in a future revision.

![](media/image4.jpeg){width="8.995833333333334in"
height="5.291666666666667in"}***Figure 2***

![](media/image5.jpeg){width="8.99375in" height="5.273611111111111in"}

> ***Figure 3***

![](media/image6.jpeg){width="8.218055555555555in"
height="6.156944444444444in"}

***Figure 4***

<table>
<colgroup>
<col style="width: 10%" />
<col style="width: 12%" />
<col style="width: 8%" />
<col style="width: 4%" />
<col style="width: 12%" />
<col style="width: 12%" />
<col style="width: 2%" />
<col style="width: 10%" />
<col style="width: 5%" />
<col style="width: 7%" />
<col style="width: 12%" />
</colgroup>
<tbody>
<tr class="odd">
<td><strong>1.01</strong></td>
<td colspan="6"><strong>Requirements Management</strong></td>
<td colspan="4"><strong>Systems Engineering</strong></td>
</tr>
<tr class="even">
<td><strong>Principle:</strong></td>
<td colspan="10">A requirements management process shall be developed
throughout the lifecycle that includes requirements identification,
tracking, and documentation as well as a flow-down and traceability of
<a href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">Level 1
requirements</a> to implementation requirements.</td>
</tr>
<tr class="odd">
<td><strong>Rationale:</strong></td>
<td colspan="10">Clear, traceable requirements lead to a good
understanding of how high level objectives and requirements drive
mission design and success.</td>
</tr>
<tr class="even">
<td><strong>Phase:</strong></td>
<td colspan="10"><strong>&lt;A A B C D E F</strong></td>
</tr>
<tr class="odd">
<td><strong>Activities:</strong></td>
<td>1. Develop <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">traceability
matrix</a>.<br />
2. Develop draft Mission Requirements Document.</td>
<td colspan="2">1. Update <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">traceability
matrix</a>.<br />
2. Define traceable <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">Level 2
requirements</a> in Mission Requirements Document.<br />
3. Identify requirements management tools for Phases B, C, &amp;
D.<br />
4. Validate consistency of requirements from all mission elements.</td>
<td>1. Update Mission Requirements Document and put under <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">CM</a>.<br />
2. Implement requirements management tool.<br />
3. Identify documentation structure required to define implementation of
<a href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">Level 2
requirements</a>, <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">Level 3
requirements</a>, and <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">Level 4
requirements</a>.<br />
4. Define Level 3 and 4 requirements and draft requirement
documents.<br />
5. Develop <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">SEMP</a>.</td>
<td>1. Update Mission Requirements Document.<br />
2. Track changes to <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">Level 2
Requirements</a>, <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">Level 3
requirements</a>, and <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">Level 4
requirements</a>.</td>
<td colspan="2">1. Verify consistency of requirements in <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">traceability
matrix</a>.<br />
2. Document requirements verification.</td>
<td colspan="2">1. Verify that mission operations requirements are still
valid and make appropriate contingency plans.</td>
<td>1. Verify that disposal requirements are still valid and make
appropriate contingency plans.</td>
</tr>
<tr class="even">
<td><strong>Verification:</strong></td>
<td>1. Verify through project team concurrence, peer review, and at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">MCR</a>.</td>
<td colspan="2">1. Verify at MRR and <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">MDR</a>.</td>
<td>1. Verify at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">PDR</a>.</td>
<td>1. Verify through peer review and at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">CDR</a>.</td>
<td colspan="2">1. Verify through peer review and at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">PER</a>, <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">MOR</a>, <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">FOR</a>, and <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">PSR</a>.</td>
<td colspan="2">N/A</td>
<td>N/A</td>
</tr>
<tr class="odd">
<td colspan="3"><p><strong>Revision Status:</strong></p>
<p>Baseline</p></td>
<td colspan="6"><p><strong>Owner:</strong></p>
<p>Mission Engineering and Systems Analysis Division (590)</p></td>
<td colspan="2"><p><strong>Reference:</strong></p>
<p>GPR 7120.5A</p></td>
</tr>
</tbody>
</table>

<table>
<colgroup>
<col style="width: 10%" />
<col style="width: 12%" />
<col style="width: 8%" />
<col style="width: 4%" />
<col style="width: 12%" />
<col style="width: 12%" />
<col style="width: 2%" />
<col style="width: 10%" />
<col style="width: 5%" />
<col style="width: 7%" />
<col style="width: 12%" />
</colgroup>
<tbody>
<tr class="odd">
<td><strong>1.02</strong></td>
<td colspan="6"><strong>Development &amp; Implementation of Mission
Operations Concept</strong></td>
<td colspan="4"><strong>Systems Engineering</strong></td>
</tr>
<tr class="even">
<td><strong>Principle:</strong></td>
<td colspan="10">The Mission Operations Concept and Plan shall be
defined and its implementation shall be verified throughout the
lifecycle.</td>
</tr>
<tr class="odd">
<td><strong>Rationale:</strong></td>
<td colspan="10">The Mission Operations Plan is critical to the
development of mission architecture necessary for a successful launch,
deployment, commission, operation, and disposal.</td>
</tr>
<tr class="even">
<td><strong>Phase:</strong></td>
<td colspan="10"><strong>&lt;A A B C D E F</strong></td>
</tr>
<tr class="odd">
<td><strong>Activities:</strong></td>
<td>1. Establish and document a concept for operations that incorporates
instrument operations concept and accomplishes <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">Level 1
requirements</a>.</td>
<td colspan="2">1. Identify all mission operation modes and
configurations.<br />
2. Update concept for operations.<br />
3. Develop a concept for ground system design.</td>
<td>1. Draft Operations Concept.<br />
2. Identify contingency concepts and safe hold modes.<br />
3. Develop requirements for ground system.</td>
<td>1. Draft Operations Plan.<br />
2. Begin development of operations procedures for ground system.</td>
<td colspan="2">1. Update Operations Plan and put under <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">CM</a>.<br />
2. Perform mission simulations and testing to verify Operations Plan,
utilizing mission elements including ground system operations
procedures.<br />
3. Complete operations procedures.</td>
<td colspan="2">1. Update post-launch changes to Operations Plan and
document operational constraints.</td>
<td>1. Perform disposal operations per Operations Plan.</td>
</tr>
<tr class="even">
<td><strong>Verification:</strong></td>
<td>1. Verify at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">MCR</a>.</td>
<td colspan="2">1. Verify through project team concurrence and at MRR
and <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">MDR</a>.</td>
<td>1. Verify through peer review and at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">PDR</a>.</td>
<td>1. Verify through peer review and at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">CDR</a>.</td>
<td colspan="2">1. Verify at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">MOR</a>, <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">FOR</a>, <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">LRR</a>, and <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">PSR</a>, and <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">ORR</a>.</td>
<td colspan="2">N/A</td>
<td>1. Verify at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">DR</a>.</td>
</tr>
<tr class="odd">
<td colspan="3"><p><strong>Revision Status:</strong></p>
<p>Baseline</p></td>
<td colspan="6"><p><strong>Owner:</strong></p>
<p>Mission Engineering and Systems Analysis Division (590)</p></td>
<td colspan="2"><p><strong>Reference:</strong></p>
<p>GPR 7120.5A</p></td>
</tr>
</tbody>
</table>

<table>
<colgroup>
<col style="width: 10%" />
<col style="width: 12%" />
<col style="width: 8%" />
<col style="width: 4%" />
<col style="width: 12%" />
<col style="width: 12%" />
<col style="width: 2%" />
<col style="width: 10%" />
<col style="width: 5%" />
<col style="width: 7%" />
<col style="width: 12%" />
</colgroup>
<tbody>
<tr class="odd">
<td><strong>1.03</strong></td>
<td colspan="6"><strong>Verification of Mission
Requirements</strong></td>
<td colspan="4"><strong>Systems Engineering</strong></td>
</tr>
<tr class="even">
<td><strong>Principle:</strong></td>
<td colspan="10">A process that ensures all mission requirements are
verified shall be developed and implemented.</td>
</tr>
<tr class="odd">
<td><strong>Rationale:</strong></td>
<td colspan="10"><a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">Mission
success</a> requires that mission functions can be achieved and that
system designs are implemented correctly.</td>
</tr>
<tr class="even">
<td><strong>Phase:</strong></td>
<td colspan="10"><strong>&lt;A A B C D E F</strong></td>
</tr>
<tr class="odd">
<td><strong>Activities:</strong></td>
<td>1. Develop a verification matrix that identifies a verification
method for all system functions that are critical to <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">Mission
success</a>.</td>
<td colspan="2">1. Update draft verification matrix.</td>
<td>1. Draft a verification plan that identifies items and interfaces as
well as functions to be verified, the verification method, and the
method of approving results as well as necessary equipment, tools and
facilities.</td>
<td>1. Update verification plan to include verification method for all
requirements and mission-critical functions.<br />
2. Draft a Comprehensive Performance Test Plan.<br />
3. Put all plans under <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">CM</a>.</td>
<td colspan="2">1. Prepare verification plans for tests, simulations or
inspections.<br />
2. Perform verifications; analyze and document results.</td>
<td colspan="2">N/A</td>
<td>N/A</td>
</tr>
<tr class="even">
<td><strong>Verification:</strong></td>
<td>1. Verify at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">MCR</a>.</td>
<td colspan="2">1. Verify at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">MDR</a>.</td>
<td>1. Verify at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">SDR</a> and <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">PDR</a>.</td>
<td>1. Verify at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">CDR</a>.</td>
<td colspan="2">1. Verify at subsystem peer review, <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">PER</a>, <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">PSR</a>, <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">LRR</a>, and
MRR.</td>
<td colspan="2">N/A</td>
<td>N/A</td>
</tr>
<tr class="odd">
<td colspan="3"><p><strong>Revision Status:</strong></p>
<p>Baseline; Updated: Rev D</p></td>
<td colspan="6"><p><strong>Owner:</strong></p>
<p>Mission Engineering and Systems Analysis Division (590)</p></td>
<td colspan="2"><p><strong>Reference:</strong></p>
<p>GPR 7120.5A</p></td>
</tr>
</tbody>
</table>

<table>
<colgroup>
<col style="width: 10%" />
<col style="width: 12%" />
<col style="width: 8%" />
<col style="width: 4%" />
<col style="width: 12%" />
<col style="width: 12%" />
<col style="width: 2%" />
<col style="width: 10%" />
<col style="width: 5%" />
<col style="width: 7%" />
<col style="width: 12%" />
</colgroup>
<tbody>
<tr class="odd">
<td><strong>1.04</strong></td>
<td colspan="6"><strong>System Modes</strong></td>
<td colspan="4"><strong>Systems Engineering</strong></td>
</tr>
<tr class="even">
<td><strong>Principle:</strong></td>
<td colspan="10"><a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">System</a> and
sub-system (e.g., <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">ACS</a>, <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">FSW</a>, EPS,
etc.) modes and states shall be properly identified and verified.</td>
</tr>
<tr class="odd">
<td><strong>Rationale:</strong></td>
<td colspan="10">Proper function of all system and sub-system modes,
states, and transitions need to be verified for <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">Mission
success</a>. If not directly addressed, this verification can easily be
overlooked.</td>
</tr>
<tr class="even">
<td><strong>Phase:</strong></td>
<td colspan="10"><strong>&lt;A A B C D E F</strong></td>
</tr>
<tr class="odd">
<td><strong>Activities:</strong></td>
<td>1. Identify strawman system and sub-system modes and states.</td>
<td colspan="2">1. Produce preliminary diagram of system and sub-system
mode and state transitions.</td>
<td>1. Refine diagram of system and sub-system mode and state
transitions.<br />
2. Define tests and analyses that verify system and sub-system modes,
states, and mode transitions.<br />
3. Incorporate into verification plan.</td>
<td>1. Update diagram of system and sub-system mode and state
transitions.<br />
2. Put document under configuration management control by <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">CDR</a>.<br />
3. Perform detailed design of modes, states, and transitions.<br />
4. Update verification of modes, states and transitions in verification
plan.</td>
<td colspan="2">1. Implement design of modes, states, and
transitions.<br />
2. Verify mode and state functionality and performance.<br />
3. Define on-orbit execution of operational modes, states, and
transitions.</td>
<td colspan="2">N/A</td>
<td>N/A</td>
</tr>
<tr class="even">
<td><strong>Verification:</strong></td>
<td>1. Verify at Peer review.</td>
<td colspan="2">1. Verify at end of Phase A: Peer Review, <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">SDR</a> or <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">SRR</a>.</td>
<td>1. Verify at Peer review, <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">PDR</a>,
CR.</td>
<td>1. Verify at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">CDR</a>.</td>
<td colspan="2">1. Verify at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">PER</a>, <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">PSR</a>.</td>
<td colspan="2">N/A</td>
<td>N/A</td>
</tr>
<tr class="odd">
<td colspan="3"><p><strong>Revision Status:</strong></p>
<p>Revision B</p></td>
<td colspan="6"><p><strong>Owner:</strong></p>
<p>Mission Engineering and Systems Analysis Division (590)</p></td>
<td colspan="2"><strong>Reference:</strong></td>
</tr>
</tbody>
</table>

<table>
<colgroup>
<col style="width: 10%" />
<col style="width: 12%" />
<col style="width: 8%" />
<col style="width: 4%" />
<col style="width: 12%" />
<col style="width: 12%" />
<col style="width: 2%" />
<col style="width: 10%" />
<col style="width: 5%" />
<col style="width: 7%" />
<col style="width: 12%" />
</colgroup>
<tbody>
<tr class="odd">
<td><strong>1.05</strong></td>
<td colspan="6"><strong>Single Point Failures</strong></td>
<td colspan="4"><strong>Systems Engineering</strong></td>
</tr>
<tr class="even">
<td><strong>Principle:</strong></td>
<td colspan="10">Single point failures that inhibit the ability to fully
meet minimum <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">Mission
success</a> requirements shall be identified, and the risk associated
with each shall be characterized, managed, and tracked.</td>
</tr>
<tr class="odd">
<td><strong>Rationale:</strong></td>
<td colspan="10">Robust design approaches make the elimination of single
point failures desirable. From a risk management perspective, it is
recognized that the acceptance of some single point failures may be
prudent. In these cases, it is essential to understand the attendant
risks and receive approval from senior management.</td>
</tr>
<tr class="even">
<td><strong>Phase:</strong></td>
<td colspan="10"><strong>&lt;A A B C D E F</strong></td>
</tr>
<tr class="odd">
<td><strong>Activities:</strong></td>
<td>1. Identify all requirements necessary for minimum <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">Mission
success</a>.<br />
2. Determine if a breech of any of these requirements will cause the
minimum mission to fail.</td>
<td colspan="2">1. Identify failures that would cause the minimum
mission to fail and develop a design strategy to avoid single point
failures.</td>
<td>1. Identify failures for all hardware and software that performs
mission-critical functions.<br />
2. Develop a design to avoid single point failures.</td>
<td>1. Design mission-critical elements to avoid single point
failures.</td>
<td colspan="2">1. Verify that there are no single string failures in
mission elements that are necessary for minimum <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">Mission
success</a>.</td>
<td colspan="2">N/A</td>
<td>N/A</td>
</tr>
<tr class="even">
<td><strong>Verification:</strong></td>
<td>1. Verify at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">MCR</a>.</td>
<td colspan="2">1. Verify at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">MDR</a>.</td>
<td>1. Verify at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">PDR</a>.</td>
<td>1. Verify at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">CDR</a>.</td>
<td colspan="2">1. Verify at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">PER</a> and <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">PSR</a>.</td>
<td colspan="2">N/A</td>
<td>N/A</td>
</tr>
<tr class="odd">
<td colspan="3"><p><strong>Revision Status:</strong></p>
<p>Baseline</p></td>
<td colspan="6"><p><strong>Owner:</strong></p>
<p>Mission Engineering and Systems Analysis Division (590)</p></td>
<td colspan="2"><strong>Reference:</strong></td>
</tr>
</tbody>
</table>

<table>
<colgroup>
<col style="width: 10%" />
<col style="width: 12%" />
<col style="width: 8%" />
<col style="width: 4%" />
<col style="width: 12%" />
<col style="width: 12%" />
<col style="width: 2%" />
<col style="width: 10%" />
<col style="width: 5%" />
<col style="width: 7%" />
<col style="width: 12%" />
</colgroup>
<tbody>
<tr class="odd">
<td><strong>1.06</strong></td>
<td colspan="6"><strong>Resource Margins</strong></td>
<td colspan="4"><strong>Systems Engineering</strong></td>
</tr>
<tr class="even">
<td><strong>Principle:</strong></td>
<td colspan="10">Resource margins shall be met in accordance with <a
href="javascript:openPictureWindow(&#39;getimage.php?i_id=1&#39;, 632, 360);">Table
1.06-1</a>.</td>
</tr>
<tr class="odd">
<td><strong>Rationale:</strong></td>
<td colspan="10">Compliance with these margins improves performance on
cost and schedule as well as overall mission performance.<br />
NOTE: Flight software margin warnings are covered in Rule 3.07.</td>
</tr>
<tr class="even">
<td><strong>Phase:</strong></td>
<td colspan="10"><strong>&lt;A A B C D E F</strong></td>
</tr>
<tr class="odd">
<td><strong>Activities:</strong></td>
<td>1. Identify resource margins.<br />
2. Identify the percent of resource that was determined by estimation,
calculation or measurement.</td>
<td colspan="2">1.Update resource margins.<br />
2. Identify the percent of resource that was determined by estimation,
calculation or measurement.</td>
<td>1. Update resource margins.<br />
2. Identify the percent of resource that was determined by estimation,
calculation or measurement.</td>
<td>1. Update resource margins.<br />
2. Identify the percent of resource that was determined by estimation,
calculation or measurement.</td>
<td colspan="2">1. Update resource margins.</td>
<td colspan="2">N/A</td>
<td>N/A</td>
</tr>
<tr class="even">
<td><strong>Verification:</strong></td>
<td>1. Verify at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">MCR</a>.</td>
<td colspan="2">1. Verify at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">ICR</a> and <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">MDR</a>.</td>
<td>1. Verify at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">PDR</a> and
confirmation review.</td>
<td>1. Verify at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">CDR</a>.</td>
<td colspan="2">1. Verify at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">PER</a> and <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">PSR</a>.</td>
<td colspan="2">N/A</td>
<td>N/A</td>
</tr>
<tr class="odd">
<td colspan="3"><p><strong>Revision Status:</strong></p>
<p>Baseline; Updated: Rev C.2</p></td>
<td colspan="6"><p><strong>Owner:</strong></p>
<p>Mission Engineering and Systems Analysis Division (590)</p></td>
<td colspan="2"><p><strong>Reference:</strong></p>
<p>Guidelines for Margins (future)</p></td>
</tr>
</tbody>
</table>

+----------------------+----------+------+------+------+------+------+
| **Table 1.06-1       |          |      |      |      |      |      |
| Technical Resource   |          |      |      |      |      |      |
| Margins** All values |          |      |      |      |      |      |
| are assumed to be at |          |      |      |      |      |      |
| the end of the phase |          |      |      |      |      |      |
+----------------------+----------+------+------+------+------+------+
| **Resource**         | **P      | **P  | **P  | **P  | **P  | **P  |
|                      | re-Phase | hase | hase | hase | hase | hase |
|                      | A**      | A**  | B**  | C**  | D**  | E**  |
+----------------------+----------+------+------+------+------+------+
|                      |          |      |      |      |      |      |
+----------------------+----------+------+------+------+------+------+
| **Mass**             | [\>      | [\>  | [\>  | [\>  | 0    |      |
|                      | ]{.under | ]{.u | ]{.u | ]{.u |      |      |
|                      | line}30% | nder | nder | nder |      |      |
|                      |          | line | line | line |      |      |
|                      |          | }25% | }20% | }15% |      |      |
+----------------------+----------+------+------+------+------+------+
| **Power (wrt EOL     | [\>      | [\>  | [\>  | [\>  | [\>  |      |
| capacity)**          | ]{.under | ]{.u | ]{.u | ]{.u | ]{.u |      |
|                      | line}30% | nder | nder | nder | nder |      |
|                      |          | line | line | line | line |      |
|                      |          | }25% | }15% | }15% | }10% |      |
|                      |          |      |      |      | \*   |      |
+----------------------+----------+------+------+------+------+------+
| **Propellant**       | 3σ\*\*\* |      |      |      | 3σ   |      |
+----------------------+----------+------+------+------+------+------+
| **Telemetry and      | [\>      | [\>  | [\>  | [\>  | 0    |      |
| Command hardware     | ]{.under | ]{.u | ]{.u | ]{.u |      |      |
| channels\*\***       | line}25% | nder | nder | nder |      |      |
|                      |          | line | line | line |      |      |
|                      |          | }20% | }15% | }10% |      |      |
+----------------------+----------+------+------+------+------+------+
|                      |          |      |      |      |      |      |
+----------------------+----------+------+------+------+------+------+
| Margin (in percent)= |          |      |      |      |      |      |
| (Available           |          |      |      |      |      |      |
| Resource-Estimated   |          |      |      |      |      |      |
| Value of             |          |      |      |      |      |      |
| Resource)/Estimated  |          |      |      |      |      |      |
| Resource X 100       |          |      |      |      |      |      |
+----------------------+----------+------+------+------+------+------+
|                      |          |      |      |      |      |      |
+----------------------+----------+------+------+------+------+------+
| \*At launch there    |          |      |      |      |      |      |
| shall be 10%         |          |      |      |      |      |      |
| predicted power      |          |      |      |      |      |      |
| margin for mission   |          |      |      |      |      |      |
| critical, cruise and |          |      |      |      |      |      |
| safing operating     |          |      |      |      |      |      |
| modes as well as to  |          |      |      |      |      |      |
| accommodate          |          |      |      |      |      |      |
| in-flight            |          |      |      |      |      |      |
| operational          |          |      |      |      |      |      |
| uncertainties.       |          |      |      |      |      |      |
|                      |          |      |      |      |      |      |
| \*\* Telemetry and   |          |      |      |      |      |      |
| command hardware     |          |      |      |      |      |      |
| channels read data   |          |      |      |      |      |      |
| from hardware such   |          |      |      |      |      |      |
| as thermistors,      |          |      |      |      |      |      |
| heaters, switches,   |          |      |      |      |      |      |
| motors, etc.         |          |      |      |      |      |      |
|                      |          |      |      |      |      |      |
| \*\*\* The 3 sigma   |          |      |      |      |      |      |
| variation is due to  |          |      |      |      |      |      |
| the following: 1.    |          |      |      |      |      |      |
| Worst-case           |          |      |      |      |      |      |
| spacecraft mass      |          |      |      |      |      |      |
| properties 2.        |          |      |      |      |      |      |
| 3-sigma low launch   |          |      |      |      |      |      |
|                      |          |      |      |      |      |      |
| vehicle performance  |          |      |      |      |      |      |
| 3. 3-sigma low       |          |      |      |      |      |      |
| propulsion subsystem |          |      |      |      |      |      |
| performance          |          |      |      |      |      |      |
| (thruster            |          |      |      |      |      |      |
| pe                   |          |      |      |      |      |      |
| rformance/alignment, |          |      |      |      |      |      |
| propellant           |          |      |      |      |      |      |
| residuals) 4.        |          |      |      |      |      |      |
| 3-sigma flight       |          |      |      |      |      |      |
| dynamics errors and  |          |      |      |      |      |      |
| constraints 5.       |          |      |      |      |      |      |
| Thruster failure     |          |      |      |      |      |      |
| (applies only to     |          |      |      |      |      |      |
| s                    |          |      |      |      |      |      |
| ingle-fault-tolerant |          |      |      |      |      |      |
| systems)             |          |      |      |      |      |      |
+----------------------+----------+------+------+------+------+------+
|                      |          |      |      |      |      |      |
+----------------------+----------+------+------+------+------+------+

<table>
<colgroup>
<col style="width: 10%" />
<col style="width: 12%" />
<col style="width: 8%" />
<col style="width: 4%" />
<col style="width: 12%" />
<col style="width: 12%" />
<col style="width: 2%" />
<col style="width: 10%" />
<col style="width: 5%" />
<col style="width: 7%" />
<col style="width: 12%" />
</colgroup>
<tbody>
<tr class="odd">
<td><strong>1.07</strong></td>
<td colspan="6"><strong>End-to-End GN&amp;C Phasing</strong></td>
<td colspan="4"><strong>Systems Engineering</strong></td>
</tr>
<tr class="even">
<td><strong>Principle:</strong></td>
<td colspan="10">All <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">GN&amp;C</a>
sensors and actuators shall undergo end-to-end phasing/polarity testing
after spacecraft integration and shall have flight software mitigations
to correct errors efficiently.</td>
</tr>
<tr class="odd">
<td><strong>Rationale:</strong></td>
<td colspan="10">Many spacecraft have had serious on-orbit problems due
to inadequate verification of signal phasing or polarity.
Component-level and end-to-end phasing tests and flight software
mitigations can ensure correct operation.</td>
</tr>
<tr class="even">
<td><strong>Phase:</strong></td>
<td colspan="10"><strong>&lt;A A B C D E F</strong></td>
</tr>
<tr class="odd">
<td><strong>Activities:</strong></td>
<td>N/A</td>
<td colspan="2">N/A</td>
<td>1. Define interface requirements of sensors and actuators.<br />
2. Design flight software to include capability to fix polarity problems
via table upload.</td>
<td>1. Update ICDs to include polarity definition<br />
2. Review vendor unit-level phasing test plans.<br />
3. Write flight S/W to include capability to fix polarity problems via
table upload.<br />
4. Create unit-level &amp; end-to-end phasing test plan.</td>
<td colspan="2">1. Perform unit-level phasing tests.<br />
2. Test flight S/W for table upload functionality.<br />
3. Perform end to-end phasing test for all sensor-to-actuator
combinations.<br />
4. Develop &amp; test contingency flight ops procedures for fixing
phasing problems.</td>
<td colspan="2">N/A</td>
<td>N/A</td>
</tr>
<tr class="even">
<td><strong>Verification:</strong></td>
<td>N/A</td>
<td colspan="2">N/A</td>
<td>1. Verify through peer review and at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">PDR</a>.</td>
<td>1. Verify through peer review and at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">CDR</a>.</td>
<td colspan="2">1. Verify at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">PSR</a> and <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">LRR</a>.</td>
<td colspan="2">N/A</td>
<td>N/A</td>
</tr>
<tr class="odd">
<td colspan="3"><p><strong>Revision Status:</strong></p>
<p>Baseline</p></td>
<td colspan="6"><p><strong>Owner:</strong></p>
<p>Flight Dynamics Analysis Branch (595)</p></td>
<td colspan="2"><strong>Reference:</strong></td>
</tr>
</tbody>
</table>

<table>
<colgroup>
<col style="width: 10%" />
<col style="width: 12%" />
<col style="width: 8%" />
<col style="width: 4%" />
<col style="width: 12%" />
<col style="width: 12%" />
<col style="width: 2%" />
<col style="width: 10%" />
<col style="width: 5%" />
<col style="width: 7%" />
<col style="width: 12%" />
</colgroup>
<tbody>
<tr class="odd">
<td><strong>1.08</strong></td>
<td colspan="6"><strong>End-to-End Testing</strong></td>
<td colspan="4"><strong>Systems Engineering</strong></td>
</tr>
<tr class="even">
<td><strong>Principle:</strong></td>
<td colspan="10"><a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">System</a>
end-to-end testing shall be performed using actual hardware or
simulation, and shall apply from input to instrument(s), through the
spacecraft, transmitted to receiving antennas, and through the ground
system - reconciled against what is physically achievable before launch,
and consistent with associated mission risk.</td>
</tr>
<tr class="odd">
<td><strong>Rationale:</strong></td>
<td colspan="10">End-to-end testing is the best verification of the
system's functionality, and often cannot be fully achieved because of
difficulties in closing some of the links. Breaks from a continuous <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">End-to-end
test</a> are permitted in such cases, if they are consistent with the
associated risks of the mission classification.</td>
</tr>
<tr class="even">
<td><strong>Phase:</strong></td>
<td colspan="10"><strong>&lt;A A B C D E F</strong></td>
</tr>
<tr class="odd">
<td><strong>Activities:</strong></td>
<td>1. Identify end-to-end tests that represent system-level
functions.</td>
<td colspan="2">1.Review and update the list of end-to-end tests and
analyses identified in Pre-phase A.<br />
2. Define success criteria for verification and incorporate into
verification plan.<br />
3. Review and update verification plan and schedule<br />
4. Identify facilities required for end-to-end testing.</td>
<td>1. Review and update list of end-to end tests and analyses
identified in Phase A.<br />
2. Review and update verification plan and schedule.<br />
3. Identify test plans and facilities that need to be in place for
end-to-end testing.</td>
<td>1. Draft final verification plan.<br />
2. Sign off on plan, put under <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">CM</a> test
schedule.<br />
3. Identify and schedule sequence of analyses and testing for verifying
end-to-end flight performance.<br />
4. Quantify the fidelity of each verification step.</td>
<td colspan="2">1. Perform unit-level phasing tests.<br />
2. Test flight S/W for table upload functionality.<br />
3. Perform end to-end phasing test for all sensor-to-actuator
combinations.<br />
4. Develop &amp; test contingency flight ops procedures for fixing
phasing problems.</td>
<td colspan="2">N/A</td>
<td>N/A</td>
</tr>
<tr class="even">
<td><strong>Verification:</strong></td>
<td>1. Verify all elements of the operating observatory and ground
system at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">MCR</a>.</td>
<td colspan="2">1. Verify at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">MDR</a>.</td>
<td>1. Verify at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">SDR</a> or <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">SRR</a>, <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">PDR</a>.</td>
<td>1. Verify at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">CDR</a>.</td>
<td colspan="2">1. Verify at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">PSR</a> and <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">LRR</a>.</td>
<td colspan="2">N/A</td>
<td>N/A</td>
</tr>
<tr class="odd">
<td colspan="3"><p><strong>Revision Status:</strong></p>
<p>Revision B</p></td>
<td colspan="6"><p><strong>Owner:</strong></p>
<p>Mission Engineering and Systems Analysis Division (590)</p></td>
<td colspan="2"><p><strong>Reference:</strong></p>
<p>GEVS 2.8</p></td>
</tr>
</tbody>
</table>

<table>
<colgroup>
<col style="width: 10%" />
<col style="width: 12%" />
<col style="width: 8%" />
<col style="width: 4%" />
<col style="width: 12%" />
<col style="width: 12%" />
<col style="width: 2%" />
<col style="width: 10%" />
<col style="width: 5%" />
<col style="width: 7%" />
<col style="width: 12%" />
</colgroup>
<tbody>
<tr class="odd">
<td><strong>1.09</strong></td>
<td colspan="6"><strong>Test Like You Fly</strong></td>
<td colspan="4"><strong>Systems Integration &amp; Test</strong></td>
</tr>
<tr class="even">
<td><strong>Principle:</strong></td>
<td colspan="10">All GSFC missions shall follow a, "Test Like You Fly
(TLYF) - Fly Like You Test" approach, throughout all applicable
lifecycles.</td>
</tr>
<tr class="odd">
<td><strong>Rationale:</strong></td>
<td colspan="10">Testing of all critical mission-operation elements in
the same manner as they will be flown greatly reduces the risk of
encountering negative impacts upon <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">Mission
success</a>, from partial to full loss of mission capability.</td>
</tr>
<tr class="even">
<td><strong>Phase:</strong></td>
<td colspan="10"><strong>&lt;A A B C D E F</strong></td>
</tr>
<tr class="odd">
<td><strong>Activities:</strong></td>
<td></td>
<td colspan="2">1. Develop the preliminary test plan employing a <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">TLYF</a>
philosophy.</td>
<td>1. Develop final test plan, employing a <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">TLYF</a>
philosophy.</td>
<td>1. Develop test procedures employing a <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">TLYF</a>
philosophy.</td>
<td colspan="2">1. Perform testing per plan / procedures.</td>
<td colspan="2">N/A</td>
<td>N/A</td>
</tr>
<tr class="even">
<td><strong>Verification:</strong></td>
<td></td>
<td colspan="2">1. Verify at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">MDR</a>.</td>
<td>1. Verify at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">PDR</a>.</td>
<td>1. Verify at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">CDR</a>.</td>
<td colspan="2">1. Verify at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">PER</a>.</td>
<td colspan="2">N/A</td>
<td>N/A</td>
</tr>
<tr class="odd">
<td colspan="3"><p><strong>Revision Status:</strong></p>
<p>Revision C.1</p></td>
<td colspan="6"><p><strong>Owner:</strong></p>
<p>Rules &amp; Processes (171)</p></td>
<td colspan="2"><p><strong>Reference:</strong></p>
<p>TLYF.pdf</p></td>
</tr>
</tbody>
</table>

<table>
<colgroup>
<col style="width: 10%" />
<col style="width: 12%" />
<col style="width: 8%" />
<col style="width: 4%" />
<col style="width: 12%" />
<col style="width: 12%" />
<col style="width: 2%" />
<col style="width: 10%" />
<col style="width: 5%" />
<col style="width: 7%" />
<col style="width: 12%" />
</colgroup>
<tbody>
<tr class="odd">
<td><strong>1.10</strong></td>
<td colspan="6"><strong>Logistics and Spares</strong></td>
<td colspan="4"><strong>Systems Engineering; Electrical</strong></td>
</tr>
<tr class="even">
<td><strong>Principle:</strong></td>
<td colspan="10">All projects shall define a plan for required spare
units (including spare <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">EEE</a> parts)
that is compatible with available resources and acceptable risk.</td>
</tr>
<tr class="odd">
<td><strong>Rationale:</strong></td>
<td colspan="10">An inadequate spare parts program leads to part
shortages during the development phase and has a direct impact on
potential workarounds or retrofit plans.</td>
</tr>
<tr class="even">
<td><strong>Phase:</strong></td>
<td colspan="10"><strong>&lt;A A B C D E F</strong></td>
</tr>
<tr class="odd">
<td><strong>Activities:</strong></td>
<td>N/A</td>
<td colspan="2">1. Address spare parts program and acquisition strategy
for critical long lead items in concept study.<br />
2. Define preliminary parts plan.<br />
3. Identify parts list and ETUs required for life testing.<br />
4. Identify critical parts that require spares.</td>
<td>1. Identify parts acquisition plan for long lead parts.<br />
2. Update preliminary parts plan.<br />
3. Develop acquisition strategy for parts and ETUs for life testing and
critical parts that require spares.</td>
<td>1. Finalize parts plan.<br />
2. Implement acquisition strategy for parts and ETUs for life testing
and critical parts that require spares.<br />
3. Begin life testing where relevant.</td>
<td colspan="2">1. Track critical spare parts and prepare specific risk
mitigation plans(s) for lower quantity spares.</td>
<td colspan="2">N/A</td>
<td>N/A</td>
</tr>
<tr class="even">
<td><strong>Verification:</strong></td>
<td>N/A</td>
<td colspan="2">1. Verify at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">MDR</a>.</td>
<td>1. Verify at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">PDR</a>.</td>
<td>1. Verify at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">CDR</a>.</td>
<td colspan="2">Verify at MRR.</td>
<td colspan="2">N/A</td>
<td>N/A</td>
</tr>
<tr class="odd">
<td colspan="3"><p><strong>Revision Status:</strong></p>
<p>Baseline</p></td>
<td colspan="6"><p><strong>Owner:</strong></p>
<p>Mission Engineering and Systems Analysis Division (590)</p></td>
<td colspan="2"><strong>Reference:</strong></td>
</tr>
</tbody>
</table>

<table>
<colgroup>
<col style="width: 10%" />
<col style="width: 12%" />
<col style="width: 8%" />
<col style="width: 4%" />
<col style="width: 12%" />
<col style="width: 12%" />
<col style="width: 2%" />
<col style="width: 10%" />
<col style="width: 5%" />
<col style="width: 7%" />
<col style="width: 12%" />
</colgroup>
<tbody>
<tr class="odd">
<td><strong>1.11</strong></td>
<td colspan="6"><strong>Qualification of Heritage Flight
Hardware</strong></td>
<td colspan="4"><strong>Systems Engineering</strong></td>
</tr>
<tr class="even">
<td><strong>Principle:</strong></td>
<td colspan="10">All heritage flight hardware shall be fully qualified
and verified for use in its new application. This qualification shall
take into consideration necessary design modifications, changes to
expected environments, and differences in operational use.</td>
</tr>
<tr class="odd">
<td><strong>Rationale:</strong></td>
<td colspan="10">All hardware, whether heritage or not, needs to be
qualified for its expected environment and operational uses.</td>
</tr>
<tr class="even">
<td><strong>Phase:</strong></td>
<td colspan="10"><strong>&lt;A A B C D E F</strong></td>
</tr>
<tr class="odd">
<td><strong>Activities:</strong></td>
<td>1. Identify/list <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">heritage
hardware</a> to be used and make a cursory assessment of "use as is" or
delta-qual.</td>
<td colspan="2">1. Update hardware list and identify the qualification
requirements.<br />
2. Assess through the peer review process the ultimate applicability of
previously flown/heritage hardware designs.</td>
<td>1. Refine/finalize <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">heritage
hardware</a> list and the required qualification requirements.</td>
<td>1. Qualify <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">heritage
hardware</a> as part of overall qualification of mission hardware.</td>
<td colspan="2">1. Develop, test, and integrate the flight
articles.</td>
<td colspan="2">N/A</td>
<td>N/A</td>
</tr>
<tr class="even">
<td><strong>Verification:</strong></td>
<td>1. Review summary documentation at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">MCR</a>.</td>
<td colspan="2">1. Review summary documentation at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">MDR</a>.</td>
<td>1. Review summary documentation at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">PDR</a>.</td>
<td>1. Review summary documentation at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">CDR</a>.</td>
<td colspan="2">1. Review summary documentation at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">PER</a> and <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">PSR</a>.</td>
<td colspan="2">N/A</td>
<td>N/A</td>
</tr>
<tr class="odd">
<td colspan="3"><p><strong>Revision Status:</strong></p>
<p>Baseline; Updated: Rev D</p></td>
<td colspan="6"><p><strong>Owner:</strong></p>
<p>Mission Engineering and Systems Analysis Division (590)</p></td>
<td colspan="2"><strong>Reference:</strong></td>
</tr>
</tbody>
</table>

<table>
<colgroup>
<col style="width: 10%" />
<col style="width: 12%" />
<col style="width: 8%" />
<col style="width: 4%" />
<col style="width: 12%" />
<col style="width: 12%" />
<col style="width: 2%" />
<col style="width: 10%" />
<col style="width: 5%" />
<col style="width: 7%" />
<col style="width: 12%" />
</colgroup>
<tbody>
<tr class="odd">
<td><strong>1.12</strong></td>
<td colspan="6"><strong>Units of Measurement</strong></td>
<td colspan="4"><strong>Systems Engineering</strong></td>
</tr>
<tr class="even">
<td><strong>Principle:</strong></td>
<td colspan="10">All design elements shall be specified and designed to
ensure the consistent and compatible use of physical units of
measure.</td>
</tr>
<tr class="odd">
<td><strong>Rationale:</strong></td>
<td colspan="10">Critical functions can be misprepresented by errors in
unit conversions.</td>
</tr>
<tr class="even">
<td><strong>Phase:</strong></td>
<td colspan="10"><strong>&lt;A A B C D E F</strong></td>
</tr>
<tr class="odd">
<td><strong>Activities:</strong></td>
<td>1. Determine unit standards.</td>
<td colspan="2">1. Implement unit standards.</td>
<td>1. Implement unit standards and document as part of requirements
management process.<br />
2. All drawings, figures, presentations, and user interfaces shall
clearly include units.</td>
<td>1. Implement unit standards and document as part of requirements
management process.<br />
2. All drawings, figures, presentations, and user interfaces shall
clearly include units.</td>
<td colspan="2">N/A</td>
<td colspan="2">N/A</td>
<td>N/A</td>
</tr>
<tr class="even">
<td><strong>Verification:</strong></td>
<td>1. Verify at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">MCR</a>.</td>
<td colspan="2">1. Verify at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">MDR</a>.</td>
<td>1. Verify at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">PDR</a>.</td>
<td>1. Verify at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">CDR</a>.</td>
<td colspan="2">N/A</td>
<td colspan="2">N/A</td>
<td>N/A</td>
</tr>
<tr class="odd">
<td colspan="3"><p><strong>Revision Status:</strong></p>
<p>Baseline</p></td>
<td colspan="6"><p><strong>Owner:</strong></p>
<p>Mission Engineering and Systems Analysis Division (590)</p></td>
<td colspan="2"><p><strong>Reference:</strong></p>
<p>JPL D-176868 rev. 2: 4.11.1.3</p></td>
</tr>
</tbody>
</table>

<table>
<colgroup>
<col style="width: 10%" />
<col style="width: 12%" />
<col style="width: 8%" />
<col style="width: 4%" />
<col style="width: 12%" />
<col style="width: 12%" />
<col style="width: 2%" />
<col style="width: 10%" />
<col style="width: 5%" />
<col style="width: 7%" />
<col style="width: 12%" />
</colgroup>
<tbody>
<tr class="odd">
<td><strong>1.13</strong></td>
<td colspan="6"><strong>Performance Demonstration During Qualification
Testing</strong></td>
<td colspan="4"><strong>Systems Engineering</strong></td>
</tr>
<tr class="even">
<td><strong>Principle:</strong></td>
<td colspan="10">During qualification testing, hardware shall
demonstrate expected (i.e.: within-tolerance) performance over a range
of conditions that envelops the worst-case operating parameters
anticipated to occur during the planned operational mission. Testing at
all levels (system, sub-system, and component) shall have clearly
defined pass/fail criteria.</td>
</tr>
<tr class="odd">
<td><strong>Rationale:</strong></td>
<td colspan="10"><a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">Mission
success</a> requires demonstration of performance over a range of
worst-case operating conditions.</td>
</tr>
<tr class="even">
<td><strong>Phase:</strong></td>
<td colspan="10"><strong>&lt;A A B C D E F</strong></td>
</tr>
<tr class="odd">
<td><strong>Activities:</strong></td>
<td>N/A</td>
<td colspan="2">N/A</td>
<td>1. Identify worst-case operating parameters for performance
testing.<br />
2. Develop plans for qualification testing that demonstrates performance
under worst-case operating parameters.</td>
<td>1. Update plans for qualification testing that demonstrates
performance under worst-case operating parameters.<br />
2. Document plans and put under configuration control.</td>
<td colspan="2">1. Perform qualification testing that demonstrates
performance under worst-case operating parameters.</td>
<td colspan="2">N/A</td>
<td>N/A</td>
</tr>
<tr class="even">
<td><strong>Verification:</strong></td>
<td>N/A</td>
<td colspan="2">N/A</td>
<td>1. Verify at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">PDR</a>.</td>
<td>1. Verify at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">CDR</a>.</td>
<td colspan="2">1. Verify at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">PER</a>.</td>
<td colspan="2">N/A</td>
<td>N/A</td>
</tr>
<tr class="odd">
<td colspan="3"><p><strong>Revision Status:</strong></p>
<p>Baseline</p></td>
<td colspan="6"><p><strong>Owner:</strong></p>
<p>Mission Engineering and Systems Analysis Division (590)</p></td>
<td colspan="2"><strong>Reference:</strong></td>
</tr>
</tbody>
</table>

<table>
<colgroup>
<col style="width: 10%" />
<col style="width: 12%" />
<col style="width: 8%" />
<col style="width: 4%" />
<col style="width: 12%" />
<col style="width: 12%" />
<col style="width: 2%" />
<col style="width: 10%" />
<col style="width: 5%" />
<col style="width: 7%" />
<col style="width: 12%" />
</colgroup>
<tbody>
<tr class="odd">
<td><strong>1.14</strong></td>
<td colspan="6"><strong>Mission Critical Telemetry and Command
Capability</strong></td>
<td colspan="4"><strong>Systems Engineering</strong></td>
</tr>
<tr class="even">
<td><strong>Principle:</strong></td>
<td colspan="10">Continuous telemetry coverage shall be maintained
during all mission-critical events. <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">Mission-critical</a>
events shall be defined to include separation from the launch vehicle;
power-up of major components or subsystems; deployment of mechanisms
and/or mission-critical appendages; and all planned propulsive maneuvers
required to establish mission orbit and/or achieve safe attitude. After
separation from the launch vehicle, continuous command coverage shall be
maintained during all following mission-critical events.</td>
</tr>
<tr class="odd">
<td><strong>Rationale:</strong></td>
<td colspan="10">With continuous telemetry and command capability,
operators can prevent anomalous events from propagating to mission loss.
Also, flight data will be available for anomaly investigations.</td>
</tr>
<tr class="even">
<td><strong>Phase:</strong></td>
<td colspan="10"><strong>&lt;A A B C D E F</strong></td>
</tr>
<tr class="odd">
<td><strong>Activities:</strong></td>
<td>1. Identify anddocument potentialmission-critical events in concept
of operations.<br />
2. Identify and document in concept of operations all potential needs
for communications coverage, such as TDRSS or backup ground
stations.</td>
<td colspan="2">1. Update concept of operations.<br />
2. Identify requirements for critical event coverage in ground system
design.</td>
<td>1. Address and document coverage of mission critical events in draft
of Mission Operations Concept.<br />
2. Address critical event coverage in requirements for ground system
design.</td>
<td>1. In Operation Plan, identify telemetry and command coverage for
all mission-critical events.</td>
<td colspan="2">1. Update Operations Plan.<br />
2. Address telemetry and command coverage of critical events in
Operations Procedures.</td>
<td colspan="2">1. Perform critical events with telemetry and command
capability.</td>
<td>N/A</td>
</tr>
<tr class="even">
<td><strong>Verification:</strong></td>
<td>1. Verify at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">MCR</a>.</td>
<td colspan="2">1. Verify at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">MDR</a>.</td>
<td>1. Verify at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">PDR</a>.</td>
<td>1. Verify at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">CDR</a>.</td>
<td colspan="2">1. Verify at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">ORR</a>.</td>
<td colspan="2">1. Verify telemetry capability during mission
operations.</td>
<td>N/A</td>
</tr>
<tr class="odd">
<td colspan="3"><p><strong>Revision Status:</strong></p>
<p>Baseline; Updated: Rev A, B, C, C.1</p></td>
<td colspan="6"><p><strong>Owner:</strong></p>
<p>Guidance, Navigation and Control Systems Engineering (591)</p></td>
<td colspan="2"><strong>Reference:</strong></td>
</tr>
</tbody>
</table>

<table>
<colgroup>
<col style="width: 10%" />
<col style="width: 12%" />
<col style="width: 8%" />
<col style="width: 4%" />
<col style="width: 12%" />
<col style="width: 12%" />
<col style="width: 2%" />
<col style="width: 10%" />
<col style="width: 5%" />
<col style="width: 7%" />
<col style="width: 12%" />
</colgroup>
<tbody>
<tr class="odd">
<td><strong>1.15</strong></td>
<td colspan="6"><strong>GSE Use at Launch Site</strong></td>
<td colspan="4"><strong>Systems Engineering</strong></td>
</tr>
<tr class="even">
<td><strong>Principle:</strong></td>
<td colspan="10">All testing of operations of flight systems at the
launch site or in the field shall only use <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">GSE</a> and
test configurations that have been previously used with the flight
hardware.</td>
</tr>
<tr class="odd">
<td><strong>Rationale:</strong></td>
<td colspan="10">New testing configurations introduce unknown variables
that could possibly cause damage to flight or ground test hardware as
well as delays in schedule.</td>
</tr>
<tr class="even">
<td><strong>Phase:</strong></td>
<td colspan="10"><strong>&lt;A A B C D E F</strong></td>
</tr>
<tr class="odd">
<td><strong>Activities:</strong></td>
<td>N/A</td>
<td colspan="2">N/A</td>
<td>N/A</td>
<td>1. Identify tests and associated <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">GSE</a>
required in the field or at the launch site.<br />
2. Ensure that the <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">GSE</a>
required for these tests is used in <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">I&amp;T</a> and
is available for use in the field or at the launch site.</td>
<td colspan="2">1. Draft test plans for launch site verifications and
specify all test configurations required.<br />
2. Ensure that these configurations are verified with the flight article
and in use before shipping.</td>
<td colspan="2">N/A</td>
<td>N/A</td>
</tr>
<tr class="even">
<td><strong>Verification:</strong></td>
<td>N/A</td>
<td colspan="2">N/A</td>
<td>N/A</td>
<td>1. Verify at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">CDR</a>.</td>
<td colspan="2">1. Verify at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">PER</a> and <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">PSR</a>.</td>
<td colspan="2">N/A</td>
<td>N/A</td>
</tr>
<tr class="odd">
<td colspan="3"><p><strong>Revision Status:</strong></p>
<p>Baseline</p></td>
<td colspan="6"><p><strong>Owner:</strong></p>
<p>Mission Engineering and Systems Analysis Division (590)</p></td>
<td colspan="2"><strong>Reference:</strong></td>
</tr>
</tbody>
</table>

<table>
<colgroup>
<col style="width: 10%" />
<col style="width: 12%" />
<col style="width: 8%" />
<col style="width: 4%" />
<col style="width: 12%" />
<col style="width: 12%" />
<col style="width: 2%" />
<col style="width: 10%" />
<col style="width: 5%" />
<col style="width: 7%" />
<col style="width: 12%" />
</colgroup>
<tbody>
<tr class="odd">
<td><strong>1.16</strong></td>
<td colspan="6"><strong>Ground Systems Configuration</strong></td>
<td colspan="4"><strong>Systems Engineering</strong></td>
</tr>
<tr class="even">
<td><strong>Principle:</strong></td>
<td colspan="10"><a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">Mission-critical</a>
software and hardware used for performing <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">I&amp;T</a> and
mission operations shall be under configuration control.</td>
</tr>
<tr class="odd">
<td><strong>Rationale:</strong></td>
<td colspan="10">Software configuration ensures that ground systems will
repeatedly perform as expected, which is critical for spacecraft
maneuvers, mission planning, spacecraft monitoring, and science data
processing.</td>
</tr>
<tr class="even">
<td><strong>Phase:</strong></td>
<td colspan="10"><strong>&lt;A A B C D E F</strong></td>
</tr>
<tr class="odd">
<td><strong>Activities:</strong></td>
<td>N/A</td>
<td colspan="2">N/A</td>
<td>1. Define all configuration items (<a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">CIs</a>) needed
for ground operations throughout the mission lifecycle, including
hardware, software, and documentation.</td>
<td>1. Define configuration control processes, <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">CCB</a>
members, and due dates for CIs.</td>
<td colspan="2">1. Provide <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">CIs</a> to <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">CCB</a> for
approval.<br />
2. Populate <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">CI</a>
database.<br />
3. Freeze mission-critical software by <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">FOR</a>.</td>
<td colspan="2">1. Ensure that only approved <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">CIs</a> are
used for critical spacecraft operations.<br />
2. Maintain <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">CCB</a>
processes for including new <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">CIs</a>.</td>
<td>1. Ensure that only approved <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">CIs</a> are
used for disposal.<br />
2. Maintain <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">CCB</a>
processes for including new <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">CIs</a>.</td>
</tr>
<tr class="even">
<td><strong>Verification:</strong></td>
<td>N/A</td>
<td colspan="2">N/A</td>
<td>1. Verify at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">PDR</a>.</td>
<td>1. Verify at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">CDR</a>.</td>
<td colspan="2">1. Verify at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">FOR</a> and <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">ORR</a>.</td>
<td colspan="2">1. Mission Director and Flight Operations Team verify
during operations.</td>
<td>1. Verify at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">DR</a>.</td>
</tr>
<tr class="odd">
<td colspan="3"><p><strong>Revision Status:</strong></p>
<p>Baseline; Updated: Rev D</p></td>
<td colspan="6"><p><strong>Owner:</strong></p>
<p>Flight Dynamics Analysis Branch (595)</p></td>
<td colspan="2"><strong>Reference:</strong></td>
</tr>
</tbody>
</table>

<table>
<colgroup>
<col style="width: 10%" />
<col style="width: 12%" />
<col style="width: 8%" />
<col style="width: 4%" />
<col style="width: 12%" />
<col style="width: 12%" />
<col style="width: 2%" />
<col style="width: 10%" />
<col style="width: 5%" />
<col style="width: 7%" />
<col style="width: 12%" />
</colgroup>
<tbody>
<tr class="odd">
<td><strong>1.17</strong></td>
<td colspan="6"><strong>Safe Hold Mode</strong></td>
<td colspan="4"><strong>Observatory Subsystems; GN&amp;C</strong></td>
</tr>
<tr class="even">
<td><strong>Principle:</strong></td>
<td colspan="10">All spacecraft shall have a power-positive control mode
(Safe Hold) to be entered in spacecraft emergencies. <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">Safe Hold
Mode</a> shall have the following characteristics: (1) its safety shall
not be compromised by the same <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">credible</a>
fault that led to Safe Hold activation; (2) it shall be as simple as
practical, employing the minimum hardware set required to maintain a
safe attitude; and (3) it shall require minimal ground intervention for
safe operation.</td>
</tr>
<tr class="odd">
<td><strong>Rationale:</strong></td>
<td colspan="10"><a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">Safe Hold
Mode</a> should behave very predictably while minimizing its demands on
the rest of the spacecraft. This facilitates the survival, diagnosis,
and recovery of the larger system. Complexity typically reduces the
robustness of Safe Hold, since it increases the risk of failure due to
existing spacecraft faults or unpredictable controller behavior.</td>
</tr>
<tr class="even">
<td><strong>Phase:</strong></td>
<td colspan="10"><strong>&lt;A A B C D E F</strong></td>
</tr>
<tr class="odd">
<td><strong>Activities:</strong></td>
<td>1. Ensure that requirements document and operations concept include
<a href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">Safe Hold
Mode</a>.</td>
<td colspan="2">1. Ensure that requirements document and operations
concept include <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">Safe Hold
Mode</a>.</td>
<td>1. Identify hardware &amp; software configuration for <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">Safe Hold
Mode</a>.<br />
2. In preliminary FMEA, demonstrate that no single <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">credible</a>
fault can both trigger Safe Hold entry and cause Safe Hold
failure.<br />
3. Analyze performance of preliminary Safe Hold algorithms.</td>
<td>1. Establish detailed Safe Hold design including entry/exit criteria
and <a href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">FDAC</a>
requirements for flight software.<br />
2. In final FMEA, demonstrate that no single <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">credible</a>
fault can both trigger Safe Hold entry and cause Safe Hold
failure.<br />
3. Analyze performance of Safe Hold algorithms.<br />
4. Via a rigorous risk assessment, decide whether or not to test Safe
Hold on-orbit.</td>
<td colspan="2">1. Implement <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">Safe Hold
Mode</a>.<br />
2. Verify proper mode transitions, redundancy, and phasing in ground
testing.<br />
3. Execute recovery procedures during mission simulations.<br />
4. Perform on-orbit testing if applicable.</td>
<td colspan="2">N/A</td>
<td>N/A</td>
</tr>
<tr class="even">
<td><strong>Verification:</strong></td>
<td>1. Verify through peer review and at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">MCR</a>.</td>
<td colspan="2">1. Verify through peer review and at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">MDR</a>.</td>
<td>1. Verify through peer review and at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">PDR</a>.</td>
<td>1. Verify through peer review and at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">CDR</a>.</td>
<td colspan="2">1. Verify at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">PER</a> and <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">FOR</a>.</td>
<td colspan="2">N/A</td>
<td>N/A</td>
</tr>
<tr class="odd">
<td colspan="3"><p><strong>Revision Status:</strong></p>
<p>Baseline; Updated: Rev A</p></td>
<td colspan="6"><p><strong>Owner:</strong></p>
<p><a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">GN&amp;C</a>
Systems Engineering Branch (591)</p></td>
<td colspan="2"><p><strong>Reference:</strong></p>
<p>Code 590 Policy</p></td>
</tr>
</tbody>
</table>

<table>
<colgroup>
<col style="width: 10%" />
<col style="width: 12%" />
<col style="width: 8%" />
<col style="width: 4%" />
<col style="width: 12%" />
<col style="width: 12%" />
<col style="width: 2%" />
<col style="width: 10%" />
<col style="width: 5%" />
<col style="width: 7%" />
<col style="width: 12%" />
</colgroup>
<tbody>
<tr class="odd">
<td><strong>1.18</strong></td>
<td colspan="6"><strong>Physically Co-Located Redundant
Elements</strong></td>
<td colspan="4"><strong>Systems Engineering</strong></td>
</tr>
<tr class="even">
<td><strong>Principle:</strong></td>
<td colspan="10">Failure in a physically co-located redundant element
shall not cause damage to, or interfere with the proper operation of,
other redundant elements (explosive decomposition, emission of
contaminants).</td>
</tr>
<tr class="odd">
<td><strong>Rationale:</strong></td>
<td colspan="10">While redundancy can greatly enhance system reliability
and confidence, it also incorporates added complexity to the overall
design. Design considerations must take into account the complexity that
is added by redundant components, in order to mitigate potential
negative effects upon the overall system reliability.</td>
</tr>
<tr class="even">
<td><strong>Phase:</strong></td>
<td colspan="10"><strong>&lt;A A B C D E F</strong></td>
</tr>
<tr class="odd">
<td><strong>Activities:</strong></td>
<td>1. Complete applicability assessment.</td>
<td colspan="2">1. Reassess and update applicability. 2. Complete
initial compliance assessment, based upon applicability.</td>
<td><p>1. Reassess compliance.</p>
<p>2. Ensure flow-down traceability to appropriate sub-system in draft
technical requirements and Design-To specifications.</p>
<p>3. Define verification approach.</p></td>
<td><p>1. Reassess compliance.</p>
<p>2. Ensure flow-down traceability to appropriate sub-system in
technical requirements and Design-To specification baselines.</p>
<p>3. Update verification approach.</p></td>
<td colspan="2"><p>1. Reassess compliance.</p>
<p>2. Perform verification activity.</p></td>
<td colspan="2">N/A</td>
<td>N/A</td>
</tr>
<tr class="even">
<td><strong>Verification:</strong></td>
<td>1. Verify at MCR.</td>
<td colspan="2">1. Verify at SRR, MDR, and PNAR.</td>
<td>1. Verify at PDR and NAR.</td>
<td>1. Verify at CDR and SIR.</td>
<td colspan="2">1. Verify at ORR, SMSR, and FRR.</td>
<td colspan="2">N/A</td>
<td>N/A</td>
</tr>
<tr class="odd">
<td colspan="3"><p><strong>Revision Status:</strong></p>
<p>Revision D</p></td>
<td colspan="6"><p><strong>Owner:</strong></p>
<p>Applied Engineering and Technology Directorate (500)</p></td>
<td colspan="2"><strong>Reference:</strong></td>
</tr>
</tbody>
</table>

<table>
<colgroup>
<col style="width: 10%" />
<col style="width: 12%" />
<col style="width: 8%" />
<col style="width: 4%" />
<col style="width: 12%" />
<col style="width: 12%" />
<col style="width: 2%" />
<col style="width: 10%" />
<col style="width: 5%" />
<col style="width: 7%" />
<col style="width: 12%" />
</colgroup>
<tbody>
<tr class="odd">
<td><strong>1.19</strong></td>
<td colspan="6"><strong>Initial Thruster Firing
Limitations</strong></td>
<td colspan="4"><strong>Observatory Subsystems; GN&amp;C</strong></td>
</tr>
<tr class="even">
<td><strong>Principle:</strong></td>
<td colspan="10">All initial thruster firings shall occur with real-time
telemetry and command capability. If alternate actuators (e.g. reaction
wheels) are present, the momentum induced by initial firings shall be
within the alternate actuators' capability to execute safe recovery of
the spacecraft.</td>
</tr>
<tr class="odd">
<td><strong>Rationale:</strong></td>
<td colspan="10">Polarity issues and thruster underperformance typically
occur early in the mission. Both conditions can result in a spacecraft
emergency due to excessive spacecraft spin rates.</td>
</tr>
<tr class="even">
<td><strong>Phase:</strong></td>
<td colspan="10"><strong>&lt;A A B C D E F</strong></td>
</tr>
<tr class="odd">
<td><strong>Activities:</strong></td>
<td>1. The Attitude Control <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">System</a>
(ACS) Concept shall ensure that thrusters will not be required during
launch vehicle separation for a 3-sigma distribution of cases. The
concept for operations shall ensure that, except in case of emergency,
all thrusters can be test-fired on-orbit prior to the first delta-v
maneuver.</td>
<td colspan="2">1. The Attitude Control <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">System</a>
shall design the thruster electronics, size and place the thrusters, and
size other actuators (e.g. reaction wheels) such that a failed thruster
can be shut down and the momentum absorbed before power or thermal
contstraints are violated. The activities specified in Pre-Phase A shall
be maintained.</td>
<td>1. Hardware (processors, power interfaces, data interfaces, etc.)
and software shall ensure that anomalous thruster firings will be shut
down quickly enough to allow recovery of the spacecraft to a power-safe
and thermal-safe condition.<br />
2. Develop design and operations concept consistent with the activities
established in Pre-Phase-A.</td>
<td>1. Estabish detailed recovery procedures. Finalize design and
operations concept consistent with the activities established in
Pre-Phase-A.</td>
<td colspan="2">1. Test failed thruster conditions with the greatest
possible fidelity. Verify transitions and polarity.<br />
2. Ensure that recovery procedures have been simulated with the flight
operations team.<br />
3. During on-orbit testing, thrusters shall be test fired to verify
polarity and performance prior to being used in a closed loop
control.</td>
<td colspan="2">1. Ground contact shall be maintained during thruster
firings.</td>
<td>1. Maintain activity per Phase E.<br />
2. Document any lessons learned.</td>
</tr>
<tr class="even">
<td><strong>Verification:</strong></td>
<td>1. <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">GN&amp;C</a>
and system engineering organizations shall verify at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">MCR</a>.</td>
<td colspan="2">1. <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">GN&amp;C</a>
and system engineering organizations shall verify at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">MDR</a>.</td>
<td>1. <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">GN&amp;C</a>
and system engineering organizations shall verify at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">PDR</a>.</td>
<td>1. <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">GN&amp;C</a>
and system engineering organizations shall verify at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">CDR</a>.</td>
<td colspan="2">1. <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">GN&amp;C</a>
and system engineering organizations shall verify at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">SAR</a>.<br />
2. Follow-up at Operational Readiness Review (ORR).</td>
<td colspan="2">1. Document lessons learned.</td>
<td>1. <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">GN&amp;C</a>
and system engineering organizations shall verify at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">DR</a>.<br />
2. <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">GN&amp;C</a>
and system engineering organizations document lessons learned.</td>
</tr>
<tr class="odd">
<td colspan="3"><p><strong>Revision Status:</strong></p>
<p>Baseline</p></td>
<td colspan="6"><p><strong>Owner:</strong></p>
<p>Flight Dynamics Analysis Branch (595)</p></td>
<td colspan="2"><strong>Reference:</strong></td>
</tr>
</tbody>
</table>

<table>
<colgroup>
<col style="width: 10%" />
<col style="width: 12%" />
<col style="width: 8%" />
<col style="width: 4%" />
<col style="width: 12%" />
<col style="width: 12%" />
<col style="width: 2%" />
<col style="width: 10%" />
<col style="width: 5%" />
<col style="width: 7%" />
<col style="width: 12%" />
</colgroup>
<tbody>
<tr class="odd">
<td><strong>1.20</strong></td>
<td colspan="6"><strong>Manifold Joints of Hazardous
Propellants</strong></td>
<td colspan="4"><strong>GN&amp;C; Propulsion</strong></td>
</tr>
<tr class="even">
<td><strong>Principle:</strong></td>
<td colspan="10">All joints in the propellant manifold between the
propellant supply tank and the first isolation valve shall be
NDE-verified welds.</td>
</tr>
<tr class="odd">
<td><strong>Rationale:</strong></td>
<td colspan="10">Failure of manifold joint poses critical or
catastrophic threat to personnel and/or facility.</td>
</tr>
<tr class="even">
<td><strong>Phase:</strong></td>
<td colspan="10"><strong>&lt;A A B C D E F</strong></td>
</tr>
<tr class="odd">
<td><strong>Activities:</strong></td>
<td>N/A</td>
<td colspan="2">N/A</td>
<td>1. Confirm system requirements for welded manifold joints.</td>
<td>1.Present weld &amp; technician certification plans and NDE
plans.</td>
<td colspan="2">1. Certify integrity of welds by NDE.</td>
<td colspan="2">N/A</td>
<td>N/A</td>
</tr>
<tr class="even">
<td><strong>Verification:</strong></td>
<td>N/A</td>
<td colspan="2">N/A</td>
<td>1. Verify at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">PDR</a>.</td>
<td>1. Verify at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">CDR</a>.</td>
<td colspan="2">1. Verify at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">PER</a>.</td>
<td colspan="2">N/A</td>
<td>N/A</td>
</tr>
<tr class="odd">
<td colspan="3"><p><strong>Revision Status:</strong></p>
<p>Baseline</p></td>
<td colspan="6"><p><strong>Owner:</strong></p>
<p>Propulsion Branch (597)</p></td>
<td colspan="2"><strong>Reference:</strong></td>
</tr>
</tbody>
</table>

<table>
<colgroup>
<col style="width: 10%" />
<col style="width: 12%" />
<col style="width: 8%" />
<col style="width: 4%" />
<col style="width: 12%" />
<col style="width: 12%" />
<col style="width: 2%" />
<col style="width: 10%" />
<col style="width: 5%" />
<col style="width: 7%" />
<col style="width: 12%" />
</colgroup>
<tbody>
<tr class="odd">
<td><strong>1.21</strong></td>
<td colspan="6"><strong>Overpressurization Protection in Liquid
Propulsion Systems</strong></td>
<td colspan="4"><strong>GN&amp;C; Propulsion</strong></td>
</tr>
<tr class="even">
<td><strong>Principle:</strong></td>
<td colspan="10">The propulsion system design and operations shall
preclude damage due to pressure surges ("water hammer"). (Note: See also
rule 1.28 "Unintended Propellant Vapor Ignition.")</td>
</tr>
<tr class="odd">
<td><strong>Rationale:</strong></td>
<td colspan="10">Pressure surges could result in damage to components or
manifolds, leading to failure of the propulsion system, damage to
facilities, and/or safety risk to personnel.</td>
</tr>
<tr class="even">
<td><strong>Phase:</strong></td>
<td colspan="10"><strong>&lt;A A B C D E F</strong></td>
</tr>
<tr class="odd">
<td><strong>Activities:</strong></td>
<td>N/A</td>
<td colspan="2">N/A</td>
<td>1. Perform pressure surge analysis, based on worst-case operating
conditions, to determine maximum surge pressure.<br />
2. If maximum surge pressure is greater than system proof pressure,
incorporate design features to reduce surge pressure below proof
pressure.</td>
<td>1. Demonstrate by test that maximum surge pressure is less than
system proof pressure.<br />
2. Demonstrate by test that surge-suppression features (if applicable)
do not lead to violation of flowrate/pressure drop requirements.<br />
3. Demonstrate by analysis that flight <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">SW</a> and/or
on-orbit procedures will prevent operation of propulsion system beyond
conditions assumed in pressure surge analyses and tests.</td>
<td colspan="2">N/A</td>
<td colspan="2">N/A</td>
<td>N/A</td>
</tr>
<tr class="even">
<td><strong>Verification:</strong></td>
<td>N/A</td>
<td colspan="2">N/A</td>
<td>1. Verify at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">PDR</a>.</td>
<td>1. Verify at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">CDR</a>.</td>
<td colspan="2">N/A</td>
<td colspan="2">N/A</td>
<td>N/A</td>
</tr>
<tr class="odd">
<td colspan="3"><p><strong>Revision Status:</strong></p>
<p>Baseline</p></td>
<td colspan="6"><p><strong>Owner:</strong></p>
<p>Propulsion Branch (597)</p></td>
<td colspan="2"><strong>Reference:</strong></td>
</tr>
</tbody>
</table>

<table>
<colgroup>
<col style="width: 10%" />
<col style="width: 12%" />
<col style="width: 8%" />
<col style="width: 4%" />
<col style="width: 12%" />
<col style="width: 12%" />
<col style="width: 2%" />
<col style="width: 10%" />
<col style="width: 5%" />
<col style="width: 7%" />
<col style="width: 12%" />
</colgroup>
<tbody>
<tr class="odd">
<td><strong>1.22</strong></td>
<td colspan="6"><strong>Purging of Residual Test Fluids</strong></td>
<td colspan="4"><strong>GN&amp;C; Propulsion</strong></td>
</tr>
<tr class="even">
<td><strong>Principle:</strong></td>
<td colspan="10">Propulsion system design and the assembly &amp; test
plans shall preclude entrapment of test fluids that are reactive with
wetted material or propellant.</td>
</tr>
<tr class="odd">
<td><strong>Rationale:</strong></td>
<td colspan="10">Residual test fluids can be reactive with the
propellant or corrosive to materials in the system leading to critical
or catastrophic failure.</td>
</tr>
<tr class="even">
<td><strong>Phase:</strong></td>
<td colspan="10"><strong>&lt;A A B C D E F</strong></td>
</tr>
<tr class="odd">
<td><strong>Activities:</strong></td>
<td>N/A</td>
<td colspan="2">N/A</td>
<td>1. If test fluids are used in the assembled system, present plans
for purging &amp; drying of system.</td>
<td>1. Demonstrate that the method for drying the wetted system has been
validated by test on an equivalent or similar system.</td>
<td colspan="2">1. Verify dryness of wetted system by test.</td>
<td colspan="2">N/A</td>
<td>N/A</td>
</tr>
<tr class="even">
<td><strong>Verification:</strong></td>
<td>N/A</td>
<td colspan="2">N/A</td>
<td>1. Verify at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">PDR</a>.</td>
<td>1. Verify at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">CDR</a>.</td>
<td colspan="2">1. Verify at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">PSR</a>.</td>
<td colspan="2">N/A</td>
<td>N/A</td>
</tr>
<tr class="odd">
<td colspan="3"><p><strong>Revision Status:</strong></p>
<p>Baseline; Updated: Rev A</p></td>
<td colspan="6"><p><strong>Owner:</strong></p>
<p>Propulsion Branch (597)</p></td>
<td colspan="2"><strong>Reference:</strong></td>
</tr>
</tbody>
</table>

<table>
<colgroup>
<col style="width: 10%" />
<col style="width: 12%" />
<col style="width: 8%" />
<col style="width: 4%" />
<col style="width: 12%" />
<col style="width: 12%" />
<col style="width: 2%" />
<col style="width: 10%" />
<col style="width: 5%" />
<col style="width: 7%" />
<col style="width: 12%" />
</colgroup>
<tbody>
<tr class="odd">
<td><strong>1.23</strong></td>
<td colspan="6"><strong>Spacecraft 'OFF' Command</strong></td>
<td colspan="4"><strong>Systems Engineering</strong></td>
</tr>
<tr class="even">
<td><strong>Principle:</strong></td>
<td colspan="10">In a redundant Spacecraft with no hardware failures, no
single command shall result in Spacecraft "OFF." In a single string
Spacecraft, or a redundant Spacecraft with a failure, no single command
shall result in Spacecraft "OFF."</td>
</tr>
<tr class="odd">
<td><strong>Rationale:</strong></td>
<td colspan="10">While redundancy can greatly enhance system reliability
and confidence, it also incorporates added complexity to the overall
design. Design considerations must take into account the complexity that
is added by redundant components, in order to mitigate potential
negative effects upon the overall system reliability.</td>
</tr>
<tr class="even">
<td><strong>Phase:</strong></td>
<td colspan="10"><strong>&lt;A A B C D E F</strong></td>
</tr>
<tr class="odd">
<td><strong>Activities:</strong></td>
<td>1. Complete applicability assessment.</td>
<td colspan="2"><p>1. Reassess and update applicability.</p>
<p>2. Complete initial compliance assessment, based upon
applicability.</p></td>
<td><p>1. Reassess compliance.</p>
<p>2. Ensure flow-down traceability to appropriate sub-system in draft
technical requirements and Design-To specifications.</p>
<p>3. Define verification approach.</p></td>
<td><p>1. Reassess compliance.</p>
<p>2. Ensure flow-down traceability to appropriate sub-system in
technical requirements and Design-To specification baselines.</p>
<p>3. Update verification approach.</p></td>
<td colspan="2"><p>1. Reassess compliance.</p>
<p>2. Perform verification activity.</p></td>
<td colspan="2">N/A</td>
<td>N/A</td>
</tr>
<tr class="even">
<td><strong>Verification:</strong></td>
<td>Verify at MCR.</td>
<td colspan="2">Verify at SRR, MDR, and PNAR.</td>
<td>Verify at PDR and NAR.</td>
<td>Verify at CDR and SIR.</td>
<td colspan="2">Verify at ORR, SMSR, and FRR.</td>
<td colspan="2">N/A</td>
<td>N/A</td>
</tr>
<tr class="odd">
<td colspan="3"><p><strong>Revision Status:</strong></p>
<p>Revision D</p></td>
<td colspan="6"><p><strong>Owner:</strong></p>
<p>Electrical Engineering Division (560)</p></td>
<td colspan="2"><strong>Reference:</strong></td>
</tr>
</tbody>
</table>

<table>
<colgroup>
<col style="width: 10%" />
<col style="width: 12%" />
<col style="width: 8%" />
<col style="width: 4%" />
<col style="width: 12%" />
<col style="width: 12%" />
<col style="width: 2%" />
<col style="width: 10%" />
<col style="width: 5%" />
<col style="width: 7%" />
<col style="width: 12%" />
</colgroup>
<tbody>
<tr class="odd">
<td><strong>1.24</strong></td>
<td colspan="6"><strong>Propulsion System Safety Electrical
Disconnect</strong></td>
<td colspan="4"><strong>GN&amp;C; Propulsion</strong></td>
</tr>
<tr class="even">
<td><strong>Principle:</strong></td>
<td colspan="10">An electrical disconnect "plug" or set of restrictive
commands shall be provided to preclude inadvertant operation of
components.</td>
</tr>
<tr class="odd">
<td><strong>Rationale:</strong></td>
<td colspan="10">Unplanned operation of propulsion system components
(e.g. 'dry' cycling of valve; heating of catalyst bed in air; firing of
thrusters after loading propellant) can result in injury to personnel or
damage to components.</td>
</tr>
<tr class="even">
<td><strong>Phase:</strong></td>
<td colspan="10"><strong>&lt;A A B C D E F</strong></td>
</tr>
<tr class="odd">
<td><strong>Activities:</strong></td>
<td>N/A</td>
<td colspan="2">N/A</td>
<td>1. Present design and/or operational plan that preclude unplanned
operation of propulsion system components.</td>
<td>1. Present detailed design of electrical disconnect and/or set of
restrictive commands to preclude unplanned operation of propulsion
system components.</td>
<td colspan="2">1. Demonstrate the effectiveness of the disconnect
and/or set of restrictive commands by test. N</td>
<td colspan="2">N/A</td>
<td>N/A</td>
</tr>
<tr class="even">
<td><strong>Verification:</strong></td>
<td>N/A</td>
<td colspan="2">N/A</td>
<td>1. Verify at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">PDR</a>.</td>
<td>1. Verify at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">CDR</a>.</td>
<td colspan="2">1. Verify at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">PER</a>.</td>
<td colspan="2">N/A</td>
<td>N/A</td>
</tr>
<tr class="odd">
<td colspan="3"><p><strong>Revision Status:</strong></p>
<p>Baseline</p></td>
<td colspan="6"><p><strong>Owner:</strong></p>
<p>Propulsion Branch (597)</p></td>
<td colspan="2"><strong>Reference:</strong></td>
</tr>
</tbody>
</table>

<table>
<colgroup>
<col style="width: 10%" />
<col style="width: 12%" />
<col style="width: 8%" />
<col style="width: 4%" />
<col style="width: 12%" />
<col style="width: 12%" />
<col style="width: 2%" />
<col style="width: 10%" />
<col style="width: 5%" />
<col style="width: 7%" />
<col style="width: 12%" />
</colgroup>
<tbody>
<tr class="odd">
<td><strong>1.25</strong></td>
<td colspan="6"><strong>Redundant Systems</strong></td>
<td colspan="4"><strong>Systems Engineering</strong></td>
</tr>
<tr class="even">
<td><strong>Principle:</strong></td>
<td colspan="10">When redundant systems or functions are implemented for
risk mitigation, the redundant components, or functional command paths,
shall be electrically, thermally, mechanically and functionally
independent, such that the failure of one component or command path does
not affect the other component or command path.</td>
</tr>
<tr class="odd">
<td><strong>Rationale:</strong></td>
<td colspan="10">While redundancy can greatly enhance system reliability
and confidence, it also incorporates added complexity to the overall
design. Design considerations must take into account the complexity that
is added by redundant components, in order to mitigate potential
negative effects upon the overall system reliability.</td>
</tr>
<tr class="even">
<td><strong>Phase:</strong></td>
<td colspan="10"><strong>&lt;A A B C D E F</strong></td>
</tr>
<tr class="odd">
<td><strong>Activities:</strong></td>
<td>1. Complete applicability assessment.</td>
<td colspan="2"><p>1. Reassess and update applicability.</p>
<p>2. Complete initial compliance assessment, based upon
applicability.</p></td>
<td><p>1. Reassess compliance.</p>
<p>2. Ensure flow-down traceability to appropriate sub-system in draft
technical requirements and Design-To specifications.</p>
<p>3. Define verification approach.</p></td>
<td><p>1. Reassess compliance.</p>
<p>2. Ensure flow-down traceability to appropriate sub-system in
technical requirements and Design-To specification baselines.</p>
<p>3. Update verification approach.</p></td>
<td colspan="2"><p>1. Reassess compliance.</p>
<p>2. Perform verification activity.</p></td>
<td colspan="2">N/A</td>
<td>N/A</td>
</tr>
<tr class="even">
<td><strong>Verification:</strong></td>
<td>1. Verify at MCR.</td>
<td colspan="2">1. Verify at SRR, MDR, and PNAR.</td>
<td>1. Verify at PDR and NAR.</td>
<td>1. Verify at CDR and SIR.</td>
<td colspan="2">1. Verify at ORR, SMSR, and FRR.</td>
<td colspan="2">N/A</td>
<td>N/A</td>
</tr>
<tr class="odd">
<td colspan="3"><p><strong>Revision Status:</strong></p>
<p>Revision D</p></td>
<td colspan="6"><p><strong>Owner:</strong></p>
<p>Office of System Safety and Mission Assurance (300)</p></td>
<td colspan="2"><strong>Reference:</strong></td>
</tr>
</tbody>
</table>

<table>
<colgroup>
<col style="width: 10%" />
<col style="width: 12%" />
<col style="width: 8%" />
<col style="width: 4%" />
<col style="width: 12%" />
<col style="width: 12%" />
<col style="width: 2%" />
<col style="width: 10%" />
<col style="width: 5%" />
<col style="width: 7%" />
<col style="width: 12%" />
</colgroup>
<tbody>
<tr class="odd">
<td><strong>1.26</strong></td>
<td colspan="6"><strong>Safety Inhibits &amp; Fault
Tolerance</strong></td>
<td colspan="4"><strong>Systems Engineering; System Safety</strong></td>
</tr>
<tr class="even">
<td><strong>Principle:</strong></td>
<td colspan="10">If a system failure may lead to a <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf"><strong>Catastrophic
Hazard</strong></a>, the system <strong>shall</strong> have three
independant, verifiable inhibits (dual fault tolerant).<br />
If a system failure may lead to a <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf"><strong>Critical
Hazard</strong></a>, the system <strong>shall</strong> have two
independant, verifiable, inhibits (single fault tolerant).<br />
Hazards which cannot be controlled by failure tolerance (e.g.,
structures, pressure vessels, etc.) are called "Design for Minimum Risk"
(DFMR) areas of design, and have separate, detailed safety requirements
that they must meet. Hazard controls related to these areas are
extremely critical and warrant careful attention to the details of
verification of compliance on the part of the developer.</td>
</tr>
<tr class="odd">
<td><strong>Rationale:</strong></td>
<td colspan="10">Adequate control of safety hazards is necessary in
order to develop safe hardware and operations. <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">Verification</a>
of independence of inhibits is necessary to preclude propagation of
failure in safety inhibits that can result in critical or catastrophic
threats to personnel, facility, and hardware.</td>
</tr>
<tr class="even">
<td><strong>Phase:</strong></td>
<td colspan="10"><strong>&lt;A A B C D E F</strong></td>
</tr>
<tr class="odd">
<td><strong>Activities:</strong></td>
<td>N/A</td>
<td colspan="2">N/A</td>
<td>1. Identify proposed design inhibits that preclude hazardous
condition and document in preliminary hazard analysis.</td>
<td>1. Demonstrate by analysis or component test that A) failure in
selected inhibit will not cause failure of the other inhibits, or B)
that no single event or software command can open multiple
inhibits.</td>
<td colspan="2">1. Demonstrate by analysis or component test that A)
failure in selected inhibit will not cause failure of the other
inhibits, or B) that no single event or software command can open
multiple inhibits.</td>
<td colspan="2">N/A</td>
<td>N/A</td>
</tr>
<tr class="even">
<td><strong>Verification:</strong></td>
<td>N/A</td>
<td colspan="2">N/A</td>
<td>1. Verify at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">PDR</a> and in
Preliminary MSPSP/Safety Data Package.</td>
<td>1. Verify at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">CDR</a> and in
Intermediate MSPSP/Safety Data Package.</td>
<td colspan="2">1. Verify in Final MSPSP/Safety Data Package.</td>
<td colspan="2">N/A</td>
<td>N/A</td>
</tr>
<tr class="odd">
<td colspan="3"><p><strong>Revision Status:</strong></p>
<p>Baseline; Updated: Rev C</p></td>
<td colspan="6"><p><strong>Owner:</strong></p>
<p><a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">System</a>
Reliability and <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">Safety</a>
Office (302)</p></td>
<td colspan="2"><strong>Reference:</strong></td>
</tr>
</tbody>
</table>

<table>
<colgroup>
<col style="width: 10%" />
<col style="width: 12%" />
<col style="width: 8%" />
<col style="width: 4%" />
<col style="width: 12%" />
<col style="width: 12%" />
<col style="width: 2%" />
<col style="width: 10%" />
<col style="width: 5%" />
<col style="width: 7%" />
<col style="width: 12%" />
</colgroup>
<tbody>
<tr class="odd">
<td><strong>1.27</strong></td>
<td colspan="6"><strong>Propulsion System Overtemp Fuse</strong></td>
<td colspan="4"><strong>GN&amp;C; Propulsion</strong></td>
</tr>
<tr class="even">
<td><strong>Principle:</strong></td>
<td colspan="10">Flight fuses for wetted propulsion system components
shall be selected such that overheating of propellant will not occur at
the maximum current limit rating of the flight fuse. (Note: See also
rule 2.06 "System Fusing Architecture.")</td>
</tr>
<tr class="odd">
<td><strong>Rationale:</strong></td>
<td colspan="10">Propulsion components such as pressure transducers
normally draw very low current, and therefore their fuses are usually
oversized. In such cases it may be possible for a malfunctioning
component to overheat significantly without exceeding the rating of the
fuse. Exceeding temperature limits of propellant can result in mission
failure or critical/catastrophic hazard to personnel and facility.</td>
</tr>
<tr class="even">
<td><strong>Phase:</strong></td>
<td colspan="10"><strong>&lt;A A B C D E F</strong></td>
</tr>
<tr class="odd">
<td><strong>Activities:</strong></td>
<td>N/A</td>
<td colspan="2">N/A</td>
<td>1. Present fusing plan for wetted propulsion system components.</td>
<td>1. Demonstrate by analysis that wetted components will not exceed
maximum allowable temperature of propellant at the maximum current limit
rating for the flight fuse.</td>
<td colspan="2">1. Verify by inspection of QA records that the correct
flight fuse has been installed.</td>
<td colspan="2">N/A</td>
<td>N/A</td>
</tr>
<tr class="even">
<td><strong>Verification:</strong></td>
<td>N/A</td>
<td colspan="2">N/A</td>
<td>1. Verify at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">PDR</a>.</td>
<td>1. Verify at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">CDR</a>.</td>
<td colspan="2">1. Verify at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">PER</a> or <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">PSR</a>.</td>
<td colspan="2">N/A</td>
<td>N/A</td>
</tr>
<tr class="odd">
<td colspan="3"><p><strong>Revision Status:</strong></p>
<p>Baseline</p></td>
<td colspan="6"><p><strong>Owner:</strong></p>
<p>Propulsion Branch (597)</p></td>
<td colspan="2"><strong>Reference:</strong></td>
</tr>
</tbody>
</table>

<table>
<colgroup>
<col style="width: 10%" />
<col style="width: 12%" />
<col style="width: 8%" />
<col style="width: 4%" />
<col style="width: 12%" />
<col style="width: 12%" />
<col style="width: 2%" />
<col style="width: 10%" />
<col style="width: 5%" />
<col style="width: 7%" />
<col style="width: 12%" />
</colgroup>
<tbody>
<tr class="odd">
<td><strong>1.28</strong></td>
<td colspan="6"><strong>Unintended Propellant Vapor
Ignition</strong></td>
<td colspan="4"><strong>GN&amp;C; Propulsion</strong></td>
</tr>
<tr class="even">
<td><strong>Principle:</strong></td>
<td colspan="10">Propulsion system design and operations shall preclude
ignition of propellants in the feed system.</td>
</tr>
<tr class="odd">
<td><strong>Rationale:</strong></td>
<td colspan="10">Ignition of propellant vapor can occur due to a variety
of conditions including (1) mixing of fuel and oxidizer in pressurant
manifolds via diffusion and condensation; (2) pyrotechnic valve
initiator products entering propellant manifolds; (3) adiabatic
compression of gas due to pressure surges, i.e. "water hammer" effects.
These conditions can cause hardware damage and/or mission failure.</td>
</tr>
<tr class="even">
<td><strong>Phase:</strong></td>
<td colspan="10"><strong>&lt;A A B C D E F</strong></td>
</tr>
<tr class="odd">
<td><strong>Activities:</strong></td>
<td>N/A</td>
<td colspan="2">N/A</td>
<td>1. Present design analysis, including pyrovalve firing sequence
and/or propellant line initial pressurization, supporting mitigation of
conditons for ignition of propellant vapors.<br />
2. For bipropellant systems, demonstrate by analysis that the design
provides adequate margin against diffusion and condensation of
propellant vapors in common manifolds.</td>
<td>1. Demonstrate by analysis or test that pyrovalve firing sequence
and/or propellant line initial pressurization plan will not promote
conditions for ignition of propellant vapor. 2. For bipropellant
systems, demonstrate by test that selected pressurant system components
exhibit vapor diffusion resistance per the Phase B analysis.</td>
<td colspan="2">N/A</td>
<td colspan="2">N/A</td>
<td>N/A</td>
</tr>
<tr class="even">
<td><strong>Verification:</strong></td>
<td>N/A</td>
<td colspan="2">N/A</td>
<td>1. Verify at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">PDR</a>.</td>
<td>1. Verify at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">CDR</a>.</td>
<td colspan="2"></td>
<td colspan="2">N/A</td>
<td>N/A</td>
</tr>
<tr class="odd">
<td colspan="3"><p><strong>Revision Status:</strong></p>
<p>Baseline</p></td>
<td colspan="6"><p><strong>Owner:</strong></p>
<p>Propulsion Branch (597)</p></td>
<td colspan="2"><strong>Reference:</strong></td>
</tr>
</tbody>
</table>

<table>
<colgroup>
<col style="width: 10%" />
<col style="width: 12%" />
<col style="width: 8%" />
<col style="width: 4%" />
<col style="width: 12%" />
<col style="width: 12%" />
<col style="width: 2%" />
<col style="width: 10%" />
<col style="width: 5%" />
<col style="width: 7%" />
<col style="width: 12%" />
</colgroup>
<tbody>
<tr class="odd">
<td><strong>1.29</strong></td>
<td colspan="6"><strong>Leakage of Hazardous Propellant</strong></td>
<td colspan="4"><strong>Safety, Propulsion</strong></td>
</tr>
<tr class="even">
<td><strong>Principle:</strong></td>
<td colspan="10">Propulsion systems shall be dual fault tolerant (3
independant inhibits) to external leakage of hazardous propellant, which
is a <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">Catastrophic
Hazard</a>. Components where fault tolerance is not <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">credible</a> or
practical (e.g., tanks, lines, etc.) shall use design for minimum risk
instead (see Gold Rule titled "<strong>Safety Inhibits &amp; Fault
Tolerance</strong>").</td>
</tr>
<tr class="odd">
<td><strong>Rationale:</strong></td>
<td colspan="10">Adequate control of propulsion safety hazards is
necessary in order to develop safe hardware and operations. The internal
volume between redundant inhibits (seals) shall be limited to the
minimal practical volume and designed to limit the external leakage in
the event of failures.</td>
</tr>
<tr class="even">
<td><strong>Phase:</strong></td>
<td colspan="10"><strong>&lt;A A B C D E F</strong></td>
</tr>
<tr class="odd">
<td><strong>Activities:</strong></td>
<td>N/A</td>
<td colspan="2">N/A</td>
<td>Present compliance with range safety requirements, including
required fault tolerance to hazardous events. Document in subsystem
design and initial MSPSP.</td>
<td>Provide details of implementation of fault tolerance requirements of
propulsion system. Document in subsystem design and Intermediate
MSPSP.</td>
<td colspan="2">Provide details of hazard control verifications
addressing fault tolerance of propulsion system. Document in subsystem
design and Final MSPSP.</td>
<td colspan="2">N/A</td>
<td>N/A</td>
</tr>
<tr class="even">
<td><strong>Verification:</strong></td>
<td>N/A</td>
<td colspan="2">N/A</td>
<td>Verify at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">PDR</a>.</td>
<td>Verify at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">CDR</a>.</td>
<td colspan="2">Verify at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">PSR</a>.</td>
<td colspan="2">N/A</td>
<td>N/A</td>
</tr>
<tr class="odd">
<td colspan="3"><p><strong>Revision Status:</strong></p>
<p>Revision C</p></td>
<td colspan="6"><p><strong>Owner:</strong></p>
<p>Propulsion Branch (597)</p></td>
<td colspan="2"><strong>Reference:</strong></td>
</tr>
</tbody>
</table>

<table>
<colgroup>
<col style="width: 10%" />
<col style="width: 12%" />
<col style="width: 8%" />
<col style="width: 4%" />
<col style="width: 12%" />
<col style="width: 12%" />
<col style="width: 2%" />
<col style="width: 10%" />
<col style="width: 5%" />
<col style="width: 7%" />
<col style="width: 12%" />
</colgroup>
<tbody>
<tr class="odd">
<td><strong>1.30</strong></td>
<td colspan="6"><strong>Controller Stability Margins</strong></td>
<td colspan="4"><strong>Observatory Subsystem; GNC</strong></td>
</tr>
<tr class="even">
<td><strong>Principle:</strong></td>
<td colspan="10">The Attitude Control <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">System</a>
(ACS) shall have stability margins of at least 6db for rigid body
stability with 30 degrees phase margin, and 12db of gain margin for
flexible modes.</td>
</tr>
<tr class="odd">
<td><strong>Rationale:</strong></td>
<td colspan="10">Proper gain and phase margins are required to maintain
stability for reasonable unforeseen changes and uncertainty in
spacecraft configuration.</td>
</tr>
<tr class="even">
<td><strong>Phase:</strong></td>
<td colspan="10"><strong>&lt;A A B C D E F</strong></td>
</tr>
<tr class="odd">
<td><strong>Activities:</strong></td>
<td>1. Identify in the Attitude Control <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">System</a>
(ACS) Concept if the gain and phase margin requirements will be
difficult to meet due to the spacecraft configuration.</td>
<td colspan="2">1. Update the <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">ACS</a> concept
and identify if the gain and phase margin requirements will be difficult
to meet due to the spacecraft configuration.</td>
<td>1. Design all control modes so that the rigid body stability margins
are at least 6 dB of gain margin and 30 degrees of phase margin.<br />
2. Ensure that flexible modes have at least 12 dB of gain margin.</td>
<td>1. Stability analyses should include all flexible mode effects,
sample data and delay effects (and other nonlinear effects such as fuel
slosh) incorporated with adequate evaluation of mode shape, damping and
frequency uncertainties.</td>
<td colspan="2">1. Perform verification test and present data.</td>
<td colspan="2">N/A</td>
<td>N/A</td>
</tr>
<tr class="even">
<td><strong>Verification:</strong></td>
<td>1. <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">GN&amp;C</a>
and system engineering organizations verify at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">MCR</a>.</td>
<td colspan="2">1. <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">GN&amp;C</a>
and system engineering organizations verify at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">MDR</a>.</td>
<td>1. <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">GN&amp;C</a>
and system engineering organizations verify at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">PDR</a>.</td>
<td>1. <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">GN&amp;C</a>
and system engineering organizations verify at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">CDR</a>.</td>
<td colspan="2">1. Verify at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">PSR</a>.</td>
<td colspan="2">N/A</td>
<td>N/A</td>
</tr>
<tr class="odd">
<td colspan="3"><p><strong>Revision Status:</strong></p>
<p>Baseline; Updated: Rev B</p></td>
<td colspan="6"><p><strong>Owner:</strong></p>
<p>Flight Dynamics Analysis Branch (595)</p></td>
<td colspan="2"><p><strong>Reference:</strong></p>
<p>ACS Handbook</p></td>
</tr>
</tbody>
</table>

<table>
<colgroup>
<col style="width: 10%" />
<col style="width: 12%" />
<col style="width: 8%" />
<col style="width: 4%" />
<col style="width: 12%" />
<col style="width: 12%" />
<col style="width: 2%" />
<col style="width: 10%" />
<col style="width: 5%" />
<col style="width: 7%" />
<col style="width: 12%" />
</colgroup>
<tbody>
<tr class="odd">
<td><strong>1.31</strong></td>
<td colspan="6"><strong>Actuator Sizing Margins</strong></td>
<td colspan="4"><strong>Observatory Subsystems; GN&amp;C</strong></td>
</tr>
<tr class="even">
<td><strong>Principle:</strong></td>
<td colspan="10">The Attitude Control <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">System</a>
(ACS) actuator sizing shall reflect specified allowances for mass
properties growth.</td>
</tr>
<tr class="odd">
<td><strong>Rationale:</strong></td>
<td colspan="10">Knowledge of spacecraft mass and inertia can be very
uncertain at early design stages, so actuator sizing should be done with
the appropriate amount of margin to ensure a viable design.</td>
</tr>
<tr class="even">
<td><strong>Phase:</strong></td>
<td colspan="10"><strong>&lt;A A B C D E F</strong></td>
</tr>
<tr class="odd">
<td><strong>Activities:</strong></td>
<td>N/A</td>
<td colspan="2">1. <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">ACS</a>
actuators (including propulsion) shall be sized for the current best
estimate of spacecraft mass properties with 100% design margin.</td>
<td>1. <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">ACS</a>
actuators (including propulsion) shall be sized for the current best
estimate of spacecraft mass properties with 50% design margin.</td>
<td>1. <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">ACS</a>
actuators (including propulsion) shall be sized for the current best
estimate of spacecraft mass properties with 25% design margin.</td>
<td colspan="2">N/A</td>
<td colspan="2">N/A</td>
<td>N/A</td>
</tr>
<tr class="even">
<td><strong>Verification:</strong></td>
<td>N/A</td>
<td colspan="2">1. At <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">MDR</a>, <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">GN&amp;C</a>
and system engineering organizations shall verify.</td>
<td>1. At <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">PDR</a>, <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">GN&amp;C</a>
and system engineering organizations shall verify.</td>
<td>1. At <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">CDR</a>, <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">GN&amp;C</a>
and system engineering organizations shall verify.</td>
<td colspan="2">N/A</td>
<td colspan="2">N/A</td>
<td>N/A</td>
</tr>
<tr class="odd">
<td colspan="3"><p><strong>Revision Status:</strong></p>
<p>Baseline</p></td>
<td colspan="6"><p><strong>Owner:</strong></p>
<p>Flight Dynamics Analysis Branch (595)</p></td>
<td colspan="2"><strong>Reference:</strong></td>
</tr>
</tbody>
</table>

<table>
<colgroup>
<col style="width: 10%" />
<col style="width: 12%" />
<col style="width: 8%" />
<col style="width: 4%" />
<col style="width: 12%" />
<col style="width: 12%" />
<col style="width: 2%" />
<col style="width: 10%" />
<col style="width: 5%" />
<col style="width: 7%" />
<col style="width: 12%" />
</colgroup>
<tbody>
<tr class="odd">
<td><strong>1.32</strong></td>
<td colspan="6"><strong>Thruster and Venting Impingement</strong></td>
<td colspan="4"><strong>Systems Engineering</strong></td>
</tr>
<tr class="even">
<td><strong>Principle:</strong></td>
<td colspan="10">Thruster or external venting plume impingment shall be
analyzed and demonstrated to meet mission requirements.</td>
</tr>
<tr class="odd">
<td><strong>Rationale:</strong></td>
<td colspan="10">Impingement is likely to contaminate critical surfaces
and degrade material properties. It can also create adverse and
unpredictable <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">S/C</a> torques
and unacceptable localized heating.</td>
</tr>
<tr class="even">
<td><strong>Phase:</strong></td>
<td colspan="10"><strong>&lt;A A B C D E F</strong></td>
</tr>
<tr class="odd">
<td><strong>Activities:</strong></td>
<td>N/A</td>
<td colspan="2">N/A</td>
<td>1. Develop analytical mass transport model.<br />
2. Update as design evolves.</td>
<td>1. Refine analysis based on updated designs.</td>
<td colspan="2">1. Refine analysis based on updated designs.<br />
2. Measure venting rates during T/V tests and verify analysis.</td>
<td colspan="2">N/A</td>
<td>N/A</td>
</tr>
<tr class="even">
<td><strong>Verification:</strong></td>
<td>N/A</td>
<td colspan="2">N/A</td>
<td>1. Verify at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">PDR</a>.</td>
<td>1. Verify at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">CDR</a>.</td>
<td colspan="2">1. Verify at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">PSR</a>.</td>
<td colspan="2">N/A</td>
<td>N/A</td>
</tr>
<tr class="odd">
<td colspan="3"><p><strong>Revision Status:</strong></p>
<p>Baseline</p></td>
<td colspan="6"><p><strong>Owner:</strong></p>
<p>Mechanical Engineering and Systems Analysis Division (590)</p></td>
<td colspan="2"><p><strong>Reference:</strong></p>
<p>JPL D-17868 rev. 2: 2.4.2.2.6</p></td>
</tr>
</tbody>
</table>

<table>
<colgroup>
<col style="width: 10%" />
<col style="width: 12%" />
<col style="width: 8%" />
<col style="width: 4%" />
<col style="width: 12%" />
<col style="width: 12%" />
<col style="width: 2%" />
<col style="width: 10%" />
<col style="width: 5%" />
<col style="width: 7%" />
<col style="width: 12%" />
</colgroup>
<tbody>
<tr class="odd">
<td><strong>1.33</strong></td>
<td colspan="6"><strong>Polarity Checks of Critical
Components</strong></td>
<td colspan="4"><strong>Observatory Subsystems</strong></td>
</tr>
<tr class="even">
<td><strong>Principle:</strong></td>
<td colspan="10">All hardware shall verified by test or inspection of
the proper polarity, orientation, and position of all components
(sensors, switches, and mechanisms) for which these parameters affects
performance.</td>
</tr>
<tr class="odd">
<td><strong>Rationale:</strong></td>
<td colspan="10">Each spacecraft and instrument contains many components
that can be reversed easily during installation. Unless close
inspections are performed, and proper installations are verified by
test, on-orbit failures can occur when these components are
activated.</td>
</tr>
<tr class="even">
<td><strong>Phase:</strong></td>
<td colspan="10"><strong>&lt;A A B C D E F</strong></td>
</tr>
<tr class="odd">
<td><strong>Activities:</strong></td>
<td>N/A</td>
<td colspan="2">1. Identify all polarity-dependent components in the
spacecraft design concept.<br />
2. Ensure that design concept provides capability for testing
functionality of polarity-dependent components at end-to-end mission
system level, in addition to subsystem level.</td>
<td>1. Identify all polarity-dependent components in the spacecraft
prelminary design.<br />
2. Ensure that preliminary design provides capability for testing
functionality of polarity-dependent components at end-to-end mission
system level, in addition to subsystem level.<br />
3. Develop test plan for polarity-dependent components.</td>
<td>1. Identify all polarity-dependent components in the spacecraft
detailed design.<br />
2. Ensure that detailed design provides capability for testing
functionality of polarity-dependent components at end-to-end mission
system level, in addition to subsystem level.<br />
3. Develop test procedures for polarity-dependent components.</td>
<td colspan="2">1. Execute polarity tests at subsystem and end-to-end
mission system levels.</td>
<td colspan="2">N/A</td>
<td>N/A</td>
</tr>
<tr class="even">
<td><strong>Verification:</strong></td>
<td>N/A</td>
<td colspan="2">1. Verify through peer review and at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">MDR</a>.</td>
<td>1. Verify through peer review and at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">PDR</a>.</td>
<td>1. Verify through peer review and at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">CDR</a>.</td>
<td colspan="2">1. Verify through peer review, at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">PER</a>, and at
<a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">PSR</a>.</td>
<td colspan="2">N/A</td>
<td>N/A</td>
</tr>
<tr class="odd">
<td colspan="3"><p><strong>Revision Status:</strong></p>
<p>Baseline</p></td>
<td colspan="6"><p><strong>Owner:</strong></p>
<p><a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">GN&amp;C</a>
Systems Engineering Branch (591)</p></td>
<td colspan="2"><strong>Reference:</strong></td>
</tr>
</tbody>
</table>

<table>
<colgroup>
<col style="width: 10%" />
<col style="width: 12%" />
<col style="width: 8%" />
<col style="width: 4%" />
<col style="width: 12%" />
<col style="width: 12%" />
<col style="width: 2%" />
<col style="width: 10%" />
<col style="width: 5%" />
<col style="width: 7%" />
<col style="width: 12%" />
</colgroup>
<tbody>
<tr class="odd">
<td><strong>1.34</strong></td>
<td colspan="6"><strong>Closeout Photo Documentation of Key
Assemblies</strong></td>
<td colspan="4"><strong>Systems Engineering</strong></td>
</tr>
<tr class="even">
<td><strong>Principle:</strong></td>
<td colspan="10">Projects shall produce closeout photographic
documentation of key assemblies during the manufacturing process and of
the final integrated configuration "as flown."</td>
</tr>
<tr class="odd">
<td><strong>Rationale:</strong></td>
<td colspan="10">Closeout photographic documentation provides an
essential record in the event of mishaps or anomalies.</td>
</tr>
<tr class="even">
<td><strong>Phase:</strong></td>
<td colspan="10"><strong>&lt;A A B C D E F</strong></td>
</tr>
<tr class="odd">
<td><strong>Activities:</strong></td>
<td>N/A</td>
<td colspan="2">1. Identify plan to capture closeout photographic
documentation of key assemblies.</td>
<td>1. Update plan to capture closeout photographic documentation of key
assemblies.</td>
<td>1. Implement plan to capture closeout photographic documentation of
key assemblies.</td>
<td colspan="2">1. Provide closeout photographic documentation of key
assemblies.</td>
<td colspan="2">N/A</td>
<td>N/A</td>
</tr>
<tr class="even">
<td><strong>Verification:</strong></td>
<td>N/A</td>
<td colspan="2">1. Verify at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">MDR</a>.</td>
<td>1. Verify at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">PDR</a>.</td>
<td>1. Verify at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">CDR</a>.</td>
<td colspan="2">1. Verify at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">PSR</a></td>
<td colspan="2">N/A</td>
<td>N/A</td>
</tr>
<tr class="odd">
<td colspan="3"><p><strong>Revision Status:</strong></p>
<p>Baseline</p></td>
<td colspan="6"><p><strong>Owner:</strong></p>
<p>Office of <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">Mission
success</a></p></td>
<td colspan="2"><strong>Reference:</strong></td>
</tr>
</tbody>
</table>

<table>
<colgroup>
<col style="width: 10%" />
<col style="width: 12%" />
<col style="width: 8%" />
<col style="width: 4%" />
<col style="width: 12%" />
<col style="width: 12%" />
<col style="width: 2%" />
<col style="width: 10%" />
<col style="width: 5%" />
<col style="width: 7%" />
<col style="width: 12%" />
</colgroup>
<tbody>
<tr class="odd">
<td><strong>1.35</strong></td>
<td colspan="6"><strong>Maturity of New Technologies</strong></td>
<td colspan="4"><strong>Systems Engineering; Instruments</strong></td>
</tr>
<tr class="even">
<td><strong>Principle:</strong></td>
<td colspan="10">All technologies shall achieve a <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">TRL</a> 6 by <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">PDR</a>. Not
applicable to technology demonstration opportunities.</td>
</tr>
<tr class="odd">
<td><strong>Rationale:</strong></td>
<td colspan="10">The use of new and unproven technologies requires a
thorough qualification program in order to reduce risk to an acceptable
level.</td>
</tr>
<tr class="even">
<td><strong>Phase:</strong></td>
<td colspan="10"><strong>&lt;A A B C D E F</strong></td>
</tr>
<tr class="odd">
<td><strong>Activities:</strong></td>
<td>1. Identify relevant technologies, readiness levels, develop overall
risk mitigation plan (including fall back to existing technologies), and
conduct peer review(s).</td>
<td colspan="2">1. Develop qualification plan for specific technologies,
including risk mitigation. Peer review plan.</td>
<td>1. Implement qualification plan and demonstrate that <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">TRL</a> 6 has
been achieved. Peer review qualification results.</td>
<td>N/A</td>
<td colspan="2">N/A</td>
<td colspan="2">N/A</td>
<td>N/A</td>
</tr>
<tr class="even">
<td><strong>Verification:</strong></td>
<td>1. Review summary documentation at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">MCR</a>.</td>
<td colspan="2">1. Review summary documentation at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">MDR</a>.</td>
<td>1. Review summary documentation at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">PDR</a>.</td>
<td>N/A</td>
<td colspan="2">N/A</td>
<td colspan="2">N/A</td>
<td>N/A</td>
</tr>
<tr class="odd">
<td colspan="3"><p><strong>Revision Status:</strong></p>
<p>Baseline; Updated: Rev B</p></td>
<td colspan="6"><p><strong>Owner:</strong></p>
<p>Applied Engineering and Technology Directorate (500)</p></td>
<td colspan="2"><strong>Reference:</strong></td>
</tr>
</tbody>
</table>

<table>
<colgroup>
<col style="width: 10%" />
<col style="width: 12%" />
<col style="width: 8%" />
<col style="width: 4%" />
<col style="width: 12%" />
<col style="width: 12%" />
<col style="width: 2%" />
<col style="width: 10%" />
<col style="width: 5%" />
<col style="width: 7%" />
<col style="width: 12%" />
</colgroup>
<tbody>
<tr class="odd">
<td><strong>1.36</strong></td>
<td colspan="6"><strong>Block-Redundant Component Failure</strong></td>
<td colspan="4"><strong>Systems Engineering</strong></td>
</tr>
<tr class="even">
<td><strong>Principle:</strong></td>
<td colspan="10">Failure in block-redundant components shall not damage
the redundant block nor prevent successful switching to the redundant
block (where the primary block has failed).</td>
</tr>
<tr class="odd">
<td><strong>Rationale:</strong></td>
<td colspan="10">Cascading of failures can result in system being
zero-fault tolerant and may lead to loss of mission.</td>
</tr>
<tr class="even">
<td><strong>Phase:</strong></td>
<td colspan="10"><strong>&lt;A A B C D E F</strong></td>
</tr>
<tr class="odd">
<td><strong>Activities:</strong></td>
<td>N/A</td>
<td colspan="2">N/A</td>
<td>1. Conduct preliminary failure modes and effects analysis (FMEA) to
demonstrate that failure of primary components will not prevent
successful switching to, and operation of, redundant components.</td>
<td>1. Conduct final failure modes and effects analysis (FMEA) to
demonstrate that failure of primary components will not prevent
successful switching to, and operation of, redundant components.</td>
<td colspan="2">N/A</td>
<td colspan="2">N/A</td>
<td>N/A</td>
</tr>
<tr class="even">
<td><strong>Verification:</strong></td>
<td>N/A</td>
<td colspan="2">N/A</td>
<td>1. Verify at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">PDR</a>.</td>
<td>1. Verify at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">CDR</a>.</td>
<td colspan="2">N/A</td>
<td colspan="2">N/A</td>
<td>N/A</td>
</tr>
<tr class="odd">
<td colspan="3"><p><strong>Revision Status:</strong></p>
<p>Revision B</p></td>
<td colspan="6"><p><strong>Owner:</strong></p>
<p>Guidance, Navigation and Control Systems Engineering (591)</p></td>
<td colspan="2"><strong>Reference:</strong></td>
</tr>
</tbody>
</table>

<table>
<colgroup>
<col style="width: 10%" />
<col style="width: 12%" />
<col style="width: 8%" />
<col style="width: 4%" />
<col style="width: 12%" />
<col style="width: 12%" />
<col style="width: 2%" />
<col style="width: 10%" />
<col style="width: 5%" />
<col style="width: 7%" />
<col style="width: 12%" />
</colgroup>
<tbody>
<tr class="odd">
<td><strong>1.37</strong></td>
<td colspan="6"><strong>Stowage Configuration</strong></td>
<td colspan="4"><strong>GN&amp;C</strong></td>
</tr>
<tr class="even">
<td><strong>Principle:</strong></td>
<td colspan="10">When a spacecraft is in its stowed (launch)
configuration, it shall not obscure visibility of any attitude sensors
required for acquisition, and it shall not block any antennas required
for command and telemetry.</td>
</tr>
<tr class="odd">
<td><strong>Rationale:</strong></td>
<td colspan="10">Establishment of spacecraft communications and
acquisition of safe attitude are the two highest-priority
post-separation activities, and should not be dependent on completion of
deployments.</td>
</tr>
<tr class="even">
<td><strong>Phase:</strong></td>
<td colspan="10"><strong>&lt;A A B C D E F</strong></td>
</tr>
<tr class="odd">
<td><strong>Activities:</strong></td>
<td>N/A</td>
<td colspan="2">1. Demonstrate by inspection that mechanical subsystem
concept allows for full visibility of sensors and telemetry &amp;
command antennas.</td>
<td>1. Demonstrate by field-of-view analysis that mechanical subsystem
preliminary design allows for full visibility of sensors and telemetry
&amp; command antennas.</td>
<td>1. Demonstrate by field-of-view analysis that mechanical subsystem
detailed design allows for full visibility of sensors and telemetry
&amp; command antennas.</td>
<td colspan="2">1. Ensure during <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">I&amp;T</a>
that mechanical subsystem detailed design allows for full visibility of
sensors and telemetry &amp; command antennas.</td>
<td colspan="2">N/A</td>
<td>N/A</td>
</tr>
<tr class="even">
<td><strong>Verification:</strong></td>
<td>N/A</td>
<td colspan="2">1. Verify at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">MDR</a>.</td>
<td>1. Verify at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">PDR</a>.</td>
<td>1. Verify at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">CDR</a>.</td>
<td colspan="2">1. Verify at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">PER</a>.</td>
<td colspan="2">N/A</td>
<td>N/A</td>
</tr>
<tr class="odd">
<td colspan="3"><p><strong>Revision Status:</strong></p>
<p>Revision B</p></td>
<td colspan="6"><p><strong>Owner:</strong></p>
<p>Guidance, Navigation and Control Systems Engineering (591)</p></td>
<td colspan="2"><strong>Reference:</strong></td>
</tr>
</tbody>
</table>

<table>
<colgroup>
<col style="width: 10%" />
<col style="width: 12%" />
<col style="width: 8%" />
<col style="width: 4%" />
<col style="width: 12%" />
<col style="width: 12%" />
<col style="width: 2%" />
<col style="width: 10%" />
<col style="width: 5%" />
<col style="width: 7%" />
<col style="width: 12%" />
</colgroup>
<tbody>
<tr class="odd">
<td><strong>1.38</strong></td>
<td colspan="6"><strong>Configuration Command Confirmation</strong></td>
<td colspan="4"><strong>Systems Engineering; CNDH</strong></td>
</tr>
<tr class="even">
<td><strong>Principle:</strong></td>
<td colspan="10">Every configuration command shall have a direct
telemetry confirmation and a secondary indirect confirmation.</td>
</tr>
<tr class="odd">
<td><strong>Rationale:</strong></td>
<td colspan="10">Undetected failure to properly configure spacecraft
could lead to premature or unsafe operations, resulting in mission
failure.</td>
</tr>
<tr class="even">
<td><strong>Phase:</strong></td>
<td colspan="10"><strong>&lt;A A B C D E F</strong></td>
</tr>
<tr class="odd">
<td><strong>Activities:</strong></td>
<td>N/A</td>
<td colspan="2">N/A</td>
<td>1. Establish telemetry parameters to ensure that at least two
methods can be used to verify success of each configuration
command.</td>
<td>1. Establish go/no-go criteria to proceed with any
post-configuration operations and include these in procedures for ground
testing and on-orbit tests.</td>
<td colspan="2">1. During all test operations, exercise all available
methods to verify success of configuration commands.</td>
<td colspan="2">1. During all flight operations, exercise all available
methods to verify success of configuration commands.</td>
<td>N/A</td>
</tr>
<tr class="even">
<td><strong>Verification:</strong></td>
<td>N/A</td>
<td colspan="2">N/A</td>
<td>1. Verify at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">PDR</a>.</td>
<td>1. Verify at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">CDR</a>.</td>
<td colspan="2">1. Verify at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">FOR</a> and <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">PSR</a></td>
<td colspan="2">1. Verify during mission operations.</td>
<td>N/A</td>
</tr>
<tr class="odd">
<td colspan="3"><p><strong>Revision Status:</strong></p>
<p>Revision B</p></td>
<td colspan="6"><p><strong>Owner:</strong></p>
<p>Guidance, Navigation and Control Systems Engineering (591)</p></td>
<td colspan="2"><strong>Reference:</strong></td>
</tr>
</tbody>
</table>

<table>
<colgroup>
<col style="width: 10%" />
<col style="width: 12%" />
<col style="width: 8%" />
<col style="width: 4%" />
<col style="width: 12%" />
<col style="width: 12%" />
<col style="width: 2%" />
<col style="width: 10%" />
<col style="width: 5%" />
<col style="width: 7%" />
<col style="width: 12%" />
</colgroup>
<tbody>
<tr class="odd">
<td><strong>2.01</strong></td>
<td colspan="6"><strong>Flight Electronic Hardware Operating
Time</strong></td>
<td colspan="4"><strong>Electrical</strong></td>
</tr>
<tr class="even">
<td><strong>Principle:</strong></td>
<td colspan="10">One thousand (1000) hours of operating/power-on time
shall be accumulated on all flight electronic hardware (including all
redundant hardware) prior to launch, of which at least 200 hours shall
be in vacuum. The last 350 hours of operating/power-on time shall be
failure-free.</td>
</tr>
<tr class="odd">
<td><strong>Rationale:</strong></td>
<td colspan="10">Accumulated power-on time that demonstrates
trouble-free parts performance helps reduce the risk of failures after
launch.</td>
</tr>
<tr class="even">
<td><strong>Phase:</strong></td>
<td colspan="10"><strong>&lt;A A B C D E F</strong></td>
</tr>
<tr class="odd">
<td><strong>Activities:</strong></td>
<td>N/A</td>
<td colspan="2">1. Draft test plan.</td>
<td>1. Approve test plan.</td>
<td>1. Update test plan.</td>
<td colspan="2">1. Conduct 1000 hours of testing of all flight hardware
and spares. The last 350 hours shall be trouble-free. At least 200 shall
be in vacuum.</td>
<td colspan="2">N/A</td>
<td>N/A</td>
</tr>
<tr class="even">
<td><strong>Verification:</strong></td>
<td>N/A</td>
<td colspan="2">1. Verify at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">MDR</a>.</td>
<td>1. Verify at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">PDR</a>.</td>
<td>1. Verify at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">CDR</a>.</td>
<td colspan="2">1. Verify at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">PSR</a> that
testing has been conducted.<br />
2. Verify at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">PER</a> that
the test plan is sufficient for completion of required hours.</td>
<td colspan="2">N/A</td>
<td>N/A</td>
</tr>
<tr class="odd">
<td colspan="3"><p><strong>Revision Status:</strong></p>
<p>Baseline; Updated: Rev A, B</p></td>
<td colspan="6"><p><strong>Owner:</strong></p>
<p>Office of Systems <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">Safety</a> and
Mission Assurance (300)</p></td>
<td colspan="2"><p><strong>Reference:</strong></p>
<p>GEVS 2.3.4</p></td>
</tr>
</tbody>
</table>

<table>
<colgroup>
<col style="width: 10%" />
<col style="width: 12%" />
<col style="width: 8%" />
<col style="width: 4%" />
<col style="width: 12%" />
<col style="width: 12%" />
<col style="width: 2%" />
<col style="width: 10%" />
<col style="width: 5%" />
<col style="width: 7%" />
<col style="width: 12%" />
</colgroup>
<tbody>
<tr class="odd">
<td><strong>2.02</strong></td>
<td colspan="6"><strong>EEE Parts Program for Flight
Missions</strong></td>
<td colspan="4"><strong>Electrical</strong></td>
</tr>
<tr class="even">
<td><strong>Principle:</strong></td>
<td colspan="10">A <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">EEE</a> parts
program shall be plannned for and implemented for all flight missions
for the purpose of part selection, de-rating, screening, and overall
qualifications.</td>
</tr>
<tr class="odd">
<td><strong>Rationale:</strong></td>
<td colspan="10">Lack of comprehensive parts program may lead to parts
shortages or design impacts due to unexpected long lead times or
qualification status of the parts.</td>
</tr>
<tr class="even">
<td><strong>Phase:</strong></td>
<td colspan="10"><strong>&lt;A A B C D E F</strong></td>
</tr>
<tr class="odd">
<td><strong>Activities:</strong></td>
<td>1. Address parts program and acquisition strategy for critical long
lead parts in concept study.</td>
<td colspan="2">1. Define preliminary parts plan.</td>
<td>1. Identify parts acquisition plan for long lead parts.</td>
<td>1. Prepare a detailed list of critical part(s) (including spares)
and qualification plan(s).</td>
<td colspan="2">1. Track critical parts and prepare specific risk
mitigation plan(s).</td>
<td colspan="2">N/A</td>
<td>N/A</td>
</tr>
<tr class="even">
<td><strong>Verification:</strong></td>
<td>1. Verify at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">MCR</a>.</td>
<td colspan="2">1. Verify at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">MDR</a>.</td>
<td>1. Verify at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">PDR</a>.</td>
<td>1. Verify at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">CDR</a>.</td>
<td colspan="2">1. Verify at MRR.</td>
<td colspan="2">N/A</td>
<td>N/A</td>
</tr>
<tr class="odd">
<td colspan="3"><p><strong>Revision Status:</strong></p>
<p>Baseline</p></td>
<td colspan="6"><p><strong>Owner:</strong></p>
<p>Electrical Engineering Division (560)</p></td>
<td colspan="2"><strong>Reference:</strong></td>
</tr>
</tbody>
</table>

<table>
<colgroup>
<col style="width: 10%" />
<col style="width: 12%" />
<col style="width: 8%" />
<col style="width: 4%" />
<col style="width: 12%" />
<col style="width: 12%" />
<col style="width: 2%" />
<col style="width: 10%" />
<col style="width: 5%" />
<col style="width: 7%" />
<col style="width: 12%" />
</colgroup>
<tbody>
<tr class="odd">
<td><strong>2.03</strong></td>
<td colspan="6"><strong>Radiation Hardness Assurance
Program</strong></td>
<td colspan="4"><strong>Electrical</strong></td>
</tr>
<tr class="even">
<td><strong>Principle:</strong></td>
<td colspan="10">A Radiation Hardness Assurance (RHA) Program shall be
planned for and implemented for all flight missions to verify component-
and system-level radiation hardness by <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">CDR</a>.</td>
</tr>
<tr class="odd">
<td><strong>Rationale:</strong></td>
<td colspan="10">Projects that ignore or underfund this discipline often
discover too late that instruments/spacecraft are susceptible to
radiation effects.</td>
</tr>
<tr class="even">
<td><strong>Phase:</strong></td>
<td colspan="10"><strong>&lt;A A B C D E F</strong></td>
</tr>
<tr class="odd">
<td><strong>Activities:</strong></td>
<td>1. Include a preliminary <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">RHA</a>
assessment in the concept study.</td>
<td colspan="2">1. Update <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">RHA</a>
assessment, and include resources for <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">RHA</a> program
support in proposal.</td>
<td>1. Complete radiation environment analysis and assess radiation
sensitivity of parts through test databases or by testing.</td>
<td>1. Implement radiation hardness requirements for part
selection.<br />
2. Identify mitigation plans for non-compliance.<br />
3. Complete parts acceptability categorization.<br />
4. Complete parts <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">RHA</a>
qualification.</td>
<td colspan="2">1. Implement mitigation plans.<br />
2. Complete radiation test reports.</td>
<td colspan="2">N/A</td>
<td>N/A</td>
</tr>
<tr class="even">
<td><strong>Verification:</strong></td>
<td>1. Verify at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">MCR</a>.</td>
<td colspan="2">1. Verify at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">MDR</a>.</td>
<td>1. Verify at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">PDR</a>.</td>
<td>1. Verify at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">CDR</a>.</td>
<td colspan="2">1. Verify through peer review prior to start of
manufacturing and at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">PER</a>.</td>
<td colspan="2">N/A</td>
<td>N/A</td>
</tr>
<tr class="odd">
<td colspan="3"><p><strong>Revision Status:</strong></p>
<p>Baseline</p></td>
<td colspan="6"><p><strong>Owner:</strong></p>
<p>Electrical Engineering Division (560)</p></td>
<td colspan="2"><strong>Reference:</strong></td>
</tr>
</tbody>
</table>

<table>
<colgroup>
<col style="width: 10%" />
<col style="width: 12%" />
<col style="width: 8%" />
<col style="width: 4%" />
<col style="width: 12%" />
<col style="width: 12%" />
<col style="width: 2%" />
<col style="width: 10%" />
<col style="width: 5%" />
<col style="width: 7%" />
<col style="width: 12%" />
</colgroup>
<tbody>
<tr class="odd">
<td><strong>2.04</strong></td>
<td colspan="6"><strong>Dedicated Hardware ETU and EGSE</strong></td>
<td colspan="4"><strong>Electrical; Systems Engineering</strong></td>
</tr>
<tr class="even">
<td><strong>Principle:</strong></td>
<td colspan="10">All new developments with components at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">TRL</a> 5 or
lower at Pre-Phase A shall have a dedicated hardware <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">ETU</a> &amp;
<a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">EGSE</a>.</td>
</tr>
<tr class="odd">
<td><strong>Rationale:</strong></td>
<td colspan="10">A hardware <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">ETU</a> &amp;
<a href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">EGSE</a>
helps reduce risk to mission performance and <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">Project
execution</a> by reducing scheduling conflicts and identifying potential
problems early in a mission's lifecycle.</td>
</tr>
<tr class="even">
<td><strong>Phase:</strong></td>
<td colspan="10"><strong>&lt;A A B C D E F</strong></td>
</tr>
<tr class="odd">
<td><strong>Activities:</strong></td>
<td>1. Identify items at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">TRL</a> levels
5 or lower and define plans for <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">ETU</a> and <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">EGSE</a>.</td>
<td colspan="2">1. Address needed resources for dedicated <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">ETU</a> and <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">EGSE</a>.</td>
<td>1. Begin implementation of <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">ETU</a> and <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">EGSE</a>.<br />
2. Develop preliminary development schedule.</td>
<td>1. Prepare detailed development schedule utilizing dedicated <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">ETU</a>.<br />
2. Build and test <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">ETU</a> and <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">EGSE</a>.</td>
<td colspan="2">N/A</td>
<td colspan="2">N/A</td>
<td>N/A</td>
</tr>
<tr class="even">
<td><strong>Verification:</strong></td>
<td>1. Verify at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">MCR</a>.</td>
<td colspan="2">1. Verify at MRR.</td>
<td>1. Verify at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">PDR</a>.</td>
<td>1. Verify at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">CDR</a>.</td>
<td colspan="2">N/A</td>
<td colspan="2">N/A</td>
<td>N/A</td>
</tr>
<tr class="odd">
<td colspan="3"><p><strong>Revision Status:</strong></p>
<p>Baseline</p></td>
<td colspan="6"><p><strong>Owner:</strong></p>
<p>Electrical Engineering Division (560)</p></td>
<td colspan="2"><strong>Reference:</strong></td>
</tr>
</tbody>
</table>

<table>
<colgroup>
<col style="width: 10%" />
<col style="width: 12%" />
<col style="width: 8%" />
<col style="width: 4%" />
<col style="width: 12%" />
<col style="width: 12%" />
<col style="width: 2%" />
<col style="width: 10%" />
<col style="width: 5%" />
<col style="width: 7%" />
<col style="width: 12%" />
</colgroup>
<tbody>
<tr class="odd">
<td><strong>2.05</strong></td>
<td colspan="6"><strong>System Grounding Architecture</strong></td>
<td colspan="4"><strong>Electrical</strong></td>
</tr>
<tr class="even">
<td><strong>Principle:</strong></td>
<td colspan="10">A system grounding concept shall be developed for all
missions.</td>
</tr>
<tr class="odd">
<td><strong>Rationale:</strong></td>
<td colspan="10">Poor system grounding design will lead to grounding
incompatibility between different systems during the integration phase,
with potential degradation of end-to-end functional performance,
especially for magnetic sensitive missions.</td>
</tr>
<tr class="even">
<td><strong>Phase:</strong></td>
<td colspan="10"><strong>&lt;A A B C D E F</strong></td>
</tr>
<tr class="odd">
<td><strong>Activities:</strong></td>
<td>1. Identify a preliminary grounding concept.</td>
<td colspan="2">1. Complete a preliminary grounding design and
communicate it to all hardware developers.</td>
<td>1. State grounding requirements in all Electrical ICDs for the
users.</td>
<td>1. Prepare a detailed <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">System</a>
Grounding Document.<br />
2. Implement the design.</td>
<td colspan="2">1. Oversee implementation of the design.<br />
2. Demonstrate safety, compatibility, and system performance.</td>
<td colspan="2">N/A</td>
<td>N/A</td>
</tr>
<tr class="even">
<td><strong>Verification:</strong></td>
<td>1. Verify at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">MCR</a>.</td>
<td colspan="2">1. Verify at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">MDR</a>.</td>
<td>1. Verify through peer review and at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">PDR</a>.</td>
<td>1. Verify through peer review and at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">CDR</a>.</td>
<td colspan="2">1. Verify through peer review prior to TRR and at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">PER</a>.</td>
<td colspan="2">N/A</td>
<td>N/A</td>
</tr>
<tr class="odd">
<td colspan="3"><p><strong>Revision Status:</strong></p>
<p>Baseline</p></td>
<td colspan="6"><p><strong>Owner:</strong></p>
<p>Electrical Engineering Division (560)</p></td>
<td colspan="2"><strong>Reference:</strong></td>
</tr>
</tbody>
</table>

<table>
<colgroup>
<col style="width: 10%" />
<col style="width: 12%" />
<col style="width: 8%" />
<col style="width: 4%" />
<col style="width: 12%" />
<col style="width: 12%" />
<col style="width: 2%" />
<col style="width: 10%" />
<col style="width: 5%" />
<col style="width: 7%" />
<col style="width: 12%" />
</colgroup>
<tbody>
<tr class="odd">
<td><strong>2.06</strong></td>
<td colspan="6"><strong>System Fusing Architecture</strong></td>
<td colspan="4"><strong>Electrical</strong></td>
</tr>
<tr class="even">
<td><strong>Principle:</strong></td>
<td colspan="10">A system fusing architecture shall be developed for all
missions, including the payloads. (See also 1.27 "Propulsion <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">System</a>
Overtemp Fuse.")</td>
</tr>
<tr class="odd">
<td><strong>Rationale:</strong></td>
<td colspan="10">Lack of a system fusing design may lead to fuse
incompatabilities between the power source and the payloads, which could
lead to the power source fuse being blown prior to the payloads. The
system fusing design should maximize the reliability of the system.</td>
</tr>
<tr class="even">
<td><strong>Phase:</strong></td>
<td colspan="10"><strong>&lt;A A B C D E F</strong></td>
</tr>
<tr class="odd">
<td><strong>Activities:</strong></td>
<td>N/A</td>
<td colspan="2">1. Indentify a preliminary system fusing architecture
for the mission and communicate with all hardware developers.</td>
<td>1. Develop system fusing requirements for the mission and and state
requirements in all Electrical ICDs for the users, including transient
requirements.</td>
<td>1. Prepare a detailed <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">System</a>
Fusing Document.</td>
<td colspan="2">1. Oversee correct implementation of design by all
users.</td>
<td colspan="2">N/A</td>
<td>N/A</td>
</tr>
<tr class="even">
<td><strong>Verification:</strong></td>
<td>N/A</td>
<td colspan="2">1. Verify through peer review and at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">MDR</a>.</td>
<td>1. Verify all system fusing requirments (including the payloads)
through peer review and at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">PDR</a>.</td>
<td>1. Verify user implementation at electrical systems peer peview and
at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">CDR</a>.</td>
<td colspan="2">1. Verify that design verification includes fusing
design prior to TRR.</td>
<td colspan="2">N/A</td>
<td>N/A</td>
</tr>
<tr class="odd">
<td colspan="3"><p><strong>Revision Status:</strong></p>
<p>Baseline</p></td>
<td colspan="6"><p><strong>Owner:</strong></p>
<p>Electrical Engineering Division (560)</p></td>
<td colspan="2"><strong>Reference:</strong></td>
</tr>
</tbody>
</table>

<table>
<colgroup>
<col style="width: 10%" />
<col style="width: 12%" />
<col style="width: 8%" />
<col style="width: 4%" />
<col style="width: 12%" />
<col style="width: 12%" />
<col style="width: 2%" />
<col style="width: 10%" />
<col style="width: 5%" />
<col style="width: 7%" />
<col style="width: 12%" />
</colgroup>
<tbody>
<tr class="odd">
<td><strong>2.07</strong></td>
<td colspan="6"><strong>End-to-End Test of Release Mechanism for Flight
Deployables</strong></td>
<td colspan="4"><strong>Electrical</strong></td>
</tr>
<tr class="even">
<td><strong>Principle:</strong></td>
<td colspan="10">A release mechanism test for the flight deployable
components shall be performed as an end-to-end system-level test under
worst-case conditions and a realistic timeline.</td>
</tr>
<tr class="odd">
<td><strong>Rationale:</strong></td>
<td colspan="10">Often when <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">EGSE</a> is
used for mechanism release during <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">I&amp;T</a>,
potential system design problems with the release mechanisms are not
detected until after the completion of the environmental program.
Redesigning late in the program has many technical implications and
significant cost/schedule impact.</td>
</tr>
<tr class="even">
<td><strong>Phase:</strong></td>
<td colspan="10"><strong>&lt;A A B C D E F</strong></td>
</tr>
<tr class="odd">
<td><strong>Activities:</strong></td>
<td>N/A</td>
<td colspan="2">1. Develop preliminary environmental test plan (with
reference to end-to-end aspect of the test program).</td>
<td>1. Develop final environmental test plan including the end-to-end
system level test and present at Peer Review.</td>
<td>1. Develop test procedures for the end-to-end system level test and
present at Peer Review.</td>
<td colspan="2">1. Present detailed test configuration at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">PER</a>.</td>
<td colspan="2">N/A</td>
<td>N/A</td>
</tr>
<tr class="even">
<td><strong>Verification:</strong></td>
<td>N/A</td>
<td colspan="2">1. Verify at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">MDR</a>.</td>
<td>1. Verify through peer review and at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">SDR</a> and <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">PDR</a>.</td>
<td>1. Verify at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">CDR</a>.</td>
<td colspan="2">1. Verify at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">PER</a> that
spacecraft circuits will be used during tests.</td>
<td colspan="2">N/A</td>
<td>N/A</td>
</tr>
<tr class="odd">
<td colspan="3"><p><strong>Revision Status:</strong></p>
<p>Baseline; Updated: Rev A</p></td>
<td colspan="6"><p><strong>Owner:</strong></p>
<p>Office of Systems <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">Safety</a> and
Mission Assurance (300)</p></td>
<td colspan="2"><p><strong>Reference:</strong></p>
<p>GEVS 2.6.2.4.b</p></td>
</tr>
</tbody>
</table>

<table>
<colgroup>
<col style="width: 10%" />
<col style="width: 12%" />
<col style="width: 8%" />
<col style="width: 4%" />
<col style="width: 12%" />
<col style="width: 12%" />
<col style="width: 2%" />
<col style="width: 10%" />
<col style="width: 5%" />
<col style="width: 7%" />
<col style="width: 12%" />
</colgroup>
<tbody>
<tr class="odd">
<td><strong>2.08</strong></td>
<td colspan="6"><strong>Secondary Circuit Failure</strong></td>
<td colspan="4"><strong>Electrical Engineering</strong></td>
</tr>
<tr class="even">
<td><strong>Principle:</strong></td>
<td colspan="10">Failure in a secondary circuit (telemetry, current
monitoring, etc.) shall not unacceptably degrade the primary
function.</td>
</tr>
<tr class="odd">
<td><strong>Rationale:</strong></td>
<td colspan="10">While redundancy can greatly enhance system reliability
and confidence, it also incorporates added complexity to the overall
design. Design considerations must take into account the complexity that
is added by redundant components, in order to mitigate potential
negative effects upon the overall system reliability.</td>
</tr>
<tr class="even">
<td><strong>Phase:</strong></td>
<td colspan="10"><strong>&lt;A A B C D E F</strong></td>
</tr>
<tr class="odd">
<td><strong>Activities:</strong></td>
<td>1. Complete applicability assessment.</td>
<td colspan="2"><p>1. Reassess and update applicability.</p>
<p>2. Complete initial compliance assessment, based upon
applicability.</p></td>
<td><p>1. Reassess compliance.</p>
<p>2. Ensure flow-down traceability to appropriate sub-system in draft
technical requirements and Design-To specifications.</p>
<p>3. Define verification approach.</p></td>
<td><p>1. Reassess compliance.</p>
<p>2. Ensure flow-down traceability to appropriate sub-system in
technical requirements and Design-To specification baselines.</p>
<p>3. Update verification approach.</p></td>
<td colspan="2"><p>1. Reassess compliance.</p>
<p>2. Perform verification activity.</p></td>
<td colspan="2">N/A</td>
<td>N/A</td>
</tr>
<tr class="even">
<td><strong>Verification:</strong></td>
<td>1. Verify at MCR.</td>
<td colspan="2">1. Verify at SRR, MDR, and PNAR.</td>
<td>1. Verify at PDR and NAR.</td>
<td>1. Verify at CDR and SIR.</td>
<td colspan="2">1. Verify at ORR, SMSR, and FRR.</td>
<td colspan="2">N/A</td>
<td>N/A</td>
</tr>
<tr class="odd">
<td colspan="3"><p><strong>Revision Status:</strong></p>
<p>Revision D</p></td>
<td colspan="6"><p><strong>Owner:</strong></p>
<p>Electrical Engineering Division (560)</p></td>
<td colspan="2"><strong>Reference:</strong></td>
</tr>
</tbody>
</table>

<table>
<colgroup>
<col style="width: 10%" />
<col style="width: 12%" />
<col style="width: 8%" />
<col style="width: 4%" />
<col style="width: 12%" />
<col style="width: 12%" />
<col style="width: 2%" />
<col style="width: 10%" />
<col style="width: 5%" />
<col style="width: 7%" />
<col style="width: 12%" />
</colgroup>
<tbody>
<tr class="odd">
<td><strong>2.09</strong></td>
<td colspan="6"><strong>Spectrum Allocation Considerations</strong></td>
<td colspan="4"><strong>Electrical</strong></td>
</tr>
<tr class="even">
<td><strong>Principle:</strong></td>
<td colspan="10">National spectrum paperwork shall be developed for all
new GSFC missions, as well as analysis of mission compliance with
national and international spectrum regulations and recommendations.
This will include the determination of what specific carrier frequencies
should be recommended for these missions to minimize potential
interference.</td>
</tr>
<tr class="odd">
<td><strong>Rationale:</strong></td>
<td colspan="10">NASA requires that all operating missions be in
accordance with national allocations, service requirements, and
authorizations, and that its satellite systems be protected against
unacceptable interference from other satellite systems.</td>
</tr>
<tr class="even">
<td><strong>Phase:</strong></td>
<td colspan="10"><strong>&lt;A A B C D E F</strong></td>
</tr>
<tr class="odd">
<td><strong>Activities:</strong></td>
<td>N/A</td>
<td colspan="2">1. Begin work with mission to determine spectrum
requirements and inform mission as to what frequency bands are available
and what regulations must be met (e.g., PFD limits, <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">OOB</a>
emissions limits).</td>
<td>1. Continue consultations with project, including evaluating mission
design changes based on requirement to comply with national and
international spectrum regulations.</td>
<td>1. Confirm compliance with applicable national and international
regulations.<br />
2. Determine optimal frequency within desired band, based on search of
<a href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">GMF</a> and
<a href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">ITU</a>
databases and interference analysis.<br />
3. If there is non-compliance, inform project and recommend changes to
bring mission into compliance. If an acceptable frequency cannot be
found, recommend appropriate systems modifications.</td>
<td colspan="2">1. Validate compliance with applicable national and
international regulations by performing end-to-end compatibility
test.</td>
<td colspan="2">1. If mission experiences interference while in orbit,
investigate cause and recommend appropriate technical and/or regulatory
remedies.</td>
<td>1. If mission will be operational past originally authorized date,
file appropriate paperwork to ensure extension is granted.</td>
</tr>
<tr class="even">
<td><strong>Verification:</strong></td>
<td>N/A</td>
<td colspan="2">1. Verify at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">MDR</a>.</td>
<td>1. Verify at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">PDR</a>.</td>
<td>1. Verify at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">CDR</a>.</td>
<td colspan="2">1. Verify at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">PER</a> and <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">PSR</a>.</td>
<td colspan="2"></td>
<td></td>
</tr>
<tr class="odd">
<td colspan="3"><p><strong>Revision Status:</strong></p>
<p>Baseline</p></td>
<td colspan="6"><p><strong>Owner:</strong></p>
<p>Applied Engineering and Technology Directorate (500)</p></td>
<td colspan="2"><strong>Reference:</strong></td>
</tr>
</tbody>
</table>

<table>
<colgroup>
<col style="width: 10%" />
<col style="width: 12%" />
<col style="width: 8%" />
<col style="width: 4%" />
<col style="width: 12%" />
<col style="width: 12%" />
<col style="width: 2%" />
<col style="width: 10%" />
<col style="width: 5%" />
<col style="width: 7%" />
<col style="width: 12%" />
</colgroup>
<tbody>
<tr class="odd">
<td><strong>2.10</strong></td>
<td colspan="6"><strong>Electronic Design for Flight
Missions</strong></td>
<td colspan="4"><strong>Electrical</strong></td>
</tr>
<tr class="even">
<td><strong>Principle:</strong></td>
<td colspan="10">All flight mission electronics design and development
shall comply with the GSFC Electronics Design and Development Guidelines
500-PG-8700.2.2.</td>
</tr>
<tr class="odd">
<td><strong>Rationale:</strong></td>
<td colspan="10">Applying a structured approach to the planning,
execution and validation phases of a flight electronics product
mitigates the risk of budget and schedule overruns, and incorporates the
use of good engineering practices.</td>
</tr>
<tr class="even">
<td><strong>Phase:</strong></td>
<td colspan="10"><strong>&lt;A A B C D E F</strong></td>
</tr>
<tr class="odd">
<td><strong>Activities:</strong></td>
<td>1. Identify mission requirements and formulate a preliminary
electrical conceptual design.</td>
<td colspan="2">1. Collect all applicable design inputs into a
requirements document.<br />
2. Generate design planning documentation.<br />
3. Finalize conceptual design.</td>
<td>1. Perform detailed design.<br />
2. Demonstrate high risk areas through the use of breadboards, analysis
and/or simulations.<br />
3. Conduct design trade studies.</td>
<td>1. Build design verification platform such as an <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">ETU</a>,
testbed, etc.<br />
2. Demonstrate the design meets mission requirements.</td>
<td colspan="2">1. Fabricate and assemble flight hardware.<br />
2. Validate performance via the environmental test program.<br />
3. Document all results properly.<br />
4. Certify all requirements have been met.</td>
<td colspan="2">N/A</td>
<td>N/A</td>
</tr>
<tr class="even">
<td><strong>Verification:</strong></td>
<td>1.Verify at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">MCR</a>.</td>
<td colspan="2">1. Verify at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">SRR</a> and <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">MCR</a>.</td>
<td>1. Verify through peer review and at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">PDR</a>.</td>
<td>1. Verify through peer<br />
review and at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">CDR</a>.</td>
<td colspan="2">1. Verify through peer review and at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">PER</a> and <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">PSR</a>.</td>
<td colspan="2">N/A</td>
<td>N/A</td>
</tr>
<tr class="odd">
<td colspan="3"><p><strong>Revision Status:</strong></p>
<p>Baseline</p></td>
<td colspan="6"><p><strong>Owner:</strong></p>
<p>Electrical Engineering Division (560)</p></td>
<td colspan="2"><p><strong>Reference:</strong></p>
<p>500-PG-8700.2.2</p></td>
</tr>
</tbody>
</table>

<table>
<colgroup>
<col style="width: 10%" />
<col style="width: 12%" />
<col style="width: 8%" />
<col style="width: 4%" />
<col style="width: 12%" />
<col style="width: 12%" />
<col style="width: 2%" />
<col style="width: 10%" />
<col style="width: 5%" />
<col style="width: 7%" />
<col style="width: 12%" />
</colgroup>
<tbody>
<tr class="odd">
<td><strong>2.11</strong></td>
<td colspan="6"><strong>EMI/EMC Design for Flight Missions</strong></td>
<td colspan="4"><strong>Electrical</strong></td>
</tr>
<tr class="even">
<td><strong>Principle:</strong></td>
<td colspan="10">All flight mission systems/subsystems shall comply with
EMI/EMC requirements in <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">GEVS</a>
Section 2.5.</td>
</tr>
<tr class="odd">
<td><strong>Rationale:</strong></td>
<td colspan="10">Applying a structured EMI approach to the planning,
execution and validation phases of a flight electronics product
mitigates the risk of budget and schedule overruns, and incorporates the
use of good engineering practices.</td>
</tr>
<tr class="even">
<td><strong>Phase:</strong></td>
<td colspan="10"><strong>&lt;A A B C D E F</strong></td>
</tr>
<tr class="odd">
<td><strong>Activities:</strong></td>
<td>1. Assess potential for EMI/EMC concerns.</td>
<td colspan="2">1. Identify system/subsystem components and their
interfaces relative to EMI/EMC concerns.<br />
2. Categorize system components according to known or expected noise
magnitude and frequencies.</td>
<td>1. Using detailed electrical design, identify potential noise
sources and victims as well as coupling mechanisms.<br />
2. Perform analysis and simulations as required to assess and optimize
system configuration.<br />
3. Generate design guidelines for system and subsystems, including
grounding and shielding philosophy.<br />
4. Customize <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">EMC</a> test
levels and configuration and publish as the <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">EMC</a> Test
Plan.</td>
<td>1. Using subsystem ETU's and Test Beds, Confirm by measurement the
high risk source-victim noise coupling levels.<br />
2. Implement corrective measures as needed.<br />
3. Verify effectiveness of corrective measures.<br />
4. Identify mitigation strategies applicable to the flight
hardware.</td>
<td colspan="2">1. EMI Test Facility generates the EMI Test
Procedure.<br />
2. Using flight hardware, conduct environmental EMI tests to validate
performance against the <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">EMC</a> Test
Plan requirements.<br />
3. Evaluate EMI Test Results Report for EMI compliance.</td>
<td colspan="2">N/A</td>
<td>N/A</td>
</tr>
<tr class="even">
<td><strong>Verification:</strong></td>
<td>1. Verify at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">MCR</a>.</td>
<td colspan="2">1. Verify at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">SRR</a> and <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">MCR</a>.</td>
<td>1. Verify through peer<br />
reviews and at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">PDR</a>.</td>
<td>1. Verify through peer<br />
reviews and at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">CDR</a>.</td>
<td colspan="2">1. Verify through peer reviews and at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">PER</a> and <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">PSR</a>.</td>
<td colspan="2">N/A</td>
<td>N/A</td>
</tr>
<tr class="odd">
<td colspan="3"><p><strong>Revision Status:</strong></p>
<p>Baseline; Updated: Rev A</p></td>
<td colspan="6"><p><strong>Owner:</strong></p>
<p>Electrical Engineering Division (560)</p></td>
<td colspan="2"><p><strong>Reference:</strong></p>
<p>GEVS 2.5</p></td>
</tr>
</tbody>
</table>

<table>
<colgroup>
<col style="width: 10%" />
<col style="width: 12%" />
<col style="width: 8%" />
<col style="width: 4%" />
<col style="width: 12%" />
<col style="width: 12%" />
<col style="width: 2%" />
<col style="width: 10%" />
<col style="width: 5%" />
<col style="width: 7%" />
<col style="width: 12%" />
</colgroup>
<tbody>
<tr class="odd">
<td><strong>2.12</strong></td>
<td colspan="6"><strong>Printed Circuit Board Coupon
Analysis</strong></td>
<td colspan="4"><strong>Electrical</strong></td>
</tr>
<tr class="even">
<td><strong>Principle:</strong></td>
<td colspan="10">All flight printed circuit boards (PCBs) shall be
verified by coupon testing.</td>
</tr>
<tr class="odd">
<td><strong>Rationale:</strong></td>
<td colspan="10">Verifying the integrity of printed circuit boards
reduces the risk of an on-orbit board failure, and saves the added cost
of replacing flight-qualified components and reassembly if board failure
occurs during qualification testing.</td>
</tr>
<tr class="even">
<td><strong>Phase:</strong></td>
<td colspan="10"><strong>&lt;A A B C D E F</strong></td>
</tr>
<tr class="odd">
<td><strong>Activities:</strong></td>
<td>1. Provide within the conceptual study the electronic requirements
that will drive mission cost, schedule, and design.</td>
<td colspan="2">1. Update electronic requirements.<br />
2. Include coupon verification of flight boards in mission cost and
schedule estimates.</td>
<td>1. Update coupon evaluation requirements.</td>
<td>1. Finalize required PCBs.</td>
<td colspan="2">1. Submit coupons for analysis.</td>
<td colspan="2">N/A</td>
<td>N/A</td>
</tr>
<tr class="even">
<td><strong>Verification:</strong></td>
<td>1. Verify at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">MCR</a>.</td>
<td colspan="2">1. Verify at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">MDR</a>.</td>
<td>1. Verify at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">PDR</a>.</td>
<td>1. Verify at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">CDR</a>.</td>
<td colspan="2">1. Verify results of all coupon testing at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">PER</a>.</td>
<td colspan="2">N/A</td>
<td>N/A</td>
</tr>
<tr class="odd">
<td colspan="3"><p><strong>Revision Status:</strong></p>
<p>Baseline</p></td>
<td colspan="6"><p><strong>Owner:</strong></p>
<p>Electrical Engineering Division (560)</p></td>
<td colspan="2"><p><strong>Reference:</strong></p>
<p>300-PG-7120.2.2B</p></td>
</tr>
</tbody>
</table>

<table>
<colgroup>
<col style="width: 10%" />
<col style="width: 12%" />
<col style="width: 8%" />
<col style="width: 4%" />
<col style="width: 12%" />
<col style="width: 12%" />
<col style="width: 2%" />
<col style="width: 10%" />
<col style="width: 5%" />
<col style="width: 7%" />
<col style="width: 12%" />
</colgroup>
<tbody>
<tr class="odd">
<td><strong>2.13</strong></td>
<td colspan="6"><strong>Electrical Connector Mating</strong></td>
<td colspan="4"><strong>Electrical</strong></td>
</tr>
<tr class="even">
<td><strong>Principle:</strong></td>
<td colspan="10">Mating of all flight connectors which cannot be
verified via ground tests, shall be clearly labeled and keyed uniquely,
and mating of them shall be verified visually to prevent incorrect
mating.</td>
</tr>
<tr class="odd">
<td><strong>Rationale:</strong></td>
<td colspan="10">Error in mating of interchangeable connectors can
result in mission degradation or failure.</td>
</tr>
<tr class="even">
<td><strong>Phase:</strong></td>
<td colspan="10"><strong>&lt;A A B C D E F</strong></td>
</tr>
<tr class="odd">
<td><strong>Activities:</strong></td>
<td>N/A</td>
<td colspan="2">N/A</td>
<td>1. Identify operations that cannot be tested on the ground.</td>
<td>1. Present plans to prevent error in mating of electrical
connectors.</td>
<td colspan="2">1. Verify by inspection &amp; photo documentation that
electrical connectors are mated correctly.</td>
<td colspan="2">N/A</td>
<td>N/A</td>
</tr>
<tr class="even">
<td><strong>Verification:</strong></td>
<td>N/A</td>
<td colspan="2">N/A</td>
<td>1. Verify at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">PDR</a>.</td>
<td>1. Verify at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">CDR</a>.</td>
<td colspan="2">1. Verify at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">PER</a>.</td>
<td colspan="2">N/A</td>
<td>N/A</td>
</tr>
<tr class="odd">
<td colspan="3"><p><strong>Revision Status:</strong></p>
<p>Baseline</p></td>
<td colspan="6"><p><strong>Owner:</strong></p>
<p>Electrical Engineering Division (560)</p></td>
<td colspan="2"><strong>Reference:</strong></td>
</tr>
</tbody>
</table>

<table>
<colgroup>
<col style="width: 10%" />
<col style="width: 12%" />
<col style="width: 8%" />
<col style="width: 4%" />
<col style="width: 12%" />
<col style="width: 12%" />
<col style="width: 2%" />
<col style="width: 10%" />
<col style="width: 5%" />
<col style="width: 7%" />
<col style="width: 12%" />
</colgroup>
<tbody>
<tr class="odd">
<td><strong>2.14</strong></td>
<td colspan="6"><strong>Capping of Test Points and Plugs</strong></td>
<td colspan="4"><strong>Flight System I&amp;T (EED) </strong></td>
</tr>
<tr class="even">
<td><strong>Principle:</strong></td>
<td colspan="10">All test points and plugs must be capped or protected
from discharge for flight.</td>
</tr>
<tr class="odd">
<td><strong>Rationale:</strong></td>
<td colspan="10">Capping open connectors provides protection from
electrostatic discharge resulting from space charging.</td>
</tr>
<tr class="even">
<td><strong>Phase:</strong></td>
<td colspan="10"><strong>&lt;A A B C D E F</strong></td>
</tr>
<tr class="odd">
<td><strong>Activities:</strong></td>
<td>N/A</td>
<td colspan="2">N/A</td>
<td>1. Develop electrical systems requirements.<br />
2. Identify the need for capping all open connectors and grounding the
caps to chassis.</td>
<td>1. Develop electrical <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">ICD</a> stating
requirement for capping open connectors.<br />
2. Develop harness drawings.</td>
<td colspan="2">1. Verify by inspection of build records (WOAs,
traveler, etc.) that provisions for capping open connectors have been
completed.<br />
2. Verify final blanket closeout procedure includes check to verify
connectors are capped.</td>
<td colspan="2">N/A</td>
<td>N/A</td>
</tr>
<tr class="even">
<td><strong>Verification:</strong></td>
<td>N/A</td>
<td colspan="2">N/A</td>
<td>1. Verify through peer review and at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">PDR</a>.<br />
2. Ensure parts and materials list include connector caps.</td>
<td>1. Verify harness drawings include connector caps for any open
connectors and their grounding provisions.</td>
<td colspan="2">1. Inspect during pre-fairing, post fairing installation
and final blanket closeouts.</td>
<td colspan="2">N/A</td>
<td>N/A</td>
</tr>
<tr class="odd">
<td colspan="3"><p><strong>Revision Status:</strong></p>
<p>Revision B</p></td>
<td colspan="6"><p><strong>Owner:</strong></p>
<p>Flight Systems Integration and Test Branch (568)</p></td>
<td colspan="2"><strong>Reference:</strong></td>
</tr>
</tbody>
</table>

<table>
<colgroup>
<col style="width: 10%" />
<col style="width: 12%" />
<col style="width: 8%" />
<col style="width: 4%" />
<col style="width: 12%" />
<col style="width: 12%" />
<col style="width: 2%" />
<col style="width: 10%" />
<col style="width: 5%" />
<col style="width: 1%" />
<col style="width: 5%" />
<col style="width: 12%" />
</colgroup>
<tbody>
<tr class="odd">
<td><strong>2.15</strong></td>
<td colspan="6"><strong>Flight and Ground Electrical
Hardware</strong></td>
<td colspan="5"><strong>Flight System I&amp;T (EED)</strong></td>
</tr>
<tr class="even">
<td><strong>Principle:</strong></td>
<td colspan="11">The use of pure tin, cadmium, and zinc plating in
flight and ground electrical hardware shall be prohibited.</td>
</tr>
<tr class="odd">
<td><strong>Rationale:</strong></td>
<td colspan="11">High purity tin, zinc and cadmium finishes are prone to
formation of metallic whiskers which may produce an electrical shorting
or contamination hazard. The current worldwide initiative to reduce the
use of potentially hazardous materials such as lead (Pb) is driving the
electronics industry to consider alternatives to the widely used
tin-lead alloys used for plating. Pure tin, cadmium and zinc finishes
renew the concern over the threat of system failures due to metallic
whiskers.</td>
</tr>
<tr class="even">
<td><strong>Phase:</strong></td>
<td colspan="11"><strong>&lt;A A B C D E F</strong></td>
</tr>
<tr class="odd">
<td><strong>Activities:</strong></td>
<td>N/A</td>
<td colspan="2">N/A</td>
<td>1. Define procurement specs for <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">EEE</a> parts
and mechanical hardware to preclude the use of pure tin, zinc and
cadmium finishes (to include both external and internal finishes as well
as the use of these finishes an under plates).</td>
<td>1. Evaluate Application Specific Risks to assess the risk of whisker
induced failures. These factors include circuit geometries that are
sufficiently large to preclude the risk of a tin whisker short, mission
criticality, mission duration, collateral risk of rework, schedule and
cost.<br />
2. Manufacturers should provide material and chemical information on
packages, solder and lead finishes of the parts manufactured for their
project to document/certify zinc, cadmium tin alloy.</td>
<td colspan="2">1. Parts Lists should be generated for tracking
potential parts application issues, and to ensure monitoring of
GIDEP/Manufacturer process change notices to be aware of lead free
changes at specified manufacturers.<br />
2. Parts lists should be kept current, uploaded into the parts database,
and reviewed for risk assessment.<br />
3. Conduct <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">EEE</a> parts
materials evaluation of each of parts list to verify that the chemical
composition of the packages, lead frames, connectors and/or solder does
not contain prohibited materials.</td>
<td colspan="3">N/A</td>
<td>N/A</td>
</tr>
<tr class="even">
<td><strong>Verification:</strong></td>
<td>N/A</td>
<td colspan="2">N/A</td>
<td>1. Verify at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">PDR</a>.</td>
<td>1. Verify at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">CDR</a>.</td>
<td colspan="2">1. Verify using the Parts List Evaluation Report prior
to Launch ( <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">PER</a> and <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">PSR</a> ).</td>
<td colspan="3">N/A</td>
<td>N/A</td>
</tr>
<tr class="odd">
<td colspan="3"><p><strong>Revision Status:</strong></p>
<p>Revision B</p></td>
<td colspan="7"><p><strong>Owner:</strong></p>
<p>Parts, Packaging and <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">Assembly</a>
Technologies (562); Materials Engineering (541)</p></td>
<td colspan="2"><strong>Reference:</strong></td>
</tr>
<tr class="even">
<td><strong>2.16</strong></td>
<td colspan="6"><strong>Solar Arrays</strong></td>
<td colspan="5"><strong>Flight System I&amp;T (EED)</strong></td>
</tr>
<tr class="odd">
<td><strong>Principle:</strong></td>
<td colspan="11">Solar Arrays shall be designed in accordance with
563-PG-8700.2.2, and tested to withstand the environment to which they
will be exposed. The q-panel and array shall be tested under
illumination at the highest predicted operating temperature, and in
accordance with AIAA S-111-2005 and AIAA S-112-2005.</td>
</tr>
<tr class="even">
<td><strong>Rationale:</strong></td>
<td colspan="11">At the time this is written, solar arrays are the least
reliable component on spacecraft.</td>
</tr>
<tr class="odd">
<td><strong>Phase:</strong></td>
<td colspan="11"><strong>&lt;A A B C D E F</strong></td>
</tr>
<tr class="even">
<td><strong>Activities:</strong></td>
<td>1. Design the array.</td>
<td colspan="2">1. Revise the design of the array.</td>
<td>1. Revise the design of the array.</td>
<td>1. Revise the design and develop test plans for the array.<br />
2. Write an <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">ICD</a>.</td>
<td colspan="2">1. Fabricate the solar cells and solar array.<br />
2. Test the q-panel and array under illumination at highest predicted
operating temperature to AIAA S-111-2005 &amp; AIAA S-112-2005.<br />
3. Test the solar cells, q-panel and solar array to AIAA S-111-2005
&amp; AIAA S-112-2005.</td>
<td colspan="3">1. Monitor array output on an hourly basis for 48 hours
subsequent to launch and on a weekly basis thereafter.<br />
2. Check output versus predictions and reconcile.</td>
<td>N/A</td>
</tr>
<tr class="odd">
<td><strong>Verification:</strong></td>
<td>1. Verify at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">MCR</a>.</td>
<td colspan="2">1. Verify at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">MDR</a>.</td>
<td>1. Verify at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">PDR</a>.</td>
<td>1. Verify at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">CDR</a>.<br />
2. Peer review the array design, applicable ICDs and test program.</td>
<td colspan="2">1. Verify at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">PER</a>, <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">PSR</a>.</td>
<td colspan="3">1. Verify hourly in the 48 hours subsequent to launch,
and weekly thereafter.</td>
<td>N/A</td>
</tr>
<tr class="even">
<td colspan="3"><p><strong>Revision Status:</strong></p>
<p>Revision B</p></td>
<td colspan="6"><p><strong>Owner:</strong></p>
<p>Flight Systems Integration and Test (568)</p></td>
<td colspan="3"><strong>Reference:</strong></td>
</tr>
</tbody>
</table>

<table>
<colgroup>
<col style="width: 10%" />
<col style="width: 12%" />
<col style="width: 8%" />
<col style="width: 4%" />
<col style="width: 12%" />
<col style="width: 12%" />
<col style="width: 2%" />
<col style="width: 10%" />
<col style="width: 5%" />
<col style="width: 7%" />
<col style="width: 12%" />
</colgroup>
<tbody>
<tr class="odd">
<td><strong>2.17</strong></td>
<td colspan="6"><strong>I&amp;T Development Input</strong></td>
<td colspan="4"><strong>Electrical Engineering</strong></td>
</tr>
<tr class="even">
<td><strong>Principle:</strong></td>
<td colspan="10">Integration &amp; Test discipline expertise shall be
used throughout the product lifecycle.</td>
</tr>
<tr class="odd">
<td><strong>Rationale:</strong></td>
<td colspan="10">Projects proposed, defined or designed without adequate
focus on the integration and testing process have had significant cost
and schedule overruns.</td>
</tr>
<tr class="even">
<td><strong>Phase:</strong></td>
<td colspan="10"><strong>&lt;A A B C D E F</strong></td>
</tr>
<tr class="odd">
<td><strong>Activities:</strong></td>
<td>1. Analyze system level requirements for test planning.</td>
<td colspan="2">1. Review system level and subsystem requirements for <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">I&amp;T</a>
planning.</td>
<td>1. Review system verification and testing plans and subsystem test
concepts and flow-down.<br />
2. Formulate <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">I&amp;T</a>
Plan and begin facilities planning.</td>
<td>1. Review test plans and procedures.</td>
<td colspan="2">1. Establish final staffing personnel.<br />
2. Review subsystem testing and results.<br />
3. Finalize environmental test plans.<br />
4. Finalize test scripts and C&amp;T database.<br />
5. Conduct <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">I&amp;T</a> per
<a href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">I&amp;T</a>
Plan.</td>
<td colspan="2">N/A</td>
<td>N/A</td>
</tr>
<tr class="even">
<td><strong>Verification:</strong></td>
<td>1. Verify at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">MCR</a>.</td>
<td colspan="2">1. Verify at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">MDR</a>.</td>
<td>1. Verify at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">SDR</a>, <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">PDR</a>.</td>
<td>1. Verify at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">CDR</a>.</td>
<td colspan="2">1. Verify at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">PER</a>, <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">PSR</a>.</td>
<td colspan="2">N/A</td>
<td>N/A</td>
</tr>
<tr class="odd">
<td colspan="3"><p><strong>Revision Status:</strong></p>
<p>Revision B</p></td>
<td colspan="6"><p><strong>Owner:</strong></p>
<p>Flight Systems Integration and Test (568)</p></td>
<td colspan="2"><strong>Reference:</strong></td>
</tr>
</tbody>
</table>

<table>
<colgroup>
<col style="width: 10%" />
<col style="width: 12%" />
<col style="width: 8%" />
<col style="width: 4%" />
<col style="width: 12%" />
<col style="width: 12%" />
<col style="width: 2%" />
<col style="width: 10%" />
<col style="width: 5%" />
<col style="width: 7%" />
<col style="width: 12%" />
</colgroup>
<tbody>
<tr class="odd">
<td><strong>2.18</strong></td>
<td colspan="6"><strong>Redundant Functions</strong></td>
<td colspan="4"><strong>Electrical Engineering</strong></td>
</tr>
<tr class="even">
<td><strong>Principle:</strong></td>
<td colspan="10">Redundant functions shall not be routed through a
single connector, relay, or integrated circuit. The same applies to
related signals from both sides of a redundant subsystem (such as an
ENABLE for side A and an ARM for side B).</td>
</tr>
<tr class="odd">
<td><strong>Rationale:</strong></td>
<td colspan="10">While redundancy can greatly enhance system reliability
and confidence, it also incorporates added complexity to the overall
design. Design considerations must take into account the complexity that
is added by redundant components, in order to mitigate potential
negative effects upon the overall system reliability.</td>
</tr>
<tr class="even">
<td><strong>Phase:</strong></td>
<td colspan="10"><strong>&lt;A A B C D E F</strong></td>
</tr>
<tr class="odd">
<td><strong>Activities:</strong></td>
<td>1. Complete applicability assessment.</td>
<td colspan="2"><p>1. Reassess and update applicability.</p>
<p>2. Complete initial compliance assessment, based upon
applicability.</p></td>
<td><p>1. Reassess compliance.</p>
<p>2. Ensure flow-down traceability to appropriate sub-system in draft
technical requirements and Design-To specifications.</p>
<p>3. Define verification approach.</p></td>
<td><p>1. Reassess compliance.</p>
<p>2. Ensure flow-down traceability to appropriate sub-system in
technical requirements and Design-To specification baselines.</p>
<p>3. Update verification approach.</p></td>
<td colspan="2"><p>1. Reassess compliance.</p>
<p>2. Perform verification activity.</p></td>
<td colspan="2">N/A</td>
<td>N/A</td>
</tr>
<tr class="even">
<td><strong>Verification:</strong></td>
<td>1. Verify at MCR.</td>
<td colspan="2">1. Verify at SRR, MDR, and PNAR.</td>
<td>1. Verify at PDR and NAR.</td>
<td>1. Verify at CDR and SIR.</td>
<td colspan="2">1. Verify at ORR, SMSR, and FRR.</td>
<td colspan="2">N/A</td>
<td>N/A</td>
</tr>
<tr class="odd">
<td colspan="3"><p><strong>Revision Status:</strong></p>
<p>Revision D</p></td>
<td colspan="6"><p><strong>Owner:</strong></p>
<p>Electrical Engineering Division (560)</p></td>
<td colspan="2"><strong>Reference:</strong></td>
</tr>
</tbody>
</table>

<table>
<colgroup>
<col style="width: 10%" />
<col style="width: 12%" />
<col style="width: 8%" />
<col style="width: 4%" />
<col style="width: 12%" />
<col style="width: 12%" />
<col style="width: 2%" />
<col style="width: 10%" />
<col style="width: 5%" />
<col style="width: 7%" />
<col style="width: 12%" />
</colgroup>
<tbody>
<tr class="odd">
<td><strong>2.19</strong></td>
<td colspan="6"><strong>Multiple Circuit Power Buss Loss</strong></td>
<td colspan="4"><strong>Electrical Engineering</strong></td>
</tr>
<tr class="even">
<td><strong>Principle:</strong></td>
<td colspan="10">Designs with multiple circuits operating from separate,
somewhat isolated power buses, shall be able to tolerate the shorting or
loss of any one of those power buses.</td>
</tr>
<tr class="odd">
<td><strong>Rationale:</strong></td>
<td colspan="10">While redundancy can greatly enhance system reliability
and confidence, it also incorporates added complexity to the overall
design. Design considerations must take into account the complexity that
is added by redundant components, in order to mitigate potential
negative effects upon the overall system reliability.</td>
</tr>
<tr class="even">
<td><strong>Phase:</strong></td>
<td colspan="10"><strong>&lt;A A B C D E F</strong></td>
</tr>
<tr class="odd">
<td><strong>Activities:</strong></td>
<td>1. Complete applicability assessment.</td>
<td colspan="2"><p>1. Reassess and update applicability.</p>
<p>2. Complete initial compliance assessment, based upon
applicability.</p></td>
<td><p>1. Reassess compliance.</p>
<p>2. Ensure flow-down traceability to appropriate sub-system in draft
technical requirements and Design-To specifications.</p>
<p>3. Define verification approach.</p></td>
<td><p>1. Reassess compliance.</p>
<p>2. Ensure flow-down traceability to appropriate sub-system in
technical requirements and Design-To specification baselines.</p>
<p>3. Update verification approach.</p></td>
<td colspan="2"><p>1. Reassess compliance.</p>
<p>2. Perform verification activity.</p></td>
<td colspan="2">N/A</td>
<td>N/A</td>
</tr>
<tr class="even">
<td><strong>Verification:</strong></td>
<td>1. Verify at MCR.</td>
<td colspan="2">1. Verify at SRR, MDR, and PNAR.</td>
<td>1. Verify at PDR and NAR.</td>
<td>1. Verify at CDR and SIR.</td>
<td colspan="2">1. Verify at ORR, SMSR, and FRR.</td>
<td colspan="2">N/A</td>
<td>N/A</td>
</tr>
<tr class="odd">
<td colspan="3"><p><strong>Revision Status:</strong></p>
<p>Revision D</p></td>
<td colspan="6"><p><strong>Owner:</strong></p>
<p>Electrical Engineering Division (560)</p></td>
<td colspan="2"><strong>Reference:</strong></td>
</tr>
</tbody>
</table>

<table>
<colgroup>
<col style="width: 10%" />
<col style="width: 12%" />
<col style="width: 8%" />
<col style="width: 4%" />
<col style="width: 12%" />
<col style="width: 12%" />
<col style="width: 2%" />
<col style="width: 10%" />
<col style="width: 5%" />
<col style="width: 7%" />
<col style="width: 12%" />
</colgroup>
<tbody>
<tr class="odd">
<td><strong>2.20</strong></td>
<td colspan="6"><strong>Single Point Failure Dependency in
Active-Redundant Cross-Strapped Architectures</strong></td>
<td colspan="4"><strong>Electrical Engineering</strong></td>
</tr>
<tr class="even">
<td><strong>Principle:</strong></td>
<td colspan="10">Cross-strapped redundant elements (inside an assembly,
or at external interfaces) shall be isolated from anomalous control line
conditions.</td>
</tr>
<tr class="odd">
<td><strong>Rationale:</strong></td>
<td colspan="10">The most essential analysis in a design that uses
redundancy is that of the cross-strapping networks. A mechanism is
needed to identify and quantify the risk to select an implementation
that will ultimately reduce the risk to the minimum permissible level
within a project’s cost, schedule, and performance constraints. Because
most spacecraft systems are extremely complex, a method of risk
identification must be used which has total visibility into the system.
The FMECA has been recognized as such an approach.</td>
</tr>
<tr class="even">
<td><strong>Phase:</strong></td>
<td colspan="10"><strong>&lt;A A B C D E F</strong></td>
</tr>
<tr class="odd">
<td><strong>Activities:</strong></td>
<td>1. Complete applicability assessment.</td>
<td colspan="2"><p>1. Reassess and update applicability.</p>
<p>2. Complete initial compliance assessment, based upon
applicability.</p></td>
<td><p>1. Reassess compliance.</p>
<p>2. Ensure flow-down traceability to appropriate sub-system in draft
technical requirements and Design-To specifications.</p>
<p>3. Define verification approach.</p></td>
<td><p>1. Reassess compliance.</p>
<p>2. Ensure flow-down traceability to appropriate sub-system in
technical requirements and Design-To specification baselines.</p>
<p>3. Update verification approach.</p></td>
<td colspan="2"><p>1. Reassess compliance.</p>
<p>2. Perform verification activity.</p></td>
<td colspan="2">N/A</td>
<td>N/A</td>
</tr>
<tr class="even">
<td><strong>Verification:</strong></td>
<td>1. Verify at MCR.</td>
<td colspan="2">1. Verify at SRR, MDR, and PNAR.</td>
<td>1. Verify at PDR and NAR.</td>
<td>1. Verify at CDR and SIR.</td>
<td colspan="2">1. Verify at ORR, SMSR, and FRR.</td>
<td colspan="2">N/A</td>
<td>N/A</td>
</tr>
<tr class="odd">
<td colspan="3"><p><strong>Revision Status:</strong></p>
<p>Revision D</p></td>
<td colspan="6"><p><strong>Owner:</strong></p>
<p>Electrical Engineering Division (560)</p></td>
<td colspan="2"><strong>Reference:</strong></td>
</tr>
</tbody>
</table>

<table>
<colgroup>
<col style="width: 10%" />
<col style="width: 12%" />
<col style="width: 8%" />
<col style="width: 4%" />
<col style="width: 12%" />
<col style="width: 12%" />
<col style="width: 2%" />
<col style="width: 10%" />
<col style="width: 5%" />
<col style="width: 7%" />
<col style="width: 12%" />
</colgroup>
<tbody>
<tr class="odd">
<td><strong>2.21</strong></td>
<td colspan="6"><strong>Gross Failure of Integrated
Circuits</strong></td>
<td colspan="4"><strong>Electrical Engineering</strong></td>
</tr>
<tr class="even">
<td><strong>Principle:</strong></td>
<td colspan="10">Integrated circuits, or other devices receiving signals
from redundant sides, shall incorporate isolation resistors, capacitors,
or other elements such that gross failure of the integrated circuit
(such as Vcc short to ground) shall not compromise both signal
sources.</td>
</tr>
<tr class="odd">
<td><strong>Rationale:</strong></td>
<td colspan="10">While redundancy can greatly enhance system reliability
and confidence, it also incorporates added complexity to the overall
design. Design considerations must take into account the complexity that
is added by redundant components, in order to mitigate potential
negative effects upon the overall system reliability.</td>
</tr>
<tr class="even">
<td><strong>Phase:</strong></td>
<td colspan="10"><strong>&lt;A A B C D E F</strong></td>
</tr>
<tr class="odd">
<td><strong>Activities:</strong></td>
<td>1. Complete applicability assessment.</td>
<td colspan="2"><p>1. Reassess and update applicability.</p>
<p>2. Complete initial compliance assessment, based upon
applicability.</p></td>
<td><p>1. Reassess compliance.</p>
<p>2. Ensure flow-down traceability to appropriate sub-system in draft
technical requirements and Design-To specifications.</p>
<p>3. Define verification approach.</p></td>
<td><p>1. Reassess compliance.</p>
<p>2. Ensure flow-down traceability to appropriate sub-system in
technical requirements and Design-To specification baselines.</p>
<p>3. Update verification approach.</p></td>
<td colspan="2"><p>1. Reassess compliance.</p>
<p>2. Perform verification activity.</p></td>
<td colspan="2">N/A</td>
<td>N/A</td>
</tr>
<tr class="even">
<td><strong>Verification:</strong></td>
<td>1. Verify at MCR.</td>
<td colspan="2">1. Verify at SRR, MDR, and PNAR.</td>
<td>1. Verify at PDR and NAR.</td>
<td>1. Verify at CDR and SIR.</td>
<td colspan="2">1. Verify at ORR, SMSR, and FRR.</td>
<td colspan="2">N/A</td>
<td>N/A</td>
</tr>
<tr class="odd">
<td colspan="3"><p><strong>Revision Status:</strong></p>
<p>Revision D</p></td>
<td colspan="6"><p><strong>Owner:</strong></p>
<p>Electrical Engineering Division (560)</p></td>
<td colspan="2"><strong>Reference:</strong></td>
</tr>
</tbody>
</table>

<table>
<colgroup>
<col style="width: 10%" />
<col style="width: 12%" />
<col style="width: 8%" />
<col style="width: 4%" />
<col style="width: 12%" />
<col style="width: 12%" />
<col style="width: 2%" />
<col style="width: 10%" />
<col style="width: 5%" />
<col style="width: 7%" />
<col style="width: 12%" />
</colgroup>
<tbody>
<tr class="odd">
<td><strong>2.22</strong></td>
<td colspan="6"><strong>Corona Region Testing of High Voltage
Equipment</strong></td>
<td colspan="4"><strong>Electrical Engineering</strong></td>
</tr>
<tr class="even">
<td><strong>Principle:</strong></td>
<td colspan="10">Assemblies containing a High Voltage supply that is not
tested through the Corona region shall undergo venting / outgassing
analysis to determine when it is safe to turn on and operate after
launch.</td>
</tr>
<tr class="odd">
<td><strong>Rationale:</strong></td>
<td colspan="10">Each High Voltage supply is different in its design and
the voltage where coronal discharge may occur will vary by the
construction and materials used.  It will also be dependent on how clean
the supply is and how well the outgassing products are vented to
space.</td>
</tr>
<tr class="even">
<td><strong>Phase:</strong></td>
<td colspan="10"><strong>&lt;A A B C D E F</strong></td>
</tr>
<tr class="odd">
<td><strong>Activities:</strong></td>
<td>1. Complete applicability assessment.</td>
<td colspan="2"><p>1. Reassess and update applicability.</p>
<p>2. Complete initial compliance assessment, based upon
applicability.</p></td>
<td><p>1. Reassess compliance.</p>
<p>2. Ensure flow-down traceability to appropriate sub-system in draft
technical requirements and Design-To specifications.</p>
<p>3. Define verification approach.</p></td>
<td><p>1. Reassess compliance.</p>
<p>2. Ensure flow-down traceability to appropriate sub-system in
technical requirements and Design-To specification baselines.</p>
<p>3. Update verification approach.</p></td>
<td colspan="2"><p>1. Reassess compliance.</p>
<p>2. Perform verification activity.</p></td>
<td colspan="2">N/A</td>
<td>N/A</td>
</tr>
<tr class="even">
<td><strong>Verification:</strong></td>
<td>1. Verify at MCR.</td>
<td colspan="2">1. Verify at SRR, MDR, and PNAR.</td>
<td>1. Verify at PDR and NAR.</td>
<td>1. Verify at CDR and SIR.</td>
<td colspan="2">1. Verify at ORR, SMSR, and FRR.</td>
<td colspan="2">N/A</td>
<td>N/A</td>
</tr>
<tr class="odd">
<td colspan="3"><p><strong>Revision Status:</strong></p>
<p>Revision D</p></td>
<td colspan="6"><p><strong>Owner:</strong></p>
<p>Electrical Engineering Division (560)</p></td>
<td colspan="2"><strong>Reference:</strong></td>
</tr>
</tbody>
</table>

<table>
<colgroup>
<col style="width: 10%" />
<col style="width: 12%" />
<col style="width: 8%" />
<col style="width: 4%" />
<col style="width: 12%" />
<col style="width: 12%" />
<col style="width: 2%" />
<col style="width: 10%" />
<col style="width: 5%" />
<col style="width: 7%" />
<col style="width: 12%" />
</colgroup>
<tbody>
<tr class="odd">
<td><strong>3.01</strong></td>
<td colspan="6"><strong>Verification and Validation Program for Mission
Software Systems</strong></td>
<td colspan="4"><strong>Software</strong></td>
</tr>
<tr class="even">
<td>Principle:</td>
<td colspan="10">A thorough verification and validation process shall be
applied to all mission software systems. This process shall trace
customer/mission operations concepts and science requirements to
implementation requirements and system design, and shall include
requirements based testing of all mission elements, and end-to-end
system operations scenario testing.</td>
</tr>
<tr class="odd">
<td>Rationale:</td>
<td colspan="10">Mission software, especially flight software, must be
tested thoroughly to ensure a successful mission/project.</td>
</tr>
<tr class="even">
<td>Phase:</td>
<td colspan="10"><strong>&lt;A A B C D E F</strong></td>
</tr>
<tr class="odd">
<td>Activities:</td>
<td>1. Develop first version of Operations Concept with customer.<br />
2. Document <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">SW</a>
functionality at high level.<br />
3. Document <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">SW</a>
verification and validation approach.<br />
4. Document cost estimate for overall <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">SW</a>
design.</td>
<td colspan="2">1. Update Ops Concept.<br />
2. Identify test tools to be used for software testing (fidelity,
quantity).<br />
3. Update verification and validation approach and associated cost and
schedule based upon updated requirements.</td>
<td>1. Draft Software Test Plan<br />
2. Draft <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">SW</a> <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">Traceability
Matrix</a> showing <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">SW</a>
requirements traced to parent requirements and to software
components.</td>
<td>1. Complete <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">SW</a> test
plan.<br />
2. Identify verification and validation program risks.<br />
3. Update <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">SW</a> <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">Traceability
Matrix</a>.</td>
<td colspan="2">1. Develop detailed test scenarios/cases.<br />
2. Complete traceability of requirements to <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">SW</a> design
and <a href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">SW</a>
test program.<br />
3. Execute <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">SW</a> test
plan.</td>
<td colspan="2">N/A</td>
<td>N/A</td>
</tr>
<tr class="even">
<td><strong>Verification:</strong></td>
<td>1. Verify by inspection through peer review and at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">MCR</a>.</td>
<td colspan="2">1. Review by analysis the verification and validation
approach for the mission through peer review and at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">MDR</a>.</td>
<td>1. Verify software development and test program by analysis through
peer review.<br />
2. Verify that budget and schedule accommodate regression and end-to-end
mission testing at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">SDR</a> and <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">PDR</a>.</td>
<td>1. Verify by analysis at software <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">PDR</a>.</td>
<td colspan="2">1. Verify by analysis at software <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">CDR</a> and
Test Readiness Review.</td>
<td colspan="2">N/A</td>
<td>N/A</td>
</tr>
<tr class="odd">
<td colspan="3"><p><strong>Revision Status:</strong></p>
<p>Baseline</p></td>
<td colspan="6"><p><strong>Owner:</strong></p>
<p>Systems Integration and Engineering Branch (581)</p></td>
<td colspan="2"><p><strong>Reference:</strong></p>
<p>GPR 8700.5</p></td>
</tr>
</tbody>
</table>

<table style="width:100%;">
<colgroup>
<col style="width: 10%" />
<col style="width: 12%" />
<col style="width: 8%" />
<col style="width: 4%" />
<col style="width: 12%" />
<col style="width: 12%" />
<col style="width: 2%" />
<col style="width: 10%" />
<col style="width: 3%" />
<col style="width: 9%" />
<col style="width: 12%" />
</colgroup>
<tbody>
<tr class="odd">
<td><strong>3.02</strong></td>
<td colspan="6"><strong>Elimination of Dead Software/Code</strong></td>
<td colspan="4"><strong>Systems Engineering; Software</strong></td>
</tr>
<tr class="even">
<td><strong>Principle:</strong></td>
<td colspan="10">GSFC missions shall not deploy systems containing dead
software/code. For the purposes of this rule, dead software/code is
defined as: <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">Unreachable
Code</a> (Unintentional/Intentional); <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">Unused Code</a>
(Unintentional/Intentional); <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">Unused Reuse
Capabilities</a> ; <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">Unused Design
Capabilities</a> ; <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">Unneeded
Features</a> in Commercial Software; <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">Test
Features</a> (Advertised/Unadvertised, Documented/Undocumented,
Tested/Untested; <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">Debug
Features</a> (Advertised/Unadvertised, Documented/Undocumented,
Tested/Untested); <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">Meaningless
Code</a>. See Glossary.</td>
</tr>
<tr class="odd">
<td><strong>Rationale:</strong></td>
<td colspan="10">Dead software/code greatly increases a system's EXE
and/or DLL file sizes, directly contributing to an inefficient use of
memory and slower execution times. In addition, dead code means more
source code to read, understand, and maintain, directly leading to
increased costs. Most importantly, dead code is carried forward,
untested, creating the potential for future system problems, thus having
a negative effect upon <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">Mission
success</a>.</td>
</tr>
<tr class="even">
<td><strong>Phase:</strong></td>
<td colspan="10"><strong>&lt;A A B C D E F</strong></td>
</tr>
<tr class="odd">
<td><strong>Activities:</strong></td>
<td>N/A</td>
<td colspan="2">1. Ensure consideration in Preliminary Software
Management Plan.<br />
2. Coordinate with Systems Engineering Management Plan.</td>
<td>1. Prepare functional and design-to baselines.<br />
2. Ensure consideration in baseline Software &amp; Systems Engineering
Management Plans.</td>
<td>1. Prepare lower-level design, software interface documents.<br />
2. Refine verification plans.</td>
<td colspan="2">1. Develop verification procedures.<br />
2. Implement integration plan.<br />
3. Audit as-built configuration.</td>
<td colspan="2">N/A</td>
<td>N/A</td>
</tr>
<tr class="even">
<td><strong>Verification:</strong></td>
<td>N/A</td>
<td colspan="2">1. Verify at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">MDR</a>.</td>
<td>1. Verify at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">SDR</a> &amp;
<a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">PDR</a>.</td>
<td>1. Verify at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">CDR</a>.</td>
<td colspan="2">1. Verify at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">PSR</a> and
FRR.</td>
<td colspan="2">N/A</td>
<td>N/A</td>
</tr>
<tr class="odd">
<td colspan="3"><p><strong>Revision Status:</strong></p>
<p>Revision C.1</p></td>
<td colspan="6"><p><strong>Owner:</strong></p>
<p>Rules &amp; Processes (171)</p></td>
<td colspan="2"><p><strong>Reference:</strong></p>
<p>Dead Code Definition_Ver300.doc</p></td>
</tr>
</tbody>
</table>

<table>
<colgroup>
<col style="width: 10%" />
<col style="width: 12%" />
<col style="width: 8%" />
<col style="width: 4%" />
<col style="width: 12%" />
<col style="width: 12%" />
<col style="width: 2%" />
<col style="width: 10%" />
<col style="width: 5%" />
<col style="width: 7%" />
<col style="width: 12%" />
</colgroup>
<tbody>
<tr class="odd">
<td><strong>3.03</strong></td>
<td colspan="6"><strong>High Fidelity Interface Simulation
Capabilities</strong></td>
<td colspan="4"><strong>Software</strong></td>
</tr>
<tr class="even">
<td><strong>Principle:</strong></td>
<td colspan="10">A software simulation capability shall be provided for
each external interface to <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">FSW</a>. Both
nominal and anomalous data inputs to <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">FSW</a> shall
be configurable in real-time using the procedure language of the <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">FSW</a> test
workstation.</td>
</tr>
<tr class="odd">
<td><strong>Rationale:</strong></td>
<td colspan="10">When adequate simulation capabilities aren't planned,
there is severe impact to <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">FSW</a>
development/maintenance productivity and funds.</td>
</tr>
<tr class="even">
<td><strong>Phase:</strong></td>
<td colspan="10"><strong>&lt;A A B C D E F</strong></td>
</tr>
<tr class="odd">
<td><strong>Activities:</strong></td>
<td>N/A</td>
<td colspan="2">1. Describe functional and performance capabilities for
each flight processor external interface in technical proposal.<br />
2. Include cost estimate.</td>
<td>1. Update description of required simulation capabilities to reflect
any changes in requirements since previous phase.<br />
2. Document acquisition strategy for acquiring simulation capabilities,
including responsible organizations.</td>
<td>1. Update requirements to reflect any changes since previous
phase.<br />
2. Deliver flight software external interface test tools to <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">FSW</a>
team.</td>
<td colspan="2">1. Maintain <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">FSW</a>
external interface test tools.</td>
<td colspan="2">N/A</td>
<td>N/A</td>
</tr>
<tr class="even">
<td><strong>Verification:</strong></td>
<td>N/A</td>
<td colspan="2">1. Verify by observation at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">MDR</a>.</td>
<td>1. Verify by observ. at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">SW</a> <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">SRR</a>.<br />
2. Verify flight sim. capabil. defined to accommod. test of all <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">FSW</a> data
I/O, <a href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">FSW</a>
modes, nominal &amp; anomalous conditions &amp; load/stress tests for
each flight CPU.<br />
3. Verify sim. develop. &amp; <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">FSW</a>
schedules consistent.</td>
<td>1. Verify by observation at software <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">CDR</a>.</td>
<td colspan="2">1. Verify by observation at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">MOR</a>.</td>
<td colspan="2">N/A</td>
<td>N/A</td>
</tr>
<tr class="odd">
<td colspan="3"><p><strong>Revision Status:</strong></p>
<p>Baseline</p></td>
<td colspan="6"><p><strong>Owner:</strong></p>
<p>Flight Software Branch (582)</p></td>
<td colspan="2"><strong>Reference:</strong></td>
</tr>
</tbody>
</table>

<table>
<colgroup>
<col style="width: 10%" />
<col style="width: 12%" />
<col style="width: 8%" />
<col style="width: 4%" />
<col style="width: 12%" />
<col style="width: 12%" />
<col style="width: 2%" />
<col style="width: 10%" />
<col style="width: 5%" />
<col style="width: 7%" />
<col style="width: 12%" />
</colgroup>
<tbody>
<tr class="odd">
<td><strong>3.04</strong></td>
<td colspan="6"><strong>T&amp;C System Selection Trade Study for
Operations Ground System</strong></td>
<td colspan="4"><strong>Mission Operations</strong></td>
</tr>
<tr class="even">
<td><strong>Principle:</strong></td>
<td colspan="10">An engineering trade analysis shall be performed on the
selection of the flight operations telemetry and command (T&amp;C)
system. This analysis shall define the benefits, costs, and risks
associated with each candidate system. The trade shall explicitly
address potential reuse of the <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">I&amp;T</a> <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">T&amp;C</a>
system, as well as the use of government-provided versus commercial
systems.</td>
</tr>
<tr class="odd">
<td><strong>Rationale:</strong></td>
<td colspan="10">The selection of the flight operations <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">T&amp;C</a>
system is one of the most important decisions made by the ground system
implementation team. There are several systems available that generally
could meet the ground system requirements, but each will provide its own
benefits and drawbacks. A thorough engineering trade analysis will help
ensure the best system is selected for the mission.</td>
</tr>
<tr class="even">
<td><strong>Phase:</strong></td>
<td colspan="10"><strong>&lt;A A B C D E F</strong></td>
</tr>
<tr class="odd">
<td><strong>Activities:</strong></td>
<td>1. Begin early stages of the trade study to evaluate the candidate
systems. The study should identify the factors and characteristics of
the mission that will have the greatest influence on the trade.</td>
<td colspan="2">1. Update trade study.<br />
At minimum, trade shall address potential reuse of <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">I&amp;T</a>
products in ops, approach for developing &amp; validating ops products
(e.g., procedures &amp; databases), configuration and maintenance costs,
history of candidate systems providing ops support, &amp; potential to
use ops system for <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">I&amp;T</a>.<br />
2. For in-house missions, trade study shall also assess impacts to <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">FSW</a>
develop./test &amp; <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">I&amp;T</a> if
ops <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">T&amp;C</a>
sys. different than default <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">FSW</a> &amp;
<a href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">I&amp;T</a>
system.</td>
<td>1. Complete the trade study.<br />
2. Make a decision on operations <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">T&amp;C</a>
system. This is needed to provide a reference architecture within which
ground system requirements are defined and cost estimates are
solidified.</td>
<td>N/A</td>
<td colspan="2">N/A</td>
<td colspan="2">N/A</td>
<td>N/A</td>
</tr>
<tr class="even">
<td><strong>Verification:</strong></td>
<td>1. Verify at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">MCR</a> that
trade is adequate.</td>
<td colspan="2">1.Verify at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">MDR</a> that
trade addresses above and other appropriate items.</td>
<td>1. Verify at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">PDR</a> that
the trade study is completed and demonstrates a thorough analysis that
justifies the decision .</td>
<td>N/A</td>
<td colspan="2">N/A</td>
<td colspan="2">N/A</td>
<td>N/A</td>
</tr>
<tr class="odd">
<td colspan="3"><p><strong>Revision Status:</strong></p>
<p>Baseline</p></td>
<td colspan="6"><p><strong>Owner:</strong></p>
<p>Systems Integration and Engineering Branch (581)</p></td>
<td colspan="2"><strong>Reference:</strong></td>
</tr>
</tbody>
</table>

<table>
<colgroup>
<col style="width: 10%" />
<col style="width: 12%" />
<col style="width: 8%" />
<col style="width: 4%" />
<col style="width: 12%" />
<col style="width: 12%" />
<col style="width: 2%" />
<col style="width: 10%" />
<col style="width: 5%" />
<col style="width: 7%" />
<col style="width: 12%" />
</colgroup>
<tbody>
<tr class="odd">
<td><strong>3.05</strong></td>
<td colspan="6"><strong>Flight / Ground System Test
Capabilities</strong></td>
<td colspan="4"><strong>Ground System; Mission Operations</strong></td>
</tr>
<tr class="even">
<td><strong>Principle:</strong></td>
<td colspan="10">Flight system interface and functional capabilities
shall be provided to support ground system development and test, and
flight operations development, test and training. These capabilities
shall be provided via a combination of one or more spacecraft simulators
and the actual spacecraft. The spacecraft capabilities, access time, and
schedule required to support ground system/operations development and
test shall be defined by and negotiated with the ground system and
operations teams.</td>
</tr>
<tr class="odd">
<td><strong>Rationale:</strong></td>
<td colspan="10">The ground system must be compatible with the <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">S/C</a> it is
being designed to support, and this must be proven prior to launch via
tests. Similarly, the ops team must be able to develop and validate a
variety of operations products, such as procedures, databases, display
pages, and launch scripts. The ops team must also have opportunities to
learn about operating the <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">S/C</a> and
prove this knowledge has been acquired prior to launch.</td>
</tr>
<tr class="even">
<td><strong>Phase:</strong></td>
<td colspan="10"><strong>&lt;A A B C D E F</strong></td>
</tr>
<tr class="odd">
<td><strong>Activities:</strong></td>
<td>1. Develop plans for providing the flight system interfaces for use
by the ground sytsem and flight operations teams.</td>
<td colspan="2">1. Develop preliminary simulation concepts.</td>
<td>1. Generate preliminary simulator requirements and identify long
lead procurement items.<br />
2. Incorporate the agreements on simulator and spacecraft access time
into the <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">I&amp;T</a>
schedule.</td>
<td>1. Complete simulator requirements, design, and delivery
plan/schedules.<br />
2. Ensure simulator and spacecraft access times are integrated into the
detailed <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">I&amp;T</a>
schedule.</td>
<td colspan="2">1. Provide simulator and <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">S/C</a>
hardware access for both ground system verification and validation, and
for ops teams to prepare for launch.<br />
2. Ensure <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">S/C</a> and
instrument design changes are accommodated by simulator updates as
appropriate.<br />
3. Ensure plan &amp; budget are in place to maintain simulators post-
launch.</td>
<td colspan="2">N/A</td>
<td>N/A</td>
</tr>
<tr class="even">
<td><strong>Verification:</strong></td>
<td>1. Verify at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">MCR</a>.</td>
<td colspan="2">1. Verify at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">MDR</a>.</td>
<td>1. Verify at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">PDR</a>.</td>
<td>1. Verify at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">CDR</a>.</td>
<td colspan="2">1. Verify at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">MOR</a> that
plan for simulator use is described.<br />
2. Verify at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">FOR</a> that
plan and schedule for simulator maintenance is in place.</td>
<td colspan="2">N/A</td>
<td>N/A</td>
</tr>
<tr class="odd">
<td colspan="3"><p><strong>Revision Status:</strong></p>
<p>Baseline</p></td>
<td colspan="6"><p><strong>Owner:</strong></p>
<p>Systems Integration and Engineering Branch (581)</p></td>
<td colspan="2"><strong>Reference:</strong></td>
</tr>
</tbody>
</table>

<table>
<colgroup>
<col style="width: 10%" />
<col style="width: 12%" />
<col style="width: 8%" />
<col style="width: 4%" />
<col style="width: 12%" />
<col style="width: 12%" />
<col style="width: 2%" />
<col style="width: 10%" />
<col style="width: 5%" />
<col style="width: 7%" />
<col style="width: 12%" />
</colgroup>
<tbody>
<tr class="odd">
<td><strong>3.06</strong></td>
<td colspan="6"><strong>Dedicated ETU for Flight Software (FSW)
Testing</strong></td>
<td colspan="4"><strong>Software</strong></td>
</tr>
<tr class="even">
<td><strong>Principle:</strong></td>
<td colspan="10">An <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">ETU</a> flight
data system testbed shall be dedicated to <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">FSW</a> teams
specifically for <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">FSW</a>
development and test. Such ETUs are supplemented by external interface
simulators as specified in Rule 3.03. Hardware and <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">I&amp;T</a>
teams shall not plan to use the <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">FSW</a> ETUs
for their critical path schedule. The number of flight data system
testbed units shall be sufficient to support the <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">FSW</a>
development schedule and the overall mission schedule.</td>
</tr>
<tr class="odd">
<td><strong>Rationale:</strong></td>
<td colspan="10">Early investment in dedicated <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">FSW</a> testbed
hardware fidelity saves costs and avoids significant schedule risks to
<a href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">FSW</a> and
<a href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">I&amp;T</a>
teams. Anything less than a dedicated <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">ETU</a> will
add to mission risk and threaten cost/schedule.</td>
</tr>
<tr class="even">
<td><strong>Phase:</strong></td>
<td colspan="10"><strong>&lt;A A B C D E F</strong></td>
</tr>
<tr class="odd">
<td><strong>Activities:</strong></td>
<td>N/A</td>
<td colspan="2">1. Define high-level <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">ETU</a>
requirements for <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">FSW</a> with
clear and detailed rationale.</td>
<td>1. Update <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">ETU</a>
requirements from Phase A.<br />
2. <a href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">FSW</a>
team ensure that <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">ETU</a>
development and delivery schedule is consistent with <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">FSW</a>
development team need dates.<br />
3. <a href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">FSW</a>
team develop <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">ETU</a>
acceptance criteria for <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">ETU</a>
deliveries.</td>
<td>1. Review <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">ETU</a>
design.<br />
2. Review <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">ETU</a>
delivery schedule.</td>
<td colspan="2">1. <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">FSW</a> team
verify availability of ETUs to meet <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">FSW</a>
development and test schedules.<br />
2. <a href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">FSW</a>
team lead accept <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">ETU</a>
deliveries and verify functionality.</td>
<td colspan="2">1. <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">FSW</a> team
review and provide inputs on <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">ETU</a>
maintenance plan.</td>
<td>N/A</td>
</tr>
<tr class="even">
<td><strong>Verification:</strong></td>
<td>N/A</td>
<td colspan="2">1. Verify by observation at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">MDR</a> that <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">ETU</a> quality
<a href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">FSW</a> test
beds are clearly represented in the technical proposal, and that costs
for dedicated <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">FSW</a> testbed
ETUs are included in the electronics cost proposal.</td>
<td>1. Verify by observ. at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">SDR</a> &amp;
<a href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">SW</a> <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">SRR</a>
that<br />
a) <a href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">FSW</a>
<a href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">ETU</a>
testbed(s) represent maturing flight architecture;<br />
b) min. 1 test bed w/ full <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">ETU</a>
fidelity costed &amp; deliv. sched. consis. w/ <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">FSW</a>
needs;<br />
c) <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">I&amp;T</a>
plans minimize shar-ing <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">ETU</a>, or
dedicated <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">ETU</a>
provided.</td>
<td>1. Verify by observation at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">SW</a> <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">PDR</a>
that<br />
a) deliv. plans for ETU-quality <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">FSW</a>
testbed(s) consistent w/ <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">FSW</a>
develop. needs;<br />
b) <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">I&amp;T</a>
plans require minimal use of a shared <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">ETU</a>, or <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">I&amp;T</a>
have own dedicated <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">ETU</a>.</td>
<td colspan="2">1. Verify by observ. at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">SW</a> <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">CDR</a>
that<br />
a) ETU-quality <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">FSW</a>
testbed(s) have been delivered to <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">FSW</a>
team;<br />
b) <a href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">ETU</a>
<a href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">FSW</a>
testbed confirmed adequate by <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">FSW</a> staff
for on-orbit maintenance and ops support.</td>
<td colspan="2">1. Verify by observ. at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">FOR</a>
that<br />
a) <a href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">FSW</a>
<a href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">ETU</a>
testbeds have been moved to their long-term environ. for <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">FSW</a> maint.
&amp; ops support;<br />
b) Sys. Admins, facility and hardware support are in place.</td>
<td>N/A</td>
</tr>
<tr class="odd">
<td colspan="3"><p><strong>Revision Status:</strong></p>
<p>Baseline</p></td>
<td colspan="6"><p><strong>Owner:</strong></p>
<p>Flight Software Branch (582)</p></td>
<td colspan="2"><strong>Reference:</strong></td>
</tr>
</tbody>
</table>

<table>
<colgroup>
<col style="width: 10%" />
<col style="width: 12%" />
<col style="width: 8%" />
<col style="width: 4%" />
<col style="width: 12%" />
<col style="width: 12%" />
<col style="width: 2%" />
<col style="width: 10%" />
<col style="width: 5%" />
<col style="width: 7%" />
<col style="width: 12%" />
</colgroup>
<tbody>
<tr class="odd">
<td><strong>3.07</strong></td>
<td colspan="6"><strong>Flight Software Margins</strong></td>
<td colspan="4"><strong>Software</strong></td>
</tr>
<tr class="even">
<td><strong>Principle:</strong></td>
<td colspan="10">Flight software resource margins shall be maintained in
accordance with <a
href="javascript:openPictureWindow(&#39;getimage.php?i_id=2&#39;, 596, 740);">Table
3.07-1</a> and presented at Key Decision Point (KDP) milestone
reviews.</td>
</tr>
<tr class="odd">
<td><strong>Rationale:</strong></td>
<td colspan="10">Early and repeated attention by flight software teams
to resource utilization will improve resource margins for future phases
of the mission.</td>
</tr>
<tr class="even">
<td><strong>Phase:</strong></td>
<td colspan="10"><strong>&lt;A A B C D E F</strong></td>
</tr>
<tr class="odd">
<td><strong>Activities:</strong></td>
<td>N/A</td>
<td colspan="2">1. Establish clear rationale for <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">FSW</a>
resource estimates using the proposed hardware.</td>
<td>1. Update software margins based on updated requirements.<br />
2. Coordinate with <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">S/C</a> and
instrument procurement and hardware development teams to ensure margins
can be maintained.</td>
<td>1. Design <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">FSW</a> within
defined design margins.<br />
2. Continue coordination with <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">S/C</a> and
instrument hardware development teams.</td>
<td colspan="2">1. Track development to design margins.<br />
2. Report systems not able to maintain margins.<br />
3. Provide mitigation plans or work-arounds for margins that are not
being maintained.</td>
<td colspan="2">N/A</td>
<td>N/A</td>
</tr>
<tr class="even">
<td><strong>Verification:</strong></td>
<td>N/A</td>
<td colspan="2">1. Verify by observation at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">MDR</a>.</td>
<td>1. Verify by observation at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">SDR</a> and <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">FSW</a> <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">SRR</a>.</td>
<td>1. Verify by observation at Mission <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">CDR</a> and <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">FSW</a> <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">PDR</a>.</td>
<td colspan="2">1. Verify by observation at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">FSW</a> <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">CDR</a> and <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">PER</a>.</td>
<td colspan="2">N/A</td>
<td>N/A</td>
</tr>
<tr class="odd">
<td colspan="3"><p><strong>Revision Status:</strong></p>
<p>Baseline; Updated: Rev D</p></td>
<td colspan="6"><p><strong>Owner:</strong></p>
<p>Flight Software Branch (582)</p></td>
<td colspan="2"><strong>Reference:</strong></td>
</tr>
</tbody>
</table>

**Table 3.07-1 Resource Margins for Flight Software Development**

The numbers in the table below are margins for different mission phases
and maturity levels. These do not represent hard limits, but levels
where the software development team should start to get concerned.

Margin is calculated using the formula: (available resource -- estimated
usage of resource) / available resource.

  -------------------- ------------ ------------ ------------ -----------------
  **Mission Phase**    **FSW SRR**  **FSW PDR**  **FSW CDR**  **Ship/Flight**

  Method               Estimate     Analysis     Analysis/    Measured
                                                 Measured     

  Average CPU Usage    50%          50%          40%          30%

  CPU Deadlines        50%          50%          40%          30%

  PROM                 50%          30%          20%          0%

  EEPROM               50%          50%          40%          30%

  RAM                  50%          50%          40%          30%

  PCI Bus              75%          70%          60%          50%

  1553 Bus             30%          25%          20%          10%

  Spacewire (1355)     TBD          TBD          TBD          TBD

  UART/Serial I/F      50%          50%          40%          30%
  -------------------- ------------ ------------ ------------ -----------------

**3.07-1 Flight Software Margin Table**

Selecting which column to use at a particular time is not always
obvious. Generally, one should pay more attention to the "Method" row
than the "Mission Phase" row. For example, if there is a lot of re-use
and you have actual measured code sizes for most modules, your PROM
could be 80% full at PDR without causing concern. Different resource
elements can be at different maturity levels at any given point in a
project. The right-most column should only be used when the code is
fully integrated [and tested]{.underline}. Those are the margins we want
to save for in-flight maintenance.

Average CPU Utilization: This should be estimated/measured over about a
five second interval under the worst-case normal operating conditions.
The numbers represent the percentage of time the CPU is doing
non-background processing work. Background processing may include tasks
such as memory scrubbing or table check summing if those tasks have very
loose timing requirements.

Deadlines: This is the fine-scale companion to the row above. This row
usually represents the interrupt timing requirements of the system. For
example: How quickly does the processor need to re-fill that FIFO after
the HW interrupt is asserted? If you have a 50ms deadline for an ISR and
you estimate the processor can meet it in 20ms, your usage (margin) is
40%(150%). If that same ISR occurs twice per second, it would only add
4% to the CPU usage calculation. All deadlines in the system should be
considered, and compared individually to the recommended margin. Also,
consider which deadlines can occur simultaneously to calculate the
worst-case timing. (Q: should there be different recommended numbers for
the worst case timing?)

PROM is non-volatile memory that cannot be modified in flight.

EEPROM is non-volatile memory that can be modified in flight.

RAM is volatile memory where the executing code and data are stored.
This memory is always on the processor's local bus.

Note: Bulk memory used for storage of housekeeping and science data has
been removed from this table. The amount of bulk memory is driven more
by mission parameters (data rates, number of ground contacts, etc) than
software design. So, systems engineers should track the bulk memory
margin. However, some systems have the "bulk" memory on the processor
card, indistinguishable from regular RAM. In this case, the software
team should track margins on this combined RAM/bulk memory space.

1553 Bus: Usage calculations should include 1 retry for each
transaction, unless mission requirements specify otherwise. If the
scheduling of bus traffic is segmented into slots or channels, the usage
should be calculated based on the number of slots used (rather than
actual bus time).

Spacewire: Under development.

Other Data Busses: For busses and interfaces not listed, try to select
the one that is closest in behavior among the listed busses. If none is
even close, work with your systems engineer to define acceptable margins
for that unique bus. Then, we can add that new bus to the table.

<table>
<colgroup>
<col style="width: 10%" />
<col style="width: 12%" />
<col style="width: 8%" />
<col style="width: 4%" />
<col style="width: 12%" />
<col style="width: 12%" />
<col style="width: 2%" />
<col style="width: 10%" />
<col style="width: 5%" />
<col style="width: 7%" />
<col style="width: 12%" />
</colgroup>
<tbody>
<tr class="odd">
<td><strong>3.09</strong></td>
<td colspan="6"><strong>Software Development Approach</strong></td>
<td colspan="4"><strong>Software</strong></td>
</tr>
<tr class="even">
<td><strong>Principle:</strong></td>
<td colspan="10">Acquisition and development of software shall be
performed in accordance with the requirements of <a
href="http://nodis3.gsfc.nasa.gov/displayDir.cfm?Internal_ID=N_PR_7150_0002_&amp;page_name=main">NPR
7150.2</a>. GSFC in-house developments shall use practices documented in
GSFC GPR-8700.5 and reflected at the software.gsfc.nasa.gov website. Out
of house development efforts shall be assessed against these same
criteria during an independent software peer review which shall include
peers fully familiar with the requirements of GSFC GPR-8700.5 and the
software.gsfc.nasa.gov website.</td>
</tr>
<tr class="odd">
<td><strong>Rationale:</strong></td>
<td colspan="10">External organizations will often apply pressure to
software teams to abandon good engineering practices to reduce costs
and/or improve schedule. However, the consistent application of sound
and proven discipline engineering practices throughout the life cycle
greatly facilitates meeting cost, schedule and quality expectations
while managing risk. Sound discipline practices provide the best
assurance of developing the right products on schedule and within
costs.</td>
</tr>
<tr class="even">
<td><strong>Phase:</strong></td>
<td colspan="10"><strong>&lt;A A B C D E F</strong></td>
</tr>
<tr class="odd">
<td><strong>Activities:</strong></td>
<td>1. Review <a
href="http://nodis3.gsfc.nasa.gov/displayDir.cfm?Internal_ID=N_PR_7150_0002_&amp;page_name=main">NPR
7150.2</a> and <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">GPR</a>
referenced above.<br />
2. Scope software plans.</td>
<td colspan="2">1. Develop and execute software acquisition
strategy.<br />
2. Classify software products based on mission criticality.<br />
3. Develop software contents of RFPs and proposals.<br />
4. Draft software cost estimates.</td>
<td>1. Develop Software Management Plan, <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">CM</a> Plan,
Test Plan and Software Requirements as described in <a
href="http://nodis3.gsfc.nasa.gov/displayDir.cfm?Internal_ID=N_PR_7150_0002_&amp;page_name=main">NPR
7150.2</a> and at above website.<br />
2. Complete compliance matrix for <a
href="http://nodis3.gsfc.nasa.gov/displayDir.cfm?Internal_ID=N_PR_7150_0002_&amp;page_name=main">NPR
7150.2</a>.</td>
<td>1. Document software development and test plans and adhere to the
documented plans and practices.<br />
2. Set up software test environment.</td>
<td colspan="2">1. Software development, test and deliveries adhere to
the documented Plans and practices.<br />
2. Software Maintenance Plan is developed to be consistent with the
above website.</td>
<td colspan="2">1. Software maintenance and test adhere to the
documented plan and practices.</td>
<td>N/A</td>
</tr>
<tr class="even">
<td><strong>Verification:</strong></td>
<td>1. Verify by observation at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">MCR</a> that
new business plans reflect the intent to follow the above standard.</td>
<td colspan="2">1. Verify by observation at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">MDR</a>
that<br />
a) <a href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">SW</a>
plans are consistent with formulation and applicable requirements in <a
href="http://nodis3.gsfc.nasa.gov/displayDir.cfm?Internal_ID=N_PR_7150_0002_&amp;page_name=main">NPR
7150.2</a>.<br />
2. Perform "Quick Look Review" of the proposed software plan.</td>
<td>1. Verify by observation at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">SW</a> <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">SRR</a>
that<br />
a) <a href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">SW</a>
Plans and requirements documentation are consistent with <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">GPR</a> and
NPR;<br />
b) any waiver requests have been thoroughly evaluated.</td>
<td>1. Verify by observation at Mission <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">CDR</a> and
Software <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">PDR</a>.</td>
<td colspan="2">1. Verify by observation at Software <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">CDR</a> and
Mission <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">FOR</a>.</td>
<td colspan="2">N/A</td>
<td>N/A</td>
</tr>
<tr class="odd">
<td colspan="3"><p><strong>Revision Status:</strong></p>
<p>Baseline</p></td>
<td colspan="6"><p><strong>Owner:</strong></p>
<p>Flight Software Branch (582)</p></td>
<td colspan="2"><p><strong>Reference:</strong></p>
<p>http://software.gsfc.nasa.gov</p></td>
</tr>
</tbody>
</table>

<table>
<colgroup>
<col style="width: 10%" />
<col style="width: 12%" />
<col style="width: 8%" />
<col style="width: 4%" />
<col style="width: 12%" />
<col style="width: 12%" />
<col style="width: 2%" />
<col style="width: 10%" />
<col style="width: 5%" />
<col style="width: 7%" />
<col style="width: 12%" />
</colgroup>
<tbody>
<tr class="odd">
<td><strong>3.10</strong></td>
<td colspan="6"><strong>Flight Operations Preparations and Team
Development</strong></td>
<td colspan="4"><strong>Mission Operations; Software;
Systems</strong></td>
</tr>
<tr class="even">
<td><strong>Principle:</strong></td>
<td colspan="10">Mission preparation tests shall require a minimum of 2
successful end-to-end tests (to include launch and early orbit
simulations), and 2 day-in-the-life simulations, and a minimum of 200
hours with the flight ops team running the flight system. Flight
operators shall participate as test conductors during integration and
test (I&amp;T) at a minimum as specified in the tests above.</td>
</tr>
<tr class="odd">
<td><strong>Rationale:</strong></td>
<td colspan="10">Using flight operators as test conductors gives them a
great deal of real, hands-on experience with the observatory prior to
launch without requiring as much time dedicated to FOT training and
simulations during operations. Involving the FOT early in the mission
helps ensure that the mission design will be considerate of operational
requirements and practicalities, and will allow the FOT to become
intimately familiar with the mission design, including design
rationale.</td>
</tr>
<tr class="even">
<td><strong>Phase:</strong></td>
<td colspan="10"><strong>&lt;A A B C D E F</strong></td>
</tr>
<tr class="odd">
<td><strong>Activities:</strong></td>
<td>1. Assess the flight operations team's role throughout the mission
lifecycle. Flight operations experts review the operations concept.</td>
<td colspan="2">1. Flight operations and software experts support the
development of operations concepts and flight/ground architecture.<br />
2. Update mission design estimates.</td>
<td>1. Identify candidate FOT members.<br />
2. Review and update operations concepts and identify details on
approach to operations team support.<br />
3. Conduct peer review flight/ground architecture for soundness.</td>
<td>1. Involve FOT in test plan development. Support the completion of
the operations concept.</td>
<td colspan="2">1. Ensure all FOT members are assigned as test
conductors during <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">I&amp;T</a>.<br />
2. Ensure all FOT members gain knowledge &amp; experience on ground
systems during <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">I&amp;T</a>.<br />
3. Prior to launch, require a min of 2 successful end-to-end tests (to
include launch &amp; early orbit sims) and 2 day-in-the-life sims, and a
min of 200 hrs w/ flight ops team running flight sys<br />
4. Complete flight ops plan.</td>
<td colspan="2">N/A</td>
<td>N/A</td>
</tr>
<tr class="even">
<td><strong>Verification:</strong></td>
<td>1. Verify at MCR:<br />
a) Ensure flight development experts were consulted during mission
formulation.<br />
b) Ensure that operations concept covers flight ops team's role during
entire mission lifecycle.</td>
<td colspan="2">1. Verify at MDR:<br />
a) Flight operations concepts are sound.<br />
b) Inquire about project coordination with the flight software
organization.</td>
<td>1. Verify at PDR:<br />
a) Flight operations personnel are identified.<br />
2b Flight and ground system interfaces are well defined.</td>
<td>1. Verify at CDR:<br />
a) Flight ops experts have been consulted on the overall system
design<br />
b) FOT will provide test conductors during <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">I&amp;T</a>.<br />
c) The project has completed full mission life cycle design.</td>
<td colspan="2">1. Verify at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">MOR</a> and
FOR:<br />
a) Members of FOT are serving as test conductors during <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">I&amp;T</a>.<br />
b) Test items above were completed at MRR.</td>
<td colspan="2">N/A</td>
<td>N/A</td>
</tr>
<tr class="odd">
<td colspan="3"><p><strong>Revision Status:</strong></p>
<p>Baseline</p></td>
<td colspan="6"><p><strong>Owner:</strong></p>
<p>Systems Integration and Engineering Branch (581)</p></td>
<td colspan="2"><strong>Reference:</strong></td>
</tr>
</tbody>
</table>

<table>
<colgroup>
<col style="width: 10%" />
<col style="width: 12%" />
<col style="width: 8%" />
<col style="width: 4%" />
<col style="width: 12%" />
<col style="width: 12%" />
<col style="width: 4%" />
<col style="width: 8%" />
<col style="width: 5%" />
<col style="width: 7%" />
<col style="width: 12%" />
</colgroup>
<tbody>
<tr class="odd">
<td><strong>3.11</strong></td>
<td colspan="6"><strong>Long Duration And Failure Free System Level Test
of Flight Software</strong></td>
<td colspan="4"><strong>Software</strong></td>
</tr>
<tr class="even">
<td><strong>Principle:</strong></td>
<td colspan="10">Ground test of the fully integrated <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">FSW</a> system
shall include demonstration of error free operations-like scenarios over
an extended time period. The minimum duration uninterrupted <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">FSW</a>
system-level test (on the highest fidelity <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">FSW</a>
testbed) is 72 hours for Class A and B, 48 hours for Class C, and 36
hours for Class D missions, respectively.</td>
</tr>
<tr class="odd">
<td><strong>Rationale:</strong></td>
<td colspan="10">Frequent restart of <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">FSW</a> during
ground tests may mask problems which will only occur following extended
execution of the <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">FSW</a>.</td>
</tr>
<tr class="even">
<td><strong>Phase:</strong></td>
<td colspan="10"><strong>&lt;A A B C D E F</strong></td>
</tr>
<tr class="odd">
<td><strong>Activities:</strong></td>
<td>N/A</td>
<td colspan="2">N/A</td>
<td>N/A</td>
<td>1. Develop <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">FSW</a> Test
Plan.</td>
<td colspan="2">1. Complete and execute <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">FSW</a> Test
Plan, to include long duration <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">FSW</a>
testing.</td>
<td colspan="2">N/A</td>
<td>N/A</td>
</tr>
<tr class="even">
<td><strong>Verification:</strong></td>
<td>N/A</td>
<td colspan="2">N/A</td>
<td>N/A</td>
<td>1. Verify at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">PDR</a> that <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">FSW</a> Test
Plan is baselined and that it includes long duration testing.</td>
<td colspan="2">1. Verify at MOR:<br />
a) The longest duration, uninterrupted <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">FSW</a>
system-level test (on the highest fidelity <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">FSW</a>
testbed) has been completed.<br />
b) Verify that long duration tests were minimally between 36 and 72
hrs.<br />
c) Verify that realistic post-launch science operations and safe-hold
operations were represented by the long duration test(s).</td>
<td colspan="2">N/A</td>
<td>N/A</td>
</tr>
<tr class="odd">
<td colspan="3"><p><strong>Revision Status:</strong></p>
<p>Revision B</p></td>
<td colspan="6"><p><strong>Owner:</strong></p>
<p>Flight Software Branch (582)</p></td>
<td colspan="2"><strong>Reference:</strong></td>
</tr>
</tbody>
</table>

<table>
<colgroup>
<col style="width: 10%" />
<col style="width: 12%" />
<col style="width: 8%" />
<col style="width: 4%" />
<col style="width: 12%" />
<col style="width: 12%" />
<col style="width: 2%" />
<col style="width: 10%" />
<col style="width: 5%" />
<col style="width: 7%" />
<col style="width: 12%" />
</colgroup>
<tbody>
<tr class="odd">
<td><strong>3.12</strong></td>
<td colspan="6"><strong>Visibility of Spacecraft State</strong></td>
<td colspan="4"><strong>Software</strong></td>
</tr>
<tr class="even">
<td><strong>Principle:</strong></td>
<td colspan="10">Onboard telemetry and downlink priorities shall be
defined to unambiguously report the state of the spacecraft and
instruments to underground operators early in each ground tracking pass
- specifically identifying any faults experienced.</td>
</tr>
<tr class="odd">
<td><strong>Rationale:</strong></td>
<td colspan="10">Immediate ground attention to anomalous spacecraft
status at the start of a ground contact provides the greatest
opportunity for ground reaction, if necessary, during this same ground
pass.</td>
</tr>
<tr class="even">
<td><strong>Phase:</strong></td>
<td colspan="10"><strong>&lt;A A B C D E F</strong></td>
</tr>
<tr class="odd">
<td><strong>Activities:</strong></td>
<td>N/A</td>
<td colspan="2">N/A</td>
<td>1. Develop requirements and operations concept.<br />
2. Complete preliminary design.</td>
<td>1. Update requirements and operations concept.<br />
2. Update design.</td>
<td colspan="2">1. Define on-board events and telemetry.<br />
2. Establish priorities for downlink of onboard data.<br />
3. Test and verify implementation.</td>
<td colspan="2">N/A</td>
<td>N/A</td>
</tr>
<tr class="even">
<td><strong>Verification:</strong></td>
<td>N/A</td>
<td colspan="2">N/A</td>
<td>1. At PDR:<br />
a) Verify overall s/c &amp; instrument states of health; characteristics
of critical onboard anomalies are the first downlink of each ground
contact during all mission phases and anomalous conditions.<br />
b) Verify same during minimum telemetry bandwidth conditions.</td>
<td>1. At CDR:<br />
a) Verify overall s/c &amp; instrument states of health; characteristics
of critical onboard anomalies are the first downlink of each ground
contact during all mission phases and anomalous conditions.<br />
b) Verify same during minimum telemetry bandwidth conditions.</td>
<td colspan="2">1. Verify above items at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">FOR</a>.<br />
2. Verify at MOR:<br />
1a) Overall s/c &amp; instrument states of health; characteristics of
critical onboard anomalies are the first downlink of each ground contact
during all mission phases and anomalous conditions.<br />
b) Verify same during minimum telemetry bandwidth conditions.</td>
<td colspan="2">N/A</td>
<td>N/A</td>
</tr>
<tr class="odd">
<td colspan="3"><p><strong>Revision Status:</strong></p>
<p>Revision B</p></td>
<td colspan="6"><p><strong>Owner:</strong></p>
<p>Flight Software Branch (582)</p></td>
<td colspan="2"><strong>Reference:</strong></td>
</tr>
</tbody>
</table>

<table>
<colgroup>
<col style="width: 10%" />
<col style="width: 12%" />
<col style="width: 8%" />
<col style="width: 4%" />
<col style="width: 12%" />
<col style="width: 12%" />
<col style="width: 2%" />
<col style="width: 10%" />
<col style="width: 5%" />
<col style="width: 7%" />
<col style="width: 12%" />
</colgroup>
<tbody>
<tr class="odd">
<td><strong>3.13</strong></td>
<td colspan="6"><strong>Operational Software Redundant
Element</strong></td>
<td colspan="4"><strong>Software</strong></td>
</tr>
<tr class="even">
<td><strong>Principle:</strong></td>
<td colspan="10">The updating of code/software should be limited to a
single target memory device under user ground control and monitoring.
Under no circumstances shall prime and redundant memories be modified
concurrently, or before the operational performance of the change is
properly assured in a single unit.</td>
</tr>
<tr class="odd">
<td><strong>Rationale:</strong></td>
<td colspan="10">Prevents inadvertent updates of the backup element from
the primary element. Ensures that the ground system can update each
element without dependence on any of the other elements.</td>
</tr>
<tr class="even">
<td><strong>Phase:</strong></td>
<td colspan="10"><strong>&lt;A A B C D E F</strong></td>
</tr>
<tr class="odd">
<td><strong>Activities:</strong></td>
<td>N/A</td>
<td colspan="2">N/A</td>
<td>N/A</td>
<td>1. Ensure system level design does not allow modification of
software between one CPU and its redundant elements.</td>
<td colspan="2">N/A</td>
<td colspan="2">N/A</td>
<td>N/A</td>
</tr>
<tr class="even">
<td><strong>Verification:</strong></td>
<td>N/A</td>
<td colspan="2">N/A</td>
<td>N/A</td>
<td>1. Verify at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">CDR</a>.</td>
<td colspan="2">N/A</td>
<td colspan="2">N/A</td>
<td>N/A</td>
</tr>
<tr class="odd">
<td colspan="3"><p><strong>Revision Status:</strong></p>
<p>Revision B</p></td>
<td colspan="6"><p><strong>Owner:</strong></p>
<p>Real-Time Software Engineering Branch (584)</p></td>
<td colspan="2"><strong>Reference:</strong></td>
</tr>
</tbody>
</table>

<table>
<colgroup>
<col style="width: 10%" />
<col style="width: 12%" />
<col style="width: 8%" />
<col style="width: 4%" />
<col style="width: 12%" />
<col style="width: 12%" />
<col style="width: 2%" />
<col style="width: 10%" />
<col style="width: 5%" />
<col style="width: 7%" />
<col style="width: 12%" />
</colgroup>
<tbody>
<tr class="odd">
<td><strong>3.14</strong></td>
<td colspan="6"><strong>Command Procedure Changes</strong></td>
<td colspan="4"><strong>Software</strong></td>
</tr>
<tr class="even">
<td><strong>Principle:</strong></td>
<td colspan="10">Command procedures and mission databases (on-board and
ground) shall be controlled (treated with the same rigor as changes to
flight critical software). This includes formal configuration
management, peer review by knowledgeable technical personnel, and full
verification with up-to-date simulations wherever possible. (Routine
loads to perform nominal operations may require less test rigor.)</td>
</tr>
<tr class="odd">
<td><strong>Rationale:</strong></td>
<td colspan="10">Changes in command procedures and critical database
areas that are not tracked, controlled, and fully tested can cause loss
of science and/or the mission.</td>
</tr>
<tr class="even">
<td><strong>Phase:</strong></td>
<td colspan="10"><strong>&lt;A A B C D E F</strong></td>
</tr>
<tr class="odd">
<td><strong>Activities:</strong></td>
<td>N/A</td>
<td colspan="2">N/A</td>
<td>1. Ensure draft <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">CM</a> Plans
address items defined in this rule.</td>
<td>1. Ensure that the final <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">CM</a> and Test
Plans address the items defined in this rule.<br />
2. Ensure that the Ops Plan and Sustaining Eng Plan address the items
defined in this rule.</td>
<td colspan="2">1. Perform routine maintenance.</td>
<td colspan="2">N/A</td>
<td>N/A</td>
</tr>
<tr class="even">
<td><strong>Verification:</strong></td>
<td>N/A</td>
<td colspan="2">N/A</td>
<td>1. Verify at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">CDR</a>.</td>
<td>1. Verify at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">CDR</a>.</td>
<td colspan="2">N/A</td>
<td colspan="2">N/A</td>
<td>N/A</td>
</tr>
<tr class="odd">
<td colspan="3"><p><strong>Revision Status:</strong></p>
<p>Revision B</p></td>
<td colspan="6"><p><strong>Owner:</strong></p>
<p>Real-Time Software Engineering Branch (584)</p></td>
<td colspan="2"><strong>Reference:</strong></td>
</tr>
</tbody>
</table>

<table style="width:100%;">
<colgroup>
<col style="width: 10%" />
<col style="width: 12%" />
<col style="width: 8%" />
<col style="width: 4%" />
<col style="width: 12%" />
<col style="width: 12%" />
<col style="width: 2%" />
<col style="width: 10%" />
<col style="width: 7%" />
<col style="width: 5%" />
<col style="width: 12%" />
</colgroup>
<tbody>
<tr class="odd">
<td><strong>3.15</strong></td>
<td colspan="6"><strong>Test and GSE Software Interfaces</strong></td>
<td colspan="4"><strong>Flight Systems I&amp;T, Software</strong></td>
</tr>
<tr class="even">
<td><strong>Principle:</strong></td>
<td colspan="10">Test and <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">GSE</a> (Ground
Support Equipment) software that interfaces with or evaluates flight
software and hardware shall be acceptance tested before testing with <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">FSW</a> and
flight hardware.</td>
</tr>
<tr class="odd">
<td><strong>Rationale:</strong></td>
<td colspan="10">Test and <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">GSE</a>
software are used to test critical flight software and hardware and, in
doing so, may cause damage to flight hardware if not developed and
tested in a rigorous manner.</td>
</tr>
<tr class="even">
<td><strong>Phase:</strong></td>
<td colspan="10"><strong>&lt;A A B C D E F</strong></td>
</tr>
<tr class="odd">
<td><strong>Activities:</strong></td>
<td>N/A</td>
<td colspan="2">N/A</td>
<td>1. Identify test and <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">GSE</a>
software functions needed for <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">GSE</a> and
flight software testing.<br />
2. Ensure software development costs/schedule include critical testing
of test and <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">GSE</a>
software.</td>
<td>1. Ensure that the final <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">CM</a> and Test
Plans address the items defined in this rule.<br />
2. Ensure that the Ops Plan and Sustaining Eng Plan address the items
defined in this rule.</td>
<td colspan="2">1. Perform routine maintenance.</td>
<td colspan="2">N/A</td>
<td>N/A</td>
</tr>
<tr class="even">
<td><strong>Verification:</strong></td>
<td>N/A</td>
<td colspan="2">N/A</td>
<td>1. Verify at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">PDR</a>.</td>
<td>1. Verify at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">CDR</a>.</td>
<td colspan="2">1. Verify at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">FSW</a> <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">CDR</a>.</td>
<td colspan="2">N/A</td>
<td>N/A</td>
</tr>
<tr class="odd">
<td colspan="3"><p><strong>Revision Status:</strong></p>
<p>Revision B</p></td>
<td colspan="6"><p><strong>Owner:</strong></p>
<p>Flight Systems Integration and Test (568); Real-Time Software
Engineering (584)</p></td>
<td colspan="2"><strong>Reference:</strong></td>
</tr>
</tbody>
</table>

<table>
<colgroup>
<col style="width: 10%" />
<col style="width: 12%" />
<col style="width: 8%" />
<col style="width: 4%" />
<col style="width: 12%" />
<col style="width: 12%" />
<col style="width: 2%" />
<col style="width: 10%" />
<col style="width: 5%" />
<col style="width: 7%" />
<col style="width: 12%" />
</colgroup>
<tbody>
<tr class="odd">
<td><strong>4.01</strong></td>
<td colspan="6"><strong>Contamination Control, Planning, and
Execution</strong></td>
<td colspan="4"><strong>Mechanical</strong></td>
</tr>
<tr class="even">
<td><strong>Principle:</strong></td>
<td colspan="10">Specific contamination control requirements and
processes (such as analytical modeling, laboratory investigations, and
contamination protection and avoidance plans) that support mission
objectives shall be identified.</td>
</tr>
<tr class="odd">
<td><strong>Rationale:</strong></td>
<td colspan="10">Contamination sensitive components are often critical
elements that directly affect system performance. It is essential that
critical component performance be preserved and not allowed to degrade
due to contamination exposure &amp; accumulations.</td>
</tr>
<tr class="even">
<td><strong>Phase:</strong></td>
<td colspan="10"><strong>&lt;A A B C D E F</strong></td>
</tr>
<tr class="odd">
<td><strong>Activities:</strong></td>
<td>1. Provide within the conceptual study the preliminary contamination
control requirements that will drive mission cost, schedule, and
design.</td>
<td colspan="2">1. Update requirements and develop control
methodologies.<br />
2. Write draft Contamination Control Plan (CCP) to document cost,
schedule, and design requirements.</td>
<td>1. Update <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">CCP</a> as
mission and design details evolve.</td>
<td>1. Finalize <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">CCP</a>.<br />
2. Implement appropriate elements of <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">CCP</a> in
fabrication.</td>
<td colspan="2">1. Implement all elements of the <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">CCP</a>.</td>
<td colspan="2">1. Monitor system performance for evidence of
contamination related degradation and prepare mitigation plans if
necessary.</td>
<td>N/A</td>
</tr>
<tr class="even">
<td><strong>Verification:</strong></td>
<td>1. Verify above at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">MCR</a>.</td>
<td colspan="2">1. Verify through peer review, proposal team, and at
MRR.</td>
<td>1. Verify through peer review and at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">MDR</a>.</td>
<td>1. Verify that <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">CCP</a> is
under formal configuration control.<br />
2. Verify through peer review and at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">PDR</a> and <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">CDR</a>.</td>
<td colspan="2">1. Verify through peer review.</td>
<td colspan="2">1. Verify mitigation plan at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">ORR</a>.</td>
<td>N/A</td>
</tr>
<tr class="odd">
<td colspan="3"><p><strong>Revision Status:</strong></p>
<p>Baseline; Updated: Rev A</p></td>
<td colspan="6"><p><strong>Owner:</strong></p>
<p>Mechanical Systems Division (540)</p></td>
<td colspan="2"><p><strong>Reference:</strong></p>
<p>GEVS 2.7</p></td>
</tr>
</tbody>
</table>

<table>
<colgroup>
<col style="width: 10%" />
<col style="width: 12%" />
<col style="width: 8%" />
<col style="width: 4%" />
<col style="width: 12%" />
<col style="width: 12%" />
<col style="width: 2%" />
<col style="width: 10%" />
<col style="width: 5%" />
<col style="width: 7%" />
<col style="width: 12%" />
</colgroup>
<tbody>
<tr class="odd">
<td><strong>4.03</strong></td>
<td colspan="6"><strong>Structural Analysis and Design Factors of
Safety</strong></td>
<td colspan="4"><strong>Mechanical</strong></td>
</tr>
<tr class="even">
<td><strong>Principle:</strong></td>
<td colspan="10">Structural analysis and design factors of safety shall
apply to all systems in accordance with <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">GEVS</a>
Section 2.2.5.</td>
</tr>
<tr class="odd">
<td><strong>Rationale:</strong></td>
<td colspan="10">This will provide confidence that the hardware will not
experience failure or detrimental permanent deformation under test,
ground handling, launch, or operational conditions.</td>
</tr>
<tr class="even">
<td><strong>Phase:</strong></td>
<td colspan="10"><strong>&lt;A A B C D E F</strong></td>
</tr>
<tr class="odd">
<td><strong>Activities:</strong></td>
<td>N/A</td>
<td colspan="2">1. Employ design factors of safety in accordance with <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">GEVS</a>
2.2.5.</td>
<td>1. Employ design factors of safety in accordance with <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">GEVS</a>
2.2.5.</td>
<td>1. Employ design factors of safety in accordance with <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">GEVS</a>
2.2.5.</td>
<td colspan="2">1. Employ design factors of safety in accordance with <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">GEVS</a>
2.2.5.</td>
<td colspan="2">N/A</td>
<td>N/A</td>
</tr>
<tr class="even">
<td><strong>Verification:</strong></td>
<td>N/A</td>
<td colspan="2">1. Verify that factors of safety are defined at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">MDR</a>.</td>
<td>1. Verify that factors of safety are defined at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">SDR</a> and <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">PDR</a>.</td>
<td>1. Verify that factors of safety are defined at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">CDR</a>.</td>
<td colspan="2">1. Verify that factors of safety are being met at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">PER</a> and <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">PSR</a>.</td>
<td colspan="2">N/A</td>
<td>N/A</td>
</tr>
<tr class="odd">
<td colspan="3"><p><strong>Revision Status:</strong></p>
<p>Baseline; Updated: Rev A</p></td>
<td colspan="6"><p><strong>Owner:</strong></p>
<p>Mechanical Systems Division (540)</p></td>
<td colspan="2"><p><strong>Reference:</strong></p>
<p>GEVS 2.2.5</p></td>
</tr>
</tbody>
</table>

<table>
<colgroup>
<col style="width: 10%" />
<col style="width: 12%" />
<col style="width: 8%" />
<col style="width: 4%" />
<col style="width: 12%" />
<col style="width: 12%" />
<col style="width: 2%" />
<col style="width: 10%" />
<col style="width: 5%" />
<col style="width: 7%" />
<col style="width: 12%" />
</colgroup>
<tbody>
<tr class="odd">
<td><strong>4.06</strong></td>
<td colspan="6"><strong>Validation of Thermal Coatings
Properties</strong></td>
<td colspan="4"><strong>Mechanical</strong></td>
</tr>
<tr class="even">
<td><strong>Principle:</strong></td>
<td colspan="10">All thermal analysis shall employ thermal coatings
properties validated to be accurate for materials and mission flight
parameters over the lifecycle of the mission.</td>
</tr>
<tr class="odd">
<td><strong>Rationale:</strong></td>
<td colspan="10">Thermal coatings properties directly affect <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">Mission
success</a> through <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">S/C</a> or
instrument thermal design.</td>
</tr>
<tr class="even">
<td><strong>Phase:</strong></td>
<td colspan="10"><strong>&lt;A A B C D E F</strong></td>
</tr>
<tr class="odd">
<td><strong>Activities:</strong></td>
<td>N/A</td>
<td colspan="2">N/A</td>
<td>1. Determine appropriate <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">BOL</a> and <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">EOL</a>
coatings properties to be used in the thermal analysis.</td>
<td>1. Update thermal coatings properties as coatings selection
matures.</td>
<td colspan="2">1. Update thermal coatings properties as coatings
selection matures.<br />
2. Measure coatings properties when appropriate.</td>
<td colspan="2">N/A</td>
<td>N/A</td>
</tr>
<tr class="even">
<td><strong>Verification:</strong></td>
<td>N/A</td>
<td colspan="2">N/A</td>
<td>1. Verify through peer review and at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">PDR</a>.</td>
<td>1. Verify at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">CDR</a>.</td>
<td colspan="2">1. Verify at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">PER</a>.</td>
<td colspan="2">N/A</td>
<td>N/A</td>
</tr>
<tr class="odd">
<td colspan="3"><p><strong>Revision Status:</strong></p>
<p>Baseline</p></td>
<td colspan="6"><p><strong>Owner:</strong></p>
<p>Thermal Engineering Branch (545)</p></td>
<td colspan="2"><p><strong>Reference:</strong></p>
<p>Coatings Handbook (future)</p></td>
</tr>
</tbody>
</table>

<table>
<colgroup>
<col style="width: 10%" />
<col style="width: 12%" />
<col style="width: 8%" />
<col style="width: 4%" />
<col style="width: 12%" />
<col style="width: 12%" />
<col style="width: 2%" />
<col style="width: 10%" />
<col style="width: 5%" />
<col style="width: 7%" />
<col style="width: 12%" />
</colgroup>
<tbody>
<tr class="odd">
<td><strong>4.07</strong></td>
<td colspan="6"><strong>Solder Joint Intermetallics
Mitigation</strong></td>
<td colspan="4"><strong>Mechanical</strong></td>
</tr>
<tr class="even">
<td><strong>Principle:</strong></td>
<td colspan="10">All materials at a solder joint shall be selected to
avoid the formation of potentially destructive intermetallic
compounds.</td>
</tr>
<tr class="odd">
<td><strong>Rationale:</strong></td>
<td colspan="10">Solder joints can be significantly weakened by
excessive intermetallic formations. Particularly destructive is the
formation of gold-tin intermetallics which are brittle and change the
conductivity of the joints. Substrates to be joined using a soldering
process should be selected to mitigate the formation of these
compounds.</td>
</tr>
<tr class="even">
<td><strong>Phase:</strong></td>
<td colspan="10"><strong>&lt;A A B C D E F</strong></td>
</tr>
<tr class="odd">
<td><strong>Activities:</strong></td>
<td>N/A</td>
<td colspan="2">N/A</td>
<td>1. Substrates and processes shall be selected to avoid the formation
of excessive intermetallics. Use of gold coated substrates shall be
carefully monitored to keep gold concetration in joint below 5% by
weight.</td>
<td>1. Test representative samples of joint materials to assure
compatibility.</td>
<td colspan="2">1. Practices to mitigate the intermetallic formations in
solder joints shall be considered if incompatible substrates can't be
avoided.</td>
<td colspan="2">1. Monitor system performance for evidence of potential
solder joint-related failures. Use these data to refine solder joint
substrate requirements for future missions.</td>
<td>N/A</td>
</tr>
<tr class="even">
<td><strong>Verification:</strong></td>
<td>N/A</td>
<td colspan="2">N/A</td>
<td>1. Verify at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">PDR</a>.</td>
<td>1. Verify at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">CDR</a>.</td>
<td colspan="2">1. Verify at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">PER</a>.</td>
<td colspan="2">1. Document lessons learned.</td>
<td>N/A</td>
</tr>
<tr class="odd">
<td colspan="3"><p><strong>Revision Status:</strong></p>
<p>Baseline</p></td>
<td colspan="6"><p><strong>Owner:</strong></p>
<p>Materials Engineering Branch (541)</p></td>
<td colspan="2"><strong>Reference:</strong></td>
</tr>
</tbody>
</table>

<table>
<colgroup>
<col style="width: 10%" />
<col style="width: 12%" />
<col style="width: 8%" />
<col style="width: 4%" />
<col style="width: 12%" />
<col style="width: 12%" />
<col style="width: 2%" />
<col style="width: 10%" />
<col style="width: 5%" />
<col style="width: 7%" />
<col style="width: 12%" />
</colgroup>
<tbody>
<tr class="odd">
<td><strong>4.08</strong></td>
<td colspan="6"><strong>Space Environment Effects on Material
Selection</strong></td>
<td colspan="4"><strong>Mechanical</strong></td>
</tr>
<tr class="even">
<td><strong>Principle:</strong></td>
<td colspan="10">Thorough evaluation of the environmental effects of the
trajectory paths/orbits shall be assessed for the impact on materials
selection and design.</td>
</tr>
<tr class="odd">
<td><strong>Rationale:</strong></td>
<td colspan="10">Understanding the trajectory and orbital environmental
effects (e.g., ESD, radiation, Atomic Oxygen, etc.) on the spacecraft
will eliminate costly redesign and fixes, as well as minimize the
on-orbit failures due to environmental interaction with spacecraft
materials.</td>
</tr>
<tr class="even">
<td><strong>Phase:</strong></td>
<td colspan="10"><strong>&lt;A A B C D E F</strong></td>
</tr>
<tr class="odd">
<td><strong>Activities:</strong></td>
<td>1. Orbit and life requirement information shall be used by <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">MAE</a> to
assure compatibility of material selections.</td>
<td colspan="2">1. Refine materials compatibility analysis.</td>
<td>1. Review preliminary <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">M&amp;P</a>
list for environmental compatibility. Effects to be considered should
include but not be limited to ESD, thermal effects, radiation, atomic
oxygen, and orbital debris. As appropriate, environmental simulation
tests shall be conducted to characterize material compatibility.</td>
<td>1. Review updated <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">M&amp;P</a>
list for environmental compatibility. Continue material testing as
appropriate.</td>
<td colspan="2">1. Review updated <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">M&amp;P</a>
list for environmental compatibility. Continue material testing as
appropriate.</td>
<td colspan="2">N/A</td>
<td>N/A</td>
</tr>
<tr class="even">
<td><strong>Verification:</strong></td>
<td>1. Verify at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">MCR</a>.</td>
<td colspan="2">1. Verify at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">MDR</a>.</td>
<td>1. Verify at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">PDR</a>.</td>
<td>1. Verify at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">CDR</a>.</td>
<td colspan="2">1. Verify at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">PER</a>.</td>
<td colspan="2">N/A</td>
<td>N/A</td>
</tr>
<tr class="odd">
<td colspan="3"><p><strong>Revision Status:</strong></p>
<p>Baseline</p></td>
<td colspan="6"><p><strong>Owner:</strong></p>
<p>Materials Engineering Branch (541)</p></td>
<td colspan="2"><strong>Reference:</strong></td>
</tr>
</tbody>
</table>

<table>
<colgroup>
<col style="width: 10%" />
<col style="width: 12%" />
<col style="width: 8%" />
<col style="width: 4%" />
<col style="width: 12%" />
<col style="width: 12%" />
<col style="width: 2%" />
<col style="width: 10%" />
<col style="width: 5%" />
<col style="width: 7%" />
<col style="width: 12%" />
</colgroup>
<tbody>
<tr class="odd">
<td><strong>4.09</strong></td>
<td colspan="6"><strong>Mechanical Test Factors and
Duration</strong></td>
<td colspan="4"><strong>Mechanical</strong></td>
</tr>
<tr class="even">
<td><strong>Principle:</strong></td>
<td colspan="10">The project shall employ the mechanical test factors
and durations in accordance with Section 2.2.4 of <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">GEVS</a>.</td>
</tr>
<tr class="odd">
<td><strong>Rationale:</strong></td>
<td colspan="10">Using minimum recommended test durations and factors
developed over years of development experience will increase confidence
in test adequacy and verification status.</td>
</tr>
<tr class="even">
<td><strong>Phase:</strong></td>
<td colspan="10"><strong>&lt;A A B C D E F</strong></td>
</tr>
<tr class="odd">
<td><strong>Activities:</strong></td>
<td>N/A</td>
<td colspan="2">N/A</td>
<td>N/A</td>
<td>1. Formulate test plans for all structural elements incorporating
the requirements described in the principle.</td>
<td colspan="2">1. Write test plans and execute tests.</td>
<td colspan="2">N/A</td>
<td>N/A</td>
</tr>
<tr class="even">
<td><strong>Verification:</strong></td>
<td>N/A</td>
<td colspan="2">N/A</td>
<td>N/A</td>
<td>1. Verify at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">CDR</a>.</td>
<td colspan="2">1. Verify at engineering peer reviews, <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">PER</a>, and <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">PSR</a>.</td>
<td colspan="2">N/A</td>
<td>N/A</td>
</tr>
<tr class="odd">
<td colspan="3"><p><strong>Revision Status:</strong></p>
<p>Baseline; Updated: Rev A</p></td>
<td colspan="6"><p><strong>Owner:</strong></p>
<p>Mechanical Systems Analysis and <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">Simulation</a>
Branch (542)</p></td>
<td colspan="2"><p><strong>Reference:</strong></p>
<p>GEVS SE 2.2.4</p></td>
</tr>
</tbody>
</table>

<table>
<colgroup>
<col style="width: 10%" />
<col style="width: 12%" />
<col style="width: 8%" />
<col style="width: 4%" />
<col style="width: 12%" />
<col style="width: 12%" />
<col style="width: 2%" />
<col style="width: 10%" />
<col style="width: 5%" />
<col style="width: 7%" />
<col style="width: 12%" />
</colgroup>
<tbody>
<tr class="odd">
<td><strong>4.10</strong></td>
<td colspan="6"><strong>Minimum Workmanship</strong></td>
<td colspan="4"><strong>Mechanical</strong></td>
</tr>
<tr class="even">
<td><strong>Principle:</strong></td>
<td colspan="10">All electrical, electronic, and electro-mechanical
components shall be subjected to minimum workmanship test levels as
specified in <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">GEVS</a>
Section 2.4.2.5.</td>
</tr>
<tr class="odd">
<td><strong>Rationale:</strong></td>
<td colspan="10">The workmanship levels defined in <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">GEVS</a>
Section 2.4.2.5 have been found to be the minimum input level necessary
to adequately screen aerospace electronic hardware for workmanship
flaws.</td>
</tr>
<tr class="even">
<td><strong>Phase:</strong></td>
<td colspan="10"><strong>&lt;A A B C D E F</strong></td>
</tr>
<tr class="odd">
<td><strong>Activities:</strong></td>
<td>N/A</td>
<td colspan="2">N/A</td>
<td>1. Envelop minimum workmanship levels when deriving component random
vibration test levels.</td>
<td>1. Envelop minimum workmanship levels when deriving component random
vibration test levels.</td>
<td colspan="2">1. Envelop minimum workmanship levels when deriving
component random vibration test levels</td>
<td colspan="2">N/A</td>
<td>N/A</td>
</tr>
<tr class="even">
<td><strong>Verification:</strong></td>
<td>N/A</td>
<td colspan="2">N/A</td>
<td>1. Verify that component test levels envelop minimum
workmanship.</td>
<td>1. Verify that component test levels envelop minimum
workmanship.</td>
<td colspan="2">1. Verify that components have been adequately screened
for workmanship.</td>
<td colspan="2">N/A</td>
<td>N/A</td>
</tr>
<tr class="odd">
<td colspan="3"><p><strong>Revision Status:</strong></p>
<p>Baseline; Updated: Rev A</p></td>
<td colspan="6"><p><strong>Owner:</strong></p>
<p>Mechanical Systems Analysis and <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">Simulation</a>
Branch (542)</p></td>
<td colspan="2"><p><strong>Reference:</strong></p>
<p>GEVS Section 2.4.2.5</p></td>
</tr>
</tbody>
</table>

<table style="width:100%;">
<colgroup>
<col style="width: 10%" />
<col style="width: 12%" />
<col style="width: 8%" />
<col style="width: 4%" />
<col style="width: 12%" />
<col style="width: 12%" />
<col style="width: 2%" />
<col style="width: 10%" />
<col style="width: 3%" />
<col style="width: 9%" />
<col style="width: 12%" />
</colgroup>
<tbody>
<tr class="odd">
<td><strong>4.11</strong></td>
<td colspan="6"><strong>Testing in Flight Configuration</strong></td>
<td colspan="4"><strong>Mechanical</strong></td>
</tr>
<tr class="even">
<td><strong>Principle:</strong></td>
<td colspan="10">Mechanical environmental testing (sine, random &amp;
acoustic) of flight hardware shall be performed with the test article in
appropriate (e.g. launch, landing, etc.) configuration. Hardware that is
to be powered on for launch shall be powered on for testing.</td>
</tr>
<tr class="odd">
<td><strong>Rationale:</strong></td>
<td colspan="10">Testing in-flight configuration ensures that hardware
that is difficult to analyze (i.e. blankets, harnesses, mechanisms) will
be adequately screened by environmental testing for design or
workmanship flaws.</td>
</tr>
<tr class="even">
<td><strong>Phase:</strong></td>
<td colspan="10"><strong>&lt;A A B C D E F</strong></td>
</tr>
<tr class="odd">
<td><strong>Activities:</strong></td>
<td>N/A</td>
<td colspan="2">N/A</td>
<td>N/A</td>
<td>1. Develop plans necessary to allow testing of hardware in flight
configuration.</td>
<td colspan="2">1. Perform testing in flight configuration.</td>
<td colspan="2">N/A</td>
<td>N/A</td>
</tr>
<tr class="even">
<td><strong>Verification:</strong></td>
<td>N/A</td>
<td colspan="2">N/A</td>
<td>N/A</td>
<td>1. Verify that appropriate planning has been performed to conduct
test in flight configuration.</td>
<td colspan="2">1. Verify that testing has been performed with the test
article in flight configuration.</td>
<td colspan="2">N/A</td>
<td>N/A</td>
</tr>
<tr class="odd">
<td colspan="3"><p><strong>Revision Status:</strong></p>
<p>Baseline; Updated: Rev A</p></td>
<td colspan="6"><p><strong>Owner:</strong></p>
<p>Mechanical Systems Analysis and <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">Simulation</a>
Branch (542)</p></td>
<td colspan="2"><p><strong>Reference:</strong></p>
<p>GEVS Sections 2.4.2, 2.4.3, 2.4.4</p></td>
</tr>
</tbody>
</table>

<table>
<colgroup>
<col style="width: 10%" />
<col style="width: 12%" />
<col style="width: 8%" />
<col style="width: 4%" />
<col style="width: 12%" />
<col style="width: 12%" />
<col style="width: 2%" />
<col style="width: 10%" />
<col style="width: 5%" />
<col style="width: 7%" />
<col style="width: 12%" />
</colgroup>
<tbody>
<tr class="odd">
<td><strong>4.12</strong></td>
<td colspan="6"><strong>Structural Proof Testing</strong></td>
<td colspan="4"><strong>Mechanical</strong></td>
</tr>
<tr class="even">
<td><strong>Principle:</strong></td>
<td colspan="10">Primary and secondary structures fabricated from
nonmetallic composites, beryllium, or containing bonded joints or bonded
inserts shall be proof tested in accordance with GEVS-SE Section
2.4.1.4.1.</td>
</tr>
<tr class="odd">
<td><strong>Rationale:</strong></td>
<td colspan="10">The mechanical strength of the above items is dependent
on workmanship and processing and can only be verified by proof
testing.</td>
</tr>
<tr class="even">
<td><strong>Phase:</strong></td>
<td colspan="10"><strong>&lt;A A B C D E F</strong></td>
</tr>
<tr class="odd">
<td><strong>Activities:</strong></td>
<td>N/A</td>
<td colspan="2">N/A</td>
<td>1. Identify structure requiring proof testing.</td>
<td>1. Develop test methods and plans for performing proof testing.</td>
<td colspan="2">1. Perform proof testing to verify mechanical
strength.</td>
<td colspan="2">N/A</td>
<td>N/A</td>
</tr>
<tr class="even">
<td><strong>Verification:</strong></td>
<td>N/A</td>
<td colspan="2">N/A</td>
<td>1. Verify that all structural elements requiring proof testing have
been identified.</td>
<td>1. Verify that approach for proof testing appropriate structural
elements has been defined.</td>
<td colspan="2">1. Verify that proof testing has been performed.</td>
<td colspan="2">N/A</td>
<td>N/A</td>
</tr>
<tr class="odd">
<td colspan="3"><p><strong>Revision Status:</strong></p>
<p>Baseline; Updated: Rev A</p></td>
<td colspan="6"><p><strong>Owner:</strong></p>
<p>Mechanical Systems Analysis and <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">Simulation</a>
Branch (542)</p></td>
<td colspan="2"><p><strong>Reference:</strong></p>
<p>GEVS 2.4.1.4.1</p></td>
</tr>
</tbody>
</table>

<table>
<colgroup>
<col style="width: 10%" />
<col style="width: 12%" />
<col style="width: 8%" />
<col style="width: 4%" />
<col style="width: 12%" />
<col style="width: 12%" />
<col style="width: 2%" />
<col style="width: 10%" />
<col style="width: 5%" />
<col style="width: 7%" />
<col style="width: 12%" />
</colgroup>
<tbody>
<tr class="odd">
<td><strong>4.13</strong></td>
<td colspan="6"><strong>Modal Survey Characterization</strong></td>
<td colspan="4"><strong>Mechanical</strong></td>
</tr>
<tr class="even">
<td><strong>Principle:</strong></td>
<td colspan="10">A modal survey shall be performed for flight hardware
that has modes in the frequency range as specified in <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">GEVS</a>
Section 2.4.1.2.</td>
</tr>
<tr class="odd">
<td><strong>Rationale:</strong></td>
<td colspan="10">Modal surveys are invaluable tools in the process of
validating computer model analysis of structures. They are essential
elements of any verification process.</td>
</tr>
<tr class="even">
<td><strong>Phase:</strong></td>
<td colspan="10"><strong>&lt;A A B C D E F</strong></td>
</tr>
<tr class="odd">
<td><strong>Activities:</strong></td>
<td>N/A</td>
<td colspan="2">N/A</td>
<td>1. Include modal survey in the verification plan and verification
matrix for all appropriate structural elements.</td>
<td>1. Formulate test plans describing appropriate modal survey
techniques for structural elements.</td>
<td colspan="2">1. Write test procedures and conduct modal surveys.</td>
<td colspan="2">N/A</td>
<td>N/A</td>
</tr>
<tr class="even">
<td><strong>Verification:</strong></td>
<td>N/A</td>
<td colspan="2">N/A</td>
<td>1. Verify at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">PDR</a>.</td>
<td>1. Verify at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">CDR</a>.</td>
<td colspan="2">1. Verify at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">PER</a> and <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">PSR</a>.</td>
<td colspan="2">N/A</td>
<td>N/A</td>
</tr>
<tr class="odd">
<td colspan="3"><p><strong>Revision Status:</strong></p>
<p>Baseline; Updated: Rev A</p></td>
<td colspan="6"><p><strong>Owner:</strong></p>
<p>Mechanical Systems Analysis and <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">Simulation</a>
Branch (542)</p></td>
<td colspan="2"><p><strong>Reference:</strong></p>
<p>GEVS 2.4.1.2</p></td>
</tr>
</tbody>
</table>

<table style="width:100%;">
<colgroup>
<col style="width: 10%" />
<col style="width: 12%" />
<col style="width: 8%" />
<col style="width: 4%" />
<col style="width: 12%" />
<col style="width: 12%" />
<col style="width: 2%" />
<col style="width: 10%" />
<col style="width: 3%" />
<col style="width: 9%" />
<col style="width: 12%" />
</colgroup>
<tbody>
<tr class="odd">
<td><strong>4.14</strong></td>
<td colspan="6"><strong>Structural Qualification</strong></td>
<td colspan="4"><strong>Mechanical</strong></td>
</tr>
<tr class="even">
<td><strong>Principle:</strong></td>
<td colspan="10">Structural tests that demonstrate that flight hardware
is compatible with expected mission environments shall be conducted in
compliance with <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">GEVS</a>
2.4.</td>
</tr>
<tr class="odd">
<td><strong>Rationale:</strong></td>
<td colspan="10">Demonstration of structural requirements is a key risk
reduction activity during mission development.</td>
</tr>
<tr class="even">
<td><strong>Phase:</strong></td>
<td colspan="10"><strong>&lt;A A B C D E F</strong></td>
</tr>
<tr class="odd">
<td><strong>Activities:</strong></td>
<td>1. Develop outline of structural qualification methodology.</td>
<td colspan="2">1. Update structural qualification methodology and
develop preliminary strength qualification plan.</td>
<td>1. Develop draft structural qualification methodology and plan.</td>
<td>1. Finalize structural qualification plan.<br />
2. Implement plan.</td>
<td colspan="2">1. Demonstrate that flight hardware supports expected
mission environments and complies with specified verification
requirements.</td>
<td colspan="2">N/A</td>
<td>N/A</td>
</tr>
<tr class="even">
<td><strong>Verification:</strong></td>
<td>1. Verify at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">MCR</a>.</td>
<td colspan="2">1. Verify at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">MDR</a>.</td>
<td>1. Verify that plan is under configuration control.<br />
2. Verify through peer review and at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">PDR</a>.</td>
<td>1. Verify through <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">CDR</a> peer
review and at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">CDR</a>.</td>
<td colspan="2">1. Verify at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">PER</a> and <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">PSR</a>.</td>
<td colspan="2">N/A</td>
<td>N/A</td>
</tr>
<tr class="odd">
<td colspan="3"><p><strong>Revision Status:</strong></p>
<p>Baseline; Updated: Rev A</p></td>
<td colspan="6"><p><strong>Owner:</strong></p>
<p>Mechanical Engineering Branch (543)</p></td>
<td colspan="2"><p><strong>Reference:</strong></p>
<p>GEVS Sections 2.4.2, 2.4.3, 2.4.4</p></td>
</tr>
</tbody>
</table>

<table>
<colgroup>
<col style="width: 10%" />
<col style="width: 12%" />
<col style="width: 8%" />
<col style="width: 4%" />
<col style="width: 12%" />
<col style="width: 12%" />
<col style="width: 2%" />
<col style="width: 10%" />
<col style="width: 5%" />
<col style="width: 7%" />
<col style="width: 12%" />
</colgroup>
<tbody>
<tr class="odd">
<td><strong>4.15</strong></td>
<td colspan="6"><strong>Torque Margin</strong></td>
<td colspan="4"><strong>Mechanical</strong></td>
</tr>
<tr class="even">
<td><strong>Principle:</strong></td>
<td colspan="10">The Torque <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">Margin</a> (TM)
requirement defined in <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">GEVS</a>
section 2.4.5.3 shall apply to all mechanical functions, those driven by
motors as well as springs, etc. at beginning of life (BOL). End of Life
(EOL) mechanism performance shall be determined by life testing, and/or
by analysis; however, all torque increases due to life test results
and/or analysis shall be included in the final <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">TM</a>
calculation and verification. Margins shall include all flight drive
electronics effects and limitations.</td>
</tr>
<tr class="odd">
<td><strong>Rationale:</strong></td>
<td colspan="10">This torque margin requirement relates to the
verification phase of the hardware in question. Conservative decisions
should be made during the design phase to ensure adequate margins are
realized. However, it is recognized that under some unique circumstances
these specified Factors of <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">Safety</a>
(FOS) might be detrimental (excessive) to the design of a system. For
specific cases that require approval of a waiver, appropriate <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">FOS</a> shall
be determined based on design complexity, engineering test data,
confidence level, and other pertinent information.</td>
</tr>
<tr class="even">
<td><strong>Phase:</strong></td>
<td colspan="10"><strong>&lt;A A B C D E F</strong></td>
</tr>
<tr class="odd">
<td><strong>Activities:</strong></td>
<td>N/A</td>
<td colspan="2">1. Identify and create a plan for determination and
implementation for Torque <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">Margin</a>
verification.</td>
<td>1. The Torque <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">Margin</a> (TM)
shall be calculated per the guidelines in <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">GEVS</a>
Section 2.4.5.3 using <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">PDR</a> Factors
of <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">Safety</a>.
Identify basis for input to analysis.</td>
<td>1. The Torque <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">Margin</a> (TM)
shall be calculated per the guidelines in <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">GEVS</a>
Section 2.4.5.3 using <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">CDR</a> Factors
of <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">Safety</a>.
Identify basis for input to analysis.<br />
2. Present all available engineering test data used for these
analyses.</td>
<td colspan="2">1. The Torque <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">Margin</a> (TM)
shall be Calculated per the guidelines in <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">GEVS</a>
Section 2.4.5.3 using Post Acceptance / Qualification Factors of <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">Safety</a>.</td>
<td colspan="2">1. Monitor system performance for evidence of mechanism
degradation. Use this data to improve future design approaches.<br />
2. Prepare mitigation plan to extend the life of the mission if
degradation becomes evident.</td>
<td>N/A</td>
</tr>
<tr class="even">
<td><strong>Verification:</strong></td>
<td>N/A</td>
<td colspan="2">1. The Torque <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">Margin</a> Plan
shall be presented at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">MDR</a> as part
of the analysis and verification process.</td>
<td>1. Present <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">TM</a> analysis
at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">PDR</a>.</td>
<td>1. Present <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">TM</a> analysis
at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">CDR</a>.</td>
<td colspan="2">1. Present final test verified <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">TM</a> analysis
at <a href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">PSR</a>.
Identify basis for input to analysis. Present all available hardware
verification test data used for these analyses.</td>
<td colspan="2"></td>
<td>N/A</td>
</tr>
<tr class="odd">
<td colspan="3"><p><strong>Revision Status:</strong></p>
<p>Baseline; Updated: Rev A</p></td>
<td colspan="6"><p><strong>Owner:</strong></p>
<p>Mechanical Engineering Branch (543)</p></td>
<td colspan="2"><p><strong>Reference:</strong></p>
<p>GEVS (Rev B Draft) 2.4.5.3</p></td>
</tr>
</tbody>
</table>

<table>
<colgroup>
<col style="width: 10%" />
<col style="width: 12%" />
<col style="width: 8%" />
<col style="width: 4%" />
<col style="width: 12%" />
<col style="width: 12%" />
<col style="width: 2%" />
<col style="width: 10%" />
<col style="width: 5%" />
<col style="width: 7%" />
<col style="width: 12%" />
</colgroup>
<tbody>
<tr class="odd">
<td><strong>4.18</strong></td>
<td colspan="6"><strong>Deployment and Articulation
Verification</strong></td>
<td colspan="4"><strong>Mechanical</strong></td>
</tr>
<tr class="even">
<td><strong>Principle:</strong></td>
<td colspan="10">All flight deployables, movable appendages, and
mechanisms shall demonstrate full range of motion and articulation under
worst-case conditions prior to flight.</td>
</tr>
<tr class="odd">
<td><strong>Rationale:</strong></td>
<td colspan="10">Environmental factors such as temperature, gravity,
acceleration fields, wire bundle stiffness, and others can adversely
effect successful deployment. <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">Verification</a>
of these systems under worst-case conditions will improve on-orbit
success.</td>
</tr>
<tr class="even">
<td><strong>Phase:</strong></td>
<td colspan="10"><strong>&lt;A A B C D E F</strong></td>
</tr>
<tr class="odd">
<td><strong>Activities:</strong></td>
<td>N/A</td>
<td colspan="2">N/A</td>
<td>1. Include articulation in the verification plan and verification
matrix.</td>
<td>1. Analyze design and use environment to determine worst case
deployment conditions.<br />
2. Demonstrate that all deployable system test plans include provisions
to verify deployment under worst case conditions.</td>
<td colspan="2">1. Update worst case analysis and test plans.<br />
2. Write test procedure(s).<br />
3. Conduct tests.</td>
<td colspan="2">N/A</td>
<td>N/A</td>
</tr>
<tr class="even">
<td><strong>Verification:</strong></td>
<td>N/A</td>
<td colspan="2">N/A</td>
<td>1. Verify at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">PDR</a>.</td>
<td>1. Verify worst case condition analysis and test plans/procedures
through engineering peer review and at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">CDR</a>.</td>
<td colspan="2">1. Verify test procedures and test results through
engineering peer reviews, and at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">PER</a> and <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">PSR</a>.</td>
<td colspan="2">N/A</td>
<td>N/A</td>
</tr>
<tr class="odd">
<td colspan="3"><p><strong>Revision Status:</strong></p>
<p>Baseline</p></td>
<td colspan="6"><p><strong>Owner:</strong></p>
<p>Mechanical Engineering Branch (543)</p></td>
<td colspan="2"><strong>Reference:</strong></td>
</tr>
</tbody>
</table>

<table>
<colgroup>
<col style="width: 10%" />
<col style="width: 12%" />
<col style="width: 8%" />
<col style="width: 4%" />
<col style="width: 12%" />
<col style="width: 12%" />
<col style="width: 2%" />
<col style="width: 10%" />
<col style="width: 5%" />
<col style="width: 7%" />
<col style="width: 12%" />
</colgroup>
<tbody>
<tr class="odd">
<td><strong>4.20</strong></td>
<td colspan="6"><strong>Fastener Locking</strong></td>
<td colspan="4"><strong>Mechanical</strong></td>
</tr>
<tr class="even">
<td><strong>Principle:</strong></td>
<td colspan="10">All threaded fasteners shall employ a locking
feature.</td>
</tr>
<tr class="odd">
<td><strong>Rationale:</strong></td>
<td colspan="10">If not locked in the torqued, preloaded position,
threaded fasteners subjected to vibration and thermal cycling loads will
tend to relieve their preload and potentially jeopardize the
mission.</td>
</tr>
<tr class="even">
<td><strong>Phase:</strong></td>
<td colspan="10"><strong>&lt;A A B C D E F</strong></td>
</tr>
<tr class="odd">
<td><strong>Activities:</strong></td>
<td>N/A</td>
<td colspan="2">N/A</td>
<td>N/A</td>
<td>1. Review all design drawings and specifications to assure all
fastners employ an appropriate locking feature.</td>
<td colspan="2">1. Inspect all threaded fastener related assemblies to
verify that the specified locking feature has been properly
applied.</td>
<td colspan="2">N/A</td>
<td>NA</td>
</tr>
<tr class="even">
<td><strong>Verification:</strong></td>
<td>N/A</td>
<td colspan="2">N/A</td>
<td>N/A</td>
<td>1. Verify at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">CDR</a>.</td>
<td colspan="2">1. Verify at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">PER</a> and <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">PSR</a>.</td>
<td colspan="2">N/A</td>
<td>N/A</td>
</tr>
<tr class="odd">
<td colspan="3"><p><strong>Revision Status:</strong></p>
<p>Baseline</p></td>
<td colspan="6"><p><strong>Owner:</strong></p>
<p>Electromechanical Systems Branch (544)</p></td>
<td colspan="2"><strong>Reference:</strong></td>
</tr>
</tbody>
</table>

<table>
<colgroup>
<col style="width: 10%" />
<col style="width: 12%" />
<col style="width: 8%" />
<col style="width: 4%" />
<col style="width: 12%" />
<col style="width: 12%" />
<col style="width: 2%" />
<col style="width: 10%" />
<col style="width: 5%" />
<col style="width: 7%" />
<col style="width: 12%" />
</colgroup>
<tbody>
<tr class="odd">
<td><strong>4.22</strong></td>
<td colspan="6"><strong>Precision Component Assembly</strong></td>
<td colspan="4"><strong>Mechanical</strong></td>
</tr>
<tr class="even">
<td><strong>Principle:</strong></td>
<td colspan="10">When precise location of a component is required, the
design shall use a stable, positive location system (not relying on
friction) as the primary means of attachment.</td>
</tr>
<tr class="odd">
<td><strong>Rationale:</strong></td>
<td colspan="10">When in the domain of arc-sec to sub-arc-sec location
requirements, the use of pinning or similar non-friction reliant method
will help ensure alignment is maintained through all expected
stresses.</td>
</tr>
<tr class="even">
<td><strong>Phase:</strong></td>
<td colspan="10"><strong>&lt;A A B C D E F</strong></td>
</tr>
<tr class="odd">
<td><strong>Activities:</strong></td>
<td>1. Begin to identify potential high precision interfaces.</td>
<td colspan="2">1. Refine identification of high precision
interfaces.</td>
<td>1. Identify methodology for precise location attachment.</td>
<td>1. Design and document attachment methods.</td>
<td colspan="2">1. Inspect assemblies to assure specified attachment
techniques are properly applied.</td>
<td colspan="2">N/A</td>
<td>N/A</td>
</tr>
<tr class="even">
<td><strong>Verification:</strong></td>
<td>N/A</td>
<td colspan="2">N/A</td>
<td>1. Verify through peer review and at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">PDR</a>.</td>
<td>1. Verify through peer review and at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">CDR</a>.</td>
<td colspan="2">1. Verify through peer review and at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">PER</a>.</td>
<td colspan="2">N/A</td>
<td>N/A</td>
</tr>
<tr class="odd">
<td colspan="3"><p><strong>Revision Status:</strong></p>
<p>Baseline</p></td>
<td colspan="6"><p><strong>Owner:</strong></p>
<p>Electromechanical Systems Branch (544)</p></td>
<td colspan="2"><strong>Reference:</strong></td>
</tr>
</tbody>
</table>

<table>
<colgroup>
<col style="width: 10%" />
<col style="width: 12%" />
<col style="width: 8%" />
<col style="width: 4%" />
<col style="width: 12%" />
<col style="width: 12%" />
<col style="width: 2%" />
<col style="width: 10%" />
<col style="width: 5%" />
<col style="width: 7%" />
<col style="width: 12%" />
</colgroup>
<tbody>
<tr class="odd">
<td><strong>4.23</strong></td>
<td colspan="6"><strong>Life Test</strong></td>
<td colspan="4"><strong>Mechanical</strong></td>
</tr>
<tr class="even">
<td><strong>Principle:</strong></td>
<td colspan="10">A life test shall be conducted, within representative
operational environments, to at least 2x expected life for all
repetitive motion devices with a goal of completing 1x expected life by
<a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">CDR</a>.</td>
</tr>
<tr class="odd">
<td><strong>Rationale:</strong></td>
<td colspan="10">Reliability of electro-mechanical systems can have
serious <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">Mission
success</a> implications. Documented life testing must be performed
which demonstrate performance requirements for mission life. Life tests
must consider the flight drive electronics effects and limitations.</td>
</tr>
<tr class="even">
<td><strong>Phase:</strong></td>
<td colspan="10"><strong>&lt;A A B C D E F</strong></td>
</tr>
<tr class="odd">
<td><strong>Activities:</strong></td>
<td>N/A</td>
<td colspan="2">1. Develop a life test outline for all repetitive motion
devices.</td>
<td>1. Develop draft life test plan.</td>
<td>1. Finalize plan and implement.</td>
<td colspan="2">1. Present life test conclusions and compare to mission
performance requirements.</td>
<td colspan="2">N/A</td>
<td>N/A</td>
</tr>
<tr class="even">
<td><strong>Verification:</strong></td>
<td>N/A</td>
<td colspan="2">1. Verify at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">MDR</a>.</td>
<td>1. Verify that plan has been drafted at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">PDR</a>.</td>
<td>1. Verify plan and any existing life test data.</td>
<td colspan="2">1. Verify life test results at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">PER</a> and <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">PSR</a>.</td>
<td colspan="2">N/A</td>
<td>N/A</td>
</tr>
<tr class="odd">
<td colspan="3"><p><strong>Revision Status:</strong></p>
<p>Baseline; Updated: Rev A</p></td>
<td colspan="6"><p><strong>Owner:</strong></p>
<p>Electromechanical Systems Branch (544)</p></td>
<td colspan="2"><p><strong>Reference:</strong></p>
<p>GEVS 2.4.5.1</p></td>
</tr>
</tbody>
</table>

<table>
<colgroup>
<col style="width: 10%" />
<col style="width: 12%" />
<col style="width: 8%" />
<col style="width: 4%" />
<col style="width: 12%" />
<col style="width: 12%" />
<col style="width: 2%" />
<col style="width: 10%" />
<col style="width: 5%" />
<col style="width: 7%" />
<col style="width: 12%" />
</colgroup>
<tbody>
<tr class="odd">
<td><strong>4.24</strong></td>
<td colspan="6"><strong>Mechanical Clearance Verification</strong></td>
<td colspan="4"><strong>Mechanical</strong></td>
</tr>
<tr class="even">
<td><strong>Principle:</strong></td>
<td colspan="10"><a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">Verification</a>
of mechanical clearances and margins (e.g. potential reduced clearances
after blanket expansion) shall be performed on the final as-built
hardware.</td>
</tr>
<tr class="odd">
<td><strong>Rationale:</strong></td>
<td colspan="10">Proper mechanical clearances are often critical to
successful on-orbit performance (e.g. free-movement area, thruster
impingment, <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">FOV</a>, etc.).
<a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">Verification</a>
through analysis and drawing checking alone is not sufficient to
properly demonstrate adequate clearance.</td>
</tr>
<tr class="even">
<td><strong>Phase:</strong></td>
<td colspan="10"><strong>&lt;A A B C D E F</strong></td>
</tr>
<tr class="odd">
<td><strong>Activities:</strong></td>
<td>N/A</td>
<td colspan="2">N/A</td>
<td>N/A</td>
<td>1. Demonstrate that mechanical integration plans include provisions
for verifying mechanical clearences at appropriate integration
milestones.<br />
2. Conduct inspections and measurements.</td>
<td colspan="2">1. Demonstrate that mechanical integration plans include
provisions for verifying mechanical clearences at appropriate
integration milestones.<br />
2. Conduct inspections and measurements.</td>
<td colspan="2">N/A</td>
<td>N/A</td>
</tr>
<tr class="even">
<td><strong>Verification:</strong></td>
<td>N/A</td>
<td colspan="2">N/A</td>
<td>N/A</td>
<td>1. Verify at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">CDR</a>.</td>
<td colspan="2">1. Verify at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">PER</a> and <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">PSR</a>.</td>
<td colspan="2">N/A</td>
<td>N/A</td>
</tr>
<tr class="odd">
<td colspan="3"><p><strong>Revision Status:</strong></p>
<p>Baseline</p></td>
<td colspan="6"><p><strong>Owner:</strong></p>
<p>Electromechanical Systems Branch (544)</p></td>
<td colspan="2"><strong>Reference:</strong></td>
</tr>
</tbody>
</table>

<table>
<colgroup>
<col style="width: 10%" />
<col style="width: 12%" />
<col style="width: 8%" />
<col style="width: 4%" />
<col style="width: 12%" />
<col style="width: 12%" />
<col style="width: 2%" />
<col style="width: 10%" />
<col style="width: 5%" />
<col style="width: 7%" />
<col style="width: 12%" />
</colgroup>
<tbody>
<tr class="odd">
<td><strong>4.25</strong></td>
<td colspan="6"><strong>Thermal Design Margins</strong></td>
<td colspan="4"><strong>Mechanical</strong></td>
</tr>
<tr class="even">
<td><strong>Principle:</strong></td>
<td colspan="10">Thermal design shall provide adequate margin between
stacked worst-case flight predictions and component allowable flight
temperature limits.<br />
Note: This applies to normal operations and planned contingency modes.
This does not apply to cryogenic systems.</td>
</tr>
<tr class="odd">
<td><strong>Rationale:</strong></td>
<td colspan="10">Positive temperature margins are required to account
for uncertainties in power dissipations, environments, and thermal
system parameters.</td>
</tr>
<tr class="even">
<td><strong>Phase:</strong></td>
<td colspan="10"><strong>&lt;A A B C D E F</strong></td>
</tr>
<tr class="odd">
<td><strong>Activities:</strong></td>
<td>1. Thermal design concept produces minimum 5C margins, except for
heater controlled elements which have a maximum 70% heater duty cycle,
and two-phase flow systems which have a minimum 30% heat transport
margin. For Pre-A, larger margins advisable.</td>
<td colspan="2">1. Thermal design concept produces minimum 5C margins,
except for heater controlled elements which have a maximum 70% heater
duty cycle, and two-phase flow systems which have a minimum 30% heat
transport margin. For Phase A, larger margins advisable.</td>
<td>1. Thermal design concept produces minimum 5C margins, except for
heater controlled elements which have a maximum 70% heater duty cycle,
and two-phase flow systems which have a minimum 30% heat transport
margin.</td>
<td>1. Thermal design concept produces minimum 5C margins, except for
heater controlled elements which have a maximum 70% heater duty cycle,
and two-phase flow systems which have a minimum 30% heat transport
margin.</td>
<td colspan="2">1. <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">System</a>
thermal balance test produces test-correlated model. Test and worst-case
flight thermal analysis with test-correlated model demonstrate minimum
5C margins, except for heater controlled elements which demonstrate a
maximum 70% heater duty cycle, and two-phase flow systems which
demonstrate a minimum 30% heat transport margin.</td>
<td colspan="2">1. Thermal analysis with flight-correlated model shows
minimum 5C margins for mission trade studies, except for heater
controlled elements which have a maximum 70% heater duty cycle, and
two-phase flow systems which have a minimum 30% heat transport
margin.</td>
<td>1. Thermal analysis with flight-correlated model shows minimum 5C
margins for mission disposal options, except for heater controlled
elements which have a maximum 70% heater duty cycle, and two-phase flow
systems which have a minimum 30% heat transport margin.</td>
</tr>
<tr class="even">
<td><strong>Verification:</strong></td>
<td>1. Verify at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">MCR</a>.</td>
<td colspan="2">1. Verify worst-case thermal analysis of concept through
peer review and at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">SRR</a> and <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">MDR</a>.</td>
<td>1. Verify worst-case thermal analysis of design through peer review
and at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">PDR</a>.</td>
<td>1. Verify worst-case thermal analysis of detailed design through
peer review and at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">CDR</a>.</td>
<td colspan="2">1. Verify through peer review and at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">PER</a> and <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">PSR</a>.</td>
<td colspan="2">1. Verify thermal analysis of flight system using
flight-correlated thermal model through peer review.</td>
<td>1. Verify thermal analysis of flight system using flight-correlated
thermal model through peer review.</td>
</tr>
<tr class="odd">
<td colspan="3"><p><strong>Revision Status:</strong></p>
<p>Baseline; Updated: Rev A</p></td>
<td colspan="6"><p><strong>Owner:</strong></p>
<p>Thermal Engineering Branch (545)</p></td>
<td colspan="2"><p><strong>Reference:</strong></p>
<p>GEVS 2.63; 545-PG-8700.2.1</p></td>
</tr>
</tbody>
</table>

<table>
<colgroup>
<col style="width: 10%" />
<col style="width: 12%" />
<col style="width: 8%" />
<col style="width: 4%" />
<col style="width: 12%" />
<col style="width: 12%" />
<col style="width: 2%" />
<col style="width: 10%" />
<col style="width: 5%" />
<col style="width: 7%" />
<col style="width: 12%" />
</colgroup>
<tbody>
<tr class="odd">
<td><strong>4.26</strong></td>
<td colspan="6"><strong>Thermal Design Margins - Unplanned
Conditions</strong></td>
<td colspan="4"><strong>Mechanical</strong></td>
</tr>
<tr class="even">
<td><strong>Principle:</strong></td>
<td colspan="10">For <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">credible</a>
abnormal conditions, the thermal design shall maintain temperatures with
allowable flight temperature (AFT) limits extended by +/- 5C (Flight
Acceptance (FA) temperature range).</td>
</tr>
<tr class="odd">
<td><strong>Rationale:</strong></td>
<td colspan="10">The Acceptance Temperature margin of +/-5C can be used
to absorb temperature impacts resulting from <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">credible</a>
abnormal conditions such as anomaly-induced power dissipation,
off-nominal sun attitude conditions, and/or thermal control element
(active or passive) anomalous behavior.</td>
</tr>
<tr class="even">
<td><strong>Phase:</strong></td>
<td colspan="10"><strong>&lt;A A B C D E F</strong></td>
</tr>
<tr class="odd">
<td><strong>Activities:</strong></td>
<td>N/A</td>
<td colspan="2">N/A</td>
<td>1. Systems Engineering defines <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">credible</a>
abnormal conditions for inclusion in system definition for thermal
analysis.</td>
<td>1. Systems Engineering refines and updates <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">credible</a>
conditions for evaluation in system definition for thermal
analysis.</td>
<td colspan="2">1. Thermal Balance Testing shall include, where
appropriate, a simulation of the abnormal <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">credible</a>
condition for empirical evaluation.</td>
<td colspan="2">1. Thermal analysis with flight-correlated model shows
temperatures at or less than FA Limits for <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">System</a>
Engineering defined <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">credible</a>
abnormal conditions.</td>
<td>1. Thermal analysis with flight-correlated model shows temperatures
at or less than FA Limits for <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">System</a>
Engineering defined <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">credible</a>
abnormal conditions.</td>
</tr>
<tr class="even">
<td><strong>Verification:</strong></td>
<td>N/A</td>
<td colspan="2">N/A</td>
<td>1. Verify at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">PDR</a>.</td>
<td>1. Verify at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">CDR</a>.</td>
<td colspan="2">1. Verify through peer review and at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">PSR</a>.</td>
<td colspan="2">1. Verify through thermal analysis of flight system
using flight-correlated thermal model.</td>
<td>1. Verify through thermal analysis of flight system using
flight-correlated thermal model.</td>
</tr>
<tr class="odd">
<td colspan="3"><p><strong>Revision Status:</strong></p>
<p>Baseline</p></td>
<td colspan="6"><p><strong>Owner:</strong></p>
<p>Thermal Engineering Branch (545)</p></td>
<td colspan="2"><p><strong>Reference:</strong></p>
<p>JPL D-17868 rev. 2: 4.8.2.4</p></td>
</tr>
</tbody>
</table>

<table>
<colgroup>
<col style="width: 10%" />
<col style="width: 12%" />
<col style="width: 8%" />
<col style="width: 4%" />
<col style="width: 12%" />
<col style="width: 12%" />
<col style="width: 2%" />
<col style="width: 10%" />
<col style="width: 5%" />
<col style="width: 7%" />
<col style="width: 12%" />
</colgroup>
<tbody>
<tr class="odd">
<td><strong>4.27</strong></td>
<td colspan="6"><strong>Test Temperature Margins</strong></td>
<td colspan="4"><strong>Mechanical</strong></td>
</tr>
<tr class="even">
<td><strong>Principle:</strong></td>
<td colspan="10">Components and systems shall be tested beyond allowable
flight temperature limits. The margin required for proto-flight thermal
vacuum testing is 10C beyond allowable flight temperature limits.
Acceptance test margin may be reduced to 5C. For actively controlled
systems with selectable/variable setpoints, the margin may be reduced to
5C. For active control systems with a fixed setpoint, margin shall be
demonstrated by increasing or decreasing (as appropriate) the heat load
(internal or external) by at least 30% and still maintain the control
temperature.</td>
</tr>
<tr class="odd">
<td><strong>Rationale:</strong></td>
<td colspan="10">(Note: This rule does not apply to cryogenic
systems.)</td>
</tr>
<tr class="even">
<td><strong>Phase:</strong></td>
<td colspan="10"><strong>&lt;A A B C D E F</strong></td>
</tr>
<tr class="odd">
<td><strong>Activities:</strong></td>
<td>N/A</td>
<td colspan="2">N/A</td>
<td>1. <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">Component</a>
proto-flight thermal vacuum test temperatures shall be specified with
the required margin as stated in principle above.</td>
<td>1. <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">Component</a>,
subsystem, and system proto-flight thermal vacuum test temperatures
shall be specified with the required margin as stated in principle
above.</td>
<td colspan="2">1. Components and systems shall undergo proto-flight
thermal vacuum testing with the required margin as stated in principle
above. Yellow and Red limits for flight temperature telemetry database
shall be consistent with actual proto-flight system thermal vacuum test
temperatures.</td>
<td colspan="2">1. Yellow and Red limits for flight temperature
telemetry database shall be consistent with actual proto-flight system
thermal vacuum test temperatures.</td>
<td>1. Yellow and Red limits for flight temperature telemetry database
shall be consistent with actual proto-flight system thermal vacuum test
temperatures.</td>
</tr>
<tr class="even">
<td><strong>Verification:</strong></td>
<td>N/A</td>
<td colspan="2">N/A</td>
<td>1. Verify at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">PDR</a>.</td>
<td>1. Verify at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">CDR</a>.</td>
<td colspan="2">1. Verify results of component and subsystem thermal
vacuum tests at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">PER</a>.<br />
2. Verify results of system thermal vacuum test at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">PSR</a>.<br />
3. Verify flight database limits at MRR and/or FRR.</td>
<td colspan="2"></td>
<td></td>
</tr>
<tr class="odd">
<td colspan="3"><p><strong>Revision Status:</strong></p>
<p>Baseline; Updated: Rev A</p></td>
<td colspan="6"><p><strong>Owner:</strong></p>
<p>Thermal Engineering Branch (545)</p></td>
<td colspan="2"><p><strong>Reference:</strong></p>
<p>GEVS 2.6</p></td>
</tr>
</tbody>
</table>

<table>
<colgroup>
<col style="width: 10%" />
<col style="width: 12%" />
<col style="width: 8%" />
<col style="width: 4%" />
<col style="width: 12%" />
<col style="width: 12%" />
<col style="width: 2%" />
<col style="width: 10%" />
<col style="width: 5%" />
<col style="width: 7%" />
<col style="width: 12%" />
</colgroup>
<tbody>
<tr class="odd">
<td><strong>4.28</strong></td>
<td colspan="6"><strong>Thermal Design Margin Verification</strong></td>
<td colspan="4"><strong>Mechanical</strong></td>
</tr>
<tr class="even">
<td><strong>Principle:</strong></td>
<td colspan="10">All subsystems/systems having a thermal design with
identifiable thermal design margins shall be subject to a Thermal
Balance Test at the appropriate assembly level per <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">GEVS</a>
Section 2.6.</td>
</tr>
<tr class="odd">
<td><strong>Rationale:</strong></td>
<td colspan="10">This test shall provide an empirical verification of
the subsystem/system's thermal design margin. In addition, steady state
temperature data from this test shall be used to validate
subsystem/system thermal math models (TMMs)</td>
</tr>
<tr class="even">
<td><strong>Phase:</strong></td>
<td colspan="10"><strong>&lt;A A B C D E F</strong></td>
</tr>
<tr class="odd">
<td><strong>Activities:</strong></td>
<td>1. Identify thermal balance test concepts.</td>
<td colspan="2">1. Include thermal balance test in environmental test
plan.</td>
<td>1. Identify preliminary thermal balance test architecture and
scope.</td>
<td>1. Identify specific thermal balance test architecture and
cases.</td>
<td colspan="2">1. Implement test.</td>
<td colspan="2">N/A</td>
<td>N/A</td>
</tr>
<tr class="even">
<td><strong>Verification:</strong></td>
<td>1. Verify at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">MCR</a>.</td>
<td colspan="2">1. Verify at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">MDR</a>.</td>
<td>1. Verify at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">SDR</a> and <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">PDR</a>.</td>
<td>1. Verify at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">CDR</a>.</td>
<td colspan="2">1. Verify at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">PER</a>.</td>
<td colspan="2">N/A</td>
<td>N/A</td>
</tr>
<tr class="odd">
<td colspan="3"><p><strong>Revision Status:</strong></p>
<p>Baseline; Updated: Rev A</p></td>
<td colspan="6"><p><strong>Owner:</strong></p>
<p>Thermal Engineering Branch (545)</p></td>
<td colspan="2"><p><strong>Reference:</strong></p>
<p>GEVS 2.6</p></td>
</tr>
</tbody>
</table>

<table>
<colgroup>
<col style="width: 10%" />
<col style="width: 12%" />
<col style="width: 8%" />
<col style="width: 4%" />
<col style="width: 12%" />
<col style="width: 12%" />
<col style="width: 2%" />
<col style="width: 10%" />
<col style="width: 5%" />
<col style="width: 7%" />
<col style="width: 12%" />
</colgroup>
<tbody>
<tr class="odd">
<td><strong>4.29</strong></td>
<td colspan="6"><strong>Thermal-Vacuum Cycling</strong></td>
<td colspan="4"><strong>Mechanical</strong></td>
</tr>
<tr class="even">
<td><strong>Principle:</strong></td>
<td colspan="10">All systems flying in unpressurized areas shall have
been subjected to a minimum of eight (8) thermal-vacuum test cycles
prior to installation on a spacecraft. Four (4) of these cycles may
include cycles at the subsystem or instrument level of assembly.</td>
</tr>
<tr class="odd">
<td><strong>Rationale:</strong></td>
<td colspan="10">This provides workmanship and performance verifications
at lower levels of assembly where required environments can be achieved
and reduces the risk to cost during spacecraft Integration and Test
(I&amp;T).</td>
</tr>
<tr class="even">
<td><strong>Phase:</strong></td>
<td colspan="10"><strong>&lt;A A B C D E F</strong></td>
</tr>
<tr class="odd">
<td><strong>Activities:</strong></td>
<td>1. Identify environmental test concept.</td>
<td colspan="2">1. Develop preliminary environmental test plan.</td>
<td>1. Update environmental test plan and put under configuration
control.</td>
<td>1. Update plan.</td>
<td colspan="2">1. Implement test cycles.</td>
<td colspan="2">N/A</td>
<td>N/A</td>
</tr>
<tr class="even">
<td><strong>Verification:</strong></td>
<td>1. Verify at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">MCR</a>.</td>
<td colspan="2">1. Verify at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">MDR</a>.</td>
<td>1. Verify at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">SDR</a> and <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">PDR</a>.</td>
<td>1. Verify at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">CDR</a>.</td>
<td colspan="2">1. Verify that all components have seen required testing
prior to spacecraft <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">I&amp;T</a> at
<a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">PER</a>.</td>
<td colspan="2">N/A</td>
<td>N/A</td>
</tr>
<tr class="odd">
<td colspan="3"><p><strong>Revision Status:</strong></p>
<p>Baseline; Updated: Rev A</p></td>
<td colspan="6"><p><strong>Owner:</strong></p>
<p>Office of Systems <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">Safety</a> and
Mission Assurance (300)</p></td>
<td colspan="2"><p><strong>Reference:</strong></p>
<p>GEVS 2.6.2.4.b</p></td>
</tr>
</tbody>
</table>

<table>
<colgroup>
<col style="width: 10%" />
<col style="width: 12%" />
<col style="width: 8%" />
<col style="width: 4%" />
<col style="width: 12%" />
<col style="width: 12%" />
<col style="width: 2%" />
<col style="width: 10%" />
<col style="width: 5%" />
<col style="width: 7%" />
<col style="width: 12%" />
</colgroup>
<tbody>
<tr class="odd">
<td><strong>5.04</strong></td>
<td colspan="6"><strong>Instrument Testing for
Multipaction</strong></td>
<td colspan="4"><strong>Instruments; Electrical</strong></td>
</tr>
<tr class="even">
<td><strong>Principle:</strong></td>
<td colspan="10">Active <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">RF</a>
components, such as radars, shall be designed and tested for immunity to
multipaction.</td>
</tr>
<tr class="odd">
<td><strong>Rationale:</strong></td>
<td colspan="10">Multipaction on <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">RF</a>
components that carry large amounts of <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">RF</a> power
can degrade overall performance and cause damage. Unless significant
design margin is demonstrated, small unit-to-unit variations make it
impossible to predict whether an <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">RF</a>
component is susceptible to multipaction.</td>
</tr>
<tr class="even">
<td><strong>Phase:</strong></td>
<td colspan="10"><strong>&lt;A A B C D E F</strong></td>
</tr>
<tr class="odd">
<td><strong>Activities:</strong></td>
<td>1. Determine the likely maximum power levels that components are
going to see and determine if multipaction could be an issue.</td>
<td colspan="2">1. Further refine power requirements and for components
that are likely to have multipaction issues.<br />
2. Begin vendor research to determine the extent of the issues.</td>
<td>1. Down select vendor and finalize component performance and power
requirements.<br />
2. Develop multipaction immunity verification plan.</td>
<td>1. Build engineering models of all components that could experience
multipaciton and perform testing on these components before and after
environmental testing.</td>
<td colspan="2">1. Build flight models and perform multipaction testing
on all flight components before and after environmental testing.</td>
<td colspan="2">1. Monitor instrument performance to determine if
component damage or degradation is occurring due to multipaction.</td>
<td>N/A</td>
</tr>
<tr class="even">
<td><strong>Verification:</strong></td>
<td></td>
<td colspan="2">1. Gather data from multiple vendors to have several
points of comparison.</td>
<td>1. Verify design and verification plan at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">PDR</a>.</td>
<td>1. Verify results of EM testing at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">CDR</a>.</td>
<td colspan="2">1. Verify results of testing at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">PSR</a>.</td>
<td colspan="2">1. Track long-term performance of instrument for trends
in overall performance and compare to expectations.</td>
<td>N/A</td>
</tr>
<tr class="odd">
<td colspan="3"><p><strong>Revision Status:</strong></p>
<p>Baseline</p></td>
<td colspan="6"><p><strong>Owner:</strong></p>
<p>Microwave Instrument Technology Branch (555)</p></td>
<td colspan="2"><strong>Reference:</strong></td>
</tr>
</tbody>
</table>

<table>
<colgroup>
<col style="width: 10%" />
<col style="width: 12%" />
<col style="width: 8%" />
<col style="width: 4%" />
<col style="width: 12%" />
<col style="width: 12%" />
<col style="width: 2%" />
<col style="width: 10%" />
<col style="width: 5%" />
<col style="width: 7%" />
<col style="width: 12%" />
</colgroup>
<tbody>
<tr class="odd">
<td><strong>5.05</strong></td>
<td colspan="6"><strong>Fluid Systems GSE</strong></td>
<td colspan="4"><strong>Instruments</strong></td>
</tr>
<tr class="even">
<td><strong>Principle:</strong></td>
<td colspan="10">Fluid systems <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">GSE</a> used to
pressurize flight systems shall be compliant with the fault tolerance
requirements of Rule 1.26.</td>
</tr>
<tr class="odd">
<td><strong>Rationale:</strong></td>
<td colspan="10">Fluid systems <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">GSE</a> is
usually at a pressure significantly above the flight systems final
pressure and therefore poses a risk of over-pressurizing the flight
system.</td>
</tr>
<tr class="even">
<td><strong>Phase:</strong></td>
<td colspan="10"><strong>&lt;A A B C D E F</strong></td>
</tr>
<tr class="odd">
<td><strong>Activities:</strong></td>
<td>1. Recognize the need for this specialized <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">GSE</a>.</td>
<td colspan="2">1. Determine if candidate <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">GSE</a> exist
and availability (versus a new build).</td>
<td>1. Secure agreement for existing <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">GSE</a>.<br />
2. Design new <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">GSE</a> and
procure components.</td>
<td>1. Recertify existing <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">GSE</a> before
use.<br />
2. Assemble and certify <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">GSE</a>.</td>
<td colspan="2">1. Use <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">GSE</a> to test
flight system (and components if necessary).</td>
<td colspan="2">N/A</td>
<td>N/A</td>
</tr>
<tr class="even">
<td><strong>Verification:</strong></td>
<td>1. Verify inclusion in proposal write-up and cost estimate.</td>
<td colspan="2">1. Present <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">GSE</a>
asessment at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">MDR</a>.</td>
<td>1. Verify through peer review and at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">PDR</a>.</td>
<td>1. Present certification at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">CDR</a>.</td>
<td colspan="2">1. Verify that procedures for <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">GSE</a> are
approved by <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">PER</a>.</td>
<td colspan="2">N/A</td>
<td>N/A</td>
</tr>
<tr class="odd">
<td colspan="3"><p><strong>Revision Status:</strong></p>
<p>Baseline; Updated: Rev D</p></td>
<td colspan="6"><p><strong>Owner:</strong></p>
<p>Cryogenics and Fluids Branch (552)</p></td>
<td colspan="2"><strong>Reference:</strong></td>
</tr>
</tbody>
</table>

<table>
<colgroup>
<col style="width: 10%" />
<col style="width: 12%" />
<col style="width: 8%" />
<col style="width: 4%" />
<col style="width: 12%" />
<col style="width: 12%" />
<col style="width: 2%" />
<col style="width: 10%" />
<col style="width: 5%" />
<col style="width: 7%" />
<col style="width: 12%" />
</colgroup>
<tbody>
<tr class="odd">
<td><strong>5.06</strong></td>
<td colspan="6"><strong>Flight Instrument Characterization
Standard</strong></td>
<td colspan="4"><strong>Instruments </strong></td>
</tr>
<tr class="even">
<td><strong>Principle:</strong></td>
<td colspan="10">Flight instruments and their components shall be
characterized for performance over their expected operating temperature
range.</td>
</tr>
<tr class="odd">
<td><strong>Rationale:</strong></td>
<td colspan="10">Detector performance falls of rapidly as a function of
temperature for both increasing and decreasing temperature.
Additionally, structural-thermal, and optical performance models need to
be correlated against tests.</td>
</tr>
<tr class="even">
<td><strong>Phase:</strong></td>
<td colspan="10"><strong>&lt;A A B C D E F</strong></td>
</tr>
<tr class="odd">
<td><strong>Activities:</strong></td>
<td>1. Test mission-enabling parts and components at room temperature
(extrapolate performance at other than room temperature).</td>
<td colspan="2">1. Test critical parts and components over the flight
operation temperature range, plus margin (no extrapolations) beyond
intended operating range.</td>
<td>1. Test flight-like subsystem and components over the flight
operation temperature range, plus margin beyond intended operating
range.</td>
<td>1. Test flight-like systems and components operating temperature
range, plus margin beyond intended operating range.</td>
<td colspan="2">1. Test flight system over operating temperature range,
plus margin beyond intended operating range.</td>
<td colspan="2">N/A</td>
<td>N/A</td>
</tr>
<tr class="even">
<td><strong>Verification:</strong></td>
<td>1. Test result reviewed by principal investigator.</td>
<td colspan="2">1. Test result reviewed by principal investigator and
science working group.</td>
<td>1. Review summary of results at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">PDR</a>.</td>
<td>1. Review summary of results at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">CDR</a>.</td>
<td colspan="2">1. Verify through peer review and at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">PER</a>.</td>
<td colspan="2">N/A</td>
<td>N/A</td>
</tr>
<tr class="odd">
<td colspan="3"><p><strong>Revision Status:</strong></p>
<p>Baseline</p></td>
<td colspan="6"><p><strong>Owner:</strong></p>
<p>Detector Systems Branch (553)</p></td>
<td colspan="2"><strong>Reference:</strong></td>
</tr>
</tbody>
</table>

<table>
<colgroup>
<col style="width: 10%" />
<col style="width: 12%" />
<col style="width: 8%" />
<col style="width: 4%" />
<col style="width: 12%" />
<col style="width: 12%" />
<col style="width: 2%" />
<col style="width: 10%" />
<col style="width: 5%" />
<col style="width: 7%" />
<col style="width: 12%" />
</colgroup>
<tbody>
<tr class="odd">
<td><strong>5.08</strong></td>
<td colspan="6"><strong>Laser Development Contamination
Control</strong></td>
<td colspan="4"><strong>Instruments</strong></td>
</tr>
<tr class="even">
<td><strong>Principle:</strong></td>
<td colspan="10">All flight laser development shall include an approved
laser-specific Contamination Control Plan (CCP).</td>
</tr>
<tr class="odd">
<td><strong>Rationale:</strong></td>
<td colspan="10"><a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">Component</a>
and/or system contamination has been identified as the contributing
cause in most laser failures to-date. There are unique requirements of a
laser <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">CCP</a> that
differ significantly from those of a general <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">CCP</a> (as
required by 4.01).</td>
</tr>
<tr class="even">
<td><strong>Phase:</strong></td>
<td colspan="10"><strong>&lt;A A B C D E F</strong></td>
</tr>
<tr class="odd">
<td><strong>Activities:</strong></td>
<td>N/A</td>
<td colspan="2">N/A</td>
<td>1. Review 'Laser Contamination Control Plan Outline' and prepare a
program specific <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">CCP</a>.</td>
<td>1. Implement <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">CCP</a> at the
component level.</td>
<td colspan="2">1. Continue implementation of the <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">CCP</a> through
launch.</td>
<td colspan="2">1. Continue any post-launch aspects of the <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">CCP</a>.</td>
<td>N/A</td>
</tr>
<tr class="even">
<td><strong>Verification:</strong></td>
<td>N/A</td>
<td colspan="2">N/A</td>
<td>1. Review documentation at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">PDR</a>.</td>
<td>1. Verify at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">CDR</a>.</td>
<td colspan="2">1. Verify at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">PER</a> and <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">PSR</a>.</td>
<td colspan="2">1. Verify post-launch summary of activities.</td>
<td>N/A</td>
</tr>
<tr class="odd">
<td colspan="3"><p><strong>Revision Status:</strong></p>
<p>Baseline</p></td>
<td colspan="6"><p><strong>Owner:</strong></p>
<p>Laser and Electronic Optics Branch (554)</p></td>
<td colspan="2"><strong>Reference:</strong></td>
</tr>
</tbody>
</table>

<table>
<colgroup>
<col style="width: 10%" />
<col style="width: 12%" />
<col style="width: 8%" />
<col style="width: 4%" />
<col style="width: 12%" />
<col style="width: 12%" />
<col style="width: 2%" />
<col style="width: 10%" />
<col style="width: 5%" />
<col style="width: 7%" />
<col style="width: 12%" />
</colgroup>
<tbody>
<tr class="odd">
<td><strong>5.09</strong></td>
<td colspan="6"><strong>Cryogenic Pressure Relief</strong></td>
<td colspan="4"><strong>Instruments</strong></td>
</tr>
<tr class="even">
<td><strong>Principle:</strong></td>
<td colspan="10">Stored cryogen systems (and related GSE) shall be
compliant with the fault tolerance requirements of Rule 1.26.</td>
</tr>
<tr class="odd">
<td><strong>Rationale:</strong></td>
<td colspan="10">Credible, albeit unintended, conditions can lead to
potential system over-pressurization.</td>
</tr>
<tr class="even">
<td><strong>Phase:</strong></td>
<td colspan="10"><strong>&lt;A A B C D E F</strong></td>
</tr>
<tr class="odd">
<td><strong>Activities:</strong></td>
<td>1. Identify personnel or organization to conduct the appropriate
analyses during subsequent phases.</td>
<td colspan="2">1. Identify underlying assumptions and conduct
preliminary emergency venting analysis.</td>
<td>1. Refine analysis and identify candidate relief devices.</td>
<td>1. Finalize analysis and include relief devices in design. Procure
devices and test them at the component level.</td>
<td colspan="2">1. Include the devices in the hardware build-up and test
function during build-up as appropriate.<br />
2. Review flight hardware and <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">GSE</a>
configurations prior to testing to ensure that relief paths are not
circumvented.</td>
<td colspan="2">N/A</td>
<td>N/A</td>
</tr>
<tr class="even">
<td><strong>Verification:</strong></td>
<td>1. Grass-root cost estimate to include cryogenic engineering.</td>
<td colspan="2">1. Ensure venting analysis included in larger cryogenic
system analysis report/summary that is reviewed by the system engineer
and/or review team.</td>
<td>1. Review at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">PDR</a>.</td>
<td>1. Review at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">CDR</a>.</td>
<td colspan="2">1. Review at <a
href="http://gsfcrules.gsfc.nasa.gov/rules/glossary.pdf">PER</a>.</td>
<td colspan="2">N/A</td>
<td>N/A</td>
</tr>
<tr class="odd">
<td colspan="3"><p><strong>Revision Status:</strong></p>
<p>Baseline; Updated: Rev D</p></td>
<td colspan="6"><p><strong>Owner:</strong></p>
<p>Cryogenics and Fluids Branch (552)</p></td>
<td colspan="2"><strong>Reference:</strong></td>
</tr>
</tbody>
</table>

**GLOSSARY AND ACRONYM GUIDE**

Anomaly An unanticipated or unpredicted behavior that occurs as a
discrete episode

ASIC Application Specific Integrated Circuit

Assembly A functional subdivision of a component consisting of parts or
subassemblies that perform functions necessary for the operation of a
component as a whole (Ref: GEVS 1-6)

ACS Attitude Control System

BOL Beginning of Life

Breadboard A model used to test hardware at TRL 4 or 5 (See TRL levels.)

Catastrophic Hazard A condition that may cause death or permanently
disabling injury, major system or facility destruction on the ground, or
vehicle during the mission.

CCB Configuration Control Board

CCP Contamination Control Plan

CDR Critical Design Review

CI Configuration Item

CM Configuration Management. A management discipline applied over the
product\'s life cycle to provide visibility and to control performance
and functional and physical characteristics (Ref: NPR 7120.5b)

Component A functional subdivision of a subsystem and generally a
self-contained combination of items performing a function necessary for
the subsystem's operation (Ref: GEVS 1-6)

Credible Capable of being believed (A plausible likelihood of failure)

Critical Hazard A condition that may cause severe injury or occupational
illness, or major property damage to facilities, systems, or flight
hardware.

Debug Features With the best of intentions of helping to debug software
and/or hardware problems, there exists a feature

(Maybe Advertised or that is not needed by the operation software, but
was accidentally or intentionally left in the code for

Unadvertised, Maybe debug purposes.

Documented or

Undocumented, Maybe

Tested or Untested)

DR Decommissioning Review

EEE Electrical Engineering

EGSE Electrical Ground Support Equipment

Element A portion of a hardware or software unit that is logically
discrete

EMC Electromagnetic Compatibility

End-to-end test A test performed on the integrated ground and flight
system, including all elements of the payload, its control, stimulation,
communications, and data processing (Ref: GEVS 1-5)

ETU Engineering Test Unit

EOL End of Life

FDAC Failure Detection and Correction

FOR Flight Operations Review

FOS Factors of Safety

FOV Field of Vision

FPGA Field Programmable Gate Arrays

FSW Flight Software

GEVS General Environmental Verification Specification

GMF Geomagnetic Field

GN&C Guidance, Navigation, and Control

GPR Goddard Policy Requirement

GSE Ground Support Equipment

Heritage hardware Hardware from a previous project, program, or mission

High fidelity Addresses form, fit, and function. Equipment that can
simulate and validate all system specifications within a laboratory
setting (Ref: Defense Acquisition University)

High-level objectives High level objectives -- science or technology
validation objectives that define the purpose of the mission. Also Level
0 requirements

HW Hardware

ICD Interface Control Document

ICR Initial Confirmation Review

ITU Integrated Test Unit

I&T Integration and Testing

KDP The event at which the Decision Authority determines the readiness
of a program/project to progress to the next phase of the life cycle (or
to the next KDP).

LRR Launch Readiness Review

Level 1 Requirements A Project's fundamental and basic set of
requirements levied by the Program or Headquarters on the Project. (Ref:
GPG 7120.5) Level 1 Requirements are sufficient to define the scope of
scientific or technology validation objectives and describe the
measurements required to achieve these objectives. Level 1 Requirements
should also define success criteria for an expected mission and a
minimum mission

Level 2 Requirements Requirements allocated to mission segments
(instruments, spacecraft bus, ground system, and launch vehicle). Level
2 Requirements also envelop Mission Assurance Requirements and technical
resource allocations

Level 3 Requirements Subsystem requirements. Level 3 Requirements
include instrument specifications and interface definitions

Level 4 Requirements Component requirements. Level 4 Requirements cover
all hardware and software components to be designed or procured, such as
optics, filter wheels, and CCDs

Margin The amount by which hardware capability exceeds requirements
(Ref: GEVS 1-7)

MAR Mission Assurance Requirement

MAE Materials Assurance Engineer

MDR Mission Definition Review

MCR Mission Concept Review

Meaningless Code During the development process, modifications are made
to the software such that code exists, but doesn't do any meaningful
work. For example, a variable is declared and assigned a value, but
never used.

Mission-critical Item or function that must retain its operational
capability to assure no mission failure (See Mission success) (Ref: MSFC
SMA Directorate)

Mission success Those activities performed in line and under the control
of the program or project that are necessary to provide assurance that
the program or project will achieve its objectives. The mission success
activities will typically include risk assessments, system safety
engineering, reliability analysis, quality assurance, electronic and
mechanical parts control, software validation, failure
reporting/resolution, and other activities that are normally part of a
program or project work structure (Ref: NPR 7120.5b)

MOR Mission Operations Review

M&P Materials and Processes

OOB Out-of-band

ORR Operational Readiness Review

OTS Off-the-shelf

Payload An integrated assemblage of modules, subsystems, etc., designed
to perform a specified mission in space (Ref: GEVS 1-7)

PDR Preliminary Design Review

PER Pre-Environmental Review

Performance Verification Determination by test, analysis, or a
combination of the two that the payload element can operate as intended
in a particular mission (Ref: GEVS 1-7)

PLD Programmable Logic Device

Project execution The performance with respect to schedule, cost, and
other key managerial metrics and considerations.

Prototype hardware Hardware of a new design. It is subject to a design
qualification test program; it is not intended for flight (Ref: GEVS
1-6)

PSR Pre-Ship Review

RF Radio Frequency

RHA Radiation Hardness Assurance

Safe Hold Mode A control mode designed to provide a spacecraft with a
mode to preserve its health and safety while recovery efforts are
undertaken

Safety Freedom from those conditions that can cause death, injury,
occupational illness, damage to or loss of equipment or property, or
damage to the environment (Ref: NPR 7120.5b)

SAR System Acceptance Review

S/C Spacecraft

SDR System Design Review

SEMP Systems Engineering Management Plan

Simulation A synthetic representation of the characteristics of real
world system or situation, typically by interfacing controls and
displays (operational or simulated) and positions of the system with a
computer (Ref: MIL-HDBK-220B)

SMO Systems Management Office

SORR Science Operations Readiness Review

Spare part A replacement part (reparable or expendable supplies)
purchased for use in the maintenance of systems such as aircraft, launch
vehicles, spacecraft, satellites, ground communication systems, ground
support equipment, and associated test equipment. It can include
line-replaceable units, orbit-replaceable units, shop-replaceable units,
or piece parts used to repair subassemblies (Ref: NPR 5900.1)

SPP Spare Parts Program

SRR System Readiness Review

Subsystem A functional subdivision of a payload consisting of two or
more components (Ref: GEVS 1-6)

System The combination of elements that function together to produce the
capability required to meet a need. The elements include all hardware,
software, equipment, facilities, personnel, processes, and procedures
needed for this purpose (Ref: NPR 7120.5, NASA Program and Project
Management Processes and Requirements)

System Integrity The ability of a system to maintain its form and
function (See System)

SW Software

T&C Telemetry and Command

T&M Time and Materials

Test Features (Maybe With the best of intentions of helping to test and
validate the software, there exists a feature that is not

Advertised or needed by the operational software, but is desirable to
have for testing purposes.

Unadvertised, Maybe

Documented or

Undocumented, Maybe

Tested or Untested)

TLYF Test Like You Fly

TM Torque Margin

TRL Technology Readiness Level - A systematic metric/measurement system
that supports assessments of the maturity of a particular technology and
the consistent comparison of maturity between different types of
technology. NASA recognizes nine technological readiness levels:

> TRL 9 Actual system "flight proven" through successful mission
> operations
>
> TRL 8 Actual system completed and "flight qualified" through test and
> demonstration (ground or flight)
>
> TRL 7 System prototype demonstration in a space environment
>
> TRL 6 System/subsystem model or prototype demonstration in a relevant
> environment (ground or space)
>
> TRL 5 Component and/or breadboard validation in relevant environment
>
> TRL 4 Component and/or breadboard validation in laboratory environment
>
> TRL 3 Analytical and experimental critical function and/or
> characteristic proof-of-concept
>
> TRL 2 Technology concept and/or application formulated
>
> TRL 1 Basic principles observed and reported
>
> (Ref: Space Science Enterprise Management Handbook, Appendix E 11)

Traceability Matrix A matrix demonstrating the flow-down of requirements
to successively lower levels

TSR Technical Status Review

Unreachable Code A section of code exists that can never be executed
because pre-conditions will never be met. For

(unintentional) example, a properly developed function will validate all
parameters to ensure the function doesn't perform any illegal actions.
However, it is possible to write the larger program such that it will
never call the function with an improper parameter. Therefore, the error
condition checks inside the function are really unreachable code.

Unreachable Code During the development process, modifications are made
to the software while trying to define/debug a

(intentional) problem and the resulting solution has code that is
unreachable.  For example, an unconditional return from a function was
inserted prior to the end of the function.

Unused Code During a development effort over an extended period of time
with multiple developers, there exists

(unintentional) unused code in the form of a file, a function, a
variable, a parameter, an enumeration, a constant, an external
declaration, a define, a macro, a return code, or a type that is no
longer used.

Unused Code During the evolution of a software development effort, a
requirement or group of requirements is deleted

(intentional) which results in code that is no longer needed by the
surviving set of requirements and an intentional decision is made to
simply leave the unneeded code alone and don\'t advertise it exists
(remove database definitions of commands and telemetry as necessary). 
This results in code that could potentially be executed that has never
been tested.

Unused Design In an effort to promote software reuse an OS API is
developed for application tasks to use. As part of a Capabilities new
project the OS API is re-hosted to a new OS (which features that are
actually needed are unknown

> early in a development effort). As part of the new project, there
> exist functions in the API that are not needed.

Unneeded Features Commercial software has plenty of capabilities and
features the marketing folks use to sway developers

in Commercial Software to choose their products. In reality, some of
those features will not be needed.

Unused Reuse In an effort to save schedule and cost a software library
component is reused (by definition, a library

Capabilities component is fully tested and ready to be used -- but may
not have been used/tested on the H/W platform of the new project).
However, certain capabilities of the library component are not needed by
the new project.

Validation Proof that Operations Concept, Requirements, and Architecture
and Design will meet Mission Objectives, that they are consistent, and
that the "right system" has been designed. May be determined by a
combination of test or analysis. Generally accomplished through trade
studies and performance analysis by Phase B and through tests in Phase D
(Ref: GPG 7120.5)

Verification Proof of compliance with requirements and that the system
has been "designed and built right." May be determined by a combination
of test, analysis, and inspection (Ref: GPG 7120.5)

+----------+---------+------------------------------------------------+
| **Re     | **Ef    | **Description**                                |
| vision** | fective |                                                |
|          | Date**  |                                                |
+----------+---------+------------------------------------------------+
| **       | **10-D  |                                                |
| Baseline | ec-04** |                                                |
| R        |         |                                                |
| elease** |         |                                                |
+----------+---------+------------------------------------------------+
| **A**    | **30-M  | \[P. 10\] User\'s Guide: removed text          |
|          | ay-05** | examples, replaced with bullets explaining     |
|          |         | what general information goes into each rule   |
|          |         | section.                                       |
+----------+---------+------------------------------------------------+
|          |         | Addition of Change History page (against 12/10 |
|          |         | baseline rulebook).                            |
+----------+---------+------------------------------------------------+
|          |         | \[P. 7\] Revised Front Matter Graphics         |
|          |         | (architectural diagram - Figure 2).            |
+----------+---------+------------------------------------------------+
|          |         | \[Rule 1.17, Glossary\] 1. Added \"credible\"  |
|          |         | to Principle, Phase B, and Phase C; 2. Added   |
|          |         | \"credible\" definition to Glossary.           |
+----------+---------+------------------------------------------------+
|          |         | \[Rule 1.22\] Phase C revision - Replaced      |
|          |         | existing language with: \"Demonstrate that the |
|          |         | method for drying the wetted system has been   |
|          |         | validated by test on an equivalent or similar  |
|          |         | system.\"                                      |
+----------+---------+------------------------------------------------+
|          |         | \[Rule 1.14\] Revision to the Principle and    |
|          |         | Rationale.                                     |
|          |         |                                                |
|          |         | [Revised Principle]{.underline}: Telemetry     |
|          |         | coverage shall be acquired during all          |
|          |         | mission-critical events. *Continuous telemetry |
|          |         | and command capability shall be maintained     |
|          |         | during launch and until the spacecraft has     |
|          |         | been established on-orbit in a stable,         |
|          |         | power-positive mode.\"*                        |
+----------+---------+------------------------------------------------+
|          |         | \[Rule 1.06\] Added table 1.06-1 to website    |
|          |         | rule set.                                      |
+----------+---------+------------------------------------------------+
|          |         | \[Rule 3.07\] Added table 3.07-1 to website    |
|          |         | rule set.                                      |
+----------+---------+------------------------------------------------+
|          |         | \[Rules: 2.01, 2.07, 2.11, 4.01, 4.03, 4.09,   |
|          |         | 4.10, 4.11, 4.12, 4.13, 4.14, 4.15, 4.23,      |
|          |         | 4.25, 4.27, 4.28, 4.29\]                       |
|          |         |                                                |
|          |         | 1\. Corrected GSFC-STD-7000 (GEVS) references  |
|          |         | in GSFC-STD-1000.                              |
|          |         |                                                |
|          |         | 2\. Created reference PDFs.                    |
|          |         |                                                |
|          |         | 3\. Added reference links.                     |
+----------+---------+------------------------------------------------+
|          |         | \[Rule 3.09\] Added web links to source        |
|          |         | material (NPR 7150.2, GPG 8700.5).             |
+----------+---------+------------------------------------------------+

+----------+---------+------------------------------------------------+
| **Re     | **Ef    | **Description**                                |
| vision** | fective |                                                |
|          | Date**  |                                                |
+----------+---------+------------------------------------------------+
| **B**    | **30-Ju | \[P. 6\] Updated Introduction.                 |
|          | ne-06** |                                                |
+----------+---------+------------------------------------------------+
|          |         | \[P. 9\] Revised Figure 3 Lifecycle Chart -    |
|          |         | Removed "from SMO"                             |
+----------+---------+------------------------------------------------+
|          |         | \[P. 10\] Updated User's Guide.                |
+----------+---------+------------------------------------------------+
|          |         | New Systems Engineering Rule: 1.04 -- System   |
|          |         | Modes.                                         |
+----------+---------+------------------------------------------------+
|          |         | New Systems Engineering Rule: 1.08 -- End to   |
|          |         | End Testing.                                   |
+----------+---------+------------------------------------------------+
|          |         | \[Rule 1.14\] Revised Principle, Rationale,    |
|          |         | Activities (Phase E), and Verification (Phases |
|          |         | pre-A, A, C  E).                              |
|          |         |                                                |
|          |         | [Revised Principle:]{.underline} *Continuous   |
|          |         | telemetry and command coverage shall be        |
|          |         | maintained during all mission-critical events. |
|          |         | Mission-critical events shall be defined to    |
|          |         | include separation from the launch vehicle;    |
|          |         | power-up of major components or subsystems;    |
|          |         | deployment of mechanisms and/or                |
|          |         | mission-critical appendages; and all planned   |
|          |         | propulsive maneuvers required to establish     |
|          |         | mission orbit and/or achieve safe attitude.*   |
|          |         |                                                |
|          |         | [Revised Rationale:]{.underline} *With         |
|          |         | continuous telemetry and command capability,   |
|          |         | operators can prevent anomalous events from    |
|          |         | propagating to mission loss. Also, flight data |
|          |         | will be available for anomaly investigations.* |
+----------+---------+------------------------------------------------+
| **B.1**  | **29-Se | Formatting changes to Rules 1.17, 2.02, 2.17,  |
|          | pt-06** | 3.03, 3.06, 3.07, 3.09, 3.10, 3.14, 3.15,      |
|          |         | 4.07, 4.15, 4.20, 4.28, Page 2, Table 307-1    |
|          |         | and Glossary "Space Part"                      |
+----------+---------+------------------------------------------------+
|          |         | Typographical errors corrected on Rule 1.28,   |
|          |         | 3.10, 4.08, 4.18, 4.23, 4.26                   |
+----------+---------+------------------------------------------------+
|          |         | Replaced Page 2 and 3 of Table 3.07-1          |
+----------+---------+------------------------------------------------+
| **C**    | **30-O  | Rule 1.14 -- Revised Language in "Principle"   |
|          | ct-06** | Statement                                      |
+----------+---------+------------------------------------------------+
|          |         | Rule 1.26 -- Major Revision                    |
+----------+---------+------------------------------------------------+
|          |         | New Systems Engineering Rule: 1.29 Leakage of  |
|          |         | Hazardous Propellant                           |
+----------+---------+------------------------------------------------+
|          |         | Glossary -- Added definitions for critical and |
|          |         | catastrophic hazards                           |
+----------+---------+------------------------------------------------+
|          |         | Table of Contents -- Updated to Reflect        |
|          |         | Changes for Rules 1.26, 1.29                   |
+----------+---------+------------------------------------------------+
| **C.1**  | **12-D  | New Systems Engineering Rule: 1.09 Test Like   |
|          | ec-06** | You Fly                                        |
+----------+---------+------------------------------------------------+
|          |         | New Software Rule: 3.02 Elimination of Dead    |
|          |         | Software Code                                  |
+----------+---------+------------------------------------------------+
|          |         | Table of Contents -- Updated to Reflect        |
|          |         | Changes/Insertion for Rules 1.09, 3.02         |
+----------+---------+------------------------------------------------+
|          |         | Glossary -- Added Definitions for Dead         |
|          |         | Software/Code & Acronym for "Test Like You     |
|          |         | Fly"                                           |
+----------+---------+------------------------------------------------+
|          |         | Table of Contents -- Typographical error in    |
|          |         | Rule 1.08 title corrected                      |
+----------+---------+------------------------------------------------+
|          |         | \[Rule 1.14\] Revised Verification for Phases  |
|          |         | pre-A  E.                                     |
+----------+---------+------------------------------------------------+
| **C.2**  | **12-D  | Introduction -- Corrected language for GPR     |
|          | ec-06** | 8070.4                                         |
+----------+---------+------------------------------------------------+
|          |         | Table 1.06-1 -- Deleted "RF Link" Margin       |
+----------+---------+------------------------------------------------+

  --------------- ----------------- ----------------------------------------------
  **Revision**    **Effective       **Description**
                  Date**            

  **D**           **01-March-08**   Table of Contents -- Revised to Reflect Rev D
                                    Changes

                                    Rule 1.03 -- Revised "Principle" Statement

                                    Rule 1.11 -- Revised "Principle" Statement

                                    Rule 1.16 -- Revised "Principle" Statement

                                    Rule 3.07 -- Revised "Title" and "Principle"
                                    Statement

                                    Rule 5.05 -- Revised "Principle" Statement

                                    Rule 5.09 -- Revised "Principle" Statement

                                    New Systems Engineering Rule: 1.18 Physically
                                    Co-Located Redundant Elements

                                    New Systems Engineering Rule: 1.23 Spacecraft
                                    "OFF" Command

                                    New Systems Engineering Rule: 1.25 Redundant
                                    Systems

                                    New Electrical Engineering Rule: 2.08
                                    Secondary Circuit Failures

                                    New Electrical Engineering Rule: 2.18
                                    Redundant Functions

                                    New Electrical Engineering Rule: 2.19 Multiple
                                    Circuit Power Bus Loss

                                    New Electrical Engineering Rule: 2.20 Single
                                    Control Line Dependency

                                    New Electrical Engineering Rule: 2.21 Gross
                                    Failure of Integrated Circuits

                                    New Electrical Engineering Rule: 2.22 Corona
                                    Region Testing of High Voltage Equipment

                                    Table 3.07-1 -- Revised first paragraph

                                    
  --------------- ----------------- ----------------------------------------------

**This page intentionally left blank.**