Federal Enterprise Architecture: The Challenges and Changes

1
Federal Enterprise ArchitectureThe Challenges
and Changes

• Michael Tiemann
• Enterprise Architecture Practice Manager

May 2005
2
Abstract Bio

• This speech presents the summary of many
  seemingly disparate Federal Enterprise
  Architecture (FEA) initiatives now on-going and
  explains the presenter's views both in his
  historical context and with respect to future
  directions and possibilities for the FEA.  It
  will open the dialogue to questions like
• Will EA be able to significantly change the
  Federal Government or government in general if it
  continues to be narrowly focused on IT?
• How can such an expansive program with such
  potential impact continue to be run by an office
  with only one permanent FTE and a set of
  rotational volunteers with a few contractors?
• How will the issued resultant from GAO and the
  OMB both measuring agencies EAs by different
  means play out especially with GAO now starting a
  new government-wide review?
• Can the LoB concept for collaborations across the
  government work to instantiate the FEA and what
  will be required to make this happen?
• What are the significances of the new DRM, the
  various profiles (Geospacial and Records
  Management) and mechanisms like Core.gov and
  certifying Federal components like
  E-authentication?
• What must happen for the FEA to continue as
  opposed to break under its own weight?
• All these questions and more will be asked and
  discussed in an interactive presentation, with an
  eye towards what can and should happen for the
  FEA to proceed and ultimately succeed.
• Bio
• Mike Tiemann currently is employed by ATT as the
  Enterprise Architecture (EA) Practice Manager a
  role he accepted after 31 years distinguished
  service in the Federal Government. He was the
  Program Manager (PM) for Information Resources
  Management Planning headquarters-wide at the
  Department of Energy (DOE). In 1994, he became
  the PM for the DOE-wide Information Architecture,
  before the Clinger-Cohen Act. He served as the
  DOE Chief Architect until 1997. From then,
  almost until he left federal service in 2002, he
  served as the Director, Division of Architecture
  and Standards and during 2001, as Acting
  Associate CIO for Architecture, Standards and
  Planning. He was the DOE representative to the
  Federal CIO Councils Architecture and
  Infrastructure Committee and was the founding
  Chair and later Co-chair of the Federal
  Architecture Working Group. Mike is an outspoken
  advocate for EA, writing and commenting about it
  in current periodicals and lecturing on it at
  numerous Federal and industry conferences and
  forums, including past E-Gov EA Conferences and
  as a faculty member of the Federal EA
  Certification Institute. Mike has received
  numerous performance awards and citations,
  including, Federal Computer Weeks Federal 100
  Award, the Federal CIO Council Citation and
  Special Recognition and Act Awards from the
  Secretary and Deputy Secretary of Energy. Mike
  holds a Bachelors of Environmental Design
  (Architecture) from Texas AM University and a
  Masters of Science in Systems Management from
  University of Southern California. He is on the
  Industry Advisory Councils Enterprise
  Architecture Shared Interest Group leadership
  team, and as such, represents IAC on the Chief
  Architects Forum. He is a member of the
  Association of Enterprise Architects and an
  Associate Editor of the a/EA Journal He lives in
  Northern Virginia, is married and has two
  children.
• He will be leaving ATT and joining
  BoozAllenHamilton as a Senior Associate later
  this month.

3
Todays IT Governance Challenges
Presidential ManDates
E-Government
Federal Enterprise Architecture
Standards
Business Reference Model
BUDGET CUTS
OMB Review
Business Cases
HR- Brain Drain
Technology Changes
Resizing Redirection of Programs
Leadership-Loss
SECURITY
GAO AUDITS MATURITY
Semantic Interoperability
Access Vs. Privacy
4
You may have questions like these?

• Will EA be able to significantly change the
  Federal Government or government in general if it
  continues to be narrowly focused on IT?
• How can such an expansive program, with such
  potential impact, continue to be run by an office
  with only one permanent FTE and a set of
  rotational volunteers and a few contractors?
• How will the issues resultant from GAO and the
  OMB both measuring agencies EAs, by different
  means, play out especially with GAO now starting
  a new government-wide review?
• Can the LoB concept for collaborations across the
  government work to instantiate the FEA and what
  will be required to make this happen?
• What are the significances of the new DRM, the
  various profiles (Geospacial and Records
  Management) and mechanisms like Core.gov and
  certifying Federal components like
  E-authentication?
• What must happen for the FEA to continue, as
  opposed to break under its own weight?

5
Agenda
6
What is the Federal Enterprise Architecture

• Some definitions to start
• What it is and is not
• The reference models and their evolution
• The parts of the FEA

7
Federal Enterprise Architecture - What is
it?Some terms-

• Enterprise architecture A management process
  that uses an analytical approach to develop an
  enterprise-wide knowledgebase used in decision
  making to, among other things, ensure IT
  alignment in support of business/mission
  functions. It typically has an As-Is, To-Be and a
  Transition Plan.
• FEA Reference Models A set of five modeled
  views of the federal enterprise used to determine
  alignment and compliance. They are the
  PRM,BRM,SRM,DRM and TRM. Now also added are the
  growing number of profiles including Security and
  Privacy, Geospacial and Records Management .
• FEAPMO - The Federal EA Program Management
  Office (Richard Dick Burk is the Chief
  Architect) in the OMB under the Deputy
  Administrator for E-government (Karen Evans).
• Chief architect The manager usually in the
  Agencys Office of the CIO, responsible for EA
  program development and management. Most every
  agency has one.

8
FEA What is itmore terms.

• Exhibit 300 Information OMB requires to be
  filed for each major IT investment with the
  budget, every year. Also it is referred to as the
  investment business case. Every major agency was
  required to submit a consolidated EA Program
  Exhibit 300 (identifies funding department-wide)
  last year.
• Lines-of-Business Crosscutting business areas
  or support functions where the government is
  beginning to consolidate functions, systems or
  technology or all three. Current LOBs are
• National Health Architecture
• Financial Systems
• Grants
• Human Resources
• Case Tracking
• Two new LOBs Security and Information Sharing

9
Termscont.

• E-Gov Initiatives 25 E-Gov or IT systems
  initiatives, also referred to as the presidential
  or quicksilver initiatives, covering
  collaborative services or capabilities and public
  access. Agencies are compelled to participate or
  use these systems. They include E-Grants,
  Recreation One Stop, E-Travel, E-Authentication,
  E-Pay and others.
• CPIC Capital Planning and Investment Control
  The process that compliments EA and is focused on
  management of the agency IT Portfolio and
  ensuring appropriate project management and
  performance controls and reviews. Theoretically,
  projects perpetually 10 behind schedule or over
  costs should be terminated. This past year 342 of
  11087 IT investments were put on OMBs watch list
  (total worth 15B).

10
Framework and Methods Evolution
Zachman and Spewak
To DoDAF(C4SI) and FEAFTo
11
Federal EA Reference Models
The FEA was established by OMB, with support from
the Federal CIO Council.
Source FEAPMO - OMB
12
A Concept for Integrating the FEA Reference
Models The E-Gov Initiatives and LoBs with the
modified FEAF
Agency Mission/Business Strategic Plan
E-Gov Initiatives

• Lines-of-Business
• Health Architecture
• Grants Administration
• Human Resources
• Financial Services
• Case management
• Security Services
• Budget

Agency IT Strategic Plan
Note that this also fits in the Agency
Mission and IT Strategic Plans
13
The FEA Reference Models
Performance Reference Model V 1.0 (PRM)
Business Reference Model V 2.0 (BRM)
Service Component Reference Model V 1.0 (SRM)
Security Privacy Profile
Records Mgmt Profile
Data Reference Model V1.0 (DRM)
Technical Reference Model V 1.1 (TRM)
Relationships, Use, Understanding agencies need
it.
Geospacial Profile
14
A view of the FEA Program Parts
Source FEAPMO - OMB
15
One view of the FEA
The FEA provides a set of common, reusable
components
Source FEAPMO - OMB
16
Which EnterpriseArchitecture?
Federal Enterprise Architecture
Agency Z
Site
Agency X
Region
Site
Bureau
Administration
Bureau
Lab
Office
STATE
Office
Agency Y
Region
Site
Region
Site
Program
Program
Board or Commission
Site
Office
Site
17
OMB and CIO Council FEA Support Structure
Vacant
Chief Technology Officer
What do you think would be required to develop
and implement a well orchestrated Federal EA?
FEA PMO
Richard Dick Burk
Support Contractor
Chief Enterprise Architect
Detailee
Detailee
Detailee
Detailee
Detailee
Supporting Partners
Lines of Business
OMB Portfolio Managers
Governmentwide Groups
Chief Architects Forum
State and Local (NASCIO)
NASCIO
Industry Working Groups (i.e., OMG, ,Open Group
w3.org), others
Industry ACT/IAC EA -SIG
18
Principles of the FEA PMO
Principles

• EA is Business-driven
• Collaborative across the Federal government
• Architecture improves the effectiveness and
  efficiency of government information resources

Source FEAPMO - OMB
19
FEA Roadmap to Government Transformation
Source FEAPMO - OMB
20
So what about EA in the Federal Government?

• Last year over 500 million dollars programmed in
  the budget for EA work (not including CPIC
  support) just on the Civilian side.
• More than that on the Defense side (Army, Navy,
  AF DoD).
• Beside EA work, much related work in areas
  touching EA SDLC, Security, Privacy,
  Accessibility CPIC Investments Management.
• Congress decreed that DoDs failure to align
  major investments to its EA is anti-deficiency
  (miss appropriation of funds) potentially
  punishable by jail time!!! Comptrollers seek out
  the EAs in DoD.
• The FEAPMO Plans will further ramp up the
  requirements to show EA Alignment of Investments
  with EAAF 2.0.

21
Early Benefits of EA to the Government

• Identification of vast array of IT resources and
  opportunities for consolidated purchasing and
  management of infrastructures
• Ability to question whether consolidation or
  coordination in Lines-of-Business or e-Gov
  services makes sense
• In the Case of Homeland Security - EA has
  postured them to more quickly move forward with
  restructuring and realignment of major systems
  and to let key procurements (UICDS,IWINS)
• DoD has made significant strides in modernization
  and transformation of warfighting supported by
  their DoDAF based EAs

22
(No Transcript)
23
High Level Business Proposition

• Government Requirement ALL AGENCIES MUST HAVE
  EAs and their Major Investments (IT Projects)
  must be aligned to the EA
• Infrastructure and Large Systems Projects not
  aligned may be turned down
• Increasingly Government Agencies will be asked to
  develop common solutions within Federal Lines of
  business (Justice, healthcare, case
  tracking..etc)
• Projected Savings, Lowered Costs, Higher
  Performance are critical factors for Agency
  EAsso EA will be tightly coupled to the PART
  management Scores by OMB-ongoing.

24
So what are the FEA-PMOs Objectives and what do
they believe are the challenges?

• Need to focus on Outcomes of Government
• Business/Mission
• Need to emphasize and measure use of the EAs in
  decisionmaking and holding agencies accountable
• Looking for more Lines of Business
• Have to find ways to help agencies transform and
  perform
• Must see (make visible) the benefits of EA

25
FEA PMO 2005 E-Gov Strategic Initiatives

• Articulate FEA value and build trust with EA
  partners
• Evolve the FEA to drive results
• Develop and evolve the LoBs and
• other collaborative opportunities
• Measure EA value with the EA Assessment Program

26
FEA PMO 2005 Strategic Initiatives
1. Articulate FEA value and build trust with EA
Partners

• Refine the FEA value proposition
• Develop and implement a
• communications strategy
• Gather and share EA case
• studies

Source FEAPMO - OMB
27
FEA PMO 2005 Strategic Initiatives
2. Evolve the FEA to drive results

• Establish and implement a governance framework
• Link the PRM to the PART
• Evolve the BRM to align EA to strategic
  planning
• Complete the development of the DRM -ONGOING
• Engineer the FEA to standardize linkages
  between Reference
• Models
• Update the Security and Privacy Profile ONGOING
  (Version 2)
• Launch a Records Management Profile ONGOING
• Create a Geospatial Profile - ONGOING

Source FEAPMO - OMB
28
FEA PMO 2005 Strategic Initiatives
Source FEAPMO - OMB
29
FEA PMO 2005 Strategic Initiatives
Source FEAPMO - OMB
30
Collaborative involvement sought by FEAPMO
Source FEAPMO - OMB
31
Plan Revised DRM Structure
Source M. Daconta, DRM WG
32
An XML-ized DRM View
33
(No Transcript)
34
Chief Information Officer
Executive Review Boards
35
Vision - An INTEGRATED CITIZEN-Centric GOVERNMENT
True Horizontal and Vertical Information
Integration Sharing and Reuse
XML and other STANDARDs AND INTERFACES
County and Tribal
Facilitated by Standards, Components, and
Practices EA and consistent CPIC and security
integration.
36
OMB EAAF Results 24 of 25 Major agencies scored
3.0 or higher

• GAO just started a review using its EAMMF which
  will show different results than OMBbecause the
  two frameworks are different and scored
  differently.
• OMB is changing the EAAF to version 2.0 in the
  fall reframing focus on the results that EA is or
  is not achieving rather than on the Completion of
  the EA.
• This will cause confusionagain.
• In the next few months there will be a number of
  new issuances- DRM, Records Management Profile,
  Geospacial Profile, EA Glossary lots of changes

37
For More Information
Michael Mike Tiemann EA Practice
Manager tiemann_at_att.com 703-506-5133
(Office) 202-255-5887 (mobile)
EAPTM is our Core Methodology