Sue Probert

1
ebXML Core Components and Business Processes
UN/CEFACT

• Sue Probert
• Senior Director, Document Standards, Commerce
  One
• Vice-Chair, UN/CEFACT Forums
• International Trade Business Processes Group

Electronic Business XML Copenhagen
November 7, 2002
2
eb XML
Transport, Routing Packaging, Partner Profile
Agreements and Registry Repository
Architecture, Business Processes and Core
Components
Syntax Neutral Intl. eBusiness Framework
Global XML Technical Framework
3
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

4
UN/CEFACT Forum Structure
Forum Co-ordination Team (FCT)
Business Processes Trade Facilitation (TBG)
InformationContent (ICG)
Applied (ATG) Technologies
Technologies Methodologies (TMG)
Legal (LG)
5
ebXML phase 2
TRP TC
UN/CEFACT
OASIS
ebXML Messaging
ebXML JCC
CPPA TC
ebXML Partner Profiles Agreements
Joint Architecture
Forum
RegRep TC
ebXML Registry Repository
TBG
TMG
ATG
UBL TC
Syntax Neutral BP Models CCs
Syntax Solutions EDIFACT XML
ebXML CC BP Tech Specs
XSD Design Rules, Document Schemas And Context
Assembly
6
ebXML Methodology Architecture
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 Model Exchange
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
7
ebXML Business Processes

• September 2002 BPWG set up within the UN/CEFACT
  Forums 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

8
Example BP Catalog Scenario
9
Example of BP Definition
10
Example BP Catalog Entries
11
ebXML Core Components Methodology

• September 2002 CCWG set up within the UN/CEFACT
  Forums 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

12
Core Component Technical Specification

• Discovery and Analysis methodologies
• Library of Core Components
• Naming Conventions Rules
• Global Semantic Vocabulary
• Context
• Classification of context drivers
• Extension Methodology
• Describe ways in which components are reused

13
Core Component Hierarchy
Business Process Model
Basic Aggregate BIEs
Basic Aggregate CCs
CC Semantic Framework
CC Types
Global Semantics Vocabulary
14
Core Component Overview
15
CCTS Normative Section
16
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

17
ebXML CC Representation Types
Primary
Definition
Secondary
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.
Numeric
Value, Rate, Percentage
Numeric information that is assigned or is
determined by calculation, counting or
sequencing.
Quantity
A counted number of non-monetary units..
Text
A character string generally in the form of words
of a language.
Name
18
Application of CC Naming Rules
19
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.

20
Operation of the Context Mechanism
21
ebXML BP CC Definitions

• Discovery by user communities
• Collation of candidate definitions
• Harmonisation within TBG
• Publication by UN/CEFACT
• Usage by all!

22
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

23
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

24
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)

25
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