The document outlines the Cargo Interchange Message Procedures (CIMP) aimed at automating cargo data exchange to facilitate a paper-free environment. It discusses the functionalities of the Skychain messaging system, including message configurations, queue management, and user training, while emphasizing compliance with international regulations. Benefits like increased efficiency and accuracy in cargo operations through automated messaging and data handling are highlighted throughout the text.

1. SKYCHAIN MESSAGING
Mohammed Anwer Ali

2. ABOUT MYSELF

3. WHY WE ARE HERE?

4. What is CIMP?
Cargo Interchange Message Procedures (Cargo-IMP)
To support a paper-free environment, the Cargo Interchange Message Procedures (Cargo-IMP) has been converted to an
easy-to-use electronic format. This interactive application provides faster, easier access to necessary data and each section
can be customized to meet your specific needs.
Uniformity, accuracy and economy of cargo data exchange
Cargo data exchange automation between airlines and other parties works much more efficiently if messaging procedures and
standards are applied. IATA's CIMP is the standard for exchanging critical cargo operations information.
Key Benefits
Maximize the benefits of your cargo operations through increased messaging automation by ensuring your cargo interchange
message procedures are compliant with international and local regulations and practices:
Message Specifications including embedded data elements, abbreviation codes, and enhanced search function printing
capabilities
WHAT IS IATA-CIMP?

5. PROCESS

6. BENEFITS

7. NEXT STEPS

8. IATA has mentioned two SkyChain users as E-Awb complaince in April, 2012

9. IATA CONFERENCE, APRIL 2013
IATA has mentioned three SkyChain users as E-Awb complaince in April, 2013

10. GARUDA E-FREIGHT VISION 2015
By Year 2015 – Less than 20%
By Year 2016 – between 75% to 20%
By Year 2017 – Between 100% to 75%

11. DEAR GARUDA TEAM,
ALL THE VERY BEST

12. Day 1
-- PIE Overview
-- PIE - Participant and Message Configuration in SkyChain
-- Message Processing
-- Message Search, Error Correction
-- Introduction to Queues
Day 2-8
-- Message Processing
-- Queue Processing
AGENDA
IATA Cargo IMP IATA AHM
•FFR + FNA + FMA + FFA •SSM
•FSU •ASM
•FWB •MVT
•FHL •CPM
•FBL •LDM
•FSR
•FSA
•FFM
MFM

13. What is this Training for?
-- This Training familiarizes the business users with the Messaging Module of SkyChain
-- Provides the users with an overview of the messaging capabilities of SkyChain and how can
it support and improve the business functions.
Whom should Attend?
– Users who do the messaging administration
– Users who manage SkyChain interfaces with external customers and systems
– Users who correct business messages such as FFR, FWB etc.
SKYCHAIN MESSAGING

14. PIE OVERVIEW
Airline/Agents communicate to each other for Exchanging business information such as:
-- To make a booking
-- To send a status update
-- To receive notifications

15. Steps
--------
-- Create Participant
-- Configure Communication Channel
-- Configure Message(s) and Version(s)
MESSAGE CONFIGURATION

16. CREATING PARTICIPANT

17. CONFIGURING MESSAGE TYPES

18. PIE MESSAE SEARCH

19. QUEUES

20. Queues are a list of entries. “View Queue Entries” Screen where Queue is placed for someone to inspect and take
action on it.
Queues are of three types, Public/Standard/Personal.
– Public Queues will be created by default when station is created at Network Level.
– Standard Queues are pre-defined Queues at the Station Level
– Personal Queues for individual User Level
Mode of Queue Placement are of two types
– Manual
• User initiates by pressing "Send to Q" button, this will invoke a queue Search Screen.
• User can choose a Queue Manually from the list and save. This Manual action will be queued in the selected Queue.
• Note: These Manual queued queues will not be deleted automatically when appropriate action taken, these queues need to be
removed manually only or get deleted automatically when scheduled jobs run to delete queues.
– System
• System Queues are placed automatically in the respective Queue and get deleted automatically when appropriate action taken to
resolve it.
QUEUES

21. MANAGING QUEUES

22. VIEW/ACTION QUEUES

23. QUEUE CONFIGURATION EXAMPLES
Queue Name QueueType Queue Description Station Classifier Code
Allotment Alert S Notifying the allotment holder station about release of an allotment CGK ALE
Allotment Approval Notification S Allotment Approval Request Notifications CGK APR
Allotment Response S Queue for the Allotment requester CGK ALT
Rejected SSIM S Incorrect SSIM CGK REJ
Processed SSM S Processed SSM CGK PROC_SSM
UnProcessed SSM Message S UnProcessed SSM Message CGK UNPROC_SSM
Processed SSM/ASM S Processed SSM/ASM CGK SSM
UnProcessed ASM Message S UnProcessed ASM Message CGK UNPROC_ASM
Q09-ASM Changes S ASM Changes CGK ASM
Processed ASM S Processed ASM CGK PROC_ASM
OAL schedule update S OAL schedule update CGK OAL
Schedule Amendment Queue S Schedule Amendment Queue CGK SCHMVT
AWB Irregularities S AWB Irregularities CGK AWB
Charges Correction Advice S Charges Correction Advice CGK CCA
Res pending confirmation S Notifications to stations on waitlisting or unconfirming/rejected bookings CGK CFO
Res pending confirmation S Notifications to stations on waitlisting or unconfirming/rejected bookings CGK RES
Res pending confirmation S Notifications to stations on waitlisting or unconfirming/rejected bookings CGK CTP
Consignee Acceptance S Consignee Acceptance CGK CNP
System S Default queue for CGK CGK HDQDEF
System S Default queue for CGK CGK DEF
Dwell time failure S Dwell time failure CGK DWL
Embargo failure S Embargo failure CGK EMB
Escalation Queue S Escalation Queue CGK ESC
FFM Rejections S FFM Rejections CGK MSG
FFM Rejections S FFM Rejections CGK NFY
FFM Rejections S FFM Rejections CGK FFM
FFM Rejections S FFM Rejections CGK JNK
FFR Queue S FFR (Flight Reservation request) CGK MSG
FFR Queue S FFR (Flight Reservation request) CGK FFR
FSU Validation Errors S Freight Status Update - Validation error CGK FSU
FWB/FHL Validation Errors S FWB/FHL Validation Errors CGK FWB
FWB/FHL Validation Errors S FWB/FHL Validation Errors CGK HDQFWB
Mail S Post Office Mail - CARDIT/RESDIT/Validation errors CGK MLA
MVT S Movement Messages - Validation failures CGK MVT
Offload S Offload Shipment CGK joining shipments CGK OFC
Special Load Transit Permit S Special Load Transit Permit CGK PER
Reservation S Station reservation queue - validation errors CGK CFM
Special Cargo S Special Cargo validation errors CGK SHC
Tracing S Tracing CGK TRC
Manager S Manager CGK DIM
Rating S Rating failures CGK RAT
Tariff approval S Approving Tariff CGK TRF
Other charges S Approving Other Charges CGK OTH
Merc Res S Station Res pending UU (to be removed) CGK CFM

24. DAY 2

25. PIE PRODUCTION – MESSAGE SEARCH REVIEW

26. SKYCHAIN PRODUCTION – QUEUES REVIEW

27. MESSAGING

28. 1. PIE will validate for the Correct Participant, Message configuration, correct message
format. If all these are valid then it will “Decode Successfully” and send to SkyChain for
business Validation.
2. SkyChain will do the business Validation for the message, depending on the message
type, SkyChain will do the necessary action.
3. For some messages depends on the Action of the message (success/fail) it will be
queued, in the respective Queue classifier for that Station.
4. In case of FFR, Skychain will do one more additional check, if FFR does not process due
to “Invalid Agent”, “Invalid Stock”, any other reason then it will go to “UnProcessed FFR”
Screen.
MESSAGE PROCESSING

29. MESSAGES
IATA Cargo IMP IATA AHM
•FFR + FNA + FMA + FFA •SSM
•FSU •ASM
•FWB •MVT
•FHL •CPM
•FBL •LDM
•FSR
•FSA
•FFM
MFM

30. MESSAGE PROCESSING - FFR

31. FFR WITH NEGATIVE ACKNOWLEDGEMENT

32. PIE PROCESSED AND DELIVERED SUCCESSFULLY

33. SUCCESSFUL FFR MESSAGE PROCESSED

34. • Configuring Agents to send FFR
• Sending FFR for Host Airline without configuring “Customer Code” in PIE Participent
• Corrected “Invalid Agent” error in in „UnProcessed FFR” Screen by adding “Customer Code” in PIE
Participant.
• Other corrections in “UnProcessed FFR” Screen are,
• “Invalid Stock”
• “Invalid Flight”
• Created Reservation with the below Scenarios.
• Created Reservation using FFR for Own Airwaybill with Own Flight
• Created Reservation using FRR for Own Airwaybill with OAL Flight
• Created Reservation using FFR for OAL Airwaybill with OWN Flight
• Created Reservation using FFR for OAL Airwaybill with OAL Flight
• Configured “FNA”,”FMA”,”FFA” to received Acknowledgements.
• Created Embargo and Send FFR, Received FMA with Embargo Error
• Try to make reservation (FFR) on the Flight whose capacity is already utilized, received FMA with
“Capacity Error”
• Configured PIE to send and received other airline FFRs.
• Created Reservation by sending FFR with Multileg shipment, having one sector Own and second sector
OAL. OAL Airline received the “FFR”
• Message Pouch to check all “Incoming” and “Outgoing” Messages.
SUMMARY DAY 2

35. • For HOST airwaybill, when FFR comes it will do all validations, for example:
• Document Number
• Agent
• Flight
• Board Point
• Off Point
• and so on…
• For OAL Airwaybill it will check depends on the setting provided in the Screen “Document Maintenance
[STK0001]. Menu Link  Network  Stocks
• (Note: screen shot attached in the next slide).

36. OAL FFR DOCUMENT CHECK FAIL?
When OAL Document Number are failing with error “Invalid document Number”, if the system is doing
Check Digit then depends on the agreement with that Airline, either Mark “Check” or “UnCheck” the
Check Digit and as well Stock Controlled option.

37. DAY 3

38. MESSAGES
IATA Cargo IMP IATA AHM
•FFR + FNA + FMA + FFA •SSM
•FWB •ASM
•FSU •MVT
•FHL •CPM
•FBL •LDM
•FSR
•FSA
•FFM
MFM

39. MESSAGE PROCESSING - FWB

40. CARRIER HAS AN OFFICE AT ORIGIN AND DESTINATION
The following high-level data flow describes the information flow when the carrier has its own
operational airfreight processing office at origin and at destination.

41. 1. The Freight Forwarder at Origin, before delivering the freight, sends the FWB and FHL messages to the Carrier‟s Offices at Origin.
FHL message may be only the checklist (FHL type 1) and potentially also the details of house waybills (FHL type 2) to facilitate advance
cargo information for Customs.
2. The Carrier at Origin relays the FWB and FHL messages to the Ground Handling Agent at Origin before the Freight Forwarder at
Origin delivers the freight.
3. The Ground Handling Agent at Origin receives the freight and accepts it as Ready for Carriage (or rejects it) and sends back to the
Carrier at Origin the status messages (FSU) with the standard code Ready For Carriage (RCS). The Ground Handling Agent at Origin
may also relay to the Carrier at Origin other messages according to the agreement in place between them, and
– a. If the Carrier at Origin is performing the aircraft load planning the Carrier at Origin sends the FFM to the Ground Handling Agent at
Origin;
– b. If the Ground Handling Agent at Origin is performing the aircraft load planning, the Ground Handling Agent at Origin sends the FFM to
the Carrier at Origin.
4. The Carrier at Origin relays to the Freight Forwarder at Origin the status messages (FSU) with the standard code Ready For Carriage
(RCS). The Carrier at Origin may also relay other FSU messages to the Freight Forwarder at Origin in accordance with the agreement in
place.
e-AWB:
– The Carrier and Freight Forwarder at Origin both have a complete and valid Shipment Record based on the FWB and FSU (RCS) which
they can archive in their systems according to the pertaining regulatory requirements.
– The Carrier at Origin and Freight Forwarder at Origin can subcontract the Shipment Record management to its IT service provider if they
so desire.
– The Carrier at Origin, if so requested by the Freight Forwarder at Origin can produce a Cargo Receipt (subject to agreement).
5. Where they are not using a shared application, the Carrier at Origin sends to the Carrier at Destination the FFM, FWB‟ and FHL‟ (FWB
and FHL with the confirmed or modified information as per the FSU/RCS).
6. Carrier at Destination sends to the Ground Handling Agent at Destination the FFM, FWB‟, FHL‟ (FWB and FHL with the confirmed or
modified information as per the FSU/RCS).
– a. All agreed FSU messages are passed from the Ground Handling Agent at Destination to the Carrier at Destination who relays
these to the Carrier at Origin and the Freight Forwarder at Destination according to the agreements in place
CARRIER HAS AN OFFICE AT ORIGIN AND DESTINATION

42. CARRIER HAS AN OFFICE AT ORIGIN BUT NOT AT DESTINATION

43. 1. Before delivering the freight, the Freight Forwarder at Origin sends the FWB and FHL messages to the Carrier at Origin. FHL message
may be only the check list (FHL type 1) and potentially also the details of house waybills (FHL type 2) to facilitate advance customs
information.
2. The Carrier at Origin relays the FWB and FHL messages to the Ground Handling Agent at Origin before the Freight Forwarder at
Origin delivers the freight.
3. The Ground Handling Agent at Origin receives the freight and accepts it as Ready for Carriage (or rejects it) and sends it back to the
Carrier at Origin the status messages (FSU) with the standard code Ready For Carriage (RCS).
If the Ground Handling Agent at Origin is performing the load planning, the Ground Handling Agent at Origin sends the FFM to the Carrier
at Origin. If the Carrier at Origin is performing the load planning the Carrier at Origin sends the FFM to the Ground Handling Agent at
Origin.
4. The Carrier at Origin relays to the Freight Forwarder at Origin the status messages (FSU) with the standard code Ready For Carriage
(RCS).
e-AWB:
– - The Carrier and Freight Forwarder at Origin both have a complete and valid Shipment Record based on the FWB and RCS which they
will archive in their systems according to the pertaining regulatory requirements.
– - The Carrier and Freight Forwarder at Origin can subcontract the Shipment Record management to its IT service provider if they so
desire.
– - The Carrier at Origin, if so requested by the Freight Forwarder at Origin can produce a Cargo Receipt.
5. The Carrier at Origin sends to the Ground Handling Agent at Destination the FFM, FWB‟, FHL‟ (FWB and FHL with the confirmed or
modified information as per the FSU/RCS).
CARRIER HAS AN OFFICE AT ORIGIN BUT NOT AT DESTINATION

44. CARRIER HAS NO OFFICE AT ORIGIN BUT ONE AT DESTINATION

45. 1. Before delivering the freight, the Freight Forwarder at Origin, , sends the FWB and FHL messages to the Ground Handling Agent at
Origin. FHL message may be only the checklist (FHL type 1) and potentially also the details of house waybills (FHL type 2) to facilitate
advance cargo information for Customs.
2. The Ground Handling Agent at Origin receives the freight and accepts it as Ready for Carriage (or rejects it) and sends back to the
Freight Forwarder at Origin the status messages (FSU) with the standard code Ready For Carriage (RCS).
e-AWB:
– Both the Ground Handling Agent at Origin on behalf of the Carrier (need to be clearly defined in the GHA agreement) and the Freight
Forwarder at Origin have a complete and valid Shipment Record (based on the FWB and FSU(RCS) messages exchanged) which they
should archive in their systems according to the pertaining regulatory requirements.
– The Ground Handling Agent at Origin and/or the Freight Forwarder at Origin can subcontract the Shipment Record management to their IT
service provider if they so desire.
– The Ground Handling Agent at Origin, if so requested by the Carrier must be able to produce a Cargo Receipt.
3. The Ground Handling Agent at Origin sends to the Carrier at Destination the FFM, FWB‟ and FHL‟ (FWB and FHL with the confirmed
or modified information as per the FSU/RCS).
4. The Carrier at Destination sends to the Ground Handling Agent at Destination the FFM, FWB‟, FHL‟ (FWB and FHL with the confirmed
or modified information as per the FSU/RCS).
CARRIER HAS NO OFFICE AT ORIGIN BUT ONE AT DESTINATION

46. • Configure PIE to Send and Receive FWB Messages
• Add “FWB” Classifier in Maintain Queue for the respective Station
• Scenario 1
• Send FFR (Reservation should be created)
• Send FWB with same pieces and weight as FFR, (AWB should be captured)
• Scenario 2
• Send FFR (Reservation should be Created)
• Send FWB with different pieces and weight as FFR (AWB should be created with Irregularities)
• Action Irregularities, by mapping correct Pieces and Weight in AWB General Screen.
• Scenario 3
• Send FWB (AWB should be captured)
• Send FFR (nothing should happen)
• Scenario 4
• Send FWB (AWB should be captured)
• Send FWB (again by changing Pieces and Weight) (it should be queued to FWB queue classifier with
remarks “AWB already captured”
• Scenario 5
• Send FWB for OAL shipment
DAY 3 - EXERCISE

47. THANK YOU – NEXT SESSION DAY 4 - FSU