Project

A. General Information

1. Title

PAA e-AWB

2. Status of the project
Operating
3. Implementation period of the project/service:
From
2004
To
-
4. Website
https://www.paa.net
5. Geographical coverage
Regional: Asia and the Pacific
Participating countries: China, Hong Kong, China, Macao, China, Indonesia, Japan, Malaysia, Philippines, Republic of Korea, Singapore, Thailand
Hub Point: China
6. Participating agencies/entities of the project/service:
a. Development stage
Lead agencies/entities
PAA
Other participating agencies/entities
--
b. Operational stage
Lead agencies/entities (op)
PAA
Other participating agencies/entities (op)
CIECC – China, NACCS – Japan, InterCommerce – Philippines, Trade-Van– Chinese Taipei, KTNET – Korea, CrimsonLogic – Singapore, Tradelink – Hong Kong SAR, TEDMEV – Macau SAR, CAT Telecom – Thailand, EDI-I – Indonesia, Dagang Net – Malaysia
7. Main stakeholders/beneficiaries of the project
Transport
Customs
8. Business process category of the project
Regulatory/official control

B. Lessons Learned

9. Summary description of the project/service
Brief Summary

The Pan-Asian e-commerce Alliance's Electronic Air Waybill project aims at replacing traditional paper air waybills with electronic versions to facilitate air cargo exchanges through the secure and reliable transmission of trade and logistic data between the 15 members of the PAA.


 

a. Objective(s)
  • To enable secure and reliable transmission of trade and logistics data and documents 
  • To allow inter-connection of network services to provide e-Commerce transaction application services for the trade business community 
  • To create a Pan-Asian portal to enable global B2B connection and communication 
b. Business need for the project (background)
  • Freight forwarders were having difficulty in submitting Air Manifest to Customs due to advance filing scheme 
c. Business process covered*

Exchange of electronic AWB data　 

d. Overall architecture and functionalities*
  • Van to Van interconnectivity method 
  • ebXML for interconnectivity protocol 
  • PKI  
  • Proprietary PAA XML for messages 
e. Relevant document/figure
--
10. Documents and data exchanged via the project

AWB(Air Way Bill) 

11. Data models/databases, proprietary solutions, hybrid approaches
--
12. Main challenges faced during the project

Due to the change of regulation (submission of Air Manifest by origin country freight forwarder), the needs from the freight forwarder had decreased.

13. Lessons learned from the project

Cross-border trade data and document exchange are highly correlated with regulatory requirements.

14. Main benefit(s) of the project
Enhanced regulatory compliance*
Transaction Cost savings*
Transaction Time savings
Simplified process
14A. Elaborations/detailed description on benefits gained

In Korea, a freight forwarder of destination country had to report Air Manifest prior to arrival of airplane. Considering that most flight from South Asian economies are departing around midnight, the collection of AWB and capturing data for Air Manifest submission was a hard work for a freight forwarder. PAA had introduced a PAA AWB service collecting AWB data from the origin country freight forwarder and sending the data to a freight forwarder in importing country. Value added service was also provided to a freight forwarder in importing country which was to convert the AWB data into Air Manifest and automatically submitted it to Customs simplifying a manual submission work process of a freight forwarder.  

15. Technical/financial/capacity building/other assistance

None.

16. Future plan for expansion of the project
--
17. Other information or relevant references on the project
--
18. Relevant document regarding the project
--

C. Relevant Standards

19. Name(s) of any international, national legal instrument underpinning the project
PAA Club Agreement
20. Electronic message standard
20A. Electronic message standard supporting the project
XML:
- Other XML format: PAA XML
20B. Type of standard for electronic message applied for the project
Proprietary solution
 
Proprietary solution was applied because:
- No relevant international standard
- No need for standard because it is purely a commercial product
21. Technical communication standard
21A. Technical communication standard supporting the project
ebMS (ebXML)
21B. Type of technical communication standard applied for the project
International standard
22. Security-related standards*
22A. Security-related standard supporting the project
PKI
22B. Type of security-related standard applied for the project
Proprietary solution
 
Proprietary solution was applied because:
- No relevant international standard
23. Other Technical Information
23A. Interface developed for data exchange with an internal system
--
23B. Other technical implementation information
--