Online IATA Telex Processor

I launched a first version of a Telex processor with a web frontend. It is a beta version and currently only processes MVT standard messages.

Some words about the requirements for a flexible interface processor

  • Though IATA Telexes are defined by a standard, variations are common because some are produced automatically by other systems and some are created manually, which causes more errors. The processing of telexes, the pattern recognition, must be flexible enough to be able to handle extra inline whitespaces and dots, as well extra lines with free text or extra headers and trailer, eg. now it is more common to receive telexes via email and often some extra email information is added as header before it reaches your system. Customers also might create their own telex standards, meaning the whole message is transported as free text message, but inside the message the customer uses his own syntax for data transmission.
    This requires a message interpreter that can be configured for new or non-standard formats on the fly, without the need to change any sourcecode and to redeploy a system.
    (I saw a project at one airport where the change of LDM format interpretation would have cost the customer around 10.000 Euro because one of the cargo airlines send messages with an extra header line)
  • Other standard messages, such as AFTN, NOTAM or CFMU should be processed by the same engine using the same approach. One interface engine with the flexibility of the scripts covers the various aspects of the different types.

A few words about concept and architecture

  • ESB
    Certainly the word ESB sometimes might appear bloated like other IT buzzwords, but it hardly makes sense today to implement distinct own interface systems for every protocol or subsystem type you come across. In a heterogeneous IT landscape like an airport an ESB allows you to easily connect inbound and outbound to a number of other systems via TCPIP, Email, FTP,.. or even talk to other standard systems like SAP, Salesforce.com and so on. We use one connector to talk to the ESB, the rest we orchestrate in the ESB itself. With MULE ESB we have the freedom of an opensource product as well the power of enterprise support. The learning curve for MULE is not too steep.
    For the sample of telexes: Sometimes you ‘receive’ telexes by using the auto export function of the Sitatex application and retrieve the files with the messages via FTP, or you receive the messages as email or via a queuing server from a central corporate entrypoint. We can swing over to another source or run in parallel without touching the main system.
  • Script Engine
    Instead of hardcoding the various formats, we use a Java Script engine executing Groovy Scripts. These scripts, one for each message type, are stored in the DB and can be adjusted or customized easily. The scripts produce an internal XML formatted standard output which easily can be un-marshalled during the downstream processing using proper XSD.
  • Data Processing
    Whatever requirements you have how to handle the received data. In our sample system here, receive from the web frontend and make it human readable.

Please feel free to drop by http://tools.airtilus.net:8080/AirtilusTelexR and try by yourself. Please note: Do not process confidential as the data is transmitted unsecured and might be stored (to improve the quality). This is NOT a commercial offering but a technology showcase. There is no warranty that the server is available or the processor correct. You can use the example message and modify it, otherwise copy and paste your own message.

The service is currently running on a Amazon EC2 micro instance, performance might decrease with a lot of traffic.

Online Telex Processor

Outlook

  • Summary for errors and rejected messages.
  • For the next versions I will add some of the other available telex types will follow such as LDM and CPM.
  • Add AFTN message interpretation.
  • Email Reply (send an email to the service and the human readable version is emailed back to the user).
Advertisements

IATA Telex Types Definition

Updates about the online telex processor here

Working in the airport IT industry you are always challenged with integration tasks at each airport. Usually you face a heterogeneous landscape of home-brew or taylored solutions and standard software running on anything from mainframe to virtual instances in a private clouds. Using an ESB we can tackle a lot of interfacing work and focus on the data integration part. One interface that you will find on all airports that operate commercial flights, is a link to the SITA network to send and receive IATA Telexes.

It is hard to find any information online, so I summarised the available message types here. Btw, these telex types are often referred to as SITA Telex types, which is not correct, IATA (Air Transport Association) defines the available telex types and SITA is operating the network to distribute the messages between airlines, airports, ATC, groundhandling agents and other relevant members of the airport community.

This list should be almost complete, giving you the type, the description and the AHM (Airport Handling Manual) or RP (Recommended Practice) reference. The AHM that you can purchase from IATA gives you all the syntax and details for most of the available types.

Find more info about baggage messaging here: IATA Type B Bag Messages and Baggage Messaging Refresher

 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

Disclaimer: The list might not be correct or complete. It is for educational purpose only. For reliable information please refer to the IATA manuals.

MVT, LDM, PTM, TPM, CPM, PSM, UCM are among the most common telexes from my experience. If you implement a telex interpreter you definitely need to implement these types first.

I am working on an online telex processor, a demo version I will put online soon.