International Trade and Business Processes Group Report to the UN/CEFACT Plenary http://www.uncefactforum.org/TBG/TBG%20Home/tbg_home.htm Chair: Jean-Luc Champion Vice-Chair: Pat Toufar 14th May 2007 Geneva

TBG’s Mandate The purpose of the TBG is to be responsible for the simplification of international trade procedures, business and governmental process analysis, and best practices, using the UN/CEFACT Modeling Methodology, where appropriate, to support the development of trade facilitation & e-Business standards. 14th May 2007 Geneva

TBG Summary Typical Forum attendance - 150 experts within 16 Working Groups Consistent, continuing participation however is less than 50% Many participants are sponsored by companies, trade associations and national governments but in all cases are expected to contribute as individual subject matter experts Since the last UN/CEFACT Plenary, International Trade and Business Processes Groups met during the 9th and 10th UN/CEFACT Forums Also to progress work forward, TBG Work Groups conducted numerous face to face interim meetings and more than 100 internet conferences and conference calls UN/CEFACT Forums facilitate collaborative meetings with Permanent Groups and Cross domain meetings with TBG Groups 14th May 2007 Geneva

TBG Working Groups TBG Working Groups can be categorized into three general areas: Buy - Ship – Pay Independent Domain Cross Domain

Buy – Ship - Pay Working Groups Develop the core work contributing to the deliverables of Trade Facilitation Business Process Models cover Procurement through Payment Contribute to the Core Components Libraries From these libraries UN/CEFACT builds syntax neutral e-Business standards Deliverables developed for UN/CEFACT Registry

Independant Domains Working Groups Industry centric work content Incorporates reusable Buy-Ship-Pay content Contributes domain specific content to the Core Components Libraries An example of the independent domain business area is Travel, Tourism and Leisure

Cross Domains Working Groups Harmonisation of Business Process Models from Buy-Ship-Pay and Independent Domains Harmonisation of syntax neutral Core Components from Domain Groups and External Liaisons

TBG Working Groups UN/EDIFACT Data Maintenance Requests reviewed by respective TBGs prior to approval and publishing in directory libraries Most TBG Groups working in concert with industry and government organisations develop cross industry business process models and identify data requirements for their respective domains Work Groups collaborate with each other on Cross Domain projects Enable Trade Facilitation for Governments, Industries and Companies by providing consistent harmonised e-Business standards

Working Groups within Buy-Ship-Pay TBG1-Supply Chain TBG2-UNeDocs and Digital Paper TBG3-Transportation TBG4-Customs TBG5-Finance TBG8-Insurance TBG15-International Trade Procedures TBG18-Agriculture TBG19-eGovernment

Working Groups within Independent Domains TBG6-Architecture, Engineering and Construction TBG9-Travel, Tourism and Leisure TBG12-Accounting and Audit TBG13-Environmental

Working Groups within Cross Domains TBG14-Business Process Analysis TBG17-Core Component Harmonisation

Buy – Ship - Pay In the following slides are explanations of each groups purpose and programme of work Working Groups within Buy – Ship - Pay TBG1-Supply Chain TBG2-UNeDocs and Digital Paper TBG3-Transportation TBG4-Customs TBG5-Finance TBG8-Insurance TBG15-International Trade Facilitation TBG18-Agriculture TBG19-eGovernment

TBG1-Supply Chain & eProcurement Purpose Supply chain and e-Procurement covers the Purchasing, Material Management and Payment areas http://www.uncefactforum.org/TBG/TBG1/tbg1.htm Programme of Work Cross Industry Invoice XML Schema Released Material Safety Data Sheet Cross Industry Remittance Advice Cross Industry Scheduling Process Cross Industry Delivery/Despatch and Receipt Advice Cross Industry Supply and Order Status Cross Industry Quotation eCatalogue Product Data Market Research/Information Process 14th May 2007 Geneva

Cross Industry Invoice (CII) Cross Industry Invoice development deliberately broad in design Intended as an “in all contexts” Schema Collected and harmonised many industry specific business requirements Developed the “CII’ including the harmonised requirements of two or more industry specific data requirements Intended to be used as the basis for a “sector specific context” invoice schema Automotive Industry contextualization underway Can be used in current form as validation mechanism for XML instances from any sector Customization of the schema is at the discretion of the trading partners Will be refined based on alignment work underway between Supply Chain and UBL UN/CEFACT looking at defining format for “Implementation Guides” for schema to help in understanding 14th May 2007 Geneva

TBG2-UNeDocs and Digital Paper Purpose Develop standards and best practice for the migration from paper to paperless trade in international supply chains Programme of Work UNeDocs Contribution to Cross Border Reference Data Model (CBRDM) Clickable Contracts http://www.uncefactforum.org/TBG/TBG2/tbg2.htm 14th May 2007 Geneva

TBG3-Transportation and Logistics Purpose Develop the eBusiness standards for Logistics planning and Transport. This covers operational movements of goods, administrative and governmental requirements and safety and security of freight movements. Programme of Work Collaborate on UNeDocs harmonisation Complete business requirements for IFTM International Forwarding Multimodal Transport Priorities for next business requirements: Booking, WayBill, Transport Status, Manifest http://www.uncefactforum.org/TBG/TBG3/tbg3.htm 14th May 2007 Geneva

TBG4-Customs Purpose Programme of Work Collaborate with World Customs Organisation (WCO) covering Business to Government (B2G), Government to Government (G2G) and Business to Business (B2B) requirements in cross border transactions. Programme of Work Cross Border Reference Data Model (CBRDM) http://www.uncefactforum.org/TBG/TBG4/tbg4.htm 14th May 2007 Geneva

TBG5-Finance Purpose Programme of Work Be responsible within the financial services area for the simplification of international trade procedures, business and governmental process analysis, and optimization of all information exchange standards. Programme of Work Cross Domain Collaboration on Invoicing, Remittance Advice and Accounting Token Continue development with SWIFT and ISO Technical Committee 68 Convergence with the International Standard UNIFI, Business Process Catalogue & Data (ISO 20022) and UN/CEFACT methodologies http://www.uncefactforum.org/TBG/TBG5/tbg5.htm 14th May 2007 Geneva

TBG6-Architecture Architecture, Engineering and Construction http://www.uncefactforum.org/TBG/TBG6/tbg6.htm 14th May 2007 Geneva

TBG7 - Statistics http://www.uncefactforum.org/TBG/TBG7/tbg7.htm 14th May 2007 Geneva

TBG8 - Insurance Purpose Programme of Work Global and cross sector, within the functional area of insurance business which includes the complete cycle of policy production, placement, claims, risk management and accounts between customers of insurance companies, the insurance companies and their agents and insurance brokers. It includes domestic and international environments, insurance and reinsurance, single company policies and co-insurance. Programme of Work Contribution of Data Dictionary Development of Insurance specific Core Components http://www.uncefactforum.org/TBG/TBG8/tbg8.htm 14th May 2007 Geneva

TBG9 - Travel and Leisure http://www. uncefactforum. org/TBG/TBG9/tbg9 TBG10 – Healthcare http://www.uncefactforum.org/TBG/TBG10/tbg10.htm TBG11 - Social Security, Employment and Safety http://www.uncefactforum.org/TBG/TBG11/tbg11.htm TBG12 - Accounting and Auditing http://www.uncefactforum.org/TBG/TBG12/tbg12.htm TBG13 – Environment http://www.uncefactforum.org/TBG/TBG13/tbg13.htm TBG14 - Business Process Group http://www.uncefactforum.org/TBG/TBG14/tbg14.htm 14th May 2007 Geneva

TBG15-International Trade Procedures Purpose Analyze, simplify, harmonize and align public and private sector practices, procedures and information flows relating to international trade transactions both in goods and related services. Programme of Work Development of new UNCEFACT Recommendations Nos. 34 and 35 Revision of existing UN CEFACT Recommendations Nos. 6, 11 and 12 Exploring use of UNCEFACT standards for coding Single Transport Contract http://www.uncefactforum.org/TBG/TBG15/tbg15.htm 14th May 2007 Geneva

TBG16 - Entry Point http://www.uncefactforum.org/TBG/TBG16/tbg16.htm TBG17 - Harmonization http://www.uncefactforum.org/TBG/TBG17/tbg17.htm 14th May 2007 Geneva

TBG18-Agriculture Purpose Programme of Work Develop and maintain Business Process Models, the Business Transaction Models, the semantics and the contents in a syntax neutral way that fulfil the requirements of the Agro – Food communities Programme of Work E-Certification Project eDAPLOS project http://www.uncefactforum.org/TBG/TBG18/tbg18.htm 14th May 2007 Geneva

TBG19-eGovernment Purpose Programme of Work Develop and maintain business scenarios and business transactions to facilitate the electronic delivery of services to citizens, businesses and government organizations. Programme of Work Common eGovernment data model development Investigate interest in Greenhouse Gas emission and Carbon Trading transactions (GHGCT) processes and standards eArchiving http://www.uncefactforum.org/TBG/TBG19/tbg19.htm 14th May 2007 Geneva

Working Groups within Independent Domains TBG6-Architecture, Engineering and Construction TBG9-Travel, Tourism and Leisure TBG12-Accounting and Audit TBG13-Environmental

TBG6-Architecture, Engineering & Construction Purpose Responsible to coordinate and propose new developments and maintenance in the area of Architecture, Engineering and Construction Industry (AEC). Programme of Work eTendering for Construction Release Candidate Schema Released // ODP step 6: the implementation verification for two different existing systems in Japan was successfully completed and another has been successfully completed by Korea. Further reviews by India, and European Countries (Germany, France and United Kingdom) will be made. Project Schedule and Cost Performance Management to be released with CCL 07A in June. Contract Financial Execution Management in progress http://www.uncefactforum.org/TBG/TBG6/tbg6.htm 14th May 2007 Geneva

TBG9-Travel, Tourism & Leisure Purpose To support and promote international business activities related to the exchange of travel industry data. Programme of Work Small Scaled Lodging House data requirements included in CCL 06B Develop Core Components for documenting the business data in travel, tourism and leisure business functionality. http://www.uncefactforum.org/TBG/TBG9/tbg9.htm 14th May 2007 Geneva

TBG12-Accounting & Audit Purpose The accounting and auditing domains and financial reporting. The exchanges are between the accountants and certified accountants, the auditors, and the enterprises. Internal or external financial reporting towards the economic partners of the enterprises, the private and public collection bodies. Programme of Work Development of Business Process Models to fulfill accounting requirements for Accounting Entry Accounting Ledger Accounting Trial Balance Accounting Reporting Accounting Chart of Accounts http://www.uncefactforum.org/TBG/TBG12/tbg12.htm 14th May 2007 Geneva

TBG13-Environmental Purpose Programme of Work To support and promote both international and regional cooperation activities related to environmental data exchange. Programme of Work To develop a suite of UN/EDIFACT compliant messages that will support a completely electronic process of notification and tracking under national and international law associated with ECS import/export, including all transactions among the competent environmental authorities, shippers (or exporters), consignees (or importers), and competent customs authorities. Continued work on business requirements for Waste Movement from original UMM models. http://www.uncefactforum.org/TBG/TBG13/tbg13.htm 14th May 2007 Geneva

Working Groups within Cross Domains TBG14-Business Process Analysis http://www.uncefactforum.org/TBG/TBG14/tbg14.htm TBG17-Core Component Harmonization http://www.uncefactforum.org/TBG/TBG17/tbg17.htm

TBG14-Business Process Analysis Purpose Responsible for defining the International Supply Chain model to present the various processes and parties involved within the international supply chain in a simplified way. Programme of Work Work with the buy-ship-pay and domain groups to harmonise business processes models Build a cross domain catalog of common business processes within the International Supply Chain framework. http://www.uncefactforum.org/TBG/TBG14/tbg14.htm 14th May 2007 Geneva

TBG17-Core Component Harmonisation Purpose Responsible for consistency and harmonisation of core components across business domains and sectors, contributing to a concise and well-defined glossary of business terms, business data semantic definitions, and structuring of data exchanges. Programme of Work Harmonisation of TBG and External Liaison submissions Results of Deliverables are content of Core Component Libraries http://www.uncefactforum.org/TBG/TBG17/tbg17.htm 14th May 2007 Geneva

Overview An Introduction to Core Components Trade and Business Processes Group - Harmonization (TBG17) Purpose Membership Submission & Acceptance Process Harmonization Process Publication & Syntax Solutions Results Commitment Needs 14th May 2007 Geneva

Basic building block – a data element No business context Types Core Components Basic building block – a data element No business context Types ACC = Aggregate Core Component Like a segment in X12 or EDIFACT BCC = Basic Core Component Like a data element in X12 or EDIFACT ASCC = Associate Core Component Connects two ACCs Like a Party to an Address Just a little education, for those of you who haven’t had the joy of working on or reading the CCTS. I hope that you’re familiar with EDI? An ACC, or Aggregate Core Component is like a segment, or a segment group, or a loop. It’s a collection of business data that logically works together. But without the business context. Within an ACC, are BCCs, Basic Core Components. These are like data elements. Think back on the example we saw earlier. The Object Class was Address; we have an ACC for Address. And within it are a lot of BCCs; the ones that you would all be able to figure out. Street, City, PO Box, and so on. 14th May 2007 Geneva

Business Information Entities Built from Core Components Have Business Context (8 possible) Like Trade, Purchasing, Switzerland Types ABIE = Aggregate Business Information Entity Built from an ACC Qualified with a meaningful term BBIE = Basic Business Information Entity Built from a BCC ASBIE= Association Business Information Entity Connects two ABIEs Built from an ASCC Just a little education, for those of you who haven’t had the joy of working on or reading the CCTS. I hope that you’re familiar with EDI? An ACC, or Aggregate Core Component is like a segment, or a segment group, or a loop. It’s a collection of business data that logically works together. But without the business context. Within an ACC, are BCCs, Basic Core Components. These are like data elements. Think back on the example we saw earlier. The Object Class was Address; we have an ACC for Address. And within it are a lot of BCCs; the ones that you would all be able to figure out. Street, City, PO Box, and so on. 14th May 2007 Geneva

All BCCs and BBIEs have a data type Data Types All BCCs and BBIEs have a data type Such as date, code, measure BBIEs can have a qualified data type Can point to codes lists maintained by UN or ISO or an industry group Such as certain codes from Recommendation 20 – Units of Measure, or ISO Country Codes Just a little education, for those of you who haven’t had the joy of working on or reading the CCTS. I hope that you’re familiar with EDI? An ACC, or Aggregate Core Component is like a segment, or a segment group, or a loop. It’s a collection of business data that logically works together. But without the business context. Within an ACC, are BCCs, Basic Core Components. These are like data elements. Think back on the example we saw earlier. The Object Class was Address; we have an ACC for Address. And within it are a lot of BCCs; the ones that you would all be able to figure out. Street, City, PO Box, and so on. 14th May 2007 Geneva

Each dictionary entry name has three parts Naming Each dictionary entry name has three parts Object Class – like Address or Person Property Term – like Street or Name Representation Term – like Code or Text Based on ISO 11179 Put together like this Object Class. Property. Representation Address. Street. Text Each Core Component dictionary entry name has three parts, an Object Class, a Property Term, and a Representation Term. They are put together, separated by a period and a space. In some cases, each part of the CC is obvious, like this one. 14th May 2007 Geneva

assign a globally unique ID Once approved, we assign a globally unique ID Example We use the Oxford English Dictionary Unique ID Dictionary Entry Name CC Type Definition UN00000010 Address. Details ACC The information relevant to a specific address. UN00000014 Address. Postcode. Code BCC The postal code of the address. UN00000033 Address. Street Name. Text A name of a street or thoroughfare. UN00000013 Address. City Name. Text The name of the city, town or village of this address. UN00000203 Address. Country. Identifier A unique identifier of a country, e.g. as specified in ISO 3166 and UNECE Rec 3. UN00000204 Address. Type. Code The type of this address such as business address or home address. These are just a few of the columns from the CC submission spreadsheet. Trust me, there loads more columns to fill out for a submission! I picked Address. You see Address. Details; we chose that format for all the ACCs. And under it you see just a few of the BCCs that belong to Address. For definitions, we use the Oxford English Dictionary. And for each Core Component, we assign a unique identifier. This identifier is globally unique, and will be stored, with all the other CC information, in a global repository. 14th May 2007 Geneva

ABIE: Store_ Address. Details Example of an ABIE ABIE: Store_ Address. Details BBIE: Store_ Address. Street Name. Text BBIE: Store_ Address. City Name. Text BBIE: Store_ Address. Country. Identifier qDT for Country. Identifier List of countries from ISO 3166 where the organization has stores Context Retail 14th May 2007 Geneva

Core Component Harmonization Purpose Core Component Harmonization Goal: to provide a consistent and harmonized set of core components across business domains and sectors, contributing to a concise and well-defined glossary of business terms, business data semantic definitions, and structuring of data exchanges. 14th May 2007 Geneva

Who we are Other TBGs Liaisons Unlike other UN/CEFACT TBGs, TBG17 members can represent groups Members represent Other TBGs eg Insurance (TBG8) Liaisons ECOM EDIFICE GS1 JAI OAGi SWIFT UBL USG 14th May 2007 Geneva

Submission & Acceptance Process Submission from TBG or liaison member BRS and/or RSM and/or Class Diagram Spreadsheet or file Core Components Business Information Entities Maybe Qualified Data Types An editor performs technical QA When submission is technically correct, added to work program The submitter describes the process and reviews the diagrams 14th May 2007 Geneva

Harmonization Based on priorities (CEFACT Plenary/FMG/Submission Date) TBG17 reviews submitted Core Components Across submissions when similar business meaning Review each CC for completeness, good definition and name May make changes, with agreement from submitter If any changes made Return submission Submitter (or team) updates BIEs based on TBG17 changes BIEs and qDTs harmonized by TBG17 14th May 2007 Geneva

Publication and Syntax Solutions When whole submission is harmonized and approved TBG17 sends to ICG For audit For inclusion in next UN/CEFACT Core Component Library If the submitter requests a UN/CEFACT syntax solution, the TBG Project Manager sends the appropriate documents to ATG1 and/or ATG2 for message development. 14th May 2007 Geneva

Results Published in CCL 06B Ready to send for CCL 07A eTendering Cross Industry Invoice Small Scale Lodging House Ready to send for CCL 07A Project Scheduling and Cost Performance Management Harmonized for CCL 07B Product Registration Material Safety Date Sheet Cross Border Transport (in process) 14th May 2007 Geneva

Harmonization Meetings and Calls Commitment Harmonization Meetings and Calls In one year (13 December 2005 to 5 December 2006) 37 three-hour virtual meetings 4 five-day face-to-face meetings Not included: Submission specific conference calls Library Development Travel 14th May 2007 Geneva

CC Harmonization Needs Current Members More time allocated by management Ability to attend all face-to-face meetings Additional Resources Expertise in: Documentation Specific Domains Core Components 14th May 2007 Geneva

Resources skill set Funding Subject matter experts Tools Domain Modelling Technical developers Project Management skills Funding Tools Registry development 14th May 2007 Geneva