1 / 15

NetOps Data Strategy

Track 4, Session 4: NetOps Data Strategy. PURPOSE: This session will explore the NetOps Data Strategy for achieving seamless exchange of NetOps data from the Brigade Combat Team to the Joint Level, and the ability to manipulate that data in order to perform our mission of operating, managing, and d

lise
Download Presentation

NetOps Data Strategy

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

    1. Rule: Follow the exact same format in this slide template. Indicate your rank/title, first, last name, office symbol, AKO email address, office phone number.Rule: Follow the exact same format in this slide template. Indicate your rank/title, first, last name, office symbol, AKO email address, office phone number.

    3. Why a Data Strategy? DoD Net-Centric Data Strategy, 9 May 2003. Ensuring data are visible, available, and usable when needed and where needed to accelerate decision making “Tagging” of all data (intelligence, non-intelligence, raw, and processed) with metadata to enable discovery of data by users Posting of all data to shared spaces to provide access to all users except when limited by security, policy or regulations Advancing the Department from defining interoperability through point-to-point interfaces to enabling the “many-to-many” exchanges typical of a net-centric data environment

    4. Why do we need a Service Oriented Architecture ? To evolve from the complicated, pair-wise, expensive integration paradigm of the past to a platform independent, flexible, common interface, integration paradigm, we need a Service Oriented Architecture

    5. Standards and the DoD Data Strategy Bottom Line: Given that standardization of data across the enterprise is not feasible, standardize data on a smaller scale and use enterprise-wide IT and metadata standards to make data visible, accessible, understandable, etc. to all others (DoD Net-Centric Data Strategy and DoDD 8320.2) Standardize data within COIs, Vocabulary, schema Standardize how you make data visible, accessible, understandable, etc. across the enterprise XML, WSDL, UDDI, Metadata specifications, DoD Metadata Registry, DoD Service Registry Service Oriented Architecture Provide for translation between the vocabularies and schemas of COIs Mediation services (XSLT, Semantic metaframes, ontologies, etc.)

    6. Joint NetOps COI Data Working Group MISSION The Joint NetOps COI DWG will develop the NetOps component of the DoD Net-Centric Data Strategy and provides an open forum for identifying, mediating, and making decisions concerning NetOps data. VISION A technical and operational environment in which NetOps data is properly defined, tagged, stored and registered to enable easy discovery and use by all authorized users. SCOPE The DWG will focus on developing a data strategy and framework specifically for the sharing of NetOps-related data and information. Activities and associated definitions will be worked and coordinated with the Joint NetOps Architecture Working Group. MEMBERS Membership in the DWG consists of Combatant Commands, Services, and Agencies (CC/S/A). GOVERNANCE Oversight. The Joint NetOps DWG is part of and falls under the oversight of the Joint NetOps COI Technology Steering Group (TSG) and operates in accordance with the TSG Charter. Chair. The DWG is chaired by the JTF-GNO Technical Director representing USSTRATCOM. Secretariat. The Secretariat function will be performed by DISA PEO IA/NetOps.

    7. Objectives Objective 1 Develop a comprehensive NetOps IESS with the goal of improved situational awareness of the LandWarNet. Objective 2 Test the IESS concepts by implementing within a web service solution for a real world interoperability problem.

    8. Information Exchange Standard (IES) Definition: A model of the interoperable, shared data Determined by the Community of Interest Represented by a logical data model Contains business rules for the exchange of information Set within the context of an ontology and vocabulary Source for XML Schemas and XML data exchanges

    9. Information Exchange Standard, Cont. A complete NetOps IES does not exist today. The CND community has made the most progress in developing a data model based on OVAL, CPE and other standards. DISA has developed a Joint trouble ticketing standard (Gig Standard Ticketing). WIN-T/FCS is using the ICWG data standard for their network management. PM NetOps is looking at the CIM standard. JC3IEDM primarily developed for Command and Control functions. Many of the commercial network mgt tools are based on CIM WSDM is a newer standard from OASIS. Need to continue cross-walks of these standards and determine way ahead How do we implement….what good are they? Heat to Remedy Implementation Example

    10. CHNOPS Top-level Design

    11. CMDB/SD Architecture

    12. Short-term Architecture Using Web Services

    14. Long-term Architecture Using Web Services and ESB

    15. Army Enterprise NetOps Integrated Architecture

    16. Summary Two Pronged Approach Develop the overall NetOps Information Exchange Standard Implement a real-world project to develop lessons learned Understand why we need a NetOps Data Strategy See the importance of an Information Exchange Standard Take away lessons learned from actual implementations

More Related