OMB as a Driver of Transformation

Transcription

DoD Systems and Software Technology Conference (SSTC) 2007
OMB as a Driver of Transformation:
Federal Enterprise Architecture (FEA)
Overview and Implications
Thursday, June 21, 2007
Marilyn T. Gaska, PhD
Program Management Senior Manager
Lockheed Martin Systems Integration
Owego, New York
[email protected]
607-751-2232 (office)
607-759-3011 (mobile)
M.T.Gaska - 1
©Copyright Gaska, 2007
Outline
Office of
Management
and Budget
(OMB)
Context
OMB FEA/
CIO Council
Transformation
Drivers
President’s
Management
Agenda
FEA Benefits
and
Implications
Specific
Government
Contract
Frameworks and
Systems/Software
Impacts
Transformation
Example
from Logistics
Domain
Leveraging FEA/SOA for Business Case to Drive
Transformation Opportunities in DoD
Way Forward
M.T.Gaska - 2
Executive Office of the President Office
of Management and Budget (OMB)
Karen Evans,
Office of
e-Gov and IT
With FEA PMO
http://www.whitehouse.gov/omb/omb_org_chart.pdf
M.T.Gaska - 3
President’s Management Agenda Scorecard
Focus on Improving Government Management
• Quarterly Scorecards on Line at:
http://www.whitehouse.gov/results/agenda/scorecard.html
• E-Gov and Budget/Performance Integration are 2
Areas
• Subset for March 31, 2007
M.T.Gaska - 4
Federal CIO Council
“Originally Established by Executive Order 13011 (Federal
Information Technology) and Later Codified by the Egovernment Act of 2002, the Chief Information Officers
Council (the CIO Council) is the Principal Interagency
Forum to Improve Agency Practices for the Management
of Information Technology.
The CIO Council is One Element of an Interagency Support
Structure Established to Achieve Information Resource
Management (IRM) Objectives Delineated in Legislation
Including the E-government Act of 2002 (Public Law 107-347),
Government Paperwork Elimination Act (GPEA), Paperwork
Reduction Act (PRA), Government Performance and Results
Act (GPRA), and the Information Technology Management
Reform Act of 1996 (ITMRA).”
http://www.whitehouse.gov/omb/egov/d-1-cio.html
M.T.Gaska - 5
FEA Program Management Office
Enabling Citizen-centered Electronic Government
2005 - 2006 FEA PMO Action Plan
“The FEA Program Management
Office (FEA PMO), Located in OMB’s
Office of E-gov and IT, Equips OMB
and Federal Agencies with a Common
Language and Framework to Describe
and Analyze IT Investments, Enhance
Collaboration and Ultimately
Transform the Federal Government
into a Citizen-centered, Resultsoriented, and Market-based
Organization as Set Forth in the
President’s Management Agenda
(PMA).”
http://www.whitehouse.gov/omb/egov/documents/2005_FEA_PMO_Action_Plan_FINAL.pdf
M.T.Gaska - 6
FEA Roadmap to Government Transformation
2005-2006 Federal Enterprise Architecture Action Plan, p. 5
http://www.whitehouse.gov/omb/egov/documents/2005_FEA_PMO_Action_Plan_FINAL.pdf
M.T.Gaska - 7
What is FEA?
“The FEA consists of a set of interrelated
“reference models” designed to facilitate crossagency analysis and the identification of
duplicative investments, gaps and opportunities
for collaboration within and across agencies.
Collectively, the reference models comprise a
framework for describing important elements of
the FEA in a common and consistent way.
Through the use of this common framework and
vocabulary, IT portfolios can be better managed
and leveraged across the federal government.”
FEA Consolidated Reference Model Document Version 2.1
http://www.whitehouse.gov/omb/egov/documents/FEA_CRM_v21_Final_Dec_2006.pdf
M.T.Gaska - 8
Federal Enterprise Architecture Principles
• The Federal Government is:
– Citizen - Centered
– Results - Oriented
– Market - Based
– A Single, Federated Enterprise
– Operates Collaboratively
• The Federal Architecture is Business - Driven
• Flexibility and Agility are Design Standards
• Information is an Enterprise Asset
• Security and Privacy are Design Standards
Dick Burk, Dec. 1, 2005 Conference Presentation (p. 21)
http://www.whitehouse.gov/omb/egov/documents/2005_IT_EA_in_Govt.pdf
FEA Mission: Develop and Use the FEA to Improve
Government Efficiency and Effectiveness
M.T.Gaska - 9
Enterprise Architecture Guidance
Dick Burk, Dec. 1, 2005 Conference Presentation
http://www.whitehouse.gov/omb/egov/documents/2005_IT_EA_in_Govt.pdfM.T.Gaska - 10
FEA Reference Model Overview
http://en.wikipedia.org/wiki/Federal_Enterprise_Architecture
M.T.Gaska - 11
Model Structures/Terminology
Framework for Performance Measurement
Providing Common Output Measurements
Throughout the Federal Government.
Business-driven, Functional Framework
Classifying Service Components According
to How they Support Business and
Performance Objectives.
Tiered Hierarchy Representing the
Business Functions of the Federal
Government.
Component-driven, Technical Framework
Categorizing the Standards & Technologies to
Support and Enable the Delivery of Service
Components & Capabilities.
M.T.Gaska - 12
Information Sharing Implications
Data Reference Model
The DRM is a Flexible
and Standards-based
Framework to Enable
Information Sharing
and Reuse Across the
Federal Government via
the Standard Description
and Discovery of
Common Data and the
Promotion of Uniform
Data Management
Practices.
Detail at http://www.whitehouse.gov/omb/egov/documents/DRM_2_0_Final.pdf
M.T.Gaska - 13
Performance Management Implications
M.T.Gaska - 14
Business Reference Model
M.T.Gaska - 15
Service Reference Model
M.T.Gaska - 16
Technical Reference Model
M.T.Gaska - 17
OMB Budgetary Approval Process Requires
Enterprise Architecture Planning
• “An Agency Submitting Investments to OMB for Budgetary
Approval Must Indicate in Exhibit 300s that the Investments Help
Meet Agency Goals and Further its Mission. Enterprise Architecture
is a Representation of These Goals, and Consequently, Any
Investment Must be Consistent With the Target EA and the EA
Transition Strategy. This Consistency is Shown by Mapping
Investments to the FEA Reference Models.”
–
http://www.whitehouse.gov/omb/egov/a-2-EABudget.html
• Focus is IT and Major Capital Investment Justification
–
–
–
Capital Assets = Land, Structures, Equipment, Intellectual Property (e.g., Software),
and Information Technology (Including IT Service Contracts) Used by the Federal
Government and Having an Estimated Useful Life of Two Years or More. See
Appendix One of the Capital Programming Guide for a More Complete Definition of
Capital Assets.
http://www.whitehouse.gov/omb/circulars/a11/current_year/s300.pdf
http://www.whitehouse.gov/omb/egov/documents/FY08_IT_Budget_Rollout.pdf
M.T.Gaska - 18
FEA Budget Allocation Implications
SEC. 5122. CAPITAL
PLANNING AND
INVESTMENT
CONTROL.
the Value and Assessing
and Managing the Risks
of the Information
Implement in the Agency
a Process for Maximizing
Technology Acquisitions
W. Kennedy, 2005
Define Technical
Alternatives
-- Status Quo
-- Process/Organization
Projects
-- Security projects
Telecommunications
-- Technical/System/IT
Agency
Guidance
OMB A-11 and A-130
Clinger-Cohen Act:
IT Investments are to be Defined, Selected,
and Managed on the Basis of a Well-founded
Business Case
Business Line
and IS Inputs
Strategic Plan
Benefit/Cost
Assessment
-- $ Benefits and
Costs
-- Business
Benefits
-- CFO/Budget
Spreadsheet
-- Risks
CCA and FASA
Enterprise Architecture
Modernization Plan
Define Strategic Business
Needs/Value Capture
-- Derived from Strategic Plan
Performance Metrics and/or
Cost Savings
-- Enterprise Architecture
Define Customer Needs
Define Critical Success
Factors
Gap analysis (Process,
Organization, IT Capability)
Risk ID, Assessment,
and Define
Management Plan
Define Acquisition and
Program Management
Plans
Business
Case
(OMB A-11
IT Investment
Guidance
Refine
Selected
Alternative
300)
http://www.whitehouse.gov/omb/egov/e-5-documents.html
FEA Experience, Discipline, and Tools are Needed
M.T.Gaska - 19
Budget/Performance Integration Implications:
EA Assessment CONOPS
Annual Assessments and Quarterly Progress
http://www.whitehouse.gov/omb/egov/a-2-EAAssessment.html
M.T.Gaska - 20
Federal Transition Framework (FTF)
The Federal Transition Framework (FTF) is a Catalog of Cross-agency
Information Technology (IT) Initiatives. It is a Single Information Source for
Government-wide IT Policy Objectives and Cross-agency Initiatives
Including:
• OMB-sponsored Initiatives, e.g., E-Gov Initiatives, LOB Initiatives
• Government-wide Initiatives, e.g., Internet Protocol Version 6 (IPV6),
Homeland Security Presidential Directive 12 (HSPD 12).
http://www.whitehouse.gov/omb/egov/a-2-EAFTF.html
http://www.whitehouse.gov/omb/egov/documents/FTF_Usage_Guide_Pilot_Final_Dec_2006.pdf
M.T.Gaska - 21
FEA and Service Oriented Architecture (SOA)
Commercial Industry Basis
• Building a Service Oriented Architecture With Business Process Management
(BPM) and Model Driven Architecture (MDA): (OMG, Oct. 2006)
– Recognizing that its Business Processes Extend Out to its Customers and Suppliers, the
IT-enabled Enterprise Needs a Networking Environment that Supports Design,
Development, Deployment, and Maintenance of Systems that Extend Business
Automation Far Beyond the Firewall. Today's State-of-the-art Infrastructure Couples
Web Services (WS) Loosely into a Service-Oriented Architecture (SOA), Designed and
Built With an Eye to Business Processes With the Assistance of OMG's Model Driven
Architecture (MDA), Since Model-driven Development is a Necessity for Systems this
Large and Complex. Early Adopters have WS/SOA Systems in Place Already; Mainline
Enterprises are in Various Stages of Investigation and Prototyping as Vendors Move up
from WS-development Tools to WS-management Tools.
http://www.omg.org/news/meetings/soa-bpm-mda/index.htm
• Dick Burk, Chief Architect, e-Gov and IT OMB
– Service-Oriented Architecture While at HUD
M.T.Gaska - 22
Cross-Agency Collaboration Implications:
Line of Businesses (LOB)
Case Management (CM)
Financial Management (FM)
Grants Management (GM)
Human Resources Management (HR)
Federal Health Architecture (FHA)
IT Security (ITS)
Budget Formulation and Evaluation (BFE)
Geospatial LoB
IT Infrastructure (IOI)
http://www.whitehouse.gov/omb/egov/c-presidential.html
First Five LOBs in 2004 Expanded to 9 in 2006
M.T.Gaska - 23
Component-Based Architectures Implications
M.T.Gaska - 24
Alliant Alignment with FEA/DoDEA
•To Provide a Common Language to Describe IT Requirements
•To Facilitate the Evolution of Alliant and Alliant SB Over Their Entire
Lifecycle
•To Assist Customers in Defining Their IT Investments in the Same
Context as Their OMB Submissions
GWAC Vehicle Details at http://www.gsa.gov/alliant
Agency Requirement
OMB Exhibit 300
Project Mgmt
BRM/PRM
Alliant Task Order
Management
Alliant
SOW
Financial
Application
Equipment
SRM
TRM
Application
Infrastructure
Sections
Parallel
FEA
Example: Agency Requirement: New Web-based Financial System
M.T.Gaska - 25
Line of Business Opportunities
OMB and the LoB Task Forces are Focused on Business-driven,
Common Solutions Developed Through Architectural Processes.
The Following LoBs
Undertaken in FY 2006:
• Budget Formulation
and Execution
• IT Infrastructure
Optimization
• Geospatial
Common Solutions: A Business Process
and/or Technology Based Shared Service Made
Available to Government Agencies.
Business Driven (vs. Technology Driven):
Solutions Address Distinct Business
Improvements that Directly Impact LoB
Performance Goals.
Developed Through Architectural
Processes: Solutions are Developed Through a
Set of Common and Repeatable Processes and
Tools.
M.T.Gaska - 26
DISA ENCORE II and NCES
• “The Defense Information Systems Agency (DISA) Supports the Department
of Defense (DoD), Joint Chiefs of Staff, Commanders, and the President in
Times of Peace and War. DISA is Responsible for Maintaining and Improving
the Effectiveness of the Global Information Grid (GIG), a Technological
Foundation of the United States Military. In 2002, DISA Created the NetCentric Enterprise Services (NCES) Program to Provide a Robust Servicesbased Infrastructure for GIG that Enables the Integration and Delivery of Realtime and Near-real-time, Decision-quality Information to its Communities of
Interest (COI). At its Essence, NCES is a Service-Oriented Architecture
(SOA) Foundation for Connecting all DoD Information Systems, Both Those
that are Owned by the DoD and those Owned by its Contractors and Related
Agencies.”
http://www.amberpoint.com/customers/studies_disa.shtml
DISA Encore II Engineering Support Will Provide Assistance in
Utilizing the NCES Capabilities Via the Four Product Lines
https://www.ditco.disa.mil/dcop/public/asp/requirement.asp?req_no=HC1013-05-R-2003
M.T.Gaska - 27
DISA Net-Centric Enterprise Services
(NCES) Program Overview
http://www.disa.mil/nces/about_nces/overview_content.html
M.T.Gaska - 28
DoD Business Transportation Agency
The Transformation Planning and Performance (TPP) Facilitates
Maximum Resource Utilization and Increased Performance Within
the Business Transformation Agency’s Time, Cost and
Performance Constraints. TPP Provides Matrix Support to All
Agency Processes and Product Development of Designated
Deliverables, Including the Business Enterprise Architecture
(BEA) and the Enterprise Transition Plan (ETP). (See
http://www.dod.mil/bta/ and http://www.defenselink.mil/bta/products/etp.html)
M.T.Gaska - 29
Transformation Examples: Logistics
Federal Agencies and
Budgeting Systems
Combat Service
Support Systems
Performance Based
Logistics (PBL) Contracts
& Performance
Driven Outcomes
FEA Services
Global Information Grid
And NCES Services
Commercial Service Oriented
Architecture Implementation
Common Technical Reference Model Standards for Interoperability of Services
Interoperability Between Government and Industry
in Logistics Domain Offers Opportunities
for Collaboration and Interoperability
M.T.Gaska - 30
Suggested Way Forward:
Government / Industry Collaboration
• Leverage Government / Industry Partnerships to Leverage
FEA, Emerging LOBs, and Next-generation 10-year ID/IQ
Vehicles to Implement Transformational Initiatives
• Participate in Industry/Government Groups Shaping the
Future, leveraging Cooperative Research and
Development Agreements (CRADAs)
• Align Systems and Software Technologies for Reuse
Consistent with FEA, NCES and SOA Concepts
• Coordinate Transformation Roadmaps and Business Cases
Be a Leader vs. Compliance Focused!
M.T.Gaska - 31
Key Acronyms
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
BRM – Business Reference Model
CIO – Chief Information Officer
CRADA – Cooperative Research and Development Agreement
DISA – Defense Information Systems Agency
DRM – Data Reference Model
DoDEA – Department of Defense Enterprise Architecture
ETP – Enterprise Transition Plan
GIG – Global Information Grid
FEA – Federal Enterprise Architecture
LOB – Line of Business
NCES – Network Centric Enterprise Services
OMB – Office of Management and Budget
PBL – Performance Based Logistics
PDO – Performance Driven Outcomes
PRM – Performance Reference Model
SOA – Service Oriented Architecture
SRM – Service Reference Model
TPP – Transformation Planning Performance
TRM – Technical Reference Model
M.T.Gaska - 32

OMB as a Driver of Transformation

Transcription

Similar documents

Facility Management Technology.indd

Charles A. Harris Senior Software Engineer The Boeing Company

HOW IT WORKS:

Flat epithelial Atypia

The DoD Civilian Workforce - American Society of Military

9th DoD/VA and Gov Health IT Post Summit Report

First 100 days of the new OMB Chairman

ALUMNI TRUCKER LINE - Norwalk City School District