Overview of the Federal Enterprise Architecture

Transcription

1 Overview of the Federal Enterprise Architecture Presented by Craig Miller Director of Enterprise Planning Solutions 8618 Westwood Center Drive Suite 310 Vienna, Virginia Ph: (703) Fax: (703)

2 Agenda Introducing the Federal Enterprise Architecture The FEA Reference Models Business Performance Technical Service Component Data and Information Applying the FEA FEA or FEAF? Benefits Limitations 2

3 Introducing the Federal Enterprise Architecture The Federal Enterprise Architecture to develop an enterprise architecture framework for federal agencies The FEA is the responsibility of the Office of Management and Budget with input from the federal CIO Council OMB statement: The FEA is a tool that enables the Federal Government to identify opportunities to leverage technology and alleviate redundancy, or to highlight where agency overlap limits the value of IT investments It is a framework designed to help agencies identify opportunities for business improvement via standardization, interoperability, consolidation, data sharing All major agency IT investments are required to document how they align to the FEA (OMB Exhibit 300) 3

4 FEA Reference Models Overview The FEA consists of five related reference models that describe enterprise domains that may benefit from standardized taxonomies to facilitate improvements to business processes 4

5 The Business Reference Model (BRM) The BRM is considered to be the foundation of the FEA Provides a standardized taxonomy of business services Business areas Lines of business Business sub-functions Goal: promote crossagency collaboration Related FEA initiatives underway to describe business processes in detail for specific domains (healthcare, finance, etc.) 5

6 The Performance Reference Model (PRM) The PRM exists to provide a line of sight between IT investments and the agency programs they support PRM defines generic performance measurement areas, categories and indicators Up to agencies to define specific performance goals and metrics 6

7 The Service Component Reference Model (SRM) The SRM is based on the idea of service components that link IT services to business processes SRM provides the linkage between the business and technical views of the enterprise architecture Service components represent opportunities for organizational reuse 7

8 The Technical Reference Model (TRM) The TRM provides a standardized taxonomy for services, specifications and technologies It does NOT dictate which specs/standards should be adopted by an agency 8

9 The Data and Information Reference Model (DRM) The DRM provides a standardized taxonomy of data classifications that can be used to identify opportunities for data sharing and exchange FEA PMO will provide common data subject areas Agencies / communities of practice will define information exchange packages and data objects DRM is incomplete and currently in draft form only Data concept taxonomy defined No standardized descriptions of data areas or subject types yet 9

10 FEA or FEAF? The Federal Enterprise Architecture Framework was a previous initiative to provide a standardized govt. EA framework More ambitious scope than FEA Less detail (no standardized taxonomies) More emphasis on the process of developing an EA (baseline and target architectures, sequencing plans) The two frameworks may be harmonized by OMB/ CIO Council in the future 10

11 FEA Benefits FEA takes an important step to defining standardized taxonomies for several important facets of an enterprise architecture Ongoing initiative that is expanding into additional EA areas: Security profile Detailed EA drilldowns through specific sectors Documenting FEA alignment a prerequisite for funding major federal IT initiatives Adoption likely to spread beyond federal agencies (e.g. states, perhaps private sector) Some tool support in progress 11

12 FEA Limitations High-level and generic Designed to apply across all agencies In most cases you must define more concrete elements that are specific to your organization s needs NOT a complete enterprise architecture framework Does not address important aspects of strategy, stakeholders, business activities, infrastructure, workforce, facilities, etc. NOT a process for developing an enterprise architecture Does not describe how to differentiate between baseline and target architecture development Does not describe how to develop a transition plan Does not describe best practices for EA 12

13 For More Information FEA Program Management Office site: Reference models Latest news and developments OMB Guidance Chief Information Officers Council site: Architecture Guidance on applying EA Older FEAF materials Blueprint Technologies: Best Practices in Enterprise Architecture whitepaper 13

14 Questions? Thank you! 14