1. UNeDocs – Vision for Cross- Border Data Exchange From Stoneage to Digital World

2. May 2006A Vision for Cross-Border Data ExchangeSlide 2 UNeDocs Process Scope Buy Pay Ship Prepare for export Import Prepare for import Transport Export Commercial Procedures Establish sales contract Order goods Advise on delivery Request payment Transport Procedures Establish transport contract Collect, transport and deliver goods Provide waybills, Goods receipts, etc. Regulatory Procedures Obtain im/export licenses etc. Provide Customs Declarations Provide cargo Declarations Apply security measures Clear goods Financial Procedures Provide credit rating Insurance Execute payment Issue statements Cross Border - International Trade Reference Model

3. May 2006A Vision for Cross-Border Data ExchangeSlide 3 To remove paper you have to start from paper

4. May 2006A Vision for Cross-Border Data ExchangeSlide 4 A Combined Approach Recipient prints and stores Paper Documents Electronic Document Exchange XML or UN/EDIFACT Electronic Edit Form <n:Invoice xmlns:n="urn:oasis:names:tc:ubl:Invoice:1.0:0.70" xsi:schemaLocation="urn:oasis:names:tc:ubl:Invoice:1.0 :0.70 UBL_Library_0p70_Invoice.xsd"> token 2003-02-14 Bills Microdevices Joes Office Supply 1 5 Pencils, box #2 red … to cover the needs of both paper view and application Recipient processes the content into applications

5. May 2006A Vision for Cross-Border Data ExchangeSlide 5 A Combined Approach Paper Document aligned to UN Layout Key Electronic Document Exchange XML or UN/EDIFACT Electronic Edit Form <n:Invoice xmlns:n="urn:oasis:names:tc:ubl:Invoice:1.0:0.70" xsi:schemaLocation="urn:oasis:names:tc:ubl:Invoice:1.0 :0.70 UBL_Library_0p70_Invoice.xsd"> token 2003-02-14 Bills Microdevices Joes Office Supply 1 5 Pencils, box #2 red … to cover the needs of both classic and digital paper

6. May 2006A Vision for Cross-Border Data ExchangeSlide 6 The ‘old fashioned‘ paper form knows different sizes and formats (Letter, A4) knows continuation pages, a reverse and splitting of data layout elements may have a semantic meaning (colours) has background master data (titles, standing clauses, box titles, watermarks, holograms), even multilingual likes clear names rather than codes is flat and hides the deeper structuring of data is flexible, simple and allows different data in a box may allow annotations and non-requested data Can be easily signed and just as easily falsified

7. May 2006A Vision for Cross-Border Data ExchangeSlide 7 UN Layout Key Cross-Sector Transaction Data Sector Specific Detail e.g. order line items, goods items... Document Function Specific

8. May 2006A Vision for Cross-Border Data ExchangeSlide 8 UNLK Form Families Trade Documents – Quotation, Order, Invoice etc. Materials Management Documents – Despatch Advice, Pick List, Packing List etc. Transport Documents – Bill of Lading, Shipping Instructions etc. Customs Documents – Export, Import, Transit Declarations, Cargo Reports etc. Other Regulatory Documents – Cert of Origin, DGN etc.

9. May 2006A Vision for Cross-Border Data ExchangeSlide 9 Align international Cross Border Data across Customs – Regulatory Documents – Transport and Trade Provide smooth migration path towards Digital Paper Increased semantic interoperability through reuse of UN/CEFACT Core Component Library Electronic successor of the paper-based UN Layout Key (the UN Rec No 1 Unsung Hero) Combining ISO 15000-5 Core Components, EDI, XML, document presentation and box completion guidelines Easy migration to newer versions Customization methodology for the integration of new user requirements UNeDocs Objectives

10. May 2006A Vision for Cross-Border Data ExchangeSlide 10 Project Deliverables · · · · A Business Process Model illustrating where the UNeDocs documents fit into the operation of the International Supply Chain based on the UNCEFACT International Supply Chain Reference Model. A ISO 15000 Part 5 compliant Common Data Model based on candidate or published UNCEFACT Core Components that are linked to the UNTDED/ISO 7372. Methodology for the presentation of data contained in electronic data exchanges onto electronic or paper forms and the update of UNLK to become eUNLK. For each document the project will develop: o A class diagram and document structure o The paper and electronic, re-usable layout description of the document based on the UN Layout Key o Box Completion Guideline o XML profiles o UN/EDIFACT message implementation guide

11. May 2006A Vision for Cross-Border Data ExchangeSlide 11 Status UNeDocs Current focus: Integrated data model Finishing the migration to the UN/CEFACT Core Component Library v 06A Submit remaining semantic pieces of data to UN/CEFACT Implementing the Customisation methodology XML schema production using the UN/CEFACT Schema rules (June)... Working with Customs... data

12. May 2006A Vision for Cross-Border Data ExchangeSlide 12 Customized Implementation Projects Approved by UN/CEFACT ITAIDE (EU Customs & Taxation, interoperability research) Draft Project Proposals UNeDocs Senegal (Kenya..) UNeDocs Pakistan Under development UNeDocs Malaysia, UNeDocsUK (SITPRO), Negotiable BoL for the Oil sector, IATA

13. May 2006A Vision for Cross-Border Data ExchangeSlide 13 Experiencing UNeDocs eForms techniques Adobe, Microsoft (see also Dakosy example) National Implementation UNeDocsUK (SITPRO) Mapping UNeDocs and WCO data model UNeDocs Technical Workshop Kuala Lumpur / Vancouver (Export declaration)

14. May 2006A Vision for Cross-Border Data ExchangeSlide 14 Experiencing UNeDocs

15. May 2006A Vision for Cross-Border Data ExchangeSlide 15 UNeDocs... Customs data are missing - Simply copy WCO? Re-invent? Collaborate with shared ownership?

16. May 2006A Vision for Cross-Border Data ExchangeSlide 16 WCO DM... Trader, Transport, OGA data are missing -

17. May 2006A Vision for Cross-Border Data ExchangeSlide 17 Do WCO DM and UNeDocs fit together? ? Similiar concepts: WCO Overall Model and UNeDocs Master Document Same ISO and UN Standards are used (TDED ISO 7372, UN/Layout Keys, UN/EDIFACT, ISO 15000-5 Core Components...) Both are about Global Cross Border Trade Both have to manage digital and classic paper Both are aware of the conventional and regulatory requirements in Global trade Both are projects of International Organizations (UN, WCO) Data: Complementary....

18. May 2006A Vision for Cross-Border Data ExchangeSlide 18 UN Trade Data Element Directory UNeDocs – International Standards Aspects Slide 18

19. May 2006A Vision for Cross-Border Data ExchangeSlide 19 UN Layout Mapping Example 2280 Transport Means. Actual Departure. Date Time Date and or time of the departure of means of transport Flight Date, Sailing Date an..17 UNLK: L 17, P 16 UID Name Definition Synonym Repr. Mapping UNeDocs – International Standards Aspects Slide 19 See „UN Layout Key for Trade Documents“

20. May 2006A Vision for Cross-Border Data ExchangeSlide 20 The differences are complementary too WCO DM DEFINES data sets and messages UNeDocs - is an integrating project and only REUSES - adds eForm views and technologies - provides Customization Methodology - developed process oriented structuring of data and documents ? e.g. reuse of the Core Components of UN/CEFACT/TBG3 Transport Maritime Transport/SMDG/Rail/Land transport

21. May 2006A Vision for Cross-Border Data ExchangeSlide 21 UNeDocs...Customs - If we are serious then there is no other chance than to align and collaborate!

22. May 2006A Vision for Cross-Border Data ExchangeSlide 22 UN/CEFACT expertise

23. May 2006A Vision for Cross-Border Data ExchangeSlide 23 No data redundancy... “ If information is electronic, then individual data elements should only be submitted once. ” ( Background paper...) Related to ONE document/procedure: example Customs Import procedure: 1of 2 step and 2 of 2 step Related to a Business Case with a SET of Documents? How often redundant data shall be received and checked...... E.g. Consignee?  New types of documents

24. May 2006A Vision for Cross-Border Data ExchangeSlide 24 Dataset and Document Ownership Forms or Convention Stakeholders plus UN/CEFACT Country Delegations 1st 2nd 3rd UN/CEFACT Forum Trade & Business Group Digital Paper Workgroup (TBG2) UneDocs UNeDocs National, Regional or Industry Projects such as UNeDocsUK led by SITPRO

25. May 2006A Vision for Cross-Border Data ExchangeSlide 25 Maintenance and ownership “ a mechanism through which it [the CRDM] can be developed and maintained. ” Stable, trackable and trustable maintenance procedures needed Stakeholders have to be responsible for their data/documents – on their reuse level Maintenance owners Updates and intermediate versions for reusers

26. May 2006A Vision for Cross-Border Data ExchangeSlide 26 Interoperability - Value of the CRDM NOBODY changes his legacy application just because of a Data Model or any XML schemas NO single grammar for the exchange of cross border trade related documents Use of the CRDM as a Canonical model where everything is maped against and as a source for XML

27. May 2006A Vision for Cross-Border Data ExchangeSlide 27 The domain view of a Common Reference Data Model Trade Data Insurance TransportMaterials Management Customs Data Other Govt. Agencies International Trade Single Window Payment

28. May 2006A Vision for Cross-Border Data ExchangeSlide 28 UN/CEFACT CC Library CRDM ABIE Library Libraries for Single Windows It is time for new types of documents – not just mirrors of the existing paper world. A reuse concept based on the UN/CEFACT Core component Library is the foundation for new document types whilst also providing legacy support and a migration path between the two. TradeInsurance Customs & OGAs Transport Materials Management

29. May 2006A Vision for Cross-Border Data ExchangeSlide 29 Common Reference Data Model - The interoperability platform for Single Window implementations The CRDM is based on the concept of a cross-domain Trade, Transport and Customs data model from which any document used within the international purchase and supply chain can be derived. This data model, which is based on international standards, allows users to produce documents in paper, EDI or XML format. The main benefit of the CRDM is that it provides countries with an “ out of the box ” option for International Trade Single Window projects which is aligned to international standards. The implementation of the CRDM does not require a detailed understanding of all of the standards on which it is based. Since the CRDM data model is a superset of data elements used within the international purchase and supply chain, it can be easily tailored to user requirements yet remain internationally aligned.

30. May 2006A Vision for Cross-Border Data ExchangeSlide 30 Customization Methodology how to include regional, national etc requirements

31. May 2006A Vision for Cross-Border Data ExchangeSlide 31 Lessons learnt… Almost no EDI standard has ever been used as published Implementation Guidelines have always been developed, where users defined their own way, data and layouts Examples - RosettaNet designed XML Rnet Implementation Guidelines (RIGs) - The UBL derived XML of the Danish Government is documented by Guidelines which consist of XSD schema, Word files with semantic clarifications, restrictions and Excel files with detailed field information

32. May 2006A Vision for Cross-Border Data ExchangeSlide 32 Lessons learnt… If the standard does not allow necessary things, then the standard will be misused It is impossible to foresee everything Not everybody can give his IP Rights away A well used standard lives and there are changes, amendments, extensions etc

33. May 2006A Vision for Cross-Border Data ExchangeSlide 33 Consequently… Customization has to be allowed A customization methodology has to be set up from the very beginning A user feedback must be organized There is a need to respect the economics and the political interest of the users Maintenance procedures needed THERE IS REALITY OUTSIDE OF A STANDARD!

34. May 2006A Vision for Cross-Border Data ExchangeSlide 34 Customization The adoption of an eStandard to meet specific requirements This refinement may happen by extension or restriction or combination of both This includes textual clarifications, codes and business rules/dependencies May include a refinement of methodologies

35. May 2006A Vision for Cross-Border Data ExchangeSlide 35 Customization Methodology how to include regional, national etc requirements UNeDocs Change Request UNeDocs Core Components Based on UNeDocs Business Data and Documents Core Component Library UNeDocs Core Contextualized Documents UNeDocs Regional, National Guidelines/Applications UNeDocs Industry, Company Guidelines/Applications

36. May 2006A Vision for Cross-Border Data ExchangeSlide 36 Customization UNeDocs Change Request UNeDocs Core Components Based on UNeDocs Business Data and Documents Core Component Library UNeDocs Core Contextualized Documents UNeDocs Regional, National Guidelines/Applications UNeDocs Industry, Company Guidelines/Applications

37. May 2006A Vision for Cross-Border Data ExchangeSlide 37 Guideline extension and restriction (draft) UNeDocs Change Request UNeDocs Core Components Based on UNeDocs Business Data and Documents Core Component Library UNeDocs Core Contextualized Documents (agreed) extensions must be included into UNeDocs Business Data and Documents Restrictions only! Supplementary semantic explanations

38. May 2006A Vision for Cross-Border Data ExchangeSlide 38 Core Standard extension and restriction (draft) UNeDocs Business Data and Documents UNeDocs Core Contextualized Documents A subset of the UNeDocs Business Data and Documents with that data which is considered to be core for UNeDocs Restrictions only! Supplementary semantic explanations

39. May 2006A Vision for Cross-Border Data ExchangeSlide 39 What is ebXML? Questions? Dill@gefeg.com  http://www.unece.org/cefact/forum_grps /tbg/tbg2_edocs/tbg2_edocs.htm  www.unedocs.org