Frequently Asked Questions for BEA
Table of Contents
What is the Business Enterprise Architecture (BEA)?
Where can I find previous copies of the BEA?
Why is the BEA important to the Department of Defense?
How are the BEA, the Agency Strategic Plan (ASP), Enterprise Transition Plan (ETP) and Congressional Report related?
What are the DoD's Core Business Missions? How do they relate to the BEA?
What is the scope of the BEA? Will priorities change in each version?
Does BEA 11 address gaps from previous versions? What other revisions were made?
Does the BEA provide solutions?
Does the BEA use the DoD Architecture Framework? If so, what products are included?
What is the focus of the BEA 11?
What are the next steps for the BEA?
When is the next scheduled release of the BEA?
Who is responsible for developing the BEA? How is it developed?
Which version of the BEA will be used for annual investment certification reviews?

What is the Business Enterprise Architecture (BEA)?

The BEA is the enterprise architecture for the DoD Business Mission Area (BMA) and defines the DoD business transformation priorities, the Business Capabilities required to support those priorities, and the combinations of Enterprise Systems and Initiatives that enable those capabilities.

The BEA is developed using a set of integrated DoD Architecture Framework (DoDAF) models. The BEA uses DoDAF 2.0 naming conventions - Capability Viewpoint, Data & Information Viewpoint, Standard Viewpoint, and Services Viewpoints. The BEA includes Operational Activities, Business Processes, Data, Information Exchanges, Business Rules, System Functions, System Data Exchanges, terms, and linkages to Laws, Regulations, and Policies (LRP).

The purpose of the BEA is:

"To provide a blueprint for DoD business transformation that helps to ensure that the right capabilities, resources and materiel are rapidly delivered to our warfighters: What they need, where they need it, when they need it, anywhere in the world. The BEA guides and constrains implementation of interoperable defense business system solutions as required by the National Defense Authorization Act (NDAA) and guides information technology (IT) investment to align with strategic Business Capabilities as required by NDAA, Clinger-Cohen and supporting Office of Management and Budget (OMB) and Government Accountability Office (GAO) policy."


Return to FAQs

Where can I find previous copies of the BEA?

BEA 11.2 can be found at http://bea.osd.mil.

For BEA versions older than 11, please Contact Us.

Return to FAQs


Why is the BEA important to the Department of Defense?

The BEA is critical to the DoD because it defines business transformation priorities, business capabilities required to support those priorities, and systems and initiatives that enable these capabilities. The BEA articulates the future vision of change within the Department's business enterprise. The BEA guides and constrains implementation of interoperable defense business system solutions as required by the National Defense Authorization Act (NDAA) and guides information technology (IT) investments to align with strategic Business Capabilities as required by NDAA, Clinger-Cohen and supporting Office of Management and Budget (OMB) and Government Accountability Office (GAO) policy.

Return to FAQs


How are the BEA, the Agency Strategic Plan (ASP), Enterprise Transition Plan (ETP) and Congressional Report related?

The ASP is the key driver for development of the BEA. BEA development efforts focus on alignment with the SMP defined goals and objectives. The SMP sets the strategic direction for the Department's business operations. The transformation effort guiding BEA development continues to focus on SMP alignment, providing tangible outcomes for a limited set of priorities, and developing architecture that is integrated, understandable and actionable.

The Enterprise Transition Plan (ETP) is the conceptual roadmap that implements the DoD Business Enterprise Architecture (BEA). It does so by linking current and proposed agency investments to the target architecture, thereby defining the path to a transformed DoD enterprise and by identifying business investments that provide enterprise capabilities that support the warfighter and decision makers. Major time-phased milestones for Enterprise and Component Systems, performance measures, financial resource needs, and risks or challenges to integration into the BEA are depicted therein. The ETP also lists legacy systems that will not be part of the BEA, together with the schedule for terminating those legacy systems

The ASP and ETP provide important information to DoD leaders to help them guide future efforts toward progress evaluation, gap and overlap identification, and the achievement of Department priorities. The identification of such overlaps minimizes redundancy; while the knowledge of and refocused attention to existing gaps better enables requisite business capabilities. The SMP, BEA, and ETP provide a guide, blueprint, and roadmap, respectively, for defense business transformation.

The Congressional Report provides a status on specific improvements in business operations and cost savings resulting from successful Defense Business Systems programs, as well as status of BEA and ETP implementation. Together, these products identify the Department's business mission area enterprise priorities (SMP), the target environment (BEA), the path to that target environment (ETP), and the progress towards that target environment (Congressional Report).

Return to FAQs


What are the DoD's Core Business Missions? How do they relate to the BEA?

The Core Business Missions (CBMs) are a defined area of responsibility with functions and processes that provide end-to-end support to the warfighter and articulate business transformation requirements into the BEA from the Strategic Management Plan (SMP). The SMP sets priorities and provides strategic direction for Departmental business operations to enable business transformation within the DoD. The five Core Business Missions are: Financial Management (FM), Human Resources Management (HRM), Materiel Supply & Service Management (MSSM), Real Property & Installations Lifecycle Management (RPILM), and Weapon System Lifecycle Management (WSLM). These five CBMs are represented by the Under Secretaries of Defense that lead various business initiatives and ensure business outcomes are addressed and implemented.

The five CBMs are:

Financial Management (FM)  The Office of the Under Secretary of Defense (Comptroller) (OUSD(C)) plays a pivotal role in guarding and guiding the proper stewardship of taxpayer dollars in support of the DoD mission and is a key participant in overall Defense business process management. The Comptroller has three primary goals:

  • Acquire the resources necessary to meet national defense objectives;
  • Ensure the legal, effective, and efficient use of DoD resources;
  • Champion a strong and capable FM workforce

Human Resources Management (HRM)  HRM encompasses all functional processes required to acquire, train, manage, pay and provide benefits to the military and civilian personnel in the DoD (throughout their careers and beyond), as well as support family members, veterans, retirees, volunteers and contractors. A primary objective of the HRM CBM portfolio is to provide accurate human resources information to decision makers such as numbers, competencies (occupations, skills, education and training), reception accounting, individual readiness, patient accountability and status reporting, individuals' unit and location, and assigned duty within organizations. This mission includes ensuring that Combatant Commanders have access to timely and accurate data on personnel that includes their skill sets and competencies.

Material Supply and Service Management (MSSM)  The Materiel Supply and Service Management Core Business Mission covers DoD's supply chain, responsible for ensuring enterprise business capabilities to maintain readiness for the warfighter and sustain the force at a level of performance that meets or exceeds Combatant Commander's requirements. The key elements of MSSM include the planning, sourcing, procurement, contract management and oversight, operational contract support (OCS), making and manufacturing, maintenance and repairing, performing logistics and field services, sustainment operations, delivery of property and forces, retail sales, and the return or retrograde of all classes of supply (materiel), and forces (deployments).

Real Property and Installations Lifecycle Management (RPILM)  The Real Property and Installations Lifecycle Management provides the warfighter and Core Business Missions (CBM) access to near-real time secure, accurate and reliable information on real property assets and environment, safety and occupational health sustainability.

Weapon System Lifecycle Management (WSLM)  The Weapon System Lifecycle Management (WSLM) Core Business Mission is responsible for the full lifecycle management -'cradle-to-grave'- of Defense acquisition of weapon systems and automated information systems to include requirements, technology, development, production, sustainment, and disposal.

Refer to the BEA 11 Core Business Mission section for more detailed descriptions of each CBM.

The Defense Business Systems Investment Management Process Guidance of June 2012 also describes the new IRB process that introduced the concept of Functional Strategies. "Informed by the Quadrennial Defense Review (QDR) and the DoD Strategic Management Plan (SMP), Functional Strategies will provide guidance to DoD Components on the strategic vision, goals, priorities, outcomes, measures and any mandatory enterprise solutions for a given Functional Area."

There is a general alignment between the new Functional Areas and the Core Business Missions (CBM) that are represented in the BEA. For BEA 10.0 the CBM naming conventions will be maintained due to time constraints imposed by the February 14, 2013 delivery date.

Return to FAQs


What is the scope of the BEA? Will priorities change in each version?

The scope of the BEA is defined within the End-to-End (E2E) Framework, which are integrated Business Flows which span both functions and organizations. The BEA includes functions, processes, rules, data or standards that are required to be used in a standard manner to support or describe the DoD business enterprise. Scope is further defined by the SMP to meet the strategic outcomes identified therein. Priorities may change as articulated or directed by DoD senior leadership to meet mission and strategic objectives.

Return to FAQs


Does the BEA 11.2 address gaps from previous versions? What other revisions were made?

Each BEA release addresses selected architecture gaps identified in the previous release's AV-1 Findings and Recommendations, the Functional Strategies and Organizational Execution Plans (OEP) and the Enterprise Transition Plan. In addition to new content, the current release includes architecture maintenance work to clarify existing content and improve the usability, production, visualization and functionality of the architecture. Refer to the BEA 11.2 Summary for a detail description of changes.

Return to FAQs


Does the BEA provide solutions?

No. The BEA is an enterprise-level transformation architecture. Under the tiered accountability paradigm, specific solutions will be developed at the Component and Program level, based upon BEA requirements.

Return to FAQs


Does the BEA use the DoD Architecture Framework? If so, what products are included?
Yes. BEA 11 aligns with DoDAF 2.0 naming conventions for products where applicable, such as Capability Viewpoint, Data & Information Viewpoint, Standard Viewpoint, and Services Viewpoints. The BEA 11 products are listed in the table below:

Name DoDAF Moniker Translation
AV - All Viewpoint
Overview and Summary AV-1 Executive overview
Integrated Dictionary AV-2 Lexicon of Architectural Objects
Capability Viewpoint
Capability Taxonomy CV-2 What abilities are depicted?
Data and Information Viewpoint
Conceptual Data Model DIV-1 What data and information is required?
Logical Data Model DIV-2 How do rules apply to the data and information?
OV - Operational Viewpoint
Operational Resource Flow Description OV-2 What resources are required by whom?
Operational Resource Flow Matrix OV-3 What resources are exchanged between tasks?
Operational Activity Decomposition Tree OV-5a What are the tasks and their hierarchies?
Operational Activity Model OV-5b What is required to perform a task?
Operational Rules Model OV-6a What are the rules that constrain tasks?
Event-Trace Description (Business Process Model) OV-6c What is the sequence of tasks?
Systems Viewpoint
Systems Interface Description SV-1 What are the standards?
Systems Interface Details SV-1 How do systems interface with other systems?
Operational Activity to Systems Function Traceability Matrix SV-5a How are tasks performed by systems?
Systems Resource Flow Matrix SV-6 How do systems interface with other systems?
Standards Viewpoint
Standards Profile StdV-1 What are the Standards?
Services Viewpoint
Services Context Description SvcV-1 What services and interconnections are required?
Operational Activity to Services Traceability Matrix SvcV-5 How do these services map back to functional activities?

Return to FAQs


What is the focus of the BEA 11?

The main focus areas for BEA 11.2 support the intended uses of the architecture: FY2015 - FY2018 Agency Strategic Plan (ASP), the Department will focus its efforts to improve overall management of its business system investments in five areas:

  • Defeat our Adversaries, Deter War, and Defend the Nation
  • Sustain a Ready Force to Meet Mission Needs
  • Strengthen and Enhance the Health and Effectiveness of the Total Workforce
  • Achieve Dominant Capabilities through Innovation and Technical Excellence
  • Reform and Reshape the Defense Institution

Return to FAQs


What are the next steps for the BEA?

The Defense Business Systems Investment Management Process Guidance of June 2012 describes how the BEA will be incorporated into the DoD business transformation effort This new investment management approach will allow for an expansive and thorough look at how investments within a given functional or organizational portfolio fit and help to ensure that the Department is making smart investments that align to mission priorities. The process focuses on DoD Components taking responsibility for reviewing and aligning all business system investments within their Component prior to bringing their Organizational Execution Plan to the DBC. This process also helps to align a number of other statutorily required activities. Functional strategies will help to expand and refine the Department's Agency Strategic Plan. Organizational Execution Plans will serve as the basis for the Department's Enterprise Transition Plan (ETP), become the "Target Defense Business Systems Computing Environment," and be incorporated into the Department's BEA.

The BEA will remain aligned to the Department of Defense Architecture Framework (currently DoDAF v2.0) and use the DoDAF Meta Model (DM2) as its foundation. DM2 describes an architectural meta-model that enables the integration, federation and exchange of Architectural Descriptions. In order to leverage the semantics (meaning) within these integrated architectures, the federated BEA ontology will be described using a common language (World-Wide Web Consortium (W3C), open standards Resource Description Framework (RDF)/Web Ontology Language (OWL)) and modeling notation (Business Process Modeling Notation (BPMN) 2.0 with Analytic Conformance Class (Primitives)). These standards shall be applied to all subordinate enterprise and solution architectures federated with the BEA.

The E2E framework shall be used to drive BEA content within the federated BEA ontology. Future releases of the BEA will be synchronized with our highest priority system acquisition and modernization efforts related to the critical activities within the E2E lifecycle models.

Return to FAQs


When is the next scheduled release of the BEA?
The Office of the Chief Management Officer (OCMO) annually releases the enterprise architecture for the DoD Business Mission Area (BMA) to help defense business system owners and program managers make informed decisions in support of the Department. Annual releases are concurrent with the release of the March Congressional Report. Informational releases are delivered on an interim basis to serve as a "snapshot" of ongoing development efforts and reflect informational content updates to the latest official annual release of the BEA.

Return to FAQs


Who is responsible for developing the BEA? How is it developed?

The BEA content is developed by the stakeholders from the Principal Staff Assistants (PSA) in conjunction with DoD Components and Agencies. The CMO coordinates requirements gathering, BEA development, integration and technical DoDAF solutions. Refer to the Architecture Product Guide (APG) for specific guidance on development of each product in the BEA.

Return to FAQs


Which version of the BEA will be used for annual investment certification reviews?

The version of the BEA to be used during investment reviews will be announced at the start of the Fiscal Year for the investment review and Organizational Execution Plan (OEP) development cycle that begins in the 3rd quarter of that same Fiscal Year. Interim BEA releases for information and planning purposes may be announced periodically prior to a Fiscal Year's start.

Return to FAQs