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

UNeDocs – Vision for Cross-Border Data Exchange

From Stoneage to Digital World

May 2006 A Vision for Cross-Border Data Exchange Slide 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


To remove paper you have to start from paper


A Combined Approach

Recipient prints and stores Paper Documents

Electronic Document ExchangeXML or UN/EDIFACT

Electronic Edit Form

<?xml version="1.0" encoding="UTF-8"?><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.70UBL_Library_0p70_Invoice.xsd">

<cat:ID>token</cat:ID><cat:IssueDate>2003-02-14</cat:IssueDate><n:TaxPointDate>2003-02-14</n:TaxPointDate><cat:BuyerParty>

<cat:PartyName><cat:Name>Bills

Microdevices</cat:Name></cat:PartyName>

</cat:BuyerParty><cat:SellerParty>

<cat:ID/><cat:PartyName>

<cat:Name>Joes Office Supply</cat:Name>

</cat:SellerParty><cat:InvoiceLine>

<cat:ID>1</cat:ID><cat:InvoicedQuantity

unitCode="token">5</cat:InvoicedQuantity><cat:Item>

<cat:Description>Pencils, box #2 red</cat:Description>

</cat:Item></cat:InvoiceLine>

</n:Invoice>

… to cover the needs of both paper view and application

Recipient processes the content into applications


A Combined Approach

Paper Documentaligned to UN Layout Key

Electronic Document ExchangeXML or UN/EDIFACT

Electronic Edit Form

<?xml version="1.0" encoding="UTF-8"?><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.70UBL_Library_0p70_Invoice.xsd">

<cat:ID>token</cat:ID><cat:IssueDate>2003-02-14</cat:IssueDate><n:TaxPointDate>2003-02-14</n:TaxPointDate><cat:BuyerParty>

<cat:PartyName><cat:Name>Bills

Microdevices</cat:Name></cat:PartyName>

</cat:BuyerParty><cat:SellerParty>

<cat:ID/><cat:PartyName>

<cat:Name>Joes Office Supply</cat:Name>

</cat:SellerParty><cat:InvoiceLine>

<cat:ID>1</cat:ID><cat:InvoicedQuantity

unitCode="token">5</cat:InvoicedQuantity><cat:Item>

<cat:Description>Pencils, box #2 red</cat:Description>

</cat:Item></cat:InvoiceLine>

</n:Invoice>

… to cover the needs of both classic and digital paper


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


UN Layout Key

Cross-Sector Transaction Data

Sector Specific Detail e.g. order line items, goods items ...

Document Function Specific


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.


• 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


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 structureo The paper and electronic, re-usable layout description of the document based on the UN Layout Key o Box Completion Guidelineo XML profiles o UN/EDIFACT message implementation guide


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


Customized Implementation ProjectsApproved by UN/CEFACTITAIDE (EU Customs & Taxation, interoperability

research)

Draft Project ProposalsUNeDocs Senegal (Kenya..)UNeDocs Pakistan

Under developmentUNeDocs Malaysia, UNeDocsUK (SITPRO), Negotiable

BoL for the Oil sector, IATA


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)


Experiencing UNeDocs


UNeDocs... Customs data are missing

--

• Simply copy WCO?• Re-invent?• Collaborate with shared

ownership?


WCO DM... Trader, Transport, OGA data are

missing

--


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....


UN Trade Data Element Directory

UNeDocs – International Standards AspectsSlide 18


UN Layout Mapping Example

2280 Transport Means. Actual Departure. Date TimeDate and or time of the departure of means

of transportFlight Date, Sailing Datean..17UNLK: L 17, P 16

UIDNameDefinition

SynonymRepr.Mapping

UNeDocs – International Standards AspectsSlide 19

See „UN Layout Key for Trade Documents“


The differences are complementary too

WCO DM DEFINES data sets and messagesUNeDocs - 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


UNeDocs...Customs

--

If we are serious then there is no other chance than to align and collaborate!


UN/CEFACT expertise

TBG1 Supply ChainTBG2 Digital PaperTBG3 TransportTBG4 CustomsTBG5 FinanceTBG6 Architecture & ConstructionTBG7 StatisticsTBG8 InsuranceTBG9 Travel, Tourism & LeisureTBG10 HealthcareTBG11 Social ServicesTBG12 Accounting & AuditTBG13 Environment ProtectionTBG14 Business Process AnalysisTBG15 International Trade ProceduresTBG17 HarmonisationTBG18 AgricultureTBG19 e-government

UN/CEFACT TBG Working Groups


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 stepRelated 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


Dataset and Document Ownership

Forms or Convention Stakeholdersplus UN/CEFACT Country Delegations

1st

2nd

3rd

UN/CEFACT Forum Trade & Business GroupDigital Paper Workgroup (TBG2) UneDocs

UNeDocs National, Regional or Industry Projects such as UNeDocsUK led by SITPRO


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


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


The domain view of a Common Reference Data Model

Trade Data

Insurance

TransportMaterialsManagementCustoms Data

Other Govt. Agencies

International TradeSingle Window

Payment


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.

Trade InsuranceCustoms &

OGAsTransportMaterials

Management


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.


Customization Methodologyhow to include regional,

national etc requirements


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


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


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!


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


Customization Methodologyhow 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



Customization



Based on




UNeDocs Regional, National


UNeDocs Industry, Company



Guideline extension and restriction (draft)



Based on




(agreed) extensions must be included into UNeDocs Business

Data and Documents

Restrictions only!Supplementary semantic

explanations


Core Standard extension and restriction (draft)



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


What is ebXML?

Questions?

[email protected]

http://www.unece.org/cefact/forum_grps/tbg/tbg2_edocs/tbg2_edocs.htmwww.unedocs.org

mailto:[email protected]

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

Documents

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