ImageVerifierCode 换一换
格式:PDF , 页数:4 ,大小:100.46KB ,
资源ID:1017615      下载积分:10000 积分
快捷下载
登录下载
邮箱/手机:
温馨提示:
如需开发票,请勿充值!快捷下载时,用户名和密码都是您填写的邮箱或者手机号,方便查询和重复下载(系统自动生成)。
如填写123,账号就是123,密码也是123。
特别说明:
请自助下载,系统不会自动发送文件的哦; 如果您已付费,想二次下载,请登录后访问:我的下载记录
支付方式: 支付宝扫码支付 微信扫码支付   
注意:如需开发票,请勿充值!
验证码:   换一换

加入VIP,免费下载
 

温馨提示:由于个人手机设置不同,如果发现不能下载,请复制以下地址【http://www.mydoc123.com/d-1017615.html】到电脑端继续下载(重复下载不扣费)。

已注册用户请登录:
账号:
密码:
验证码:   换一换
  忘记密码?
三方登录: 微信登录  

下载须知

1: 本站所有资源如无特殊说明,都需要本地电脑安装OFFICE2007和PDF阅读器。
2: 试题试卷类文档,如果标题没有明确说明有答案则都视为没有答案,请知晓。
3: 文件的所有权益归上传用户所有。
4. 未经权益所有人同意不得将文件中的内容挪作商业或盈利用途。
5. 本站仅提供交流平台,并不能对任何下载内容负责。
6. 下载文件中如有侵权或不适当内容,请与我们联系,我们立即纠正。
7. 本站不保证下载资源的准确性、安全性和完整性, 同时也不承担用户因使用这些下载资源对自己和他人造成任何形式的伤害或损失。

版权提示 | 免责声明

本文(REG NASA NPD 2830 1 REV A-2011 NASA ENTERPRISE ARCHITECTURE.pdf)为本站会员(explodesoak291)主动上传,麦多课文库仅提供信息存储空间,仅对用户上传内容的表现方式做保护处理,对上载内容本身不做任何修改或编辑。 若此文所含内容侵犯了您的版权或隐私,请立即通知麦多课文库(发送邮件至master@mydoc123.com或直接QQ联系客服),我们立即给予删除!

REG NASA NPD 2830 1 REV A-2011 NASA ENTERPRISE ARCHITECTURE.pdf

1、 NODIS Library | Legal Policies(2000s) | Search | NASAPolicyDirective NPD 2830.1AEffective Date: November 02,2011Expiration Date: November 02,2016COMPLIANCE IS MANDATORY Printable Format (PDF)(NASA Only) Subject: NASA Enterprise Architecture Responsible Office: Office of the Chief Information Offic

2、er1. POLICY a. This directive establishes the policy and responsibilities for maintaining and using theNASA Enterprise Architecture (EA). Under the direction of the Agency Chief InformationOfficer (CIO), NASA will establish an EA Program (NASA EA Program) to develop andmaintain the NASA EA that will

3、 serve as the primary authoritative resource for InformationTechnology (IT) planning and execution. b. The NASA EA shall: 1. be a composition of architectures and set of integrated reference models that map all ITinitiatives, capabilities, and services to Agency needs; 2. serve to guide executive de

4、cision making, establishing a clear linkage between presentcapabilities and future NASA mission needs. This includes the identification of potentialshortfalls and redundancies in IT capabilities; the timeframe in which the shortfall orredundancy exists; and an analysis of the industry alternatives a

5、nd remedialsolutions/approaches; 3. provide a foundation for further development, modernization or modification, andenhancements of integrated architectures; 4. identify mission IT dependencies; 5. make service and related information available through the NASA Open Governmentinitiative; 6. be used

6、as a tool to integrate strategic planning efforts and to select, guide, manage,rationalize, and prioritize Agency investments; 7. establish the framework for Agency interoperability by providing the standard, rigorousconstruct for horizontal and vertical integration of mission needs and business pro

7、cessesthrough architecture; 8. be integral to the budget life cycle, enabling informed and timely procurement decisionmaking to influence capital and strategic sourcing investments; and 9. promote transparency and accountability by aligning NASA functions/capabilities,services, systems, components,

8、and related standards to Agency strategy; Agencystrategy may also be informed by a better understanding of all these mission supportelements. c. The NASA EA Program shall define the NASA EA, the operational parameters for itsRequest Notification of ChangeNPD 2830.1A - main Verify Current version bef

9、ore use at:http:/nodis3.gsfc.nasa.gov/ Page 1 of 4 NPD 2830.1A - main Verify Current version before use at:http:/nodis3.gsfc.nasa.gov/ Page 1 of 4 Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-development, and requirements for its intended use. d.

10、The NASA EA common framework and methodology shall be used Agency wide. 2. APPLICABILITYThis NPD is applicable to NASA Headquarters and NASA Centers, including ComponentFacilities and Technical and Service Support Centers. This language applies to the JetPropulsion Laboratory (JPL), other contractor

11、s, grant recipients, or parties to agreementsonly to the extent specified or referenced in the appropriate contracts, grants, oragreements. 3. AUTHORITY a. 5 U.S.C. 552a, Privacy Act of 1974, as amended. b. 40 U.S.C. 11101 et seq., Clinger-Cohen Act of 1996, also known as the InformationTechnology M

12、anagement Reform Act, as amended. 4. APPLICABLE DOCUMENTSa. OMB Circular No. A-130 (Revised), Management of Federal Information Resources. b. OMB Circular No. A-11, Preparation, Submission and Execution of the Budget. c. NPD 1000.0, NASA Governance and Strategic Management Handbook. d. NPD 2800.1, M

13、anaging Information Technology. e. NPD 2810.1, NASA Information Security Policy. f. NPR 4200.1, NASA Equipment Management Procedural Requirements. g. NPR 7120.7, NASA Information Technology and Institutional Infrastructure Program andProject Management Requirements. h. NPR 8831.2, Facilites Maintena

14、nce and Operations Management. i. National Institute of Standards and Technology (NIST) Special Publications 800 Series. j. Chief Financial Officers Act of 1990 (this is currently misplaced in the ReferencesAppendix). k. NPR 2830.1, NASA Enterprise Architecture Procedures. 5. RESPONSIBILITYa. The CI

15、O shall: 1. be the executive sponsor of the NASA EA, responsible for executive direction and forcommunicating its strategic use as a management tool; 2. be responsible for the implementation and management of the EA Program and assuch, provides its strategic direction and enforces its requirements;

16、3. appoint a NASA Chief Enterprise Architect (NCEA) with the day-to-day responsibility formanaging the NASA EA Program, conducting oversight of its implementation throughoutthe Agency, and measuring the use of EA as the organizing construct for enabling a highlyintegrated mission and institution; an

17、d 4. develop policy and procedure for integrated capabilities-based planning to augment andfacilitate existing strategic planning processes. b. Each Directorate Associate Administrator shall be responsible for ensuring that theirrespective current and future directorate requirements, needs, activiti

18、es, and capabilitiesare appropriately integrated into the NASA EA and use their discretion in assigningappropriate personnel to this activity. NPD 2830.1A - main Verify Current version before use at:http:/nodis3.gsfc.nasa.gov/ Page 2 of 4 NPD 2830.1A - main Verify Current version before use at:http:

19、/nodis3.gsfc.nasa.gov/ Page 2 of 4 Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-c. The Assistant Administrator for Procurement shall: 1. be responsible for the inclusion of appropriate contract clauses that contain therequirement for compliance an

20、d alignment with the NASA EA; and 2. shall use EA artifacts as a contributing component of the Agency-wide procurementstrategy. d. The Chief Financial Officer (CFO) shall: 1. use the NASA EA as the basis for Agency IT financial management planning, includingthose required in the Chief Financial Offi

21、cers Act of 1990 (the CFO Act, as amended); and 2. collaborate with the CIO to ensure that the NASA EA supports the Agencys Planning,Programming, and Budget Execution (PPBE) processes. e. The Agency Chief Engineer (CE) shall work with the NCEA to assist in the creation,maintenance, and governance of

22、 an EA that establishes: 1. a strategic direction for the Agencys IT services in support of the CEs missionobjectives; 2. a long-term plan for implementing those services according to the CEs needs; 3. a basis for assessing program and project compliance with the strategy and plan; 4. a basis for me

23、asuring the performance of existing and future IT services; and 5. reference for iteratively integrating and optimizing the Agencys ability to achieve itsstrategic goals. f. The NCEA shall: 1. develop and maintaining the NASA EA; 2. issue procedures, technical standards, and guidelines associated wi

24、th the EA; 3. report, through the Office of the Chief Information Officer, on the maturity of the EAProgram to the Office of Management and Budget and the Government AccountabilityOffice; 4. use the EA to plan, design and manage services/investments through technologyforecasts, such that institution

25、al provisioning of IT capabilities anticipates and servicesprogrammatic needs; 5. coordinate with stakeholders to ensure their requirements are captured in the NASA EAand make the contents of the NASA EA widely available; and 6. issue guiding principles, procedures, and technical standards for the E

26、A to create anintegrated Agency-wide perspective, including a function as integrator for the Agency EA,facilitating the coordination and collaboration between architecture elements. g. Each Center Director (including the JPL Director) shall: 1. be responsible for governing Center-level IT investment

27、 implementation, and operationdecisions and activities based on the NASA EA; 2. collaborate across Center-level organizations, programs, and projects to progressivelyintegrate IT needs and architecture activities into the NASA EA; and 3. appoint a responsible designee (“Center Enterprise Architect“

28、) for Center-levelarchitecture activities. h. Each Center Enterprise Architect shall: 1. be responsible for interface, collaboration, and coordination of EA activities with theNCEA and the Mission Directorate programs and projects at their Center; and NPD 2830.1A - main Verify Current version before

29、 use at:http:/nodis3.gsfc.nasa.gov/ Page 3 of 4 NPD 2830.1A - main Verify Current version before use at:http:/nodis3.gsfc.nasa.gov/ Page 3 of 4 Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-2. interface as required to maintain alignment with the NA

30、SA EA, including adhering tostandards and other guidance as appropriate from the NCEA. 6. DELEGATION OF AUTHORITYNone. 7. MEASUREMENTSNASA Headquarters, Mission Directorates, NASA Centers, Component Facilities, and JPLshall develop, maintain, and communicate balanced measures that best indicate the

31、EAperformance in their organizations through formal reporting systems to the Agency ChiefEnterprise Architect. Measures are described in the companion NASA ProceduralRequirement, NPR 2830. 8. CANCELLATIONNPD 2830.1, The NASA Enterprise Architecture, December 2005. /s/ Charles F. Bolden, Jr.Administr

32、atorATTACHMENT A: Reference Documents:a. 5 U.S.C. 1 et seq., Government Performance and Results Act of 1993, as amended. b. 31 U.S.C. 501 et seq., Chief Financial Officers Act of 1990, as amended. c. 44 U.S.C. 3544 Coordination of Federal Information Policy - Federal AgencyResponsibilities. d. 41 U.

33、S.C. 251, Federal Acquisition Streamlining Act of 1994, as amended. e. 44 U.S.C. 3504, Government Paperwork Elimination Act of 1998, as amended. f. 44 U.S.C. 3601 et seq., E-Government Act of 2002: Management and Promotion ofElectronic Government Services, as amended. /s/ Charles F. Bolden, Jr.Admin

34、istrator(URL for Graphic) DISTRIBUTION:NODIS This Document Is Uncontrolled When Printed.Check the NASA Online Directives Information System (NODIS) Libraryto Verify that this is the correct version before use: http:/nodis3.gsfc.nasa.govNPD 2830.1A - main Verify Current version before use at:http:/nodis3.gsfc.nasa.gov/ Page 4 of 4 NPD 2830.1A - main Verify Current version before use at:http:/nodis3.gsfc.nasa.gov/ Page 4 of 4 Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-

copyright@ 2008-2019 麦多课文库(www.mydoc123.com)网站版权所有
备案/许可证编号:苏ICP备17064731号-1