MG II Technical Messaging Overview

ACSICG/3 – IP/16 Agenda Item 6 12/05/16

GEMS Agenda

• Global SWIM Concept Review

• Mini Global GEMS Architecture

• Lessons Learned

2

Global Coordination

• Seamless information exchange across Flight Information Regions (FIRs) is essential for operators and Air Navigation Service Providers (ANSPs)

• Global Interoperability is a major component of ICAO's future roadmap

Mini Global – ASBU Connection

Mini Global supports Global Air Navigation Plan (GANP) and Aviation System Block Upgrades (ASBUs) goals

Global Enterprise Messaging Services

SWIM SWIM SWIM

SWIM

SWIM SWIM

SWIM SWIM

SWIM

SWIM

SWIM SWIM

SWIM

5

Mini Global SWIM Enterprise Messaging

Harris GEMS Indra GEMS Mosaic GEMS NEC GEMS

Current Architecture

ICAO SWIM Concept Architecture

7

GEMS MG II Architecture

FAA User 2 User 3

Service by Indra

User 4 User 5 User 6

User 7 User 8 User 9

Service by NEC

User 10

User 11

User 12

Service by Mosaic ATM

Service by Harris

SWIM Region A

SWIM Region C

SWIM Region B

SWIM Region D

AP

AP

Common GEMS Standard

AP

AP

Flight Weather Aeronautical

FAA SWIM (NEMS)

Local SWIM Standard

Policy Enforcement

9

Service by Harris

User 1 User 2 User 3

Service by Indra

User 4 User 5 User 6

Service by Mosaic ATM

User 7 User 8 User 9

Service by NEC

User 10 User 11 User 12

Regional

Common

Local

GEMS

Lessons Learned

• Open standards provide flexibility for GEMS

Service Providers

• Governance must be handled by GEMS

Providers in unison and in a flexible manner

• A common security model must be implemented

by GEMS Providers

• Mediation is core to the success of Global SWIM

GEMS Working Group Charter

Include technical experts from each GEMS Service Provider

Ensure seamless end-to-end connectivity for Mini Global participants

Use common, open standard messaging protocol(s)

Develop data sharing agreements amongst the data providers

Enforcing governance policies across multiple EMS

GEMS Working Group Topics

General

• Agree on definition of EMS

• What are the minimum requirements for a GEMS provider?

• How will participant become aware of existing data sources / services connected to the GEMS?

Governance

• What is the process for generating governance rules and policies?

• How will governance rules and policies be communicated, enforced and monitored over a distributed EMS to EMS architecture?

Validation

• Where should validation of standards take place?

• What is the process for non-valid messages / data elements?

Routing

• What metadata requirements are required to ensure proper message routing?

• What is the process for defining and maintaining a common message definition (ICAO Doc 4444 ATS messages)

Security

• What are the components of security which will be enforced by EMS (integrity, authentication, authorization, non-repudiation, etc.)?

Data Sharing Agreements

13

• Participants define sensitive data elements in System Description Document

• Users request access to sensitive data elements through GEMS Service Provider

• Primary GEMS service provider converts the declaration of sensitive data elements / approved user needs into GEMS system configuration

• Primary GEMS notify other GEMS service providers of configuration

GEMS Mediation Example

14

Global Enterprise Message Service (Governance, Validation, Security,

and Routing)

GEMS Provider A

A P Common

Messaging

JMS (Body)

JMS (Metadata)

AMQP (Body)

AMQP (Metadata)

GEMS Adaptor

Source

A P

Global Enterprise Message Service (Governance, Validation, Security,

and Routing)

GEMS Provider B

Consumer

STOMP (Body)

STOMP (Metadata)

AMQP (Body)

AMQP (Metadata)

GEMS Adaptor

Validation

GEMS Validation

• GEMS Service Providers ensure messages published by data sources adhere to messaging and metadata standards

• Non-valid message are not routed to their destination

Data Governance Module (DGM) Validation

• All messages published over the GEMS Service Providers are sent to the DGM

• DGM ensures message content adheres to international data standards (AIXM, WXXM, FIXM)

Routing

• Ensuring information routes from each data source to the correct destination

• Enforcing data sharing agreements

• Adhering to standard for GEMS Message Metadata

GEMS Service Providers are responsible for:

GEMS Metadata Standard Example

17

Header Name Values Descriptions

GEMS_EMS

SBI Service by Indra

SBM Service by Mosaic

SBH Service by Harris

SBC Service by Canada

GEMS_SOURCE

FAA Federal Aviation Administration

SBM_FO Mosaic_FO

SBM_AW AIXM, iWXXM, WXXM

SBM_OTHER Conflict reporting and other legacy messages

SBH_OTHER Other legacy messages

NAVP NAV Portugal AGENCY US Government other than FAA AEROTHAI Aero Thai ASA Air services Australia CAAS Singapore JCAB Japan NAVCANADA NAVCanada ROK Republic of Korea BRAZIL National Civil Aviation Agency (ANAC)

TRINIDAD_TOBAGO Trinidad and Tobago

HARRIS Harris Test System

NCB FAA Network Communications Branch

Security Example

GEMS

Organization

System

User name/pass

authenticated

User access to Web Service

Endpoint authorized

Req/Reply

Pub/Sub

User access to network

authorized

Pub/Sub Messages filter based on user

access

Future Topics

• Governance development

Advanced governance synchronization

Data Sharing Agreements

FF-ICE Governance Rules

• Messaging development

Flight Object Messaging

• Global Security Model