UN/CEFACT – MRI Modelers Reference Initiative Newcomers Session Stockholm Forum Sun, 23 nd September 2007

UN/CEFACT – MRIModelers Reference Initiative


Newcomers Session

Stockholm ForumSun, 23nd September 2007

MRI – 23rd Sept. 2007 BPM/UMM - Niki Sahling 2/35

BusinessDomain

BRS

DescribeBusiness

Requirements

Map to standardcomponents

RSM

Syntaxcreation

Syntaxexpression

UMM

CCTS

CCMA

Harmonization

CCLBIE lib

Process & information

Syntax neutral data

Syntaximpl.

BusinessCollaboration

Harmonizedinformation

semantics

NDR

Syntax specific

Business use

BCSS

ODP Forum workflow process

ATG2

Newcomers SessionNewcomers Session



Newcomers SessionCEFACT Architecture

Nada Reinprecht


MRI – 23rd Sept. 2007 CEFACT Architecture - Nada Reinprecht 4/35

IntroductionIntroduction

CEFACT StrategyCEFACT ArchitectureCCMA and CEFACT ebArchitecture


UN/CEFACTs StrategyUN/CEFACTs Strategy

Analyse, model collaborative business processes; define choreography of business processes;

• UMM (UN/CEFACT Modelling Methodology)• Store to Common Business Process Catalog

Standardise business information; develop technology neutral business ontology and semantics;

• CCTS (Core Components Technical Specifications)• Store in Core Component Library

Apply current and emerging technologies to structure and transfer the business information.

UNeDocs (Formular Layout based on Core Components)


class Dependencies

TechnicalSpecification

CCTSTechnicalSpecification

UMM

TechnicalSpecification

XMLNDR

pkg TechnicalSpecifications

Dependencies

+ CCTS

+ UMM

+ XMLNDR

ReleasePackage_06B

+ ReleasePackage_06B

pkg Standards

Recommendations

BusinessStandards

+ CCL

+ EDIFACT Library

+ Harmonised Components

+ Harmonised Processes

+ Industry Domains

+ International Trade

TechnicalSpecifications

+ Dependencies

+ ReleasePackage_06B



Runtime engine

Technology Transformations

CCMA – Information Envelope

UMM - Business Process View

UMM - Business Collaboration View

UMM Business Transaction ViewUMM - Business Choreography View

CCTS - Core Components

CCL - Business Information Entities Library

UMM - Information Entity

UCM – Business Context

UCM –Action/Intention

SBDH

SBDH

XML NDR - XML EDIFACT

UCM – Run-time Context

Communication layer

Transport layer

Sem

an

ticsS

ervices

UMM - Business Entity View



Newcomers SessionIntroduction to CCTS

Mary Kay Blantz

Stockholm ForumSunday, 23rd September 2007

MRI – 23rd Sept. 2007 CCTS - Mary Kay Blantz 10/35

CCTS - IntroductionCCTS - Introduction

Project started in 1999 Collaboration between UN/CEFACT and OASIS Several versions developed

Core Component Technical Specification 2.01 Both a UN/CEFACT and ISO Specification Published over three years ago Define the methodology for developing syntax neutral building

blocks – reusable, standardized data Able to serve as the canonical model for all other data

repositories

Current project to develop the next version


CCTS – RelationshipCCTS – Relationship

Business Process (UMM) feeds into CCTS Business Process models describe the business Class Diagrams describe the actual data needed

• BRS describes the business data requirements• RSM describes the Core Components need to describe the

business date What CCs are NOT

Core Components are not XML; they are syntax neutral Core Components are not messages; but they can be used to

populate syntax neutral message models Summary

CCTS is used to build the foundational data for use by all business domains within UN/CEFACT


CCTS – Follow up MaterialsCCTS – Follow up Materials

Chair: [email protected] Editor: [email protected] Application related Information

Almost all TBGs developing Core Components CC Harmonization the responsibility of TBG17

• [email protected]

More about TBG17 a little later

mailto:[email protected]



Newcomers SessionBusiness Process Modeling / UMM

Niki Sahling



UMM – IntroductionUMM – Introduction

Definition UN/CEFACTs Modeling Methodology (UMM) is a UML

modeling approach to design the business services that each business partner must provide in order to collaborate

It provides the business justification for the service to be implemented in a service-oriented architecture (SOA)

Goals and Scope Collaboration between different Business Partners


UMM – Goals and ScopeUMM – Goals and Scope

UMM Focus on Collaborations Describing interfaces and the choreography of

Business Processes between Organizations• CollaborationRequirementsView (mapping of roles)• BusinessChoreographyView

Provides / describes the Context of:• BusinessTransactions• BusinessEntities

Transactions can be reused in different Context


UMM – ArtifactsUMM – Artifacts

UseCases

ProcessView

EntityState

Diagram

Collaboration

Requirements

Roles involved

Transactions

Patterns

BusinessInformation

CoreComponents

deriveCollaborations

Collaborationsare made out of

Transactions

Business Informationsare assembled

CoreComponents

BDVBusinessDomainView

BRVBusinessRequirementsView

BTVBusinessTransactionView

Choreography

Leve

l of

Det

ail

Analysis Aids

Deliverables

Analysis Phase Modeling Phase


UMM – Status & ResultsUMM – Status & Results

Target audience Business Experts: describe the relevant collaborations Technical Architects: to derive solutions/implementation from the

model

Status UMM v1.0 available for implementation v2.0 under development (draft)

Result, by creating UMM models … Standardized approach to specify business requirements Supports consistent modeling approach (with verification) Next step (towards implementation): Technical system

specification


Technical System SpecificationTechnical System SpecificationBusiness

Model

Patterns(Collaboration)

UseCaseDiagram

FunctionalModel

SequenceDiagram

ClassDiagram

Technological Environment(Requirenments from:)

External WebServicesto be used: - WSDL

ebXMLservice oriented approach

Legacy Systemsdescription about:

- Interface and - Data (Information Model)

Technical System Specification

Specifications for all

Services:Sequence(Choreography) ofFunction Calls (RPC)

Class Diagram

ArchitecturalModel

Project Definition

Decision whichand how

collaborations areimplemented

The BSI implements the interface toexisting applications (Legacy Systems)

One sequencediagramm per

service

WSDL provides all informationneeded to call such a service

The Class Diagramprovides an overviewabout all used dataitems in the wholebusiness case

One Business Model (per BusinessCase = EmptiesCain) defines thescope where all subsequentcreated objects relate to

BSIBusiness ServiceInterface = LegacySystem Interface

The specificationfor the servicescan be deriveddirect from the

funcional modell


UMM – RelationshipUMM – Relationship

Relation to other Projects, Standards … Technology independent requirement specification Based on UML Methodology for UN/CEFACT’s BRS ISCM: TBG14 Project using UMM process modeling data modeling

Summary Well established process modeling:

• Provides context for data modeling• Supports data harmonization• Precondition for process harmonization


UMM – Follow up MaterialsUMM – Follow up Materials

Technical Papers Technical Spec, User Guides, … TMG Christian Huemer

Application related Information TBG’s projects need to follow ODP and create BRS UMM supports with consistency between data and

process model TBG14: Business process modeling and harmonization

ISCM



Newcomers SessionIntroduction to ATG2 and XML NDR

Jostein Frømyr, ATG2 chair


MRI – 23rd Sept. 2007 ATG2/XML NDR - Jostein Frømyr 23/35

Applied Technologies Group

Applied Technologies Group

ATG1 - EDIFACT Syntax Development and maintenance of

EDIFACT syntax solutions to support UN/CEFACT work program

Chaired by Gait Boxman Activities

Processing of EDIFACT DMRs UML2EDIFACT Project

• Currently at ODP6

ATG2 - XML Syntax Development and maintenance of XML

syntax solutions to support UN/CEFACT work program

Chaired by Jostein Frømyr Activities

XML Schema production XML Naming and Design Rules, V3

• Currently at ODP3 Data Type Library

• Currently at ODP3 Standard Business Document Header, v2

• Currently at ODP2 XML Representation of Core Components

• Currently at ODP3

Mandate Create and maintain the trade, business and administration document structures

based on a specific technology or standard Design, assembly and production of syntax specific solutions based on identified

business and/or technical requirements from the empowered groups of UN/CEFACT


ATG inthe big picture

ATG inthe big picture

BusinessDomain

BRS

DescribeBusiness

Requirements

Map to standardcomponents

RSM

Syntaxcreation

Syntaxexpression

UMM

CCTS

CCMA

Harmonization

CCLBIE lib

Process & information

Syntax neutral data

Syntaximpl.

BusinessCollaboration

Harmonizedinformation

semantics

NDR

Syntax specific

Business use

BCSS

ODP Forum workflow process

ATG2


The UN/CEFACT XMLNaming and Design Rules

The UN/CEFACT XMLNaming and Design Rules

A technical specification defining rules and guidelines for naming and design of XML schema constructs on the basis of

Collaboration models developed in accordance to the UMM

Information models developed in accordance to the CCTS Documenting ”best practices” in order to optimise

Use of XML schema Semantic interoperability Modularity Extensibility Maintainability Re-use …

Contains XML schema for the instantiation of the basic data types defined in CCTS (Unqualified Data Types)

Focus is on facilitation of efficient semantic interoperability

May be used as a basis for automated production, as well as handcrafting, of XML schemas

Makes use of the most common features of the XML schema specification and other W3C standards holding recommendation status


XML NDRXML NDR

202 rules on how to create UN/CEFACT XML schemas Representation of CCTS components Naming Modularity Namespace

Use of built-in XSD data types Schema location Versioning Extension and restriction

Use of XML Elements, attributes and types Layout and structure of XML schemas Annotation Use of XML schema constructs


The UN/CEFACT XML puzzle

The UN/CEFACT XML puzzle

Message.xsd BIE.xsd QDT.xsd

UDT.xsd

Code list.xsdimports imports imports

is a restriction of

is the source for generation of



imports

RSM andMessage Assembly

spreadsheet BIE-lib

CDT-library

references constructs in

BRS

describes the realization of requirements defined in

CC-lib

is based on

ABIEsBBIEsQDTs

ACCsBCCs

UDTs


More info…More info…

On ATG http://www.uncefactforum.org/ATG/ATG_Home.htm

On the work of ATG2 http://www.unstandards.org:8080/display/ATG/ATG2

Available schemas http://www.unece.org/cefact/xml_schemas/index.htm The schemas themselves are available at http://

www.unece.org/uncefact/....

http://www.uncefactforum.org/ATG/ATG_Home.htm

http://www.uncefactforum.org/ATG/ATG_Home.htm

http://www.unstandards.org:8080/display/ATG/ATG2

http://www.unece.org/cefact/xml_schemas/index.htm

http://www.unece.org/cefact/xml_schemas/index.htm

http://www.unece.org/uncefact/





Newcomers SessionOpen Develop Process Overview

Jim Wilson


Open Develop Process Overview – Jim WilsonMRI – 23rd Sept. 2007 30/##

ODP- IntroductionODP- Introduction

Introduction Goals and Scope: Define UN/CEFACT’s process for

producing publications. Target Audience: UN/CEFACT Project Teams Project Status: Complete Delivery: Open Development Process

(PDF document)TRADE_R.650_Rev.4_Add.1_R1April17_12pt.pdf


ODP– RelationshipODP– Relationship

Relation to other Projects, Standards, Methodology This publication is top-level: all other projects relate to

it.

Summary The Open Development Process Defines

UN/CEFACT’s process for producing publications.


ODP – Final MaterialODP – Final Material

Technical Papers Not applicable

Application related Information Open Development Process

(PDF document)TRADE_R.650_Rev.4_Add.1_R1April17_12pt.pdf

http://www.unece.org/cefact; look for “Open Development Process”

http://www.unece.org/cefact

http://www.unece.org/cefact



Cross Domain ProjectsCore Component Harmonization (TBG17)

Mary Kay Blantz


MRI – 23rd Sept. 2007 TBG17 - May Kay Blantz

TBG17 – PurposeTBG17 – Purpose

Core Component Harmonization

The purpose of TBG17 is to be 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.


TBG17 – MembershipTBG17 – Membership

Unlike other UN/CEFACT TBGs, TBG17 members can represent groups

Members represent Other TBGs Liaisons

• ECOM• EDIFICE• GS1• JAI• OAGi• SWIFT• UBL• USG

Other PGs (ICG and ATG)


Work LoadWork Load

Currently harmonizing submissions from: TBG2_3 (TBG1-4-5-12-15-18-19)

• eDocs• Transport

TBG5/SWIFT (TBG1 and TBG2) TBG8 TBG12 TBG18

• eCerts (collaboration with TBG2)• eDAPLOS

TBG19 JAI

TBG17


TBG17 – Where we fitTBG17 – Where we fit

TBG or LiaisonDevelops business and data modelsSubmits class diagram and core components(CCs/BIEs/qDTs) to TBG17

TBG17Harmonizes across submissionsDevelops cross-domain librarySubmits to ICG for audit

ICGAudits based on CCTS rulesGives final approval for publication

UNECESecretariat

Publishes Core Component Library (CCL)Plan is to publish twice yearly.



Cross Domain ProjectsTBG2 – UNeDocs project

Niki Sahling (for Sue Probert)


UNeDocs - Sue Probert

UNeDocs is about Cross Border Trade Facilitation

Slide 39

A single data modelling approach for: Paper documents Electronic documents which are simply

equivalent to paper documents Structured electronic documents

UNEDIFACT, Cargoimp, VDA, XML etc. Snippets, e.g. Web/Service Orientated

eTransactions


UNeDocs ObjectivesUNeDocs Objectives

To facilitate international trade by providing a migration path towards paperless trade by:

developing a cross-domain, multimodal cross-border Core Component data model (the UNeDocs Workbase) mapped to the United Nations Trade Data Element Directory (UNTDED)

publishing and maintaining a set of UN/CEFACT syntax implementation standards including EDIFACT, XML amd aligned paper document layouts

To support maintainable national, regional and industry-focussed contextual implementations by:

delivering Capacity Building Workshops developing and publishing UNeDocs implementation

guidance documentation.

Slide 40


Slide 41

Combined ApproachCombined 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>


Slide 42

UNeDocs Process Scope

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

International Trade Reference Model


International Supply Chain Actors and Roles

Buyer

ImporterExporterCarrier

Seller

Carrier(Transport Service Provider)

Authority

FinancialInstitution

ConsignorConsignee

PayorPayee

CommercialOrder

DeliverPay Supplier

LogisticalOrder Transport

Ship GoodsPay Carrier

RegulatoryIssue Licences & Certificates

Clear GoodsPay Duties

FinancialInstruct Payment

Credit/Debit AccountsProvide Statements


Slide 45

UN/CEFACT Cross-Border TradeBusiness Standards

UN/CEFACT Cross-Border TradeBusiness Standards

TBG18 Agriculture

TBG5Finance

TBG8 Insurance

TBG13Environment

TBG1Supply Chain

TBG4WCO DM

TBG3Transport

TBG2Digital Paper

United Nations Trade Data Elements Directory (UNTDED)

TBG15Trade Facilitation

TBG15 International Trade Single Window Recommendations (33 & 34)

TBG19 eGov

TBG17 UN/CEFACT Core Component Library

TBG14 International Supply Chain Model & TBG2 UNeDocs Workbase


Cross-Border TradeSingle Window

Cross-Border TradeSingle Window

Slide 46

Trade InsuranceTransportMaterialsManagement

CustomsOther Govt. Agencies

WorkbaseData Model

UNeDocsWCO

Payment

B2G

G2G

B2B


UNeDocs BIMsUNeDocs BIMsBusiness Information Masters

Procurement

Buy BIM

CargoInsurance

Customs &OGAs

Transport

Ship BIM

Materials Management BIM

Supply ChainLogistics

Transport Equipment BIM

Business Information Masters:• are common patterns for one or more business document families• can be cross domain/silo breaking• therefore ensure consistency of data within and across document families


UNeDocsTransport Contract

BIM

ASEANExport

Transit Space Booking

Air(IATA

…)

Road(IRU,

FIATA ...)

Consignment Booking

Transport Order/Shipping

Instructions

Waybill

CargoInsurance(TBG8)

Customs Declaration

TransportContract(TBG3)

Rail(UIC …)

Sea(IMO …)

Import

Thai…

UNeDocs Document Families

Status Reporting

Arrival Notice

...

Etc.

Certificates & Licences

(TBG15 & TBG18)

……

Document Family

Common Semantics

BIM


UNeDocsFollow up Materials

UNeDocsFollow up Materials

Slide 50

Project Leaders: Sue Probert ([email protected])Michael Dill ([email protected]) Project Documents:www.unece.org/cefact/forum_grps/tbg/tbg2_edocs/tbg2_edocs.htm


http://www.unece.org/cefact/forum_grps/tbg/tbg2_edocs/tbg2_edocs.htm










Cross Domain ProjectsInternational Supply Chain

Reference ModelColin Clark


MRI – 23rd Sept. 2007 ISCM - Colin Clark

International Supply Chain Reference Model

and its role in

Trade Facilitation &Standardisation

MRI – 23rd Sept. 2007 ISCM - Colin Clark

International Supply Chain Reference Model

and its role in

Trade Facilitation &Standardisation

Buy Ship Pay

MRI – 23rd Sept. 2007 ISCM - Colin Clark 54/35

International Supply Chain Reference ModelInternational Supply Chain Reference Model

A model of the international supply chain, modelling commodity trade across national borders.

Uses know-how contained in the ITT and obtained from SWIFT, WCO, and UN/CEFACT s domain groups.

Maps the natural process flow of trade to separate business areas (i.e. regulatory, business, finance procedures).

Describes these processes at various levels of detail, conforming to UMM.

Links trade processes/transactions to the business information used by them.



Prepare for

ExportExport Transport Import

SHIPBUY PAY

Prepare for

Import

Commercial Procedures

Transport Procedures

Regulatory Procedures

Financial Procedures


CommercialProcedures

• Establish Sales Contract

• Order Goods• Advise On Delivery• Request Payment

INVOLVESINVOLVES

Prepare for

ExportExport Transport Import

SHIPBUY PAY

Prepare for

Import

TransportProcedures

• Establish Transport Contract

• Collect Transport and Deliver Goods

• Provide Waybills, Goods Receipts Status Reports

Regulatory Procedures

• Obtain Import/Export Licences

• Provide Customs Declarations

• Provide Cargo Declarations

• Apply Trade Security Procedures

• Clear Goods for Import/Export

FinancialProcedures

• Provide Credit Rating• Provide Insurance• Provide Credit• Execute Payment• Issue Statements



UN/CEFACTInformation flows for trade process

Payment

Transport

Order

CarrierSupplier CustomsTransport

PayerCustomer's

BankCustomer

International Supply Chain:

Proof ofCollection

Order Transport

Declare Goods for Departure

Declare Goods for Export

Supplier'sBank

Transport Contract

DispatchAdvise

OtherGovernmental

Agencies

Transport Status

Order Goods

Information onExport

Information onDeparture

Declare Goodsfor Import

Information onImport

Proof of Delivery

Freight Invoice

Request Payment

Initiate Payment

TransferMoney


Business Process Normative Category Partner Type Partner TypeObtain Product Information Procurement&Sales Customer SupplierProvide Quotation Procurement&Sales Customer SupplierNegotiate Sales Contract Procurement&Sales Customer SupplierPlace Order Procurement&Sales Customer SupplierProvide Delivery Schedule Procurement&Sales Customer SupplierAdvise Despatch Procurement&Sales Customer SupplierInvoice for Order Procurement&Sales Customer SupplierProvide Credit Note Procurement&Sales Customer SupplierProvide Debit Note Procurement&Sales Customer SupplierAdvise Remittance Procurement&Sales Customer SupplierObtain Export Licence etc Regulatory Services Supplier AuthorityObtain Import Licence etc Regulatory Services Customer AuthorityProvide Customs Declaration (Export) Regulatory Services Supplier AuthorityProvide Cargo Declaration (Export) Regulatory Services Transporter AuthorityProvde Customs Declaration (Import) Regulatory Services Customer AuthorityProvide Cargo Declaration (Import) Regulatory Services Transporter AuthorityClear Goods (Export) Regulatory Services Authority Transporter, SupplierClear Goods (Import) Regulatory Services Authority Transporter,CustomerPay Customs Tarif Regulatory Services Customer, Supplier AuthorityNegotiate Transport Contract Logistical Services Customer, Supplier Transporter Book Transport Logistical Services Customer, Supplier Transporter Provide Transport Documentation (WayBill,etc)Logistical Services Transporter Customer, SupplierConfirm Delivery Logistical Services Transporter SupplierProvide Status Report Logistical Services Transporter Customer, SupplierInvoice for Transport Service Logistical Services Transporter Customer, SupplierProvide Credit Rating Financial Services Bank CustomerProvide Credit Financial Services Bank CustomerProvide Goods Insurance Financial Services Insurer Customer, SupplierExecute Payment Financial Services Customers Bank Suppliers BankProvide Financial Statements Financial Services Bank Customer, Supplier

The ISCM Business Processes


The ISCM Business Processes

Business Process

Normative Category

Partner Type Partner Type

Provide Quotation Procurement & Sales

Supplier Customer

Order Procurement & Sales

Customer Supplier

Obtain Export Licence

Regulatory Services

Supplier Authority

Provide Cargo Declaration (Export)

Regulatory Services

Transporter Authority

Book Transport Logistical Services Transporter Customer,

Supplier

Invoice for Transport Service

Logistical Services Transporter Customer, Supplier


Integrating Sector ModelsIntegrating Sector Models



Provide ReusableProcesses

Expand the Scopeand Detail

TBGn

SHIPBUY PAY


ISCM Top Level StructureISCM Top Level Structure


Position TBGn projects into ISCMPosition TBGn projects into ISCM

uc CrossIndustryInvoice

IdentifyProductsAndPartnersEstablishBusinessAgreement Order Ship Pay

«ProcessArea»CrossIndustryInvoice

(from ProcurementSales)

«realize»


Example: Regulatory ProcessesExample: Regulatory Processes


Example: Request for Quote (Business Interaction View)Example: Request for Quote (Business Interaction View)


Example: Request for Quote (Business Information View)Example: Request for Quote (Business Information View)

Link to Data Model

Core Components Message Assembly

class QuoteItem

«InformationEnvelope»QuoteItemRequest

# Date: # Recipient: # Sender:

«Information...QuoteItemHeader

«Information...QuoteItemBody

# Quality: # Quantity:

«Information...QuoteItem

# Date: # Recipient: # Sender:

«Information...QuoteItemHeader

# Reference:

«Information...QuoteItemBody

# Quality: # Quantity:

+header +body+header +body


BenefitsBenefits

Standardisation: Re–useable processes to develop new, specific process models Framework to support harmonization Context to identify business information & documents

Trade Facilitation Identification of process and procedures related to trade barriers Assess the implications of planned policy measures (Security

Related, AEO) “Capacity Building“ – Training & Education

Business Implement "best practice" processes Use to develop company specific implementations


Value PropositionValue Proposition

Accelerated delivery and adoption of high quality,flexible, low cost e-commerce solutions

Predicated upon a library of re useable process models and associated data

Registered within UN/CEFACT repository and discoverable for re use



Data and Process ModelingLatest CCMA draft specification

Fred van Blommestein


MRI – 23rd Sept. 2007 CCMA - Fred van Blommestein 70/35

What is a Document or Business Message

not?

An arbitrary collection of (grouped) data elements


• A Statement from a business partner to another business partner that may change their legal, commercial or operational relation

• A bundle of information about Business Entities that updates the knowledge of the receiving partner

• A step in a business process

What is a Document or Business Message?

The exchange of a Business Message is an event with Business implications


Local system

Local system

Reporting events and decisions

Reporting events and decisions

• Business Messages• Synchronization of knowledge

about real world objects• Process stepsBusiness Partner 1 Business Partner 2

Common knowledge

Orders, Products, Locations, Commitments, …

B2B


• Real world objects or Business Entities are represented as ABIEs

• A Business Message consists of a set of updates on information about Business Entities

• “Update” may be add, change, delete, refer to, repeat or request

• ABIEs to be updated may occur on any level in the data structure (e.g. change the price of an article in the catalog)

Knowledge updating


Add: An ABIE instance with the same ID may not already exist

Change, Delete: An ABIE instance with the same ID must exist

Refer to: ABIE is only in the document to be able to identify another ABIE that is to be added, changed or deletedExample: Delivery Period in a Call Off line of which the quantities are changed

Repeat: The information on the Business Entity is to be the same as previously exchangedInformation was re-sent for legal or technical reasons.

Request: The sender requests (queries) the receiver to send him information on the (identified) Business Entity.

Action verbs


• Whether information is added, changed, deleted, etc. is not defined on ABIE level

• If the update action is to be defined implicitly, for each ABIE we would need 6 versions (or sub-ABIEs)

• The CCMA draft adds these Action Verbs explicitly

• CCMA defines Messaging Business Information Entities (MBIEs)

• An MBIE is based on an ABIE, but may have an additional Action Verb (Add, Change, Delete, etc.)

• An MBIE may also have additional constraints wrt the ABIE

MBIEs


ABIE with actions

Business Context<<InformationEnvelope>>

Business Message Type

Aggregate BusinessInformation Entity

1..*

<<InformationEntity>>

Business Document Header

1..1

is valid in

contains


Messaging BusinessInformation Entity

1..*

ASBIE

ASMA

0..*

ASMBIE

0..*

Based on

CCMA basic structure


• The ‘top level’ MBIEs in a Business Message may be grouped by means of Message Assemblies (MAs)

• The Grouping structure is intended for readability and processability and does not have business semantics

• Business semantics are defined in the ABIE structuring• The sequence in which MBIEs on the same level appear

in the Business Message may be indicated

Grouping and Sequencing


Business Context

<<InformationEnvelope>>

Business Message Type

0..*


Message Assembly

1..*

0..*


Standard Business Document Header

1..1

is valid in

contains

ASMA


Messaging BusinessInformation Entity

0..*

0..*

ASMA

ASMA

ASMA

ASMBIE

0..*

No semantics,No property term

MBIE Grouping


Business Message Type: Business

Message Instance 1

Business Document Header:Header Instance

Logical definition, presentation to the application


Message Instance 2


Message Instance 3




Physical interchange


Message Instance 1


Message Instance 2


Message Instance 3

Logical view vs. technical implementation


• An MBIE may be constrained with respect to the ABIE it is based on

• Constraints may beInvariants, Preconditions, Postconditions, Transition Conditions

• By defining Constraints at message level, the process flow may be documented

Constraints


ProcessStep

State(precondition)

State(postcondition)

UpdatesView on View on

Schema

DefinesPrecondition = Information Requirements to perform the Process Step

Postcondition = Goal

Common knowledge

Orders, Products, Locations, Commitments, …

Modular Process Steps


• The precise wording of CCMA needs further discussion• The basic set of CCMA methods and features has

however been agreed• To allow implementation preparation a User Guide has

been prepared

CCMA Guide



Data and Process ModelingAdvanced Possibilities

Glenn Miller


MRI – 23rd Sept. 2007 Data and Process Modeling - Glenn Miller 84/35

UN/CEFACT - Advanced PossibilitiesUN/CEFACT - Advanced Possibilities


Work Product vs. WorkflowWork Product vs. Workflow

Work Product Business Processes Business Artifacts Requirements for Implementation

Workflow Organization of Information "Approval" of information Publication of Information


Work ProductWork Product

Business Requirements SpecificationBusiness ModelsCore ComponentsRequirements Specification MappingSchema Generation


WorkflowWorkflow

Creation of Project Plan Creation of BRS, RSM Creation of Business Models

Using• Supply Chain Reference Model• Enumeration lists• Code Lists• Context Values

Harmonization of Business Processes Harmonization of Core Components Creation of Production Schemas Publication


Issues for resolutionIssues for resolution

E-Architecture – Enabler of the complete environment

Advanced Workflow products – how do we move forward?

Integration of BRS, Core Components, RSM into the United Nations Modeling Methodology

Implement a Registry/Repository


Registry SolutionRegistry Solution

Can Store Work Products "Single Project" is comprised of all Work Product in a single

Global source Can streamline Workflow

Steering Committee for acceptance of Project Plan ICG for acceptance of BRS, RSM TBG14/MRI for Business Process Modeling Acceptance by TBG17 for Core Components Point Source for ATG2 to Apply Naming and Design Rules Represents a single source for Global Implementers


The Process Without a RegistryThe Process Without a Registry

TBGProject

(Project Team)

Steering Committeefor approval

Distribution List

Create a BRS(Project team)

Submit BRS to Steering/ICG

Distribution List

Perform Modeling(Project Team)

Process Harmonization Distribution

List

Create Core Components

Submit to TBG17

Distribution List

Create an RSMSubmit to ICG

Distribution List

Submit Work Product to ATG/

ATG2

Distribution List

Create Schemas

Submit to ICG for Publication

Global Implementers


The Process with a RegistryThe Process with a Registry

TBGProject

(Project Team)

Steering Committeefor approval

Perform Modelling

Registry/Repository

ICG Reviews BRSHandover to

TBG17ICG Reviews RSM

ATG Creates Schemas

ICG Publishes Project

(Standard)

Global Implementers


Why use a Registry?Why use a Registry?

Automated Notification of WorkflowGlobal collaboration for workflow

Reduces “Time to Market”

Single Delivery source for Published Specifications

Federated environment reduces “Which version, and Where is it” syndrome


Why use a Registry? (2)Why use a Registry? (2)

Re-use Business Processes Enumerated Lists Code sets

Every artifact discovered, should become re-useable to the enterprise Savings of both Time and Dollars


ContactContact

Glenn Miller Senior Partner – G.F. Miller Consulting Ltd [email protected] +001.613.820-5478 (Office) +001.613.853-3520 (Mobile)



UN/CEFACTSIMPLE, TRANSPARENT AND EFFECTIVE PROCESSES

FOR GLOBAL BUSINESS.