Common Business Processes Catalog

1. Common Business Processes Catalog  2004

2. Common Business Process Catalog Objective of Presentation To report on Progress with two Projects - Catalog Specification Project - Proof of Concept Project Seek Input for next steps

3. What is the common business process catalog ? A business library Hosted in a Global Registry/Repository Containing details of common business processes Where businesses can �publish� and find processes used by other trading partners Classified so as to provide ease of identifying candidate processes And support references to Core Components, BPSS etc and support e-business in accordance with UN/CEFACT standards

4. CBPC Specification

5. Catalog Information Model

6. Usage of CBPC Store, query and integrate business process artifacts, such as: Process descriptions and instances Reusable business transactions Can provide the capability to associate key business elements: Business processes Business documents Information elements (e.g., BIE, CC) Facilitate other business and technical operational components. Provide inputs for: Technical agreements Electronic exchange

7. Global Registry Content Life Cycle Populate Avoid ambiguity Must be globally acceptable Must be generic in nature Applicable across multiple industries Simple and clear to understand Populate Avoid ambiguity Must be globally acceptable Must be generic in nature Applicable across multiple industries Simple and clear to understand

8. ClassificationScheme instances are RegistryEntry instances that describe a structured way to classify or categorize RegistryObject instances. The structure of the classification scheme may be defined internal or external to the registry, resulting in a distinction between internal and external classification schemes. ClassificationNode instances are RegistryObject instances that are used to define tree structures under a ClassificationScheme, where each node in the tree is a ClassificationNode and the root is the ClassificationScheme. Classification instances are RegistryObject instances that are used to classify other RegistryObject instances. A Classification instance identifies a ClassificationScheme instance and taxonomy value defined within the classification scheme. ClassificationScheme instances are RegistryEntry instances that describe a structured way to classify or categorize RegistryObject instances. The structure of the classification scheme may be defined internal or external to the registry, resulting in a distinction between internal and external classification schemes. ClassificationNode instances are RegistryObject instances that are used to define tree structures under a ClassificationScheme, where each node in the tree is a ClassificationNode and the root is the ClassificationScheme. Classification instances are RegistryObject instances that are used to classify other RegistryObject instances. A Classification instance identifies a ClassificationScheme instance and taxonomy value defined within the classification scheme.

9. Technical View of Registry/Repository Notes for Page 16 Implemented a prototype system: 1. Core scenarios: Used OAG STAR Business Object Documents (BOD), which were stored in Reg/Rep (OAGIS nouns and verbs). 2. Core business processes � BP and CPA. General Motors mandated the CPA. Focused on business collaboration first. RI Detailed Description The ebXML Registry Repository version 2.0 (Reg/Rep) was used to discover, classify, store and query the documents and trading partner relationships associated with the ebXML RI. These documents include the Collaboration Protocol Profile (CPPs), Collaboration Protocol Agreements (CPAs), Business Process Specifications (BPSS), Core Components (CC) or OAG BODs, and document type definitions (DTDs). The following is a short list of the accomplishments associated with the RI: �Provided the first fully 2.0-compliant Reg/Rep implementation available in the market. �Provided a JAXR pluggable provider implementation. �Provided a SOAP tool for submitting documents with attachments to the Reg/Rep. �Designed and submitted the meta-data classification schema that describes the organization of the RI documents. �Provided a swing-based GUI browser customized for the ebXML demo. �Provided a Java web-start-based browser and access to a global registry. �Provided security including authentication and authorization using user profiles and digital certificates. �Provided audit trail for the stored objects. Notes for Page 16 Implemented a prototype system: 1. Core scenarios: Used OAG STAR Business Object Documents (BOD), which were stored in Reg/Rep (OAGIS nouns and verbs). 2. Core business processes � BP and CPA. General Motors mandated the CPA. Focused on business collaboration first. RI Detailed Description The ebXML Registry Repository version 2.0 (Reg/Rep) was used to discover, classify, store and query the documents and trading partner relationships associated with the ebXML RI. These documents include the Collaboration Protocol Profile (CPPs), Collaboration Protocol Agreements (CPAs), Business Process Specifications (BPSS), Core Components (CC) or OAG BODs, and document type definitions (DTDs). The following is a short list of the accomplishments associated with the RI: �Provided the first fully 2.0-compliant Reg/Rep implementation available in the market. �Provided a JAXR pluggable provider implementation. �Provided a SOAP tool for submitting documents with attachments to the Reg/Rep. �Designed and submitted the meta-data classification schema that describes the organization of the RI documents. �Provided a swing-based GUI browser customized for the ebXML demo. �Provided a Java web-start-based browser and access to a global registry. �Provided security including authentication and authorization using user profiles and digital certificates. �Provided audit trail for the stored objects.

10. CBPC POC Architecture

12. CBPC and RIM mapping � Contd...

13. Implementation in Client Login to the registry Discovery Select CBPC query link under search option Search by specifying parameters or thru browse and drill down Preparation Submit entries to be incorporated in the CBPC Enter the basic and additional information Population Select the entries thru Discovery mechanism Evaluate - Accept / reject / hold the submitted entries Populate � Upload the accepted entries onto a centralized CBPC repository Maintenance Select the entries thru Discovery mechanism Update the Catalog details as in Preparation Maintain metadata information for use in classifying CBPC information

14. BIZ-REG Registry This is the home page . User can search the catalog without login . Browse and drill down option and CBPC query link can be used to discover Catalog.This is the home page . User can search the catalog without login . Browse and drill down option and CBPC query link can be used to discover Catalog.

15. Discovery phase � Browse and drill down UN-CEFACT reference model shown in slide is equivalent to the Porter value chain . Provide purchase order is a business transaction and is appearing under Procurement/Sales/Negotiation . CBPC root node contain additional metadata like Economic agent, Role , Context etc as Child node of CBPC classification scheme. UN-CEFACT reference model shown in slide is equivalent to the Porter value chain . Provide purchase order is a business transaction and is appearing under Procurement/Sales/Negotiation . CBPC root node contain additional metadata like Economic agent, Role , Context etc as Child node of CBPC classification scheme.

16. Discovery phase � Parameter based search User can select any of the parameter shown in slide and can input keyword and will find the result at the bottom of the page . For example provide purchase order has been keyed in and the search result has been shown at the bottom . Clicking on red link show the details of this transaction.User can select any of the parameter shown in slide and can input keyword and will find the result at the bottom of the page . For example provide purchase order has been keyed in and the search result has been shown at the bottom . Clicking on red link show the details of this transaction.

17. Populate Catalog �.Contd. This page appears after submitting the data in previous slide . User can Click on individual tab like Classification , Association, External identification , External Link, Slot etc to provide the addition metadata for Transaction I.e Provide purchase order. In this slide ,Association tab appears in yellow color means this is the active tab and user can use button Role , Business, Event etc appearing below to get the corresponding screen and add the necessary data. In the above slide Role details are appearing at bottom after the addition.This page appears after submitting the data in previous slide . User can Click on individual tab like Classification , Association, External identification , External Link, Slot etc to provide the addition metadata for Transaction I.e Provide purchase order. In this slide ,Association tab appears in yellow color means this is the active tab and user can use button Role , Business, Event etc appearing below to get the corresponding screen and add the necessary data. In the above slide Role details are appearing at bottom after the addition.

18. Acknowledgments Nita Scharma William McCarthy http://www.msu.edu/user/mccarth4/ Colin Clark Brian Leapman Bob Haugen Alan Kotok Farrukh Najmi John Junker Monica Martin and Many Others