1. CCS Hungary BACH Best Airport/Airline Cargo Handling System presentation CCS Hungary BACH system demo - copyright CCS Hungary Aircargo Ltd.

2. Development History 1993: Company established to provide state of the art IT services for the air cargo industry. 1996: After two years development the Hungarian Cargo Community System began to operate. By the end of the first year, most major forwarders and airlines connected. 1997: The first version of air cargo handling system was cut-over at Budapest Airport Authority. 1999: Electronic Customs Interface created for MALEV Hungarian Airlines and for DHL Hungary. 2001: The new version of Cargo Community System software was installed at more than a hundred connected forwarder. 2002: The new Communication Center of CCS HUNGARY began to work in the city center of Budapest. 2003: Programming work started on the third generation air cargo handling system: called „BACH”.

3. 2004: CCS Hungary BACH cutover at Budapest Airport Cargo Base. 2005 JUL: FARNAIR contracted for CCS Hungary BACH. 2005 AUG: The tailor made version of CCS Hungary BACH called MACH was installed at MALEV replacing SITA Cargo to provide similarly good service as for Budapest Airport Rt. 2005 OCT: CCS Hungary bought his own office building and a new Communication Center was built there. Migration to the new place made as planned – no interruption in service. 2006 MAR: PECS Airport project completed a week before deadline, all airport, handling (including CCS Hungary BACH) and communication systems were delivered by CCS. OS made its inaugural flight with success. 2006 NOV: Two forwarders started the operational testing of the new CCS Hungary Integrated Forwarder system package. 2006 NOV: Development of the booking and schedule module of CCS Hungary BACH for MALEV has been finished 2006 DEC: MALEV contracted to add MACH the invoicing and financial module (CCS Hungary Financial) and create the interface to MALEV central financial system.

4. WHOOSE REQIREMENTS SHOULD AN AIR CARGO HANDLING SYSTEM FULLFILL? WHAT ARE THESE REQUIREMENTS? …and how can our CCS Hungary BACH system fulfill these needs ?

5. Handled Carriers require…  Air safety  Quick and error-free cargo handling  IATA and ICAO standards, EDI  Flexible service of special requirements, flexibility, conformability  Highly automatic – reduce human errors  Statistics, reports – 100% trustable  Neutrality, data-security, history of entries  Proper representation in front of customers

6. BACH satisfy these needs, because:  Weight control and correct manifest ensured  Checks and supervisor „flight close” functions  PC based, easy to modify, tailor make  Process incoming EDI messages and fill in screens with data  Automatic functions like making prints, sending out messages  Data reported secured  Data are stored on your server. All entries are recorded with user name and date/time  Satisfy even the Cargo 2000 group requirements

7. Law, Authorities require…  EU regulations, recommendations  Accounting law, tax authorities: up to date, error free reports, invoices  Customs: cooperation, reports, shipment history, electronic interface  Ministry, aviation authorities: air safety (flown as manifested, DGR goods)  Police: security, customer database, support the fight against pilferage

8. BACH satisfy these needs, because:  We tailor make all necessary reports to make the system 100% compatible  We have great practice in making electronic customs interface – CCS Hungary is Customs Approved Development Company  Manifest is re-checked by supervisor at flight close  All special handling codes are handled, auto located  Pre-flight information from FFM, remark option, procedures built on customer database, strict warehouse control

9. Forwarders, shippers, consignees requires…  Accounting law, tax authorities: up to date, error free reports, invoices  Customs: cooperation, reports, shipment history, electronic interface  Ministry, aviation authorities: air safety (flown as manifested, DGR goods)  Police: security, customer database, support the fight against pilferage

10. BACH satisfy these needs, because:  Proven procedures and live-tested software modules  Tested with most major multinational forwarders  Freight status information is always up to date and available for display and EDI  Serve special forwarder requirements – special requirements of Hungarian market  Local data storage, system access security and history ensures data security  Fully automatic consignee notification by any or all communications channel (fax, SITA etc.)

11. Own company requires…  Fulfill internal and external regulations  Profit  Competitiveness, growing business, tools to control  Low cost but good support and training  Economic operation  Good relationship with partners and authorities

12. BACH satisfy these needs, because:  Tailor made cut-over system, continuous development  CCS Hungary BACH ensures a higher service level, and less mistake consequents less cost and higher service charges made feasible  Capability for free, IP based communications  Special managers’ tools are built-in to follow the operations  Partners receive what they need – flexible approach, quick responses

13. Finally the employees require…  A tool that HELPS, easy to use  Good training, effective support  Warnings and checks to help avoiding mistakes  System procedures that fit local procedures  Local language

14. BACH satisfy these needs, because:  The work will be easier with more feeling of success! Multiple data entry avoided, the procedure is clear and easy to follow  Cut-over followed by on site training, re-training  Latest graphical IT technology is used to visualize process statuses and personalized warnings  Local IT company ensures at hand support  Final process will be created together with the user

15. IATA standard Electronic Data Interchange messages 1. FWB: Master Air Waybill dataFWB: Master Air Waybill data FHL: House Air Waybill dataFHL: House Air Waybill data FFR: Freight Reservation RequestFFR: Freight Reservation Request FFA: Freight Reservation AnswerFFA: Freight Reservation Answer FMA: Freight Reservation Request AcknowledgeFMA: Freight Reservation Request Acknowledge FNA: Syntactical or Semantical ErrorFNA: Syntactical or Semantical Error FVR: Flight Schedule and Availability RequestFVR: Flight Schedule and Availability Request FVA: Flight Schedule and Availability AnswerFVA: Flight Schedule and Availability Answer FIR: Flight Schedule RequestFIR: Flight Schedule Request FIA: Flight Schedule AnswerFIA: Flight Schedule Answer STM: Surface Transportation MovementSTM: Surface Transportation Movement SLS: Statistical Load SummarySLS: Statistical Load Summary

16. IATA standard Electronic Data Interchange messages 2. FSU: Freight Status UpdateFSU: Freight Status Update FSR: Freight Status RequestFSR: Freight Status Request FSA: Freight Status AnswerFSA: Freight Status Answer FSL: Multiple Status Update ListFSL: Multiple Status Update List FAD: Advice of DiscrepancyFAD: Advice of Discrepancy FDA: Discrepancy AnswerFDA: Discrepancy Answer FRP: Irregularity ReportFRP: Irregularity Report FBL: Freight Booked ListFBL: Freight Booked List UCM: ULD ControlUCM: ULD Control FFM: Airline Flight ManifestFFM: Airline Flight Manifest TXT: Free TextTXT: Free Text

17. Types of FSA/FSU status messages: OSI: No record foundOSI: No record found RCS: Received from shipperRCS: Received from shipper RCT: Received from carrierRCT: Received from carrier RCF: Arrived on flightRCF: Arrived on flight BKD: BookedBKD: Booked MAN: ManifestedMAN: Manifested DEP: DepartedDEP: Departed ULD: Partly or fully loaded ULDULD: Partly or fully loaded ULD TRM: To be transferred for shipperTRM: To be transferred for shipper TFD: Transferred for shipperTFD: Transferred for shipper NFD: Consignee notifiedNFD: Consignee notified AWD: Documents handed over to consigneeAWD: Documents handed over to consignee CRC: Customs notified – waiting for clearanceCRC: Customs notified – waiting for clearance CCD: Shipment customs clearedCCD: Shipment customs cleared DLV: Delivered to consigneeDLV: Delivered to consignee DDL: Delivered to doorDDL: Delivered to door

18. NON-IATA standard Electronic Data Interchange messages USR: Urgent Shipment RequestUSR: Urgent Shipment Request USA: Urgent Shipment AnswerUSA: Urgent Shipment Answer WAR: Warehouse Acceptance ReceiptWAR: Warehouse Acceptance Receipt BEA: Notification of arrivalBEA: Notification of arrival

19. Attributes that differs CCS Hungary BACH from other available systems: Uniquely wide EDI functionalityUniquely wide EDI functionality Bar coded technology supportBar coded technology support Built-in quality control systemBuilt-in quality control system Full functional customs interfaceFull functional customs interface Expandable, easy to tailor make, ready to interfaceExpandable, easy to tailor make, ready to interface Local technical supportLocal technical support Low price compared to competitors, good referencesLow price compared to competitors, good references Speaks local languageSpeaks local language You get cargo handling „know how” with the systemYou get cargo handling „know how” with the system Investment free solution based on monthly feeInvestment free solution based on monthly fee New versions, functions are free for usersNew versions, functions are free for users

20. Please let us assist you to offer for your customers a better, state of the art air cargo service with less effort. THANK YOU FOR YOUR VALUABLE TIME !