C4I Forum Joint Command and Control JC2 and Service Oriented Architecture SOA Discussion

1

• C4I Forum Joint Command and Control (JC2) and
  Service Oriented Architecture (SOA) Discussion

2
JC2 Concept

• JC2 will be a key Contributor to building the DoD
  C2 Domainbut not the only Contributor
• JC2 will use/integrate with GIG Enterprise
  Services
• JC2 will be implemented using a Service Oriented
  Architecture that is monitored and managed
• JC2 will allow Operational Users to link services
  to create managed workflows and processes
• Process-centric, not application centric
• The GCCS Family of Systems will evolve to the JC2
  Family of Capabilities using a spiral process to
  reduce risk
• Federated development
• Pilot service

3
Conceptual JC2
C2Governance Scope
JC2 DOMAIN
Joint Air Space Ops
Joint Fires/Maneuvers
Force Projection
Readiness
Intelligence
Situational Awareness
Force Protection
Others / Additional?
COIs
OtherC2 Programs (CCICCS, C2BMC)
OtherDomains (Log, Finance)
C2 Common Services
JC2 Common Services
Services
GIG Enterprise Services
DoDEnterprise
4
Service Oriented Architecture
Service Oriented Architectures provide greater
capabilities and more flexibility then todays
Platform Oriented Architectures

• A service provider can be
• A source of data to DoD end-users and systems or
  MCPs
• A provider of a value-added service, such as
  multiple source data fusion, track management,
  translation, syndication, or content filtering
• or a provider of a core enabling service for the
  enterprise
• From the consumers point of view services are
• Black Boxes on the network, in the sense that
  their internal implementation is hidden.
• A services inputs are specified and its outputs
  are returned, however, from the consumers point
  of view on the outside, the service
  implementation remains unknown.

Analogous to API for software
5
From the component to a web service
Input Data
Operation
Output Data
6
Service Composability
Higher-Level Service Composed of Lower-Level
Fundamental or Atomic Services
7
Multiple Service Layers
Service Requestor Environment
Realization/Rendering Services
Presentation Services (Client Side)
Presentation Service
Only One Required
Application Service
Data Service
Presentation Services (Server-Side)
Local Database
Application Services
Presentation, application and data layers are
unbundled replaced by service modules--which
expose a well-defined public interface
Data Services
Service Provider Environment
Enterprise Database
End User
JC2 Service Provider
8
NCES and GIG Services
9
GIG Governance
Business Mission Area
Warfighter Mission Area
National Intelligence Mission Area
Governance
Governance
Governance
In work
Installations Environment Domain
Strategic Planning Budgeting Domain
Accounting Finance Domain
Battlespace Communications Systems
Human Resources Management Domain
Acquisition Domain
Logistics Domain
Battlespace Awareness
Force Application
Protection
Focused Logistics
Information Assurance Domain
In work
Core Enterprise Services Domain
Core Enterprise Services Domain
Computing Infrastructure Domain
Communications Domain
Governance
National Intelligence Enterprise Information
Environment Mission Area
Governance
Enterprise Information Environment Mission Area
10
Possible C2 and Military Capability Package
Services
Executive Summary Services
. . .
Decision Making
Force Projection Services
Planning and Conducting Operations
Air/Space Operations Services
Joint Fires Maneuvers Services
Force Projection Services
. . .
MCPs
Sense Making and Battlespace Understanding
Intel Services
Readiness Services
Situational Awareness Services
. . .
JC2
Process Mgt Services
Organizing and Managing Workflow and C2 Processes
User Management Services
Workflow Services
Resource Mgt Services
. . .
C2 Support Services
Notification Services
Unit Alerting Services
Visualization Services
Core C2 Support Tools Functions
. . .
Association Services
Entity Management Services
Workspace Services
Overlay Services
Fusion Services
Organizing and Managing Data and Information
. . .
UDOP
Track Services
Weather Services
Terrain Services
Oceanography Services
Blue Force Services
Measuring and Disseminating Real-World Information
. . .
Discovery Services
Mediation Services
Messaging Services
ESM Services
Security Services
Hosting and enterprise access to information
CES
. . .
11
Implications of Service Oriented Architectures
(1/2)

• Services provide many operational benefits
• Faster delivery of new capabilities
• Assuming the regulatory environment can be
  accommodated
• (Near) zero footprint deployment on user
  platforms
• Assuming robust connectivity to the net
• Improved Backwards Compatibility
• Assuming you can isolate the legacy system
  interfaces
• Competition/best of breed among service providers
  
• Assuming the service developers follow
  architecture and design guidance

12
Implications of Service Oriented Architectures
(2/2)

• Service Providers do not control the end user
  computing environment
• Assuming the organic environment does not drive
  the services to be designed to specific platforms
• Less risk in migrating from GCCS Family of
  Systems to JC2 SOA better suited to supporting
  dynamic workflow management
• Assumes there are proven tools to support dynamic
  workflow management in a open architecture
• Note that theres nothing to do with specific
  technologies here
• Some technologies may help
• But providing you implement these principles,
  anything will do messaging, FTP, e-mail, batch
  tables, etc

13
Discussion

• Where does the MS COI fit in?
• How does the SOA effect the way I do business
  now?
• What is the future of MS in C4I?

14
Food for Thought

• 03F-SIW-121
• Modeling and Simulation Integration with
  Network-Centric Command and Control Architectures
• Tutorial I/ITSEC 2004
• MS in the GIG Environment An Expanded View of
  Distributing Simulation

15
DoD Documents

• Global Information Grid (GIG)
• DoD Directive 8100.1. Global Information Grid
  (GIG) Overarching Policy.The Pentagon,
  Washington, D.C., September 2002
• Net Centric Data Strategy
• DoD, Chief of Information Operations
  (CIO).Department of Defense Net-Centric Data
  Strategy.The Pentagon, Washington, D.C., May 9,
  2003
• DoD Metadata
• DoD, Deputy Assistant Secretary of
  DefenseDepartment of Defense Discovery Metadata
  Specification (DDMS) Version 1.0.The Pentagon,
  Washington, D.C.