1 / 18

Coalition Interoperability Architecture

Coalition Interoperability Architecture. KSCO Conference 2007 Egon Kuster Presented By Don Perugini Command, Control, Communications and Intelligence Division (C3ID) Defence Science and Technology Organisation (DSTO), Australia. Background.

topaz
Download Presentation

Coalition Interoperability Architecture

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. Coalition Interoperability Architecture KSCO Conference 2007 Egon Kuster Presented By Don Perugini Command, Control, Communications and Intelligence Division (C3ID) Defence Science and Technology Organisation (DSTO), Australia

  2. Background “The sharing of information with potential coalition participants is crucial to building trust and confidence among possible coalition partners.” Source: Australian Defence Doctrine Publication 00.3 - Coalition Operations, 2002

  3. Purchase of Foreign System, Requires additional training, Difficult to integrate with National processes, data, policies, system requirements, Using the same software does not guarantee interoperability, Updates must be synchronized. Typical Approaches (1)

  4. New Coalition System, Requires additional training, Difficult to integrate with National processes, data, policies, system requirements, Centralized data store, Does support the coalition requirements. Typical Approaches (2)

  5. Individual System Integration, Fragility and dependence on numerous integration translators, Large maintenance overhead, Dependence on multiple foreign acquisition cycles. Typical Approaches (3)

  6. Data release, Authoritative data sources, Dynamic coalition membership, Multiple concurrent coalition operations, System ownership/administration/maintenance, Coalition agility, Integration flexibility, Extensible. Requirements

  7. Architecture – Overview

  8. Architecture – Cross Domain

  9. Architecture – Coalition Domain

  10. Coalition Data Standards Self Describing Core Data Set Extensible Coalition Interface Standards Authoritative Data Sources Data Management (1)

  11. Message Orientation Pull versus Push Data Release Data Management (2)

  12. Ownership of Architectural Components Responsibility for: Maintenance, Administration, Compliance. Distributed Control

  13. Data contained in the National Release Points (NRP). Remove the NRP removes the data. Multiple and Dynamic Coalitions

  14. Dynamic and Multiple Coalitions • Dynamic Coalitions • Data contained in the National Release Points (NRP). • Remove the NRP removes the data. • Multiple Coalitions • Many networks • Many Cross Domains

  15. Distributed Data Storage Coalition Network is the biggest bottleneck Data Pull Mode only transfers required data NRP is another potential bottleneck Many examples of high load and availability Web Service solutions. Use of XML XML translators and parsers are extremely quick. Possible of using XML hardware technologies (if required). Scalability and Performance

  16. Predefined structured data. Coalition network support Dynamic discovery of services Potential use of WS-Discovery Maintaining data standards Issues

  17. Semantic Web and Semantic Service Oriented Architectures (SSOA). Use of WS-Discovery of similar Improvement of Coalition Networks Autonomic Coalition Systems Quadrilateral In-Transit Visibility (ITV) Future Work

  18. Egon Kuster egon.kuster@dsto.defence.gov.au Defence Science and Technology Organisation (DSTO) Questions

More Related