NCES Program Overview
Rita EspirituNCES Program Manager
2
Components of Net-Centric Warfare
DoDDoDNetNet--CentricCentric
Data StrategyData StrategyInformationInformationAssuranceAssuranceStrategyStrategy
Global ConnectivityGlobal Connectivity(Transformational(TransformationalCommunications)Communications)
Core EnterpriseCore EnterpriseServicesServices(NCES)(NCES)
global connectivity, real-time collaboration and rapid and continuous information exchange
3
NCES Vision
NCES will enable the secure, agile, robust, dependable, interoperable data sharing
environment for DoD where warfighter, business, and intelligence users share knowledge on a global
network that facilitates information superiority, accelerates decision-making, effective operations,
and net-centric transformation.
4
What is NCES?
NCES enables information sharing by connecting people/systems who have information* with people/systems who need information
For people who have information, NCES provides global information advertising and delivery services
For people who need information, NCES provides global services to find and receive information
* Information – data and services
5
The NCES Program is all about Information Sharing
VisibleVisibleIs an information resource discoverable by most users?
Is it available on the network, and are tools readily available to use it?
Can it be intelligibly used? Are the semantics well documented?
Can it be combined or compared with other information?
Is the source, accuracy and currency of the data available to users?
Is the data what users need? Are robust user feedback mechanisms in place to improve it?
AccessibleAccessible
UnderstandableUnderstandable
TrustedTrusted
InteroperableInteroperable
ResponsiveResponsive
NCES enables the DoD Net-Centric Data Strategy
6
NCES Guiding PrinciplesNCES will enable the DoD Net-Centric Data StrategySpeed to deployment – risk management
– Adopt service specifications– Buy performance-based, managed
services from service providers– Create absolutely minimize
Leverage existing assets to manage risk– Use pilots, experiments, early adopters,
proofs of concept to control risk
DISA partnership with the Services– Capability to the Tactical Edge– Include C/S/A in selecting solutions– Participation in pilots, experiments, proofs
of concept
Easy, simple, fast governance– Delegate fielding authority of independent
capabilities to lowest level– Tailored acquisition processes
Business Strategy– Manage a portfolio of services
– Use performance-based service level agreements (SLAs) for managed and adopted services
– Exploit competition for commercially available solutions
– Hosting in GIG or commercial computing nodes as appropriate
– Provide acquisition flexibility by limiting upfront investment
Technical Strategy– Timely access to rapidly evolving
technologies
– Define service interfaces to ensure open industry standards, loosely coupled services, and evolutionary plug and play architecture
– Document interface end-of-life strategy
GN1
Risk Management and ControlRisk Management and Control
Slide 6
GN1 revise and expand to subelementsGerard Nash, 11/4/2005
7
NCES is a key component of the GIG
Enterprise Information Environment Mission Area
Net-CentricEnterprise Services
User/Entity
National Intelligence
Mission Area
Warfighting Mission Area
Expedient COIs
Institutional COIs
Information Exchange
Cross Domain COIs
Con
trol
led
Info
rmat
ion
Exch
ange
Allied/Coalition &
Multinational
Communications Infrastructure Computing Infrastructure
Core information and services anyone can
use
Specialized functional area information and
services
Business Mission Area
Con
trol
led
Info
rmat
ion
Exch
ange
Users
8
NCES is the Foundation for Net-Centric Warfare
Unit of Action
Unit of Employment
FCS Battalion
Unit of Employment
Unit of Action
FCS Battalion
FCS Battalion
Unit of Employment
Source: TRADOC
14 December 2001
NCES Enterprise Collaboration
ConstellationNetFORCEnet
LandWarNet
NCES SOA Foundation
NCES Discovery Services
9
Why NCES? NCES creates a shared information space, increasing decision velocity
NGADIA
NRO NSA
Command& Control
Intelligence Warfighter Business
SituationalAwareness
FocusedLogistics
Data
ForceProtection Mission
Planning
Insufficient synchronous collaboration
JTF HQ
COCOM
Mission Areas: Battlespace Awareness,Force Application, Force Protection
Mission Areas: Focused LogisticsMission Areas:Battlespace Awareness
StateMaritime
Land SoFAir
DepotsLog Bases
TRANSCOM
Industry
Observe
Orient
ActDecide
NGADIA
NRO NSA
Intelligence Warfighter Business
JTF HQ
COCOM
Mission Areas: Battlespace Awareness,Force Application, Force Protection
Mission Areas: Focused LogisticsMission Areas:Battlespace Awareness
StateMaritime
Land SoFAir
DepotsLog Bases
TRANSCOM
Industry
� Mission Planning� Situational Awareness
� Logistics� Force ProtectionShared Space
COICOI
COI COICOI
COICOI
COI
Shared, accessible information = Small OODA Loop
Pre-NCES OODA Loop“As-Is” Environment
ObserveOrient
Act
Post NCES OODA Loop
Decide
“To-Be” EnvironmentStove-piped information = Large OODA Loop
10
How Do We Do It?4 Product Lines
SOA FoundationProvides DOD’s software foundation for interoperable computing
Content Discovery & DeliveryProvides information advertisement, discovery, and efficient delivery
Enterprise CollaborationEnables synchronous communication and file sharing among users
Defense Online PortalProvides personalized, user-defined, web-based presentation
4 Product Lines
Acquiredvia
9 Core EnterpriseServices
11
How Do We Do It?Turning Services into Capabilities
• DOD Web Services Profile• Service Discovery• Service Security• Service Management• Identity Management• Metadata Services• Service Mediation• Machine-to-Machine
Messaging• Web Service Profile Update• Service Discovery: Registry
Integration• Service Security: Attribute
access control• Service Management: Alerts• Web Service Profile Update• Service Discovery: Metadata
Registry Integ.• Service Mgmt: Automated
Failover & Recovery• Service Mediation:
Orchestration• Federated Search Service• Enterprise Catalog Service• Data Source Integration• Content Delivery• Web Conferencing• Instant Messaging
NeededCapabilities
Yield
Acquiredvia
4 Product Lines9 Core
EnterpriseServices
12
How Do We Do It?Overall Acquisition Strategy Features
NCES will acquire managed services, not individual products– Adopt existing standards, specifications, and interface definitions
for services– Acquire as commercially managed service or as a government
managed service• Prefer a commercial- or vendor-managed service with appropriate
contract enforcement provisions
– Service Providers are responsible for full lifecycle support• Buying hardware/software, and integration/development as
appropriate• Operational support (help desk, etc), maintenance• Technology refresh
Initial Increment I approach is to continue to support current capabilities until service providers are in place
– Early Capabilities Baseline (ECB) will be available for early adopters as “operational capability” at Milestone B
– Minimize investment in ECBs
13
How Do We Do It?NCES Program Master Schedule
FY06 FY07
Q1 Q2 Q3 Q4 Q1 Q2 Q3 Q4
Migration
14
What We Have DoneNCES Pilot Environment, Early Adopters & Content Discovery
Pilot Environment– NCES NIPRNET and SIPRNET Pilot Environments declared Open
For Business on 26 September 2005– Access to services in a pre-production environment for users and
service providers/consumers
Early Adopters– Working with Communities of Interest (COI) to utilize NCES
services, develop and employ data taxonomies and associated tools.
– Formal COI’s include:• Intelligence, Surveillance, and Reconnaissance (ISR)• Space Situational Awareness (SSA)
Metadata Tagging– Established Metadata registry to support implementation of DoD
data strategy• 6000 NIPR registered users (people & systems)• 30 SIPR registered users
15
What We Have DoneNCES Metadata Tagging & Collaboration
Content Discovery and Delivery– Acquired commercial technology to speed delivery of large
amounts of information between COCOMs and Agencies (NIPRNET and SIPRNET)
– Automated imagery distribution processes and improved computing performance for operational commands.
Collaboration– Conducted acquisition pilot to validate use of commercially
managed collaboration product– Supported multiple operational requirements w/ Pilot
capabilities• Tsunami Relief Effort• Presidential Inauguration
16
What We Have DoneNavy Activities
Trident Warrior
– Supported demonstration of NCES Content Discovery Core Enterprise Service in early September using service from DECC Columbus OH.
U.S. Navy Operations Center
– Instituted “SMART PULL”, automated web updating and information caching support to the Navy Operations Center in the Pentagon. This vastly speeds up the process of identifying and accessing new or changed information.
USNAVEUR
– Providing Content Discovery services to the Naval component commander in Naples, Italy.
USS Iwo Jima
– Supported Content Delivery capabilities to the USS Iwo Jima during Operation Liberia, freeing critical C2 bandwidth for operational use.
NCES Messaging Support
– Provided NCES messaging and technical support to SPAWARSYSCOM in support of the Net-centric Capability Pilot (NCCP) Demonstration.
17
NCES Aligns with and Supports FORCEnetGoals and Objectives
• DOD Web Services Profile• Service Discovery
CapabilitiesProduct Lines Environment
• Service Security• Service Management• Identity Management• Metadata Services• Service Mediation• Machine-to-Machine
Messaging• Web Service Profile Update• Service Discovery: Registry
Integration• Service Security: Attribute
access control• Service Management: Alerts• Web Service Profile Update• Service Discovery: Metadata
Registry Integ.• Service Mgmt: Automated
Failover & Recovery• Service Mediation:
Orchestration• Federated Search Service• Enterprise Catalog Service• Data Source Integration• Content Delivery• Web Conferencing• Instant Messaging
NeededNCES FORCEnetProvide In Support of
• How do we get there from here?
18
NCES & FORCEnet What are the opportunties available to us?
Provide joint connectivity for Service enterprise architectures
– Facilitate connectivity with Army and Air Force enterprise architectures
– NCES-FORCEnet interoperability will promote “best of breed” evaluations of FORCEnet capabilities for NCES
Provide Increment 1 capability flexible enough to support forward-deployed platforms
– Feedback from Services will assist NCES in meeting forward-deployed KPPs in Increment 2
DEP/JDEP testing opportunities for FORCEnet and NCES interoperability
19
NCES and FORCEnetSome thoughts on how we get there from here…
Consider an MOA between FORCEnet stake holders (RDA CHENG, SPAWAR 05, JRAE) and the NCES program
– NCES is in the final stages of coordinating an MOA with the ArmySOSCOE program
Synchronize Navy NESI development with NCES SOA foundation development
Participate in JRAE experimentation. Utilize JRAE lessons learned while developing the DoD-wide SOA Foundation
Work with NESI, JRAE and Navy Open Architecture Initiative to ensure we are all developing truly interoperable standards and systems.
Facilitate Navy PORs implementation of net-centric data standards (see back up slide)
Seeking Navy Pilot Participants and Early Adopters
Continue Trident Warrior Participation
20
To Get Involved:http://defenseonline.dod.mil
21
SummaryNCES is essential to enabling Network Centric Warfare
Working collaboratively with the DOD community, NCES will provide the infrastructure necessary for SOA implementation and operation across the DOD enterprise.
NCES seeks partnerships with the Navy to advance Net-centricity.
– This conference is an opportunity to collaborate with you and establish a foundation for net centric success.
“A services-oriented architecture facilitates the kind of agility and flexibility we need to achieve true net-centricity.”
– RADM Ken Slaght
Recommended