WIXLIB

utilize periodic analyses of the aforementioned to realize continuous processimprovement and update of EA.The DoD EA Transition Strategy is an annual report that describes and updates all DoDefforts toward this continuous improvement process. The basic content reflects theOMB criteria for a transition strategy as outlined in the Federal Enterprise ArchitecturePractice Guidance, November 2007, and the DoD version, A Practical Guide forBringing Enterprise Architecture Value to the Mission, May 2007. In addition, OMB,through the OMB EA Assessment Framework, requires a transition strategy as a part ofthe DoD EA.Because of the large and complex Department of Defense with its multiple missions, theDoD EA Transition Strategy encompasses a federated approach to its development.For example, the Business Transformation Agency (BTA) 2007 Enterprise TransitionPlan (ETP) focuses specifically on the Business MA (BMA) and meets the criteria for anagency transition plan. The Enterprise Information Environment Mission Area (EIE MA)will publish an EA in January 2008 and plans to develop a Segment Architecture andTransition Strategy derived from the EA. The Warfighting MA (WMA), DefenseIntelligence MA (DIMA), and Intelligence MA (IMA) are also in the process of developingEAs and their related segment architectures and transition strategies. Projectedcompletion for the WMA and DIMA EAs is in late FY 2008/early FY 2009.Internet Protocol v6 (IPv6), has also developed a transition strategy, the IPv6 TransitionPlan V2.0, June 2006. In addition, as a sample set to exemplify DoD Components’transition planning, the 65 current Exhibit 300 investments have submitted MiniTransition Strategies to be used as a basis for analysis in this DoD EA TransitionStrategy,Using the DoD EA Annual Plan (embedded in Appendix A), a plan for that addressesEA progress as a guide, the DoD EA Transition Strategy accomplishes the following: Provides a repeatable process for creating, maintaining, and managing the DoDEA Transition Strategy, including processes for performing gap analysis,alternatives analysis, and the management of projects over time. Provides a mechanism for identifying opportunities for consolidation or reuse andgaps between the “baseline” and “target” architecture. Documents defined programs and projects and sequencing plans in support of itstarget architecture. Addresses priorities and performance objectives identified in the 2006 QDR. Includes initiatives with milestones for at least one segment architecture, theBusiness EA (BEA) for DoD’s Business Mission Area. Demonstrates clear linkage between Net-Centric capabilities in the TransitionStrategy and investments in the DoD investment portfolio.3

Includes defined and measurable performance milestones that indicate theDepartment’s success in achieving performance targets and has processes andtools in place to track performance. Identifies timelines for implementing net-centric attributes with supportingartifacts for investments in the IT300 Exhibit.The approach for developing this DoD EA Transition Strategy to address the complexDoD environment and meet the criteria for the OMB EA Assessment Framework,includes the following steps: Describe associations with the DoD transformation goals from the 2006 QDR Describe the status of DoD EA as a federated baseline architecture and thestatus of ongoing transformation efforts Describe the GIG Architectural Vision and related artifacts that comprise thefederated objective (target) architecture Analyze representative DoD IT300 Exhibit investments’ transition strategies andtheir performance measures to document transformation progress. Summarizefindings. Recommend an approach for continuous process improvement, including theDoD EA governance process and a DoD federated process that makes DoD NetCentric transformation information visible, accessible, and understandable.4

Section 2. DoD Net-Centric Environment (NCE)This section addresses the Mission and Change Drivers of DoD and by outlining theQuadrennial Defense Review (QDR) goals for transformation and the inherent need fora transition strategy to track progress toward the future Net-Centric Environment (NCE).Section 2 Contents: Description of the NCEDescription of the NCEThe DoD EA Transition Strategy links to the strategic goals of the Department asrepresented in the QDR 2006. These strategic goals cannot be accomplished without astrategy to transition from the existing environment represented by stove-piped systemsand islands of information to the desired NCE, and a commitment to the changesnecessary to accomplish the capabilities of the transformational NCE.The DoD leadership envisions the NCE as the underpinning of the many changesforeseen in the QDR 2006, which is a top-down look at US defense strategy, taking intoaccount the world environment, threats, current forces and programs, and the resourceslikely to be available. The Department foresees the need for continuous change, whichbuilds on the ever changing world in which the warfighter operates. The QDR maps theway ahead for the next 20 years as the Department confronts current and futurechallenges and continues its transformation for the 21st century.To characterize the nature of the Department’s transformation, it should be viewed as ashift of emphasis to meet the new strategic environment. Examples of this shift inemphasis include:1From a peacetime tempoFrom a time of reasonable predictabilityFrom single-focused threatsFrom nation-state threatsTo a wartime sense of urgencyTo an era of surprise and uncertaintyTo multiple, complex challengesTo decentralized network threats fromnon-state enemiesTo conducting war in countries we are notat war with (safe havens)To tailored deterrence for rogue powers,terrorist networks and near-peercompetitorsTo preventive actions so problems do notbecome crises (proactive)To shaping the futureTo capabilities based planningFrom conducting war against nationsFrom “one size fits all” deterrenceFrom responding after a crisis starts(reactive)From crisis responseFrom threat-based planning12006 Quadrennial Defense Review5

From peacetime planningFrom a focus on kineticsFrom 20th century processesFrom static defense, garrison forcesFrom under-resourced, standby forces(hollow units)From a battle-ready force (peace)From large institutional forces (tail)To rapid adaptive planningTo a focus on effectsTo 21st century integrated approachesTo mobile, expeditionary operationsTo fully-equipped and fully-manned forces(combat ready units)To battle hardened forces (war)To more powerful operational capabilities(teeth).From major conventional combatTo multiple irregular, asymmetricoperations –operationsFrom separate military Service concepts of To joint and combined operationsoperationFrom forces that need to de-conflictTo integrated, interdependent forcesFrom exposed forces forwardTo reaching back to CONUS to supportexpeditionary forcesFrom an emphasis on ships, guns, tanksTo focus on information, knowledge andand planestimely, actionable intelligenceFrom massing forcesTo massing effectsFrom set-piece maneuver and massTo agility and precisionFrom single Service acquisition systemsTo joint portfolio managementFrom broad-based industrial mobilizationTo targeted commercial solutionsFrom Service and agency intelligenceTo truly Joint Information OperationsCentersFrom vertical structures and processesTo more transparent, horizontal integration(stovepipes)(matrix)From moving the user to the dataTo moving data to the userFrom fragmented homeland assistanceTo integrated homeland securityFrom static alliancesTo dynamic partnershipsFrom predetermined force packagesTo tailored, flexible forcesFrom the U.S. military performing tasksTo a focus on building partner capabilitiesFrom static post-operations analysisTo dynamic diagnostics and real-timelessons learnedFrom focusing on inputs (effort)To tracking outputs (results)From Department of Defense solutionsTo interagency approachesThis shift in emphasis depends on the changes enabled by the NCE. Harnessing thepower of information connectivity defines Net-Centricity and serves as an underpinningof all other transformations. By enabling critical networked relationships betweenorganizations and people, the Department will be able to accelerate the speed ofbusiness processes, operational decision-making and subsequent actions due to better,more timely information. The collection and dissemination of information should bemanaged by portfolios of capabilities that cut across legacy stove-piped systems. Thesecapability portfolios require the identification of capability increments to measure6

progress toward the NCE and to address gaps, redundancies, and opportunities forreuse.The foundation for Net-Centric operations is the GIG, the target architecture describedin the GIG Architectural Vision that includes a globally interconnected, end-to-end set oftrusted and protected information networks. The GIG will enable the secure, agile,robust, dependable, interoperable data sharing environment for the Department wherewarfighter, business, and intelligence users share knowledge on a global network thatfacilitates information superiority, accelerates decision-making, effective operations, andNet-Centric transformation.The Department has made steady progress implementing Net-Centric systems andconcepts of operation. It has deployed an enhanced land-based network and newsatellite constellation as part of the Transformational Communication Architecture (TCA)to provide high-bandwidth, survivable internet protocol communications. Together, theysupport battle-space awareness, time-sensitive targeting and communicationscapabilities on the move. Deployed terminals – from command and control (JointTactical Radio System) to very large bandwidth ISR systems – are extending thecommunications “backbone” down to the smallest tactical unit in the field.Another foundation for Net-Centric operations is the DoD Net-Centric Data Strategyenabling the fusion of information from any platform or terminal. Pulling all this together,the revised Unified Command Plan has assigned U.S. STRATCOM lead responsibilityto operate and protect the GIG. To move closer toward this vision and build on progressto date, the Department will: Strengthen its data strategy – including the development of common datalexicons, standards, organization, and categorization – to improve informationsharing and information assurance, and extend it across a multitude of domains,ranging from intelligence to personnel systems. Increase investment to implement the GIG, defend and protect information andnetworks and focus research and development on its protection. Develop an information-sharing strategy to guide operations with Federal, state,local and coalition partners. Shift from Military Service-focused efforts toward a more Department-wideenterprise Net-Centric approach, including expansion of the Distributed CommonGround System. Restructure the Transformational Satellite (TSAT) prog

The DoD Enterprise Architecture (EA) Transition Strategy 2008 follows the outline in the Federal Practice Guidance, November 2007, for developing a Transition Strategy and meeting the criteria for the OMB EA Assessment. To help the reader to understand the document, a description of the sections and their content follows: Section 1. Introduction.