Multi-Domain Command and Control Proceedings of a Workshop–in Brief (2018) / Chapter Skim
Currently Skimming:
Multi-Domain Command and Control: Proceedings of a Workshop - in Brief
Multi-Domain Command and Control: Proceedings of a Workshop - in Brief
Pages 1-12
The Chapter Skim interface presents what we've algorithmically identified as the most significant single chunk of text within every page in the chapter.
Select key terms on the right to highlight them within pages of the chapter.
From page 1... ...
for which MDC2 systems are necessary and how it differs from traditional joint force and cross-domain operations. As noted by some of the participants, previous incarnations of what has been termed MDO have existed, initially as an evolution on previous forms of combined arms, joint operations, and crossdomain operations.
|
From page 2... ...
(Winston Strategic Management Consulting) A common characterization used by sev- and several other participants pointed out that eral participants emphasized the importance policy challenges regarding data sharing and interoperability remain primary antagonists to achieving horizontal data sharing.
|
From page 3... ...
Winston and other requirements. He suggested they have become participants noted that ownership across the so ubiquitous in USAF systems that they are not USAF enterprise will be critical to ensure sustainrecognized as horizontal requirements today.
|
From page 4... ...
DeMaio commented that there is nisms available to streamline procurement. For currently no official MDO doctrine in the USAF, instance, a lack of a common and consistent and there is a disconnect between space, air, understanding of agile acquisition prevents its and cyber doctrines -- with no common doctrine widespread adoption for acquisition.
|
From page 5... ...
Shared Data Layer and Accessibility -- Brian McLean A key component of the horizontal infrastructure is a common and shared data layer that exists across all systems. As Return to using the term several participants noted, including Kern and Langston in DEVSECOPS instead of just their introductory presentation, for the data to be useful to DEVOPS to ensure security is the operator, it must be accessible, curated, tailored, and factored in from the start.
|
From page 6... ...
As some participants observed, the po tential for modern information technology sys ITERATIVE AND CYCLICAL tems is to dramatically increase the speed in PROCESSES which the C2 OODA loop can be completed The remainder of the key themes and issues of and thus greatly enhance the effectiveness and the workshop were characterized by several speed at which military forces can be controlled participants as inherently iterative and cyclical to respond to an adversary's actions and comprocesses requiring a continuous feedback loop plete its objectives. Saltzman suggested future with recurring iterations, rapid turnarounds, conflicts will be decided by which side obtains and insertions.
|
From page 7... ...
will be critical for curating and processthese lines. Crider described her proposed data ing the massive data flows in a MDC2 system.
|
From page 8... ...
Iterative Systems programs are defined by a list of requirements Several participants noted in order to keep pace that are informed by capability needs, but they with the data flow and analyze data autono- are also "set in stone," as one participant noted. mously in support of warfighter needs, the core To maintain pace, Hamel stressed the need to systems and software will need to undergo con- focus development of MDC2 systems on capastant refresh -- like the data they process, they bilities over set requirements.
|
From page 9... ...
Cloud computing, experimentation can provide constant infor- storage and processing technologies for masmation updates to the iterative development sive data sets, tailored interfaces and cognitive process and help the USAF explore means of agents, and machine learning and artificial inteltechnology insertion and testing. Langston sug- ligence were identified by several participants as gested a tangible first step in prototyping for critical technologies, already ubiquitous in the MDC2 would be to commission a series of rapid commercial sector, that will need to be leverprototypes to test and flesh out infrastructure aged for multi-domain systems.
|
From page 10... ...
NEW ACQ METHODS AND tion. OTAs provide a mechanism for rapid-pro AUTHORITIES FOR ITERATIVE totyping development when certain criteria are DEVELOPMENT OF MDC2 SYSTEMS met, including when the prototype project is directly relevant to enhancing military effectiveCritical to the iterative development process of ness, when competition to the maximum extent MDC2 systems will be rapid acquisition methods is allowed, and when the data from the project and mechanisms.
|
From page 11... ...
offices to avoid some of the bureaucratic hurdles program management, the need to adopt cyexperienced by other acquisition programs by clical and recurring processes in command and focusing on the deployment of prototypes and control, data management, systems developupgrades for existing systems. Several partici- ment, operator/support integration, prototyppants commented on the usefulness of MTAs ing, commercial adoption, and rapid acquisition for the iterative development process critical for methods and mechanisms.
|
From page 12... ...
Kirk Kern, NetApp; Marv Langston, Independent Consultant; Mark Maybury, Stanley Black & Decker; Julie J.C.H. Ryan, Wyndrose Technical Group; Rebecca Winston, Winston Strategic Management Consulting.
|
Key Terms
This material may be derived from roughly machine-read images, and so is provided only to facilitate research.
More
information on Chapter Skim is available.