Maritime Operations Center (MOC) Collaborative … Operations Center (MOC) Collaborative Information Environment (CIE): A Concept Demonstration for Visualizing Requirements Paul North

Maritime Operations Center (MOC) Collaborative Information Environment (CIE):

A Concept Demonstration for Visualizing Requirements

Paul [email protected]

slide 2

Background (1 of 2)

• USFF N9 has requested PACFLT N3/N5 and C4F support for enhancing the April 2010, Maritime Operations Center POM-12 DCR gap 8-05 “Maritime Operations Center lacks a standardized, secure, globally networked Collaborative Information Environment (CIE) infrastructure.”

• The Navy has identified shortfalls in the form of significant variations within and among operational-level C2 processes across the range of military operations, which negatively affect the Navy’s ability to deploy distributed operations capabilities across its core missions

“Distribution Statement A – Approved for public release: distribution is unlimited”

slide 3

Background (2 of 2)

• JHU APL is tasked, under the Sea Trial initiative 11117 to • Focus on processes related to mission planning• Develop a set of requirements based on analysis of those processes

that relate to conducting planning operations in a shared, distributed environment

• Develop a capability for visualizing those requirements in the form of a MOC CIE exemplar to facilitate requirements discussion and vetting

• Interact with and obtain feedback from the Fleets and other Navyorganizations such as PMW-150 regarding this effort


slide 4

What is the Problem?

• How to standardize MOC C2 planning processes and utilize those standardized processes within and among MOCs in a distributed, collaborative environment?

• What are the requirements for doing so and how best to discuss and vet?


slide 5

Approach• Focus effort on the processes related to the

“Conduct Operational Planning” task and in particular on, the mission analysis and COA development sub-tasks

• Model that task and associated workflow• Develop a set of requirements related to that

task and model• Develop a MOC CIE exemplar to represent an

instantiation of those requirements in application form to facilitate requirements discussion and vetting

• Use each spiral of the MOC CIE exemplar as the basis for a “build-upon” set of requirements for a MOC CIE of the future


slide 6

Conduct Operational Planning M&S

Develop a model and simulation of the tasks/workflow that need to be completed for the Conduct Operational Planning task. The model includes:

• Tasks definitions and their relationships• Task timing information/battle rhythm context• Task completion responsibility• Task input and output product definitions

Model Task


slide 7

Conduct Operational Planning M&SConduct Operational Planning M&S

FOPs Swim Lane FPs Swim Lane MHQ CDR Swim Lane MOC CIE BR

Model Task


slide 8

Detailed Model of the Conduct Operational Detailed Model of the Conduct Operational Mission Analysis SubMission Analysis Sub--processprocess

Baseline Sub-model

Alternative Sub-model with Parallel Activities

Model Task


slide 9

Alternative Planning Process for Alternative Planning Process for Conduct Operational Mission AnalysisConduct Operational Mission Analysis

Baseline Sub-model

Alternative Sub-model with Parallel Activities

Model Task


slide 10

Detailed Model of the Conduct Detailed Model of the Conduct Operational Planning ProcessOperational Planning Process• The model elements includes:

• Detailed sub-process and sub-sub-process workflow• Battle Rhythm Events (BRE)• Collaborative Information Environment (CIE)• Information flows to and from the CIE• Depiction of how generated document products support the BRE

• The model and associated simulation can be used to • Analyzing alternative TTPs for the MOC • Analyze the potential impact of process improvement on future MOC

operations• Support a decision support tool by identifying norms for the processes:

provides commander’s with a “head’s up” that a current process may be delayed

Model Task


slide 11

Develop MOCDevelop MOC--CIE Requirements (1 of 2)CIE Requirements (1 of 2)1. The MOC CIE shall be considered as an

essential element of a larger group of systems, which taken collectively, represent a Core Navy Planning Tool

Navy Planning System

1

MOC CIE Navy

Planning System

2


3


4


n

Navy Core Planning Tool

2. The MOC CIE shall allow planners to share their products in a collaborative manner as mission planning evolves

3. The MOC CIE shall allow certain planning products to be developed within the CIE, e.g. MOC Commander’s Intent

4. The MOC CIE shall allow planning products developed externally from echelons above and below to be consumed by the MOC CIE and made available to the MOC planners and others

5. The MOC CIE shall allow plans for one or more missions/sub-missions to be developed as described in 2 and 3 and made available in the CIE to the MOC planners and others

6. The MOC CIE shall allow critical mission/sub-mission events to be identified, synchronized, and made available for display

Define Requirements


slide 12

Develop MOCDevelop MOC--CIE Requirements (2 of 2)CIE Requirements (2 of 2)7. The MOC CIE shall control access to MOC planning products

and operations within the CIE based on user roles and access privileges assigned to those roles

8. The MOC CIE shall provide a capability to dynamically generate and display the status of MOC planning products as they are being developed

9. The MOC CIE shall have its menu structure based on planning work as defined in Navy planning documents such as NWP 5-01, NWP 3-32, and NTTP 3-32.1

10. The MOC CIE shall provide an automated alerting mechanism to the appropriate staff when certain events require attention

11. The MOC CIE shall provide a capability to automatically build briefings and reports using MOC products developed for a given mission/sub-mission

12. The MOC CIE shall be template-driven to the extent possible

Define Requirements


slide 13

MOC CIE CapabilitiesMOC CIE CapabilitiesCapabilities are defined as the generic required behavior of a system.

MANAGE = Capabilities to effectively and efficiently monitor and manipulate the CIE application, as well as its structure and content

SHARE = Capabilities to exchange data, broadcast progress, and maintain situational awareness.

SYNCHRONIZE = Capabilities to correlate events and activity across the CIE.

CONTROL = Capabilities to manage usage of CIE content based on roles, and maintain status.

VISUALIZE = Capabilities for visualizing control structures and content within the CIE.

Cap

abili

ties

CONTROL VISUALIZEMANAGE SYNCHRONIZESHARE

Define Requirements


slide 14

MOC CIE FunctionsMOC CIE FunctionsMOC CIE Functions are defined as specific activities that enable MOC CIE Capabilities that satisfy a set of Requirements. Functions for MOC CIE Capability – MANAGE:CreateApp = Generating an instance of the CIE application

Create = Generating mission/sub-mission structure and content

Open = Retrieving and making available for manipulation mission/sub-mission structure and content

Delete = Erasing mission/sub-mission structure and content

Archive = Saving mission/sub-mission structure and content for historical purposes.

Modify = Changing mission/sub-mission structure and content.

Store = Saving mission/sub-mission structure and content for subsequent access.

Functions for MOC CIE Capability – SHARE:Input = Providing mission/sub-mission content from an external source.

Output = Exposing mission/sub-mission content for consumption by internal and external users.

Report = Making mission/sub-mission content available in structured output format.

Functions for MOC CIE Capability – SYNCHRONIZE:Define Events = Identifying and characterizing mission/sub-mission activities for synchronization and coordination.

Establish & Maintain Dependencies = Identifying, characterizing, and maintaining relationships, including potential conflicts, among mission/sub-mission activities.

Define Requirements


OC CIE FunctionsOC CIE FunctionsCIE Functions are defined as specific activities that enable MOC CIE Capabilities that satisfy a Requirements.

ons for MOC CIE Capability – CONTROL:e Roles = Creating roles, and adding, deleting, and modifying roles assigned to users.

e Privileges = Creating privileges, and adding, deleting, and modifying privileges assigned to roles.

e Status = Dynamically generating and maintaining status of mission/sub-mission content based on content presence ing requirements.

e = Navigating mission/sub-mission structure.

ons for MOC CIE Capability – VISUALIZE:= Displaying mission/sub-mission structures, content, and content status in a web-based graphical user interface


OC CIE Functional ModelOC CIE Functional Model


• Each “mission slice” through the MOC CIE cube represents a set of pages in the CIE supporting a given mission/LOO

• Each cube within a “mission slice”represents one or more content and status pages based on a PDMA/NSOT pairing, e.g. a set of Planning (P) pages at the National (N) level

• Mission page sets and their external links are instantiated dynamically at mission selection time

ional -

tegic -

ctical -

ional -

Plan -

Monitor -Assess -

Direct -

Mis

sion

1 -

Mis

sion

2 -

Mis

sion

3 -

Mis

sion

n -

MOC CIE

velop a MOCvelop a MOC--CIE Exemplar to CIE Exemplar to sualize Requirements: A Future Viewsualize Requirements: A Future View


OC CIE Exemplar StructureOC CIE Exemplar StructureBased on USFF N9 MOC Book Version 4.0 Architecture documents and NWP 5-01, NWP 3-32, and NTTP 3-32.1Being developed with Functional and Organizational View perspectivesFocus is on the Conduct Operational Planning functional and operational views


OC CIE ExemplarOC CIE Exemplarghgh--level Architecturelevel Architecture

ation Environment

ission 2 Functional

Organizational

ission 1

ission 3

FPPlan

Direct

Monitor

Assess

Intel

IM/KM

Targeting

Conduct OP Planning

Develop OEMP

Coord. Ex. Planning

Develop M & S Plans

Conduct Space Plan

Dev. Rec. & Salv. Plan

Provide METOC Sup.

Establish HQ

Coord. Joint Training

Provide Health S. Sup

Provide Personnel Sup

Conduct IO Planning

Develop Initial CCIRs

Develop FFIRs

Anal. OPLAN, COAs, ECOAs

ID Vital Intel by Phase of Op

Collate Req. Intel for OP I&W

Distill Intel Requirements

Rank/Prioritize Intel Reqs.

ID Recommended CCIRs

Approve CCIRs

FOPS

CDR

Conduct OP Mis. Anal.

Develop CCIRs

Develop COAs

Conduct COA WarGm.

Compare COAs

Trans. Fut. OP Plan.

Prepare Plans/ORDs

W>IW Mission 1>Functional>Plan>Conduct OP Planning>FP>Conduct OP Mission Anal>Dev Init. CCIRs

mation Environment

IW>IW Mission 1>Functional>Plan>Conduct OP Planning>FP>Conduct OP Mission Anal>Dev Init. CCIRs

s:

sion Analysis Briefe Informationinformation

mationCommunications With Local, Theater, and National Intel ligence Organizations

ts:

Rs

ded CCIRs

Delete

Description Response Type D isplay Order

quirements ???

Dele te

Inpu t Description Display Order

BattleRhythmDisplay

2400

1500

1800

2100

0000

Battle Rhythm (BR)

Products

Product Status

Briefs

Battle Rhythm Editor

Brief Generator

Status Engine

C CIE Navigation & Status

C CIE Page & Status

Battle Rhythm Display


MOC Collaborative Information Environment

ssionsIW

MCOOther Missions

MCECDRCIS

MIOCLRC

COPSFOPS

FEIM

MAGFP

TrainAdminMETOC

>Views Organizational

Functional

CreateOpen

ArchiveDelete

> > > >Open

Delete


MissionsIW

MCOOther Missions

>Views Organizational

Functional

CreateOpen

ArchiveDelete

> > >>

Open

Delete

Conduct OP PlanningDevelop OEMP

Conduct IO PlanningCord. Ex. Planning

Develop M & S PlansConduct Space Plan

Dev. Rec. & Salv. PlanProvide METOC Sup.

Establish HQCord. Joint Training

Provide Health S. Sup.Provide Personnel S.

>Plan

Direct

Monitor

Assess

Intel

IM/KM

argeting

> Views >

Analyze HHQ Mission

Develop ObjectivesDetermine Specific, Implied,Essential & Follow-On Tasks

State the PurposeIdentify Externally

Imposed LimitationsAnalyze Available Forces And Assets

Determine Critical Factors,COGs, & Decisive Points

Conduct OP Planning FPFOPSCDR

>

Develop Planning Assumptions

Conduct Initial RiskAssessment

Develop ProposedMission StatementPrepare Mission

>

Conduct OperationalMission Analysis >

Analyze HHQ MissionInputs:• HHQ Directives, Plans, Orders, and Guidance• Common Operational Picture (COP)• Warning Order (WARNORD)• Governing Factors• IO Products• Draft Measures of Effectiveness (MOEs)

Outputs:• Broad recommendations about forthcoming military action


tional MOC CIE Detailed Status

Status Colors:• Blue = started• Grey = not started• Red = major

problem• Yellow = minor

problem• Green = no

problem


SSTRATCOMGlobal Strike

Space IO

MOC/JFMCC LOOAnti-Piracy

HADRMission n Mission n

Status

T2 T3 T4 T5 T6 T7 T8 T9 T10 T11 T12 T13T2 T3 T4 T5 T6 T7 T8 T9 T10 T11 T12 T13

Task 3: PTask 3: PTask 4: PTask 4: P


Task 7: PTask 7: P

Direct Status

Task 9: PTask 9: P

Task 8: A


Task 1: ATask 1: PTask 1: ATask 1: ATask 1: P

Task 8: P

Monitor Status

Task 13: PTask 14: P

Task 15: P

Task 12: P

Monitor Status




Current Time: T1 ZETC: T5+10 Z

Plan

Current Time: T1 ZETC: T6+30 Z

Direct

Time: T1 Z1 Z

Monitor

P- ETC

D- ETC

M- ETC

Task 2: ATask 2: P

Task 2: ATask 2: P

Assess StatusTask 16: PTask 16: P

Current Time: T1 ZETC: T11 + 30 Z

Assess

A- ETC

MOC CIE Exemplar“Distribution Statement A – Approved for public release: distribution is unlimited”

tional MOC CIE Planning nchronization

Synchronization across multiple related LOOs showing dependencies among LOO decision points


1 T2 T3 T4 T5 T6 T7 T8 T9 T10 T11 T12 T13

iracyPlanning Tasks

Directing Tasks

Monitor Tasks

Assess Tasks

DP1DP1

DP2DP2

DRPlanning Tasks

Directing Tasks

Monitor Tasks

Assess Tasks

DP1DP1

DP2DP2

on nPlanning Tasks

Directing Tasks

Monitor Tasks

Assess Tasks

DP1DP1

Current Time

Remaining to DP1: 00:00:00Remaining to DP2: 00:00:00

Remaining to DP1: 00:00:00Remaining to DP2: 00:00:00

Remaining to DP1: 00:00:00

USSTRATCOMGlobal Strike

Space IO

MOC/JFMCC LOOAnti-Piracy

HADROther Missions Other Missions

MOC CIE Exemplar“Distribution Statement A – Approved for public release: distribution is unlimited”

onclusions

he purpose of building a MOC CIE exemplar and emonstrating its functionality is to allow war fighters and operators to visualize the requirements associated with a futuristic MOCUse each spiral of the MOC CIE exemplar as the basis for a “build-upon” set of requirements for a MOC CIE of the future

hat visualization capability is expected to add gnificant value to the process of developing an perational MOC CIE because The associated requirements will be well understoodThe requirements can be discussed, vetted, and modified in a rapid, agile fashion


Documents

Maritime Operations Center (MOC) Collaborative … Operations Center (MOC) Collaborative Information Environment (CIE): A Concept Demonstration for Visualizing Requirements Paul North