1. FOUO – Do not distribute
Federal Enterprise Architecture
Office of Management and Budget (OMB)
FEA Artifact Working Group
23 March 2012
Walt Okon
Senior Architect Engineer
Artifact Working Group
, Office
, Cell

2. Office of Management and Budget (OMB) FEA Artifact Working Group
Changes in:
Direction more strategic, mission oriented
Focus administration initiatives, agency priorities
Governance FEAPMO, CAF, AIC, ArchPlus
Approach common approach, FEAv2, DoDAF 2.0
Scope levels of solution architecture, 6 views
Method repeatable 5-step method, 6 core artifacts
Reporting revised reference model set, audit criteria
Use internal improvements, external shared services

3. Office of Management and Budget (OMB) FEA Artifact Working Group
Artifact Working Group Members
Member
Agency
Walt Okon
DoD
Vanessa Trinh
OMB
Tammy (Tamera) Trocki
NRC
Kimberly Ellmore
DHS
Bill Garvin
SSA
Jim Walterman
DOJ
Heather Shappee
IC/NGA
Brett Brunk
GSA
Thomas Milligan
Treasury
Ramana Kasibhotla
FAA
Marco Demartin
HHS
Marlon H. Sellow
SBA
Art Smith
Tracey Hanson
USDA
Lin Zhang
Interior
Gregory Weidman
ODNI
Dave McDaniel

4. Office of Management and Budget (OMB) FEA Artifact Working Group
Mission: Federal enterprise architects provide leading-edge advisement, analysis, and design services that align strategic priorities with mission capabilities and technology solutions
Artifact Scope: 8 levels of solution architecture, 6 views
Task: The task of the Artifacts working group is to map the artifacts of the DoDAF Version 2.02 (Unified Defense Architect Framework) to each domain and to state whether they are Required, Recommended or Optional

5. Office of Management and Budget (OMB) FEA Artifact Working Group
Common Approach Architecture Domains:
Strategy
Business
Data
Applications
Infrastructure
Security

6. Office of Management and Budget (OMB) FEA Artifact Working Group
Sub-Architecture Domains. Each solution produces a tangible capability (e.g., system, network, service) that spans six sub-architectural domains in the overall EA: strategy, business, data, applications, infrastructure, and security. These domains are hierarchical (except security, which is a “thread” or cross cutting concern involving all domains) in that strategic goals drive business activities, which are the source of requirements for services, data flows, and technology enablement. Security controls pervade all of the other domains by providing risk-adjusted control elements in the form of hardware, software, policy, process, and physical solutions.

7. Office of Management and Budget (OMB) FEA Artifact Working Group

8. Office of Management and Budget (OMB) FEA Artifact Working Group

9. Office of Management and Budget (OMB) FEA Artifact Working Group
Define Possible Artifacts:
DoDAF Version 2.02 (Unified Defense Architect Framework)

10. Changes in Approach
Common Approach to Federal EA
FEAF-II

11. Changes in Scope Multiple Agencies Single Agency Level Scope Planning
Detail
Impact
Audience
Multiple
Agencies
Govt.-Wide
Services
U.S. & Other
Governments
Medium
National/Global
Outcomes
Government-Wide
& International
Multiple Agencies,
Businesses,
Interest Groups
Sector
Services
Medium
Sector
Outcomes
Multi
G2C, G2B, G2G
Agency-Wide
Services
Line of Business
Specific Services
Single Agency
Program
Specific
Services

12. Changes in Method Repeatable Process for Solution Architecture.
The standardized process for solution architecture is based on the process originally developed for segments, and can scale “downward” to produce system solutions or work “upward” to support agency-wide views across all lines of business, to develop multi-agency shared services across mission sectors, identify USG-wide services, and to develop national and international solutions.

13. Changes in Reporting
The following FEA reference models would be required for each solution architecture project. Only BRM reported in the Ex 53 (none in Ex 300/400).
Performance Reference Model (PRM) – addition of strategic goal number, retain “line of sight concept” input-output-outcome.
Business Reference Model (BRM) – incorporates old SRM, levels: mission area, function, sub-function, segment.
Data Reference Model (DRM) – minor changes
Application Reference Model (ARM) – new, 3-levels oriented toward software application types and standards.
Infrastructure Reference Model (IRM) – new, 3-level taxonomy oriented toward network/cloud types and standards
Security Reference Model (SRM) – new, 3-level catalog of security controls being used (IAW NIST SP ).
(note: the Technical Reference Model will be replaced by the ARM and IRM,
the Service Reference Model will be merged into the BRM)
Core Artifacts would be:
Strategic Domain: PRM
Business Domain: High-level diagram of all workflows.
Data Domain: High-level logical diagram of all data flows.
Application Domain: High-level application interface diagram.
Infrastructure Domain: High Level network diagram.
Security Domain: High level diagram of logical & physical controls.

14. Shared Services / Cloud Solutions
Changes in Use - Delivery
IT Reform Agenda
Policy
Shared Services Strategy
Cloud Computing Strategy
Shared Service/Cloud Computing Implementation Architecture
Cloud Computing Reference Architecture (NIST)
Approach
Common Approach to Federal EA
FEAF-II / FEAv2
DODAFv2.0
Other EA
Shared Services / Cloud Solutions
IaaS
PaaS
SaaS
Light Apps
Security
Delivery
Data Center Consolidation

15. Environment & Natural Resources
Changes in Use – Shared Services
Sector designations are needed to support new services and interoperability across traditional agency boundaries.
General
Government
Policy
Resources
Oversight
Transparency
Education & Workforce Sector
Defense & Security Sector
Law & Justice
Sector
Diplomacy & Trade
Economic & Financial Sector
Transport
& Space Sector
Energy & Technology
Environment & Natural Resources
Health & Well-Being
Example: Electronic
Patient Records
Example: Border
Protection
Example:
International Legal
Cases
Example: International Trade & Exports
Example: Global
Economic Tracking
Example:
On-line Learning
Example: Energy
Efficient Housing
Smart-Roads
Example: Alternative
Fuels
Central sector for general government
support services and transparency

16. Changes in Use – Shared Services
Workspaces
Requirements Development
Space Delivery
Building Ops & Management
Lease Admin
Real Estate Asset Mgmt
Real Property Disposal
Acquisition
Requirements Definition
Solution Development
Acquisition Planning
Solicitation Writing
Source Selection
Contract Award
Contract Admin
Supply Chain
Order Management
Supplier Management
Inventory Management
Stores Management
Deliveries/ Transportation
Returns
Travel and Transportation
Government-wide Solutions
Vehicle Acquisition
Fleet Mgmt
Transportation Mgmt & Audit
Travel Mgmt
Relocation Services
Freight Mgmt
Citizen Services
Federal IT Solutions
Policy Mgmt
Federal Asset Sales
Financial Management
Financial Planning
Funds Management
Payables Accounting
Receivables Accounting
Asset Accounting
Cost Allocation
Cash Management
General Ledger
Financial Reporting
Human Resources Management
HR Strategy
Organization& Position
Staff Acquisition
Compensation &Performance
Benefits
Training
Labor & Empl Relations
Personal Action
Separation
Information Technology
IT Infrastructure
Data Mgmt
IT Planning
IT Investment Management
IT Policy
IT Security
System Development
System Maintenance
Application Integration

17. Changes in Use – Shared Services
A service has:
- provider
- consumer
- workflow
- data flow
- system(s)
- host/cloud
Cloud services have:
- On-demand self-service
Broad network access
Resource pooling
Broad elasticity
Metering

18. Changes in Use – Shared Services
Identify candidate early adopters in mission and support areas:
Mission Area Support Area
Electronic Patient Records HR LOB
GIS LOB e-Travel
Food Safety Systems Asset Mgmt.
2. Identify viable cost models for a shared service “consortium.”
Direct funding authorization to lead agency
Pass-the-hat among all participating agencies
Hybrid
3. Gain executive and program support through OMB memo, communications
campaign, and training workshops (like the Techstat program).
4. Identify a repeatable method for developing or enhancing a shared service
Based on 5-step segment architecture methodology and
GSA’s 4-Week “Sprint” business service model as an example.

19. Questions?