Emerging Trends in Net-Centric Operations


Published on

Published in: Technology, Business
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • We believe NCO enables transformation. We are working with government and one another to find an open way to demonstrate how NCO enables transformation and accelerates those efforts. We’ll have a predominantly technical focus because that’s what our companies do—but we realize a significant aspect of transformation is cultural. We can’t do business in the same way we have been and therefore hope to achieve an interoperable future.
  • slide).
  • 06/08/10 date of printout
  • 06/08/10 date of printout
  • 06/08/10 date of printout
  • Emerging Trends in Net-Centric Operations

    1. 1. Emerging Trends in Net-Centric Operations Standards and Technology Robert Marcus
    2. 2. Themes <ul><li>A key emerging trend is shared resources e.g. data, events, hardware, network, and services </li></ul><ul><li>Process, organizational, frameworks, and standards support is needed for efficient interoperable sharing </li></ul><ul><li>Standards can depend on collaboration use cases and domain-specific requirements </li></ul><ul><li>Interoperability use cases can often be categorized as Intranet-Centric (Mandated), Extranet-Centric (Negotiated), and Internet-Centric (Voluntary) </li></ul><ul><li>The selection and deployment of the appropriate technologies and standards for specific use cases is a critical issue for net-centric operations </li></ul>
    3. 3. Topics <ul><li>Net-Centric Operations 2.0 (NCOIC) </li></ul><ul><li>Enterprise Architecture Delivery (OSD NII, DISA) </li></ul><ul><li>M&S Enhanced Systems Engineering (NCOIC) </li></ul><ul><li>Systems and SOA standards (NCOIC) </li></ul><ul><li>Capabilities Mediation for SOA (DISA) </li></ul><ul><li>Emerging Standards for SOA (OMG, DISA) </li></ul><ul><li>Industry Standards for C2 Data Sharing (JFCOM) </li></ul><ul><li>Complex Event-Decision-Response (NCOIC, DISA) </li></ul><ul><li>Adaptive Information Dissemination (Army) </li></ul><ul><li>Foundation Information Grid (NCOIC and SPAWAR) </li></ul>NCOIC = Network Centric Operations Industry Consortium
    4. 4. NCOIC Overview <ul><li>A Forum for Subject Matter Experts to Collaborate on NCO Initiatives: </li></ul><ul><ul><li>Better Understand Customer’s NCO Vision, Goals, and Objectives </li></ul></ul><ul><ul><li>Exchange strategies and proven approaches to enhance system delivery </li></ul></ul><ul><li>An Organization Committed to Establishing Open, Interoperable Systems using Common Best Practices and Systems Engineering Techniques: </li></ul><ul><ul><li>Facilitates Consistency Across Industry (100 members) </li></ul></ul><ul><ul><li>Advocates for Open and Interoperable Systems Design </li></ul></ul><ul><li>Companies Committed to Meeting the Government More Than Half-Way: </li></ul><ul><ul><li>Understanding Industry’s Responsibilities and Acting </li></ul></ul><ul><ul><li>Addressing the Problem, Taking Initiative, Understanding the Requirement </li></ul></ul><ul><ul><li>Seeking close collaboration with Government and the rest of industry </li></ul></ul>The Consortium exists to exchange ideas and produce process and technology deliverables that facilitate force transformation through NCO.
    5. 5. NCOIC Technical Approach <ul><li>Complete a thorough and rigorous analysis of pertinent government agency architectures </li></ul><ul><ul><li>Customer Requirements Team </li></ul></ul><ul><li>Develop a secure information management overarching architectural framework / reference model to identify open standards and their patterns of use </li></ul><ul><ul><li>Architectures and Standards Analyses Team </li></ul></ul><ul><li>Identify the widest possible community of open standards-based product types </li></ul><ul><ul><li>Building Blocks Team </li></ul></ul><ul><li>Develop a program for education for NCO </li></ul><ul><ul><li>Education and Outreach Team </li></ul></ul><ul><li>To plan and implement strategies to develop effective collaborative engineering environments </li></ul><ul><ul><li>Engineering Processes Team </li></ul></ul>
    6. 6. Net-Centric Operations 2.0 <ul><li>Overview slide for an NCOIC session that I organized covering standards from the desktop (e.g. OpenAjax) to tactical networks (e.g. Data Distribution Services) </li></ul><ul><li>The goal of the session was to present emerging technologies and interoperability standards </li></ul><ul><li>Key issues were areas where more interoperability standards were necessary e.g. ESBs and mashups </li></ul>
    7. 7. Net-Centric Operations 2.0 1. Web Client Application 4. Composites 2. Web Message Bus 3 .Enterprise Service Manager 5. Enterprise Service Buses 6. Enterprise Data and Systems 8. Tactical Networks 7. Gateway Adaptor Data Browser – RIA, AJAX, Mashups XML over HTTP XMLHttpRequest Web Server SOAP over HTTP SOAP Server, WCF Host, Application Server Services, SCA Services, SCA ESBs with multiple transports Orchestration – BPEL, BizTalk Data HTTP Enterprise Mashups/Pipes System Aggregation Gateway Server – Protocol and Data Transformations Sensor Networks, Mobile Platforms, Devices, Gateways (DDS, Efficient XML) Event Processing External Interfaces SDO SDO
    8. 8. Net-Centric Operations 2.0 Issues Enterprise Service Buses Rich Interface Applications (RIA) Enterprise Service Managers ESB ESB ESB Tactical Networks Near Real-time Data Gateways Interoperability Interoperability Web Message Bus Connections and nodes in bold are some key issues for Net-Centric Operations 2.0
    9. 9. Enterprise Architecture Delivery Process <ul><li>This is slide from a presentation at an NCOIC session that I organized for DISA and OSD NII on “SOA Deployment: Industry Best Practices” </li></ul><ul><li>The talk was based on my experiences at Boeing and General Motors </li></ul><ul><li>A similar approach was the basis of a chapter that I wrote for the CRC Handbook of Object Technology on “Transitioning Large Organizations to Object Technology” and an Architecture Delivery Process that I created at General Motors. </li></ul>
    10. 10. Enterprise Architecture Delivery Process 1.Concept Refinement 2. Technology Development 3.System Development and Demonstration 4. Production and Deployment 5. Operations And Support Projects Enterprise Architecture Delivery Group Centralized Shared Resources Standard Reusable CONOPS Standard Reusable Technology Components And Services Standard Models, Existing Testbeds And Simulations Existing Hosting Centers and Platforms Reusable System Management Tools and Processes Up arrows are delivered standards. Down arrows are improvements based on experience
    11. 11. Enterprise Architecture Delivery Process 06/08/10 Reusable Resource Repository Project 1 Project 2 Project 3 Project 4 Centralized Standards Organization Enterprise Architecture Delivery Team
    12. 12. <ul><li>This slide was originally prepared for a proposal to the Air Force Research Lab on “Test Tracks for System of Systems Testing” </li></ul><ul><li>The basic concept was to combine Live, Virtual and Constructive (LVC) simulations of systems at different stages in the system life cycle in an integrated testing environment </li></ul>M & S Enhanced Systems Engineering
    13. 13. M & S Enhanced Systems Engineering Concept Refinement, System and Service Requirements DoD System Life Cycle Simulations, Systems and Services e.g. A, B,C Tests and V & V Proof of Concept Live (C), Virtual (B) and Constructive (A) System and Services Test Track Technology Simulation Technology Emulation Live System with Services System and Services Verification Design Testing Systems and Services Validation Interface Testing Concept Testing System and Service Analysis, Design, and Development System Development, Services Composition, and Systems Integration A B C
    14. 14. System Engineering and SOA Standards <ul><li>Overview slide for an NCOIC Session on Modeling and Simulation enhancements for System Engineering that I organized </li></ul><ul><li>The speakers included leaders on many of these topics including SysML, SDF, and UPDM. </li></ul><ul><li>The key issue for the session was the relationship between system and service modeling including related simulations </li></ul><ul><li>A secondary issue was the mapping between enterprise and technical architectures </li></ul>
    15. 15. System Engineering and SOA Standards DoDAF DoD Architectural Framework across multiple levels (Zachman And MoDAF are similar) UPDM Unified Modeling Language (UML) Profile for DoDAF and MoDAF SOA Architecture based on services SysML UML Extension for Systems Engineering FEA-DEA-BEA Federal and Defense Enterprise Architectures SCA and OSOA Component Interface Description SCBA FEA extension to Services and Components SDF Service Interface Descriptions Layers Enterprise Architects Software Architects Program Architects System Architects And Engineers MDA UML Models For software Architecture, Components and interfaces Developers Testbeds such as Federated Development and Certification Environment (FDCE) including Live Systems, Modules, Components ,Services and Simulations Services - Enterprise Systems - Operations
    16. 16. Capabilities Mediation for SOA <ul><li>This slide was developed in conjunction with DISA’s Net –Enabled Command Capability (NECC) group </li></ul><ul><li>The purpose of the slide was to lay out a strategy for defining, discovering and developing new application capabilities within service oriented architecture </li></ul><ul><li>It was also meant to be the basis for a series of Industry Day seminars to DISA </li></ul>
    17. 17. Capabilities Mediation for SOA Existing, Enhanced, Composite and possible new services and/or systems USERS Capability specifications (with priorities) and possible new capabilities Capability description (with cost of implementation) and possible new capabilities New capabilities available New capabilities needed Set of Services Set of Requirements Mediating User Requirements and Derived Requirements Matchmaking Systems Engineering Group Emerging Technology Group Capabilities Mediation Group
    18. 18. Capabilities Mediation for SOA JPMO FDCE Vendors Open Source Libraries Standards Bodies Contractors Consumers Producers Mike Hebert (JPMO) Bob Marcus (NCOIC) Needs Offerings (1) (2) (3) (4) NECC ST&T Marketplace (5) (6) (7) (8) (3) (7) (9) JMPO, FDCE groups solicited for ST&T needs Needs consolidated, prioritized and binned Needs sent to Bob Marcus Clarify need Match needs with offerings Gain producers interest Develop list of offerings – use Industry Days as delivery mechanism Scrub list of offerings and do final offering selections, finalize schedules for Industry Day(s) Ensure Industry Day(s) meet needs and ensure participation
    19. 19. Emerging Standards for SOA <ul><li>Overview slide for an OMG session that I organized for DISA’s Net-Enabled Command Capability group </li></ul><ul><li>The goal of the session was to learn about the emerging standards and to discuss possible harmonization across standards groups </li></ul><ul><li>I later presented a similar talk at a meeting of the Federal SOA Community of Practice (SOACoP) </li></ul>
    20. 20. Emerging Standards for SOA Service Data Objects Service Component Architecture Open SOA Standards Web Services Description Language (WSDL from W3C) Web Service Standards Development Apache Tuscany Eclipse SOA Development Tools C2 Model-Based Data Engineering Universal Description, Discovery and Integration (UDDI from OASIS) Submissions to W3C WS-Policy Assertions and Attachment Web Ontology Language (OWL-S) WSDL-S OASIS and WS-I Standards OASIS WS-Security WS-I Security Profiles Efficient XML
    21. 21. Service Data Objects Service Component Architecture Web Services Description Language (WSDL) Apache Tuscany Eclipse SOA Development Tools C2 Model-Based Data Engineering Universal Description, Discovery and Integration (UDDI) WS-Policy Assertions and Attachment Service Definition Framework (SDF) Web Ontology Language for Services (OWL-S) WSDL-S WS-Security and WS-I Security Profile Emerging Standards for SOA (Timeline)
    22. 22. Industry Standards for C2 Data Sharing <ul><li>Part of a NCOIC deliverable that I prepared in response to specific requests from the Joint Forces Command (JFCOM) </li></ul><ul><li>Standards and technologies were discussed and recommended based on categories of use cases </li></ul><ul><li>The draft of the deliverable was circulated within DISA and OSD NII as a possible model for standards description </li></ul>
    23. 23. Industry Standards for C2 Data Sharing <ul><li>Based on Use Cases (e.g. Intranet-Centric, Extranet-Centric, Internet-Centric) </li></ul><ul><li>Web of Services (SOAP/HTTP, ESBs, REST) </li></ul><ul><li>Data Sharing (Databases, Data Models, Metadata) </li></ul><ul><li>Detailed Summary Table with 23 Rows covering </li></ul><ul><ul><li>Standard or Technology </li></ul></ul><ul><ul><li>Description or Purpose </li></ul></ul><ul><ul><li>Status and Future Plans </li></ul></ul><ul><ul><li>Relationship to Other Standards </li></ul></ul><ul><ul><li>Recommendations </li></ul></ul>
    24. 24. Industry Standards for C2 Data Sharing Concepts Intranet-Centric Extranet-Centric Internet-Centric Business analogs Internal Enterprise Business to business Business to public Examples of Use Cases Single organization operations Joint operations Emergency and stability operations Implementation of standards Mandated Negotiated Partial and de facto System Coupling Tighter coupling Looser coupling Ad hoc coupling Communities of users Communities of interest (COI) Cross COI collaboration External non-COI collaborators Governance Centralized pre-defined policies Contractual agreements Dynamic policies enforced User authentication Individuals users known in advance User organizations known in advance Dynamic users and organizations Middleware for services Enterprise Service Bus SOAP Web Services, Service Gateways Simple Web services e.g. REST Service Discovery Design-time Deployment and Configuration Run-time Composition and mashups More static and controlled More dynamic based on standards Ad hoc and less maintainable Data sharing Common databases, data models, and semantics Standard data models and message formats for data exchange Public databases and self describing data in messages XML Metadata Internal standards Shared standards Public standards
    25. 25. Complex Event-Decision-Response <ul><li>Slide prepared for an NCOIC session on “Event Processing in Net-Centric Operations” that I organized and a workshop on Complex Systems </li></ul><ul><li>The key idea is that there are multiple levels of event processing, reactive decisions, and output responses </li></ul>
    26. 26. Complex Event-Decision-Response Preprocess In Event Input u Simple Event Processing Complex Event Processing Model Update New Model Strategy Tactics HQ Operations Field Operations Situation Impact Object Process Simple Response Service Composition of Services Plan Modification New Plan Complex Response Update Plan Create New Goals and Plan Sensor and Effects Management Observation and Control Components In Response Output u Assess and Decide Measurement Field Processors Data Structured Data Information Knowledge Wisdom Sense Respond
    27. 27. Complex Event-Decision-Response <ul><li>Sense and Respond applications include Algorithmic Trading, Threat Detection, Logistics and C4ISR </li></ul><ul><li>Event processing provides sensing capabilities for applications </li></ul><ul><li>Services can be used to provide response capabilities </li></ul><ul><li>Complex responses are created by composing simple responses </li></ul><ul><li>Complex events are created by combining simple events similar to data fusion in C4ISR </li></ul><ul><li>Complex Event Processing engines combine multiple capabilities and near real-time performance </li></ul><ul><li>The OMG is developing an events Reference Metamodel </li></ul>
    28. 28. Adaptive Information Dissemination <ul><li>I developed a design for bandwidth management of the Army’s Future Force Warrior mobile ad hoc network </li></ul><ul><li>The goal was to ensure important messages had sufficient QoS even when resources were limited </li></ul><ul><li>The importance of a message was determined by a software Dissemination Strategy Manager at the application layer </li></ul>
    29. 29. Adaptive Information Dissemination <ul><li>Limited bandwidth on the battlefield requires selective allocation of resources </li></ul><ul><li>Cost–benefits analysis and decision rules for QoS mode selection </li></ul><ul><li>Modes determine frequency, latency, fidelity, and streaming rates </li></ul><ul><li>Impact analysis of events on costs and benefits </li></ul><ul><li>Benefits analysis based on mission value of nodes messages </li></ul><ul><li>Costs computed from bandwidth (and battery charge for dismounts) resource constraints </li></ul>
    30. 30. 06/08/10 Strategy Manager Event has low impact No need to change mode Decision Support System (DSS) State Variables Adaptive Information Dissemination 1. Battlespace Event from External Applications 6. New Mode Decision 4.Impact Analysis for Event 5.Assess Aggregate Benefit versus Cost 2. Data Update to DSS Object 3. Data Extracted from DSS Object
    31. 31. Foundation Information Grid <ul><li>I proposed the Storage Resource Broker (SRB) from UC San Diego as a foundation for bottom-up construction of information grids for NCOIC demos </li></ul><ul><li>An SRB Zone provides unified access through a Metadata Catalog to multiple data sources independent of location, database and storage device </li></ul><ul><li>SRB Zones can be federated by mappings between Metadata Catalogs </li></ul><ul><li>The SRB is freely available to government projects </li></ul>
    32. 32. Foundation Information Grid Physical Storage Independence Database Independence Location Independence Metadata Catalog Zone1 Physical Storage Independence Database Independence Location Independence Metadata Catalog Multiple Client Interfaces e.g. Web Services Zone 2 Drivers Drivers
    33. 33. Foundation Information Grid 06/08/10
    34. 34. Future Activities <ul><li>Technical Lead for NCOIC review of DISA’s NECC architecture documents </li></ul><ul><li>Explore possible standardizations for Complex Event Processing with OSD NII and FAA </li></ul><ul><li>Organize a session on “Net-Centric Computing Environments: From Grids to Virtualization ” co-hosted by NCOIC and Open Grid Forum </li></ul><ul><li>Analyze feasibility for defining verifiable layers of interoperability for specific missions with NATO </li></ul>