1. Service Desk Training EDIFly
Operation Team
PT. JTI Mandiri
July 2017

2. Aviation Industry use IATA standard messaging “Type B”

3. Airline Teletype System https://en. wikipedia
The airline industry began using teletypewriter technology in the early 1920s using radio stations located at 10 airfields in the United States
IATA standardised teletype message formats throughout the airline industry – named Type B, 1960s
2010s there have been initiatives in the industry to tackle the high cost of the existing Type B network by deploying secured peer-to-peer solutions, e.g. EDIfly

4. An example of a TTY message (IATA Type B format)
QD AAABBCC
to (IATA destination address) (QD priority=deferred, QU priority = urgent, QK priority = normal)
.XXXYYZZ
from (IATA origin address + timestamp DDtttt, DD=day of month, tttt in UTC
ASM
IATA type (keyword). Identifies type of message (rest of the message conforms to the format for this type. ASM=Adhoc Schedule(-change) Message)
UTC
Time mode (Coordinated Universal Time). UTC or LOCAL
27SEP03899E001/TSTF DL Y
Message Reference line
NEW
ASM subtype (Action Identifier)
BA667/13APR
Flight and date of flight
J 319 C1M25VVA4C26
fleet & equipment information
LHR1340 BCN1610
Station/time for depart & arrival
LHRQQQ 99/1
Route information. 99 is the passenger departure terminal code
QQQBCN 98/A
Route information. 98 is the passenger arrival terminal code
QQQQQQ 906/PAYDIV B
Route information

5. SMI – Short Message Identifier
MVT AIRCRAFT MOVEMENT MESSAGE IATA AHM 780
LDM LOAD MESSAGE IATA AHM 583
PTM PASSENGER TRANSFER MESSAGE IATA RP 1718
PSM PASSENGER SERVICE MESSAGE IATA RP 1715
DIV AIRCRAFT DIVERSION MESSAGE IATA AHM 781
BSM BAGGAGE SERVICE MESSAGES IATA RP 1745
CPM CONTAINER/PALLET DISTRIBUTION MESSAGE IATA AHM 587
UCM ULD CONTROL MESSAGE IATA AHM 388
SCM ULD STOCK CHECK MESSAGE IATA AHM 385
SLS STATISTICAL LOAD SUMMARY IATA AHM 588
ASM ADHOC SCHEDULED MESSAGE IATA AHM 785
PAL PASSENGER ASSISTANCE LIST IATA RP1707b, 1708
LPM LOAD PLANNING MESSAGE IATA AHM 580
ALI ABBREVIATED LOAD INFORMATION MESSAGE IATA AHM 584
SOM SEATS OCCUPIED MESSAGE IATA RP 1712
TPM TELETYPE PASSENGER MANIFEST IATA RP 1717
RQL REQUEST LIST MESSAGE IATA RP 1709
PNL PASSENGER NAME LIST IATA RP 1708
PFS PASSENGER FINAL SALES MESSAGE IATA RP 1719
IDM INDUSTRY DISCOUNT MESSAGE IATA RP 1714
ASL ADDITIONS AND DELETIONS LIST IATA RP 1708
SAL SEATS AVAILABLE LIST IATA RP 1713
RQM REQUEST INFORMATION MESSAGE IATA AHM 783
UWS ULD/BULK LOAD WEIGHT SIGNAL IATA AHM 581
FMM FUEL MONITORING MESSAGE IATA AHM 782

6. Aviation Applications use Type B
Cargo tracking and manifests
Aircraft maintenance information and ACARS messages
Airline industry’ procurement and repair transactions for aircraft (ATA’s Spec 2000 standard depends heavily upon Type B messages)
Passenger booking/reservations and DCS
Aircraft flight plans and air traffic control data
Weight and load-balancing information
Baggage tracking and tracing information, incl. RFID
Advanced passenger information (API) which is communicated to governments
IATA clearing house data, etc.

7. GAPURA use SITATEX messaging client
SITA MSW
Airline
Other GHA
SITA
GMSNet
Internet
SITATEX – DPS
DPSFDXH
DPSGPXH
DPSKDXH
DPSKFXH
DPSKIXH
DPSKLXH
SITATEX – CGK
CGKCSXH
CGKFFXH
CGKFIXH
CGKFOXH
CGKGGXH
CGKKIXH
CGKKKXH
CGKKLXH
CGKKOXH
CGKSRXH
Sitatex
DPS..XH
SITATEX – BPN
BPNGPXH
Sitatex
SUB..XH
SITATEX – SUB
SUBGPXH
Sitatex
BPN..XH
Sitatex
CGK..XH

8. EDIfly Solution GMSNet Internet Gapura TypeB Network SITA MSW Garuda
Create local loop
Integrate backoffice server
Free transmission charge to
EDIFly member
Keep connected to legacy TypeB
SITA MSW
TypeB Transmission Charge
Free Transmission Charge
Garuda
EDIfly Server
GMSNet
Internet
Airlines
EDIfly
Server
Other GHA
Gapura
EDIfly
Server
Application Server
Client PC
Notebook
IPAD HP
Cargo
Mail
CGK..XH =
-angkasa.net
Sitatex
HLPGPXH
DPS..XH
CGK..XH
SUB..XH
BPN..XH
Additional
Clients
Gapura TypeB Network
CGKKOXH =

9. Improvement ??? Availability, Speed & Reliability Reduce Cost
Flexibility Access & Integration

10. Transition from legacy switches to modern global IP networks
SITA or ARINC
Megaswitches
EDIFLY IP
Extend the Power of the Internet Topology to Aviation Messaging
High Availability
Faster Transmission
Traceable End to End

11. More Reliable w/ 2 channel

12. Cost Perspective Legacy Software/Mailbox Type B Address X.400
Transmission Charge
EDIFly
Free

13. EDIfly Server supports the following types of connection to the Type B network:
MQ series
MATIP/BATAP TypeB
SITATEX w/ SDK
Message
Switching
TypeB
Network
AtexNet
MQ Server
MATIP
Port 351
EDIfly Server
SITATEX
TXT File
Sitatex SDK
MQ series
Port 1414

14. Back-end systems can be connected to the EDIServer using following supported protocols:
MQ series
MATIP/BATAP
File
FTP
HTTP Post
SOAP Web Services
SMTP
POP3
AS4
Any JMS compatible data source
EDIfly Server
MQ server
MQ series
MATIP/BATAP
Host TypeB
Text File
Web Services
HTTP Post
POP3/SMTP
Java Connector
File Server
Text
FTP
FTP Server
Web
Server
Web
Server
Server
Fax/Print
/SMS
Gateway
Java APP
Server

15. EDIfly Messaging Format
Type B format implements the Type B standard as defined and published by IATA
SDK format implements a message format based on a property (or keyword) file similar to other industry SDKs’ file formats
TypeB:XML format implementation has been included in the EDIServer to allow a more modern interface to Type B messaging
EDIFACT format implements the EDIFACT standard defined and published by IATA as part of the Cargo-IMP standard
Type X format implements the Type X standard as defined and published by IATA

16. Type B message flow without EDIfly®
Copyright © Innovative Software S.à.r.l.
Type B message flow without EDIfly®
1616

17. Type B Message Flow with EDIfly®
Copyright © Innovative Software S.à.r.l.
Type B Message Flow with EDIfly®
1717

18. EDIfly Type B Message Processing (RSA/AES Encryption)
If successful, remote server will send back digitally signed receipt, which will be stored in EDIfly’s local database as non-repudiation & proof of delivery
Local EDIfly server checks if the destination Type B addresses are known in local cache
If the destination addresses are served by remote EDIfly servers, then the local EDIfly server will digitally sign the message, encrypt it and attempt to send it over the internet to the remote server
Local EDIfly server stores message in local database for traceability purposes
Remote EDIfly server will forward the message to the backend system(s) connected to it
If the destination Type B addresses are not served by remote EDIfly servers (4) OR does not return a correct digitally signed receipt (6), then the local EDIfly server will automatically pass the message to its legacy link, i.e. SITA or ARINC, LH Systems or other providers.
If the destination Type B addresses are not in local cache, then the local EDIfly server contacts EDIfly directory servers, to ask if the destination addresses are served by remote EDIfly servers
Backend system sends message to local EDIfly server
EDIfly Address
Directory 4 5
Sender‘s
Backend
Systems 1
Local
EDIfly Service
Recipient‘sEDIfly
Service 7
Recpient‘s Backend
Systems 6 2 3 8
Legacy
Type B
Service
Sender‘s EDIfly
Database
1919
Copyright © Innovative Software SARL

24. Q & A

25. Thank You