1 / 10

Background

Single Window Implementation Data Standardization Draft Recommendation 34 I nternational Trade Data System - ITDS Experience of United States. Background. Single Window systems require the use of standard data Same names, definitions, and coding Use of international standards

aileen-pierce
Download Presentation

Background

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Single Window ImplementationData StandardizationDraft Recommendation 34International Trade Data System - ITDSExperience of United States

  2. Background • Single Window systems require the use of standard data • Same names, definitions, and coding • Use of international standards • the United Nations Trade Data Elements Directory (UNTDED) • UN eDocs • Core Component Technical Specifications (CCTS) • WCO Data Model and Framework • UN EDIFACT • Revised Kyoto Convention

  3. Standardization Objectives • Eliminate redundancies and duplication • Standard set of data and messages for import, export and transit • To meet government requirements for goods, conveyances, and crews • Facilitate trade, enhance security, reduce costs, and provide more accurate and timely information

  4. Key ComponentsUN ECE Recommendation 33 pp. 15 - 17 • Strong Lead Agency (8.2) • Responsible for organizing, planning, undertaking – committing resources • Organization – Standardization Team • Knowledge of trade procedures • Information requirements • Data architects (coding, structure and modelling) • Agency liaison • Communication among traders and agencies • Policies, procedures and steps

  5. Overview of Steps • Capturing • Identifying and inventorying agencies’ requirements • Defining • The meaning – information conveyed by the data element – is more important than the name • Analysing • Identifying similar names and full understanding of the element • Reconciling • Agreement to use one name, common coding, and standard messaging

  6. Name Description/definition Type (A, N, AN, X) Domain (coding) Mode of Transport Process (import, export, transit) Category of use (cargo, conveyance, crew, equipment) Legal permission to view and/or collect Source of legal authority Expiry date of authority Data Source (trade or government) Trade Source (trader or carrier) Timing – when data is required Steps – Capturing Review forms and/or data model

  7. UNTDED Groupings • Group 1: Documentation references (0001 – 1699) • Group 2: Dates, times, period of time (2000 – 2799) • Group 3: Parties, addresses, places, countries (3000 – 3799) • Group 4: Clauses, conditions, terms, instructions (4000 – 4799) • Group 5: Amounts,charges, percentages (5000 – 5799) • Group 6: Measures, quantities, identifiers (6000 – 6799) • Group 7: Goods and articles (7000 – 7799) • Group 8: Transport modes, means, equipment (8000 – 8799) • Group 9: Other data elements (9000 – 9999)

  8. Example of Defining, Analyzing, and Reconciling Findings… Port of Unloading Port of Unlading Domestic Port of Unloading Domestic Port of Unlading Foreign Port of Unloading Foreign Port of Unlading Reconciled to: WCO DM Place of discharge UNTDED 3225 UN LOCODE UN ECE Recommendation16 Port code findings… 4 N Customs Proprietary 5 N Statistical Proprietary

  9. Other Considerations • Size of the standard data set • Large – maximum set of data to be provided • All modes, all goods, all processes • Consultation with the trade community • Note Recommendation 33, 8.3 – partnership between government and trade • Impact on legacy systems • Conversion/transition from proprietary to legacy • Legal Considerations • Privacy, trade secrets

  10. UNECE UN/CEFACT

More Related