NASA GPR 7123.1

Abstract

<strong>PURPOSE</strong> <br>This directive outlines a process for the systems engineering of Goddard Space Flight Center (GSFC) Missions. The intent is to outline a set of requirements that provide a consistent method for performing systems engineering across GSFC projects. The requirements for systems engineering outlined in this directive are universal principles that, when followed, should result in sound systems. <br>This directive implements NPR 7123, NASA Systems Engineering Processes and Requirements. The NPR guidelines and requirements have been tailored and refined to support the GSFC mission. A mapping of the 17 NPR systems engineering processes to this guidance is presented in Appendix D. <br>This directive defines the minimum set of systems engineering functions for GSFC Missions. These functions, from a product perspective, are defined and described. All phases of the mission life-cycle, and systems of interest, from mission, through major system element, to subsystem, to component or assembly are considered. The systems engineering functions described in this directive are universal and generally apply across the board. What varies from project to project is who does them, to what degree they are performed, and to what degree there is insight by the customer as to how the functions are accomplished. <br>This directive is concerned with what must be done, along with insight into why it is done, rather than how it is done. The required functions are described by <em>shall</em> statements in this GPR. The referenced NASA Systems Engineering Handbook, SP-2007-6105 Rev 1, provides detailed guidance on how to perform systems engineering functions. Tailoring of how, when, where, and by whom these functions are performed is described in a project unique Systems Engineering Management Plan (SEMP). An example of a SEMP outline is listed in Appendix B. <br>Principles for tailoring systems engineering activities are listed in Appendix C. The tailoring guidelines address who performs the functions and to what degree the functions are performed. <br>This directive defines systems engineering terminology (Section P.10). Roles and Responsibilities (Section 1) and the systems engineering life-cycle (Section 2) are defined. Communications and the systems engineering team (Section 3) are discussed. Systems engineering functions and products, and critical function flow and process operations, are discussed in Section 4. Section 5 discusses Configuration Management (CM) and Documentation. The required plan for systems engineering implementation is given in section 6. Appendix A contains a list of the systems engineering requirements defined within this directive. It may be used as a sample validation matrix. <br><strong>APPLICABILITY</strong> <br>This systems engineering procedure shall be applied to all GSFC managed Flight Systems & Ground Support (FS&GS) projects that follow NPR 7120.5D, <em>NASA Space Flight Program and Project Management.</em> This procedure applies to all missions (i.e. projects) for which GSFC is responsible, as well as to deliverable instruments, spacecraft and other GSFC mission products. It applies to all concept studies, mission formulation, and implementation sub-processes, including mission operations, decommissioning and disposal. <br>This GPR implements the requirements of NPR 7123.1, as tailored and refined to support the GSFC mission. Projects specifically excluded from the application of this GPR are Basic and Applied Research (BAR), Advanced Technology Development (ATD), Institutional Projects (IP), and Institutional IT Projects. <br>For systems that contain software, the mission team shall ensure that software acquired or developed internally within NASA complies with NPD 2820.1, NASA Software Policy, and NPR 7150.2, NASA Software Engineering Requirements. <br>This GPR applies to each project going forward from the current state of the project's life-cycle. There is no intent to require retroactive compliance with activities that have already occurred in the project's life-cycle.