Mission Capability Packages

Similar documents
Digital Engineering Support to Mission Engineering

Digital Engineering. Phoenix Integration Conference Ms. Philomena Zimmerman. Deputy Director, Engineering Tools and Environments.

Technology Roadmapping. Lesson 3

I. INTRODUCTION A. CAPITALIZING ON BASIC RESEARCH

Lesson 17: Science and Technology in the Acquisition Process

SIMULATION-BASED ACQUISITION: AN IMPETUS FOR CHANGE. Wayne J. Davis

Impact of Technology on Future Defense. F. L. Fernandez

EMBEDDING THE WARGAMES IN BROADER ANALYSIS

C2 Theory Overview, Recent Developments, and Way Forward

Understanding DARPA - How to be Successful - Peter J. Delfyett CREOL, The College of Optics and Photonics

RAPID FIELDING A Path for Emerging Concept and Capability Prototyping

POSITION PAPER. GREEN PAPER From Challenges to Opportunities: Towards a Common Strategic Framework for EU Research and Innovation funding

SYSTEMS ENGINEERING MANAGEMENT IN DOD ACQUISITION

UNCLASSIFIED. R-1 ITEM NOMENCLATURE PE S: Microelectronics Technology Development and Support (DMEA) FY 2013 OCO

COMMERCIAL INDUSTRY RESEARCH AND DEVELOPMENT BEST PRACTICES Richard Van Atta

We Have an App for That: U.S. Military Use of Widgets and Apps to Increase C2 Agility

Dynamics of National Systems of Innovation in Developing Countries and Transition Economies. Jean-Luc Bernard UNIDO Representative in Iran

Other Transaction Authority (OTA)

ARMY RDT&E BUDGET ITEM JUSTIFICATION (R2 Exhibit)

Future of New Capabilities

Engineered Resilient Systems NDIA Systems Engineering Conference October 29, 2014

Voluntary Education Program Readiness (Force Education & Training)

Computer Technology and National

USEUCOM Science & Technology, E

Report to Congress regarding the Terrorism Information Awareness Program

I Need Your Cost Estimate for a 10 Year Project by Next Week

Software-Intensive Systems Producibility

Prototyping: Accelerating the Adoption of Transformative Capabilities

Defense Microelectronics Activity (DMEA) Advanced Technology Support Program IV (ATSP4) Organizational Perspective and Technical Requirements

Engineering Autonomy

Space Technology FY 2013

Stars War: Peace, War, and the Legal (and Practical) Limits on Armed Conflict in Space

DEPARTMENT OF DEFENSE SCIENCE AND TECHNOLOGY

DEFENSE ACQUISITION UNIVERSITY EMPLOYEE SELF-ASSESSMENT. Outcomes and Enablers

Brief to the. Senate Standing Committee on Social Affairs, Science and Technology. Dr. Eliot A. Phillipson President and CEO

A Knowledge-Centric Approach for Complex Systems. Chris R. Powell 1/29/2015

SUBJECT: Army Directive (Acquisition Reform Initiative #3: Improving the Integration and Synchronization of Science and Technology)

Open Systems Architecture in DoD Acquisition: Opportunities and Challenges

Proposed Curriculum Master of Science in Systems Engineering for The MITRE Corporation

Spiral Acquisition and the Integrated Command and Control System

Survey of Institutional Readiness

An exploration of the future Latin America and Caribbean (ALC) and European Union (UE) bi-regional cooperation in science, technology and innovation

UNCLASSIFIED. UNCLASSIFIED Office of Secretary Of Defense Page 1 of 5 R-1 Line #102

Agile Acquisition of Agile C2

Earth Cube Technical Solution Paper the Open Science Grid Example Miron Livny 1, Brooklin Gore 1 and Terry Millar 2

The 26 th APEC Economic Leaders Meeting

Strategic Guidance. Quest for agility, innovation, and affordability. Distribution Statement A: Approved for Public Release

DoD Research and Engineering Enterprise

B222A. Management technology and innovation

University of Massachusetts Amherst Libraries. Digital Preservation Policy, Version 1.3

Module 1 - Lesson 102 RDT&E Activities

Volume 4, Number 2 Government and Defense September 2011

Interoperable systems that are trusted and secure

Defense Innovation Day Unmanned Systems

DOD Technology Innovation & Transition

STATEMENT OF DR. MARK L. MONTROLL PROFESSOR INDUSTRIAL COLLEGE OF THE ARMED FORCES NATIONAL DEFENSE UNIVERSITY BEFORE THE HOUSE ARMED SERVICES

Please send your responses by to: This consultation closes on Friday, 8 April 2016.

Towards a World in Common Strategy. #WorldInCommon

Module 5 Harmonizing C 2 with Focus and Convergence

Broader Impacts: Achieving Greater Goals

DISTRIBUTED COHERENT RF OPERATIONS

ACCELERATING TECHNOLOGY VISION FOR AEROSPACE AND DEFENSE 2017

Belgian Position Paper

A new role for Research and Development within the Swedish Total Defence System

An Industry Response to the Acquisition Changes

SPACE SITUATIONAL AWARENESS: IT S NOT JUST ABOUT THE ALGORITHMS

Warfighters, Ontology, and Stovepiped Data, Information, and Information Technology

Compendium Overview. By John Hagel and John Seely Brown

DoD Information Enterprise Strategic Plan and Roadmap

DoD Research and Engineering

An Element of Digital Engineering Practice in Systems Acquisition

Okinawa Charter on Global Information Society

Engineered Resilient Systems DoD Science and Technology Priority

CAPACITY BUILDING INITIATIVE ON INCLUSIVE/COMMUNITY-BASED INNOVATION FOR AU MEMBER STATES

STRATEGIC FRAMEWORK Updated August 2017

NATIONAL TOURISM CONFERENCE 2018

International Energy Cooperation for Radical Innovation Keith Smith Oslo 23 May 2013

High Performance Computing Systems and Scalable Networks for. Information Technology. Joint White Paper from the

Foresight Impact on Policy making and Lessons for New Member States and Candidate Countries Insights from the FORLEARN mutual learning process

April 10, Develop and demonstrate technologies needed to remotely detect the early stages of a proliferant nation=s nuclear weapons program.

The Role of the Communities of Interest (COIs) March 25, Dr. John Stubstad Director, Space & Sensor Systems, OASD (Research & Engineering)

IFT STRATEGIC PLAN. 2017/18 Strategic Objectives

System of Systems Software Assurance

Dedicated Technology Transition Programs Accelerate Technology Adoption. Brad Pantuck

COMPETITIVE ADVANTAGES AND MANAGEMENT CHALLENGES. by C.B. Tatum, Professor of Civil Engineering Stanford University, Stanford, CA , USA

Evolution of a Software Engineer in a SoS System Engineering World

Moving to Model-Based Design

DMSMS Management: After Years of Evolution, There s Still Room for Improvement

Our Acquisition Challenges Moving Forward

Stakeholder and process alignment in Navy installation technology transitions

The New DoD Systems Acquisition Process

Frameworks for Assessing IT Systems Engineering Acquisition Issues and Proposed Approaches in Support of Public Law 111

DoD Engineering and Better Buying Power 3.0

CRS Report for Congress

The Institute for Communication Technology Management CTM. A Center of Excellence Marshall School of Business University of Southern California

Mission Engineering and Prototype Warfare: Operationalizing Technology Faster to Stay Ahead of the Threat

Integrated Transition Solutions

A Systems Engineering Perspective on Innovation

Chemical-Biological Defense S&T For Homeland Security

OSRA Overarching Strategic Research Agenda and CapTech SRAs Harmonisation. Connecting R&T and Capability Development

Transcription:

Mission Capability Packages Author: David S. Alberts January 1995 Note: Opinions, conclusions, and recommendations expressed or implied in this paper are solely those of the author and do not necessarily represent the views of the Institute for National Strategic Studies, National Defense University, the Department of Defense, or any other government agency. Winds of Change The winds of change that envelop us are driven by four forces: a constrained military budget an end to bi-polar global competition with Moscow an increase in the number of non-traditional operations the military is being called upon to execute rapid advances in technology, particularly in telecommunications and information processing Properly harnessed and shaped, these forces can propel us into a future in which the military will not only remain a cornerstone of national strength and security but become an indispensable part of the fabric of world peace and prosperity. Two prerequisites for success are in our control: 1) the development of new and innovative concepts and strategies, made possible by technology, to meet mission challenges, 2) the ability to transform these embryonic concepts and strategies into real operational capability unconstrained by institutional considerations. What is needed is a process that can ensure and facilitate the necessary innovations, then subject them to scrutiny and validation, and to bring them to fruition in the form of packages of capability designed to accomplish specific missions. Mission Capability Packages The Mission Capability Package concept proposed here is an extension of previous efforts initiated during the 1960s with the introduction of the Planning, Programming, and Budgeting Execution System (PPBS), continued by the Goldwater-Nichols legislation, and most recently advanced by the expanded JROC process, to build capabilities around a vision of how missions should be performed rather than an outmoded process based upon institutional artifacts. 1

This concept is the culmination of a long process of evolution in U.S. Force Planning. In the 1960s, the DOD was in need of "systems thinking" so that relationships among programs would be explicitly considered. Goldwater-Nichols extended this concept from programs to warfighting itself. Now the expanded JROC process is poised to complete this transformation building institutions based upon mission requirements rather than trying to satisfy mission requirements within given institutional structures and constraints. During the past year, ACT has been working with individuals in OSD, the Joint Staff, DISA, and ARPA to improve the technology insertion process. The approach described below is a result of these efforts to exploit the opportunities that technology affords to change the way we organize, equip, and fight. Mission Capability Packages (MCP), as the end products of such a process, would contain concepts of operations, command and force structures, the corresponding doctrine, training and education, technology, and systems with a support infrastructure designed and tailored to accomplish specific missions. An integral part of the MCP concept is the approach proposed to synchronize the insertion of advanced technology with our ability to change the way we fight so that we are able to take advantage of the opportunities afforded by technology. The creation of USACOM and the development of the adaptive force packaging concept represent a major step toward our ability to realize the objectives inherent in the MCP approach. Adaptive force packages must, due to the constraints of time, be assembled largely from "off-the-shelf" components. Within these limitations, USACOM's ability to tailor "force solutions" has been very successful. MCPs, with the freedom to design their own components from scratch, can fully leverage the capabilities of technology, thus creating an opportunity to radically transform current methods and approaches. Time is the key. The MCP process can produce a package in 6 months, 2 years, or 5 years. The time frame affects the nature and magnitude of the change that can be achieved and hence the degree of improvement in capabilities and/or efficiencies that can be realized. Given the broad mission spectrum we face in the coming years, no one solution, in any dimension, is going to work. While we may find some degree of commonality in the nature of our conceptual, doctrinal, and organizational solutions to these mission challenges, it is only after we develop mission-specific solutions and then compare them across the board for common threads and components that the best solutions emerge. Thus, our approach to meeting our current and future challenges must be missionoriented. MCP Process While much has been learned about putting technology to use, the pace of technological advances has quickened to such a degree that current DOD methods of incorporating technology are well behind the power curve. Although acquisition reforms are underway to help reduce the time it takes to go from design to development, they alone will not be sufficient to bring about the changes needed to meet today's mission challenges. 2

Acquisition reforms alone are insufficient because the technology development cycle is out of synch with military strategy development and the elements needed to implement military strategy. Speeding up the technology acquisition cycle without addressing the inertia in the process by which we develop military strategy, concepts, and doctrine just makes these processes more out of synch. What is needed is an approach that synchronizes the development of military strategy with the advances in technology and with the technology insertion process. The speed at which technology can be deployed is only one aspect of the problem. Consider a situation in which new technology can be made instantly available to operational users. How much of the technology's potential will be realized? In point of fact, that answer is that, at best, only incremental improvements will be made, thus only a fraction of the potential utility of the technology will be realized. This is not to say that such improvement would not be useful, or even important. But inescapably, a great deal of the potential of the technology would go unutilized. This scenario would be repeated over and over as the latest technology replaced older technology. Only a series of incremental changes and improvements in operational capability would be achieved.the MCP process address this problem squarely.it provides an opportunity to make radical changes as well, if indeed they are needed. To achieve its goal, the MCP process focuses, synchronizes, and coordinates the efforts of numerous DOD organizations. Components of this MCP process currently exist, but the glue needed to hold these pieces together is weak and the overall process iself is not as well focused as it could be. We are currently weakest in the front end or conceptual phase and in accepting and implementing approaches that require changes in culture. In the Concept Development Phase, groups of individuals with the requisite operational and technical expertise would be brought together in a safe environment with the charter to "think outside of the box." NDU offers an environment particularly well suited to this task. As concepts jell, they would be then subjected to a series of analyses, experiments, and tests to determine if they merit adoption by DOD. It is essential to keep users heavily involved insuring that each aspect of the package [command concepts and organization, doctrine and procedures, force packages, technology and systems, training, and education] is mutually supporting and operationally sound. The Concept Refinement Phase, having a distinctly "hands on" flavor, is essential to facilitating effective communication between the communities. DOD has invested in a full spectrum of models, simulations, testbeds, and instrumented ranges to support the testing of weapons, systems, equipment, doctrine, and concepts of operations and for the training and exercising of our forces. While these valuable resources help to support the assessment and refinement of MCP concepts, several areas of weakness need to be addressed. Most urgently there is a need for explicit and flexible representation of command and control and associated information effects including what has become known as "information war." While work needs to be done at all echelons of command, the most pressing need is at the CINC and JTF levels with emphasis on coalition operations. These 3

models and simulations should be able to accommodate changes in all aspects of the MCP including doctrine, organizations, command approaches, lines of authority, and information flows. Without this capability, these expensive investments would be unable to shed light on the critical issues being addressed by DOD. Equally obvious is that these models and tools no longer can be designed solely to support a particular segment of the community (e.g., training), but need to be built with the idea that they will be used in all phases of the development of MCPs. The last phase of the process requires the implementation of the institutional changes, technologies, and systems that are required by a MCP. At some point, a successful mission capability package concept will have gained sufficient credibility that the need for certain institutional changes will become widely recognized. This point is a critical junction because it is here that the battle with the forces of inertia is joined. Given the knowledge of this battlefield in advance, it is important that the senior civilian and military leadership fully embrace the MCP process and stay abreast of the development of MCP concepts and their progress. The Department of Defense needs to do a mission-by-mission review of how we can meet the challenges we face. Since organizations continually need to accommodate change in the nature of their missions, organizations also need to be structured to facilitate the development of new MCP concepts and their translation into operational capability. Recommendations Develop, as an integral part of the expanded JROC process, Mission Capability Package concepts targeted at the out years of the planning cycle. Use these MCP concepts to drive R&D priorities, to focus the technology insertion, and to guide organizational and force planning and doctrine development. Integrate future visions of command and control, information warfare, and intelligence into a coherent set of concepts and capabilities. Include explicit representation of command and control and information warfare effects in models and simulations. About this Paper Working closely with the operational community and the technologists at ARPA and DISA, the INSS Center for Advanced Command Concepts and Technology (ACT) is pursuing the development of concepts for specific MCPs by bringing together interdisciplinary, joint, and inter-agency teams to explore and assess new command concepts and their implications for other elements of a mission capability package. ACT helps insure that these teams are fully cognizant of both the needs of the operational community and the opportunities that technology can provide as well as its limitations. 4

For more information, contact: Dr. David S. Alberts, Director of CCRP, email contact@dodccrp.org. 5