The Deputy Secretary of Defense approved the release of the September 2008 Enterprise Transition Plan (ETP) to the Congressional Defense Committees on October 17. The ETP is the Departmentís integrated business transformation plan, which incorporates the transition plans of the Military Services, Components and the DoD Enterprise. The ETP provides the roadmap for achieving DoD business transformation by implementing changes to technology, process, and governance. The plan contains time-phased milestones, performance metrics, and a statement of resource needs for new and existing systems that are part of the Business Enterprise Architecture (BEA) and Component enterprise architectures. The ETP includes a schedule for terminating legacy systems and replacing them with newer, improved enterprise solutions. This ETP includes for the first time program dashboards for each program and initiative, and business capability and system metrics.
The U.S. Department of Defense, in response to Section 904 of the National Defense Authorization Act for Fiscal Year 2008, has released a Strategic Management Plan and Section 904 Implementation Plan. The Strategic Management plan provides an executive overview of the governance and management framework and processes used by the Deputy Secretary, serving as Chief Management Officer, to deliver effective and efficient support to the warfighter, describes how recent institutional and governance reforms have improved the effectiveness and efficiency of defense business operations, and suggests that this progress can serve as a template to guide future improvements. The Implementation Plan details the steps that the Department is taking to fully implement the requirements of Section 904, including creating the position of Deputy Chief Management Officer and establishing the Under Secretaryís of the Military Departments as the Chief Management Officers of their respective organizations.
The U.S. Department of Defense (DoD) Business Transformation Agency (BTA)
has released the newly updated Business
Enterprise Architecture (BEA 5.0) and March 2008 Congressional Report.
The BEA is the blueprint and the Congressional Report is the roadmap for the Department's
business transformation. The BEA provides the architectural framework
for the Department's
interoperable information infrastructure. The Congressional Report articulates a systematic
process for delivering improved capabilities that will have a major impact
on the performance of DoD's business mission.
The Office of Business Transformation (OBT), within the Department of Defense (DoD), is announcing the release of the newly updated Business Mission Area (BMA) Architecture Federation Strategy and Roadmap Version 2.4a on 29 January 2008. The BMA Architecture Federation Strategy and Roadmap was introduced to the Defense Business Systems Management Committee (DBSMC) in October of 2007 and has gained full concurrence across the Department.
The BMA's concept of architecture federation represents the DoD strategy for linking BMA architectures of Components, Services and Agencies (C/S/A) and Programs to the Business Enterprise Architecture (BEA) to form the BMA portion of the Global Information Grid (GIG). In addition the Business Mission Area (BMA) Architecture Federation Strategy and Roadmap Version 2.4a details infrastructure, products, services, capabilities and actions to implement architecture federation and deliver business services across the BMA and from tier to tier within the DoD.
The Enterprise Transition Plan (ETP) was delivered to Congress on September 28, 2007. The ETP is the roadmap for achieving DoD business transformation by implementing changes to technology, process, and governance. The plan contains time-phased milestones, performance metrics, and a statement of resource needs for new and existing systems that are part of the Business Enterprise Architecture (BEA) and Component architectures. The ETP includes a schedule for terminating old systems and replacing them with newer, improved enterprise solutions. The ETP and BEA, working together, allow leadership to evaluate gaps and overlaps between current programs and redirect efforts to minimize redundancy and provide needed business capabilities.
The driver for evolving the BEA is to produce an architecture that can be harnessed as an executive decision-making mechanism while simultaneously supporting the implementation of information technology systems and services. This Concept of Operations for Business Enterprise Architecture (BEA) Requirements addresses this objective by 1) outlining a new architecture development approach that addresses both top-down strategic requirements and bottom-up tactical requirements, and 2) expanding the governance process to encourage users and stakeholders to shape architecture form and content. The CONOPS also discusses the new annual BEA delivery cycle intended to provide improved requirements stability for transformational programs.