Products

Business Enterprise Architecture (BEA)

Business Enterprise Architecture (BEA) 6.2

The Business Transformation Agency (BTA) annually releases the Business Enterprise Architecture (BEA) for the Department of Defense (DoD) Business Mission Area (BMA) to help defense business system owners and program managers make informed decisions in support of the Department. The latest official annual release of the BEA – BEA 6.0 was delivered on March 13, 2009.

Starting in July 2009, the BTA introduced informational releases, which reflect interim content updates to allow stakeholders to accelerate the implementation of requirements outside of the official release schedule, while obtaining insight into other ongoing BEA updates. BEA 6.2, released on October 28, represents two primary areas of improvement: visualization enhancements and updates to the End-to-End (E2E) business flows.

Informational releases are published for informational purposes only and will not be used to assert compliance or update the DoD Information Technology Portfolio Repository (DITPR). The next official annual release, BEA 7.0, is scheduled for March 12, 2010.

Business Enterprise Architecture (BEA) 6.1

Business Enterprise Architecture (BEA) 6.0

The BEA is the enterprise architecture for the Department of Defense (DoD) Business Mission Area (BMA). The BEA defines the Department’s business transformation priorities, the business capabilities required to support those priorities and the combinations of enterprise systems and initiatives that enable those capabilities. 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 management 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.

Background

The BEA was statutorily mandated by the National Defense Authorization Act of 2005 (10 United States Code (U.S.C.) §186). This same statute also established requirements for a DoD Enterprise Transition Plan (ETP), an annual Report on Defense Business Operations to Congress, and a senior governance body comprised of Investment Review Boards (IRBs) and the Defense Business Systems Management Committee (DBSMC) chaired by the Deputy Secretary of Defense. The IRBs and DBSMC provide effective business capability oversight and decision-making. They certify and approve business system modernizations over $1 million as compliant to the BEA.

BEA compliance is required before funds may be obligated. BEA compliance is also required for business Major Automated Information Systems (MAIS) and Major Defense Acquisition Programs (MDAP) before milestone approval decisions. These programs utilize the Business Capability Lifecycle (BCL) process. BCL reengineers major DoD processes to provide better governance and decision support to enable faster delivery of business capabilities.

BEA Content

The transformation effort guiding BEA development continues to focus on providing tangible outcomes for a limited set of priorities and on developing architecture that is integrated, understandable and actionable. The main focus areas for BEA support the intended uses of the architecture:

Investment Management – Support alignment of services, systems and solutions to the prioritized strategic capabilities of the Department
Interoperability - Permit approval authorities to demonstrate compliance with the BEA to achieve transformation objectives and implementation of interoperable business solutions

The BEA includes activities, processes, data, information exchanges, business rules, system functions, system data exchanges, terms, and linkages to laws, regulations and policies. It is developed using a set of integrated DoD Architecture Framework (DoDAF) products, including: All View (AV), Operational View (OV), Systems and Services View (SV) and Technical Standards View (TV) products.

Authority