Electronic Business XML Copenhagen Sue Probert Senior Director, Document Standards, Commerce One Vice-Chair, UN/CEFACT Forum’s International Trade & Business

Electronic Business XMLCopenhagen

Sue Probert

Senior Director, Document Standards, Commerce One

Vice-Chair, UN/CEFACT Forum’s

International Trade & Business Processes Group

November 7, 2002

ebXML Core Components and Business Processes

UN/CEFACT


November 7, 2002ebXML CC & BP Report - 2

Syntax Neutral Intl. eBusiness

Framework

Architecture, Business Processes

and Core Components

Transport, Routing & Packaging,

Partner Profile & Agreements

and Registry & Repository

Global XMLTechnical

Framework

eb XML



Introduction to UN/CEFACT Forum

UN/CEFACT has five Groups (TBG, ICG, ATG, TMG & LG) which meet collectively as the UN/CEFACT Forum.

The UN/CEFACT Forum is driven by the business and trade facilitation needs of government and industry.

The Business Group (TBG) is the focal point for the expression of those needs

The other Groups are operational/support Groups addressing technology, implementation and legal issues.

Forum Co-ordination Team (FCT) is responsible for:

Logistical co-ordination of the Forum meeting requirements

Project management



UN/CEFACT Forum Structure

Business Processes & Trade Facilitation (TBG)

Technologies & Methodologies (TMG)

InformationContent (ICG)

Applied (ATG) Technologies

Legal (LG)

Forum Co-ordination Team (FCT)



ebXML phase 2

UN/CEFACT OASIS

ebXML CC & BP Tech Specs

TBGTMG

TRP TC

RegRep TC

UBL TC

Syntax NeutralBP Models & CCs

XSD Design Rules,Document Schemas

And Context Assembly

Forum

ebXML JCC

Joint Architecture

ATG

Syntax SolutionsEDIFACT & XML

ebXML Messaging

ebXML Registry & Repository

CPPA TC

ebXML Partner Profiles& Agreements



Legend:UMM = UN/CEFACT Modeling Methodology

BCP = Business Collaboration Protocol

BCPMC = Business Collaboration Patterns and Monitored Commitments

BEL = Business Entity Library

BPSS = Business Process Specification Schema

BRIM = Business Registry Information Model

BPIM = Business Process Information ModelExchange Schema

CBPC = Common Business Process Catalog

CC = Core Component Specification

CPPA = OASIS ebXML CPPA – Partner Profiles & Agreements

MSG = OASIS ebXML Messaging

REG = OASIS ebXML Registry & Repsoitory

CCBELBCPS BCPMC

BRIM

CBPC BPIMCPPACPPA MSGMSG

REGREG

BPSS

UMM

ebXML Methodology Architecture



ebXML Business Processes

September 2002 BPWG set up within the UN/CEFACT Forum’s TMG – chaired by David Welsh

BPWG brings together the former ebTWG projects:

BCPMC - Business Collaboration Patterns and Monitored Commitments BCP - Business Collaboration Protocol

BEL - Business Entity Library

BPIM - Business Process Information Model Exchange Schema BPSS - Business Process Exchange Schema

BRIM Business Registry Information Model

CBPC Common Business Process Catalog



Example BP Catalog Scenario



Example of BP Definition

Name Order Product Identifier D-P&SI-1,U-Order-2-4 Actors Customer, Supplier Description The Customer has a need for a product and places an Order with the

Supplier under an established Contract or Framework Agreement. The Supplier receives the order and replies with a response.

Pre-Conditions Contract or Framework agreement is in place. (Contract=InPlace, Order=Pending)

Post-Conditions Order has been confirmed, rejected or cancelled (Order=Confirmed or Order=Rejected or Order=Cancelled)

Scenario Starts when Customer recognises the need for specific quantities of one or more products and decides to place an order with a particular Supplier. Customer raises and send an order containing one or more order

lines to Supplier Supplier receives order and confirms its acceptance or rejection. Customer may subsequently cancel the order with Supplier Ends when Customer has received either Order Acceptance or Order Rejection or if Customer sends Order Cancellation



Example BP Catalog Entries



ebXML Core Components Methodology

September 2002 CCWG set up within the UN/CEFACT Forum’s TMG – chaired by Mary Kay Blantz

CCWG brings together the former ebTWG projects:

CCTS – Core Component Technical Specification V1.85 out for public review under UN/CEFACT Open Development Process End of comment period November 22nd

Available from www.unece.org/cefact/ Comments will be processed at interim meeting in early December

CCSD – Core Component Supplementary Documents Boeing spare part procurement example completed EAN.UCC despatch advice example under development CC Primer under development



• ‘Discovery’ and Analysis methodologiesLibrary of Core Components

• Naming Conventions & RulesGlobal Semantic Vocabulary

• Context Classification of context drivers

• Extension Methodology Describe ways in which components are reused

Core Component Technical Specification



Core Component Hierarchy

Global Semantics Vocabulary

CC Types

Basic & Aggregate CCs

Basic & Aggregate BIEs

Buyer

Buyer GLN

Seller

Sel ler GLN

(f rom Use Case View)

Ship_to

Ship_to GLN

(f rom Use Case View)

Carrier

Carrier GLN1

1 1

10.*0.* 0.*

0.*

Reference

Purchase Order IDPurchase Order DateOption - Consignment Number

Despatch Advice

Despatch Advise IDPick_Up_Date_TimeDelivery_Date_Time

Quantity

1

1..*

1

Logistics Unit

SSCC

1

1

1..*

Item ID

GTINTransactionItemData - Expiration DateTransactionItemData - Lot NumberTransactionItemData - Sell by DateSpecific Item Date - SSCCFMCG Extensions

1

1

1

1

0..1

Despatch Item

Despatch Item Line Number

Item Containment

1

1

0..*

Example A

Example B or C

Business ProcessModel

CC SemanticFramework



Core Component Overview



CCTS Normative Section



ebXML Naming Convention

• Describes the rules for naming ebXML Core Components

• Derived from guidelines and principles of ISO 11179 and have drawn from the UN/EDIFACT Design Rules and the TC154 Basic Semantic Registry Methodology naming rules

• Specifies reference dictionary to be Oxford English • Requires allocation of Unique Global Identifiers

(UID)• Designed to support extensions to other languages



ebXML CC Representation TypesPrimary DefinitionSecondary

Amount A number of monetary units specified in a currency where the unit of currency is explicit or implied.

Binary Object A set of finite-length sequences of binary octets.Graphic, Picture,Sound, Video

Code A character string (letters, figures or symbols) that for brevity and / or language independence may be used to represent or replace a definitive value or text of a Property.

Date Time A particular point in the progression of time (ISO 8601). Date, Time

Identifier A character string used to establish the identity of, and distinguish uniquely, one instance of an object within an identification scheme from all other objects within the same scheme.

Indicator A list of exactly two mutually exclusive Boolean values that express the only possible states of a Property.

Measure A numeric value determined by measuring an object. Measures are specified with a unit of measure.

NumericNumeric information that is assigned or is determined by calculation, counting or sequencing.

Value, Rate, Percentage

Quantity A counted number of non-monetary units..

Text A character string generally in the form of words of a language. Name



Application of CC Naming Rules



ebXML Context Drivers

Business Process: Process, collaboration, or transaction.

Business Process Role: Sender and Receiver roles.

Supporting Role: Third-party roles.

Industry Classification: Industry vertical.

Product Classification: Type of product or service.

Geopolitical: Trading region.

Official Constraints: Legal or contractual influence.

System Capabilities: System/Application constraints or

compliance requirements.



Operation of the Context Mechanism



ebXML BP & CC Definitions

Discovery by user communities

Collation of candidate definitions

Harmonisation within TBG

Publication by UN/CEFACT

Usage by all!



UN/CEFACT Business Neutral Core Components Project

• TBG Harmonisation Group project

• Take UN/TDED, UN/EDIFACT, WCO G7, EAN.UCC, ebXML etc. candidate data element definitions

• Validate against ebXML naming conventions

• Harmonise and simplify

• Build Controlled Vocabulary

• Put out results for review

• Publish, extend and maintain over time

• Develop harmonisation check list for tech assessment



ebXML BP & CC Discovery

Work underway in these TBG WGs: TBG2 Procurement & Simpl-eb

TBG1 Materials Management

TBG3 Transportation & Logistics

TBG4 Customs Procedures (WCO)

TBG5 Payments

TBG6 Construction, Architecture & Engineering

TBG8 Insurance (ACORD)

TBG9 Travel, Tourism & Leisure

TBG11 Accountancy



ebXML BP & CC Discovery

Work also underway in these User Groups: UBL (Cross Industry Supply Chain)

EAN.UCC (FMCG Retail Supply Chain)

SWIFT (Interbanking)

OAGI (eBusiness & Application Integration)

XBRL (Accountancy)

SMDX (Statistical Data & Metadata Exchange)

SMDG (Maritime Container Terminal Handling)

OTA (Travel, Tourism & Leisure)

…



What is still required

Formally stable ebXML CC TS Controlled vocabulary for business terms Common format for candidate submissions Harmonisation methodology and tools Repository for storing UN/CEFACT artefacts Confirmation of user communities willingness to converge on

building upon UN/CEFACT CC building blocks Globally agreed XML implementation design rules and business

library building blocks