Federal Enterprise Architecture Program Management Office

1
Federal Enterprise Architecture Program
Management Office
Accomplishments and Next Steps
Presentation for Conference on Open
Standards/Open Source for National and Local
E-Government Programs Robert Haycock, FEA
Program Manager, OMB March 17, 2003
2
Agenda

• Why Do We Need a Federal Enterprise
  Architecture?
• Draft Business Reference Model, Version 2.0
• Draft Performance Reference Model
• Draft Services Component, Technical, and Data
  Reference Models
• Next Steps

3
The Presidents Management Agenda sets forth a
strategy for ensuring that the Federal
Government is well-run and results-oriented

• Strategic Management of Human Capital
• Restructure agencies to be citizen-centered
• Adopt IT to capture employees knowledge and
  skills
• Acquire and develop talent and leadership
• Competitive Sourcing
• Simplify and improve procedures to evaluate
  public and private sources
• Better publicize activities subject to
  competition
• Ensure senior-level agency attention to
  competition
• Improved Financial Performance
• Baseline erroneous payments and establish goals
  for their reduction
• Ensure federal financial systems produce accurate
  and timely information
• Expanded Electronic Government
• Simplify and unify around citizen needs
• Support projects that offer performance gains
  across agency boundaries
• Maximize interoperability and minimize redundancy

Page 3
4
Extensive evidence points to the duplication,
overlap and gaps in critical Government functions

• ?50 agencies implement Federal drug control
  strategies
• ?29 agencies administer 541 clean air, water,
  and waste programs
• ?23 agencies administer 200 programs that provide
  assistance to countries formerly part of the
  Soviet Union
• ?13 agencies administer 342 Federal economic
• development-related programs
• ?12 agencies administer more than 35 food safety
  laws

Urgent Business for America Revitalizing the
Federal Government for the 21st Century. The
Report of the National Commission on the Public
Service, January 2003.
Page 4
5
Extensive evidence points to the duplication,
overlap and gaps in critical Government functions
(continued)

• ?11 agencies administer 90 early childhood
  programs
• ?9 agencies administer 86 teacher training
• programs
• ?9 agencies administer 27 teen pregnancy programs
• ?8 agencies administer 50 different programs
  to
• aid the homeless
• ?7 agencies administer 40 different job training
• programs

Page 5
6
E-Government is critical to the success of a
citizen-centered, results-oriented Government

• E-Government is a key enabler to achieve success
  in
• Human capital
• Competitive sourcing
• Financial management
• Budget and performance integration

Page 6
7
Best Practices in E-Business point to two methods
for citizen-centered Government
The Vision an order of magnitude improvement
in the federal governments value to the citizen
with decisions in minutes or hours, not weeks or
months

• HOW Unify Infrastructure
• Aggregate information around customer
• Unify access to data stores (bridge)
• Collect the data once (requires agreement on data
  definitions)
• Integrate customer interface
• Integrate delivery channels (build one-stop e.g.
  students.gov)
• Monitor and measure (define success and measure)

• HOW Simplify Process
• Simplification starts by defining and building
  and integrated delivery channels to drive
  unification.
• Simplification should start with unifying access
  to data stores
• For e-Gov to succeed, simplification must start
  by the time you collect the data

Page 7
8
E-Government Unification and simplification must
be done around citizen needs

• For individuals
• Build easy to find, one-stop shops for citizens
  creating single points of easy entry to access
  high-quality governmental services
• For businesses
• Reduce the burden on businesses through the use
  of Internet protocols, simplifying interactions,
  and consolidating redundant reporting
  requirements
• For government agencies
• Make it easier for states and localities to meet
  reporting requirements, while enabling better
  performance measurement and results (e.g.,
  grants)
• Internal efficiency and effectiveness
• Reduce costs for Federal Government
  administration by using best practices in areas
  such as supply chain management, financial
  management, and knowledge management

Page 8
9
The Federal Enterprise Architecture (FEA) will
provide the ability, for the first time, to look
across the Federal Government and identify
opportunities to collaborate, consolidate, and
leverage IT investments
Federal Enterprise Architecture (FEA)
Performance Reference Model (PRM)

• Government-wide Performance Measures Outcomes
• Line of Business-Specific Performance Measures
  Outcomes

Business Reference Model (BRM)

• Lines of Business
• Agencies, Customers, Partners

Service Component Reference Model (SRM)

• Capabilities and Functionality
• Services and Access Channels

Data Reference Model (DRM)

• Business-focused data standardization
• Cross-Agency Information exchanges

Technical Reference Model (TRM)

• IT Services
• Standards

Page 9
10
OMB has established a governance process to
identify interagency initiatives, integrate the
FEA with budget processes, and guide Government
transformation
1
2
New Fiscal Year
OMB releases Business Reference Model and IT /
E-Gov leverage opportun-ities
Presidents Management Council (PMC) establishes
priorities for E-Gov improvement and determines
whether single agency or multi-agency effort
PMC approves Cross-Agency Business Line Owners for
targeted Business Lines
Recommendations shared with Congress for funding
Open season for Agencies to submit initiatives
that align with E-gov targets
Business Line Owners establish Analysis Teams
Teams Perform Improvement Analyses
Line of Business Owners submit Business Cases
to OMB for approved E-Gov initiatives
3
Recommendations Provided to PMC for approval
Federal Enterprise Architecture Management System
(FEAMS)
Continual FEAMS access provided to Federal
agencies, OMB, and Congress
Page 10
11
OMB and the CIO Council are working together to
ensure the FEA is operationalized and the
governance process succeeds

• Committee Objectives
• Integrated OMB and CIO Council EA efforts
• Simpler, consistent EA taxonomy and terminology
• Facilitation of cross-agency efforts
• The operationalization of EA efforts

Architecture and Infrastructure Committee
IT Workforce Committee

• Subcommittee Outcomes
• Institutionalization of the FEA
• Alignment of the FEA with Agency EAs
• Integration of EA / FEA with key IT management
  processes
• Vertical integration of the FEA with State and
  Local agency EAs

Governance

• Subcommittee Outcomes
• Improved understanding of technologies that can
  support implementation of the FEA
• Faster adoption of validated capabilities for
  FEA adoption, based on registry creation and
• pilot findings
• Better understanding of FEA tradeoffs as
  established and emerging technologies compete
• and converge
• Greater FEA valuation and longer component life
  cycles

Components

• Subcommittee Outcomes
• Identification of business processes, service
  components and technologies for re-use
• Reduction in IT costs and cycle times for
  Federal agencies through re-use
• Rapid solution development through the re-use
  of components
• Rapid integration of disparate business
  services
• Development and implementation of e-Gov
  solutions based on Component-Based Architectures

Emerging Technology
Page 11
12
The CIO Councils Governance Subcommittee will
expand the FEA to include State and Local
Governments the direct providers of Government
services to citizens
Federal Enterprise Architecture Reference Models
Includes integration with other management
processes, and ensuring horizontal
vertical alignment
Agency EA
Departmental EA
GP
GP
Page 12
13
Agenda

• Why Do We Need a Federal Enterprise
  Architecture?
• Draft Business Reference Model, Version 2.0
• Draft Performance Reference Model
• Draft Services Component, Technical, and Data
  Reference Models
• Next Steps

14
The Business Reference Model (BRM), Version 1.0
was published in July 2002 for use in the FY 2004
budget process
Government to Citizen Access Channels
Internet/ Portal
Services to Citizens
Services to Citizens
Program Admin
Compliance
Program Admin
Compliance
Public Asset Management
Public Asset Management
Regulated Activity Approval
Regulated Activity Approval
On average 10 Cabinet Departments and agencies
per Line of Business
Marketable Asset Management
Marketable Asset Management
Consumer Safety
Consumer Safety
Defense Natl Security Ops
Defense Natl Security Ops
Environmental Management
Environmental Management
Diplomacy Foreign Relations
Diplomacy Foreign Relations
Law Enforcement
Law Enforcement
Disaster Management
Disaster Management
Legal
Legal
Domestic Economy
Domestic Economy
Revenue Collection
Revenue Collection
Education
Education
Trade (Import/Export)
Trade (Import/Export)
Energy Management
Energy Management
Transportation
Transportation
Insurance
Insurance
Workforce Management
Workforce Management
Employee to Employee Access Channels
Public Health
Public Health
Recreation National Resources
Recreation National Resources
Social Services
Social Services
RD Science
RD Science

• Telephone
• Voice
• Interactive

Web Services
E-system to System
Public/Private Partnerships
Intranet/ Portal
Face to Face
Fax
On average 21 Cabinet Departments and agencies
per Line of Business
Mail
Support Delivery of Services
Legislative Management Business Management of
Information IT Management Planning and Resource
Allocation Regulatory Management
Controls and Oversight Public Affairs Internal
Risk Management and Mitigation Federal Financial
Assistance
All 24 Cabinet Departments and agencies per Line
of Business
Internal Operations / Infrastructure
Inter-Agency
Intra-Agency
Human Resources, Financial Management Admin
Supply Chain Management
Human Resources, Financial Management Admin
Supply Chain Management
Page 14
15
Analysis of agencies FY 2004 budget submissions
against the BRM, Version 1.0 revealed
multi-billion dollar consolidation opportunities
across the Federal Government

• Consolidate and migrate agency investments to the
  24 E-Government initiatives
• Identify overlaps and leverage assessment on IT
  spending for common functions
• Financial Management
• Human Resources
• Data and Statistics Development
• Monetary Benefits
• Criminal Investigations
• Public Health Monitoring
• Leverage enterprise licensing and buy at
  commercial benchmarks or less

Page 15
16
OMB has developed and issued the draft Business
Reference Model, Version 2.0 for Federal agency
review and comment
DRAFT Business Reference Model Version 2.0
LEVEL 1 the purpose of government (what are the
performance goals)
LEVEL 2 the process used (how does the
government accomplish these goals)
LEVEL 3 the management and support functions
necessary to run the government and its programs
Page 16
17
Within the revised BRM, the new Mode of Delivery
layer and the revised and renamed Services for
Citizens layer should be thought of collectively

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

Services for Citizens
LEVEL 1

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

Mode of Delivery
LEVEL 2
With this construct in place, all Government
programs, agencies, mission-related IT systems,
etc., can be mapped to both a Service for
Citizens and a Mode of Delivery
Page 17
18
The Draft BRM, Version 2.0 aligns with three
critical management frameworks and improvement
initiatives

• The Presidents Budget and Performance
  Integration Initiative and the FEA Performance
  Reference Model
• The revised model differentiates between the
  purpose of the government and mechanism/process
  used to deliver services to the customer
• This distinction aligns with the Performance
  Reference Models focus on outcomes (purpose of
  government) and outputs (mechanism/process)
• OMBs Budget Function Classifications
• These classifications provide a similar
  functional description of Federal activities
• JFMIPs New Framework for Financial Management
  Systems
• Work on ensuring this alignment is ongoing, and
  with JFMIPs assistance, the final version of the
  BRM, Version 2.0 will fully reflect the new
  framework

Page 18
19
Draft Business Reference Model, Version 2.0
the revised Services for Citizens Business Area
Page 19
20
Draft Business Reference Model, Version 2.0the
new Mode of Delivery Business Area
Page 20
21
Draft Business Reference Model, Version
2.0Support Delivery of Services
While this Line of Business is considered a
support service for the management of the
government, it does represent the purpose of
the governments central management
organizations, and can therefore be thought of
with the Level 1 Lines of Business to facilitate
certain analyses.
Page 21
22
Draft Business Reference Model, Version
2.0Management of Government Resources
Note BRM Version, 2.0 continues to distinguish
between agency-centric and government-wide
resource management.
Page 22
23
Agenda

• Why Do We Need a Federal Enterprise
  Architecture?
• Draft Business Reference Model, Version 2.0
• Draft Performance Reference Model
• Draft Services Component, Technical, and Data
  Reference Models
• Next Steps

24
The Draft FEA Performance Reference Model
(PRM)At-A-Glance
25
The PRM will help agencies identify the
performance improvement opportunities that will
drive Government transformation
Page 25
26
The PRM supports the Presidents Budget and
Performance Integration initiative, which is
taking two approaches to strengthen the link
between budget dollars and results.
Page 26
27
The PRM structure is designed to clearly
articulate Line of Sightthe cause and effect
relationship between inputs, outputs and outcomes
Page 27
28
Example Operationalizing the PRM for the
Resource Training and Development sub-function
(Human Resources Line of Business) of the FEA
Business Reference Model
Page 28
29
Example Operationalizing the PRM for IRS Free
Filing, a Presidential Priority E-Gov Initiative
Page 29
30
Agenda

• Why Do We Need a Federal Enterprise
  Architecture?
• Draft Business Reference Model, Version 2.0
• Draft Performance Reference Model
• Draft Services Component, Technical, and Data
  Reference Models
• Next Steps

31
In addition to the Business and Performance
Reference Models, the FEA includes three models
that specifically address information technology
the Service Component, Technical and Data
Reference Models
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 Layers
Service Types
Service Components
Page 31
32
The SRM framework consists of seven (7) Service
Layers with 27 supporting Service Types and 143
Service Component Areas
The Draft Service Component Reference Model (SRM)
is a business-driven, functional framework that
classifies capabilities (or service components)
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)
Common Services
Digital Asset Services
Service Components
Business Analytical Services
Back Office Services
Service Layers
Page 32
33
The SRM is supported by multiple access and
delivery channels that provide a foundation for
accessing and leveraging the Service Component
Accessing the Component (Example Renewal of
Drivers License )
Access Channels (FEA-TRM)
Mobile, Wireless
Web Browser
PDA
Kiosks
Private/Public Partnership
Other
System to System
EAI
Web Service
Phone, Fax
Delivery Channels (FEA-TRM)
Intranet
Extranet
Peer to Peer
Internet
Mail
Face to Face
Portal
Marketplace
Exchange
Commerce
Integration
Service Level Agreement to structure how Service
Components are accessed and leveraged
Service Layers, Service Types, and Service
Components (FEA-SRM)
Page 33
34
The SRM will assist in defining business process
and performance gaps that may be leveraged to
improve services to stakeholders (citizens,
business partners, agencies)
Access Channels (FEA-TRM)
Access Channels (FEA-TRM)
Delivery Channels (FEA-TRM)
Delivery Channels (FEA-TRM)
What level of process, performance, and outcome
is the Service Component achieving? Does this
help to close a performance gap?
Performance Measures (FEA-PRM)
Business Process
Performance Measures
Service Layers, Service Types, and Service
Components (FEA-SRM)
Page 34
35
The Draft Technical Reference Model (TRM)
supplements existing TRM and E-Government
guidance by providing a foundation to advance the
reuse of technology and service components from a
Government-wide perspective

• Citizen Focused
• Interoperability, State / Local
• Service Component / Technology Reuse, CBA
• Government Technical Standards
• Strengthen e-Gov Act

E-Gov Guidance Office of Management and
Budget FEA-TRM

• e-Government Technology Specifications
• e-Government Building Blocks, Assembly
• OSE/OSI Service Layers, NIST

eGov Direction FEAW/CIO Council

• OSE/OSI Service Layers, NIST
• Strategic Planning, IT Capital Planning
• Baseline -gt Target Enterprise Architectures

STRATEGIC TRANSFORMATION (Partnering
Relationships)
Agency Level EA/TRM

• Baseline -gt Target Enterprise Architectures
• Mission Accomplishment
• Initiative Identification / Management

Bureau Level EA/TRM
State and Local
Integrated Enterprise Architectures (Interoperable
, Maximum Reuse of Components)
Page 35
36
The TRM provides an effective means by which
service components can be leveraged, built, and
deployed across the Federal Government
Service Access and Delivery
- Mobile, Wireless, Web
Access Channels
- Internet, Intranet, Extranet
Delivery Channels
- Section 508, Privacy, Security
Service Requirements
- HTTP, HTTPS, WAP, TCP/IP
Service Framework
Component Architecture
Security
- SOAP, XML, UDDI, WSDL
Service Interface / Interoperability
Service Transport
Presentation / Interface
Business Logic
Data Interchange
Service Platforms
Data Management
- J2EE, Windows .NET
Service Platforms
Page 36
37
The TRM will provide guidance and recommendations
that support the development and implementation
of service components that embrace a
Component-Based Architecture
Partial List
Security
Component Architecture

• X.509
• NIST / FIPS 186
• Secure Socket Layers (SSL)

Security
Presentation / Interface
Business Logic
Presentation / Interface
Data Interchange

• HTML
• JSP, ASP, ASP.Net
• DTHML, CSS, XHTMLMP

Data Management
Data Management
Business Logic
Data Interchange

• XML
• ebXML
• RDF, WSUI
• XSLT

• Java/J2EE (EJB)
• C, C, JavaScript
• COM/COM, C
• Visual Basic

• XBRL, JOLAP, OLAP
• JDBC, ODBC
• ADO, ADO.Net

Page 37
38
Each tier is comprised of multiple categories
that describe the technologies, standards, and
specifications that support the service component
FEA Technical Reference Model (TRM) - Snapshot
Service Access and Delivery
Service Framework
Service Platforms
Access Channels
Service Transport
Supporting Platforms
Component-Based Architecture
Web Servers
Delivery Channels
Application Servers
Security
Service Requirements
Development Environment
Presentation / Interface
Database / Storage
Business Logic
Data Interchange
Hardware / Infrastructure
Data Management
Service Interface and Interoperability
Page 38
39
Taken together, the TRM and other FEA reference
models can be leveraged to support the creation
and integration of cross-agency service components
U.S. Customs (New eGov 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 weight?
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
eGov Architecture Guidance
Federal Enterprise Architecture
Page 39
40
The Draft Data and Information Reference Model
(DRM) will support investment and E-Gov planning
by providing a framework for agencies to leverage
existing data components across the Federal
Government
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
41
The DRM framework is comprised of four
interrelated levels that independently classify
and categorize data to one or more areas of the
Business Reference Model
FEA Data Reference Model Overview of Framework
Conceptual
FEA Business Reference Model (BRM)
Business Area, Line, Function
Collection of supporting data object components
that contribute to the definition of the Business
Line Function or Sub-Function
Object Class Components
One or more common components /schemas that
describe a specific process or object
Aggregate Components (Aggregate BIE or ABIE)
Level of Granularity / Re-Use
Level of Context
Common Components (Business Information Entity -
BIE)
The most elemental block of data that is
descriptive of a business process or object
Core Component Type Data Type
The physical property of the Data
42
Agenda

• Why Do We Need a Federal Enterprise
  Architecture?
• Draft Business Reference Model, Version 2.0
• Draft Performance Reference Model
• Draft Services Component, Technical, and Data
  Reference Models
• Next Steps

43
Near-Term Next Steps for the FEA

• Address Agency comments on Draft Service
  Component and Technical Reference Models (due on
  March 7th), prepare Comment Response Documents,
  and issue Version 1 of the models by end-March
• Continue consultations with defense and
  intelligence agencies to obtain their input for
  the Business Reference Model, Version 2.0
• Address Agency comments on Draft Business
  Reference Model, Version 2.0 (due on March 14th),
  prepare Comment Response Document, and issue
  updated model by end-March
• Address OMB comments on Draft Performance
  Reference Model, issue draft model for Federal
  Agency review by end-March, and conduct Agency
  briefing in early April
• Continue to define and validate the Data
  Reference Model
• With CIO Council Subcommittees, develop guidance
  on use of the FEA reference models during the FY
  2005 budget formulation process and post guidance
  to www.feapmo.gov
• Launch FEAMS on www.feapmo.gov by early April

Page 43