1、 NASA Procedural Requirements NPR: 7120.7 Effective Date: November 3, 2008 Expiration Date: November 3, 2013 NASA Information Technology and Institutional Infrastructure Program and Project Management Requirements Responsible Office: Office of the Chief Engineer Provided by IHSNot for ResaleNo repro
2、duction or networking permitted without license from IHS-,-,-TABLE OF CONTENTS PREFACE CHAPTER 1. Introduction 1.1 Background 1.2 Overview of Management Processes 1.3 Document Structure CHAPTER 2. NASA Life Cycles for Institutional Infrastructure and Information Technology Programs and Projects 2.1
3、Defining Programs and Projects 2.2 Program/Project Oversight and Decision Authority 2.3 IT Governance 2.4 Program Life Cycle 2.5 Project Life Cycles 2.6 Program and Project Reviews 2.7 Independent Assessment CHAPTER 3. Program and Project Management Roles and Responsibilities 3.1 Roles and Responsib
4、ilities 3.2 Program and Project Managers 3.3 Process for Handling Dissenting Opinions 3.4 Information Technology Authority CHAPTER 4. Information Technology (IT) Program and Project Requirements by Phase 4.1 IT Programs Formulation Phase 4.2 IT Programs Implementation Phase 4.3 IT Projects Pre-Phase
5、 A 4.4 IT Projects Phase A 4.5 IT Projects Phase B 4.6 IT Projects Phase C 4.7 IT Projects Phase D 4.8 IT Projects Phase E 4.9 IT Projects Phase F CHAPTER 5. Other Mission Support Investment (OMSI) Program and Project Requirements by Phase 5.1 OMSI Programs Formulation Phase 5.2 OMSI Programs Implem
6、entation Phase 5.3 OMSI Projects Pre-Phase A 5.4 OMSI Projects Phase A 5.5 OMSI Projects Phase B 5.6 OMSI Projects Phase C 5.7 OMSI Projects Phase D ii Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-5.8 OMSI Projects Phase E 5.9 OMSI Projects Phase
7、F CHAPTER 6. Required Gate Products at Key Decision Points 6.1 Gate Products 6.2 Waiver Approval Authority APPENDIX A. Definitions APPENDIX B. Acronyms APPENDIX C. Formulation Authorization Document Template APPENDIX D. Program Commitment Agreement Template APPENDIX E. Program Plan Template APPENDIX
8、 F. Project Plan Template APPENDIX G. Technical Review Entrance and Success Criteria for Information Technology ProjectsDISTRIBUTION: NODIS iii Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-PREFACE P.1 PURPOSE This document establishes the requirem
9、ents by which NASA will formulate and execute information technology and institutional infrastructure programs and projects, consistent with the governance model contained in the NASA Governance and Strategic Management Handbook (NPD 1000.0). P.2 APPLICABILITY a. This NPR is applicable to NASA Headq
10、uarters and NASA Centers, including Component Facilities and Technical and Service Support Centers. b. This NPR is applicable to all NASA information technology and institutional infrastructure programs and projects to include the development of information technology capabilities, real property (co
11、nstruction of facilities and environmental compliance and restoration), and other mission support investments, as described in section 1.1.2. P.3 AUTHORITY a. 42 U.S.C. 2473(c) (1), Section 203(c) (1) of the National Aeronautics and Space Act of 1958, as amended. b. NPD 7120.4, Program/Project Manag
12、ement. P.4 APPLICABLE DOCUMENTS a. NID-9250, Identifying Capital Assets and Capturing Their Cost. b. NPD 1000.0, NASA Governance and Strategic Management Handbook. c. NPD 1000.3, The NASA Organization. d. NPD 1382.17, NASA Privacy Policy. e. NPD 1440.6, NASA Records Management. f. NPD 2800.1, Managi
13、ng Information Technology. g. NPD 2820.1, NASA Software Policy. h. NPD 7120.4, Program/Project Management. i. NPD 8820.2, Design and Construction of Facilities. iv Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-j. NPR 1441.1, NASA Records Retention
14、Schedules. k. NPR 2800.1, Managing Information Technology. l. NPR 2810.1, Security of Information Technology. m. NPR 2830.1, NASA Enterprise Architecture Procedures. n. NPR 4300.1, NASA Personal Property Disposal Procedural Requirements. o. NPR 7150.2, NASA Software Engineering Requirements. p. NPR
15、8000.4, Risk Management Procedural Requirements. q. NPR 8590.1, NASA Environmental Compliance and Restoration (ECR) Program. r. NPR 8820.2, Facility Project Implementation Guide. P.5 MEASUREMENT/VERIFICATION Compliance with this document is verified by submission to cognizant NASA officials, at key
16、decision points, of the gate products identified in this document. P.6 CANCELLATION NPR 7120.5C, NASA Program and Project Management Processes and Requirements, dated March 2005, is cancelled for Institutional Infrastructure Programs and Projects. /S/ Michael G. Ryschkewitsch Chief Engineer v Provid
17、ed by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-CHAPTER 1. Introduction 1.1 Background 1.1.1 NASA distinguishes programs and projects in three investment areas or product lines: Research and Technology, Space Flight, and Information Technology (IT) and ins
18、titutional infrastructure. This document establishes the management requirements for formulating, approving, implementing, and evaluating NASA IT and institutional infrastructure programs and projects consistent with the governance model contained in NPD 1000.0, NASA Governance and Strategic Managem
19、ent Handbook. 1.1.2 This NPR identifies four types of IT and institutional infrastructure investments: a. IT - Any equipment or interconnected system(s) or subsystem(s) of equipment that is used in the automatic acquisition, storage, analysis, evaluation, manipulation, management, movement, control,
20、 display, switching, interchange, transmission, or reception of data or information by the Agency. (1) NASA distinguishes between highly specialized IT and IT that is not highly specialized. Highly specialized IT is defined in Appendix A, Definitions, and is subject to NPR 7120.5, NASA Space Flight
21、Program and Project Management Requirements, or to NPR 7120.8, NASA Research and Technology Program and Project Management Requirements, depending on the program or project content. (2) IT programs and projects that are not highly specialized IT are subject to the requirements of this document, unle
22、ss granted a waiver by the NASA Chief Information Officer (CIO) or the CIO of the Center making the investment, if they meet either of the following criteria: (a) If the program or project includes the development of new IT systems or capabilities: $500K or greater total development and implementati
23、on cost or affects more than one Center. (b) If the program or project includes modification to or enhancement of existing IT systems or capabilities: $500K or greater total modification/enhancement cost, regardless of how many Centers are affected. (3) The development, modification, and enhancement
24、 of Web-based applications (here meaning software applications that support an Internet browser as a user interface) as a class are subject to this document if they meet one of the above criteria. The development, modification, and enhancement of Web sites and Web-based questionnaires that are used
25、solely to disseminate or collect information are not subject to this document. 1 Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-(4) For IT that is not highly specialized, the NASA CIO or the CIO of the implementing Center may require a program or pr
26、oject to comply with the requirements of this document even if the program or project does not meet the above criteria. Such a decision may be made, for example, for reasons related to high risk, high importance, or high visibility of the program or project. In making this determination, the CIO wil
27、l consult and coordinate with the office that is sponsoring the program or project. In the event of a disagreement, the sponsoring office may appeal the CIOs or delegees determination. If not resolved at a lower level, the NASA Associate Administrator will make the final determination. The right of
28、appeal shall not be construed as a right to delay or avoid the CIOs authority, i.e., appeals must be pursued expeditiously and responsive interim plans put in place pending hearing of the appeal. (5) It is possible that programs and projects governed by NPR 7120.5, or NPR 7120.8, will have systems u
29、nder development with both highly specialized and not highly specialized IT components, which must be developed and integrated under a unified management structure to ensure technical and programmatic success. Such IT components embedded in programs and projects will also comply with policies and ot
30、her technical requirements to ensure systems and capabilities being developed align with Agency requirements and direction for IT architectures, policies, procedures, standards, guidelines, and practices. The Office of the CIO will work with the Mission Directorate or Mission Support Office responsi
31、ble for the program or project to identify such embedded IT components and define boundaries and interfaces for inclusion in IT management processes. The Office of the CIO will also coordinate with the appropriate Governing Body required by NPR 7120.5, or NPR 7120.8, as described in section 2.3 of t
32、his document to reflect those interactions. (6) The Mission Directorate or Mission Support Office responsible for a program or project and the Office of the CIO will come to agreement concerning whether particular instances of IT included in the program or project are highly specialized or not highl
33、y specialized. The agreements shall be documented in the program plan or project plan (or other appropriate document) encompassing the systems of concern. In the event that disagreements cannot be resolved at a lower level, the NASA Associate Administrator will make the final determination. b. Const
34、ruction of Facilities (CoF) - Construction and renovation of facilities on NASA-controlled real property. This investment includes facility planning, budgeting, design, construction, and activation. (1) Critical technical facilities specifically developed or significantly modified for space flight s
35、ystems are subject to NPR 7120.5, and not this document. c. Environmental Compliance and Restoration (ECR) - Environmental restoration and environmental management efforts. 2 Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-d. Other Mission Support In
36、vestments (OMSI) - Investments for developing or enhancing a supporting capability for the Agency or a Center that are not covered elsewhere in this document or under other NPR 7120 guidance. These investments are considered to be important and visible enough to warrant project management reporting
37、and oversight. Examples include Agency-wide implementation of a Presidential directive (e.g., HSPD-12) or certification program (e.g., Voluntary Protection Program); establishment of a centralized capability for mission support services (e.g., transfer of new responsibilities to the NASA Shared Serv
38、ices Center); or implementation of a security and program protection project at a Center (e.g., a new emergency preparedness program). (1) OMSI programs and projects are subject to the requirements of this document if they meet either of the following criteria: (a) The total development and implemen
39、tation cost of the program or project is $1M or greater. (b) The total development and implementation of the program or project will take one year or longer. (2) The Official-in-Charge of the implementing Mission Directorate or Mission Support Office or the Center Director of an implementing Center
40、may require a program or project to comply with the requirements of this document even if the program or project does not meet the above criteria. Such a decision may be made, for example, for reasons related to high risk, high importance, or high visibility of the program or project. 1.2 Overview o
41、f Management Process 1.2.1 Management of NASA programs and projects is a four-part process consisting of: a. Formulation - the assessment of feasibility, technology and concepts, risk assessment, teambuilding, development of operations concepts, alternatives evaluation and trade studies, acquisition
42、 strategies, establishment of high-level requirements and success criteria, the preparation of plans, budgets, and schedules essential to the success of a program or project, and the identification of how the program or project supports the Agencys strategic needs, goals, objectives, and/or NASA Edu
43、cation outcomes. b. Approval - the acknowledgement by the responsible official (the Decision Authority) that the program/project has met expectations and formulation requirements and is ready to proceed to implementation. c. Implementation - the execution of approved plans for the development, const
44、ruction, testing, and operation of products and services, and the use of control systems to ensure performance to approved plans and alignment with the NASA Strategic Plan. 3 Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-d. Evaluation - the continu
45、al, independent (i.e., outside the advocacy chain of the program or project) evaluation of the performance of a program or project and incorporation of the evaluation findings to ensure adequacy of planning and execution according to approved plans. 1.2.2 NASAs IT and institutional infrastructure pr
46、ogram and project management process is based on life cycles with key decision points at life-cycle phase boundaries, evolving products, a decision authority, a governance structure, and independent assessment. 1.2.3 The scope and scale of NASA IT and institutional infrastructure programs and projec
47、ts are varied. They include environmental cleanup projects at an individual Center; Agency-wide programs such as the Integrated Enterprise Management Program, which includes a dozen or more financial, procurement, asset management, and human capital projects; and educational projects such as the NAS
48、A Explorer Schools, which may be in evaluation for ten years or more. The requirements and management process of IT and institutional infrastructure programs and projects take into account the scope and scale of the program or project. 1.3 Document Structure 1.3.1 The remainder of this document is o
49、rganized as follows: Chapter 2 defines the life cycles for IT and institutional infrastructure programs and projects, and Chapter 3 defines the roles and responsibilities of program and project management. 1.3.2 Chapter 4 defines the requirements for IT projects. 1.3.3 The requirements for CoF projects are defined in N
