NAMC-21C 3BSE017424R1 NAMC21C 高压控制板

 NAMC-21C 3BSE017424R1 NAMC21C 高压控制板 

A-11要求内阁级机构，包括国防部，将其提交的预算联系起来
提交给FEA，并通过企业架构每年评估这些提交
评估计划，为机构的整体进展建立评估分数。
FEA程序的核心原则是：
业务驱动的方法。
促进协作和重用。
通过以下方式提高业务运营的效率和有效性：
资本投资流程的企业架构。
通过改进核心流程证明成本节约和成本避免，以及
跨机构共享和相互投资。
国防部利用FEA结构和核心原则为国防部提供
企业管理信息：它需要实现自身的战略转型
目标并响应OMB的向上报告要求。主要目标是：
通过提供跨任务分析框架，使用EA提高国防部的性能
确定差距和冗余；通过制定过渡计划和目标
有助于将国防部转移到网络中心环境的体系结构。
存在几个描述企业级的联邦和国防部特定EA工件
管理信息。其中包括：
总统的管理议程。
OMB A-11附件300提交。
OMB有限元分析实践指南。
OMB EA评估指南。
OMB有限元分析参考模型。
国防部企业体系结构参考模型（RM）分类法。
国防部EA合并RM。
国防部企业体系结构转型战略。
国防部部门架构。
国防部EA自我评估。
国防部架构联盟战略。
这些工件有助于与FEA对齐，有助于更广泛的理解
架构对齐，为联合架构描述提供基础，促进
更高效和有效地使用资产，并终导致更好的决策。
在开发架构时，特别是在部门和组件级别，
通过利用联邦企业架构综合参考模型（FEA-CRM）文件以及国防部文件，实现与FEA的一致性，以及
作为定义过程、数据、服务和技术标准的基础的参考。作为
例如，当流程所有者确定需要架构描述时
对于某些特定用途，首先使用的参考如下所示，以及其他
高于和低于以下架构描述级别的架构描述
发展国防部级信息包含在国防部企业体系结构参考模型中，以及
具有部门范围内的实施指南、标准和说明
根据FEA构造映射到FEA-CRM的信息。
参考体系结构描述开发
资源描述体系结构使用
决定
过程
卷入的
体系结构框架
有限元分析业务
参考模型
（BRM）
（DoDAF）确定要使用的技术和符号
习惯于
（FEA BRM）确定要对齐的FEA业务流程
到使用BRM中的分类法命名流程
识别和
定义数据
DM2（DM2）
FEA数据参考
（DM2）数据组和元数据结构
（DRM）现有的政府范围元数据
20
DoDAF体系结构开发-6步流程
http://cio-nii.defense.gov/sites/dodaf20/arch_development.html[2011年3月3日下午3:33:54]
模型（DRM）与体系结构的链接
文件
建筑的
描述
并确保
顺从
体系结构框架
国防部元数据
国防部登记处（DMR）
建筑学
注册系统
（DARS）工具集
OMB EA指南
联邦
企业
建筑合并
参考模型
（FEA-CRM）
OMB EA评估
指导
（DoDAF）提供了描述的模型和指南
为演示创建适合用途的视图
目的
（DMR）提供要在中使用的现有元数据
结合DMR创建所需数据
（DARS）为架构提供注册服务
发现
（工具集）为以下方面提供了自动表示法：
创建视图
（OMB EA指南）提供所需信息
OMB 53/300流程EA的格式和内容
（OMB EA评估指南）提供以下指导
提交给OMB的架构评估
回顾

NAMC-21C 3BSE017424R1 NAMC21C 高压控制板 

NAMC-21C 3BSE017424R1 NAMC21C 高压控制板 

A-11 requires that Cabinet-level agencies, including the DoD, link their budget submissions
to the FEA, and annually evaluates those submissions through the Enterprise Architecture
Assessment Program, which establishes an evaluation score for overall agency progress.
The core principles of the FEA program are:
Business-driven approach.
Promote collaboration of effort and reuse.
Improve efficiency and effectiveness of business operations through the use of
enterprise architecture for the capital investment process.
Demonstrate cost savings and cost avoidance through improved core processes, and
cross-agency sharing and mutual investment.
DoD leverages the FEA construct and core principles to provide the Department with the
enterprise management information it needs to achieve its own strategic transformation
goals and respond to upward reporting requirements of OMB. The primary objective is to
improve DoD performance, using EA, by providing a framework for cross-mission analysis
and identification of gaps and redundancies; and by developing transition plans and target
architectures that will help move DoD to the net-centric environment.
Several Federal and DoD-specific EA artifacts exist that describe enterprise-level
management information. These include:
The President’s Management Agenda.
OMB A-11 Exhibit 300 submissions.
OMB FEA Practice Guidance.
OMB EA Assessment Guide.
OMB FEA Reference Models.
DoD EA Reference Model (RM) Taxonomy.
DoD EA Consolidated RM.
DoD EA Transition Strategy.
DoD Segment Architectures.
DoD EA Self-Assessment.
DoD Architecture Federation Strategy.
These artifacts facilitate the alignment with the FEA, contribute to a broader understanding
of architecture alignment, provide a basis for federated Architectural Descriptions, promote a
more efficient and effective use of assets, and ultimately lead to better decision-making.
When developing architectures, particularly at the Departmental and Component levels,
alignment with the FEA is accomplished by utilizing the Federal Enterprise ArchitectureConsolidated Reference Model (FEA-CRM) documents together with DoD documents and
references as a basis for defining processes, data, services, and technical standards. As an
example, when a process owner determines that an Architectural Description is needed for
some specific purpose, the first references to use are as shown below, as well as other
Architectural Descriptions above and below the level of the Architectural Description under
development. The DoD-level information is contained in the DoD EA Reference Models, along
with the implementing guidance, standards, and descriptions of Department-wide
information that is mapped to the FEA-CRM in accordance with the FEA construct.
References to Architectural Description Development
Resource Description Architecture Use
Determine
Processes
Involved
DoDAF
FEA Business
Reference Model
(BRM)
(DoDAF) Determine techniques and notation to be
used
(FEA BRM) Determine FEA business processes to align
to; use taxonomies in BRM to name processes
Identify and
Define data
DM2 (DM2)
FEA Data Reference
(DM2) Data Group and metadata structures
(DRM) Existing Government-wide metadata for
20
DoDAF Architecture Development - 6 Step Process
http://cio-nii.defense.gov/sites/dodaf20/arch_development.html[3/3/2011 3:33:54 PM]
Model (DRM) linkage to architecture
Document
Architectural
Description
and Ensure
Compliance
DoDAF
DoD Metadata
Registry (DMR) DoD
Architecture
Registry System
(DARS) Toolset
OMB EA Guidance
Federated
Enterprise
ArchitectureConsolidated
Reference Model
(FEA-CRM)
OMB EA Assessment
Guide
(DoDAF) provides described models, and guidance on
creating Fit-for-Purpose Views for presentation
purposes
(DMR) Provides existing metadata to use in
conjunction with DMR to create data required
(DARS) provides registration services for architecture
discovery
(Toolset) provides automated notation method for
creating views
(OMB EA Guidance) provides information on required
format and content of EA for OMB 53/300 process
(OMB EA Assess. Guide) provides guidance on
evaluation of architectures submitted to OMB for
review