electronic business based on rosettanet case study of supply chain management l.
Download
Skip this Video
Loading SlideShow in 5 Seconds..
Electronic Business Based on RosettaNet – Case Study of Supply Chain Management PowerPoint Presentation
Download Presentation
Electronic Business Based on RosettaNet – Case Study of Supply Chain Management

Loading in 2 Seconds...

play fullscreen
1 / 75

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


  • 549 Views
  • Uploaded on

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.

loader
I am the owner, or an agent authorized to act on behalf of the owner, of the copyrighted work described.
capcha
Download Presentation

PowerPoint Slideshow about 'Electronic Business Based on RosettaNet – Case Study of Supply Chain Management' - MartaAdara


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.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript
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
Contents
  • Evolution of Web Technology
  • RosettaNet
  • E-Supply Chain Management Based on RosettaNet at Tatung Company

EB RosettaNet

slide4
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

interactions using xml
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

what is xml
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

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

EB RosettaNet

xml protocol soap
XML Protocol: SOAP

EB RosettaNet

ap 2 ap business interactions

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

view of private and public processes
View of Private and Public Processes

BSI: Business Service Interface

EB RosettaNet

ebxml a generic eb framework soa for eb
ebXML: A Generic EB FrameworkSOA for EB
  • A generic EB framework for cross-industry horizontal integration

EB RosettaNet

phases in the use of the ebxml framework
Phases in the Use of the ebXML Framework

The implementation phase

EB RosettaNet

phases in the use of the ebxml framework14
Phases in the Use of the ebXML Framework

The discovery phase

EB RosettaNet

phases in the use of the ebxml framework15
Phases in the Use of the ebXML Framework

The runtime phase

EB RosettaNet

components of the ebxml framework
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

background
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

technical concept of rosettanet

Trading Partner

Trading Partner

Create content

Wrap it

Send it

Receive it

Unwrap it

Process content

Technical Concept of RosettaNet

EB RosettaNet

technical components
Technical Components
  • Partner Interface Processes (PIPsTM)
  • Dictionaries and Codes
  • RosettaNet Implementation Framework (RNIF) Core

EB RosettaNet

technical components pip
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

technical components pip22

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

technical components pip23
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

pip classification clusters
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

technical components pip27
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

from pip tm 3a4 business process activity controls in bov

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

from pip tm 3a4 business transaction dialog in fsv

: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

from pip tm 3a4 ifv

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

from pip tm 3a4 xml dtd
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

from pip tm 3a4 message guidelines cardinality
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

from pip tm 3a4 message guidelines business properties
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

pip summary

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

technical components dictionaries
Technical Components - Dictionaries

Why Use Dictionaries and Codes?

Simply…

  • To ensure the consistency of information exchanged between trading partners when executing PIPsTM.

EB RosettaNet

technical components dictionaries37
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

codes and dictionaries
Codes and Dictionaries
  • Partner Identification (DUNS®)
  • Product Identification
    • Product Number (GTIN)
    • Product Classification (UN/SPSC)
    • Product Descriptions (Dictionaries)

EB RosettaNet

where are they used
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

partner identification
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

duns numbering
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

duns numbering42
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

duns 4 numbering
DUNS® + 4 Numbering
  • Extension to DUNS® Numbering
  • Controlled by Individual Organization
  • Used to Identify Specific Locations or Departments within an Organization

EB RosettaNet

duns number example
DUNS® Number Example

00-825-575 4

------------- -

| |

| ----> Check Digit

|

---------------> Company Identification

EB RosettaNet

duns 4 number example
00-825-575 4 1234

---------- - ----

| | |

| | |

| | ---> Extension *

| |

| ------> Check Digit

|

-------------> Company ID

* Extension is Company Assigned

DUNS® + 4 Number Example

EB RosettaNet

duns number advantages
DUNS® Number Advantages
  • Universal Partner Identifier
  • Pass Unchanged Through Supply Chain
  • Supports “Meta-Customer” Identification
    • POS / Resale Reporting
    • Contracts and Pricing

EB RosettaNet

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

EB RosettaNet

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

EB RosettaNet

manufacturer s part
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 SiliconManufacturer’s Part

EB RosettaNet

slide50
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

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

EB RosettaNet

product specification52
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

EB RosettaNet

unspsc
UNSPSC

32 12 16 06 XX

-- -- -- -- --

| | | | |

| | | | ----> Service Type (see below)

| | | -------> Fixed thin film resistors

| | ----------> Resistors

| -------------> Printed components

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

EB RosettaNet

technical dictionaries
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.

EB RosettaNet

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

EB RosettaNet

technical dictionary example
Technical Dictionary Example

Product Class: RESISTOR–FIXED – NETWORKS

Class Characteristics:

  • Rated Dissipation: 0.100 Watt @ 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 @ 70C
  • Terminal Shape: gull-wing
  • Resistive Material: Metal Film (Thin-Film)

EB RosettaNet

technical dictionary advantages
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)

EB RosettaNet

technical components rnif
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.)

EB RosettaNet

technical components rnif59

Trading Partner

Trading Partner

Create content

Wrap it

Send it

Receive it

Unwrap it

Process content

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.

EB RosettaNet

technical components rnif60

RNIF 1.1

RNIF 2.0

PIP3A4

PIPTM1B1

Attach-

ments

RosettaNet Business Document

Service Content

Preamble Header

Service Header

Service Header

+

+

+

+

MIME Packaging

S/MIME Envelope

Encrypted Payload Container

RNIF Version ID

Service Message

Digital Signature

Preamble Header

Delivery Header

Digital Signature

+

+

+

+

+

PIP2A1

PIP3A2

MIME Packaging

RosettaNet Object (RNO)

RosettaNet Business Message

Technical Components - RNIF

EB RosettaNet

rosettanet vs ebxml
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

EB RosettaNet

tatung company profile
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.

EB RosettaNet

slide64

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

EB RosettaNet

slide65

SCM Business Process

Customer

Tatung

Supplier

Forecast

Forecast

供應商對模擬快速反應

Customer

(HQ)

模擬生產計畫

ATP

Promise Date

正式生產計畫

PO

製造/Hub

Customer

(Branch)

交貨

驗收、工單、組裝

PO

入庫、交貨

By Sea/Air

Customer

(Channel/Hub)

EB RosettaNet

rosettanet inter connections with customers and suppliers

PIPs 3A4 3A7

PIPs 3A4 3A7, 3A8

C Firm

H Firm

N Firm

I Firm

Internet

Internet

PIPs 3A4

3A7, 3A8

PIPs 4A4, 4A5

RosettaNet

A Firm

W Firm

PIPs 3A4, 3A7, 3A8

RosettaNet Inter-Connections with Customers and Suppliers

Customer

Supplier

EB RosettaNet

slide69

Tatung Side

Supplier Side

Tatung Side

3A4 PO Request

Part Number Mapping

可達交量(ATP) =庫存+PO vendor Confirm量 –該零件之所有booking量(PO,FCST, WO)

Middleware

Middleware

ATP

approval

e-mail to sales

P/O

Demand and Supply Planning

ERP

ERP

MRP

計算庫存、WO領料、PO、SO,以排出生產計畫,產生ATP, 回覆客戶

ERP

Middleware

Day 1

Day 2

7:00am(Batchprocessing, sending out 3A7, e-mailnotifying sales, )

Tatung SCM RosettaNet PO

EB RosettaNet

slide71

User

User

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

EB RosettaNet

slide73

E

A/R

Customers

Suppliers

D

Out-bound

C

In-bound

Banks

A/P

A/P

E

LSP

Plans C, D and E

A

B

plans a b c and d

BWG

PIP3A4

BWG

PIP3B2

PIP3C3

IFX

IFX

BWG

Plans A, B, C and D

ATP

EB RosettaNet