Capability management

Last updated

Capability management is a high-level management function, with particular application in the context of defense.

Contents

Capability management aims to balance economy in meeting current operational requirements, with the sustainable use of current capabilities, and the development of future capabilities, to meet the sometimes competing strategic and current operational objectives of an enterprise. Accordingly, effective capability management:

In military contexts, capabilities may also be analysed in terms of Force Structure and the Preparedness of elements or groupings within that Force Structure. Preparedness in turn may be analysed in terms of Readiness and Sustainability.

In both the military and commercial contexts, net-centric operations and related concepts are playing an increasingly important role in leading and driving business transformation, and contemporary capability management needs to have close regard of those factors. The level of interoperability, both technical and organisational/social, is a critical determinant of the net-centric capability that is able to be realised and employed.

Capability management topics

Capability

Enterprises consist of a portfolio of capabilities that are used in various combinations to achieve outcomes. Within that portfolio, a capability will be transient unless managed and maintained over time. Therefore, a typical capability lifecycle spans needs, requirements, acquisition, in-service and obsolescence/disposal phases.

While a highly developed management discipline within several national military organisations, the concepts, principles and practices of capability management are readily adaptable and effective for application in the strategy and operations of many other enterprises.

Defining capabilities in the US military

The Joint Capabilities Integration and Development System Manual, CJCSM [ clarification needed ] 3170.01, states that definitions of identified capabilities must satisfy two rules: [1]

Capabilities described with architectures. Capabilities Described with Architectures.jpg
Capabilities described with architectures.

Capabilities are organized around concepts of operations (CONOPS), which describe how a specified course of action is to be executed. The ability to execute the specified course of action depends on many factors and the relationship between those factors. Capabilities can be described as one or more sequences of activities, referred to as operational threads. The threads are composed of a set of activities that can be grouped to form the basis for a mission area architecture. The architecture then provides the structure for defining and understanding the many factors that impact the capability. The figure illustrates this sequence of relationships. [1]

The Navy has also endorsed using architectures to understand and analyze capabilities and their associated requirements. The Navy performs this architecture analysis based on the concept of Mission Capability Package (MCP). The intent is to consider all of the factors that contribute to the desired mission capability as an integrated system. An MCP is defined as "a task-oriented bundle of CONOPS, processes, and organization structures supported by networks, sensors, weapons, and systems, as well as personnel training and support services to sustain a core naval capability." The MCP and associated analysis then provide the basis for acquisition decisions. [1]

Capability management considerations

Due to the complexities of system-of-systems integration, interoperability, and the dynamic nature of operations, capability management is greatly assisted by modelling and simulating realistic strategic scenarios and contexts, in order to inform business cases and decision-making. Through those considerations and practices, the enterprise and its performance can be continuously assessed and projected into the future.

Well executed capability management therefore clearly informs strategic and operational decisions, and aids in the development of diverse but well-considered strategic and operational options, so they are readily available off-the-shelf. This should also endow significant agility to an enterprise, providing enhanced "contingency capital" and risk mitigation.

Capability management therefore centers on:

Capability management frameworks

The interlinking functions and activities of the enterprise may be defined under several best-practice paradigms or frameworks, such as the Balanced Scorecard, or the US Department of Defense Architecture Framework, The Ministry of Defence Architecture Framework, The Open Group Architecture Framework and Zachman's Framework for Enterprise Architecture. In other words, capability is typically managed and assessed with regard to several dimensions or integrative elements.

DOTMLPF

The US military analyses its capabilities in the dimensions of "DOTMLPF", being:

Interoperability concerns all capability dimensions, therefore NATO has extended the seven capability dimensions by the cross-cutting aspect of Interoperability and uses the acronym "DOTMLPF-I".

Defence Lines of Development

The UK Ministry of Defence uses a similar breakdown of Defence Lines of Development as follows:

The mnemonic "Tepid oil" is used to remember these. Though not a Defence Line of Development in itself, the unifying theme of 'interoperability' is considered to ensure a holistic approach to capability integration.

The UK Ministry of Defence cites Interoperability as an overarching theme that must be considered when any Defence Line of Development is being addressed.

Fundamental Inputs to Capability

The Australian Defence Organisation also analyses its capabilities in similar dimensions - the so-called Fundamental Inputs to Capability. These are:

These Fundamental Inputs to Capability must be integrated and managed within a defined or constraining financial envelope in order to realise and sustain a capability: a deficiency in any one adversely impacts the whole.

See also

Related Research Articles

Interoperability is a characteristic of a product or system to work with other products or systems. While the term was initially defined for information technology or systems engineering services to allow for information exchange, a broader definition takes into account social, political, and organizational factors that impact system-to-system performance.

Enterprise architecture (EA) is a business function concerned with the structures and behaviors of a business, especially business roles and processes that create and use business data. The international definition according to the Federation of Enterprise Architecture Professional Organizations is "a well-defined practice for conducting enterprise analysis, design, planning, and implementation, using a comprehensive approach at all times, for the successful development and execution of strategy. Enterprise architecture applies architecture principles and practices to guide organizations through the business, information, process, and technology changes necessary to execute their strategies. These practices utilize the various aspects of an enterprise to identify, motivate, and achieve these changes."

<span class="mw-page-title-main">Enterprise integration</span>

Enterprise integration is a technical field of enterprise architecture, which is focused on the study of topics such as system interconnection, electronic data interchange, product data exchange and distributed computing environments.

<span class="mw-page-title-main">Department of Defense Architecture Framework</span> Enterprise architecture framework

The Department of Defense Architecture Framework (DoDAF) is an architecture framework for the United States Department of Defense (DoD) that provides visualization infrastructure for specific stakeholders concerns through viewpoints organized by various views. These views are artifacts for visualizing, understanding, and assimilating the broad scope and complexities of an architecture description through tabular, structural, behavioral, ontological, pictorial, temporal, graphical, probabilistic, or alternative conceptual means. The current release is DoDAF 2.02.

<span class="mw-page-title-main">NetOps</span>

NetOps is defined as the operational framework consisting of three essential tasks, Situational Awareness (SA), and Command & Control (C2) that the Commander (CDR) of US Strategic Command (USSTRATCOM), in coordination with DoD and Global NetOps Community, employs to operate, manage and defend the Global Information Grid (GIG) to ensure information superiority for the United States.

The British Ministry of Defence Architecture Framework (MODAF) was an architecture framework which defined a standardised way of conducting enterprise architecture, originally developed by the UK Ministry of Defence. It has since been replaced with the NATO Architecture Framework.

The Joint Capabilities Integration and Development System (JCIDS), is the formal United States Department of Defense (DoD) process which defines acquisition requirements and evaluation criteria for future defense programs. JCIDS was created to replace the previous service-specific requirements generation system that allowed redundancies in capabilities and failed to meet the combined needs of all US military services. In order to correct these problems, JCIDS is intended to guide the development of requirements for future acquisition systems to reflect the needs of all four services by focusing the requirements generation process on needed capabilities as requested or defined by one of the US combatant commanders. In an ideal implementation of the JCIDS process, regional and functional combatant commanders give early and continuous feedback into the acquisition and sustainment processes to ensure their current and evolving requirements are known and met.

Enterprise systems engineering (ESE) is the discipline that applies systems engineering to the design of an enterprise. As a discipline, it includes a body of knowledge, principles, and processes tailored to the design of enterprise systems.

LandWarNet (LWN) is the United States Army’s contribution to the Global Information Grid (GIG) that consists of all globally interconnected, end-to-end set of Army information capabilities, associated processes, and personnel for collecting, processing, storing, disseminating, and managing information on demand supporting warfighters, policy makers, and support personnel. It includes all Army and leveraged Department of Defense (DOD)/Joint communications and computing systems and services, software, data security services, and other associated services. LandWarNet exists to enable the warfighter through Mission Command, previously described as Battle Command. Other U.S. service equivalent efforts to LandWarNet include the Navy's "FORCEnet" and the Air Force's "C2 Constellation."

Human Factors Integration (HFI) is the process adopted by a number of key industries in Europe to integrate human factors and ergonomics into the systems engineering process. Although each industry has a slightly different domain, the underlying approach is the same.

DOTMLPF is an acronym for doctrine, organization, training, materiel, leadership and education, personnel, and facilities. It is used by the United States Department of Defense and was defined in the Joint Capabilities Integration Development System, or JCIDS Process as the framework to design what administrative changes and/or acquisition efforts would fill a capability need required to accomplish a mission. Because combatant commanders define requirements in consultation with the Office of the Secretary of Defense (OSD), they are able to consider gaps in the context of strategic direction for the total US military force and influence the direction of requirements earlier in the acquisition process, in particular, materiel.

Military capability is defined by the Australian Defence Force as "the ability to achieve a desired effect in a specific operating environment". It is defined by three interdependent factors: combat readiness, sustainable capability and force structure.

<span class="mw-page-title-main">Enterprise life cycle</span> Process of changing an enterprise over time

Enterprise life cycle (ELC) in enterprise architecture is the dynamic, iterative process of changing the enterprise over time by incorporating new business processes, new technology, and new capabilities, as well as maintenance, disposition and disposal of existing elements of the enterprise.

<span class="mw-page-title-main">Generalised Enterprise Reference Architecture and Methodology</span>

Generalised Enterprise Reference Architecture and Methodology (GERAM) is a generalised enterprise architecture framework for enterprise integration and business process engineering. It identifies the set of components recommended for use in enterprise engineering.

Live, Virtual, & Constructive (LVC) Simulation is a broadly used taxonomy for classifying Modeling and Simulation (M&S). However, categorizing a simulation as a live, virtual, or constructive environment is problematic since there is no clear division among these categories. The degree of human participation in a simulation is infinitely variable, as is the degree of equipment realism. The categorization of simulations also lacks a category for simulated people working real equipment.

Capability management is the approach to the management of an organization, typically a business organization or firm, based on the "theory of the firm" as a collection of capabilities that may be exercised to earn revenues in the marketplace and compete with other firms in the industry. Capability management seeks to manage the stock of capabilities within the firm to ensure its position in the industry and its ongoing profitability and survival.

Cyber Quest is an annual U.S. Army event held at Fort Gordon in which participants assess new technologies against documented Cyberspace, Electronic Warfare (EW), and Signal operational requirements. Cyber Quest is sponsored by the Cyber Battle Laboratory (CBL) of the Cyber Center of Excellence (CCOE)

<span class="mw-page-title-main">Federated Mission Networking</span>

Federated Mission Networking (FMN) is a significant initiative to help ensure interoperability and operational effectiveness of the North Atlantic Treaty Organization, it is a key contribution to the Connected Forces Initiative, helping Allied and Partner forces to better communicate, train and operate together. This includes the NATO Command Structure as well as the NATO Force Structure. The purpose of FMN is ultimately to support Command, Control, Communications, Computers, Intelligence, Surveillance and Reconnaissance (C4ISR) and decision-making in operations by enabling a rapid instantiation of mission networks. Including the NATO Command Structure, 37 nations have joined the FMN initiative as so called "FMN Affiliates" and work together under the FMN Framework Process to coordinate the design, development and delivery of operational and technical capabilities required to conduct net-centric operations. Each development increment is referred to as an "FMN Spiral". The respective requirements, architecture, standards, procedural and technical instructions are documented in so called "FMN Spiral Specifications". FMN Spiral Specifications are based on well known standards and best practices, hence supported by most off-the-shelf products and vendor neutral. TACOMS standards and profiles specify a common, technology and topology independent network interoperability layer for federated mission networks. There is also a rolling 10-year FMN Spiral Specification Roadmap of the envisioned future capabilities. At the same time, the Coalition Interoperability Assurance and Validation (CIAV) process ensures that current interoperability issues are being identified and fed back into FMN capability development.

<span class="mw-page-title-main">Structure of the Common Security and Defence Policy</span> European Union military structure

This article outlines the present structure of the European Union's Common Security and Defence Policy (CSDP), a part of the Common Foreign and Security Policy (CFSP) based on articles 42–46 of the Treaty on European Union (TEU). Article 42.2 of TEU states that the CSDP includes the 'progressive framing' of a common Union defence policy, and will lead to a common defence, when the European Council of national heads of state or government, acting unanimously, so decides.

<span class="mw-page-title-main">NATO Science and Technology Organization</span>

The NATO Science and Technology Organization (STO) is the primary NATO organization for Defence Science and Technology. Its intent is to maintain NATO's scientific and technological advantage by generating, sharing and utilizing advanced scientific knowledge, technological developments and innovation to support the Alliance's core tasks.

References

  1. 1 2 3 4 Department of Defense (2003). DoDAF 1.0 Deskbook Archived 2007-09-27 at the Wayback Machine 15 Aug 2003.