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

2. MRI – 23 rd Sept. 20072/35 Business Domain BRS Describe Business Requirements Map to standard components RSM Syntax creation Syntax expression UMM CCTS CCMA Harmonization CCL BIE lib Process & information Syntax neutral data Syntax impl. Business Collaboration Harmonized information semantics NDR Syntax specific Business use BCSS ODPForum workflow process ATG2 Newcomers Session

3. UN/CEFACT – MRI Modelers Reference Initiative Newcomers Session CEFACT Architecture Nada Reinprecht Stockholm Forum Sun, 23 nd September 2007

4. MRI – 23 rd Sept. 2007CEFACT Architecture - Nada Reinprecht4/35 Introduction CEFACT Strategy CEFACT Architecture CCMA and CEFACT ebArchitecture

5. MRI – 23 rd Sept. 2007CEFACT Architecture - Nada Reinprecht5/35 UN/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)

6. MRI – 23 rd Sept. 2007CEFACT Architecture - Nada Reinprecht6/35

7. MRI – 23 rd Sept. 2007CEFACT Architecture - Nada Reinprecht7/35

8. MRI – 23 rd Sept. 2007CEFACT Architecture - Nada Reinprecht8/35 Runtime engine Technology Transformations CCMA – Information Envelope UMM - Business Process View UMM - Business Collaboration View UMM Business Transaction View UMM - Business Choreography View CCTS - Core Components CCL - Business Information Entities Library UMM - Information Entity UCM – Business Context UCM – Action/Intention SBDH XML NDR - XML EDIFACT UCM – Run-time Context Communication layer Transport layer Semantics Services UMM - Business Entity View

9. UN/CEFACT – MRI Modelers Reference Initiative Newcomers Session Introduction to CCTS Mary Kay Blantz Stockholm Forum Sunday, 23 rd September 2007

10. MRI – 23 rd Sept. 2007CCTS - Mary Kay Blantz10/35 CCTS - 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

11. MRI – 23 rd Sept. 2007CCTS - Mary Kay Blantz11/35 CCTS – 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

12. MRI – 23 rd Sept. 2007CCTS - Mary Kay Blantz12/35 CCTS – Follow up Materials Chair: gunther.stuhec@sap.com Lead Editor: mark.crawford@sap.com Application related Information  Almost all TBGs developing Core Components  CC Harmonization the responsibility of TBG17 mblantz@sbcglobal.net More about TBG17 a little later

13. UN/CEFACT – MRI Modelers Reference Initiative Newcomers Session Business Process Modeling / UMM Niki Sahling Stockholm Forum Sun, 23 nd September 2007

14. MRI – 23 rd Sept. 2007BPM/UMM - Niki Sahling14/35 UMM – 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

15. MRI – 23 rd Sept. 2007BPM/UMM - Niki Sahling15/35 UMM – 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

16. MRI – 23 rd Sept. 2007BPM/UMM - Niki Sahling16/35 UMM – Artifacts

17. MRI – 23 rd Sept. 2007BPM/UMM - Niki Sahling17/35 UMM – 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

18. MRI – 23 rd Sept. 2007BPM/UMM - Niki Sahling18/35 Technical System Specification

19. MRI – 23 rd Sept. 2007BPM/UMM - Niki Sahling19/35 UMM – 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

20. MRI – 23 rd Sept. 2007BPM/UMM - Niki Sahling20/35 UMM – 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

21. MRI – 23 rd Sept. 2007BPM/UMM - Niki Sahling21/35 descr. by UMM ebXML Architecture

22. UN/CEFACT – MRI Modelers Reference Initiative Newcomers Session Introduction to ATG2 and XML NDR Jostein Frømyr, ATG2 chair Stockholm Forum Sunday, 23 rd September 2007

23. MRI – 23 rd Sept. 2007ATG2/XML NDR - Jostein Frømyr23/35 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

24. MRI – 23 rd Sept. 2007ATG2/XML NDR - Jostein Frømyr24/35 ATG in the big picture Business Domain BRS Describe Business Requirements Map to standard components RSM Syntax creation Syntax expression UMM CCTS CCMA Harmonization CCL BIE lib Process & information Syntax neutral data Syntax impl. Business Collaboration Harmonized information semantics NDR Syntax specific Business use BCSS ODPForum workflow process ATG2

25. MRI – 23 rd Sept. 2007ATG2/XML NDR - Jostein Frømyr25/35 The UN/CEFACT XML Naming 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

26. MRI – 23 rd Sept. 2007ATG2/XML NDR - Jostein Frømyr26/35 XML 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

27. MRI – 23 rd Sept. 2007ATG2/XML NDR - Jostein Frømyr27/35 The UN/CEFACT XML puzzle Message.xsdBIE.xsdQDT.xsd UDT.xsd Code list.xsd imports is a restriction of is the source for generation of imports RSM and Message Assembly spreadsheet BIE-lib CDT-library references constructs in BRS describes the realization of requirements defined in CC-lib is based on ABIEs BBIEs QDTs ACCs BCCs UDTs

28. MRI – 23 rd Sept. 2007ATG2/XML NDR - Jostein Frømyr28/35 More info… On ATG  http://www.uncefactforum.org/ATG/ATG_Home.htm http://www.uncefactforum.org/ATG/ATG_Home.htm On the work of ATG2  http://www.unstandards.org:8080/display/ATG/ATG2 http://www.unstandards.org:8080/display/ATG/ATG2 Available schemas  http://www.unece.org/cefact/xml_schemas/index.htm http://www.unece.org/cefact/xml_schemas/index.htm  The schemas themselves are available at http://www.unece.org/uncefact/.... http://www.unece.org/uncefact/

29. UN/CEFACT – MRI Modelers Reference Initiative Newcomers Session Open Develop Process Overview Jim Wilson Stockholm Forum Sun, 23 nd September 2007

30. Open Develop Process Overview – Jim WilsonMRI – 23 rd Sept. 200730/## ODP- 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

31. Open Develop Process Overview – Jim WilsonMRI – 23 rd Sept. 200731/## ODP– 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.

32. Open Develop Process Overview – Jim WilsonMRI – 23 rd Sept. 200732/## ODP – 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

33. UN/CEFACT – MRI Modelers Reference Initiative Cross Domain Projects Core Component Harmonization (TBG17) Mary Kay Blantz Stockholm Forum Sunday, 23 rd September 2007

34. MRI – 23 rd Sept. 2007TBG17 - May Kay Blantz TBG17 – 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.

35. MRI – 23 rd Sept. 2007TBG17 - May Kay Blantz TBG17 – 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)

36. MRI – 23 rd Sept. 2007TBG17 - May Kay Blantz Work 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

37. MRI – 23 rd Sept. 2007TBG17 - May Kay Blantz TBG17 – Where we fit TBG or Liaison Develops business and data models Submits class diagram and core components (CCs/BIEs/qDTs) to TBG17 TBG17 Harmonizes across submissions Develops cross-domain library Submits to ICG for audit ICG Audits based on CCTS rules Gives final approval for publication UNECE Secretariat Publishes Core Component Library (CCL) Plan is to publish twice yearly.

38. UN/CEFACT – MRI Modelers Reference Initiative Cross Domain Projects TBG2 – UNeDocs project Niki Sahling (for Sue Probert) Stockholm Forum Sun, 23 nd September 2007

39. 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

40. UNeDocs - Sue Probert UNeDocs 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

41. UNeDocs - Sue Probert Slide 41 Combined Approach Paper Document aligned to UN Layout Key Electronic Document Exchange XML or UN/EDIFACT Electronic Edit Form <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.70 UBL_Library_0p70_Invoice.xsd"> token 2003-02-14 Bills Microdevices Joes Office Supply 1 5 Pencils, box #2 red

42. UNeDocs - Sue Probert Slide 42 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

43. UNeDocs - Sue Probert International Supply Chain Actors and Roles Buyer Importer Exporter Carrier Seller Carrier (Transport Service Provider) Authority Financial Institution Consignor Consignee Payor Payee Commercial Order Deliver Pay Supplier Logistical Order Transport Ship Goods Pay Carrier Regulatory Issue Licences & Certificates Clear Goods Pay Duties Financial Instruct Payment Credit/Debit Accounts Provide Statements

44. UNeDocs - Sue Probert Slide 44 Standards Foundation UNCEFACT Trade Reference Model for the International Purchase and Supply Chain (TBG14) UNCEFACT Unified Modelling Methodology - UMM (TMG/BP) UNCEFACT Core Components Technical Specification - CCTS (TMG/CC) UNCEFACT Core Component Library (TBG17) UNCEFACT XML Naming and Design Rules (ATG2) UNCEFACT UN/EDIFACT Directory (ATG1) United Nations Trade Data Elements Directory (UNTDED) United Nations Layout Key (UNLK) – UN/ECE Rec. 1

45. UNeDocs - Sue Probert Slide 45 UN/CEFACT Cross-Border Trade Business Standards TBG18 Agriculture TBG5 Finance TBG8 Insurance TBG13 Environment TBG1 Supply Chain TBG4 WCO DM TBG3 Transport TBG2 Digital Paper United Nations Trade Data Elements Directory (UNTDED) TBG15 Trade 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

46. UNeDocs - Sue Probert Cross-Border Trade Single Window Slide 46 TradeInsuranceTransport Materials Management Customs Other Govt. Agencies Workbase Data Model UNeDocs WCO Payment B2G G2G B2B

47. UNeDocs - Sue Probert UNeDocs BIMs Business Information Masters Procurement Buy BIM Cargo Insurance Customs & OGAs Transport Ship BIM Materials Management BIM Supply Chain Logistics 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

48. UNeDocs - Sue Probert UNeDocs Transport Contract BIM ASEAN Export TransitSpace Booking Air (IATA …) Road (IRU, FIATA...) Consignment Booking Transport Order/Shipping Instructions Waybill Cargo Insurance (TBG8) Customs Declaration Transport Contract (TBG3) Rail (UIC …) Sea (IMO …) Import Thai … UNeDocs Document Families Status Reporting Arrival Notice... Etc. Certificates & Licences (TBG15 & TBG18) … … Document Family Common Semantics BIM

49. UNeDocs - Sue Probert Slide 49 UNeDocs Summary A combination of cross-border business requirements collected from the TBG domain Working Groups and the necessary international regulatory requirements collated in conjunction with the WCO, paper-based Convention stakeholders and the Trade Facilitation work of TBG15. A harmonised, multimodal cross-domain data model (the UNeDocs Workbase) based on the reuse of the UN/CEFACT Core Component Library (CCL) plus pre-harmonised contributions to the further development of the CCL. The application of a holistic approach which incorporates the deployment of all relevant UN/CEFACT instruments and standards. The development of coordinated implementation specifications for paper, eforms, UN/EDIFACT and XML document formats and structures.

50. UNeDocs - Sue Probert UNeDocs Follow up Materials Slide 50 Project Leaders: Sue Probert (sue.probert@sepiaeb.com) Michael Dill (dill@gefeg.com)dill@gefeg.com Project Documents: www.unece.org/cefact/forum_grps/tbg/tbg2_edocs/tbg2_edocs.htm

51. UN/CEFACT – MRI Modelers Reference Initiative Cross Domain Projects International Supply Chain Reference Model Colin Clark Stockholm Forum Sun, 23 nd September 2007

52. MRI – 23 rd Sept. 2007ISCM - Colin Clark International Supply Chain Reference Model and its role in Trade Facilitation & Standardisation

53. MRI – 23 rd Sept. 2007ISCM - Colin Clark International Supply Chain Reference Model and its role in Trade Facilitation & Standardisation BuyShipPay

54. MRI – 23 rd Sept. 2007ISCM - Colin Clark54/35 International 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.

55. MRI – 23 rd Sept. 2007ISCM - Colin Clark55/35 International Supply Chain Reference Model Prepare for Export Export Transport Import SHIP BUYPAY Prepare for Import Commercial Procedures Transport Procedures Regulatory Procedures Financial Procedures

56. MRI – 23 rd Sept. 2007ISCM - Colin Clark56/35 Commercial Procedures Establish Sales Contract Order Goods Advise On Delivery Request Payment INVOLVES Prepare for Export Export Transport Import SHIP BUYPAY Prepare for Import Transport Procedures 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 Financial Procedures Provide Credit Rating Provide Insurance Provide Credit Execute Payment Issue Statements International Supply Chain Reference Model

57. MRI – 23 rd Sept. 2007ISCM - Colin Clark57/35

58. MRI – 23 rd Sept. 2007ISCM - Colin Clark58/35 The ISCM Business Processes

59. MRI – 23 rd Sept. 2007ISCM - Colin Clark59/35 The ISCM Business Processes Business Process Normative Category Partner Type Provide QuotationProcurement & Sales SupplierCustomer OrderProcurement & Sales CustomerSupplier Obtain Export Licence Regulatory Services SupplierAuthority Provide Cargo Declaration (Export) Regulatory Services TransporterAuthority Book TransportLogistical Services TransporterCustomer, Supplier Invoice for Transport Service Logistical Services TransporterCustomer, Supplier

60. MRI – 23 rd Sept. 2007ISCM - Colin Clark60/35 Integrating Sector Models

61. MRI – 23 rd Sept. 2007ISCM - Colin Clark61/35 International Supply Chain Reference Model Provide Reusable Processes Expand the Scope and Detail TBGn SHIP BUYPAY

62. MRI – 23 rd Sept. 2007ISCM - Colin Clark62/35 ISCM Top Level Structure

63. MRI – 23 rd Sept. 2007ISCM - Colin Clark63/35 Position TBGn projects into ISCM uc CrossIndustryInvoice IdentifyProductsAndPartnersEstablishBusinessAgreementOrderShipPay «ProcessArea» CrossIndustryInvoice (from ProcurementSales) «realize»

64. MRI – 23 rd Sept. 2007ISCM - Colin Clark64/35 Example: Regulatory Processes

65. MRI – 23 rd Sept. 2007ISCM - Colin Clark65/35 Example: Request for Quote (Business Interaction View)

66. MRI – 23 rd Sept. 2007ISCM - Colin Clark66/35 Example: Request for Quote (Business Information View) Link to Data Model Core Components Message Assembly

67. MRI – 23 rd Sept. 2007ISCM - Colin Clark67/35 Benefits 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

68. MRI – 23 rd Sept. 2007ISCM - Colin Clark68/35 Value 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

69. UN/CEFACT – MRI Modelers Reference Initiative Data and Process Modeling Latest CCMA draft specification Fred van Blommestein Stockholm Forum Sun, 23 nd September 2007

70. MRI – 23 rd Sept. 2007CCMA - Fred van Blommestein70/35 What is a Document or Business Message not? An arbitrary collection of (grouped) data elements

71. MRI – 23 rd Sept. 2007CCMA - Fred van Blommestein71/35 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

72. MRI – 23 rd Sept. 2007CCMA - Fred van Blommestein72/35 Local system Local system Reporting events and decisions Reporting events and decisions Business Messages Synchronization of knowledge about real world objects Process steps Business Partner 1 Business Partner 2 Common knowledge Orders, Products, Locations, Commitments, … B2B

73. MRI – 23 rd Sept. 2007CCMA - Fred van Blommestein73/35 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

74. MRI – 23 rd Sept. 2007CCMA - Fred van Blommestein74/35 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 deleted Example: 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 exchanged Information 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

75. MRI – 23 rd Sept. 2007CCMA - Fred van Blommestein75/35 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

76. MRI – 23 rd Sept. 2007CCMA - Fred van Blommestein76/35 ABIE with actions Business Context > Business Message Type Aggregate Business Information Entity 1..* > Business Document Header 1..1 is valid in contains > Messaging Business Information Entity 1..* ASBIE ASMA 0..* ASMBIE 0..* Based on CCMA basic structure

77. MRI – 23 rd Sept. 2007CCMA - Fred van Blommestein77/35 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

78. MRI – 23 rd Sept. 2007CCMA - Fred van Blommestein78/35 Business Context > Business Message Type 0..* > Message Assembly 1..* 0..* > Standard Business Document Header 1..1 is valid in contains ASMA > Messaging Business Information Entity 0..* ASMA ASMBIE 0..* No semantics, No property term MBIE Grouping

79. MRI – 23 rd Sept. 2007CCMA - Fred van Blommestein79/35 Business Message Type: Business Message Instance 1 Business Document Header :Header Instance Logical definition, presentation to the application Business Message Type: Business Message Instance 2 Business Message Type: Business Message Instance 3 Business Document Header :Header Instance Business Document Header :Header Instance Business Document Header :Header Instance Physical interchange Business Message Type: Business Message Instance 1 Business Message Type: Business Message Instance 2 Business Message Type: Business Message Instance 3 Logical view vs. technical implementation

80. MRI – 23 rd Sept. 2007CCMA - Fred van Blommestein80/35 An MBIE may be constrained with respect to the ABIE it is based on Constraints may be Invariants, Preconditions, Postconditions, Transition Conditions By defining Constraints at message level, the process flow may be documented Constraints

81. MRI – 23 rd Sept. 2007CCMA - Fred van Blommestein81/35 Process Step State (precondition) State (postcondition) Updates View on Schema Defines Precondition = Information Requirements to perform the Process Step Postcondition = Goal Common knowledge Orders, Products, Locations, Commitments, … Modular Process Steps

82. MRI – 23 rd Sept. 2007CCMA - Fred van Blommestein82/35 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

83. UN/CEFACT – MRI Modelers Reference Initiative Data and Process Modeling Advanced Possibilities Glenn Miller Stockholm Forum Sun, 23 nd September 2007

84. MRI – 23 rd Sept. 2007Data and Process Modeling - Glenn Miller84/35 UN/CEFACT - Advanced Possibilities

85. MRI – 23 rd Sept. 2007Data and Process Modeling - Glenn Miller85/35 Work Product vs. Workflow Work Product  Business Processes  Business Artifacts  Requirements for Implementation Workflow  Organization of Information  "Approval" of information  Publication of Information

86. MRI – 23 rd Sept. 2007Data and Process Modeling - Glenn Miller86/35 Work Product Business Requirements Specification Business Models Core Components Requirements Specification Mapping Schema Generation

87. MRI – 23 rd Sept. 2007Data and Process Modeling - Glenn Miller87/35 Workflow 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

88. MRI – 23 rd Sept. 2007Data and Process Modeling - Glenn Miller88/35 Issues 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

89. MRI – 23 rd Sept. 2007Data and Process Modeling - Glenn Miller89/35 Registry 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

90. MRI – 23 rd Sept. 2007Data and Process Modeling - Glenn Miller90/35 The Process Without a Registry

91. MRI – 23 rd Sept. 2007Data and Process Modeling - Glenn Miller91/35 The Process with a Registry Registry/ Repository

92. MRI – 23 rd Sept. 2007Data and Process Modeling - Glenn Miller92/35 Why use a Registry? Automated Notification of Workflow Global collaboration for workflow  Reduces “Time to Market” Single Delivery source for Published Specifications Federated environment reduces “Which version, and Where is it” syndrome

93. MRI – 23 rd Sept. 2007Data and Process Modeling - Glenn Miller93/35 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

94. MRI – 23 rd Sept. 2007Data and Process Modeling - Glenn Miller94/35 Contact Glenn Miller  Senior Partner – G.F. Miller Consulting Ltd  Glenn.miller@gfmiller.com Glenn.miller@gfmiller.com  +001.613.820-5478 (Office)  +001.613.853-3520 (Mobile)

95. MRI – 23 rd Sept. 2007BPM/UMM - Niki Sahling95/35 UN/CEFACT S IMPLE, T RANSPARENT AND E FFECTIVE P ROCESSES FOR G LOBAL B USINESS.