| NODIS Library | Legal Policies(2000s) | Search |

NASA Ball NASA
Procedural
Requirements
NPR 2830.1A
Effective Date: December 19, 2013
Expiration Date: November 30, 2021
COMPLIANCE IS MANDATORY FOR NASA EMPLOYEES
Printable Format (PDF)

(NASA Only)

Subject: NASA Enterprise Architecture Procedures

Responsible Office: Office of the Chief Information Officer


| TOC | Preface | Chapter1 | Chapter2 | Chapter3 | Chapter4 | AppendixA | AppendixB | AppendixC | ALL |

Preface

P.1 Purpose

a. The NASA Procedural Requirements (NPR) 2830.1 outlines and defines the NASA Enterprise Architecture (EA) Program for Information Technology (IT). The primary purpose of EA is to align all aspects of NASA's business, financial, scientific, and engineering needs with technology infrastructure and resources to improve the performance of IT and support NASA's Mission. EA will enhance NASA's IT governance structure through a defined enterprise process designed to develop and maintain an integrated IT roadmap that allows the Agency's governance boards to make informed investment and management decisions.

b. This NPR includes the EA processes, products and outcomes, roles and responsibilities, and procedural requirements and governance required by the Clinger-Cohen Act and OMB A-130, under the authority of NPD 2830.1, to achieve this purpose.

P.2 Applicability

a. This NPR is applicable to NASA Headquarters and NASA Centers, including Component Facilities and Technical and Service Support Centers. This language applies to Jet Propulsion Laboratory (JPL), a Federally Funded Research and Development Center (FFRDC), contractors, grant recipients, or parties to agreements, but only to the extent specified or referenced in the appropriate contracts, grants, or agreements.

b. In this directive, all mandatory actions (i.e., requirements) are denoted by statements containing the term "shall." The terms "may" or "can" denote discretionary privilege or permission, "should" denotes a good practice and is recommended but not required, "will" denotes expected outcome, and "are/is" denotes descriptive material.

c. In this directive, "NASA charters" refers to those charters that govern councils, boards, committees, panels, and working groups with Agency-wide membership.

d. In this NPR, "Center-level charters" refers to those charters that govern councils, boards, committees, panels, and working groups with Center-specific membership.

P.3 Authority

a. 40 U.S.C. 11101 et seq., Clinger-Cohen Act of 1996, also known as the Information Technology Management Reform Act (ITMRA), as amended

b. Office of Management and Budget (OMB) Circular No. A-130 Revised - Management of Federal Information Resources

c. NPD 2830.1 - NASA Enterprise Architecture

P.4 Applicable Documents and Forms

a. Circular A-11 - Preparation, Submission, and Execution of the Budget

b. Circular A-130 Revised - Management of Federal Information Resources

a. Information Resources Management (IRM) Strategic Plan

b. NPD 1001.0 - NASA Strategic Plan

c. NPD 2830.1 - NASA Enterprise Architecture

d. NPR 1441.1 - NASA Records Retention Schedules

e. NPR 2800.1B - Managing Information Technology

f. NPR 7120.7 - NASA Information Technology and Institutional Infrastructure Program and Project Management Requirements

g. NPR 8000.4A - Agency Risk Management Procedural Requirements

h. NPR 9420.1 - NASA Budget Formulation

i. OMB (M-12-10, M-13-09) - PortfolioStat

j. The Common Approach to Federal Enterprise Architecture (OMB, 05/02/2012)

P.5 Measurement/Verification

a. NASA EA effectiveness will be measured based on the results of IT implementations to achieve Agency Information Resources Management (IRM) goals and objectives. Key metrics will be established that link EA successes with alignment of IT capabilities to mission requirements, improved security, actual cost savings, performance improvements, reduction of duplication, and improved agility/flexibility through simplification and standardization. Based on these successes, EA will support mission outcomes and business and science results, as well as assure integrated infrastructure that provides NASA workers the IT resources they need to do their jobs within a comprehensive security framework.

b. The NASA Chief Enterprise Architect (NCEA) shall track these results and review the outcomes with the NASA Chief Information Officer (CIO) at least annually to communicate results and feedback, in order to improve the investment process, investment performance, and the EA program process.

P.6 Cancellation

NPR 2830.1, NASA Enterprise Architecture Procedures, dated February 9, 2006.

Original Signed by
Larry N. Sweet
Chief Information Officer



| TOC | Preface | Chapter1 | Chapter2 | Chapter3 | Chapter4 | AppendixA | AppendixB | AppendixC | ALL |
 
| NODIS Library | Legal Policies(2000s) | Search |

DISTRIBUTION:
NODIS


This document does not bind the public, except as authorized by law or as incorporated into a contract. This document is uncontrolled when printed. Check the NASA Online Directives Information System (NODIS) Library to verify that this is the correct version before use: https://nodis3.gsfc.nasa.gov.