1 / 16

KEF

MRD- Implementation phasing. Phase 1. Phase 2. Phase 3. Phase 4. Impl level 1. MAD. Impl level 2. AMS. Impl level 3. Impl level 4. ARN . OSL. CPH. HEL. ATH. BRU. BUD. LIS. KEF. CDG. VIE. Impl level 5. MXP. LIN. Other: . FRA.

toviel
Download Presentation

KEF

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. MRD- Implementationphasing Phase 1 Phase 2 Phase 3 Phase 4 Impl level 1 MAD Impl level 2 AMS Impllevel 3 Impl level 4 ARN OSL CPH HEL ATH BRU BUD LIS KEF CDG VIE Impl level 5 MXP LIN Other: FRA **Please click on each cell for more detailed information about the implementation level and its different phases**

  2. Implementation level 1 Phase 1 • Partial MRD registrationbyhandlers • Not 100% handlers use the MRD • No scan of MRD labelby Post, or • No possible link of MRD labelwithreceptacleid’s in Postal system • IPC CANreliablyreport: • Date time stamp of delivery at unit/flightlevel (mainlytoairlines) • IPC CANNOTreport: • POD data in CAPE tosendingposts at receptaclelevel Operations • < 50% handlerregistration • < 80% MRD labelrecordingby Post • Simultaneousprocessingmostlyonseveralworkstations Expected quality/quantity of data • Goodqualityfordelivery time at unit/flightlevel, 0% receptaclelevel. • <50% unitdeliveryregistration • 0-10% receptaclelevel Back to grid

  3. Implementation level 1 Phase 2 • Partial MRD registrationbyhandlers • Not 100% handlers use the MRD • No scan of MRD labelby Post, or • No possible link of MRD labelwithreceptacleid’s in Postal system • IPC CANreliablyreport: • Date time stamp of delivery at unit/flightlevel (mainlytoairlines) • IPC CANNOTreport: • POD data in CAPE tosendingposts at receptaclelevel Operations • ~ 50%-80% handlerregistration • ~ 80-98% MRD labelrecordingby Post • Mostlybatchprocessing • Simultaneousprocessingonseveralworkstations at times Expected quality/quantity of data • Good quality of data for delivery time • Not reliable receptacle level information • Quantity: 50-80% unitdeliveryinformation • 10-60% receptaclesdelivered Back to grid

  4. Implementation level 1 • Phase 3 • Partial MRD registrationbyhandlers • Not 100% handlers use the MRD • No scan of MRD labelby Post, or • No possible link of MRD labelwithreceptacleid’s in Postal system • IPC CANreliablyreport: • Date time stamp of delivery at unit/flightlevel (mainlytoairlines) • IPC CANNOTreport: • POD data in CAPE tosendingposts at receptaclelevel Operations • ~ 80%-98% handlerregistration • ~ 80-98% MRD labelrecordingby Post • Productionmodebased data transmission Expected quality/quantity of data • Good quality for delivery time at unit/flight level • 100% reliable receptacle level data • Quantity: 80-98% delivery registration • 65-95%receptacle level Back to grid

  5. Implementation level 2 Phase 1 • Partial MRD registrationbyhandlers • Not 100% handlers use the MRD • Post scans MRD labels • Post sends RESCON from MRD labelscanto IPC • Post doesnotcomplywithProductionMode (Start/endscan+Workstation ID+XML file sharing) • IPC CAN reliablyreport: • Date time stamp of delivery at unit/flightlevel (mainlytoairlines) • IPC CAN partiallyreport: • POD data receptaclelevelonlywhen IPC data checks ok • IPC CANNOTreport: • POD data in CAPE tosendingposts and carriersreceptaclelevel Operations • < 50% handlerregistration • < 80% MRD labelrecordingby Post • Simultaneousprocessingmostlyonseveralworkstations Expected quality/quantity of data • Goodqualityfordelivery time at unit/flightlevel, 0% receptaclelevel. • <50% unitdeliveryregistration • 0-10% receptaclelevel Back to grid

  6. Phase 2 Implementation level 2 • Partial MRD registrationbyhandlers • Not 100% handlers use the MRD • Post scans MRD labels • Post sends RESCON from MRD labelscanto IPC • Post doesnotcomplywithProductionMode (Start/endscan+Workstation ID+XML file sharing) • IPC CAN reliablyreport: • Date time stamp of delivery at unit/flightlevel (mainlytoairlines) • IPC CAN partiallyreport: • POD data receptaclelevelonlywhen IPC data checks ok • IPC CANNOTreport: • POD data in CAPE tosendingposts and carriersreceptaclelevel Operations • ~ 50%-80% handlerregistration • ~ 80-98% MRD labelrecordingby Post • Mostlybatchprocessing • Simultaneousprocessingonseveralworkstations at times Expected quality/quantity of data • Good quality of data for delivery time • Not reliable receptacle level information • Quantity: 50-80% unitdeliveryinformation • 10-60% receptaclesdelivered Back to grid

  7. Phase 3 Implementation level 2 • Partial MRD registrationbyhandlers • Not 100% handlers use the MRD • Post scans MRD labels • Post sends RESCON from MRD labelscanto IPC • Post doesnotcomplywithProductionMode (Start/endscan+Workstation ID+XML file sharing) • IPC CAN reliablyreport: • Date time stamp of delivery at unit/flightlevel (mainlytoairlines) • IPC CAN partiallyreport: • POD data receptaclelevelonlywhen IPC data checks ok • IPC CANNOTreport: • POD data in CAPE tosendingposts and carriersreceptaclelevel Operations • ~ 80%-98% handlerregistration • ~ 80-98% MRD labelrecordingby Post • Productionmodebased data transmission Expected quality/quantity of data • Good quality for delivery time at unit/flight level • 100% reliable receptacle level data • Quantity: 80-98% delivery registration • 65-95%receptacle level Back to grid

  8. Implementation level 3 Phase 1 • Full MRD registrationby 100% of handlers • Post scans MRD labels • Post sends RESCON from MRD labelscanto IPC • Post doesnotcomplywithProductionMode (Start/endscan+Workstation ID+XML file sharing) • IPC CAN reliablyreport: • Date time stamp of delivery at unit/flightlevel (mainlytoairlines) • IPC CAN partiallyreport: • POD data receptaclelevelonlywhen IPC data checks ok • POD data in CAPE tosendingposts and carriersreceptaclelevel Operations • < 50% handlerregistration • < 80% MRD labelrecordingby Post • Simultaneousprocessingmostlyonseveralworkstations Expected quality/quantity of data • Goodqualityfordelivery time at unit/flightlevel, 0% receptaclelevel. • <50% unitdeliveryregistration • 0-10% receptaclelevel Back to grid

  9. Implementation level 3 Phase 2 • Full MRD registrationby 100% of handlers • Post scans MRD labels • Post sends RESCON from MRD labelscanto IPC • Post doesnotcomplywithProductionMode (Start/endscan+Workstation ID+XML file sharing) • IPC CAN reliablyreport: • Date time stamp of delivery at unit/flightlevel (mainlytoairlines) • IPC CAN partiallyreport: • POD data receptaclelevelonlywhen IPC data checks ok • POD data in CAPE tosendingposts and carriersreceptaclelevel Operations • ~ 50%-80% handlerregistration • ~ 80-98% MRD labelrecordingby Post • Mostlybatchprocessing • Simultaneousprocessingonseveralworkstations at times Expected quality/quantity of data • Good quality of data for delivery time • Not reliable receptacle level information • Quantity: 50-80% unitdeliveryinformation • 10-60% receptaclesdelivered Back to grid

  10. Phase 3 Implementation level 3 • Full MRD registrationby 100% of handlers • Post scans MRD labels • Post sends RESCON from MRD labelscanto IPC • Post doesnotcomplywithProductionMode (Start/endscan+Workstation ID+XML file sharing) • IPC CAN reliablyreport: • Date time stamp of delivery at unit/flightlevel (mainlytoairlines) • IPC CAN partiallyreport: • POD data receptaclelevelonlywhen IPC data checks ok • POD data in CAPE tosendingposts and carriersreceptaclelevel Operations • ~ 80%-98% handlerregistration • ~ 80-98% MRD labelrecordingby Post • Productionmodebased data transmission Expected quality/quantity of data • Good quality for delivery time at unit/flight level • 100% reliable receptacle level data • Quantity: 80-98% delivery registration • 65-95%receptacle level Back to grid

  11. Implementation level 4 Phase 1 • Partial MRD registrationbyhandlers • Not 100% handlers use the MRD • Post scans ALL MRD labels • Post complieswithProductionMode (Start/endscan+Workstation ID+XML file sharing) • IPC CAN reliablyreport: • Date time stamp of delivery at unit/flightlevel (mainlytoairlines) • Receptacle ID POD wherereceptacles are registered • Receptacle POD data in CAPE are 100% correct • IPC CANNOT report: • POD data in CAPE tosendingposts and carriersreceptaclelevelwheredeliveries are notregisteredbyhandlers Operations • < 50% handlerregistration • < 80% MRD labelrecordingby Post • Simultaneousprocessingmostlyonseveralworkstations Expected quality/quantity of data • Goodqualityfordelivery time at unit/flightlevel, 0% receptaclelevel. • <50% unitdeliveryregistration • 0-10% receptaclelevel Back to grid

  12. Implementation level 4 Phase 2 • Partial MRD registrationbyhandlers • Not 100% handlers use the MRD • Post scans ALL MRD labels • Post complieswithProductionMode (Start/endscan+Workstation ID+XML file sharing) • IPC CAN reliablyreport: • Date time stamp of delivery at unit/flightlevel (mainlytoairlines) • Receptacle ID POD wherereceptacles are registered • Receptacle POD data in CAPE are 100% correct • IPC CANNOT report: • POD data in CAPE tosendingposts and carriersreceptaclelevelwheredeliveries are notregisteredbyhandlers Operations • ~ 50%-80% handlerregistration • ~ 80-98% MRD labelrecordingby Post • Mostlybatchprocessing • Simultaneousprocessingonseveralworkstations at times Expected quality/quantity of data • Good quality of data for delivery time • Not reliable receptacle level information • Quantity: 50-80% unitdeliveryinformation • 10-60% receptaclesdelivered Back to grid

  13. Phase 3 Implementation level 4 • Partial MRD registrationbyhandlers • Not 100% handlers use the MRD • Post scans ALL MRD labels • Post complieswithProductionMode (Start/endscan+Workstation ID+XML file sharing) • IPC CAN reliablyreport: • Date time stamp of delivery at unit/flightlevel (mainlytoairlines) • Receptacle ID POD wherereceptacles are registered • Receptacle POD data in CAPE are 100% correct • IPC CANNOT report: • POD data in CAPE tosendingposts and carriersreceptaclelevelwheredeliveries are notregisteredbyhandlers Operations • ~ 80%-98% handlerregistration • ~ 80-98% MRD labelrecordingby Post • Productionmodebased data transmission Expected quality/quantity of data • Good quality for delivery time at unit/flight level • 100% reliable receptacle level data • Quantity: 80-98% delivery registration • 65-95%receptacle level Back to grid

  14. Phase 4 Implementation level 4 • Partial MRD registrationbyhandlers • Not 100% handlers use the MRD • Post scans ALL MRD labels • Post complieswithProductionMode (Start/endscan+Workstation ID+XML file sharing) • IPC CAN reliablyreport: • Date time stamp of delivery at unit/flightlevel (mainlytoairlines) • Receptacle ID POD wherereceptacles are registered • Receptacle POD data in CAPE are 100% correct • IPC CANNOT report: • POD data in CAPE tosendingposts and carriersreceptaclelevelwheredeliveries are notregisteredbyhandlers Operations • ~ 100% handler registration • ~100% MRD label recording by Post • Production mode based data transmission Expected quality/quantity of data • ~ 100% quality at unit and receptacle level • Quantity: ~ 100% unit and receptacle level data Back to grid

  15. Implementation level 5 • Phase 3 • 100% MRD use byhandlers • Post scans ALL MRD labels • Post complieswithProductionMode (Start/endscan+Workstation ID+XML file sharing) • IPC CAN reliablyreport: • Date time stamp of delivery at unit/flightlevel (mainlytoairlines) • Receptacle POD data in CAPE are 100% correct • Full POD at receptaclelevelavailabilityforposts and airlines • IPC CANNOT report: • Potentialmissingregistrationsbecause of operationalprocessfailures Operations • ~ 80%-98% handlerregistration • ~ 80-98% MRD labelrecordingby Post • Productionmodebased data transmission Expected quality/quantity of data • Good quality for delivery time at unit/flight level • 100% reliable receptacle level data • Quantity: 80-98% delivery registration • 65-95%receptacle level Back to grid

  16. Phase 4 Implementation level 5 • 100% MRD use byhandlers • Post scans ALL MRD labels • Post complieswithProductionMode (Start/endscan+Workstation ID+XML file sharing) • IPC CAN reliablyreport: • Date time stamp of delivery at unit/flightlevel (mainlytoairlines) • Receptacle POD data in CAPE are 100% correct • Full POD at receptaclelevelavailabilityforposts and airlines • IPC CANNOT report: • Potentialmissingregistrationsbecause of operationalprocessfailures Operations • ~ 100% handler registration • ~100% MRD label recording by Post • Production mode based data transmission Expected quality/quantity of data • ~ 100% quality at unit and receptacle level • Quantity: ~ 100% unit and receptacle level data Back to grid

More Related