IPC Mail Registration Device

Use of an IPC Mail Registration Device Future of Mail by Air Initiative; Challenge to provide electronic Proof of Delivery (POD) Facilitation of scanning at hand-over remains a challenge for a number of reasons: Time Space Ramp handlers Security It is not a realistic expectation that all handlers / agents / carriers invest at all outstations in custom build interfaces and equipment for recording of handover Solution: Use of an IPC Mail Registration Device

IPC Mail Registration Device Destination Post AMU Origin Post AMU PRECON/RESCON Carrier/ Agent CENTRAL DATA PLATFORM CARDIT/RESDIT At Destination Carrier/agent scans single recept. ID, registers for delivery, prints “handover labels” with correct date-time of delivery, attaches labels to units Post scans handover labels and receptacle IDs, sends RESCON Central Data Platform links date-time stamp delivery to recept. IDs, sends to Carrier / Handlers concerned Carrier uses data to produce RESDIT 21 – delivered AMU

IPC Mail Registration Device Concept The Airline / handler is the party that creates the date-time stamp of the actual handover of “units” with mail receptacles to the Post and registers flight details This information is on handover ID label attached by handler to the “units” delivered The electronic information is provided to a central processing system in near-real time The central processing system sends PRECON to receiving Post with handover IDs and flight info

IPC Mail Registration Device The Post establishes which receptacles were taken out of the “units” handed over by scanning handover ID and receptacle IDS The Posts sends a RESCON to origin Post with receptacle IDs (copy to IPC) and a RESCON with handover IDs to IPC The central processing system extracts the relevant information from copies received of CARDIT-RESDIT and PRECON-RESCON messages And distributes the information to appropriate parties to permit generation of RESDIT messages and performance reports

IPC Mail Registration Device Who benefits from using the MRD? Carrier: receives data to monitor performance of the handling agent and data to provide RESDIT 21 with POD at receptacle level to sending Post Handler: Uses POD produced by the device to replace manual data capturing on Delivery Bills / can show Airline date-time delivery of mail at flight level Sending Post: Can use POD information to establish delivery performance with airlines contracted. Receiving Post: Gets accurate data on handover, including flight information that can be used for RESCON and performance reports 7 7

Future of Mail by Air Initiative; IPC Mail Registration Device – status Nov 2009 Handover Data capturing: First prototype installed November 2007 MRD Installed in AMS, ATH, BRU, CDG, CPH, HEL, MAD, LIS, OSL in November 2009 Handover Data reporting: Performance reports released CAPE Vision Handler & Airline reports in CAPE Handover Data sharing: XML files – with receptacle level POD data from MRD registration and RESCON scan data - are made available to airlines and airline system vendors to create RESDIT delivery events 8

IPC Mail Registration Device What is expected from the handler on delivery: One scan per unit delivered Register Flight / Airline per unit delivered Attach one label per unit delivered

Take scanner from cradle Registration Procedure for Handlers using IPC Registration Device Check the screen for Home Page Take scanner from cradle 1 2 3 4 Go to the staging area Next step… 26/02/2008

Scan one receptacle ID per container (4 carts in this example) 1 2 3 4 Scan one receptacle ID per container (4 carts in this example) 4 1 2 3 Next step… Respect the order: FROM TRACTOR BACKWARDS ! 26/02/2008

Scanning units from front to back end First Unit SecondUnit

Flight Selection Screen - Use By touching the screen for needed flights on the top list they will be added to the list below. By touching on the bottom list you delete the flight from the list. Once all the flights you need for this handover are on the list you can press the “Next” button. In the case the driver does not know the flight number, cannot find the flight number on the list, knows the carrier but not the flight number or does not have any of these data -> see Appendix 3 of the present document. 25/09/2008 13

Container to Flight Association Screen - Description This list displays the preselected flight numbers or Carriers from previous screen. There are 2 additional buttons : “Multiple Carriers” in case the container being registered contains a mix of receptacles from several different Flights/Carriers. “Carrier Not listed” in case the Carrier name was not on the selection list from the previous screen. When clicking this button the labels to be put on the carts will be printed. Here you will find the list of the containers (3 in this example) that were previously scanned. They are displayed IN THE SAME ORDER they were scanned : FROM TRACTOR BACKWARDS ! 25/09/2008 14

Container to Flight Association Screen - Use Touch the screen on the first flight you want to associate a container to. A blue frame will appear around the button Press on the button(s) with the units you want to link to the selected flight. The button(s) will then get the same background color as the Flight button above. 1 2 Repeat the previous operation with all the existinig flights until no container button is colored grey anymore. Press on the “Print Labels” button the printing of the labels will then start automatically… 3 4 25/09/2008 15

Please don’t pull the labels while they’re coming out of the printer! Label 1 of n Label 3 of n Label 2 of n There will be one label printed per previously scanned container id Label 4 of n The Proof of Delivery label (P.O.D.) will display the ID of all the scanned container id’s, and the corresponding flights/carriers (…) Label n of n P.O.D. 25/09/2008 16

Slip printed labels into corresponding container pouches ⁽*⁾ 1 2 3 4 Slip printed labels into corresponding container pouches ⁽*⁾ 4 1 ⁽*⁾ When no pouch: stick label 2 3 Respect the order: FROM TRACTOR BACKWARDS ! 25/09/2008 17

IPC Mail Registration Device What is expected from the Post after delivery: Scan each unit handover ID first before scanning receptacles out of unit Process one unit at the time per workstation/scanner In case of simultaneous scanning on more than one unit, report workstation/scanner ID in RESCON Process one delivery (train of units) at the time Register flight info in local system to report flight info for the receptacles in RESCON

Scan handover ID on cart first Flight: KL1692

One unit at the time – scan receptacles while offloading

Register actual flight per cart, using handover ID label info

Process one delivery (train of carts/ULDs) at the time

IPC Mail Registration Device What is expected from IPC: To install MRDs and retrieve handover data from the MRDs into the CAPE database To link receptacle IDs from RESCON messages to handover data MRD To check MRD handover data against CARDIT-RESDIT data for verification To produce reports in CAPE Vision with handover registrations and receptacles scanned out of unit To produce XML files for Airlines / Handlers with POD data (at later stage also POA)

Report available in CAPE Vision Flight and handover registration Flight no. Planned Flight Arrival Handover date-time Receptacle on cart scanned by Airline Handover ID created by MRD

Report available in CAPE Vision De-nest scan & handover registration Handover date-time Handler Flight Handover ID created by MRD Receptacle IDs scan from cart