Electronic Business Based on RosettaNet Case Study of Supply Chain Management - PowerPoint PPT Presentation

1 / 75
About This Presentation
Title:

Electronic Business Based on RosettaNet Case Study of Supply Chain Management

Description:

Electronic Business Based on RosettaNet. Case Study of Supply ... CSS, XSL-T, XSL-FO. XLink. XPointer. EB RosettaNet. 8. XML Protocol: SOAP. EB RosettaNet ... – PowerPoint PPT presentation

Number of Views:465
Avg rating:3.0/5.0
Slides: 76
Provided by: cseTt
Category:

less

Transcript and Presenter's Notes

Title: Electronic Business Based on RosettaNet Case Study of Supply Chain Management


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_at_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

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

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

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

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

8
XML Protocol SOAP
9
Web Service Architecture
10
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
11
View of Private and Public Processes
BSI Business Service Interface
12
ebXML A Generic EB FrameworkSOA for EB
  • A generic EB framework for cross-industry
    horizontal integration

13
Phases in the Use of the ebXML Framework
The implementation phase
14
Phases in the Use of the ebXML Framework
The discovery phase
15
Phases in the Use of the ebXML Framework
The runtime phase
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 ebXMLs
    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.

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

19
Technical Concept of RosettaNet
20
Technical Components
  • Partner Interface Processes (PIPsTM)
  • Dictionaries and Codes
  • RosettaNet Implementation Framework (RNIF) Core

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

22
Technical Components - PIP
Categorized by high-level business function
(cluster) and sub-function (segment)
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

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

25
PIP 2A2 Query Product Information Business
Process Model
26
PIP 3A4 Request Purchase Order Business Process
Model
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

28
From PIPTM3A4 Business Process Flow Diagram in BOV
29
From PIPTM3A4 Business Process Activity Controls
in BOV
30
From PIPTM3A4 Business Transaction Dialog in FSV
Purchase Order Request Dialog
31
From PIPTM3A4 IFV
Purchase Order Request Dialog
32
From PIPTM3A4 XML DTD
  • lt!ENTITY common-attributes "id CDATA IMPLIED"
    gt
  • lt!ELEMENT Pip3A4PurchaseOrderAcceptance (
  • PurchaseOrder ,
  • fromRole ,
  • toRole ,
  • thisDocumentGenerationDateTime ,
  • thisDocumentIdentifier ,
  • requestingDocumentIdentifier ,
  • GlobalDocumentFunctionCode ,
  • requestingDocumentDateTime ) gt
  • lt!ELEMENT PurchaseOrder (
  • deliverTo? ,
  • comment? ,
  • GlobalPurchaseOrderStatusCode ,

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
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 DUNS4 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.
35
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.
36
Technical Components - Dictionaries
  • Why Use Dictionaries and Codes?
  • Simply
  • To ensure the consistency of information
    exchanged between trading partners when executing
    PIPsTM.

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
38
Codes and Dictionaries
  • Partner Identification (DUNS)
  • Product Identification
  • Product Number (GTIN)
  • Product Classification (UN/SPSC)
  • Product Descriptions (Dictionaries)

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

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

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

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

43
DUNS 4 Numbering
  • Extension to DUNS Numbering
  • Controlled by Individual Organization
  • Used to Identify Specific Locations or
    Departments within an Organization

44
DUNS Number Example
  • 00-825-575 4
  • ------------- -
  • ----gt Check Digit
  • ---------------gt Company Identification

45
DUNS 4 Number Example
  • 00-825-575 4 1234
  • ---------- - ----
  • ---gt Extension
  • ------gt Check Digit
  • -------------gt Company ID
  • Extension is Company Assigned

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

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

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

49
Manufacturers Part
  • 2 QSP 16 T J 1 222- --- -- - - - ---
    ---gt Resistance Value
    - 2200 ohms -----gt Circuit
    Designator Independent Circuit
    --------gt TR Tolerance ? 5 and
    TCR ? 100 PPM / ?C
    ----------gt Packaging Type - Tube
    ------------gt Number of Terminals - 16
    ----------------gt Package Style - QSOP
    -------------------gt Product Class Thin-Film on
    Silicon

50
GTIN
  • Global Trade Item Number
  • 0 0678088 20464 3- ------- ----- -
    -----gt Check Digit
    --------gt Sequential Identifier
    ---------------gt Company Identifier
    ---------------------gt Always 0 in RosettaNet
    (Other industries use for
    packaging code)

51
GTIN Advantages
  • Single Product Identifier Throughout Supply Chain
  • Catalog Owner Responsible for GTIN
  • Eliminates Unnecessary Cross-References
  • Future Impacts in Customer Labeling

52
Product Specification
  • UN/SPSC
  • Hierarchical product classification scheme
    individual commodities represent unique instances
    of larger classes and families
  • 2-digit identification sequence per level
  • Levels Segment, family, class, commodity
  • www.un-spsc.net

53
UNSPSC
  • 32 12 16 06 XX
  • -- -- -- -- --
  • ----gt Service Type (see below)
  • -------gt Fixed thin film resistors
  • ----------gt Resistors
  • -------------gt Printed components
  • ----------------gt Electronic Components and
    Supplies
  • Service Type
  • 10 - Rental or Lease
  • 11 - Maintenance or Repair
  • 12 Manufacturer
  • 13 Wholesale
  • 14 Retail
  • 15 Recycle
  • 16 Installation
  • 17 - Service Parts

54
Technical Dictionaries
  • RosettaNet Technical Dictionary (Information
    Technology (IT) Electronic Components (EC))
  • Organizes product descriptions into reusable
    atomic properties and relationships
  • Used to search electronic catalogs, maintain
    technical information databases, generate
    technical spec sheets, etc.

55
Product Specification
  • Technical Dictionary
  • Parametric Database of Product Characteristics
  • Describes Product Form, Fit and Function
  • Electronically Searchable
  • Product Configuration / Design PIPsTM

56
Technical Dictionary Example
  • Product Class RESISTORFIXED NETWORKS
  • Class Characteristics
  • Rated Dissipation 0.100 Watt _at_ 70? C
  • Resistance 2200 Ohms
  • Resistance Tolerance ? 5
  • Rated Voltage 14.83V
  • Limiting Element Voltage 50V Max
  • Category Temperature Range -55? C to
    125?C
  • Temperature Coefficient ? 100 PPM / ?C
  • Resistor Interconnection Independent
    Circuit
  • Terminal Placement QSOP
  • Number of Resistance Elements 8
  • Number of Terminals 16
  • Rated Dissipation for the Network 0.75 watts _at_
    70?C
  • Terminal Shape gull-wing
  • Resistive Material Metal Film (Thin-Film)

57
Technical Dictionary Advantages
  • Electronically Searchable Catalog
  • Supports More Detail than Part Number
  • Can be Integrated with Product Data Management
    (PDM) and Computer Aided Design (CAD)

58
Technical Components - RNIF
  • RosettaNet Implementation Framework Core
  • RNIF (usually pronounced R-NIF)
  • RNIF 1.1 Defines RosettaNet Object (RNO),RNIF
    2.0 Defines RosettaNet Business Message
  • Specifies how to transport RosettaNet Objects and
    Business Messages between trading partners
    network applications
  • (Remember those PIPsTM? This is how the Business
    Document Payload is packaged and transported.)

59
Technical Components - RNIF
  • It is conceptually very simple.

The RNIF specifies an XML- and MIME-based
envelope in which to put the business document
payload.
60
Technical Components - RNIF
61
RosettaNet vs. ebXML
  • ebXML is a meta-Model of EB Architecture
  • RN can be seen as an instance of ebXML
  • Business Processes
  • PIPs in process models
  • PIPs are the basic dialogues for creating
    business collaborations.
  • Representation using business process language in
    ebXML, BPSS
  • Vocabulary
  • Both technical and business dictionaries RNTD,
    RNBD
  • Convert to Core Components
  • No partner profile, but having implicit agreement
  • Using CPP and CPA
  • Message service RNIF
  • ebXML message services
  • No registry
  • ebXML registry and repository

62
E-Supply Chain Management Based on RosettaNet at
Tatung Company
63
Tatung Company Profile
  • Founded in 1918, Tatung Company is a worldwide
    leader in the design and manufacturing of a vast
    array of digital consumer products, including LCD
    TVs and PDPs, network-connected devices,
    storage-based media players and home appliances.
    Tatung also delivers advanced products for
    business computing, such as Tablet PCs, WebPAD,
    and blade servers. For industrial products,
    Tatung has been well established in the power and
    energy businesses.
  • By capitalizing on the advantages of vertical
    integration, Tatung makes full use of the supply
    of key components such as flat-panel displays and
    digital tuners from its many subsidiaries located
    across the globe. In order to sustain strong,
    long-term growth, Tatung focuses particularly on
    the development of advanced technologies and
    global network of operations. With its overseas
    branches expanding into 12 countries, Tatung is
    in a solid position to deliver products more
    efficiently and render customer services more
    effectively. Monitoring its global operations
    from the Taipei headquarters, Tatung offers
    customers tremendous advantages of cost, speed,
    and seamless backend support in order to stay
    ahead in today's dynamic business world. Tatung
    specializes in the ODM/OEM business and serves
    branded customers on a global basis.

64
Tatung Worldwide
HQ M/B and Chassis Design System Assembly,
BTO/CTO Monitor/LCD Monitor
Holland Configuration LSP,RMA BTO/CTO
Canada Configuration, LSP RMA,BTO/CTO
TSTI System Configuration
Japan LSP, RMA
?
?
UK Monitor
TUA Configuration, LSP RMA,BTO/CTO
Tatung Logistics LSP
?
Thailand Monitor Manufacturing
Mexico System Configuration, LSP, RMA
Jiang-Su China PC Configuration, Monitor
Manufacturing LSP, RMA
65
SCM Business Process
Customer
Tatung
Supplier
??????????
Forecast
Forecast
Customer (HQ)
??????
ATP
Promise Date
??????
PO
??/Hub
Customer (Branch)
??
????????
PO
?????
By Sea/Air
Customer (Channel/Hub)
66
RosettaNet Inter-Connections with Customers and
Suppliers
Customer
Supplier
67
RosettaNet PO Collaboration
68
RosettaNet PIP 3A4, 3A7, 3A8 Scenario
69
Tatung SCM RosettaNet PO
70
Business Flow (Before B2B)
71
Business Flow (After B2B)
?
?
Server to Server
Server to Server
?
Message Process Automatic
?
Message Process Automatic
?
?
Integrate into legacy system
Integrate into legacy system
?
?
Support Error handling mechanism
Support Error handling mechanism
CPT
ERP
ERP
TAMIS
AS400
Public Process
Private Process
Private Process
Order
Order
RosettaNet
RosettaNet
Process
Process
Gateway
Gateway
BizTalk
BizTalk
72
Enables Departmental Application Integration
73
Plans C, D and E
A
B
74
Plans A, B, C and D
ATP
75
Thank You
Write a Comment
User Comments (0)
About PowerShow.com