1 October 2016SAS Cargo CPHQA-Q1 What is Cargo2000? Cargo2000 (=C2K) is a self-funded interest group of airlines and freight forwarders sponsered by IATA. The group has the objective to implement a worldwide quality management system for air cargo. SAS Cargo has decided to participate in the C2K initiative to produce the best possible quality for our customers.

1 October 2016SAS Cargo CPHQA-Q2 Cargo 2000 – generel purpose Cargo 2000 measures and monitores the milestones illustrated in the next slide and one extra Key Performance Indicator (KPI) called “flown as planned” – FAP. the timeliness of keeping the milestone deadlines (planned times vs. actual event times). the content of status message (i.e. correct number of pieces reported?). The timeliness of message transmission. All in all Cargo 2000 quality means To stick to a Route Plan (=RMP), especially to deliver all shipments at destination at originally planned time. Cargo 2000 quality data shall be used To improve the communication between forwarder and carrier in order to resolve process deficiencies. For improvement of your internal processes, processes at the interfaces to your carrier and as well at the interface between the carrier and the forwarder.

1 October 2016SAS Cargo CPHQA-Q3 Route Map Plan for airport-to-airport shipments The Route Map Plan (=RMP) defines the planned latest event times for following Milestones: Export at ABC station Import at XYZ station FWBRCSDEPRCFNFDDLV = RCS - 5 min. = LAT (Latest Acceptanc e Time) = STD + 15 min. = STA + agreed handling time = TOA (Time of Availability ) = TOA + 84 hrs. Event time calculation:

1 October 2016SAS Cargo CPHQA-Q4 FWB milestone Definition: Electronic Air Waybill received from export forwarder Milestone Responsibility: Forwarder is responsible for timeliness and quality of transmitted FWB to carrier. Compliance requirements: FWB is compliant if: message sent by forwarder arrives latest 5 minutes prior to RCS at carrier. message is correct according to Cargo IMP format. weight, origin and destination are same as in the last booking To do´s for GHA: None

1 October 2016SAS Cargo CPHQA-Q5 RCS Milestones 1 Defintion: Shipment/documents received from Export forwarder (shipper). Milestone responsibility: For event time: Forwarder is responsible for in time and ready for carriage delivery to GHA. After acceptance GHA is responsible for in tiem ready for carriage checks. For messaging time: GHA is responsible for timely and correct messaging to carrier.

1 October 2016SAS Cargo CPHQA-Q6 Compliance Requirements: RCS Milestone is compliant if: forwarder delivers freight and documents ready for carriage at the LCAG to GHA facility ahead of the defined trigger (LAT) to allow GHA to check ready for carriage in time. weight, pieces, origin and destination correspond with booking at time of RCS. RCS message is sent with actual RCS event time according to Cargo IMP format within 1 hour after actual RCS event time. Note: A FSU/RCS created before receipt of FWB makes the FWB non-compliant To do´s for GHA: Act according to Ground Handling Contract respectively to SAS Cargo´s Ground Handling Manual. Send FSU/RCS showing the actual event time as early as possible but not later than 24 hours after actual RCS event time. In case a RCS non-compliance occurs, send reason (irregularity or exception code) to carrier as early as possible but not later than 24 hours after actual RCS event time. RCS Milestones 2

1 October 2016SAS Cargo CPHQA-Q7 DEP Milestone 1 Definition: Shipment/documents loaded on board of booked flight and flight departed as planned (at scheduled time of departure = STD) Milestone responsibility: For event time: Gha is responsible for a timely preparation and positioning of shipment for the booked flight. For messaging time: GHA is responsible for timely and correct messaging to carrier.

1 October 2016SAS Cargo CPHQA-Q8 DEP Milestone 2 Compliance responsibility: DEP Milestone is compliant if: complete freight is loaded on board booked flight. the flight has departed as planned. DEP message is sent with actual DEP event time according to Cargo IMP format within 1 hour after actual DEP event time. pieces, origin destination in message correspond with booking at time of RCS. To do´s for GHA: Provide freight in time for transport to the aircraft according to carrier´s instructions. Send FFM and/or FSU/DEP (depending on local situation) showing the actual event time as early as possible but latest 55 minutes after actual DEP event time. In case a DEP non-compliance occurs, send reason (irregularity og exception code) to carrier as early as possible but not later than 24 hours after actual DEP event time.

1 October 2016SAS Cargo CPHQA-Q9 RCF Milestone 1 Defintion: Shipment/documents received from incoming flight and checked into the warehouse. Milestone responsibility: For event time: GHA is responsible for a timely preparation and positioning of shipment for the booked flight. For messaging time: GHA is responsible for timely and correct messaging to carrier

1 October 2016SAS Cargo CPHQA-Q10 RCF Milestone 2 Compliance requirements: RCF Milestone is compliant if shipment is completely received from flight and checked into the warehouse as soon as possible latest at planned RCF event time. RCF message is sent with actual RCF event time according to Cargo IMP format within 1 hour after actual event time pieces, origin and destination in message correspond with booking at time of RCS. To do´s for GHA: Check in freight into warehouse in time according to carriers handling instructions. Send FSU/RCF showing the actual event time as early as possible but latest 55 minutes after actual RCF event time. In case a RCF non-compliance occurs, send reason (irregularity or exception code) to carrier as early as possible but not late than 24 hours after actual event time.

1 October 2016SAS Cargo CPHQA-Q11 NFD Milestone 1 Definition: Consignee shown in Air Waybill or his agent notified that shipment/documents are available for pick up. Milestone responsibility: For event time: Carrier og GHA ( if part of contract ) is responsible for at timely nofitication of consignee shown in Air Waybill or his agent. For messaging time: GHA (if part of contract) is responsible for timely and correct messaging to carrier.

1 October 2016SAS Cargo CPHQA-Q12 NFD Milestone 2 Compliance requirements: NFD milestone is compliant if the complete shipment is available for delivery at destination before planned NFD event time (=TOA). notification of consignee shown in AWB or his agent according to local practice (fax/mail/documents put into pigeon hole) took place before planned NFD event time. NFD time is sent with actual NFD event time according to Cargo IMP format within 1 hour after actual NFD event time. pieces, origin and destination in message correspond with booking at time of RCS. To do´s for GHA: Notify consignee shown in AWB or his agent in time (if part of contract). Send FSU/NFD showing the actual event time as early as possible but latest 55 minutes after actual NFD event time. In case of NFD non-compliance, send reason (irregularity or exception code) to carrier as early as possible but not later than 24 hours after actual NFD event time.

1 October 2016SAS Cargo CPHQA-Q13 DLV Milestone 1 Definition: Shipment/documents are delivered to consignee shown in AWB or his agent at destination airport. For event time: Import forwarder is responsible for timely pickup GHA is responsible for at timely, complete and undamaged delivery to consignee shown in AWB or his agent. Milestone responsibility: For messaging time: GHA is responsible for timely and correct messaging to carrier.

1 October 2016SAS Cargo CPHQA-Q14 DLV Milestone 2 Compliance requirements: DLV Milestone is compliant if: the complete shipment is delivered to consignee shown in AWB or his agent. DLV message is sent with actual DLV event time according to Cargo IMP format within 1 hour after actual DLV event time. pieces, origin and destination in message correspond with booking time at RCS. To do´s for GHA: Deliver freight and documents complete and undamaged to consignee shown in AWB or his agent. Send FSU/DLV showing the actual event time as early as possible but latest 55 minutes after actual DLV event time. In case a DLV non-compliance occurs, send reason (irregularity or exception code) to carrier as early as possible but not later than 24 hours after actual DLV event time.