Docstoc

ISCM at MRI

Document Sample
ISCM at MRI Powered By Docstoc
					  UN/CEFACT – MRI
Modelers Reference Initiative


     Newcomers Session



        Stockholm Forum
      Sun, 23nd September 2007
                                        Newcomers Session
                                                   CCTS
                     Business
  Business       Collaboration
  Domain                                                       Harmonized
                                                               information
                  Describe                                       semantics
                  Business
                Requirements
                                                               Harmonization
 Process &                       BRS
information
                                           Map to standard                      CCL
                                            components                         BIE lib
                                                                                                   NDR
              UMM
                                        Syntax neutral data
                                                                                                                ATG2
                                                                       RSM

                                                        CCMA                                                 Syntax
                                                                                             Syntax
                                                                                            creation
                                                                                                              impl.

                                                                                                             Syntax
                                 BCSS
                                                                                                           expression
                                                                                         Syntax specific



                                                                                                                        Business
                        ODP                          Forum workflow process                                               use
       MRI – 23rd Sept. 2007                                                                                            2/35
  UN/CEFACT – MRI
Modelers Reference Initiative


     Newcomers Session
          CEFACT Architecture
             Nada Reinprecht


        Stockholm Forum
      Sun, 23nd September 2007
              Introduction


 CEFACT Strategy
 CEFACT Architecture
 CCMA and CEFACT ebArchitecture




MRI – 23rd Sept. 2007   CEFACT Architecture - Nada Reinprecht   4/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)
MRI – 23rd Sept. 2007         CEFACT Architecture - Nada Reinprecht   5/35
                                                                class Dependencies


                                                                   TechnicalSpecification
                                                                                                         TechnicalSpecification
                                                                           CCTS
                                                                                                                 UMM




                                                                                TechnicalSpecification
                                                                                      XMLNDR




MRI – 23rd Sept. 2007   CEFACT Architecture - Nada Reinprecht                                                           6/35
MRI – 23rd Sept. 2007   CEFACT Architecture - Nada Reinprecht   7/35
                 UMM - Business Process View                                          CCTS - Core Components


                                                                                      UCM – Business Context


UMM - Business Collaboration                                                      CCL - Business Information
                                     UMM - Business Entity View                                                         SBDH
           View                                                                         Entities Library


               UMM Business Transaction View




                                                                                                                                        Semantics
              UMM - Business Choreography View


                  UCM –Action/Intention




              UMM - Information Entity                                                                                      SBDH
                                                              CCMA – Information Envelope



                  XML NDR - XML                                   EDIFACT                                  Technology Transformations



                                                                            Runtime
                                               UCM – Run-time Context




                                                                                                                                         Services
                                                                            engine

                                                      Communication layer
    MRI – 23rd Sept. 2007                           CEFACT Architecture - Nada Reinprecht                                        8/35
                                                         Transport layer
  UN/CEFACT – MRI
Modelers Reference Initiative


     Newcomers Session
           Introduction to CCTS
                Mary Kay Blantz


        Stockholm Forum
    Sunday, 23rd September 2007
              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

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


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


MRI – 23rd Sept. 2007            CCTS - Mary Kay Blantz    12/35
   UN/CEFACT – MRI
Modelers Reference Initiative


      Newcomers Session
Business Process Modeling / UMM
                    Niki Sahling


          Stockholm Forum
        Sun, 23nd September 2007
              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


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


MRI – 23rd Sept. 2007             BPM/UMM - Niki Sahling            15/35
                         UMM – Artifacts
                                            Analysis Phase                    Modeling Phase
                         BDV                                           derive
                         Business        Use
                         Domain
                         View
                                        Cases                     Collaborations
       Level of Detail




                                                     Entity                    Collaboration
                         BRV            Process
                         Business                    State                  Requirements
                         Requirements    View
                         View                       Diagram                     Roles involved
                                                                                    Choreography
                                                        Collaborations
                         BTV                           are made out of           Transactions
                         Business                        Transactions
                         Transaction                                            Patterns
                         View
                                                                                      Business
                                                                                     Information
                                                    Business Informations
                               Analysis Aids           are assembled                  Core
                               Deliverables           CoreComponents
MRI – 23rd Sept. 2007                              BPM/UMM - Niki Sahling          Components      16/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

MRI – 23rd Sept. 2007              BPM/UMM - Niki Sahling                 17/35
               Technical System Specification
                               Business
                                Model           One Business Model (per Business
                                                Case = EmptiesCain) defines the                                           Technical System Specification
                                                scope where all subsequent
                                                created objects relate to

                                                                                                 The Class Diagram
                           UseCase                                                               provides an overview            Project Definition
                                                                                                 about all used data
                           Diagram                                                               items in the whole
                                                                                                 business case
                                                          Functional
                           Patterns                         Model                                                                Architectural
                           (Collaboration)                                                                                       Model

                                                         Class                                                                   Class Diagram
             Decision which
                   and how                               Diagram
          collaborations are
               implemented


                                                         Sequence                                                                Specifications for all
               Technological Environment                 Diagram                                                                 Services:
                      (Requirenments from:)                                                                                      Sequence
                                                                                                      The specification          (Choreography) of
                                                                                                       for the services
                                                          One sequence                                  can be derived           Function Calls (RPC)
                  ebXML                                   diagramm per                                  direct from the
                                                                                                      funcional modell
                  service oriented approach                     service




                  Legacy Systems                                                                                                   BSI
                  description about:                                                                                               Business Service
                   - Interface and                                                                                                 Interface = Legacy
                   - Data (Information Model)                                                                                      System Interface
                                                               The BSI implements the interface to
                                                             existing applications (Legacy Systems)

                  External WebServices
                  to be used:
MRI – 23rd Sept. 2007
                 - WSDL                                BPM/UMM - Niki Sahling                                                                              18/35
                                                                WSDL provides all information
                                                                 needed to call such a service
              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
MRI – 23rd Sept. 2007             BPM/UMM - Niki Sahling       19/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


MRI – 23rd Sept. 2007        BPM/UMM - Niki Sahling       20/35
    UN/CEFACT – MRI
 Modelers Reference Initiative


       Newcomers Session
Introduction to ATG2 and XML NDR
        Jostein Frømyr, ATG2 chair


           Stockholm Forum
      Sunday, 23rd September 2007
                                                                         Applied Technologies
                                                                                       Group
    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
ATG1 - EDIFACT Syntax                                     ATG2 - XML Syntax
 Development and maintenance of                           Development and maintenance of XML
   EDIFACT syntax solutions to support                       syntax solutions to support
   UN/CEFACT work program                                    UN/CEFACT work program
                                                           Chaired by Jostein Frømyr
 Chaired by Gait Boxman
                                                           Activities
 Activities                                                        XML Schema production
           Processing of EDIFACT DMRs                              XML Naming and Design Rules, V3
           UML2EDIFACT Project                                          •   Currently at ODP3
              • Currently at ODP6                                   Data Type Library
                                                                         •   Currently at ODP3
                                                                    Standard Business Document Header, v2
                                                                         •   Currently at ODP2
                                                                    XML Representation of Core Components
                                                                         •   Currently at ODP3

MRI – 23rd Sept. 2007                    ATG2/XML NDR - Jostein Frømyr                                 23/35
                                                                                                      ATG in
                                                   CCTS
                                                                                              the big picture
                     Business
  Business       Collaboration
  Domain                                                        Harmonized
                                                                information
                  Describe                                        semantics
                  Business
                Requirements
                                                               Harmonization
 Process &                       BRS
information
                                           Map to standard                          CCL
                                            components                             BIE lib
                                                                                                       NDR
              UMM
                                        Syntax neutral data
                                                                                                                    ATG2
                                                                       RSM

                                                        CCMA                                                     Syntax
                                                                                                 Syntax
                                                                                                creation
                                                                                                                  impl.

                                                                                                                 Syntax
                                 BCSS
                                                                                                               expression
                                                                                             Syntax specific



                                                                                                                            Business
                        ODP                          Forum workflow process                                                   use
       MRI – 23rd Sept. 2007                       ATG2/XML NDR - Jostein Frømyr                                            24/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

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

    202 rules on how to create UN/CEFACT XML
     schemas
        Representation of CCTS components       Use of built-in XSD data types      Use of XML Elements, attributes and types
        Naming                                  Schema location                     Layout and structure of XML schemas
        Modularity                              Versioning                          Annotation
        Namespace                               Extension and restriction           Use of XML schema constructs




MRI – 23rd Sept. 2007                        ATG2/XML NDR - Jostein Frømyr                                                 26/35
                                                                                            The UN/CEFACT
                                                                                                XML puzzle
          BRS                                                                                        ACCs
                                                                                       CC-lib        BCCs

describes the realization of
 requirements defined in                                                          is based on

     RSM and                                                                                         ABIEs
 Message Assembly                       references constructs in                                     BBIEs
   spreadsheet                                                                         BIE-lib       QDTs


     is the source for                                                          is the source for
       generation of                                                              generation of

                              imports                              imports                             imports
     Message.xsd                              BIE.xsd                              QDT.xsd                            Code list.xsd
                                                                               is a restriction of
                                                                                                                 imports
                                                                                   UDT.xsd
                                                                                is the source for
                                                                                  generation of


                                                                                 CDT-library          UDTs
      MRI – 23rd Sept. 2007                            ATG2/XML NDR - Jostein Frømyr                                         27/35
                                                            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/....
MRI – 23rd Sept. 2007       ATG2/XML NDR - Jostein Frømyr           28/35
     UN/CEFACT – MRI
Modelers Reference Initiative

            Newcomers Session
        Open Develop Process Overview
                           Jim Wilson


               Stockholm Forum
              Sun, 23nd September 2007
              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




MRI – 23rd Sept. 2007       Open Develop Process Overview – Jim Wilson   30/##
              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.




MRI – 23rd Sept. 2007       Open Develop Process Overview – Jim Wilson   31/##
              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”



MRI – 23rd Sept. 2007        Open Develop Process Overview – Jim Wilson   32/##
  UN/CEFACT – MRI
Modelers Reference Initiative

  Cross Domain Projects
        Core Component Harmonization (TBG17)
                            Mary Kay Blantz


                       Stockholm Forum
                  Sunday, 23rd September 2007
              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.
MRI – 23rd Sept. 2007    TBG17 - 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)
MRI – 23rd Sept. 2007        TBG17 - May Kay Blantz
                        TBG17                      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
MRI – 23rd Sept. 2007           TBG17 - May Kay Blantz
              TBG17 – Where we fit

                              Develops business and data models
TBG or Liaison                Submits class diagram and core components
                              (CCs/BIEs/qDTs) to TBG17

                                                          Harmonizes across submissions
                              TBG17                       Develops cross-domain library
                                                          Submits to ICG for audit

   Audits based on CCTS rules
   Gives final approval for publication                         ICG


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

MRI – 23rd Sept. 2007                  TBG17 - May Kay Blantz
     UN/CEFACT – MRI
Modelers Reference Initiative

           Cross Domain Projects
                     TBG2 – UNeDocs project
                Niki Sahling (for Sue Probert)

                       Stockholm Forum
                   Sun, 23nd September 2007
                                        UNeDocs is about
                           Cross Border Trade Facilitation




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

                                                           Slide 40
                                                                           Combined Approach



                           Electronic Document Exchange
                                 XML or UN/EDIFACT

                                  <?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.70
                                  UBL_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>


                                                                                           Electronic Edit Form
                                                        <cat:Description>Pencils, box #2
                                  red</cat:Description>
                                                </cat:Item>
                                         </cat:InvoiceLine>
                                  </n:Invoice>




     Paper Document
aligned to UN Layout Key
                                  UNeDocs - Sue Probert
                                                                                                         Slide 41
                                                                               UNeDocs
                                                                          Process Scope

                International Trade Reference Model

                        Buy                           Ship                       Pay



Prepare                                                                   Prepare
                       Export                        Transport                                   Import
for export                                                                 for import


                                                      Regulatory
Commercial              Transport                     Procedures             Financial
Procedures              Procedures                   • Obtain im/export      Procedures
• Establish sales       • Establish transport          licenses etc.        • Provide credit
  contract                contract                   • Provide Customs        rating
• Order goods           • Collect, transport           Declarations         • Insurance
• Advise on delivery      and deliver goods          • Provide cargo        • Execute payment
• Request payment       • Provide waybills,            Declarations         • Issue statements
                        • Goods receipts, etc.       • Apply security
                                                       measures
                                                     • Clear goods

                                          UNeDocs - Sue Probert
                                                                                                   Slide 42
                                                      International Supply Chain
                                                                Actors and Roles

                                       Commercial
                Buyer                     Order                    Seller
                                         Deliver
                                       Pay Supplier

                                       Logistical
                                     Order Transport               Consignor
           Carrier                    Ship Goods                   Consignee
(Transport Service Provider)
                                       Pay Carrier

                                        Regulatory
                               Issue Licences & Certificates       Importer
          Authority                    Clear Goods                 Exporter
                                        Pay Duties                 Carrier


                                        Financial
             Financial              Instruct Payment               Payor
            Institution           Credit/Debit Accounts            Payee
                                   Provide Statements
                                      UNeDocs - Sue Probert
                                              UN/CEFACT Cross-Border Trade
                                                       Business Standards


                                      TBG15
                    TBG2              Trade
                    Digital                                    TBG8        TBG19
  TBG18                               Facilitation
                    Paper                                      Insurance   eGov
  Agriculture
           TBG15 International Trade Single Window Recommendations (33 & 34)


         TBG14 International Supply Chain Model & TBG2 UNeDocs Workbase


                    TBG17 UN/CEFACT Core Component Library
TBG1                                                                           TBG5
Supply                                                                         Finance
Chain           United Nations Trade Data Elements Directory (UNTDED)

                 TBG4                                     TBG13
                                  TBG3
                 WCO DM                                   Environment
                                  Transport
                                  UNeDocs - Sue Probert

                                                                               Slide 45
                                              Cross-Border Trade
                                                  Single Window
                  Materials
      Trade       Management          Transport         Payment   Insurance
B2B




B2G

                        UNeDocs                   Workbase
                           WCO                    Data Model


G2G


                                              Other Govt.
              Customs UNeDocs - Sue Probert   Agencies
                                                                       Slide 46
                                                            UNeDocs BIMs
                                                 Business Information Masters

                                                  Ship BIM
       Buy BIM

                                                                 Transport Equipment BIM
              Materials Management BIM




   Procurement       Supply Chain                            Customs &        Cargo
                                          Transport
                       Logistics                               OGAs         Insurance

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

                                    UNeDocs - Sue Probert
                                                                                    UNeDocs
                                                                            Document Families

                                           UNeDocs
                                       Transport Contract
                                             BIM                 BIM
Document Family

           Customs                            Transport                           Cargo                   Certificates &
          Declaration                         Contract                          Insurance                   Licences
                                               (TBG3)                            (TBG8)                 (TBG15 & TBG18)




 ASEAN      Transit       Import     Space         Consignment       Transport         Waybill          Status     Arrival
 Export                             Booking          Booking       Order/Shipping                      Reporting   Notice
                                                                    Instructions
                                                                                                                             ...
                                   Common Semantics
                                                                                                Etc.
Thai
          ……
                                             Sea         Air             Road           Rail
                                          (IMO …)      (IATA             (IRU,        (UIC …)
                                                         …)            FIATA ...)
                      …                 UNeDocs - Sue Probert
                                                          UNeDocs
                                                Follow up Materials




Project Leaders:
Sue Probert (sue.probert@sepiaeb.com)
Michael Dill (dill@gefeg.com)

Project Documents:
www.unece.org/cefact/forum_grps/tbg/tbg2_edocs/tbg2_edocs.htm




                        UNeDocs - Sue Probert

                                                                 Slide 50
     UN/CEFACT – MRI
Modelers Reference Initiative

       Cross Domain Projects
         International Supply Chain
                   Reference Model
                         Colin Clark
            Stockholm Forum
             Sun, 23nd September 2007
                  International Supply Chain
                       Reference Model


                           and its role in

                        Trade Facilitation &
                          Standardisation
MRI – 23rd Sept. 2007          ISCM - Colin Clark
                  International Supply Chain
                       Reference Model
                        Buy            Ship            Pay


                              and its role in

                        Trade Facilitation &
                          Standardisation
MRI – 23rd Sept. 2007             ISCM - Colin Clark
                        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.


MRI – 23rd Sept. 2007             ISCM - Colin Clark           54/35
                        International Supply Chain Reference Model



                        BUY               SHIP                 PAY


 Prepare                                                   Prepare
   for                  Export          Transport            for          Import
 Export                                                    Import

 Commercial               Transport               Regulatory          Financial
 Procedures              Procedures               Procedures         Procedures




MRI – 23rd Sept. 2007                 ISCM - Colin Clark                      55/35
                            International Supply Chain Reference Model



                            BUY                    SHIP                       PAY


     Prepare                                                              Prepare
       for                   Export              Transport                  for               Import
     Export                                                               Import

                                            INVOLVES
      Commercial                    Transport                   Regulatory                  Financial
      Procedures                   Procedures                   Procedures                 Procedures
• Establish Sales           • Establish Transport          • Obtain Import/Export   • Provide Credit Rating
  Contract                    Contract                       Licences               • Provide Insurance
• Order Goods                                              • Provide Customs
                            • Collect Transport and                                 • Provide Credit
                                                             Declarations
• Advise On Delivery          Deliver Goods                                         • Execute Payment
                                                           • Provide Cargo
• Request Payment           • Provide Waybills,              Declarations           • Issue Statements
                              Goods Receipts Status        • Apply Trade Security
                              Reports                        Procedures
    MRI – 23rd Sept. 2007                      ISCM - Colin• Clark Goods for
                                                             Clear                                  56/35
                                                             Import/Export
Information flows for trade process
                                                                                                                                                                        UN/CEFACT
                                                                                                                                  Other
                            Transport                                                                                                        Customer's         Supplier's
     Customer                                        Supplier                      Carrier              Customs               Governmental
                              Payer                                                                                                            Bank               Bank
                                                                                                                                Agencies


                        Order Goods

                                                                Declare Goods for Export

                                                                                                             Information on
                                                                                                                 Export

                                             Order Transport

                                                                Declare Goods for Departure

                                                                                                             Information on
                Order
                                                                                                                Departure

                                                                             Transport Contract
                Transport
                                                                            Proof of
                                                                           Collection
                                                                Dispatch
                                                                 Advise

                                                      Transport Status

                                                                                        Declare Goods
                                                                                          for Import
                                                                                                             Information on
                                                                                                                  Import

                                Proof of Delivery

                Payment                       Freight Invoice

                            Request Payment

                                                                           Initiate Payment

                                                                                                                                                     Transfer
                                                                                                                                                     Money
      InternationalSupplyChain:

MRI – 23rd Sept. 2007                                                                         ISCM - Colin Clark                                                             57/35
                                               The ISCM Business Processes
    Business Process                            Normative Category             Partner Type         Partner Type
    Obtain Product Information                  Procurement&Sales              Customer             Supplier
    Provide Quotation                           Procurement&Sales              Customer             Supplier
    Negotiate Sales Contract                    Procurement&Sales              Customer             Supplier
    Place Order                                 Procurement&Sales              Customer             Supplier
    Provide Delivery Schedule                   Procurement&Sales              Customer             Supplier
    Advise Despatch                             Procurement&Sales              Customer             Supplier
    Invoice for Order                           Procurement&Sales              Customer             Supplier
    Provide Credit Note                         Procurement&Sales              Customer             Supplier
    Provide Debit Note                          Procurement&Sales              Customer             Supplier
    Advise Remittance                           Procurement&Sales              Customer             Supplier
    Obtain Export Licence etc                   Regulatory Services            Supplier             Authority
    Obtain Import Licence etc                   Regulatory Services            Customer             Authority
    Provide Customs Declaration (Export)        Regulatory Services            Supplier             Authority
    Provide Cargo Declaration (Export)          Regulatory Services            Transporter          Authority
    Provde Customs Declaration (Import)         Regulatory Services            Customer             Authority
    Provide Cargo Declaration (Import)          Regulatory Services            Transporter          Authority
    Clear Goods (Export)                        Regulatory Services            Authority            Transporter, Supplier
    Clear Goods (Import)                        Regulatory Services            Authority            Transporter,Customer
    Pay Customs Tarif                           Regulatory Services            Customer, Supplier   Authority
    Negotiate Transport Contract                Logistical Services            Customer, Supplier   Transporter
    Book Transport                              Logistical Services            Customer, Supplier   Transporter
                                                Logistical Services
    Provide Transport Documentation (WayBill,etc)                              Transporter          Customer, Supplier
    Confirm Delivery                            Logistical Services            Transporter          Supplier
    Provide Status Report                       Logistical Services            Transporter          Customer, Supplier
    Invoice for Transport Service               Logistical Services            Transporter          Customer, Supplier
    Provide Credit Rating                       Financial Services             Bank                 Customer
    Provide Credit                              Financial Services             Bank                 Customer
    Provide Goods Insurance                     Financial Services             Insurer              Customer, Supplier
    Execute Payment                             Financial Services             Customers Bank       Suppliers Bank
    Provide Financial Statements                Financial Services             Bank                 Customer, Supplier


MRI – 23rd Sept. 2007                                     ISCM - Colin Clark                                          58/35
                               The ISCM Business Processes
 Business               Normative              Partner Type   Partner Type
 Process                Category
 Provide Quotation      Procurement &          Supplier       Customer
                        Sales
 Order                  Procurement &          Customer       Supplier
                        Sales
 Obtain Export          Regulatory             Supplier       Authority
 Licence                Services
 Provide Cargo          Regulatory             Transporter    Authority
 Declaration            Services
 (Export)
 Book Transport         Logistical             Transporter    Customer,
                        Services                              Supplier
 Invoice for            Logistical             Transporter    Customer,
 Transport Service      Services                              Supplier
MRI – 23rd Sept. 2007                ISCM - Colin Clark                      59/35
                        Integrating Sector Models




MRI – 23rd Sept. 2007   ISCM - Colin Clark      60/35
                        International Supply Chain Reference Model



                        BUY           SHIP                   PAY

                Expand the Scope                        Provide Reusable
                   and Detail                              Processes




                                     TBGn


MRI – 23rd Sept. 2007              ISCM - Colin Clark                      61/35
                                       ISCM Top Level Structure




MRI – 23rd Sept. 2007   ISCM - Colin Clark                  62/35
                                                         Position TBGn projects into ISCM



uc CrossIndustryInvoice


                                                   «ProcessArea»
                                                   CrossIndustryInvoice




                                                         (from ProcurementSales)




                                                                                   «realize»




 IdentifyProductsAndPartnersEstablishBusinessAgreement            Order               Ship     Pay




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




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




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

        Link to Data Model
class QuoteItem


                          «InformationEnvelope»                                                 «Information...
                            QuoteItemRequest                                                      QuoteItem

                   #    Date:                                                                   #   Date:
                   #    Recipient:                                                              #   Recipient:
                   #    Sender:                                                                 #   Sender:


                                                                                      +header                     +body
         +header                              +body

                                                                                   «Information...
    «Information...                        «Information...                        QuoteItemHeader                 «Information...
   QuoteItemHeader                         QuoteItemBody                                                          QuoteItemBody
                                                                                  #    Reference:
                                          #   Quality:                                                            #   Quality:
                                          #   Quantity:                                                           #   Quantity:




                                        Core Components
                                        Message Assembly
MRI – 23rd Sept. 2007                                        ISCM - Colin Clark                                                   66/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



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


MRI – 23rd Sept. 2007   ISCM - Colin Clark                  68/35
    UN/CEFACT – MRI
 Modelers Reference Initiative


Data and Process Modeling
   Latest CCMA draft specification
            Fred van Blommestein


          Stockholm Forum
        Sun, 23nd September 2007
                        What is a Document or
                         Business Message
                                 not?

       An arbitrary collection of (grouped) data elements




MRI – 23rd Sept. 2007          CCMA - Fred van Blommestein   70/35
                        What is a Document or
                         Business Message?
   • 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

     The exchange of a Business Message is an event
               with Business implications
MRI – 23rd Sept. 2007          CCMA - Fred van Blommestein   71/35
 B2B                         Common knowledge
                          Orders, Products, Locations,
                               Commitments, …




             Reporting                                           Reporting
                          Local                       Local
             events and                                          events and
                          system                      system
             decisions                                           decisions

                           • Business Messages
                           • Synchronization of knowledge
                             about real world objects
                           • Process steps
Business Partner 1                                               Business Partner 2
MRI – 23rd Sept. 2007              CCMA - Fred van Blommestein                        72/35
                        Knowledge updating

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



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

  MRI – 23rd Sept. 2007           CCMA - Fred van Blommestein                  74/35
                          MBIEs
• 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
MRI – 23rd Sept. 2007     CCMA - Fred van Blommestein               75/35
                        CCMA basic structure
                                                                            1..*
                             <<InformationEnvelope>>          is valid in
                                                                                   Business Context
                             Business Message Type            contains      1..1
                                                                                   <<InformationEntity>>

                                                                                   Business Document
                                                                                         Header
                                                       ASMA

                                                1..*            0..*


                                                <<InformationEntity>>                 ASMBIE
                                                 Messaging Business
                                                  Information Entity
            ABIE with
             actions                                          Based on
                                                                0..*


                                                 Aggregate Business                   ASBIE
                                                  Information Entity

MRI – 23rd Sept. 2007          CCMA - Fred van Blommestein                                            76/35
                        Grouping and Sequencing

• 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



MRI – 23rd Sept. 2007           CCMA - Fred van Blommestein   77/35
                                        MBIE Grouping

                                                                                                     1..*
                                            <<InformationEnvelope>>                    is valid in               Business
   No semantics,                                                                                                  Context
                                             Business Message Type
  No property term                                                                     contains
                                                                                                      1..1

                                                                                                             <<InformationEntity>>

                                                                                                              Standard Business
                                                                                                              Document Header
              ASMA                       ASMA                                 ASMA


                        0..*                                         0..*                0..*
                                                  0..*


                          <<InformationEntity>>               0..*          <<InformationEntity>>                ASMBIE

                               Message Assembly             ASMA            Messaging Business
                                                                             Information Entity




MRI – 23rd Sept. 2007                                    CCMA - Fred van Blommestein                                            78/35
                                Logical view vs.
                            technical implementation
                  Logical definition,                                                       Physical
            presentation to the application                                               interchange
   Business                   Business           Business                                   Business
Document Header            Document Header    Document Header                            Document Header
:Header Instance           :Header Instance   :Header Instance                           :Header Instance




Business Message           Business Message   Business Message                 Business Message         Business Message
 Type: Business             Type: Business     Type: Business                   Type: Business           Type: Business
     Message                    Message            Message                          Message                  Message
    Instance 1                 Instance 2         Instance 3                       Instance 1               Instance 3
                                                                                          Business Message
                                                                                           Type: Business
                                                                                               Message
                                                                                              Instance 2
   MRI – 23rd Sept. 2007                         CCMA - Fred van Blommestein                                   79/35
                          Constraints
• 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




MRI – 23rd Sept. 2007          CCMA - Fred van Blommestein               80/35
                           Modular Process Steps
                                Common knowledge
                             Orders, Products, Locations,
                                  Commitments, …
                 View on                                          View on
                                             Updates

                 State                                              State
           (precondition)
                                    Process                      (postcondition)
                                     Step

                                            Defines
Precondition =                                                      Postcondition = Goal
Information Requirements             Schema
to perform the Process Step
  MRI – 23rd Sept. 2007            CCMA - Fred van Blommestein                      81/35
                        CCMA Guide

• 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




MRI – 23rd Sept. 2007     CCMA - Fred van Blommestein   82/35
    UN/CEFACT – MRI
 Modelers Reference Initiative

Data and Process Modeling
          Advanced Possibilities
                   Glenn Miller


         Stockholm Forum
       Sun, 23nd September 2007
        UN/CEFACT - Advanced Possibilities




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

    Work Product
           Business Processes
           Business Artifacts
           Requirements for Implementation
    Workflow
           Organization of Information
           "Approval" of information
           Publication of Information


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

 Business Requirements Specification
 Business Models
 Core Components
 Requirements Specification Mapping
 Schema Generation




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

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

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



MRI – 23rd Sept. 2007          Data and Process Modeling - Glenn Miller     89/35
                                     The Process Without a Registry
     TBG                  Steering
    Project              Committee                 Create a BRS          Submit BRS to               Perform Modeling           Create Core
(Project Team)          for approval               (Project team)         Steering/ICG                (Project Team)            Components




                                                                                                  Process
                          Distribution                                     Distribution         Harmonization   Distribution
                              List                                             List                                 List




                                                     Submit Work
                        Create Schemas              Product to ATG/          Submit to ICG              Create an RSM          Submit to TBG17
                                                        ATG2




                                                        Distribution             Distribution
                                                            List                     List                                         Distribution
                   Submit to ICG for Publication                                                                                      List




MRI – 23rd Sept. 2007                                  Data and Process Modeling - Glenn Miller                                                  90/35
                    Global Implementers
                               The Process with a Registry

         TBG              Steering
        Project          Committee           Perform Modelling                         Handover to
                                                                 ICG Reviews BRS                       ICG Reviews RSM
    (Project Team)      for approval                                                     TBG17




                                                                                                           Global Implementers
                                                                   Registry/
                                                                   Repository

                                                                                                     ICG Publishes
                               ATG Creates
                                                                                                         Project
                                Schemas
                                                                                                       (Standard)




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

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


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

    Glenn Miller
           Senior Partner – G.F. Miller Consulting Ltd
           Glenn.miller@gfmiller.com
           +001.613.820-5478 (Office)
           +001.613.853-3520 (Mobile)




MRI – 23rd Sept. 2007      Data and Process Modeling - Glenn Miller   94/35
                          UN/CEFACT
                        SIMPLE, TRANSPARENT AND EFFECTIVE PROCESSES
                                    FOR GLOBAL BUSINESS.




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

				
DOCUMENT INFO
Shared By:
Categories:
Tags:
Stats:
views:12
posted:6/26/2011
language:English
pages:92