NECC Road Show

1
C2 in a Net-Centric World Presentation for the
Villanova NetCentric Conference
Henry M (Hank) Beebe Technical Director, C2
Programs, PEO C2C Defense Information Systems
Agency (DISA)
2
Agenda

• Todays Reality
• The Challenge
• The Answer (the What)
• How We Get There (the How)
• The Benefits

3
Todays Reality

• Our Command and Control Systems have done a
  wonderful job of getting us where we are the
  best combat capable force in the world. But.

The battle is different today
4
Todays Operational Reality
The JC2 Domain
Strategic
Joint Force Commander
Interagency/NGO
Coalition / Allies
Components
5
Todays Operational Reality
23 JTFs and Counting...
Plus Variants
JTF Katrina
MNF-I
TF PALADIN (
TF ODIN
CDAC-PAK
JCC I/A
CJTF HOA
TF TROY
JIACG-CT
ISAF
6
Todays Operational Reality
Battle Command Information Challenges
7
Transforming a Joint Force

• Expand capacity
• Provide capability
• Promote integrated solutions
• Support joint, interagency, and
  multinational operations

NECC NCES
Voice Analog
80s
90s
OIF/OEF
2010
8
The Challenges

• Faster fielding of new C2 capabilities
• Flexible, easy to use C2 capabilities
• Sustainable, maintainable C2 capabilities
• Continuous, end-to-end engagement

9
ADAMS
AFSORT DET
Todays Technical Reality
ALOG
ASORTS
AMP
CFAST
DARWIN
CAMPS
DMS
CFAST
Force Sustainment
COMPASS
DMDC
DARWIN
DRRS
DCAPES
FEDB
GCCS-A
FEDMTC
GCSS
GTN
GCCS-A
FOCUS
GOMERS
ICIS
JADE
JFAST
JFAST
Force
Readiness
F













JRAMS
JRAMS
Force Planning



















MAGTF II
READI
DVT
SORTS
LOGCAT/BCAT
TRMS
JOPES
MAT
AFSATCOM/TIBS
SMS
ADSI
GSORTS
ACOA
Coalition C2
TAG
JFRG II
TCAIMS II
ETMS
WHQ
EPLRS
AFIWC
FNMOC
AF Weather
Gale Lite
Situational
Awareness
D,plk













































GCCS-A
ASAS
GCCS-M
MIDB
COP
GDSS
NGA 5D
Intelligence
NGA IPL
GRIS
Grenadier Brat
Dw















I3
WinJMEM
GTN
Raindrop
IAS
TBMCS
JSTARS
Lateral Tell
UAV GCS
Link 11/16
AMHS
Infra-structure
C2PC
NATO ICC
DCTS
NATO JOIIS
Alerts
WebCOP
DMS
NNSOC
Dwf




















DNS
NRTD
Empire
QTRACS
SBMCS
E-Mail
GPS
SDDC - TEA
Print Services
TBMCS
9
USN Observatory
TDDS
10
Todays Development Reality
Traditional synchronous SE provides capability
all at once at the end
11
The NECC Program

• NECC is a Software Program developing DoDs
  next-generation Command and Control (C2)
  capability
• Single C2 architecture for the Department
• Delivered as loosely coupled, net-centric
  services via software Capability Modules (CMs)
• Planned, developed, delivered in Increments
• Increment 1 Migrates full functionality of GCCS
  Family of Systems (GCCS-FoS) and addresses
  capability gaps
• Adaptive Planning
• Force Projection/Force Visibility
• Intelligence Support
• Shared Situational Awareness
• Cross Functional Capabilities

NECC is ready to begin System Development
Demonstration work
12
Net-Enabled Command Capability
NECC is Transforming Our Command Capability for
the 21st Century
13
Challenges NECC Solves
Warfighter Benefits
NECC
GCCS FoS
Challenge

• Functionality

• Dynamic Capabilities Based Acquisition

• C2 capability user composable and configurable
  flexibility, agility

• Static System/Program Based Acquisition

• Seamless access to information

• Service Oriented Architecture

• Client-Server / Multiple Architectures

• Technology

• Continuous engagement clarity of need and more
  timely/responsive capability process

• Dedicated Joint Combat Capability Developer
  DOTmLPF-P focus

• Multiple Service/System processes ad-hoc
  engagement

• Capabilities Process

• Acquisition Structure

• Single Acquisition Structure/Milestone Decision
  Authority

• Unity of effort and governance improved delivery
  - faster and agile

• Multiple Acquisition Structures/Decision Makers

• Footprint

• Platform Independent

• Simplified installation and deployment process

• Platform Specific

• Data

• Dynamicavailability based on user needs

• Enhanced access to shared data sources

• Staticsystem driven

14
NECC Increment 1 for FY08-11

• Migrates full functionality of GCCS FoS and
  addresses capability gaps
• Adaptive Planning
• Force Projection / Force Visibility
• Intelligence Support
• Shared Situational Awareness
• Force Employment
• Cross-Functional Capabilities

15
Planned NECC Increment 1 CMs(Part 1 of 2)
Adaptive Planning
Force Projection / Force Visibility
Employment Planning
Deployment Mgt.
Execution Mgt.
Global Force Readiness
Capability Visibility
Force Structure
DISA
4.1.25 4.1.28
1.2.2 1.2.3 1.2.10
Employment Execution
1.1.1 1.1.6 1.1.12
1.3.1
1.3.2 1.2.4 1.3.9
2.1.1 2.1.2 2.1.3
Strategic Guidance
Deployment Plan Management
Readiness Assessmentand Analysis
Force Structure Management
Capability Based Force Options
CDP 5,21
CDPs 8,20,21,22
CDP 15,21
DISA
DISA
1.1.10 1.1.11 1.1.14 1.2.7
1.1.15 1.1.16 1.1.17 1.2.5 1.2.6
CDPs 10,14
CDPs 10,18
CDP 11
Deploymentand Distribution Visibility
Sustainment Estimation
Concept,COA EffectsDevelopment
1.1.5 1.1.7
TBD
TBD
TBD
Emergent Capability Visibility
Emergent Global Force Readiness
Emergent Force Structure
CDP 19,21
CDPs 7,19,21
CDPs 15,16,17,21
1.2.4 1.2.8 1.2.9
Navy
CDP TBD
Transportation Management
CDP TBD
1.1.3 1.1.4 1.1.8
CDP TBD
4.1.13
Plan Development Refinement
Joint Force Synchronization
Mission Applications
CDP 18,21
CDP 20,21
CDP 1
TBD
TBD
Emergent Employment Planning
Emergent Deployment Management
Emergent Execution Management
TBD
CDP TBD
CDP TBD
CDP TBD
DISA
DISA
DISA
1.3.1
1.3.5 1.3.6
Joint Force Structure Data
Force Locationand Availability Data
1.1.2
1.2.1
2.1.4 2.1.5 2.1.6
EmploymentPlan Data
Deployment Data
JointReadiness Data
CDPs 10,14
CDPs 10,14
CDP 15,21
CDP 20,21
CDPs 10,12
1.3.1
Army Force Structure Data
1.1.9 1.1.13 1.3.7
Force Apportionment Data
Army
2.1.4 2.1.5 2.1.6
ArmyReadiness Data
Data Capability Modules
CDPs 10,14
LEGEND
CDPs 10,13
Navy
NECC Inc 1 CM interim release in IOC
CDPs 10,12
1.3.1
Navy Force Structure Data
NECC Increment 1 CM in FOC
NavyReadiness Data
2.1.4 2.1.5 2.1.6
CDPs 10,14
X.X.X
Relevant NECC App. D CDD Req.
1.3.1
USAF Force Structure Data
CDPs 10,12
CDP X
Relevant JFCOM NECC CDP
2.1.4 2.1.5 2.1.6
Comp
TD Phase CM/Lead Component Dev.
USAFReadiness Data
CDPs 10,14
FY08 CM Investment
1.3.1
USMC Force Structure Data
CDPs 10,12
CDPs 10,14
16
Planned NECC Increment 1 CMs(Part 2 of 2)
Intel
SituationalAwareness
ForceProtection
C2 Cross- Functional
DIA/DISA
4.1.1 to 4.1.12 4.1.17 to 4.1.22
Redirection
3.3.7 3.3.9
CollectionManagement
GlobalUDOP
TBD
TBD
CDP 24
TBD
Emergent Force Protection
TBD
Emergent Ground Ops
Emergent Maritime Ops
Emergent Air/Space Ops
Geospatial Rendering
CDP 9
CDPs 1,2,3,4,5
CDP TBD
CDP TBD
CDP TBD
CDP TBD
TBD
4.1.1 to 4.1.13 4.1.17 to 4.1.22
Emergent Intel
AssociationManagement
CDP 1,2,4,6,25
Analysis and Reporting
Mission Applications
CDP TBD
CDPs 1,2,3,5
CDP 24
Emergent SA Mission
TBD
USAF
Orchestration
CDP TBD
USAF
DISA/Navy
CDP 24
DIA/DISA
4.1.5 4.1.6 4.1.7
5.1.1 5.1.7 4.1.9
Army/MDA
Air TaskOrder Data
4.1.2 4.1.4 4.1.9 4.1.29
Red Track Data
ArmyManeuver Data
3.2.5 4.1.16
ImageryData
4.1.148.1.3
MissileDefense and Warning
C2 Collaboration
CDPs 1,3
CDP 2
Navy/USAF
CDP 2
CDP 2
USAF
CDP 25
4.1.12
Weather Data
5.1.1 5.1.55.1.7 4.1.9 4.1.13
Air SpaceManagement Data
CDPs 1,6
6.5.36.5.4 4.1.9
User Management
ArmyFires Data
CDP 2
Data Capability Modules
Army
4.1.1 4.1.2 4.1.3 4.1.4
Blue ForceGround Data
CDP 2
CDP 2
CDP 25
Navy
5.1.11 4.1.9 4.1.13 4.1.18
Air MissionPlanning Data
LEGEND
CDP 1
C2 Messaging
4.1.1 4.1.2 4.1.3 4.1.4
NECC Inc 1 CM interim release in IOC
Blue ForceMaritime Data
CDP 2
NECC Increment 1 CM in FOC
CDP 24
CDP 1
4.1.1 4.1.2 4.1.3 4.1.4
X.X.X
Relevant NECC App. D CDD Req.
Emergent C2 Cross Functional
Blue ForceAir Data
Relevant JFCOM NECC CDP
CDP X
CDP 1
Comp
TD Phase CM/Lead Component Dev.
CDP TBD
TBD
Emergent SA Data
Milestone C candidate CM (Apr-08)
FY08 CM Investment
CDP TBD
17
CMs Planned for FY08
Functional Area Capability Module Functionality April 2008 Initial Delivery Sep 2008 Initial Delivery
Shared Situational Awareness Visualization User Definable Operational Picture User definable common operational picture (UDOP) and other Situational Awareness (SA) data feeds Formerly known as Global UDOP but its name changed to more accurately reflect its primary mission of being the users graphical front end to visualization and control of SA data
Shared Situational Awareness Association Management Manage the numerous SA data feeds to form a synchronized information display providing operational context to support decision making User tailorable to their individual requirements
Shared Situational Awareness Red Force Data Net access to Red/Hostile, White/Neutral, and Gray/Unknown data from various ISR sources and data feeds.
Shared Situational Awareness Blue Force Ground Data Net access to Joint Blue Force Situational Awareness - Blue Force Tracker system and other data feeds, includes battlefield geometries/overlays, projected blue force data, and blue force history data.
Shared Situational Awareness Weather Data Net access to Navy and Air Force weather and oceanographic data - supplies meteorological information for shared situational awareness.
C2 Cross Functional User Management Net-centric security and user administration functions.
C2 Cross Functional Redirection Running CMs on alternate platforms based on operational status and connectivity - supports disconnected users, intermittent connectivity, and limited connectivity. Supports load balancing of services across multiple platforms to improve performance and response time
C2 Cross Functional Geospatial Rendering Supports multiple open system standard map display systems, decoupling geospatial data from its presentation which makes geospatial data more usable
C2 Cross Functional Orchestration Allows users to discover and compose applications and data services into an end-to-end process to support specific, changing, or emerging mission objectives. Allows users to model their mission process to automatically compose the suite of application and data services necessary to do the users mission in an optimal manner.
C2 Cross Functional C2 Messaging Service-to-service messages that supports operating in disconnected, intermittent and limited (DIL) communications environment. Net access to legacy military messaging systems currently in operation.
Adaptive Planning Employment Plan Data Net access to employment data to support deliberate / contingency planning, and dynamic operations on a rapid update cycle.
Force Proj/ Force Vis Joint Readiness Data Net access to force readiness data to support Force Projection and Force Visibility assessment and planning for sourcing, mobilization, etc.
CDP 1
18
Essential C2 Architecture
C2 Applications/Tools NECC, SERVICES, COCOMS,
ETC
Interfacing Services DISA NECC
Enterprise Services DISA NCES
Data Interface Services REGISTRIES
Data COCOMS, AGENCIES, ETC
Transport Services DISA CS
Network Environment
19
Joint Combat Capability Developer (JCCD)

• Action arm of JC2 CPM to execute operational
  sponsorship and capability development
  responsibilities
• Dynamic direct coupling of warfighter operational
  capability requirements to the capability
  material developer
• End-to-end, warfighter engagement (concept
  development through fielding and sustainment)
• DOT_LPF-P integration focus
• USJFCOM-led with active
  
  participation by
• Joint Staff
• Combatant Commands
• Services
• Agencies

Engaged throughout the process capability need
identification, capability development,
testing/certification, and fielding
20
Federated Development Certification Environment
(FDCE)
Pioneering New Solutions to Legacy Problems
Warfighter/UserCommunity
Test Evaluation/Certification Community
Increasing Capability Maturity
Capability modules
Requirements DOT_LPF-P Community
Materiel Provider/Sustainment Community
Capabilities Enter Based on Level of Maturity
21
Capability Brokers

• Concept
• An agent
• In search of non-traditional DOD providers,
  developers, etc.
• Identify candidate innovative technologies for
  potential inclusion.
• OCOI provision
• Status
• RFI issued responses received from wide variety
  of sources
• Internal evaluation and discussion underway
• May result in an RFP during FY-08

22
Joint Combat Capability Development
23
NECC Development Process
NECC provides continuous capability to the
Warfighter
JCCD Process
NECC SE AsynchronousDevelopment, Test, and
Delivery
Deployment
CM Z
CM Y
CM X
CM W
Warfighters, Developers, Testers Certifiers
Engaged End-To-End
CM Deployment
Capability Definition Package
CM Deployment
CM Deployment
CM Deployment
Develop / Certify / Test
Effective employment requires re-engineering the
development process
24
Governance Process

• Documents
• NII-approved Program Terms of Reference
• MOAs w/Service PEOs for GCCS FoS and NECC

DepSecDef Advisory WG
NECC JPEO
Program Termsof Reference GCCS Management
Transfer Plan
NECC ASG PMCE Steering Group Systems Engineering
Integration WG
C2 Capability Integration Board
PE58

MOAs

• Services DISA POMfor NECC
• DISA POMs JPEO Allocates Development Funds to
  Services/Agencies
• Services POM andmaintain responsibility of
  Implementation Funds
• Incentivize Development efforts in
  Services/Agencies

USJFCOMJC2 Capability Portfolio Manager
Ops Sponsor
NECC JPMO
NCES PKI JTEM
JEDS JSIC JDCAT Tool JCTDs
(JCRE, ASAP)
USJFCOMJCCD CDD JCCD Management Plan

CDD JCCD Management Plan
PMDT JST Test WIPT
Acq WIPT IA WIPT Cost WIPT
Service PEOsGCCS FoS NECC
Partnerships
Agreements
Fora
25
Limiting Factors of Information Sharing

• Historically, Programs have defined their own
  vocabularies and information exchange schemas,
  limiting the amount of understandable information
  that can be shared
• Communities of Interest (COI) have helped by
  developing common vocabularies within the COI to
  enable increased information sharing however,
  sharing information outside the COI is still a
  challenge
• Development of COI vocabularies has demonstrated
  that a common, minimal set of words span
  community vocabularies agreeing to the
  definition of these words will help
  cross-community information sharing

26
Universal Core To Enable Info Sharing

• Universal Core (UCore) - a joint DoD/IC effort to
  agree on a common baseline standard vocabulary to
  enable information exchange
• The Universal Core
• Reusable method and set of artifacts to improve
  the sharing of information fundamental to most
  operational processes
• Provides simple starting point for teams to
  extend as they respond to complex data sharing
  opportunities
• Reduces mediation / translation between systems
  for a small number of the most valuable
  operational concepts

27
DoD - IC Universal Core Data Schema

• A universal core data schema that enables
  information sharing
• Ways to describe what, when, where types of
  information
• Minimal set of terms in the core
• Agreed to by DoD and Intel community
• Appropriate use of open and Government standards
• Extensible by COIs and systems as needed
• Version 1.0 release in Oct 2007
• Version 2.0 will expand to include DOJ and DHS

28
Leading Change

• NECC is a Pathfinder
• JOINT organization with service and agency CPMOs
  (Army, Air Force, Navy, Marines, DNI, and MDA)
• LEVERAGING current and emerging technologies
• Procurement and production of NECC capability
  development will be done THROUGH the services
• INCENTIVIZE the Services
• Teaming with WARFIGHTING, TESTING, and
  CERTIFICATION communities

29
Key Takeaways
Focus Areas Current NECC
Requirements Fixed Warfighter can reprioritize
Processes (Development, Test, IA) Sequential (Service specific) Parallel Joint Services
Develop Strategy Large Block 18 months Small, discrete capabilities as soon as ready Adoption of existing capabilities Incentives
Warfighter Engagement - Tester - Security Certifier Periodic on-looker Continuous part of the team
C2 Solution Service Specific/ non-interoperable Built by each Service Joint Built by all w/ incentives for good performance
Transforming C2 for the Warfighter
COMBO
30
(No Transcript)