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
• Evolution of Web Technology
• RosettaNet
• E-Supply Chain Management Based on RosettaNet at
Tatung Company
EB RosettaNet
2
Evolution of Web Technology
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)
•
•
EB RosettaNet
Human-to-machine interaction
Information explosion
4
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)
EB RosettaNet
•
Machine-to-machine
interaction
Service automation
5
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
6
XML Technology
•
•
•
•
•
•
•
DTD
Namespace
Schema
DOM
CSS, XSL-T, XSL-FO
XLink
XPointer
EB RosettaNet
7
XML Protocol: SOAP
EB RosettaNet
8
Web Service Architecture
Service
descriptions
Service
registry
Find
Publish
WSDL, UDDI
Service
requester
WSDL, UDDI
Bind
Service
provider Services
Service
descriptions
EB RosettaNet
9
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
Business processes,
business documents
Business processes,
business documents
Secure and reliable
message services
Secure and reliable
message services
EB RosettaNet
10
View of Private and Public Processes
Business Transaction
Partner B
C
P
A
B
S
I
B
S
I
Private
Process
Public Process
(Business Collaboration)
Backend Processing
Backend Processing
Partner A
Private
Process
BSI: Business Service Interface
EB RosettaNet
11
ebXML: A Generic EB Framework
SOA for EB
• A generic EB framework for cross-industry horizontal
integration
Registry Host
Supplier
1
Profiles
ProcessSpecifications
5
ebXML
Registry
4
3
6
Implementation
2
Customer
EB RosettaNet
Intermediaries
12
Phases in the Use of the ebXML Framework
Registry Host
Supplier
1
Profiles
ProcessSpecifications
ebXML
Registry
3
Implementation
2
Customer
Intermediaries
The implementation phase
EB RosettaNet
13
Phases in the Use of the ebXML Framework
Registry Host
Supplier
1
Profiles
ProcessSpecifications
5
Implementation
ebXML
Registry
4
Customer
Intermediaries
The discovery phase
EB RosettaNet
14
Phases in the Use of the ebXML Framework
Registry Host
Supplier
Profiles
ProcessSpecifications
Implementation
ebXML
Registry
6
Customer
The runtime phase
Intermediaries
EB RosettaNet
15
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
16
RosettaNet
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
18
Technical Concept of RosettaNet
Trading Partner
Trading Partner
Create content
Receive it
Wrap it
Unwrap it
Send it
Process content
Business Transaction
Private
Process
Partner B
C
P
A
B
S
I
B
S
I
Public Process
(Business Collaboration)
EB RosettaNet
Backend Processing
Backend Processing
Partner A
Private
Process
19
Technical Components
• Partner Interface Processes (PIPsTM)
• Dictionaries and Codes
• RosettaNet Implementation
Framework (RNIF) Core
EB RosettaNet
20
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
21
Technical Components - PIP™
Categorized by high-level business function (cluster) and
sub-function (segment)
Cluster 3: Order Management
Segment A : Quote and Order Entry
PIP 3A1 - Provide Quote
PIP 3A2 - Query Price and Availability
PIP 3A3 - Transfer Shopping Cart
PIP 3A4 - Manage Purchase Order
PIP 3A5 - Query Order Status
PIP 3A6 - Distribute Order Status
Segment B : Transportation and Distribution
Segment C : Returns and Finance
EB RosettaNet
22
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
23
PIP Classification
Clusters
•
•
•
•
•
•
•
•
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
24
PIP 2A2 Query Product Information
Business Process Model
EB RosettaNet
25
PIP 3A4 Request Purchase Order
Business Process Model
EB RosettaNet
26
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
27
From PIPTM3A4 Business Process Flow
Diagram in BOV
EB RosettaNet
28
From PIPTM3A4 Business Process Activity
Controls in BOV
Table 3-3: Business Activity Performance Controls
Time to Acknowledge
Acceptance
Time to Perform
Retry Count
Is Authorization
Required?
Non-Repudiation of
Origin and Content?
Y
2hr
24hr
24hr
3
Y
Y
Cancel
Purchase
Order
Y
2hr
24hr
24hr
3
Y
Y
Revise
Purchase
Order
Y
2hr
24hr
24hr
3
Y
Y
Time to
Acknowledge
Buyer
Create
Purchase
Order
NonRepudiation
Required?
Buyer
Activity Name
Role Name
Buyer
Acknowledgment
of Receipt
EB RosettaNet
29
From PIPTM3A4 Business Transaction
Dialog in FSV
Purchase Order Request Dialog
:Buyer
:Seller
1. request(:PurchaseOrderRequestAction)
1.1. signal(:ReceiptAcknowledgement)
2. response(:PurchaseOrderAcceptanceAction)
2.1. signal(:ReceiptAcknowledgement)
EB RosettaNet
30
From PIPTM3A4 IFV
Purchase Order Request Dialog
Table 5-1: Business Message and Communications
Specification
1.
Purchase Order Request Guideline
1.1
Receipt Acknowledgement Guideline
2.
2.1
SSL
Required?
Business Message Guideline
Digital
Signature
Required?
#
Y
Y
Y
Y
Purchase Order Acceptance Guideline
Y
Y
Receipt Acknowledgement Guideline
Y
Y
EB RosettaNet
31
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
32
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 |
|
TM
|-- shipFrom.GlobalLocationIdentifier
EB RosettaNet
33
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
34
PIP™ Summary
A PIP specifies the structure and
format of the business document
payload for a particular business
• It is conceptually very simple.
activity.
Trading Partner
The business content is an XML
Trading
Partner
document.
Create content
Receive it
Wrap it
It also specifies the exchange
Unwrap
it
protocol between
trading
partners for that activity.
Send it
Process content
EB RosettaNet
35
Technical Components - Dictionaries
Why Use Dictionaries and Codes?
Simply…
• To ensure the consistency of information exchanged
between trading partners when executing PIPsTM.
EB RosettaNet
36
Technical Components - Dictionaries
• It is conceptually very simple…
Dictionary
Trading Partner
Trading Partner
Create content
Receive it
Wrap it
Unwrap it
Send it
Process content
Dictionary
EB RosettaNet
37
Codes and Dictionaries
• Partner Identification (DUNS®)
• Product Identification
– Product Number (GTIN)
– Product Classification (UN/SPSC)
– Product Descriptions (Dictionaries)
EB RosettaNet
38
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
39
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
40
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
41
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
42
DUNS® + 4 Numbering
• Extension to DUNS® Numbering
• Controlled by Individual Organization
• Used to Identify Specific Locations or Departments within
an Organization
EB RosettaNet
43
DUNS® Number Example
00-825-575 4
------------- |
|
|
----> Check Digit
|
---------------> Company Identification
EB RosettaNet
44
DUNS® + 4 Number Example
00-825-575 4 1234
---------- - ---|
| |
|
| |
|
|
---> Extension *
|
|
|
------> Check Digit
|
-------------> Company ID
EB RosettaNet
* Extension is Company Assigned
45
DUNS® Number Advantages
• Universal Partner Identifier
• Pass Unchanged Through Supply Chain
• Supports “Meta-Customer” Identification
– POS / Resale Reporting
– Contracts and Pricing
EB RosettaNet
46
Product Specification
• GTIN
– Global Trade Item Number
– Managed by:
• EAN International
(www.ean.be)
• Uniform Code Council (UCC)
(www.uc-council.com)
EB RosettaNet
47
Product Specification
• GTIN
–
–
–
–
Fourteen Digit Number
No Embedded Intelligence
Guaranteed Unique Product Identifier
Used in Many RosettaNet PIPsTM
EB RosettaNet
48
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 Silicon
EB RosettaNet
49
GTIN
• Global Trade Item Number
0 0678088 20464 3
- ------- ----- |
|
| |
|
|
|
----->
|
|
-------->
|
--------------->
--------------------->
Check Digit
Sequential Identifier
Company Identifier
Always ‘0’ in RosettaNet
(Other industries use for
“packaging code”)
EB RosettaNet
50
GTIN Advantages
•
•
•
•
Single Product Identifier Throughout Supply Chain
Catalog “Owner” Responsible for GTIN
Eliminates Unnecessary Cross-References
Future Impacts in Customer Labeling
EB RosettaNet
51
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
52
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
53
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
54
Product Specification
• Technical Dictionary
– Parametric Database of Product Characteristics
– Describes Product Form, Fit and Function
– Electronically Searchable
• Product Configuration / Design PIPsTM
EB RosettaNet
55
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
56
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
57
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
58
Technical Components - RNIF
• It is conceptually very simple.
Trading Partner
Trading Partner
Create content
Receive it
Wrap it
The RNIF specifies an
XML- and MIME-based
“envelope”
in whichitto put
Unwrap
the business document
payload.
Send it
Process content
EB RosettaNet
59
Technical Components - RNIF
RNIF 1.1
Preamble
Service
+
Header
Header +
PIPTM1
PIP2A1B1
PIP3A2
PIP3A4
RosettaNet
Business
Document
RNIF 2.0
Service
Header +
MIME Packaging
RNIF
Service
Digital
+
+
Version ID
Message
Signature
Service
Content
+
Attachments
S/MIME Envelope
Preamble
Delivery
+
Header
Header +
Encrypted
Digital
Payload
+ Signature
Container
MIME Packaging
RosettaNet Object
(RNO)
RosettaNet Business
Message
EB RosettaNet
60
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
61
E-Supply Chain Management Based on
RosettaNet at Tatung Company
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
63
Tatung Worldwide
Canada
Holland
Configuration, LSP
RMA,BTO/CTO
Configuration
LSP,RMA
BTO/CTO
HQ
M/B and Chassis Design
System Assembly,
BTO/CTO
Monitor/LCD Monitor
TSTI
System
Configuration

TUA
Configuration, LSP
RMA,BTO/CTO

UK
Tatung Logistics
Japan
LSP, RMA
Monitor

LSP
Thailand
Mexico
System Configuration,
LSP, RMA
Jiang-Su China
Monitor
Manufacturing
PC Configuration,
Monitor Manufacturing
LSP, RMA
EB RosettaNet
64
SCM Business Process
Customer
Customer
(HQ)
Tatung
Forecast
模擬生產計畫
ATP
Supplier
Forecast
Promise Date
正式生產計畫
供應商對
模擬快速
反應
PO
製造/Hub
Customer
(Branch)
驗收、工單、組裝
交貨
PO
入庫、交貨
Customer
(Channel/Hub)
By Sea/Air
EB RosettaNet
65
RosettaNet Inter-Connections with Customers and
Suppliers
Customer
Supplier
PIPs 3A4 3A7
PIPs 3A4 3A7, 3A8
H Firm
Intern
et
Intern
et
PIPs 4A4, 4A5
C Firm
PIPs 3A4
3A7, 3A8
N Firm
RosettaNet
PIPs 3A4, 3A7, 3A8
A Firm
I Firm
W Firm
EB RosettaNet
66
RosettaNet PO Collaboration
Buyer
Private process
(Company -specific)
Process
PO
Receive PO
Request
Figure provided by Vitria Systems
PO
PO Request
Public process
(Standard)
Send PO
Customer
Public process
(Standard)
Send PO
Supplier
Send PO
Receive PO
Select
Supplier
Generate
RFQ
Send
RFQ
Private process
(Company -specific)
Process
Sales Order
Receive PO
Check
Customer
Receive PO
Acknowledge
Send PO
Acknowledge
Receive PO
Response
Send PO
Response
Select RFQ
Response
Send
PO
Seller
CRM
Check
Credit
Check
Availability
SCM
Create Sales
Order
Send PO
Response
Acknowledge
Receive PO
Response
Acknowledge
Close
Send PO
Response
Close
EB RosettaNet
ERP
67
RosettaNet PIP 3A4, 3A7, 3A8 Scenario
Entity
Tatung
Scenario
PO
3A4 PO Request
Accept
3A4 Pending
3A7 Accept
Supplier
24 Hrs
24 Hrs
Remarks
This basic scenario is theoretically supposed to
finish in 48 hours after order issued.
In fact, supplier will send auto pending in few
minutes, and order response in hours.
item
PO
status
Line
status
3A4
Accept Accept
Accept Accept
Reason
Pending
code
Accept
3A4 PO Request
with
3A4 Pending
Change
Accept
Accept
with
Change
PO
Change
3A7 Accept
3A7 Accept
3A4 PO Request
24
24 Hrs
Hrs
24 Hrs
24 Hrs
24 Hrs
3A4 Pending
3A7 Accept
24 Hrs
3A8 PO Change
24 Hrs
3A8 Pending
24 Hrs
3A7 Accept with Change
24 Hrs
This is supposed to finish in 72 hours after order PO
issued.
status
If supplier could not completely fulfill your
request, you would have negotiation by phone Line
and ask him to do. If you have agreement on the status
original PO request, supplier would send you
Reason
3A7 (PO Accept) again for confirmation. Then
code
this is finished.
This is to finish in 120 hours after order issued. PO
If supplier could not completely fulfill your
status
request, you would have negotiation by phone.
Line
If supplier could not meet your requirement
indeed, and no second source for this, you will status
send PO change. Supplier will send you 3A8
pending immediately and have 3A7 (PO
Reason
Accept) again for change confirmation. Then it code
is ended.
EB RosettaNet
3A7
-
Accept Accept
Accept Reject
Pending Pending
Accept Accept
Accept Accept
Accept
Pending with
Change
68
Tatung SCM RosettaNet PO
Tatung Side
Supplier Side
Tatung Side
3A4 PO Request
Middleware
Middleware
ATP
e-mail to sales
Middleware
approval
P/O
ERP
MRP
ERP
Demand and
Supply Planning
Part Number Mapping
可達交量(ATP) =庫存+PO vendor Confirm
量 –該零件之所有booking量(PO,FCST, WO)
Day 1
ERP
計算庫存、WO領料、
PO、SO，以排出生產計
畫,產生ATP, 回覆客戶
Day 2
7:00am (Batch processing, sending out 3A7,
e-mail notifying sales, )
EB RosettaNet
69
Business Flow (Before B2B)
EB RosettaNet
70
Business Flow (After B2B)
Server to Server
Message & Process Automatic
Integrate into legacy system
Support Error handling mechanism
CPT
ERP
TAMIS
ERP
AS400
Public Process
Private Process
Order
Process
RosettaNet
Gateway
BizTalk
Private Process
Order
Process
RosettaNet
Gateway
BizTalk
User
User
EB RosettaNet
71
Enables Departmental Application Integration
Taiwan
e-Logistics
ASP
Web Service
LSP
Customer
Supplier
Bank
Web Service
Internet
Web Service
International
e-Logistics
ASP
Information
Interactions
Transactions
TATUNG
Gateway
HUB
Authentication
Transaction Routing
Registration
Enrollment
TATUNG
Intranet
Departmental Systems
EB RosettaNet
72
Plans C, D and E
Customers
E
A/R
A
Out-bound
D
Tatung
In-bound
PDM
ERP
C
SFIS
Banks
A/P
A/P
LSP
E
Suppliers
B
Plans A, B, C and D
A,B-Plan
Customer
C-Plan
OEM
Supplier
Bank
BWG
PIP3A4
Forecast
D-Plan
HUB
LSP
ASP
MPS
BWG
MRP
貸款
PO
Inventory Demand
Simulation
ATP
MPS
MRP
VMI
E-Loan
PIP3B2
Shippment
債權移轉
PIP3C3
Direct ASN
Shippment
3PL
A/P
Payment
IFX
Payment
A/R
IFX
徵信
E-Payment
A/R
TQRAC
EB
RosettaNet
BWG
74
Thank You