OPERATIONALIZING FORCEnet (OFn)

1
OPERATIONALIZING FORCEnet (OFn)

• Engineering Speed to Capability
• See What the Fleet SeesMeasure What the Fleet
  Does
• Presented to CDCA Conference
• on 7 November 07 by Phil Charles

Phil Charles, SSCC Chief Engineer
2
Outline

• AssumptionsEngineering Under the Hood
• Engineering ViewpointsCapability vs. Component
• Operational Complexity and Uncertainty
• Definition of Terms
• Principles of FORCEnet and NCW
• Transformation Barrier
• Focus on the Decision Maker and His Tasks
• E2E Engineering Environment with Operational
  Context
• Engineering DOT_LPF
• OFn Strategy
• Summary

3
Assumptions

• We will continue to
• Institutionalize Best Practices/Processes
• Improve E2E Engineering and Collaboration
• Institutionalize Technical Authority and
  Technical Reviews for all projects
• Stress Common, Integrated Solutions and a
  Capability Based Engineering Framework
• Strive towards Capability-Effects-Engagement
  Packages
• Improve Competencies and Processes for Enterprise
  Engineering, Integration and Testing of Services
• Establish an E2E Engineering Environment and
  Contracts
• Continue Naval Dialogue on Excellence in Systems
  Engineering

There is a lot of work to be done as part of the
above engineering initiatives, but this brief is
about our strategy to ensure benefit to the
Warfighter
4
Engineering Viewpoint Capability vs. Component
5
Increasing Complexity and Uncertainty in the
Operational Environment
Catestrophic
Detect Nuclear Device Smuggling Detect
Radiological Device Smuggling Detect Biological
Device Smuggling Detect Chemical Device
Smuggling Provide Early Dissemination of WMD
Sensor detections Provide Comms Satellite
Infrastructure Navigation Backup Systems if
HEMP Provide Afloat Internet Backup if
HEMP Provide CONUS Evacuation Support
for Leadership General Population Provide
Emergency Medical Afloat Hospital Care for Large
Scale WMD Attack Victims
Disruptive
Irregular
Information Ops Defend US Internet Comms
Satellite Infrastructure Provide Backup
Systems GPS Defense Backup Systems Disrupt
Enemy Internet Access Disrupt Enemy Satellite
Comms Disrupt Enemy Navigation Systems Defend
U.S. Power Grid Defend CONUS C2 Infrastructure
Provide Afloat backup C2 Capability
Stability Operations Counter-Insurgency Anti-Terro
rism Iraq Afghan Infrastructure Protection Mili
tary Policing in Occupied Countries
Traditional
Major Combat Ops Anti Submarine Anti Mine
Warfare TAMD Maritime Interdiction Battle Damage
Assessment Close Air Support ISR
6
Definition of Terms

• Mission (JP 01-2)
• 1. The task, together with the purpose, that
  clearly indicates the action to be taken and the
  reason therefore.
• 2. In common usage, especially when applied to
  lower military units, a duty assigned to an
  individual or unit a task.
• Course of action (JP 01-2)
• 1. Any sequence of activities that an individual
  or unit may follow.
• 2. A possible plan open to an individual or
  commander that would accomplish, or is related to
  the accomplishment of the mission.
• Capability (JP 01-2) The ability to execute a
  specified course of action. (May or may not be
  accompanied by an intention.)
• Attribute (CJCSI 31.70.01C) A testable or
  measurable characteristic that describes an
  aspect of a system or capability
• Systems Engineering The ability to decompose a
  complex problem into simple tasks that people can
  execute Dr. James Colvard

6
7
Reality

• Most higher order Capabilities are not truly
  engineered rather they are a sub optimal
  assembly of many component parts
• To perform a mission, operators must continuously
  sort through a multitude of systems, information
  displays and databases to assess the situation
  under ever changing conditions

8
Defining FORCEnet

• Integration of Sea Power 21 and JOINT
  Capabilities
• Integration of Sensors, Weapons, Platforms,
  Networks, C2, Humans to improve the kill chain
  outcome
• FORCEnet Key Attributes
• Secure, Dynamic, Reconfigurable Networks Mobile
  Ad Hoc Networks
• Shared, Common, Data and Applications
  (Distributed Services Independent of Node)
• Outcome
• Distributed, Networked Force Agile, Adaptive,
  Composeable
• New Ways to Fight Better Process, Organization,
  Technology

But, what does the operator see as they perform
their job? And can it be engineered from the
bottom up?
9
FORCEnet and NCW Tenets Principles
Tenets
10
Technologys Transformation Barrier
We are successfully employing new processes and
organizational concepts
New Process Employment
Organizational Innovation
We are innovating and experimenting with new
processes and organizations
Process Innovation
Process Integration
We have integrated existing processes and can
collaborate with each other
Process Innovation
Warfighting Benefit of Information Sharing
Transformation Required
Our applications are integrated and we can share
information seamlessly Common Operational
Picture
Technology Innovation
Application Integration
Data Integration
We have integrated our data
Digital Information Sharing
We are networked and can share digital
information E-Mail Web Chat 9 Line Messages
Voice Connectivity
We can communicate and share information via voice
Degree of Information Sharing
Its not technology but how the Warfighter can
use it!
10
Based on a slide from Vice Admiral Art Cebrowski
and Gartska
11
Our Strategy

• Operationalize FORCEnet!

To Enable JOINT
Measure this
SEA POWER 21
and
MAGTF C2
Improve Operational Effectiveness
Transformation Barrier
Provide this
Good Systems Engineering to Produce Common,
Integrated C4I Solutions
12
Focus on the Decision Makers and Their Tasks !
(Mission Execution)
Speed and Quality of Decision (SQD)
Process and Organizational Agility
Information Ready for Decision
Speed and Quality of Action
See what the operator sees, measure what the
operator does
12
13
Capability Based Engineering Framework
UARC / FFRDC / Industry Labs
UARC / FFRDC / Industry Labs
14
Architecting a SolutionMore than M in DOTMLPF
Function
Sys Node
Op Node
Activity
Info
Data
Org Unit
14
15
OFn Challenge Statement

• Operationalize FORCEnet
• Develop a strategy to demonstrate, measure
  progress, and engineer fast, affordable,
  achievable and beneficial
• What does it look like?
• How to demonstrated FORCEnet Future over FORCEnet
  Today? What will it look like and how will it
  make the operators job easier?
• How to measure it?
• How do we measure progress towards FORCEnet
  Future? How will we measure the value of a new
  technology to the Warfighter
• Is a different engineering and test strategy
  required?
• Determine a thorough, methodical approach to meet
  Fleet needs
• What is the strategy to integrate, test and
  deliver new capability fast, affordable,
  achievable and beneficial

16
Describing FORCEnet Levels
A good technology based roadmap (some capability
and performance inferred), but what does the
operator see and what will be different in each
level about how they perform their jobs?
17
FORCEnet Today

• Legacy systems designed for traditional missions
• Controlled, restricted information sharing via
  tightly coupled interfaces
• Collaboration via CHAT and VTC
• Traditional Command and Control

18
FORCEnet Near-Term

• Information sharing via meta data and context
  based semantic services
• Introduction of services compliment systems
• Coordinated C2

19
FORCEnet Future

• Automated decision support and orchestration of
  warfighting processes
• New Visualization and management of information
• Process innovation
• Collaborative C2 and collaborative planning

20
OFn Strategy

• Provide clarity of purpose. The implementation
  strategy should make clear the nature of the
  capabilities to be developed under the FORCEnet
  initiative. In particular, important points of
  scope need to be made clear in order to guide
  implementation properly.
• Establish an environment and process for the
  continuous capability evolution and innovation.
  As new technical capabilities are explored, new
  concepts for their application will be discovered
  and requirements for additional capabilities will
  be generated. Furthermore, the security
  environment in which the naval forces operate
  will continue to change, necessitating new
  capabilities on the part of the force. Thus, a
  closed-form solution for the development of
  FORCEnet capabilities cannot be specified in
  advancerather, an evolutionary approach is
  necessary.
• Apply an enterprise perspective to materiel
  development. The nature of network-centric
  operation is that all components of the force
  (weapons, sensors, C2 systems, communications,
  and so on) will relate to and draw upon one
  another. Thus, these components cannot be
  designed alone, but only in relation to the other
  components.
• Integrate with joint developments. All recent
  combat operations have been joint, and the extent
  of joint interaction in military operations is
  only likely to increase. Thus, FORCEnet
  operational and materiel capabilities must be
  developed in a joint context.

21
Summary

• The principles of FORCEnet will survive over time
• It can be engineered by seeing what the
  operators see and measuring what the operators do
• It will be  measured in terms of process value
  and organizational value, not in terms of
  technology innovation
• Operationalizing FORCEnet should be fast,
  affordable, achievable and beneficial

22

• Backup Slides

23
Admiral Gauss Technical Objectives (1997) (1 of
2)

• Access to information from a single window
• allocation of C4I/BMC3 functions
• Integrating the C4ISR BMC4I worlds
• Putting ISR into C4ISR
• IT-21, N/MCI implementation architecture

24
SE Environment Progression