Federal Enterprise Architecture Framework version 2 (January 29, 2013) (PDF, 9.3 MB) FEA Reference Models Business Reference Model version 3.1 (May 15, 2013) (PDF, 0.2 MB) The combined volumes of the DRM support data classification and enable horizontal and vertical information sharing. The DRM is a framework whose primary purpose is 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. The five reference models in version 1 (see below) have been regrouped and expanded into six in the FEAF-II. Related organizations (backlinks) Duplicated by (backlinks) Related standards/methodologies (backlinks) Provides external content. Federal Enterprise Architecture E-Gov Program Management Office, 8th floor; 1800 G Street, N.W. FEA PMO is the abbreviation for Federal Enterprise Architecture Program Management Office The Data Reference Model (DRM) is one of the five reference models of the Federal Enterprise Architecture (FEA). Appoints the Enterprise Architecture Director, who also serves as the DHS Chief Architect; 3. In 2001, the Federal Architecture Working Group (FAWG) was sponsoring the development of Enterprise Architecture products for trade and grant Federal architecture segments. Help produce enhanced performance information to improve strategic and daily decision-making; Improve the alignment — and better articulate the contribution of — inputs to outputs and outcomes, thereby creating a clear "line of sight" to desired results; Identify performance improvement opportunities that span traditional organizational structures and boundaries. The U.S. Federal Enterprise Architecture (FEA) is an initiative of the U.S. Office of Management and Budget (OMB), Office of E-Government and IT, that aims to realize the value of enterprise architecture within the U.S. Federal … It provides guidance in describing architectures for multi-organizational functional segments of the Federal Government. is of one five Federal Enterprise Architecture (FEA) interlinked models and complies with FEA guidelines published by the Office of Management and Budget. The primary stakeholders for solution architecture are system users and developers. The PRM is a standardized framework to measure the performance of major IT investments and their contribution to program performance. This document: The DRM is the starting point from which data architects should develop modeling standards and concepts. Agencies and the federal government will benefit from economies of scale by identifying and reusing the best solutions and technologies to support their business functions, mission, and target architecture. As part of the President's Management Agenda, in August 2001, the E-Government Task Force project was initiated (unofficially called Project Quicksilver). The Common Approach promotes increased levels of mission effectiveness by standardizing the development and use of architectures within and between Federal Agencies. 13 For additional information on OMB's and the CIO Council's views on service components, see: (1) Federal Enterprise Architecture - Program Management Office, Federal Enterprise Architecture Service Component Reference Model Release Document, Version 1.0. Although NIST guidance on risk management refers to enterprise architecture (EA) in the context of mission and business process perspectives on risk [59], enterprise architecture is a core information resources management program in most federal … The Office of Information Technology (OIT), Architecture and Engineering Service (AES) published its VA EA Fourth Quarter FY20 Release on October 23, 2020. NIST SP 800-53 Rev. [1], While the BRM does provide an improved way of thinking about government operations, it is only a model; its true utility can only be realized when it is effectively used. EA is driven by strategy; it helps an agency identify whether its resources are properly aligned to the agency mission and strategic goals and objectives. The U.S. Department of Labor's (DOL) Office of Chief Information Officer (OCIO) Strategic Business Management (SBM) Program focuses on improving and enhancing the alignment between business and technology across the Department to improve program performance. Through its data collection and reporting capabilities, the EAR enables organizations to better identify collaboration, modernization and transformation opportunities. Federal Enterprise Architecture Program Management Office 1. Business Reference Model version 3.1 (May 15, 2013)(.PDF, 0.2 mb) Appoints the Enterprise Architecture Director, who also serves as the DHS Chief Architect; 3. The scope of a solution architecture is typically limited to a single project and is used to implement all or part of a system or business solution. The purpose of this document is to provide guidance to Federal Agencies in initiating, developing, using, and maintaining an enterprise architecture (EA). Collectively, the reference models comprise a framework for describing important elements of federal agency operations in a common and consistent way. The FEA is built using an assortment of reference models that develop a common taxonomy for describing IT resources. The Office of the Chief Management Officer (CMO) annually produces the Business Enterprise Architecture (BEA) to help defense business system owners and program managers make informed decisions. Just as enterprises are themselves hierarchically organized, so are the different views provided by each type of architecture. Federal Enterprise Architecture Program Management Office Author: Norman Lorentz, Office of Information and Regulatory Affairs Keywords: Federal Enterprise Architecture Program Management Office Created Date: 20030106143743Z The FEAF overall framework created at that time (see image) includes the first three columns of the Zachman Framework and the Spewak's Enterprise Architecture Planning methodology.[3]. The Common Approach to Federal Enterprise Architecture (May 2, 2012) (PDF, 1.9 mb) Federal Enterprise Architecture Framework version 2 (January 29, 2013) (.PDF, 9.3 mb) FEA Reference Models. The Task Force recommended the creation a Federal Enterprise Architecture Project and the creation of the FEA Office at OMB. structure: segment architecture inherits the framework used by the EA, although it may be extended and specialized to meet the specific needs of a core mission area or common or shared service. To transform the Federal government to one that is citizen-centered, results-oriented, and market-based, the Office of Management and Budget (OMB) is developing the Federal Enterprise Architecture (FEA), a business-based framework for government-wide improvement. Federal Enterprise Architecture Program Management Office listed as FEAPMO Federal Enterprise Architecture Program Management Office listed as FEAPMO According to the Office of Management and Budget (OMB) Federal Enterprise Architecture (FEA) Practice Guidance, segment architecture is a “detailed results-oriented architecture (baseline and target) and a transition strategy for a portion or segment of the enterprise.” Federal Enterprise Architecture Program Management Office (FEAPMO) [George W. Bush Administration White House Archives] Show summary Open resource [html] ( open full abstract ) The FEAPMO is a … Federal Enterprise Architecture Program Management Office (FEAPMO) [organisation] Submitted on 27 October, 2009 - 05:22. At a minimum, these processes shall ensure that the CIO certifies that IT resources are adequately implementing … … Federal Enterprise Architecture (FEA) Got questions? This is historical material “frozen in time”. By describing the federal government around common business areas instead of by a stovepiped, agency-by-agency view, the BRM promotes agency collaboration and serves as the underlying foundation for the FEA and E-Gov strategies. The PRM is currently composed of four measurement areas: The "FEA business reference model" is a function-driven framework for describing the business operations of the Federal Government independent of the agencies that perform them. Web elements are based on database resources, and Notice Management … ... FEA-Program Management Office … Enterprise Architecture Example - Web and EJB Operations The following enterprise architecture example shows the general operation process of Web and EJB elements. The Department of Energy (DOE) Enterprise Information Architecture Program helps ensure compliance with OMB A-130 and the Clinger-Cohen Act by promoting standard architectural practices, providing a framework for corporate systems modernization, and establishing an information architecture vision aligned with the Department's strategic goals. Administrator, Office of Infonnat~n and Regulatory Affairs SUBJECT: Applying FITARA Common Baseline to Statistical Agencies and Units Introduction OMB Memorandum M-15-14. Federal Enterprise Architecture Program Management Office (FEAMO) IT Performance Reference Model (PRM) v1.0. Federal Enterprise Architecture Program Management Office April 2003 Draft Performance Reference Model: Overview for Federal Agencies Slideshare uses cookies to improve … Method—s prescribed way of approaching a particular problem. The FEA Program Management Office (PMO), located within 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, … Send email to fea@omb.eop.gov Guidance. As the Program Offices maintain architectures for the business functions under their purview, the EA Team collects, validates, and integrates those architectures into EPA’s overarching Enterprise Architecture. guidance based on business-driven, results-oriented architecture. Preface. These federal architectural segments collectively constitute the federal enterprise architecture. Washington, District of Columbia, 20502 This page was last edited on 10 September 2020, at 15:00. The latest version of the BEA, released by the DCMO, dated March 31, 2017, is BEA 11.0. support the secure delivery, exchange, and construction of business and application Service Components that may be used and leveraged in a component-based or service-oriented architecture. An enterprise architecture (EA) establishes the Agency-wide roadmap to achieve an … This includes principles for using EA to help agencies eliminate waste and duplication, increase shared services, close performance gaps, and promote engagement among government, industry, and citizens. By contrast, "segment architecture" defines a simple roadmap for a core mission area, business service, or enterprise service. Federal Enterprise Architecture Program Management Office, Office of Management and Budget Using the FEA Throughout the Budget Process: Summary and Requirements The Federal Enterprise Architecture Framework (FEAF) was established in 1999 by the Chief Information Officers (CIO) in response to the Clinger-Cohen Act of 1996. It is Federal Enterprise Architecture Program Management Office. It provides a common approach for the integration of strategic, business and technology management as part of organization design and performance improvement.[1]. FEA has a process for creating an enterprise architecture using the Federal Enterprise Architectural Best Practices. Enterprise Architecture became a recognized strategic and management best practice in U.S. Federal Government with the passage of the Clinger-Cohen Act in 1996. [5] The document meets the criteria set forth by Common Approach, emphasizing that strategic goals drive business services, which in turn provide the requirements for enabling technologies. It also contributes to achieving the Secretary of Labor's outcome goals. The Consolidated Reference Model of the Federal Enterprise Architecture Framework (FEAF) equips OMB and Federal agencies with a common language and framework to describe and analyze investments. In addition, the PRM was informed by what agencies are currently measuring through PART assessments, GPRA, enterprise architecture, and Capital Planning and Investment Control. Equally, a solution may be constrained to specific technologies and standards that are defined at the enterprise level.[2]. For example, the three Service Types associated with the Customer Services Domain are: Customer Preferences; Customer Relationship Management; and Customer Initiated Assistance. EAD provides and maintains for USDA a centralized Enterprise Architecture Repository (EAR) that aligns IT assets to the Federal Enterprise Architecture reference models. The TRM is a component-driven, technical framework categorizing the standards and technologies to support and enable the delivery of Service Components and capabilities. This guide offers an end-to-end process to initiate, implement, and sustain an EA program, and describes the necessary roles and associated responsibilities for a successful EA program. An enterprise architecture (EA) establishes the Agency-wide roadmap to achieve an Agency™s mission through optimal performance of its core business processes within an efficient … The BRM is the first layer of the Federal Enterprise Architecture and it is the main viewpoint for the analysis of data, service components and technology. What does FEA PMO stand for? Read More → Business Architecture . Aligning agency capital investments to the TRM leverages a common, standardized vocabulary, allowing interagency discovery, collaboration, and interoperability. Business Enterprise Architecture Business Process Reengineering Defense Business Council and Investment Management Deputy's Management Action Group Continuous Process Improvement DoD Conference Policies and Controls. Interim releases since that time have provided successive increases in definition for the core reference models (see below), as well as a very robust methodology for actually developing an architecture in a series of templates forming the Federal Segment Architecture Methodology (FSAM) and its next generation replacement, the Collaborative Planning Methodology (CPM), which was designed to be more flexible, more widely applicable, and more inclusive of the larger set of planning disciplines. Wikipedia quotes. enterprise architecture, and project management and reporting for IT resources. 1. Establishing a Records Management (RM) Profile in the Federal Enterprise Architecture (FEA) provides the framework for embedding common and consistent records management procedures and … Federal Enterprise Architecture Framework is an enterprise architecture process methodology for the Federal Government of United States of America. A key finding in that strategy was that the substantial overlap and redundant agency systems constrained the ability to achieve the Bush Administration strategy of making the government "citizen centered". From an investment perspective, segment architecture drives decisions for a business case or group of business cases supporting a core mission area or common or shared service. For example, the four components within the Customer Preferences Service Type include: Personalization; Subscriptions; Alerts and Notifications; and Profile Management.[7]. It also unifies existing agency TRMs and E-Gov guidance by providing a foundation to advance the reuse and standardization of technology and Service Components from a government-wide perspective.[1]. Volume One of the DRM provides a high-level overview of the structure, usage, and data-identification constructs. Overall the Federal Enterprise Architecture (FEA) is mandated by a series of federal laws and mandates. Instead, architects need to look beyond the scores to understand EA's contribution to business value. The FICAM Architecture is a framework for an agency to use in ICAM program and solution roadmap planning. Stanley Gaver, a participant of the FEA program, reports that "Enterprise Architecture within the federal government hasn't been working, and far more often than not hasn't delivered useful results. This business reference model provides an organized, hierarchical construct for describing the day-to-day business operations of the Federal government using a functionally driven approach. Through the use of the FEAF and its vocabulary, IT portfolios can be better managed and leveraged across the federal government, enhancing collaboration and ultimately transforming the Federal government. Continue coordination with Federal agency participants in order to ultimately acquire one or more records management services components for inclusion in the Federal Enterprise Architecture (FEA) component repository; and to Provides an introduction and high-level overview of the contents that will be detailed in Volumes 2–4 of the model; Provides the basic concepts, strategy, and structure to be used in future development. This lemma will focus on this particular enterprise architecture and enterprise architecture framework. Consequently, the primary stakeholders of the EA are the senior managers and executives tasked with ensuring the agency fulfills its mission as effectively and efficiently as possible.[2]. In September 1999, the Federal CIO Council published the "Federal Enterprise Architecture Framework" (FEAF) Version 1.1 for developing an Enterprise Architecture (EA) within any Federal Agency for a system that transcends multiple inter-agency boundaries. A business-based framework for Governmentwide improvement developed by the OMB to facilitate efforts to transform the Federal Government to one that is citizen-centered, results-oriented, and market-based. Federal Information Security Management Act, Learn how and when to remove this template message, Department of Defense Architecture Framework, Treasury Enterprise Architecture Framework, FEA Consolidated Reference Model Document Version 2.3, "Common Approach to Federal Enterprise Architecture", Federal Enterprise Architecture Framework version 2, "2015–2016 Baldrige Excellence Framework", FEA Records Management Profile, Version 1.0, "Why Doesn’t the Federal Enterprise Architecture Work? The Government Accountability Office has released a major update of a management maturity framework that provides a flexible benchmark against which federal agencies can plan for and measure enterprise architecture program maturity. Federal Chief Enterprise Architect Executive Office of the President Office of Management and Budget Federal Enterprise Architecture Using EA to Design Future-Ready Agencies and Implement Shared Services . A series of management tools may be involved such as Log and Notice management. These federal laws have been: The Collaborative Planning Methodology (CPM) is a simple, repeatable process that consists of integrated, multi-disciplinary analysis that results in recommendations formed in collaboration with leaders, stakeholders, planners, and implementers. Moreover, significant parts of the federal EA program have been complete and utter failures". On January 29, 2013, the White House released Version 2 of the Federal Enterprise Architecture Framework (FEAF-II), to government agencies, making it public about a year later. iii February 2001. Enter the enterprise-level, or strategic, project management office (PMO). In this Perspective document, Research Director Mike Rollings examines various ways to measure EA success. A federal enterprise architecture framework (FEAF) is the U.S. reference enterprise architecture of a federal government. Establishes the DHS Enterprise Architecture Program Management Office (EAPMO); 2. Federal Enterprise Architecture (FEA) Got questions? The functional approach promoted by the BRM will do little to help accomplish the goals of E-Government if it is not incorporated into EA business architectures and the management processes of all Federal agencies and OMB.[1]. What's New. It is an initiative of the US Office of Management and Budget that aims to comply with the Clinger-Cohen Act. Solution architecture is commonly related to segment architecture and enterprise architecture through definitions and constraints. Federal Enterprise Architecture Program Management Office (2007). Web elements are based on database resources, and Notice Management is close to multiple database sets. The Federal … The official report to the U.S. Congress in 2011 reported that "most departments and agencies reported they expect to realize the benefits from their respective enterprise architecture programs [...] sometime in the future. A federal enterprise architecture is a work in progress to achieve these goals.[2]. [1] The DRM categorizes government information into greater levels of detail. From an investment perspective, EA is used to drive decisions about the IT investment portfolio as a whole. The website is no longer updated and links to external websites and some internal pages may not work. The U.S. Federal Enterprise Architecture (FEA) is an initiative of the U.S. Office of Management and Budget, Office of E-Government and IT, that aims to realize the value of enterprise architecture within the U.S. Federal Government. The FICAM Architecture focuses on enterprise identity processes, practices, policies and information security disciplines. Results of the Federal Enterprise Architecture program are considered unsatisfactory: Reference enterprise architecture of a federal government. The Government of Canada’s Information Technology Strategic Plan sets out the four-year strategic direction for information technology (IT) in the federal government. Management and Oversight of Federal Information Technologv (June 10, 2015), requires Chief Financial Officer (CFO) Act agencies to implement the Federal lnfonnation Since its publication, the BRM has become the seminal document in Federal HR, and it continues to be used on a widespread basis across the government as the framework for the Federal HR community to manage ongoing and new initiatives. Organized in a hierarchy, the TRM categorizes the standards and technologies that collectively [3] At the time of release, the Government's IT focus on Y2K issues and then the events of September 2001 diverted attention from EA implementation, though its practice in advance and subsequent to this may have ameliorated the impact of these events. The Service Component Reference Model (SRM) is a business and performance-driven, functional framework that classifies Service Components with respect to how they support business and/or performance objectives. To develop a useful enterprise architecture (EA) it is important to first understand the questions you want to answer with your architecture. The Performance Reference Model v1.0; Software Acquisition CMM; Software Capability … CDT has a role as a strategic planner and architect for the State’s information technology programs and as a leader in formulating and advancing a vision for that program. Federal Enterprise Architecture Program Management Office April 2003 Draft Performance Reference Model: Overview for Federal Agencies Slideshare uses cookies to improve functionality and performance, and to provide you with relevant advertising. Send email to fea@omb.eop.gov Guidance. The DRM describes artifacts which can be … And each Service Type is decomposed further into components. Enterprise Architects and Solutions Architects work collaboratively with business and technical subject-matter experts from throughout the Department and other agencies to guide the development of information technology Blueprints, which represent segments within the HUD Enterprise Architecture v4.0. Investments to the TRM leverages a common and consistent way provides an enduring standard developing. ( backlinks ) provides external content ways to measure the performance of major it investments and contribution. Version 1 ( see below ) have been regrouped and expanded into in. Task Force recommended the creation of the BEA, released by the DCMO, March. At 15:00 your architecture latest version of the Federal government latest version of the DRM support data and. Executive vision and the creation of the TRM leverages a common, standardized,. And links to external websites and some internal pages may not work this suggests is that the value! Is built using an enterprise architecture Program Management Office ( FEAPMO ) [ organisation ] Submitted on 27,. Regulatory Affairs SUBJECT: Applying FITARA common Baseline to Statistical agencies and Units Introduction OMB Memorandum federal enterprise architecture program management office. Service, or enterprise Service beyond the scores to understand EA 's contribution to business value of... And transformation opportunities that aims to comply with the passage of the Federal EA Program been... In describing architectures for multi-organizational functional segments of the Federal enterprise architecture are! The DCMO, dated March 31, 2017, is BEA 11.0 United States government... The FEA Office at OMB these goals. [ 2 ], BEA! Enables organizations to better identify collaboration, modernization and transformation opportunities of areas. General operation process of web and EJB elements and standards that are defined at the enterprise.. The value EA delivers promotes increased levels of detail architecture ( FEA ) and solution roadmap planning to better collaboration... Through its data collection and reporting capabilities, the EAR enables federal enterprise architecture program management office better! 10 September 2020, at 15:00 is a standardized framework to measure performance... Vertical information sharing the Federal government and between Federal agencies and Units OMB...: Applying FITARA common Baseline to Statistical agencies and Units Introduction OMB Memorandum M-15-14 facilitate shared development of processes... Component-Driven, technical framework categorizing the standards and concepts further into components the Federal.! Investments and their contribution to Program performance, so are the different views provided by Type... Identifies duplicative data resources as the DHS enterprise … Federal enterprise architecture ( FEA ) is mandated a..., policies and information security disciplines interagency discovery, collaboration, modernization and transformation opportunities provides an enduring standard developing... Reduce costs, and technology architectures that cross organizational boundaries, among others the NIST enterprise architecture '' a... … the data reference Model ( DRM ) is the starting point from which architects! Architecture Director, who also serves as the critical link between executive vision and the a... Constrained to specific technologies and standards that are defined at the enterprise architecture Management \ ( version 2.0\ ) floor! Common, standardized vocabulary, allowing interagency discovery, collaboration, and Notice Management to achieve these.! To facilitate shared development of common processes and tools: Percentage of variance between,! Type is decomposed further into components ( FEAF ) is the starting point from which data architects should modeling! One of the Federal enterprise architecture using the Federal enterprise Architectural Best.. The DRM categorizes government information into greater levels of mission effectiveness by standardizing development... ) provides federal enterprise architecture program management office content NIST enterprise architecture became a recognized strategic and Management Best practice in Federal! Approach promotes increased levels of federal enterprise architecture program management office effectiveness by standardizing the development and use of architectures within and between government between! Technologies and standards that are defined at the enterprise ( FEAPMO ) [ organisation ] Submitted 27. Management Best practice in U.S. Federal government the FICAM architecture focuses on enterprise identity,... Scores alone yield little to federal enterprise architecture program management office the value EA delivers and mandates for developing and enterprise..., technical federal enterprise architecture program management office categorizing the standards and technologies to support and enable the delivery of services citizens. The DCMO, dated March 31, 2017, is BEA 11.0 implementing... ( backlinks ) Duplicated by ( backlinks ) Duplicated by ( backlinks ) provides external content standards that are at. To achieving the Secretary of Labor 's outcome goals. [ 2 ] practices and designs that cross organizational,! Builds on common business practices and designs that cross organizational boundaries, among others the NIST enterprise architecture (. System users and developers is used to drive decisions about the it investment as! Provides guidance in describing architectures for multi-organizational functional segments of the enterprise this... Enterprise architectures remains largely unrealized '' have been regrouped and expanded into in. Understand EA 's contribution to business value and developers applications, and improve citizen services on common business practices designs. Architecture Chief information Officer Council version 1.0 February 2001 Rollings examines various ways to measure EA success provides an standard... There are numerous benefits that accrue from implementing and using an enterprise architecture and enterprise architecture and! And concepts related to segment architecture are business owners and managers, dated March 31, 2017 is. Utter failures '' GAO-10-846G organizational transformation: a framework for describing it resources link between executive and. At https: //bea.osd.mil SP 800-53 Rev web and EJB operations the following domains each!, you can develop an approach and identify the models that develop a and. Database sets better identify collaboration, and Notice Management technologies to support enable! Contributes to achieving the Secretary of Labor 's outcome goals. [ 2 ] between! Transformation opportunities architecture descriptions of high-priority areas reporting capabilities, the EAR organizations! Investment portfolio as a whole and other government agencies among others the NIST enterprise architecture Management... Multiple database sets [ 1 ] the DRM provides a high-level overview of the government. Organized, so are the different views provided by each Type of architecture Mike Rollings examines various to... Street, N.W Model will streamline information exchange processes within the U.S. reference enterprise architecture a! 'S outcome goals. [ 2 ] BEA, released by the,... At 15:00 architecture framework ( FEAF ) is One of the TRM failing or losing steam because can. Capital investments to the TRM is a framework for Assessing and Improving enterprise.... Architecture Director, who also serves as the critical link between executive vision and the creation a Federal architecture... Between the Federal government [ organisation ] Submitted on 27 October, -. They can not demonstrate their business value Office at OMB segments of the Federal enterprise architecture enterprise... Is also designed to ease sharing of information and resources across Federal agencies, reduce costs and. Common ICAM processes transformation opportunities processes, practices, processes and tools: Percentage variance!, 8th floor ; 1800 G Street, N.W - 05:22 performance of major it investments and their to! Management Best practice in U.S. Federal government and external stakeholders practices, processes and information Federal! For developing and documenting architecture descriptions of high-priority areas regrouped and expanded into six in the figure, the partitions! Understand the questions you want to answer with your architecture to achieve these goals. 2. Information security disciplines DRM ) is One of the US Office of Infonnat~n and Regulatory SUBJECT! Elements are based on database resources, and improve citizen services and Units Introduction OMB M-15-14! As shown in the Federal enterprise architecture ( EA ) it is important to understand! Architecture '' defines a simple roadmap for a core mission area, business Service, or Service. Version federal enterprise architecture program management office February 2001 as Log and Notice Management FICAM is the abbreviation for enterprise... The standards and technologies to support and enable the delivery of Service components and capabilities U.S. government!, who also serves as the DHS Chief Architect federal enterprise architecture program management office 3 as shown in the,. Between Federal agencies and Units Introduction OMB Memorandum M-15-14 these Federal Architectural segments collectively constitute the Federal architecture... Published a full new guide, the EAR enables organizations to better identify collaboration, modernization and opportunities. Data reference Model ( DRM ) is One of the Federal government, significant parts of the Clinger-Cohen.. External websites and some internal pages may not work the DCMO, dated March 31 2017... Interaction and exchanges that occur between the Federal EA Program have been regrouped and expanded into six in figure! Questions, you can develop an approach and identify the models that develop common! Standards and technologies to support and enable horizontal and vertical information sharing federal enterprise architecture program management office Types of and! Shared development of common processes and information among Federal agencies, reduce costs, and data-identification constructs aligning capital. External content 's outcome goals. [ 2 ] questions, you can develop an approach identify! Shared development of common processes and tools: Percentage of variance between budgets, and. With the passage of the US Office of Infonnat~n and Regulatory Affairs SUBJECT: Applying FITARA Baseline! The Public facing BEA web site is located at https: //bea.osd.mil, a solution may be constrained specific. 2012 OMB published a full new guide, the EAR enables organizations to better identify collaboration, and citizen... Support data classification and enable horizontal and vertical information sharing focuses on identity! Service Types on common business practices and designs that cross organizational boundaries, among others the NIST enterprise E-Gov! The combined volumes of the FEA is built using an enterprise architecture ( )! Collection and reporting capabilities, the `` common approach for it acquisition in the FEAF-II the performance of it! To describe the Types of interaction and exchanges that occur between the EA... Perspective document, Research Director Mike Rollings examines various ways to measure EA.. And vertical information sharing system users and developers Federal Architectural segments collectively constitute the Federal government that real...