1 Copyright Advanced Systems Management Group Ltd. 1999-2010 EMSI Framework & Semantic...

1

Copyright Advanced Systems Management Group Ltd. 1999-2010

EMSI Framework & Semantic Interoperability Demonstration

“Outlining a Framework and Roadmap for System Interoperability” – EMSI 2010 - 2014

April 2010

Presented by: Mike Abramson President, Advanced Systems Management Group Co-chair OMG C4I Domain Task Force

2


Semantic Interoperability Demonstration

• Challenges in developing interoperable information systems

• Components of interoperability▫ Shared Operational Picture Exchange Services (SOPES)▫ Information Exchange Framework (IEF)▫ Semantic Specifications (SOPES, MIP, NIEM, EDXL, ….)

• Interoperability Demonstration based of SOPES and IEF Objective▫ Policy Driven Information Sharing▫ MDA process for developing:

Executable Information sharing rules Executable information protection rules Communities of Interest

• Demonstration Model Examples

3


Challenges

• Increasing complexity of the information environment

• Reduction in the perceived quality of Information:▫ Accuracy: semantics to accurately convey the perceived situation.▫ Relevance: information tailored to specific requirements of the mission, role, task or situation at hand.▫ Timeliness: information flow required to support key processes, including decision making.▫ Usability: information presented in a common, easily understood format.▫ Completeness: information that provides all necessary (or available) information needed to make decisions.▫ Brevity: information tailored to the level-of-detail required to make decisions and reduces data overload. ▫ Trustworthiness: information quality and content can be trusted by stakeholders, decision makers and users.▫ Protected: Information is protected from inadvertent or Malicious Release or use.

• Greater need to support decision makers with quality information

• Increased Operational Tempo

• Highly dynamic and fluid events and operational environments

• Inability of any communities to articulate a definitive set of information sharing requirements

3

4


Information versus information Protection

• Information Security▫ Safe-guard information at-rest and in-transit▫ Focus on network and boundary security techniques and technologies

• Information Protection (enforcement of IM Security Rules)

▫ Safe-guard information (/data) during the aggregation and marshalling of information

▫ Determination of sensitivity of aggregate information ▫ Semantic and data validation▫ Tag and Label Processing▫ Sensitivity filtering ▫ Release-ability of semantic instances vs. subscriber accreditations▫ Etc ...

5


Information Interoperability (circa 2003)

Sharable

Domain

Capability 1

Capability 2 Capability 3

Capability N

Shared Semantics / Ontological Commitment

Flexible and Adaptive Policy Enforcement Services

Information Protection and Security

Adaptive CoI-Based Data Distribution

Data Distribution Services

Communication Infrastructure

Adaptive Data-Owner Release-abilityServices and Controls

CoI Management, Data Aggregation and

Information Protection Services

Data Filters and Semantic Guards

SecurityGateway

Sharable

CoI 1

CoI 2

Organization ≈ Capability ≈ System ≈ Service

MultiplePeer-to-Peer

Gateways

5

6


Interoperability Approach Objectives

• Based on OPEN Standards

• Supported by Architecture Driven Strategies (UPDM, MDA)

• Separation of Business Rules from Software Applications/Services

• Platform Independent Solution Specifications

10


Applying Model Driven Architecture(SOPES Conceptual Architecture (2004))

Enterprise Architect

V7.1

($200-300)

Window Native

Serialized Objects

COIL Prototype

Worldwindopen Source

JC3IEDM(International Spec.)

COIL Prototype

PrismTech DDSOpen Source

Open Standard

COIL Prototype

SOPES IEDMOpen Standard

Log4Jopen Source

10

11


Demonstration Objectives

Outline a strategy that would deliver:

▫ A Flexible, Agile and Sustainable Capability for Multi-Agency Shared Operating Picture and Situational Awareness

▫ Alignment of existing capability C2 Information Sharing Capability Standardized Business Rules (SOPES IEDM) Standardized Messaging (NIEM:SAR, CAP-CP, SOPES XML, MIP PDU) Standard Situational Awareness DB (JC3IEDM) Standardized Distribution Mechanisms (DDS, SOA, Web Service, ...) Other (presentation, processing, ...)

▫ Architecture / Model Driven Information Sharing and Protection DODAF, UPDM Info Sharing /Info Protection modeling and transformation

▫ Emergency Response / Public Security Scenario and models Existing Scenario (e.g., Harbour Siren, MSOC, …) – To be selected Based on Propose EISE demonstration

11

12


Assumptions and Constraints

• The majority of described elements can be put together using existing or evolving open standards and integration software elements (Glueware)▫ Where current Glueware could be developed into a standards in

implemented as COTS (IEF information Exchange Service demonstrated through ASMG’s Common Object Interoperability Layer)

• Described elements align with previously stated C4I direction;

• Described elements can be prototyped and demonstrated within six (6) to twelve (12) months;

• Where feasible a prototype could be developed using high levels of standards based open-source or shareware products

• Demonstrate the use and effectiveness of the SOPES IEDM Specification

12

13


Demo Scenario

• Fire on a Navy Ship / Collaborative Response

• Demonstrate Selective Information replication across 4 government agencies

• Demonstration the ability to modify distribution patterns during Operations (using architecture generated information) to support changing operational context

• Demonstrate support for multiple data formats simultaneouslyPDU (primary Distribution, CAP (main Body), SOPES XML)

13

14


Communities of Interest(Based on Information Sharing Requirements)

• Demonstration has 4 Operational Nodes participating in multiple Separate Information Sharing Agreements (ISAs)

• ISAs link operational nodes into communities

• Operational Nodes can participate in multiple agreements representing virtual networks (Operations Needs, Privacy or Security Levels)

• ISAs change based on operational context

Maritime Operating

CentreNDHQ

RCMP OP Centre

RCMP OP Centre

Modifi

ed D

uring D

emo

14

15


Specifying Information Exchanges class DEMO_OV-2

«OperationalNode»PSC_OPcentre

+ ProcessData() : void+ PublishSA() : void+ ReceiveOperatorInput(char) : void+ ReceivePresentSA(char, char) : void

«OperationalNode»RCMP_OPcentre

+ ProcessData() : void+ PublishSA(char, char) : void+ ReceiveOperatorInput(char) : void+ ReceivePresentSA(char, char) : void

«OperationalNode»MaritimeOPCentre


«OperationalNode»NationalDefenceOPCentre

+ ProcessData() : void+ PublishSA(char, char) : void+ ReceiveOperatorInput(char) : void+ RecievePresentSA(char, char) : void

«SystemsNode»SAAdministration

+ ActivateContract() : void+ ConnecttoNode() : void+ DeactivateContract() : void+ ModifyContract() : void+ RetrievePresentContracts() : void

«SystemsNode»ScenarioControl

+ PauseScenario() : void+ ReadScenario(char) : void+ ResumeScenario() : void+ StartScenario() : void+ StopScenario() : void+ TriggerNodeEntry(char, char, int) : void

«Contract» con_Maritime_COP

«InformationExchange»

MANUAL ACTIVATION DURINGSCENARIO {«Contract» con_Secure_COM}


«Contract» con_Maritime_Alert


«Contract» con_Police_SA


«Contract» con_PS_SA


15

16


Alternate Approach class Secure_COM_Participa...

«Contract»Contract_Artifacts::con_Secure_COM

«OperationalNode»Nodes::MaritimeOPCentre


«OperationalNode»Nodes::RCMP_OPcentre

+ ProcessData() : void+ PublishSA(char, char) : void+ ReceiveOperatorInput(char) : void+ ReceivePresentSA(char, char) : void

«Subscriber»

«Publisher»

16

class MaritimeCOP_Participa...

«Contract»Contract_Artifacts::con_Maritime_COP

«OperationalNode»Nodes::MaritimeOPCentre

«OperationalNode»Nodes::NationalDefenceOPCentre

«PublisherSubscriber»

«PublisherSubscriber»

17


Defining a Contract class con_Secure_C...

«Contract»Contract_Artifacts::con_Secure_COM

«ContractSemantic»Contract_Artifacts::Filtered_CR_Unit_GIS

class con_Maritime_C...

«Contract»Contract_Artifacts::con_Maritime_COP

«ContractSemantic»Contract_Artifacts::

Filtered_ControlFeature_GIS


17

18


Setting up a Contract

class Filter_CR_Unit_GIS

«ContractTransactional»Contract_Artifacts::

Filtered_Organisation_Position


Filtered_Organisation_Status


Filtered_Organisation_Item



Filtered_Object_Item_Hostility_Status


Filtered_Organisation_Item_Type

18

19


Setting up a Dynamic Filter class Filtered_Organisation_Status


Filtered_Organisation_Status

«Filter»Deployed

«JC3_V3-1_Entity,CWM_Entity»Entities::ORG_STAT

+ avlbty_code: CHAR(6) [0..1]+ cbrn_dress_state_code: CHAR(6) [0..1]+ cmd_and_ctrl_role_code: CHAR(6) [0..1]+ cmtmnt_stat_code: CHAR(6) [0..1]+ creator_id: NUMBER(20)+ fire_mode_code: CHAR(6) [0..1]+ obj_item_stat_ix: NUMBER(20)+ operat_stat_code: CHAR(6)+ operat_stat_qual_code: CHAR(6) [0..1]+ org_stat_id: NUMBER(20)+ rad_dose_qty: NUMBER(6) [0..1]+ rdns_code: CHAR(6) [0..1]+ rdns_dur: CHAR(19) [0..1]+ reinforce_code: CHAR(6) [0..1]+ reserve_ind_code: CHAR(6) [0..1]+ training_code: CHAR(6) [0..1]+ update_seqnr: NUMBER(15)+ usage_stat_code: CHAR(6) [0..1]

19

20


Semantic: Organization_SA (SOPES Exemplar)

20

class Organisation_SA

«Semantic»Organisation_SA

«Transactional»Organisation_Item

«Transactional»Organisation_Item_Type

«Transactional»Organisation_Position

«Transactional»Organisation_Status

«Transactional»Organisation_Materiel_Type_Assoc

«Transactional»Organisation_Action_Assoc

«Transactional»Organisation_ActionTask_ROE

«Transactional»Organisation_Reference_Assoc

«Transactional»Organisation_Structure

1..*

1

0..1

1

1..*

1

1..*

1

0..*

1

0..*

1

0..*

1

1

Identifier

1

0..*

1

21


Semantic: Unit_SA

21

class Unit_SA

«Semantic»Semantics::Unit_SA

- current-position-lat: double- current-position-long: double- objectItemName: string- unit-hostCode: string

«Transactional»Organisation::Organisation_Status

+ org-stat-oper-stat-code: string+ org-status-orgName: string+ reportedDateTime: double

«Transactional»Organisation::Organisation_Position

- org-position-orgName: string- reportedDateTime: double+ org-position-pointLatCoord: double+ org-position-pointLongCoord: double+ org-position-pointVertDistance: int

«Transactional»Organisation::Organisation_Item

- org-item-objectItemName: string

«Transactional»ObjectItem::Object_Item_Hostility_Status

+ object-item-hostCode: string+ reportedDateTime: double

+unit-hostCode

+object-item-hostCode0..*

1

0..*

1

1..*

1

1

Identifier

1

+objectItemName

+org-item-objectItemName

22


Semantic: CR_Unit_GIS

22

class CR_Unit_GIS




- org-position-orgName: string+ org-position-pointLatCoord: double+ org-position-pointLongCoord: double+ org-position-pointVertDistance: int- reportedDateTime: double





«Semantic»Semantics::CR_Unit_GIS

+ hostil ityStatusDateTime: double+ objectItemName: string+ unitHostil ityCode: string+ unitPositionLatCoord: double+ unitPositionLongCoord: double+ unitPositionVertDistance: int+ unitTypeCatCode: string+ unitTypeName: string

«Transactional»Organisation::Organisation_Item_Type

+ org-item-type-categoryCode: string+ org-item-type-objectItemName: string+ org-item-type-typeName: string+ reportedDateTime: double

+unitPositionLongCoord

+org-position-pointLongCoord

+unitPositionVertDistance

+org-position-pointVertDistance

+unitPositionLatCoord

+org-position-pointLatCoord

+objectItemName


+unitHostil ityCode

+object-item-hostCode

+hostil ityStatusDateTime

+reportedDateTime1..*

1 1..* 1

1

Identifier

1

1..*

1

1

1

+unitTypeCatCode

+org-item-type-categoryCode

+unitTypeName

+org-item-type-typeName

23


Setting up a Dynamic Filter

23

class Unit_SA











+unit-hostCode


1

0..*

1

1..*

1

1

Identifier

1

+objectItemName


24


Setting up a Dynamic Filter

24

class Unit_SA











+unit-hostCode


1

0..*

1

1..*

1

1

Identifier

1

+objectItemName


25


Core Concepts

• Reusable Information Patterns

• Simple Extensible Notations

• Transformable into Executable Rules

• Targeting Open Standards

25

26


Questions and Answers

26

Mike Abramson, ASMG Ltd.265 Carling Ave, Suite 630, Ottawa, Ontario, K1S2E1

Fax: 613-231-2556Phone: 613-567-7097 x222

Email: [email protected]

Semantic Interoperability Demonstration April 2010

26

1 Copyright Advanced Systems Management Group Ltd. 1999-2010 EMSI Framework & Semantic...

Documents

Transcript of 1 Copyright Advanced Systems Management Group Ltd. 1999-2010 EMSI Framework & Semantic...