SC32/WG 1 e-Business Standards Prepared for: 26 May 2008 WG 1 Tutorial Paul Levine, Convenor Telcordia Technologies, Inc. 26 May 2008 JTC1 SC32N1763

ISO e-Business Standards  ISO/IEC Information technology – Open-edi reference model  ISO/IEC Information technology - Business Operational View:  Part 1: Operational aspects of Open-edi for implementation  Part 2: Registration of scenarios and their components as business objects  Part 3: Open-edi description techniques (OeDT)  Part 4: Business transaction scenarios - Accounting and economic ontology  Part 5: Identification and referencing of requirements of jurisdictional domains as sources external constraints  Part 6: Technical Introduction of eBusiness modelling  Part 7: eBusiness vocabulary  Part 8: Identification of privacy requirements as external constraints on business transactions

Open-edi environment

ISO/IEC Open-edi Reference Model  Targeted for FDIS ballot of third edition  Single English/French document  Based on second edition (English) + French text of the first edition, amended according to the second English edition  No technical changes  Update references and dates for standards referenced in Clause 3 Terms and Definitions  Update format in accordance with JTC1  It is noted that the 2 nd edition (2004) is up for review no later than 2009 anyway

ISO/IEC Part 1 - Operational aspects of Open-edi for implementation  Targeted to FDIS ballot of second edition  Incorporate Technical Corrigenda (3-level ToC)  Editorial corrections of the first edition  Specifying “person” as “Person” where appropriate  Updating for consistency with all parts of and the proposed third edition of  Update references and dates for standards referenced in Clause 3 Terms and Definitions  Update format in accordance with JTC 1 Directives  It is noted that the revisions to this proposed second edition are all editorial and that this standard is due for review anyway.

ISO/IEC Part 3 - Open-edi Description Techniques  Incorporates UN/CEFACE Modeling Methodology (for business process specification) by reference  UMM Meta Model - Base Module  UMM Meta Model - Foundation Module  Integrates ITU-T External Terminology Schema data design methodology into the UMM Business Information View  Category C liaison for this collaboration has been established under the auspices of the MoU between IEC, ISO, ITU and UN/ECE Concerning Standardization in the Field of Electronic Business

ISO/IEC Part 3 (major outline)  5 OeDT components (based on MoU between IEC, ISO, ITU and UN/ECE on electronic business)  5.1 UN/CEFACT Modeling Methodology (UMM) overview  Business domain view  Business requirements view  Business transaction view  5.2 External terminology schema (ETS) methodology (from ITU-T SG 4) overview  6 ETS methodology  6.1 Requirements on ETS notations  6.2 ETS format  7 Data interchange based on ETS methodology  7.1 ETS message construct  7.2 Generic order ETS  7.3 Derivation of an XML document template from an ETS

UMM Foundation Module Structure  5 Foundation  5.1 Business Domain View  5.2 Business Requirements View  Business Process View  Business Entity View  Partnership Requirements View  5.3 Business Transaction View  Business Choreography View  Business Interaction View  Business Information View

UMM Business Interaction View

ETS data design methodology  Extracted from ITU-T Recommendations  Rec. Z.601 Data architecture of one software system  M.1400 series recommendations  ETS provides the data definition for the UMM Business Information View  Open-edi scenario (business process) is decomposed to the individual steps that take the scenario through the state transitions of the affected business entities  Individual steps follow the atomic UMM business transaction patterns (referred to as SOA interactions)  Requestor provides the data expected by the Provider  Provider performs the expected service and responds with status of the result, including response data  Data to be interchanged in the Open-edi scenario is specified by an ETS

ETS graph for Service Management Employee Customer Operator Price Market Product Corporation Deal Contract Account Address Type Installat ion Type Role S Use Member ship Role Structur e Catalogue Country Association

ETS from ITU-T Rec. M.1403 Generic Order

ISO/IEC (the Open-edi Accounting & Economic Ontology)  ontology = categories of interest in a domain and the relationships among them  ISO is a collaboration space ontology with:  Exchanges (shown in green)  Policies (shown in yellow)  Plans (shown in purple)  For interoperability standards alignment, is being used in UN/CEFACT as a specialization module for the UMM  UML class diagrams specify the declarative components; procedural aspects illustrate operation of a collaboration space state machine.

Economic Event Economic Resource Person resource-flow from to Economic Commitment reciprocal fulfillment duality Economic Resource Type typification Economic Event Type Economic Role economic specification typification participate business policy 1.Green – Exchanges “What value exchanges have occurred” 2.Yellow – Policies “What policies or business rules govern exchanges” 3.Purple – Plans “What exchanges are planned or scheduled” 4.Black – Other classes not shown (economic contract, business events, claims, process phases, etc) economic specification

Negotiation Identification Planning Post-Actualization Actualization ISO Extended Collaboration Model “OLD” accounting- oriented model “NEW” business- process- oriented model

BT PhaseExample Business Event PlanningSeller publishes Catalog Buyer sends CatalogRequest to Seller Seller sends Catalog to Prospective Buyer IdentificationBuyer sends AvailabilityandPriceRequest to Seller Seller returns AvailabilityandPriceResult to Buyer NegotiationBuyer sends Offer to Seller Seller sends CounterOffer to Buyer Buyer accepts details of CounterOffer on Shipment and proposes PaymentSchedule Seller accepts PaymentSchedule, completing Contract specification (alternatively, another CounterOffer would loop or a NonAcceptance would suspend or abandon the Business Transaction) ActualizationSeller sends an AdvanceShippingNotice when goods are prepared for shipping Buyer sends ReceivingReport to Seller when inspected goods are accepted Seller sends an Invoice to Buyer after parts are shipped Buyer sends RemittanceAdvice to Seller with information about payment of the Invoice Post- Actualization Buyer sends WarrantyInvocation to Seller An Example Open-edi Collaboration with Business Events Grouped in Phases

Business Process Business Process Business Process Enterprise #1 Business Process Business Process Business Process Enterprise #3 Enterprise #2 Business Process Business Process Business Process Collaboration Perspective: Trading Partner vs. Independent Independent view of Inter-enterprise events (ISO ) Trading Partner view of Inter-enterprise events (upstream vendors and downstream customers) Dotted arrows represent flow of goods, services, and cash between different companies; solid arrows represent flows within companies Japan expert contribution to , 22 Oct 2001, Victoria BC,

ISO/IEC Part 5 – identification and referencing of requirements of jurisdictional domain as sources of external constraints  Objectives of Part 5  Introduction of external constraints in business transaction modeling  Address specific aspects of business agreement semantic descriptive techniques in order to be able to support legal requirements in modeling business transactions  Present a methodology and tools for specifying common classes of external constraints through the construct of “jurisdictional domain” (with various levels and categories of jurisdictional domains)  Demonstrate that external constraints of a jurisdictional domain lend themselves to being modeled through scenarios and scenario components (already demonstrated in Annex I, Part 1)

ISO/IEC Part 5 – identification and referencing of requirements of jurisdictional domain as sources of external constraints  Major Topics of Part 5  Key common requirements of jurisdictional domains include:  that of official language(s) or if not applicable, its de facto language  that of the need to be able to differentiate when a Person in a business transaction in the role of “buyer” is an individual  that where an individual if a party to a business transaction common public policy requirements apply as external constraints including consumer protection, privacy protection, individual accessibility, and other rights that a “human being” has.  Focus on ensuring unambiguity in the semantic components and information bundles comprising a business transaction as these are used in the making of binding “commitments”  Extensive work on “official, de facto and “legally recognized languages (LRL)”, importance of gender in language to support semantic unambiguity, use of human interface equivalents(HIEs)  Extensive set of detailed normative and informative Annexes

ISO/IEC Part 5 – identification and referencing of requirements of jurisdictional domain as sources of external constraints  Example of business transaction modelling with internal constraints only [see Figure 4] and then with external constraints [see Figure 6] in a “collaboration space”. [ Part 5,Figure 4 - Accounting and economic ontology (internal constraints only): Buyer, seller and common collaboration space with a third party (Graphic illustration)] Value Exchang e Buye r Seller Third Party Collaboration Space

ISO/IEC Part 5 – identification and referencing of requirements of jurisdictional domain as sources of external constraints  Example of business transaction modelling with internal constraints only [see Figure 4] and then with external constraints [see Figure 6] in a “collaboration space” Part 5, Figure 6 — Accounting and economic ontology with external constraints: Common Collaboration Space — Buyer, Seller and Regulator utilizing a Third Party (Graphic Illustration) Buyer Seller Value Exchange Third Party Regulator Collaboration Space

ISO/IEC TR Part 6 - Technical Introduction of eBusiness modelling  Objectives of this TR  Introduction to common understandings of Business Modeling for the inter-enterprise Business Collaborations  Modeling Guideline particularly focused on the inter- enterprise business process in a collaboration space where buyer, seller and various third party are involved  Major topics  Concepts and Principles of e-Business Modeling  Classification Scheme to identify the class and type of Business Transactions  Key Attributes for Classification of Business Transactions

23 Business Process Scope of ERP Scope of e-Business (Inter-enterprise Process ） Enterprise Diversity of e-Business Model - Various Pricing Models - Various 3d Party Roles TR View Point of Inter-enterprise Business Collaboration Business Process Business Process Business Process Business Process Business Process Business Process Business Process Business Process Enterprise

ISO/IEC Part 7 - eBusiness Vocabulary  Objectives  Single consolidated vocabulary of eBusiness concepts (their definitions and terms) as found in the ISO/IEC Open-edi Reference Model and the existing Parts of the multipart ISO/IEC eBusiness standard (including definitions and their terms used taken from other int’l ISO standards)  Provide rules, guidelines and procedures governing the formation of definitions for concepts relevant to eBusiness and choice of associated terms as a single harmonized and integrated controlled vocabulary. This includes rules governing multilingual expandability that integrate and support cultural adaptability requirements via human interface equivalents (HIEs)  Identify the essential data elements for each entry, their rules and specifications as well as rules for ensuring quality and integrity control requirements for each entry and their interworking doing so in an IT-enabled manner.  1 st edition already contains Chinese, English, French & Russian equivalents for eBusiness concepts and their definitions as well as (grammatical) gender codes for terms where applicable in a language

ISO/IEC Identification of privacy requirement as external constraints on business transactions  CD completed. Ballot comments to be resolved at WG1 Sydney BRM.  Objectives  Provide method(s), rules required to support the additional BOV specifications applicable to the recorded information in a business transaction where such is of the nature of “personal information”, i.e. pertaining to an identifiable “individual”  Provide fundamental principles governing privacy protection requirements in business transactions (external constraints perspective only)  Integrate normative and informative elements in support of privacy and data protection requirements (as already found in ISO/IEC and existing Parts of ISO/IEC into a single document (These constitute 90%+ of the CD document)  Focus on identifiable living individuals as buyers in a business transaction  Link to information management life cycle (ILCM) requirements but focus on “collaboration space” aspects and not internal behaviors of an organization or public administration (that are excluded as are Functional Service View (FSV) aspects including security services)