Presentation is loading. Please wait.

Presentation is loading. Please wait.

Agenda NCES Overview NCES Production Capabilities

Similar presentations


Presentation on theme: "Agenda NCES Overview NCES Production Capabilities"— Presentation transcript:

0 NCES Capabilities Overview
JA0074C.0 BM6710 AL 4/19/ :50:43 AM4/19/ :50:43 AM Marcom NCES Capabilities Overview PEO-GES Version 08.4 UNCLASSIFIED

1 Agenda NCES Overview NCES Production Capabilities
JA0074C.1 BM6710 AL 4/19/ :50:43 AM4/19/ :50:43 AM Marcom Agenda NCES Overview NCES Production Capabilities User Access: Defense Knowledge Online (DKO) Collaboration Metadata Registry (MDR) Federated Search Enterprise Catalog Machine-to-Machine Messaging Service Discovery Service Security Steps to use NCES Capabilities NCES Lessons Learned Additional NCES References

2 NCES Overview NCES is an enabler for information sharing within the DoD as well as with federal, allied, coalition and multinational partners NCES will allow users and information systems to: Find and access relevant information; Expose the information they produce for others to discover; Collaborate in a more effective manner; Distribute data to forward deployed areas; Increase performance and reliability of data access, and; Utilize the enterprise infrastructure for evolving DoD systems to a Service-Oriented Architecture. NCES is the foundation for knowledge sharing and future knowledge creation

3 NCES Overview Macro Perspective
NCES Capabilities Metadata Registry Content Delivery ServiceSecurity Service Oriented Architecture Foundation Collaboration People Discovery Service Discovery Enterprise Service Management Mediation Content Discovery User Access via DKO (SIPR & NIPR) NCES Users Global Combat Support System Distributed Common Ground System Net-Enabled Command Capability Defense Technical Information Center Theater Battle Management Core System Global Command & Control System Integrated Strategic Planning & Analysis Network National Geospatial-Intelligence Services Communities of Interest NCES Early Capabilities Baseline Users NCES is delivering capabilities to enable the Department’s net-centric information sharing transformation!

4 and reuse capabilities regardless of platform; increased flexibility
Enterprise Services Discussed Today ServiceSecurity Service Discovery Ability to operate in a secure environment Confidence that enterprise services are available and reliable Enterprise Service Management Real-time update and alert notification as information changes Ability to develop and reuse capabilities regardless of platform; increased flexibility and agility Exchange data with unanticipated users in unanticipated formats Mediation Locate people and network resources People Discovery NCES This the suite of NCES services available to COI Not all services will be used by each COI To date, the most used services are: (1) DoD Metadata Registry (2) Service Discovery (3) Content Discovery I moved the detailed slides of each service to the backup section. Just talk to some of the services and inform the users of the backups Interoperability of data with shared semantics Metadata Registry Collaboration Content Discovery Content Delivery Web-based source for information on NCES and access to its services Communicate in real-time using voice, text, and video sessions Access to shared/ stored data; improved shared awareness Improved Quality of Service

5 Defense Knowledge Online (DKO) https://www.dko.dod.mil
Purpose Provide a single point of access to DoD Services Key Facts DKO is provided by Army Knowledge Online - same platform, same services - 1.9M users online now NCES Developer's Page on DKO provides initial orientation for early adopters Legacy NCES Portal (Defense Online (DOL)/GESPortal) to shut down NLT 12/31/07 Joint Accounts on DKO available for all DOL/GES Portal users now (sign up TODAY!) CAC or User ID/Password for logon Support for software-based PKI certificates. Will be expanded to support 2.5M (NIPR) and 300K (SIPR) users by March 2008 Primary Benefits All users can create knowledge centers and post content to share information Provides personalized, user-defined, Web-based presentation that allows for secure access to enterprise services Allows users to efficiently and securely collaborate and share information Organizations can save $ by eliminating/avoiding costs to establish/sustain own local portal Primary Audience COIs, DoD Capability developers, End users 5

6 Defense Knowledge Online (DKO) https://www.dko.dod.mil
How to get started 6

7 Defense Knowledge Online (DKO) Demonstration

8 Collaboration Purpose Key Facts Primary Benefits Primary Audience
JA0074C.8 BM6710 AL 4/19/ :50:43 AM4/19/ :50:43 AM Marcom Collaboration Purpose Provide Web Conferencing, IM, Chat, file-sharing, and application-sharing capabilities Key Facts Two “Buttons” IBM Sametime ( Currently operational on NIPRNet and SIPRNet Required Static Destination Ports: Port 80 TCP – http web traffic Port 443 TCP – https encrypted web traffic Adobe Connect/Jabber IM/Chat ( Available for testing on NIPRNet and SIPRNet Requires Flash Player, Ports 443 and 5222 Primary Benefits Enables collaboration between DOD, homeland defense, intelligence, and coalition forces Enables migration from costly and complex domain-specific collaboration capabilities to an enterprise provided service Improves warfighter and employee productivity by facilitating seamless and secure communications across the enterprise Primary Audience COIs, End users 8

9 Collaboration – Button 1
9

10 Collaboration – Button 2 https://www.dco.dod.mil
10

11 Button 2 Collaboration Demonstration

12 DoD Metadata Registry (MDR) https://metadata.dod.mil
Purpose Provide an on-line repository which enables developers to reuse, understand, integrate with, and share existing data assets (metadata) Targeting web services, databases, and vocabularies Provides a portal for developer access and web services for machine-to-machine access Key Facts Over 8,000 users and 180,000 assets registered Over 900 Programs of Record supported Serving the DoD, DHS, IC, NASA and NATO Hosted on NIPR, SIPR, and JWICS User driven via DoD Metadata Working Group and Feedback links on the portal Implements the ebXML standard for Metadata Registries Single Sign-On through DKO Primary Benefits Enables reuse and governance of data assets Foundation for other services; e.g. mediation Allows the COI data assets to exist after the COI disbands Primary Audience COIs, DoD Capability developers The DoD Metadata Registry is the Department’s electronic marketplace for structural metadata components. It provides enterprise-wide visibility and access for developers, configuration controllers and program overseers to register, use, subscribe, and manage structural metadata. The purpose of the Registry is not to publish broadly applicable standards, but to provide visibility into the Department’s ongoing structural metadata investment, and to encourage reuse of existing metadata components that are both developmental and operational. While each registered component is identified with its status and distinguished by a namespace, the Registry’s purpose is to allow developers to pull whatever they need; not to try and mandate usage of any particular metadata collection. The benefits to the developer, reductions in cost, time savings and interoperability have proven to be sufficient incentive. The public may access a portion of the DoD Metadata Registry via the Internet. To examine metadata artifacts, users must be sponsored by a government employee. The contents of the Metadata Registry are organized by governance namespaces within various metadata type “galleries.” Communities of Interest (COIs) should align with and leverage collections within one or more namespaces that intersect their concerns. Top Secret instance is run in conjunction with the Intelligence Community. 12

13 DoD Metadata Registry (MDR) https://metadata.dod.mil
new The DoD Metadata Registry is the Department’s electronic marketplace for structural metadata components. It provides enterprise-wide visibility and access for developers, configuration controllers and program overseers to register, use, subscribe, and manage structural metadata. The purpose of the Registry is not to publish broadly applicable standards, but to provide visibility into the Department’s ongoing structural metadata investment, and to encourage reuse of existing metadata components that are both developmental and operational. While each registered component is identified with its status and distinguished by a namespace, the Registry’s purpose is to allow developers to pull whatever they need; not to try and mandate usage of any particular metadata collection. The benefits to the developer, reductions in cost, time savings and interoperability have proven to be sufficient incentive. The public may access a portion of the DoD Metadata Registry via the Internet. To examine metadata artifacts, users must be sponsored by a government employee. The contents of the Metadata Registry are organized by governance namespaces within various metadata type “galleries.” Communities of Interest (COIs) should align with and leverage collections within one or more namespaces that intersect their concerns. Top Secret instance is run in conjunction with the Intelligence Community. Mission Area List Domain List COI List COI Links 13

14 DoD Metadata Registry (MDR)
Demonstration

15 DoD Discovery Metadata Specification (DDMS) https://metadata. dod
Purpose Provides a uniform set of metadata to promote visibility of data assets across the Department of Defense. Key Facts Called out in DoDD , “Data Sharing in a Net-Centric Department of Defense” Endorsed by E.O , “Further Strengthening The Sharing Of Terrorism Information To Protect Americans” Uses IC Information Security Markings (IC-ISM) for security markings on elements that may contain sensitive data. Used by Federated Search, Enterprise Catalog, DoD Metadata Registry, … Employed by numerous COIs to facilitate discovery of data assets across the DoD enterprise Adopted both within and outside of the DoD, including NATO, Canadian Dept. of Nat’l Defense, and DHS Extensibility supports specialized discovery requirements Primary Benefits Common vocabulary for discovery data Managed through the DoD Metadata Working Group Leverages well established standards (Dublin Core, GML, ISO 8601, …) Primary Audience COIs, DoD Capability Developers, DoD Data Providers

16 DoD Discovery Metadata Specification (DDMS) https://metadata. dod
The DoD Discovery Metadata Specification (DDMS) defines discovery metadata elements for resources posted to community and organizational shared spaces. "Discovery" is the ability to locate data assets through a consistent and flexible search. Visibility, accessibility, and understandability are the high priority goals of the DoD Net-Centric Data Strategy. Of these goals, visibility and discovery are intimately linked. Visibility of a resource is, in a practical sense, useless, if the resource is not easily discoverable. With the express purpose of supporting the visibility goal of the DoD Net-Centric Data Strategy, the DDMS specifies a set of information fields that are to be used to describe any data or service asset, i.e., resource, that is to be made discoverable to the Enterprise, and it serves as a reference for developers, architects, and engineers by laying a foundation for Discovery Services. The DDMS will be employed consistently across the Department's disciplines, domains and data formats. This document describes the DDMS elements and their logical groupings. It does not provide an interchange specification or substantive implementation guidance. The DDMS elements as specified in this document, however, should provide a basis for organizations to begin planning, transitioning, and implementing metadata tagging initiatives that support the Department's goal of increased data visibility and Enterprise Discovery. The current version of the DoD Discovery Metadata Specification and the current XML implementation can be downloaded via the link below. Previous versions of the DDMS and their XML implementations are also available under "Prior Releases.".

17 Federated Search https://search.nces.dod.mil/mse
Purpose Provides a capability which allows users to discover information from disparate data sources with one query Key Facts Returns results from the DoD and IC instances of Google appliances, COIs, and the Enterprise Catalog Exposes all types of information via DDMS; not limited to document-based content (DDMS v1.0/Fed Search v1.3) Provides a translation layer from legacy, non-DDMS based search technologies Work in progress for converged DNI and NCES spec Content Discovery SDK Package (refer to NCES Users Guide on DKO) provides overview to integrate with the Fed Search service Federated Search portlet enables integration of search with any user portal Integrates with the NCES Security services, NCES Service Registry, and NCES Messaging Allows local systems to determine access control for search results Primary Benefits One logged-in, can retrieve results from multiple data sources Can allow users to “discover” items in their native portal Enables Web services to be linked between multiple implementations (Search Aggregation) Supports searching both structured and unstructured data Primary Audience COIs, DoD Capability developers, End users The SDK package contains documentation about the “NCES Service” and a set of sample applications demonstrating its functionality. The documentation includes an overview of the service, a developer’s guide that discusses technical details (such as the service specifications used), and a guide to the “NCES Service” SDK that provides details on the sample applications. The sample applications, which exercise the functionality of the “NCES Service”, are already integrated with NCES service security and only require a valid certificate and configuration of the proper roles for the certificate’s domain name. 17

18 Federated Search https://search.nces.dod.mil/mse
18

19 Enterprise Catalog https://search.nces.dod.mil/catalog
Purpose Increase visibility for user content Targeting documents and web sites Provide an index for information sources without cataloging capabilities Provides publish/remove operations to populate a data source with metadata Key Facts Content Discovery SDK Package (refer to NCES Users Guide on DKO) provides overview to integrate with the Enterprise Catalog service New UI available November 2007 Leveraged by early adopters TBMCS, C2 SSA, MDA Primary Benefits Expand the quantity and quality of information accessible to the enterprise. Reduce latency, increase reliability, and optimize network traffic to provide efficient delivery of information. Use standard, vendor-neutral specifications to leverage existing Community of Interest (COI) information repositories including Web servers, file servers, databases, indexes, content management systems, and other applications Primary Audience COIs, DoD Capability developers, End users 19

20 Enterprise Catalog https://search.nces.dod.mil/catalog
20

21 Machine-to-Machine Messaging
Purpose Promotes decoupling of information among producers and consumers Asynchronous point-to-multi-point event notification using multiple messaging models (Publish/Subscribe/queuing/peer-to-peer) Alerts, track updates, etc. Producers do not have to keep track of consumers Producers and consumers do not have to be continuously connected to network Key Facts Accessible through a web-based interface on the DKO portal Messages searchable through NCES Federated Search Primary Benefits Guaranteed Messaging allows subscribers to receive queued messages after reconnecting to the network Provides Client Configurable QoS parameters Guaranteed messaging Priority, time-to-live, persistence, etc. Supports Distributed, Federated GIG Multiple message brokers/administrative domains Application integration Supporting Mediation/Orchestration Primary Audience COIs, DoD Capability developers, End users 21

22 Service Discovery https://service.nces.dod.mil/wasp/uddi/bsc/web
Purpose Provides a services directory that enables users to publish and discover shared applications and services. Key Facts Currently operational on NIPRNet and SIPRNet Interacts with Service Security to streamline access Primary Benefits Promotes capability reuse Promotes service composition and orchestration Establishes basic service governance capabilities Primary Audience COI, DoD Capability developers Gets the right information to the right people at the right time. Promotes reuse - Service developers can locate information entities in a service registry and use them to reduce time and effort. Promotes unified understanding of service metadata - Metadata for published services are accessible from centralized registries, promoting interoperability across the enterprise. Enables collaborative development - Allows use of discoverable services without changing software by enabling true loose coupling among services. Promotes service virtualization - Discovers and rediscovers services whenever you need them, regardless of their location. Promotes service composition and orchestration - Assembles multiple Web Services to form a business process or a high-level business function. Provides governance of the service registry - Verifies entities published into the registry conform to existing business rules, ensuring consistency across the enterprise.

23 NCES Service Registry https://service.nces.dod.mil/wasp/uddi/bsc/web

24 Service Security https://www.us.army.mil/suite/doc/9572662?inline=true
Purpose Protects WEB services from unauthorized use Key Facts Currently operational on NIPRNet and SIPRNet Uses open standards to define the rules that secure and protect GIG services. Provides multi-attribute authorization and access control Provides a flexible architecture that PORs and COIs can employ within their enclaves Primary Benefits Ensure that shared information is only accessed by appropriate personnel, services and computers Primary Audience COIs, DoD Capability developers Screenshots of the ABAC Policy Console and CTK

25 Notional NCES Security Architecture
NCES Security Services Attribute Service Robust Certificate Validation Service Portal Request / Response Provider "In the service-oriented-architecture, some services are invoked in the background every time a customer uses an SOA application or business process. The Service Discovery service provides a kind of SOA yellow pages. Service developers and providers register each service and can provide links to information about the service as a way of advertising their service to any person or other service that might be interested. Consumers can discover services and can learn things about how well a service has been working. The Service Security service uses facilitates the safe use of all services in the GiG by helping facilitate authentication and authorization for people and other services. The security service can use other services when doing this, including identity management services and white pages services. The Service Management service provides a way to monitor performance, and to control, optimize, and integrate services within the GiG. It measures whether a particular service is living up to its agreed-upon level of service, it watches for errors in the service and helps to resolve these, and it audits use of the service. Some of this data is written into the Service Registry yellow pages so that consumers and other stakeholders (possibly people involved in GiG governance) can see how a service is performing. The Service Messaging service provides a reliable way for services to interact with each other and to interact with the service consumer. It routes messages to the appropriate service and the appropriate instance of a service (since there may be several instances of a particular service for reliability and failover) and helps to orchestrate multiple services into a composed service. Request / Response Service Consumer Agent 25

26 People Discovery and Attribute Service
Provides the capability to identify and find White Pages (e.g. locator) information on people by leveraging the Joint Enterprise Directory Service (JEDS) Capability targeted to provide access to locator information contained in Defense Eligibility and Entitlement Reporting System (DEERS), the Global Directory Service (GDS), the four Service directories and other identity repositories about personnel and about all DOD CAC Card holders. Access to JEDS restricted to authorized personnel and services JEDS provides both a White Pages website and a Web Service Interface White Pages via HTTPS Application interface via LDAPS Web Services interface via SOAP over HTTPS Web Service interface uses SAML Attribute Query/Response protocol AS NCES Security Services

27 White Pages Attributes Attribute Service Attributes
JEDS Implementation GDS DEERS Army EDS Attributes JPAS Attributes Attributes JEDS Attributes DISANET Air Force Directory Services (AFDS) Attributes Attributes Pentagon PAED Attributes Attributes NMCI (Navy/MC) White Pages Others SAML/SOAP HTTPS White Pages Attributes } HTTPS, LDAPS Attribute Service Attributes } Last Name, First Name, Middle Initial, Generational Qualifier, Rank/Title, DoD Component, DoD Sub-Component, EDI-PI, Position, Mail, Citizenship, Personnel Type, Display PKI DN, Clearance/Controls Other UID, SIPRnet , SIPRnet Display Name, Office Phone, Secure Office Phone, Mobile Phone, Secure Mobile Phone, Fax, Secure Fax, IP Phone, Secure IP Phone, DSN Phone, DRSN Phone, User Certificate, Street Address, Mail Stop, Room Number, City, State, Country, Postal Code, Source DN, Publish Flag Last Name, First Name, Middle Initial, Generational Qualifier, Rank/Title, DoD Component, DoD Sub-Component, EDI-PI, Position, Mail, Citizenship, Personnel Type, Display PKI DN, Clearance/Controls 13 per AD Naming Convention } } 2 per the ICAS User Attribute Definitions } additional attributes per the JEDS Roadmap

28 Joint Enterprise Directory Services https://jeds.gds.disa.mil/

29 NCES Techguide http://metadata.dod.mil/mdr/ns/ces/techguide/
Purpose Help promote understanding of the DoD Net-Centric Data Strategy as well as more effective use of NCES capabilities. Key Facts Helps provide background, goals and step-by-step procedures to become Data Strategy compliant Provides relevant use case scenarios often encountered throughout the DoD Content is provided in a logical structure for each role to quickly decipher and understand Linked to through disa.mil/nces and the Developers Community on DKO Primary Benefits Enable a program to achieve DoD Data Strategy Compliance via NCES Capabilities Primary Audience Program Managers, Architects and Developers

30 NCES Techguide http://metadata.dod.mil/mdr/ns/ces/techguide/

31 Using NCES Capabilities COI Data Exchange Development Perspective
Collaboration Capability for collaborating among COI Members Chat sessions Member Forums Virtual conferencing, etc…. Defense Knowledge Online (DKO) Capability for creating sites for posting COI content Meeting minutes Status reports Collaborative work-products,…. DoD Metadata Registry Capability for making structural and semantic assets visible, accessible, and understandable and locating existing assets Data exchange formats (XML Schemas) Taxonomies/Ontologies (OWL Documents) Assertion of relationships between concepts and assets

32 Using NCES Capabilities COI Pilot Development Perspective
Service Security Capability for protecting Web services produced by COI Pilot developers Ensure access to services is authentic and authorized Machine-to-Machine Messaging Capability for publishing data for the purposes of machine consumption Guaranteed messaging for high volume and rapidly changing data Federated Search & Enterprise Catalog Capability for advertising and searching for data assets DDMS entries describing data assets such as Web pages and static content,… Precision search capabilities for locating relevant data assets. DoD Metadata Registry Capability for making service interface specifications visible and accessible Web service interface specifications (WSDL files) Service Registry Capability for making data access points visible Access points for service offerings References to interface descriptions Service ownership information Speaker Note: The pilot developers can also leverage DKO and Collaboration so the speaker should clarify that these capabilities are in addition to those that were on the previous slide.

33 Using the NCES Capabilities Getting Started / Approaches for Data Exposure
Acquire PKI and/or ECA certificates and NCES accounts Get the NCES User’s Guide Register on DKO Request access to the NCES Developer’s Community OPTION 1 Expose an existing Web Server by opening it up to be crawled by the Google search engine. The enterprise Google search engine is a data provider to the Federated Search. Your Data Asset OPTION 2 Implement the Federated Search Interface and register it with the NCES Service Registry. NCES Service Registry Federated Search Service Register endpoint Your Data Asset

34 Using the NCES Capabilities Getting Started / Approaches for Data Exposure
OPTION 3 Implement a custom Web service. - Register the endpoint in the NCES Service Registry. - Register the WSDL and XML Schemas in the MDR. NCES Service Registry XML Schema DDMS WSDL Register endpoint Custom Web Service Your Data Asset DoD Metadata Registry Register Pointer to WSDL file Register Enterprise Catalog

35 Integration with NCES Services for COI Case Studies
NCES Core Enterprise Services Community of Interest MDR Enterprise Catalog Federated Search Security Messaging Service Registry C2 SSA MDA Strike C2 Global Data Pilot Pull from STRATCOM lessons learned

36 NCES Lessons Learned Posted to Developers Community on DKO
Command and Control Space Situational Awareness (C2 SSA) COI Maritime Domain Awareness Data Sharing COI STRATCOM Global C2 Data Pilot Please post additional lessons learned as they are identified

37 Additional NCES References
NCES Public Site NCES Users Guide NCES Developers Community (hosted on DKO) NCES Techguide

38 NCES URLs Defense Knowledge Online Collaboration DoD Metadata Registry
Collaboration E-CollabCenter: Defense Connect Online: DoD Metadata Registry DoD Discovery Metadata Specification Federated Search Enterprise Catalog Service Discovery Joint Enterprise Directory Service

39 NCES High-Level Schedule
FY07 DKO-N Joint user access – Jan Metadata Registry V6.0 – Feb Service Discovery Update – Feb Service Security Update – Feb Milestone B - Mar Content Discovery Centralized Search (SIPR) – Apr Release SOAF RFP - May Deploy ESM – May Converged DoD/DNI Federated Search Specification - Jun Award Collaboration Button 2- Jun M2M Messaging Upgrade – Aug Deploy People Discovery & Attribute Service (SIPR) – Sep Federated Search (SIPR) – Sep FY08 Deploy People Discovery & Attribute Service (NIPR) - Nov Award SOAF - Nov Federated Search (NIPR) - Dec Milestone C - Mar FY06 Deploy DKO-S – Jun Deploy Collaboration Button 1 NIPR - Aug FY09 Initial Operational Capability - Jan Scale Capabilities - Jan Transition Users/Sustain Capabilities - Jan

40 Version 0.1

41 Federated Search Use Case
COI, POR, C/S/A Data Sources populated from applications, databases, web content, etc. Capabilities: Interfaces: Enterprise Services – DECC Columbus Community of Interest IC Community Program of Record EC Enterprise Catalog FS DS FS DS FS DS External Applications, Services, and Data Sources FS DS FS Federated Search FS DS FS DS FS DS For immediate discoverability users may post metadata to the Enterprise Catalog Query is federated and results returned. Users FS DS Data Source FS EC NCES Fed Search Aggregator Enterprise Web Content is crawled and indexed NCES Security Service NCES Service Discovery NCES Enterprise Catalog User Authorized by NCES Security Services Fed Search Aggregator discovers data sources from Service Discovery Aggregated results returned User Submits Search Query DECC Columbus & San Antonio DS (Web Enabled) DS (Web Enabled) User Logs into DOL Portal, DKO, or COI Application Results viewed by user NCES Enterprise Services Management Federated Search enables information sharing within and between COIs and PORs

42 Messaging Use Case “Weather” Channels A - 20854 B – 20374 C – 22209
D – 75201 E – 60601 F – 95101 Interfaces: POR Database 1 POR Database 2 POR Database 3 M Messaging Interface NCES Security Service Update Published A B C D E F DECC Columbus & San Antonio M NCES Messaging Service Receives update to subscribed Channel User Subscribes to Channel User Authorized by NCES Security Services Message Store Messaging Updates M2M Messaging Information Displayed on UDOP User Logs into UDOP View Weather info

43 DKO Success Stories USMC- Building and staging content today in DKO. Using targeted channel for C4 Planning Cell. IASE- “… DKO has extended the capabilities of the information assurance (IA) community of interest." JKDDC- For the first time, Joint users can use the Learning Management System (LMS). Only need a DKO account and Joint users can access their service training with Single Sign-On (SSO). everyday

44 Why NCES? “As-Is” Environment Pre-NCES OODA Loop Observe Orient Act Decide Stove-piped information = Large OODA Loop “To-Be” Environment Post NCES OODA Loop Observe Orient Act Decide Shared, accessible information = Small OODA Loop NCES creates a shared information space, increasing decision velocity

45 Today’s Challenges Substantial time and effort required to:
Identify, aggregate, and coordinate information and deliver operational plans Identify and aggregate historical and event information from internal and external sources Sharing information to support dynamic situational awareness is difficult to attain and maintain in active combat operations Logistics, maintenance, and operational mission information is difficult and time consuming to correlate Asset visibility is difficult to achieve and maintain

46 NCES Benefits NCES will enable:
Increased user access to accurate and relevant, automatically updated, information Decreased planning cycle times Rapid user access to local and enterprise information/intelligence sources Accurate and relevant information retrieval from local and enterprise sources Rapid exchange of information in support of shared situational awareness Global visibility on combat support information NCES Benefits: Increase user access to accurate and relevant information that is automatically updated from a small set of authoritative sources and systems entry points Decreased planning cycle times Rapid user access to local and enterprise information/intelligence sources Accurate and relevant information retrieval from local and enterprise sources Rapid response to information queries supporting shared situational awareness Rapid exchange of information in support of shared situational awareness Global visibility on combat support information From: Operational Mission Planning Scenario Information/Intelligence Fusion Scenario JTF Combat Scenario Logistics Scenario


Download ppt "Agenda NCES Overview NCES Production Capabilities"

Similar presentations


Ads by Google