|
|
Industry
Advisory Council (IAC) Enterprise Architecture White Paper Series:
EA Process for Reference Model Use, Extension and Implementation
The
Federal Enterprise Program Management is developing a new approach
to Enterprise Architecture that supports the government transformation.
The Federal Enterprise Architecture (FEA) is a business-based
framework constructed as a collection of interrelated "reference
models" that will facilitate cross-agency analysis, and the
identification of duplicative investments, gaps, and opportunities
for collaboration among Federal agencies. The Reference Models
act as a Target Architecture for which each agency will align.
OMB and agencies will use the FEA for describing and analyzing
information technology (IT) and other capital investments, and
to improve Federal government service to the citizen. It includes
a strong focus on delivering services to the citizen along with
government- to- government process and information exchanges along
with consolidating and integrating the services along lines of
business.
Please
use this form if you have comments. click
here.
For those of you with extensive comments please click
here.
Please
comment on the PPT Presentation if there is no paper ready for
review. We are looking for overall concept feedback.
I.
IAC Papers and key Concepts Alignment with FEA Reference Models
The
following defines the critical Federal Enterprise Architecture
reference model elements and illustrates their direct association
of IAC process, modeling and implementation issues:
| Federal
Enterprise Architecture Reference Models |
Vision
and FEA Reference Model Association:
1.
A Business/ Service-Oriented Government Architecture: Government
Business Service Grid for Transformation
Comments due by 2/28/03
 v
2.0 - 01/07/03
|
| |
|
| Business
Reference Model (BRM) - Describes the day-to-day business
operations from a functional perspective, using lines of business
and sub-functions as the main viewpoint for analyzing data,
applications, and technology. |
2.
Extending and Expanding the Use of the Business Reference
Models for Business Design and Strategic Improvement
This paper places the Business Reference Model in context
and recommends an approach to use the BRM in Modernization
efforts and Performance Management activities. It recommends
that strategic goals be closely tied to the Business and
Mission focused Enterprise Architecture and that metrics
for the organization be built around the Enterprise Architecture
plans to move from current state to an improved target state.
Comments due by 2/28/03
v.
01/02/03  v.01/07/03
3.
Business Line Architecture and Integration
This paper discusses the Planning and Strategy
that is needed not just within the Federal business space
but also with the communication with State and Local enterprises
and along with business partners and providing access channels
to citizens.
Comments due by 3/4/03
|
| |
|
| Performance
Reference Model (PRM) - Will identify
a common set of general performance outcomes, metrics, and
measures that a Federal agency can use to achieve much broader
goals and objectives. |
4.
PRM Definition with Links to other Reference Models: Business
Driven, Cycle Time Oriented, and Outcome Focused
This paper discusses the steps that are needed
to use the Performance Reference Model (PRM) and to align
it with the Business Process Improvements, Strategic Changes,
and the ongoing GPRA-Goal Driven activities. The enablers
and inhibitors to deploying the PRM are discussed along
with a set of recommendations such as the creation of a
Performance Reference Model Users Guide, training program/workshops,
and the creation of interoperable performance exchange standard
based on extending the XML-based standards such as XBRL.
Comments due by 2/28/03
v.
01/07/0
|
| |
|
| Data
and Information Reference Model (DRM)
- Will be an aggregated description of the data and information
that support program and business line operations, describing
types of interactions and information exchanges. |
5.
Information and Data Reference Model (DRM): Standards Based
Architecture to Support Federated Data Management
This paper is based on an approach and a Federated
Information Model that can be populated along government Business
Lines and be used across Federal, State, Local and International
e-government initiatives. The approach is based on both sound
information and data base theory, a serious need, and an approach
that correlates with standards organizations to create an
open and extendable family of information models. These models
can be one element of each organization's push for information
integration and increased consistency, commonality, and visibility.
Comments due by 2/28/03 |
| |
|
| Service
Component Reference Model (SRM) - Will identify and classify
horizontal and vertical IT service components that support
Federal agencies. The model will aid in recommending service
capabilities to support the reuse of business components and
services across the Federal Government.
|
6.
IAC EA SIG “Succeeding with Components”
This paper 1) outlines the enablers and inhibitors
to components in general and to web service-oriented components,
2) recommends aspects to include in the Application-Capability
Reference Model, and 3) identifies the elements of the FEAF
and Guidebook needed to assure critical components and their
dependencies are owned as part of "contractual"
arrangement a Component Specification by "Contract"
with register component owners and users.
Comments due by 2/28/03
v
1.0 - 12/04/02
v.
12/04/02
|
|
|
| Technical
Reference Model (TRM) - Will be
a hierarchical baseline describing how technology supports
delivery of the Application-Capability and outlining elements
that support the adoption/implementation of component-based
architectures. |
7.
Interfaces, Interoperability, and Integration Strategy:
This paper focuses on the key conceptual
elements of the process and technologies that can be used
to define the interfaces, establish and interoperability
framework and define an integration strategy along a business
line such as Homeland Security, between companion e-government
projects and to address your cross-agency, Department or
Government integration issues. Provided are some common
concepts and best practices for government leaders and technical
developers alike.
Comments due by 2/28/03
v.
08/01/02
|
| |
|
| Additional
Paper Topics |
8.
Advancing Enterprise Architecture Maturity
This paper looks at the recent past and the
critical leadership needed for even greater transformation
within the extended government enterprise where the focus
begins with the citizens service needs and the combined delivery
between federal agencies, state, local with a collaborative
government environment.
While
a few agencies have made great progress on their Enterprise
Architecture following the FEAF 1.1 process, others found
great difficult getting started, developing target architectures,
and overcoming the resistance to the broader business/mission
approach required for Enterprise Architecture. This paper
provides some sound recommendations about steps that can
be taken to advance the Enterprise Architecture maturity
and deliver the expected performance transformation.
Comments due by 2/28/03
v.
1.1 - 01/03 v.
01/07/03
9.
Integrating Security and Privacy Architecture with Enterprise
Architecture
The
paper provides initial concepts needed for a Security Service
Framework along with process changes that are needed for
updates into the FEAF 2.0 draft. The integration of Security
thinking and practices as an "aspect" of all the
Enterprise Architecture is key. The paper weaves the Security
Architecture process with the Enterprise Architecture.
Comments due by 3/4/03
10.
Technology Management Process
11.
Leveraging Web Services Technology
12.
DRM: Data Federated Management
v.
2.0 - 01/07/03
13.
Homeland Security Brief to IAC
December
5, 2003
|
|
|
|
