FEADoDAF Models for Assuring Implementation Success Robert Haycock Chief Architect Office of Managem

1
FEA/DoDAF Models for Assuring Implementation
Success Robert HaycockChief ArchitectOffice
of Management and BudgetExecutive Office of the
President

• November 20, 2003

2
FEA Facilitates Expansion of E-Government by
Identifying Opportunities to Collaborate,
Consolidate, and Leverage IT Investments Across
Government
Federal Enterprise Architecture (FEA)
Performance Reference Model (PRM)

• Inputs, outputs, and outcomes
• Uniquely tailored performance indicators

Owned By Line of Business Owners
Business Reference Model (BRM)

• Lines of Business
• Agencies, customers, partners

Service Component Reference Model (SRM)

• Service domains, service types
• Business and service components

Owned by Federal CIO Council
Data Reference Model (DRM)

• Business-focused data standardization
• Cross-agency information exchanges

Technical Reference Model (TRM)

• Service component interfaces, interoperability
• Technologies, recommendations

3
A Significant Finding from the PresidentsE-Gover
nment Strategy Compelling Need for an FEA

• The goals of the Federal Enterprise Architecture
  are to
• Enable the Federal Government to identify
  opportunities to leverage technology and
  alleviate redundancy, or to highlight where
  agency overlap limits the value of information
  technology (IT) investments
• Facilitate horizontal (cross-Federal) and
  vertical (Federal, State and Local) integration
  of IT resources
• Establish the line of sight contribution of IT
  to mission and program performance
• Support a more citizen-centered, customer-focused
  government that maximizes IT investments to
  better achieve mission outcomes

4
Visibility Leads to Smarter Decision-Making
18B
35B
24.3B
34.6B
Most agencies reported more business cases for
2004. Several agencies grew significantly 14
business cases from 2003 to over 100 in 2004, 26
business cases in 2003 to over 100 in 2004, etc.
5
BRM V2.0 Is Being Used by OMB in FY05 Budget
Process

• BRM Version 2.0 (released June 12, 2003)
  includes
• 4 Business Areas
• 39 Lines of Business
• 153 Sub-functions

5 the average number of Agencies per
Sub-function 8 the average number of Agencies
per Line of Business

• Version 2.0 is an improvement over the first
  version of the BRM
• Distinguishes between the purpose of government
  and process used to deliver government services
• Tighter link to OMBs Budget Function Codes
• Federal framework for financial management
  reflected in the Financial Management Line of
  Business

Services for Citizens

• What is the purpose of government?
• What outcomes is the government hoping to
  achieve?

• What mechanisms does the government use to
  achieve these outcomes?
• What are the outputs of these processes?

Mode of Delivery
6
Lines of Business

• As a result of using the FEA BRM Version 1 in
  evaluating 2004 agency budget requests, OMB
  identified potential redundancies in six lines of
  business (LoBs)/sub-functions
• Criminal Investigations (Currently Case
  Management DOJ)
• Public Health Monitoring (Currently Federal
  Health Architecture HHS)
• Financial Management (DOL and DOE)
• Human Resources (OPM)
• Data and Statistics (Not Currently Active)
• Monetary Benefits (Not Currently Active)
• Consolidation of systems and simplification of
  work processes will yield millions in cost
  savings, measurably reduce administrative burden
  on business, and significantly improve service to
  citizens
• Initial analysis of LoBs by the PMC in January
  2003 identified over 6.8 billion in IT
  investments that should be reviewed for potential
  savings

7
Performance Reference Model (PRM)A Standardized
Framework to Measure Performance of IT
Initiativesand Their Contribution to Program
Performance

• The PRM (released in September 2003) can help
• Produce enhanced performance information to
  improve strategic and daily decision-making
• Improve the alignment and contribution of inputs
  (technology) through outputs (processes and
  activities) to outcomes (business and customer
  results)
• Identify collaboration and performance
  improvement opportunities across traditional
  agency boundaries

8
Six PRM Measurement Areas Designed to Capture
Relationship Between Inputs, Outputs, and Outcomes
Each measurement area contains measurement
categories
9
PRM Structure Is Designed to ClearlyArticulate
Line of Sight
Line of Sight is the cause-and-effect
relationship between inputs, outputs and outcomes.
10
FEA Includes Service Component, Technical, and
Data Reference Models that Specifically Address IT
Performance Reference Model (PRM) Outcomes,
Measurements, Metrics
Business Reference Model ( BRM )
Service Component Reference Model ( SRM )
Technical Reference Model ( TRM )
Rule Publication
Support Delivery of Services
Technologies
Platforms J2EE .NET Windows NT
Knowledge Mgmt CRM Content Mgmt Collaboration Sear
ch Portal Personalization
Regulatory Management
Policy and Guidance Devel. Public Comment
Tracking Regulatory Development Rule Publication
Data Mgmt ODBC JDBC Business Logic
Business lines and functions
Supporting technology and standards
Enabling capabilities, components, and services
Data and Information Reference Model
(DRM) Classification, Categorization, XML, Sharing
Component-Based Architecture
Service Components
Service Layers
Service Types
11
Service Component Reference Model (SRM) A
Functional Framework that Classifies Capabilities
According to How They Support Business and
Performance Objectives
Access and Delivery Channels
Business Process
Performance Measures
Service Types
Customer Services
Process Automation Services
Business Management Services
Cross-Cutting Service Areas (i.e., Search,
Security)
Support Services
Digital Asset Services
Service Components
Business Analytical Services
Back Office Services
Service Domain
12
The Service Component Reference ModelSnapshot
of Service Domains and Service Types
SERVICE COMPONENT REFERENCE MODEL
Process Automation Services
Business Management Services
Digital Asset Services
Business Analytical Services
Back Office Services
Customer Services
Support Services

• Security management
• Collaboration
• Search
• Communication
• Systems management

• Tracking workflow
• Routing scheduling

• Data management
• Human resources
• Financial management
• Assets / materials management
• Integration
• Human capital / workforce management

• Customer relationship management
• Customer preferences
• Customer initiated assistance

• Content management
• Document management
• Knowledge management
• Records management

• Analysis statistics
• Visualization
• Business Intelligence
• Reporting

• Management of process
• Organizational management
• Investment management
• Supply chain management

The SRM is structured across horizontal service
areas that can provide a leverageable foundation
for reuse of applications, application
capabilities, components, and business services.
13
Technical Reference Model (TRM) Provides
Effective Means for Service Components to be
DeployedAcross the Federal Government
External Environment (Outside Agency Boundaries)
Demilitarized Zone (DMZ) (Service Component
Access)
Internal Environment (Within Agency Boundaries)
Service Platform
Component Framework (n-Tier Architecture)
Security Layer
Back Office / Legacy Assets
Infrastructure
Service Integration
Service Interface
Service Interface
Infrastructure
Presentation / Interface Layer
Access Channels
Delivery Channels
Service Requirements
Service Transport
Business Logic Layer
Data Interchange
Data Management
Infrastructure
Component Framework
Service Access and Delivery
Service Platforms Infrastructure
Service Interface and Integration
14
TRM is Composed of Multiple Categories
Describing Technologies, Standards, and
SpecificationsSupporting the Service Component
FEA Technical Reference Model (TRM) - Snapshot
Service Platform and Infrastructure
Service Interface and Integration
Component Framework
Service Access and Delivery
Security
Support Platforms
Access Channels
Integration
Presentation / Interface
Delivery Servers
Interoperability
Delivery Channels
Business Logic
Software Engineering
Interface
Service Requirements
Data Interchange
Database / Storage
Hardware / Infrastructure
Data Management
Service Transport
15
The DRM Supporting Investment and E-Gov Planning
Goals and Objectives
Integrated Enterprise

• Promote horizontal and vertical information
  sharing between business lines
• Business-focused data standardization that can be
  categorized for re-use
• Re-use and integration of data as opposed to
  duplication
• Enabler to support cross-agency collaboration
• Facilitate cross-agency information exchanges
• Consistent means to categorize and classify data

Agency 1
Agency 2
FEA-DRM
State
Local
Agency 3
Agency 4
Bureau
Bureau
Bureau
DRM provides framework for agencies to leverage
existing data components across the Government
16
Combined, FEA Reference Models Help Support
Creationand Integration of Cross-Agency Service
Components
U.S. Customs (New E-Gov Border Control Initiative)
Conceptual
Acceptance of Cargo
PRM
BRM
States
FDA
SRM
TRM
Look up the license plate of the vehicle. Are
there any warrants for the driver?
Is the food properly packaged? How much does a
normal truckload of bananas normally weigh?
DRM
IRS
Justice
Does the driver fit the profile of any wanted
suspects. What country, what origin?
Check to see if the import company owes taxes,
fines, or penalties
USDA
Do not let x animals into the country. Know
viruses and risks
Agency EA
Service Component
E-Gov Architecture Guidance
Federal Enterprise Architecture
17
Inter-relationship ofFEA and DoDAF