Implementation of an IATA/ICAO/WCO PNRGOV EDI Message Processing System

WCO IT Conference 2014 - Brisbane © 2012 IBM Corporation

Who Are We?

Michael Odgers Director Industry ACBPS

Peter Brennan Architect IBM

Agenda

 International standards messages  Flow of Passenger Data – Traveller pathway  Overview of Passenger Data System  Passenger Data Collector – what it does, history, process  Engagement, experiences, case studies  Variance in data, complexity

International Standard Messages  Adopted and implemented international standard Passenger related messages  Became active participants and contributors to relevant standards bodies to assist in the development, adoption and maintenance of messages  Implemented Passenger Name Record (PNR) messages –PNRGOV 11.1 –PNRGOV 12.1 –PNRGOV 13.1

 Advanced Passenger Information (API) messages –PAXLST (UN/CEFACT) –PAXLST (IATA/ICAO/WCO) –PAXLST ( US CBP )

Passenger Data Delivery – Traveller Pathway

Passenger Data System Overview External Provider

Risk Treatment

Airlines & Airline Service Provider Systems interact via EDI interfaces

Traveller Data Stores API Landing Tables

PNRGOV PAXLST SBRRES

CONTRL CUSRES ACKRES

ETL

Movement History

PNR Landing Tables

PNR Data Store

· Manage Alerts · Manager Notifications

Reference Data

ETL

Flight Data

Create Alert

Gateway Capabilities MQ Gateway ·

Secure Corporate gateway to exchange messages between external clients and internal applications

API Data

API/PNR Storage Reconciliation Notifications

PNR Data

PNRGOV/ SBRRES/ PAXLST

Watchlist

Schedule & Monitor

ACKRES

· · · ·

Message Tracking Facility Logging Audit Security

Rules

Flight Schedules

Airline Arrangement Push Notifications and Monitoring

WebSphere Message Broker

CUSRES

Transmission Schedule Monitor

CONTRL MTF Messages Push Schedules

PNR/API XML ACKRES/CUSRES Push Notifications

· · ·

Inbound & Outbound EDI Messages Traveller & Event Notification Messages Audit, Failure, Transformation Log

Authorised, authenticated and “clean" PNRGOV, SBRRES & PAXLST EDI

IBM Passenger Data Collector · · ·

Validate and Transform PNRGOV, SBRRES, PAXLST EDI Create ACKRES/CUSRES Create Event Notifications

IATA/WCO/ICAO Passenger Message Processing Overview

Check Schedules

Message Transmission Schedules

Connectivity • The Customs Connect Facility provides external connectivity over the Internet. • Allows airlines and service providers to connect via a secure method. IBM MQ – using SSL certificates for Mutual Authentication & Encryption MSG

ACKRES

MSG ARINC

ACKRES

MSG

SITA 7

ACKRES

C C F

1. Airline establishes direct “push” connection via MQ using SSL. 2. Service provider establishes connection via MQ using SSL and a. Airline “pushes” data via service provider or b. Service provider gathers data from airline systems and “pushes” message.

What is the Passenger Data Collector (PDC) ?  Is an enterprise application that provides the ability to process, transform incoming passenger information from airlines.  Providing a single point solution for the processing of Passenger related Industry Standard messages allowing for connectivity directly to airline reservation and departure control systems for additional Passenger information  Provides a lightweight infrastructure and application solution that can be easily integrated into existing gateways or B2B Infrastructure  Supports UN/EDIFACT PAXLST, PNRPUSH (SBRRES), and PNRGOV message formats

 Transforms EDIFACT messages to a custom XML format that can be ingested by other systems

PDC prepares Passenger Data for storage & subsequent analysis Passenger Data Collector (PDC)

Connection to API provider Connection to Reservation System Connection to Reservation System & Departure Control

Inbound queue

Transformation

Outbound queue

UN EDIFACT PAXLST Messages

API PAXLST Collector

API in XML format

UN EDIFACT PNRPUSH Messages

PNRPUSH Collector

PNR in XML format

UN EDIFACT PNRGOV Messages

PNRGOV Collector

Analytics and Indicator of Risk (AIR)

Passenger Movement History

PNRGOV EDIFACT Message

UNA:+.?*'UNB+IATA:1+UA+AUCBPS+101209:2100+020A07'UNH+1+PNRGOV:11:1:IA+F6C2C268+12'MSG+:22'ORG+DL:ATL+52519950'TVL+121210:0915+LAX+SYD+UA+8 39'EQN+2'SRC'RCI+DL:MFN4TI'SSR+AVML:HK:2:DL'DAT+700:061210:1010+710:061210:1200'IFT+4:28::DL+THIS PASSENGER IS A VIP'IFT+4:28::DL+CTCR 00115555555555'ORG+DL:ATL+52519950:LON+++A+GB:GBP+D050517'ADD++702:45 HIGH STREET:SLOUGH:BERKSHIRE::GB:SL1AA:00441753637285'EBD+GBP:40.00+4::N'TIF+SMITHJR+JOHNMR:A:1'FTI+DL:1234567890:::ELITE'FT+4:15:9+LHR DL X/JFK DL YVR GBP/IT END ROE0.618831XT3.10AY6IFT+8.50YQ3.40+YC4.30XY3.10XA2.80XFATL4.5'REF+:38739393AN8739P'FAR+N+++++MIL24'SSR+DOCS:HK::DL:::::/P/GBR/123456789/GBR/12J UL64/M/23AUG19/SMITHJR/JONATHON/ROBERT'TKT+0062120234533:T:1'MON+B:2888.00:GBP+T:2957.94:GBP'PTK+NR++061210:1010+DL+006+LON'TXD++3.10:::AY+8 .50:::YQ+3.40:::YC+4.30:::XY+3.10:::XA+2.80:::XF'DAT+710:061210:1200'FOP+CC:::VI:XXXXXXXX1186:0211'IFT+4:43+TIMOTHY SIMS+2234 MAIN STREET ATLANTA, GA 30067+770 5632891'TIF+JONES+WILLIAMMR:A:2'FTI+AF:0093789865:::ELITE'IFT+4:15:9+ LHR DL X/JFK DL YVR GBP/IT END ROE0.618831 XT3.10AY68.50YQ3.40+YC4.30XY3.10XA2.80XFATL4.5'REF+:38739393AN8780P'FAR+A+++++YN324N'SSR+DOCS:HK::DL:::::////GBR/12JUL64/M//JONES/WILLIAMNEVELL 'TKT+0062120234534:T:1'MON+B:2888.00:GBP+T:2957.94:GBP'PTK+NR++061210:1010+DL+006+LON'TXD++3.10:::AY+8.50:::YQ+3.40:::YC+4.30:::XY+3.10:::XA+2.80:::XF' DAT+710:081210:1200'FOP+CC:::VI:XXXXXXXX1186:0211'IFT+4:43+TIMOTHY SIMS+2234 MAIN STREET ATLANTA, GA 30067+770 5632891'TVL+121210:0915::1230+LHR+JFK+DL+324:B'RPI+2+HK'APD+767' SSR+SEAT:HK:2:DL:::LHR:JFK+15A::1+15B::2'DAT+2:111210:0915'TRI++108:::1'TIF+SMITHJR+JOHNMR:A:1'SSD+15A++++Y'TVL+121210:2200::2330+JFK+YVR+DL+330:B 'RPI+2+HK'APD+767'SSR+SEAT:HK:2:DL:::JFK:YVR+15E::1+15F::2'EQN+1'RCI+DL:ABCDEF'MSG+8'TVL+121210:1500:151210+YVR:VANCOUVER ARMS++VN+67576:ROH'ABI+1+:LHRRR+LON++DL'DAT+ZT:071210:1010'SAC+++X'TVL+101210:0915::1230+LHR+JFK+DL+324:B'RPI+2+K'SAC+++X'SSR+AVML:HK:2:DL' SAC+++X'SSR+SEAT:HK:2:DL:::LHR:JFK+15A::1+15B::2'SAC+++X'TVL+101210:2200::2330+JFK+YVR+DL+330:B'RPI+2+K'SAC+++X'SSR+AVML:HK:2:DL'SAC+++X'SSR+S EAT:HK:2:DL:::JFK:YVR+15E::1+15F::2'SAC+++X'TVL+121210:0915::1230+LHR+JFK+DL+324:B'RPI+2+K'SAC+++X'SSR+AVML:HK:2:DL'SAC+++X'SSR+SEAT:HK:2:DL:::LH R:JFK+15A::1+15B::2'SAC+++X'TVL+121210:2200::2330+JFK+YVR+DL+330:B'RPI+2+K'SAC+++X'SSR+AVML:HK:2:DL'SAC+++X'SSR+SEAT:HK:2:DL:::JFK:YVR+15E::1+15 F::2'SRC'RCI+1A:23456'DAT+700:061210:1010+710:061210:1200'ORG+1A:MUC+12345678:F31+LON++T+GB:GBP+A78987'ADD++702:351 LANDSDOWN ROAD:SLOUGH:BERKSHIRE::GB::SL1AA'EBD+GBP:20.00+2::N'TIF+WAYNE+JOHNMR:A:1'FTI+DL:1234567893:::ELITE'IFT+4:15:9+LHR DL X/JFK DL YVR GBP/IT END ROE0.618831XT3.10AY6 8.50+YQ3.40YC4.30XY3.10XA2.80XFATL4.5'REF+:38739393AN8740P'FAR+A+++++YN324N'SSR+DOCS:HK::DL:::::/P/GBR/123456789/GBR/12JUL12/M/23AUG15/WAYNE/J OHNALVA'TKT+0062120234535:T:1'MON+B:2888.00:GBP+T:2957.94:GBP'PTK+NR++061210:1010+DL+006+LON' TXD++3.10:::AY+8.50:::YQ+3.40:::YC+4.30:::XY+3.10:::XA+2.80:::XF'DAT+710:061210:1200'FOP+CC:::VI:XXXXXXXX1186:0211'TIF+COOPER+GARYMR:A:2'FTI+AF:009378 9830:::ELITE'IFT+4:15:9+ LHR DL X/JFK DL YVR GBP/IT END ROE0.618831 XT3.10AY6 8.50+YQ3.40YC4.30XY3.10XA2.80XFATL4.5'REF+:38739393AN8793P'FAR+A+++++YN324N'SSR+DOCS:HK::DL:::::/P/GBR/987654321/GBR/12JUL15/M/15JAN13/COOPER/ GARYWILLIAM'TKT+0062120234536:T:1'MON+B:2888.00:GBP+T:2957.94:GBP'PTK+NR++061210:1010+DL+006+LON'TXD++3.10:::AY+8.50:::YQ+3.40:::YC+4.30:::XY+3.10: ::XA+2.80:::XF'DAT+710:061210:1200'FOP+CC:::DC:XXXXXXXX3578:0211'TVL+121210:0915::1230+LHR+JFK+DL+324:B'RPI+1+HK'APD+767'SSR+SEAT:HK:2:DL:::LHR:JF K++17A::1+17B::2'DAT+2:111210:0915'TRI++2:::1'TIF+COOPER+GARYMR:A:2'SSD+15A++++Y'TVL+121210:2200::2330+JFK+YVR+DL+330:B'RPI+1+HK'APD+767'SSR+SE AT:HK:2:DL:::JFK:YVR+17E::1+17F::2'ABI+1+:LHRRR+LON++DL'DAT+701:071210:1010'SAC+++X'TIF+WAYNE+JONMR:A:1'SAC+++X'TIF+WAYNE+JOHNMR:A:1'UNT+135+ 1'UNZ+1+020A07'

Transformed XML format 22 + : . ? * ' UA AUCBPS IATA 1 2010-12-09 21:00:00 020A07 2013-04-29T22:44:46.174000 AMQ QMGR PNRGOV 1 2 1 11 1 IA 12 F6C2C268 DL 1 MFN4TI

Passenger Data Collector - Asset Evolution PDC V4.x Extended Functionality

PDC V2.x - Core Functionality

 Contains the following functionality extensions : – Application of any PNRGOV message errata and compatibility verification – Implement Message Transformation and structure Changes ( Mapping & XML Output ) – Implement Message Validation Changes based on patterns in Industry Data – Implementation of Message Event processing ( for Schedule and Monitor ) – Implementation of ACKRES message response ( Optional as per PNRGOV 11.1 Specification ) – Implementation of multiple PAXLST message versions – Modifications to allow the use of OAG Flight Schedule and OAG DST & Time Zone data – Changes to meet specific operational environment implementation requirements

Usage in ACBPS – EPAC2 Collect & Store EPAC2 Collect Components PNRGOV Message Provider

PNRGOV & ACKRES EDI via MQ

WebSphere Message Broker : · Cleanse and Validate EDI envelope, Authorise Sender for Message type, version and release · Responds CONTRL if error · Retrieve Message reply routing information · Wrap ACKRES/CONTRL for CCF Processing

PNRGOV CCF

IAT PNR DataStore

WebSphere Message Broker PNR Data

ACKRES/CONTRL

PNRGOV

ACKRES/

Inbound CCF Channel Services · ·

Authenticates Message Sender Decrypts Message Payload

Outbound CCF Channel Services · · ·

APA PDC Product : · Validates PNRGOV · Transforms PNRGOV to Traveler centric XML · Responds ACKRES · Generates Events ( eg. Flight Arrival, Message processing outcomes )

WebSphere Message Broker :

PNR XML WebSphere Message Broker

APA PDC

·

Events

Identifies Message Destination Authenticates Destination Encrypts Message Payload Event Data

PDC Database Contains: · · · ·

Legend In Scope for Collect Out of Scope for Collect

Original PNRGOV EDI Message Transformed Traveler Centric XML Outbound ACKRES Message PDC Process Log Data

EPAC2 Schedule & Monitor PDC Database

·

Ingests PNR data into the existing IAT environment Process Event Notifications

Data Variance & Complexity Despite endorsed international standards for Passenger Data Messages :  Data can be represented in many different forms but still be compliant  Data can be in freeform and is frequently duplicated within a record  To create meaningful information, the mapping process must apply rules to the data intelligently, for example: Do not translate duplicates If field 1 = X then do A, if field 1 = Y then do B. If field 1 = X and field 2 = Z, then do C etc etc

 Without intelligent mapping a simple transformation of data to may generate confusing data and create problems for subsequent analysis

Key Lessons • Know the border risks you are assessing • Understand the business requirements • Ensure there is a high level of technical support • Understand the data and its origin • Use international standards

• Seek assistance from others

15

Q&A

Q&A