Federal Enterprise Architecture (FEA):Opportunity for Better AutomationOpportunity for Better Ways of Doing Business

Presentation to the MD CFUG

Dorothy FirschingUrsa Major Consulting, LLC

Dorothy@Firsching.com(703) 425-6236

June 10, 2003

04/08/23 2

Agenda

Why We need a Federal Enterprise Architecture The President’s Agenda and VisionThe Federal Enterprise Architecture (FEA) and its ComponentsOur Current Project, the Enterprise Architecture for the JWOD ProgramWhere the FEA is taking us – Future Potential

Note: the FEA part of the presentation draws from numerous FEA briefings over the past several months, mostly by Bob Haycock, FEA Program Manager, OMB

04/08/23 3

Architecture Stories: “User Requirements” Are Not Enough, or Why We Need a Federal Enterprise Architecture

Unnamed Govt. Agencies “Our department is different” “Our department has the correct data” “Our people already know this database” “Buy the equipment and software quickly

with End of FY $$, we’ll use them anyway” “What do you mean, Access won’t scale?” “We can get Perl scripts for free” “Why is the system so slow?” “Who designed this, anyway?”

04/08/23 4

Results Working systems that meet specific requirements, but are not optimal for the overall organization Clumsy systems for the ultimate user Automating the Wrong Thing Re-inventing the Wheel “Stovepipes” Personal Systems, Spreadsheets Duplicated, inconsistent data Litigation

But the Developers met the stated User Requirements at the time!

04/08/23 5

Extensive 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

Page 5

* Urgent Business for America: Revitalizing the Federal Government for the 21st Century. The Report of the National Commission on the Public Service, January 2003.

04/08/23 6

Extensive 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 toaid the homeless

7 agencies administer 40 different job training programs

04/08/23 7

This is not a technical problem! (or is it?)

Systems are specified without an enterprise-level understanding of the:

How they support the Mission Objectives Business processes (e.g., supply chain) Existing technical architecture New technology initiatives

In the Federal Government, there is no good way today to gain cross-agency, cross-organization insight.

… and the supply chain today goes BEYOND the Federal Government

Post-911 coordination between Office of Homeland Security, other Federal agencies, State, and Local law enforcement, Fire departments, etc.

04/08/23 8

Strategic Management of Human Capital Restructure agencies to be citizen-centered Adopt IT to capture employees’ knowledge and skills

Competitive Sourcing

Improved Financial Performance

Expanded Electronic Government Simplify and unify around citizen needs Support projects that offer performance gains across agency

boundaries Maximize interoperability and minimize redundancy

Budget and Performance Integration Use performance information to make budget decisions Link performance and cost in a performance budget

The President’s Management Agenda

04/08/23 9

E-Government: Unification and simplification around citizen needs

For individuals Easy to find, one-stop shops for citizens – creating single points

of easy entry to access high-quality governmental servicesFor 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 9

04/08/23 10

The Vision:

Order of magnitude improvement in the federal government’s value to the citizen; with decisions in minutes or hours, not weeks or months

Order of magnitude improvement in the federal government’s value to the citizen; with decisions in minutes or hours, not weeks or months

04/08/23 11

How?

Unify Infrastructure Unify access to data stores Collect the data once (requires agreement on data

definitions) Integrate customer interface Monitor and measure (define success and measure)

Simplify Processes Define and build integrated delivery channels

The Teeth If you don’t play, you don’t get funded The FEA is a framework for making IT investment decisions

for FY 2005 Budget (Form 300s)

The Federal Enterprise Architecture

04/08/23 13

The Federal Enterprise Architecture (FEA) is:

A Business-Focused Framework for Cross-Agency, Government-wide ImprovementA new way of describing, analyzing, and improving the Federal Government and its ability to serve the citizen

The 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

04/08/23 14

Business Reference Model (BRM)• Lines of Business• Agencies, Customers, Partners

Service Component Reference Model (SRM)

Technical Reference Model (TRM)

Data Reference Model (DRM)• Business-focused data standardization • Cross-Agency Information exchanges

Bu

sin

ess-D

riven

Ap

pro

ach

Performance Reference Model (PRM)

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

Federal Enterprise Architecture (FEA)

Com

pon

en

t-Based

Arc

hite

ctu

re

• Service Layers, Service Types• Components, Access and Delivery Channels

• Service Component Interfaces, Interoperability• Technologies, Standards Recommendations

The FEA is a set of inter-related “reference models” to facilitate collaboration and information sharing

04/08/23 15

The FEA Business Reference Model (BRM) is a framework for describing the Lines of Business performed by the Federal Government independent of the Agencies that perform them

Internal Operations / InfrastructureHuman Resources, Financial Management Admin

Supply Chain Management Human Resources, Financial Management Admin

Supply Chain Management

Inter-Agency

Support Delivery of ServicesLegislative ManagementBusiness Management of InformationIT Management, Regulator ManagementPlanning and Resource Allocation

Controls and OversightPublic AffairsInternal Risk Management and MitigationFederal Financial Assistance

WebServices

Telephone-Voice-Interactive

E-systemto System

Public/PrivatePartnerships Fax

Face toFace Mail

Program Admin ComplianceServices to Citizens

Public Asset ManagementMarketable Asset ManagementDefense & Nat’l Security OpsDiplomacy & Foreign RelationsDisaster ManagementDomestic EconomyEducationEnergy ManagementInsurancePublic HealthRecreation & National ResourcesSocial ServicesR&D & Science

Regulated Activity ApprovalConsumer Safety

Environmental ManagementLaw Enforcement

LegalRevenue Collection

Trade (Import/Export)Transportation

Workforce Management

Program Admin ComplianceServices for

CitizensPublic Asset ManagementMarketable Asset ManagementDefense & Nat’l Security OpsDiplomacy & Foreign RelationsDisaster ManagementDomestic EconomyEducationEnergy ManagementInsurancePublic HealthRecreation & National ResourcesSocial ServicesR&D & Science

Regulated Activity ApprovalConsumer Safety

Environmental ManagementLaw Enforcement

LegalRevenue Collection

Trade (Import/Export)Transportation

Workforce Management

Telephone-Voice-Interactive

E-systemto System/

Web Services

Public/Private

PartnershipsFax Kiosk Face to

Face MailInternet/Portal

Intranet/Portal

Citizen to GovernmentAccess Channels

Government Employee to Employee Access Channels

04/08/23 16

Business Reference Model (BRM) Status

Version 1.0 published in July 2002 Used in the FY 2004 budget processAnalysis of agencies’ FY 2004 budget submissions revealed multi-billion dollar consolidation opportunities across the Federal Government

Financial Management Human Resources Data and Statistics Development Monetary Benefits Criminal Investigations Public Health Monitoring Need for Enterprise licensing

Version 2.0 is in Final Agency Review

04/08/23 17

The Performance Reference Model (PRM) will help agencies identify the performance improvement opportunities that will drive Government transformation

TechnologyTechnology

Strategic Outcomes

Value

Business Results

•Mission Achievement / Outcomes•Financial

Business Results

Customer Results

•Customer Satisfaction•Service Coverage•Timeliness & Responsiveness•Service Quality•Service Accessibility

Customer Results

Processes and Activities•Financial•Productivity and Efficiency•Cycle and Resource Time

Processes and Activities

Technology•Financial•Quality & Efficiency•Information & Data•Security & Privacy•Reliability & Availability•User Satisfaction•IT Management

TechnologyOther Fixed

Assets•Financial•Quality, Maintenance, & Efficiency•Security & Safety•Utilization

Other Fixed AssetsPeople

•Employee Satisfaction & Quality of Worklife•Recruitment & Retention•Employee Development•Employee Ratios

People

OUTPUTS: Measurement of day-to-day activities agencies conduct, as driven by desired business and customer results

OUTCOMES: Mission-critical results measured from a business, program, or customer perspective

INPUTS: People, technology, and other assets, measured by their contribution

• Financial• Quality, Maintenance & Efficiency• Security & Safety Utilization

• Financial• Quality & Efficiency• Information & Data• Security & Privacy• Reliability & Availability• User Satisfaction• IT Management

• Employee Satisfaction• Recruitment & Retention• Employee Development• Employee Ratios

• Financial• Productivity & Efficiency• Cycle and Resource Time

• Quality• Security & Privacy• Mgmt. & Innovation

• Mission Achievement• Outcomes• Financial

• Customer Satisfaction• Service Coverage• Timeliness & Responsiveness• Service Quality• Service Accessibility

04/08/23 18

The Service Component Reference Model (SRM) classifies capabilities (or service components)

Regulatory Management

Support Deliveryof Services

Policy and Guidance Devel.Public Comment TrackingRegulatory DevelopmentRule Publication

Knowledge MgmtCRMContent MgmtCollaborationSearchPortalPersonalization

BusinessReference Model

( BRM )

Rule Publication

Service ComponentReference Model

( SRM )

Technologies

Platforms J2EE .NET Windows NTData Mgmt ODBC JDBCBusiness Logic

TechnicalReference Model

( TRM )

Performance Reference Model ( PRM )Outcomes and Measures

Business lines and functions

Supporting technologyand standards

Enabling capabilities, components, and

services

Component-Based ArchitectureService Layers Service Types Service Components

Data and Information Reference Model (DRM)Classification, Categorization, XML, Sharing

04/08/23 19

Examples of Service Components of a Business Function (Technology and Agency Independent)

Business Function: Regulatory Management

BRM

SRM(Service

Components)

Customer RelationshipManagement

ContentManagement

DocumentLibrary

SearchEngine

Personalization /Subscriptions

Access Control,User Management

Problem Tracking,Case ManagementPayment Collection

(Pay.Gov)

A Service Component is a functional capability which assists the business in accomplishing its mission

04/08/23 20

The FEA Technical Reference Model (TRM) is a component-driven, technical framework that identifies the standards and specifications that comprise a Service Component

Regulatory Management

Support Deliveryof Services

Policy and Guidance Devel.Public Comment TrackingRegulatory DevelopmentRule Publication

Knowledge MgmtCRMContent MgmtCollaborationSearchPortalPersonalization

BusinessReference Model

( BRM )

Rule Publication

Service ComponentReference Model

( SRM )

Technologies

Platforms J2EE .NET Windows NTData Mgmt ODBC JDBCBusiness Logic

TechnicalReference Model

( TRM )

Performance Reference Model (PRM)Outcomes, Measurements, Metrics

Business lines and functions

Supporting technologyand standards

Enabling capabilities, components, and services

Component-Based Architecture

Service Layers Service Types Service Components

Data and Information Reference Model (DRM)Classification, Categorization, XML, Sharing

04/08/23 21

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

Delivery Channels

Service Requirements

Service Transport

Component-BasedArchitecture

Service Interface andInteroperability

Supporting Platforms

Web Servers

Application Servers

Security

Presentation / Interface

Business Logic

Data Interchange

Data Management

Development Environment

Database / Storage

Hardware / Infrastructure

04/08/23 22

Collectively, the TRM technical tiers provide a robust and effective foundation to support the reuse and delivery of service components

How to leverage and

access Service Components

How to build, deploy, and exchange Service

Components

How to support and maintain

Service Components

Service PlatformsServ

ice Inte

rface

/

Inte

ropera

bili

ty

Security

Presentation / Interface

Business Logic

Data Management

Data Interchange

Component ArchitectureService

Framework

ServicePlatforms

Serv

ice T

ran

sport

FEA – Technical Reference Model

Service Requirements

Delivery Channels

Access ChannelsService Access

and Delivery

04/08/23 23

As a foundation, the tiers within the FEA TRM reside across a typical network and application topology

Outside World Demilitarized Zone(DMZ)

Internal Network

Dom

ain

Firew

all (A

CL, IP

’s)Components

Databases

DirectoryServices

BusinessIntelligence

Acce

ss Channels

Deliv

ery

Ch

annels

Serv

ice R

equ

irem

ents

Serv

ice T

ran

sport

Pro

toco

l Firew

all (H

TTP, P

ort 8

0)

ServicePlatforms

(J2EE, .NET)

Presentation / Interface

Serv

ice In

terfa

ceLeveraging or UsingA Service Component

Building a Service Componentor Application

Business Logic

Data Interchange

Data Management

Security

Synchronous / Asynchronous

04/08/23 24

The Federal Enterprise Architecture Management System (FEAMS)Personalization (My FEAMS), Content Aggregation

Options to PersonalizeContent within each dialog box

Aggregation and roll-ups of data to support rapid navigation

Visualization tools to graphically illustrate cross-agency synergy possibilities

DownloadableReports andGuidance

The Federal Enterprise Architecture Framework (FEAF)

04/08/23 26

Engineering the Transition

Current“As-Is”

Architecture

Target“To-Be”

Architecture

As-Is To-Be

StrategicDirection

Standards

Transitional Processes

Perf

Business

Applications

Data/Information

Technology

Perf

Business

Service Comp.

Data/Information

Technology

Engineer forAgency

Map to FEA(Ultimately,

Re-Use)

04/08/23 27

The FEA and Agency Frameworks

The FEA is the Enterprise Architecture for the ENTIRE Federal Government (Top-Down Categorization)Federal EA Frameworks

The Federal Enterprise Architecture Framework (FEAF), developed by the CIO Council

FEAF Version 1.1, September 1999, is Current, Version 2 is Stalled

Nonrestrictive; Agencies Can Interpret The DOD Architecture Framework (DODAF), based on the

C4ISR (Command, Control, Communications, Computers, Intelligence, Surveillance and Reconnaissance) Framework

The Treasury Enterprise Architecture Framework (TEAF) The EA Management Maturity Framework (GAO v.1.1 4/2003)

04/08/23 28

The Teeth

Agencies must develop and maintain an enterprise architecture Mandated by Clinger-Cohen Act of 1996 Must be referenced in Budget Submissions By collaboration and re-use, can share costs FEA will help to identify areas for re-use FEAMS will be repository of Agency

Architectures

04/08/23 29

The FEAF – Peeling the Onion based on the Zachman Framework

Perspective Data Architecture

Application Architecture

Technology Architecture

Planner (Scope)

List of Business Objects

List of Business Processes

List of Business Locations

Owner (Enterprise)

Semantic Model (Model of Enterprise Objects)

Business Process Model

Business Logistics Model (e.g., types of facilities at locations)

Designer (Information Systems)

Logical Data Model

Application Architecture

System Geographic Deployment Architecture

Builder (Technology)

Physical Data Model

Systems Design Technology Architecture

Subcontractor (Detailed Specification)

Data Definition Library

Programs / Supporting System Components

Network Architecture

The JWOD EA/BPR Project

04/08/23 31

The Javits-Wagner-O-Day Program

To create jobs for people with disabilities by providing goods and services to the Federal Government

Implemented by an independent Federal Agency, The Committee For Purchase From People Who Are Blind or Severely Disabled

Two Central Nonprofit Agencies National Industries for the Blind NISH, which supports people who have

other severe disabilities People with disabilities working at

nonprofit agencies around the country

04/08/23 32

JWOD Products and Services

Services Call centers, janitorial, ground

maintenance, ship stocking, base supply centers, etc.

Products Skilcraft pens and other office

supplies, military unique products (e.g., uniforms), hardware, cleaning products, medical supplies (e.g., latex gloves), etc.

Distribution Staples, Office Depot, GSA

Advantage!, jwod.com, base supply centers, direct to Federal Agencies

04/08/23 33

The JWOD EA/BPR Project, from Bottom up --

Needs from an IT Perspective A new, Enterprise-wide IT System Consistent, accessible information to all

organizations

Needs from a Business Process Perspective

Improved business processes, across all organizations

Coordination and cooperation Clarified Roles and Responsibilities

Needs from a Program Perspective Overall Buy-in to Strategic Objectives and

Performance Measures

More

Ch

alle

ng

ing

04/08/23 34

EA Supports the JWOD Modernization

New IT must support Business Processes, which must support Mission Objectives Strategic Planning Documenting Current Architecture Facilitating Development of Improved

Business Processes, Enhancing Cooperation Defining Target Architecture – Across Program

Business Processes, Performance Measures, Service Components / Application Architecture Technical / Infrastructure

Aligning to Federal Enterprise Architecture

04/08/23 35

What makes it hard --

No point in automating processes you don’t need to be doing – Need new strategic plan!

How should program resources be managed? Need organization-wide alignment

Need integration of automation across multiple organizations

Including commercial organizations, nonprofits and government

Entire supply chain? Not the whole Federal Government, TODAY…

04/08/23 36

What makes it possible --

Senior Leadership Buy-in The have an EA Champion New Presidential Appointees People Want to Have Impact Recognition of Benefit of Program-wide Integration

OMB and Presidential Guidance Federal Enterprise Architecture E-Gov Focus

Technology Enablers All players want to upgrade technology Time to get off that client/server Time to break down stovepipes and make services

available over the Web XML and Web Services – for some transactions

Where the FEA is Taking Us – Future Potential

04/08/23 38

Huge Future Potential for Improving Federal Automation over the Long Haul

As Big of an Impact As The Web The Web made Static / Dynamic Information Available to

Users Cataloged, Architected Web Services make Data and

Processes Available to Developers in Other Agencies

More Data / Code / Service Sharing Cost Savings, Not Re-inventing the Wheel More Flexible Boundaries – Federal Agencies, States, Local

Government, Private Industry, … Issues of Data Ownership, Data Quality, Data Privacy and

Security Ownership Issues – Who Maintains Services in Repositories

if Multiple Agencies Use Them?

Sensible IT Investment Decisions

04/08/23 39

The point people miss…!Enterprise Architecture is NOT about building a massive inventory of information about IT systems.

Enterprise Architecture is about ALIGNING systems to support processes that support the MISSION across agencies, and measuring the performance of the organization in achieving the mission.The TARGET Enterprise Architecture includes reorganizing SOME systems into accessible, reusable components.

04/08/23 40

The Guidance is a Moving Target

The Business Reference Model version 2.0 is overdue, but soon!

The Service Component Reference Model version 1.0 is in Draft (out for agency review)

The Technical Reference Model version 1.0 is in Draft (out for agency review)

The Data Reference Model is not out at all but is promised this summer

The FEAMS is not ready yet

The FEAF 2.0 appears to be derailed

04/08/23 41

Challenges in Software Engineering

Increased Focus on Business Objectives and Business Process

Need to optimize process across the enterprise If it is to be shared it has to be generic / common

Engineer for Re-Use / Sharing Need to Select Appropriate Level of Granularity Code Re-Use is Downstream, Component Re-Use Security, Repositories, Rules of Engagement Need to

be Worked Out

Engineering for Interoperability Standards Gaps, Cross-Platform Issues Will Still Need

Working Out

04/08/23 42

References

Federal Enterprise Architecture Program Management Office (FEAPMO) http://www.feapmo.gov

Industry Advisory Council (IAC) Enterprise Architecture SIG www.iaconline.org, http://www.ichnet

.org/IAC_EA.htm

FEA Bibliography (evolving) www.ursamajorconsulting.com

Questions/ Discussion