1 / 75

Electronic Business Based on RosettaNet – Case Study of Supply Chain Management

Electronic Business Based on RosettaNet – Case Study of Supply Chain Management . Ching-Long Yeh 葉慶隆 Department of Computer Science and Engineering Tatung University Taipei, Taiwan Email: chingyeh@cse.ttu.edu.tw (msn) URL: http://www.cse.ttu.edu.tw/chingyeh. Contents.

MartaAdara
Download Presentation

Electronic Business Based on RosettaNet – Case Study of Supply Chain Management

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Electronic Business Based on RosettaNet –Case Study of Supply Chain Management Ching-Long Yeh 葉慶隆 Department of Computer Science and Engineering Tatung University Taipei, Taiwan Email: chingyeh@cse.ttu.edu.tw (msn) URL: http://www.cse.ttu.edu.tw/chingyeh

  2. Contents • Evolution of Web Technology • RosettaNet • E-Supply Chain Management Based on RosettaNet at Tatung Company EB RosettaNet

  3. Evolution of Web Technology

  4. WWW Information Pool HTTP (Hyper Text Transport Protocol) HTML (Hyper Text Markup Language) URL (Uniform Resource Locator) Application Client Web server URL HTML Document HTTP • Human-to-machine interaction • Information explosion EB RosettaNet

  5. Interactions Using XML Information Pool Information Pool XML (eXtensible Markup Language) SOAP (Simple Object Access Protocol) Application Application SOAP server SOAP server XML Document XML Document HTTP • Machine-to-machine interaction • Service automation EB RosettaNet

  6. What is XML? • Extensible Markup Language • A Syntax for Documents • A Meta-Markup Language • A Structural and Semantic Language, not a Formatting Language • Not just for Web pages EB RosettaNet

  7. XML Technology • DTD • Namespace • Schema • DOM • CSS, XSL-T, XSL-FO • XLink • XPointer EB RosettaNet

  8. XML Protocol: SOAP EB RosettaNet

  9. Web Service Architecture EB RosettaNet

  10. Business processes, business documents Business processes, business documents Secure and reliable message services Secure and reliable message services AP-2-AP Business Interactions • RosettaNet • Partner Interface Processes, PIPTM • RosettaNet Implementation Framework, RNIF • A domain-specific EB framework for industry vertical integration Company B Company A Backend Application Backend Application EB RosettaNet

  11. View of Private and Public Processes BSI: Business Service Interface EB RosettaNet

  12. ebXML: A Generic EB FrameworkSOA for EB • A generic EB framework for cross-industry horizontal integration EB RosettaNet

  13. Phases in the Use of the ebXML Framework The implementation phase EB RosettaNet

  14. Phases in the Use of the ebXML Framework The discovery phase EB RosettaNet

  15. Phases in the Use of the ebXML Framework The runtime phase EB RosettaNet

  16. Components of the ebXML Framework • Defining how public business-process must be described using the ebXML BPSS standard. • Defining the semantics of business documents that are exchanged in public processes using ebXML’s Core Component (ebCC) standard. • Definition of services and the constraints in using the services using Collaboration Protocol Profile (CPP) defined in the ebXML CPPA standard. • Description of the mutual agreement between the business partners – Collaboration Protocol Agreement (CPA) – to carry out the public business process. The schema for a CPA is also defined by ebXML CPPA standard. • Protocols for registering, storing, and retrieving public business processes and associated business documents, and CPPs using the ebXML Registry standard. • A standard way to send and receive messages between business partners, as defined in the ebXML Message specification. EB RosettaNet

  17. RosettaNet

  18. Background • RosettaNet • A non-profit consortium • More than 500 members • Founded in February 1998, including • Computer and Consumer Electronics (CCE), • Electronic Components (EC), • Semiconductor Manufacturing (SM) • Telecommunications (TC) industries • the Logistics (LG) and Solution Provider (SP) communities • Open e-business standards and services • Breaking language barriers and establishing a global language for e-business • Companies can realize the full potential of the digital economy, • highly effective trading networks, • operational efficiencies and • new business opportunities EB RosettaNet

  19. Trading Partner Trading Partner Create content Wrap it Send it Receive it Unwrap it Process content Technical Concept of RosettaNet EB RosettaNet

  20. Technical Components • Partner Interface Processes (PIPsTM) • Dictionaries and Codes • RosettaNet Implementation Framework (RNIF) Core EB RosettaNet

  21. Technical Components - PIP™ • Partner Interface Process (PIP) • Encapsulate business processes • Specify structure and format of business document payloads • Specify activities, decisions, and roles for each trading partner involved in a particular business activity EB RosettaNet

  22. Cluster 3: Order Management Segment A : Quote and Order Entry PIP 3A1 - Provide QuotePIP 3A2 - Query Price and AvailabilityPIP 3A3 - Transfer Shopping CartPIP 3A4 - Manage Purchase OrderPIP 3A5 - Query Order StatusPIP 3A6 - Distribute Order Status Segment B : Transportation and Distribution Segment C : Returns and Finance Technical Components - PIP™ Categorized by high-level business function (cluster) and sub-function (segment) EB RosettaNet

  23. Technical Components - PIP™ • What is the composition of a PIP? • Distributed as downloadable .zip file from rosettanet.org website • Specification (.doc) + errata document(s) • XML DTDs describing schema of business document payload (.dtd) • Message guidelines (.htm) – cardinality, code lists, definitions EB RosettaNet

  24. PIP ClassificationClusters • Cluster 0: RosettaNet Support • Cluster 1: Partner Product and Service Review • Cluster 2: Product Information • Cluster 3: Order Management • Cluster 4: Inventory Management • Cluster 5: Marketing Information Management • Cluster 6: Service and Support • Cluster 7: Manufacturing EB RosettaNet

  25. PIP 2A2 Query Product Information Business Process Model EB RosettaNet

  26. PIP 3A4 Request Purchase Order Business Process Model EB RosettaNet

  27. Technical Components - PIP™ • Specification uses Open-EDI Reference Model (ISO/IEC 14662) concepts • Business Operational View (BOV) • Business aspects of business transactions • Functional Service View (FSV) • Technical aspects of business transactions • Implementation Framework View (IFV) • RosettaNet implementation aspects EB RosettaNet

  28. From PIPTM3A4 Business Process Flow Diagram in BOV EB RosettaNet

  29. Table 3-3: Business Activity Performance Controls Acknowledgment of Receipt Role Name Activity Name Time to Acknowledge Acceptance Time to Perform Retry Count Is Authorization Required? Non-Repudiation of Origin and Content? Non-Repudiation Required? Time to Acknowledge Create Purchase Order Y 2hr 24hr 24hr 3 Y Y Buyer Cancel Purchase Order Y 2hr 24hr 24hr 3 Y Y Buyer Buyer Revise Purchase Order Y 2hr 24hr 24hr 3 Y Y From PIPTM3A4 Business Process Activity Controls in BOV EB RosettaNet

  30. :Buyer :Seller 1. request(:PurchaseOrderRequestAction) 1.1. signal(:ReceiptAcknowledgement) 2. response(:PurchaseOrderAcceptanceAction) 2.1. signal(:ReceiptAcknowledgement) From PIPTM3A4 Business Transaction Dialog in FSV Purchase Order Request Dialog EB RosettaNet

  31. Table 5‑1: Business Message and Communications Specification # Business Message Guideline Digital Signature Required? SSL Required? 1. Purchase Order Request Guideline Y Y 1.1 Receipt Acknowledgement Guideline Y Y 2. Purchase Order Acceptance Guideline Y Y 2.1 Receipt Acknowledgement Guideline Y Y From PIPTM3A4 IFV Purchase Order Request Dialog EB RosettaNet

  32. From PIPTM3A4 XML DTD <!ENTITY % common-attributes "id CDATA #IMPLIED" > <!ELEMENT Pip3A4PurchaseOrderAcceptance ( PurchaseOrder , fromRole , toRole , thisDocumentGenerationDateTime , thisDocumentIdentifier , requestingDocumentIdentifier , GlobalDocumentFunctionCode , requestingDocumentDateTime ) > <!ELEMENT PurchaseOrder ( deliverTo? , comment? , GlobalPurchaseOrderStatusCode , EB RosettaNet

  33. From PIPTM3A4 Message Guidelines - Cardinality 1 PurchaseOrder 2 0..1 |-- deliverTo.PhysicalAddress 3 0..1 | |-- GlobalLocationIdentifier 4 1 | |-- cityName.FreeFormText 5 1 | |-- addressLine1.FreeFormText 6 0..1 | |-- addressLine2.FreeFormText 7 0..1 | |-- addressLine3.FreeFormText 8 1 | |-- GlobalCountryCode 9 0..1 | |-- NationalPostalCode 10 1 | |-- regionName.FreeFormText 11 0..1 |-- comment.FreeFormText 12 0..1 |-- packListRequirements.FreeFormText 13 1..n |-- ProductLineItem 14 1..n | |-- shipFrom.GlobalLocationIdentifier TM EB RosettaNet

  34. From PIPTM3A4 Message Guidelines – Business Properties Name Definition deliverTo The partner to which the product must be delivered. cityName The name of a city. addressLine1 The first line of a physical address. addressLine2 The second line of a physical address. addressLine3 The third line of a physical address. regionName The name of a state or province within a country. comment Free form textual comment attached to a business document. packListRequirements Free form textual description, on the pack list, of requirements relating to the packing of the product. shipFrom DUNS®+4 number of the location where the product is to be shipped from. productUnit A unit of product, e.g. an each or a package. countryOfOrigin Country where product originates. contractIdentifier The unique number than identifies a contract. EB RosettaNet

  35. Trading Partner Trading Partner Create content Wrap it Send it Receive it Unwrap it Process content PIP™ Summary A PIP specifies the structure and format of the business document payload for a particular business activity. The business content is an XML document. • It is conceptually very simple. It also specifies the exchange protocol between trading partners for that activity. EB RosettaNet

  36. Technical Components - Dictionaries Why Use Dictionaries and Codes? Simply… • To ensure the consistency of information exchanged between trading partners when executing PIPsTM. EB RosettaNet

  37. Technical Components - Dictionaries • It is conceptually very simple… Trading Partner Trading Partner Create content Wrap it Send it Receive it Unwrap it Process content Dictionary Dictionary EB RosettaNet

  38. Codes and Dictionaries • Partner Identification (DUNS®) • Product Identification • Product Number (GTIN) • Product Classification (UN/SPSC) • Product Descriptions (Dictionaries) EB RosettaNet

  39. Where are they used? • Partner Identification (DUNS®) – used by PIPsTM to uniquely identify trading partners and their locations • Product Identification (GTIN) – used by PIPs to identify products • Product Identification (UN/SPSC) – used by Product Information PIPs (Cluster 2) as classification schema EB RosettaNet

  40. Partner Identification • DUNS® Numbering • “Data Universal Numbering System” • Managed by DUN and Bradstreet(www.dnb.com) • Nine Digit Number • No Embedded Intelligence • Guaranteed Unique Partner Identifier • Used in Every RosettaNet PIPTM EB RosettaNet

  41. DUNS® Numbering • DUNS® Use Worldwide • 62 Million DUNS numbers worldwide • 26.4 Million in Europe • 23.3 Million in the United States • 4.6 Million in Asia Pacific • 1.6 Million in Canada • 753 Thousand in Latin America • 135 Thousand in the Middle East • 114 Thousand in Africa EB RosettaNet

  42. DUNS® Numbering • DUNS® Numbers are Available for “Any Business Location with Unique, Separate and Distinct Operations” • Not Assigned to Multiple Departments at a Single Location or to Unstaffed Locations EB RosettaNet

  43. DUNS® + 4 Numbering • Extension to DUNS® Numbering • Controlled by Individual Organization • Used to Identify Specific Locations or Departments within an Organization EB RosettaNet

  44. DUNS® Number Example 00-825-575 4 ------------- - | | | ----> Check Digit | ---------------> Company Identification EB RosettaNet

  45. 00-825-575 4 1234 ---------- - ---- | | | | | | | | ---> Extension * | | | ------> Check Digit | -------------> Company ID * Extension is Company Assigned DUNS® + 4 Number Example EB RosettaNet

  46. DUNS® Number Advantages • Universal Partner Identifier • Pass Unchanged Through Supply Chain • Supports “Meta-Customer” Identification • POS / Resale Reporting • Contracts and Pricing EB RosettaNet

  47. Product Specification • GTIN • Global Trade Item Number • Managed by: • EAN International(www.ean.be) • Uniform Code Council (UCC)(www.uc-council.com) EB RosettaNet

  48. Product Specification • GTIN • Fourteen Digit Number • No Embedded Intelligence • Guaranteed Unique Product Identifier • Used in Many RosettaNet PIPsTM EB RosettaNet

  49. 2 QSP 16 T J 1 222- --- -- - - - ---| | | | | | | | | | | | | ---> Resistance Value - 2200 ohms| | | | | -----> Circuit Designator – Independent Circuit| | | | --------> TR Tolerance  5% and | | | | TCR  100 PPM / C| | | ----------> Packaging Type - Tube| | ------------> Number of Terminals - 16| ----------------> Package Style - QSOP -------------------> Product Class – Thin-Film on Silicon Manufacturer’s Part EB RosettaNet

  50. Global Trade Item Number 0 0678088 20464 3- ------- ----- -| | | || | | -----> Check Digit| | --------> Sequential Identifier| ---------------> Company Identifier ---------------------> Always ‘0’ in RosettaNet(Other industries use for “packaging code”) GTIN EB RosettaNet

More Related