NCES Program Overview. Rita Espiritu NCES Program Manager

Transcription

1 NCES Program Overview Rita Espiritu NCES Program Manager

2 Components of Net-Centric Warfare DoD Net-Centric Data Strategy Information Assurance Strategy Global Connectivity (Transformational Communications) Core Enterprise Services (NCES) global connectivity, real-time collaboration and rapid and continuous information exchange 2

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. 3

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 4

5 The NCES Program is all about Information Sharing Visible Accessible Understandable Trusted Interoperable Responsive Is 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? Is the source, accuracy and currency of the data available to users? Can it be combined or compared with other information? Is the data what users need? Are robust user feedback mechanisms in place to improve it? NCES enables the DoD Net-Centric Data Strategy 5

6 NCES Guiding Principles NCES will enable the DoD Net-Centric Data Strategy Speed 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 GN1 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 Risk Management and Control 6

7 Slide 6 GN1 revise and expand to subelements Gerard Nash, 11/4/2005

8 NCES is a key component of the GIG User/ Entity Users Business Mission Area Warfighting Mission Area National Intelligence Mission Area Allied/ Coalition & Multinational Controlled Information Exchange Institutional COIs Expedient COIs Cross Domain COIs Information Exchange Net-Centric Enterprise Services Communications Infrastructure Computing Infrastructure Enterprise Information Environment Mission Area Controlled Information Exchange Specialized functional area information and services Core information and services anyone can use 7

9 ConstellationNet NCES is the Foundation for Net-Centric Warfare NCES Enterprise Collaboration FORCEnet 8 LandWarNet Unit of Employment Unit of Employment Unit of Action Unit of Employment FCS Battalion Unit of Action FCS Battalion FCS Battalion Source: TRADOC 14 December 2001 NCES Discovery Services NCES SOA Foundation

10 Why NCES? NCES creates a shared information space, increasing decision velocity As-Is Environment Intelligence Warfighter Mission Areas: Battlespace Awareness Business Mission Areas: Battlespace Awareness, Force Application, Force Protection Pre-NCES OODA Loop Mission Areas: Focused Logistics Observe COCOM DIA TRANSCOM NGA NRO Maritime NSA State Land SoF Air Force Protection Situational Awareness Orient Depots Log Bases JTF HQ Mission Planning Industry Command & Control Focused Logistics Data Act Decide Insufficient synchronous collaboration Stove-piped information = Large OODA Loop To-Be Environment Intelligence Warfighter Business Mission Areas: Battlespace Awareness, Force Application, Force Protection Mission Areas: Battlespace Awareness Post NCES OODA Loop Mission Areas: Focused Logistics Observe Orient COCOM DIA TRANSCOM NGA JTF HQ NRO NSA Maritime COI COI COI State Land SoF Air COI COI Mission Planning Situational Awareness Depots Log Bases Shared Space Act COI COI COI Industry Decide Logistics Force Protection Shared, accessible information = Small OODA Loop 9

11 How Do We Do It? 4 Product Lines 9 Core Enterprise Services 4 Product Lines Defense Online Portal Provides personalized, user-defined, web-based presentation Acquired via Enterprise Collaboration Enables synchronous communication and file sharing among users Content Discovery & Delivery Provides information advertisement, discovery, and efficient delivery SOA Foundation Provides DOD s software foundation for interoperable computing 10

12 How Do We Do It? Turning Services into Capabilities 9 Core Enterprise Services Acquired via 4 Product Lines Yield Needed 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 11

13 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 12

14 How Do We Do It? NCES Program Master Schedule FY06 FY07 Q1 Q2 Q3 Q4 Q1 Q2 Q3 Q4 Migration 13

15 What We Have Done NCES 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 14

16 What We Have Done NCES 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 15

17 What We Have Done Navy 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. 16

18 NCES Aligns with and Supports FORCEnet Goals and Objectives NCES Product Lines Provide Needed 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 In Support of FORCEnet Environment How do we get there from here? 17

19 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 18

20 NCES and FORCEnet Some 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 Army SOSCOE 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 19

21 To Get Involved: 20

22 Summary NCES 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 Netcentricity. 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 21

23 Contact Us! Internet: DefenseOnline.dod.mil 22