rosettanet b2b architecture rosettanet pip why standardize ... · inter-enterprise content and...

B2B StandardsDerek Coleman, Chief Technologist RosettaNetOn loan from Hewlett-Packard

2 Standards Convergence © COPYRIGHT 2001 ROSETTANET. ALL RIGHTS RESERVED.

AgendaAgenda

• RosettaNet

• Why Standardize XML?

• RosettaNet PIPTMs

• RosettaNet B2B Architecture

RosettaNet


About RosettaNetAbout RosettaNet

• Vision: The Leader inglobal e-business standards

• Mission: RosettaNet drivescollaborative developmentand rapid deployment ofinternet-based businessstandards, creating acommon language andopen e-business processesthat provide measurablebenefits and are vital to theevolution of the global,high-technology tradingnetwork.

RosettaNet Governing Process

RosettaNetPartners

• Vote onstandards

• Participate inworkshops

• Implement

IndividualSupply Chain

Boards

• Address SMsupply chain-specific issues• Prioritization• Resources• Implementationand adoption

RosettaNetExecutive Board

• Provide overallguidance• Addressprioritization andintegration acrossboards

X 3


Information Technology (IT)Supply Chain BoardInformation Technology (IT)Supply Chain Board

3Com

Arrow Electronics

Avnet

Cisco Systems

Compaq

CompUSA

Dell

Federal Express

GSA

Hewlett-PackardIBMIngramInsightIntelLucent

TechnologiesNECNetscapeOffice Depot

Pioneer

Quantum

SAP

Siemens

Solectron

Tech Data

Trilogy

UPS


Electronic Components (EC)Supply Chain BoardElectronic Components (EC)Supply Chain Board

Pioneer

Samsung

Solectron

Sony

STMicroelectronics

Texas Instruments

Toshiba

Tyco Electronics

Xilinx

Intel

Kemet

LucentTechnologies

Memec

Micron Technology

Molex

Motorola

National

Nokia

NEC

PhilipsSemiconductors

Agilent

Altera

Arrow Electronics

Avnet

AVX

Bourns

Cisco Systems

FCI

Future Electronics

Hitachi

IBM


Semiconductor Manufacturing (SM)Supply Chain BoardSemiconductor Manufacturing (SM)Supply Chain Board

Air Products &Chemicals

Agilent Technologies

Amkor Technology

Applied Materials

ASE

CharteredSemiconductor

Intel

JSR

LSI

Lucent Technologies

Micron Technology

Motorola

NationalSemiconductor

NEC

PhilipsSemiconductors

Samsung Electronics

Shin-Etsu Handoutai

Shinko Electronics

SPIL

Sumitomo Bakelite

Sumitomo Metal

Texas Instruments

TOK

Tokyo Electron

Toppan

Toshiba

TSMC

UMC

Winbond

Xilinx


What RosettaNet standardizesWhat RosettaNet standardizes

• RosettaNet does not define how trading partnersdo business together

• RosettaNet does, however, define how tradingpartners exchange information

• RosettaNet does not build or sell software butinstead works with industry thought leaders todevelop business process specifications


Industry RecognitionIndustry Recognition

In a special year-end issueof tomorrow’s LEADERS,RosettaNet is named aTOP 10 WINNEROF 2000 byInternetWeek.12.18.00 “RosettaNet's e-business

communications standardsare GIANT STEPS on

the journey towardSOLVING some

of these problems.”CRN

3.19.01

RosettaNet is “one of the MOST AMBITIOUS inter-enterprise content and process integration efforts currently underway.”Patricia Seybold Group 4.3.01

“RosettaNet is arguablythe MOTHER OF ALL

industry-specific XML EFFORTS.”eWEEK

2.26.01

Why Standardize XML


Why XML?Why XML?

• Simple to represent richly structured data in anunambiguous, extensible, non-proprietary way

• Readily available, easy-to-integrate parsing andvalidation technology

• Ideally suited for data exchange over the Internetusing well-established transfer protocols


Why Standardize?Why Standardize?

• Competitive pressure to achieve extremeoperational efficiency

• Competitive pressure to create additionalbusiness value

• Makes integration efforts efficient and repeatable

• Promotes loose coupling of trading partners,allowing for rapid reconfiguration of supply webs

• Leverages expertise and experience of those thathave come before you


Why Standardize?Why Standardize?

Transition from linearsupply chain …

…to dynamic supplyweb

RosettaNet PIPs™

Partner Interface Processes™ (PIPs™)

ProcessPO

Send POCustomer

Send POSupplier

ProcessSales Order

Customer Supplier

Receive POAcknowledge

Send POAcknowledge

Send POResponse

Close

Send PO

Receive POResponse

Send POResponse

Acknowledge

Receive PO

Send POResponse

Receive POResponse

Acknowledge

Receive PO

CheckCustomer

CheckCredit

CheckAvailability

Create SalesOrder

Receive POAcknowledge

Send POAcknowledge

Send POResponse

Close

Receive PORequest

SelectSupplier

GenerateRFQ

SendRFQ

Select RFQResponse

SendPO

Close

Send PO

Receive POResponse

Send POResponse

Acknowledge

Receive PO

Send POResponse

Receive POResponse

Acknowledge

Receive PO

CheckCustomer

CheckCredit

CheckAvailability

Create SalesOrder

Private process(Company -specific)

Public process(Standard)

Public process(Standard)

Private process(Company -specific)

PO

CRM

SCM

ERP

Figu

re p

rovi

ded

by V

itria

Sys

tem

s


30,000 ft View of the Technology30,000 ft View of the Technology

• It is conceptually very simple.

Create content

Wrap it

Send it

Trading Partner

Initiating trading partnerprepares business documentpayload.



Create content

Wrap it

Send it

Trading Partner

Payload is placed inside XML-and MIME-based transportenvelope …



Create content

Wrap it

Send it

Trading Partner

… and sent to trading partnerURI using an agreed-upontransport: HTTP(S), SMTP,others in the future.



Create content

Wrap it

Send it

Receive it

Unwrap it

Process content

Trading Partner Trading Partner

Trading partner receivesincoming envelope.



Create content

Wrap it

Send it

Receive it

Unwrap it

Process content


Envelope is “opened” tovalidate and exposeprocessing information andbusiness document payload.



Create content

Wrap it

Send it

Receive it

Unwrap it

Process content


Payload is validated andprocessed according toRosettaNet specifications …



Create content

Wrap it

Send it

Receive it

Unwrap it

Process content

Trading Partner Trading Partner… and a response is wrappedand returned to the initiatingtrading partner.



Create content

Wrap it

Send it

Receive it

Unwrap it

Process content

Trading Partner Trading PartnerConversation (exchangeprotocol or choreography)between trading partnerscontinues according toRosettaNet specifications andmay require several iterations.


Implementation TodayImplementation Today

IMPLEMENTATION SUCCESS

0

100

200

300

400

500

600

700

10.10.2000 1.31.2001 12.31.2001

IT Board

EC Board

SM Board

Other

Partner Connections with at least one PIP™

Represents a500% increase

Note: A percentage increase of partnerconnections is the best quantitativeindicator of speed and traction ofimplementation activity. Actual numbersshould not be used out of context.Because actual connections arecalculated differently company-by-company and partners may reportconnections inconsistently, thesenumbers are estimates based ondata gathered. Numbers do not reflectadditional volume of multi-PIP activities.

projection


Implementation SuccessesImplementation Successes

Moved into production this month; expected toshorten lead time

First implementationbetween Korea- andJapan-based partners

Samsung &Sony

Automated process reduced the cycle time fororder processing between the companies

Implemented PIP 3A4 andPIP 3A7

Intel & WPI(Taiwan)

Reduced the order processing lead time toseveral minutes; enabled Compaq to receivethe P.O. acknowledgement immediately andallowed departments involved in the process toreceive related information in real time

Implemented PIP 3A4 andPIP 3A7

Compaq &Delta(Taiwan)

New process converted access to inventoryinformation from a week’s delay to real-timedata; improved customer service

Implemented PIP™ 3A2 intwo weeks

Bourns &TTI

Reduced a 5-day batched delivery cycle toovernight; results in inventory reduction,improved customer satisfaction

Up and running in six weeksArrow &Carrier

ResultsImplementationPartners

IMPLEMENTATION SUCCESS

B2B Conceptual Architecture


Conceptual Architecture

BusinessBusinessConceptual ModelConceptual Model

(Definitions, format,(Definitions, format,structure, andstructure, andchoreography)choreography)

TechnicalTechnicalConceptual ModelConceptual Model

(Standards, protocols(Standards, protocols

and tools)and tools)

Vertical Business Processes (e.g. Supply Chain)

S e c u r i t y

Backend Integration

Service-oriented Architectures

Messaging

Process Coordination Framework

Process Description Language

Core XML Format Standards

Business Model Business Processes

Directory Service

Universal BusinessProcesses

Business Model-SpecificProcesses

Vertical (SupplyChain) BusinessProcesses

Business Document Definition

TechnicalDictionaryStructure

Vertical TechnicalDictionary Content

Business DictionaryStructure

Universal BusinessDictionary Content Trading Partner A

greement (TPA

)








Directory Service

Messaging


Backend Integration

Trading Partner Agreem

ent (TPA)

S e c u r i t y


Universal BusinessDictionary Content





















Business Conceptual Layer








Directory Service

Messaging


Backend Integration


ent (TPA)

S e c u r i t y











Technical Conceptual Layer




Backend Integration


Messaging



Core XML Format Standards Directory Service








Directory Service

Messaging


Backend Integration


ent (TPA)

S e c u r i t y











Business Document Stack














Directory Service

Messaging


Backend Integration


ent (TPA)

S e c u r i t y











Business Process Stack





Directory Service











Directory Service

Messaging


Backend Integration


ent (TPA)

S e c u r i t y











Execution Component Stack

Backend Integration


Messaging








Directory Service

Messaging


Backend Integration


ent (TPA)

S e c u r i t y











Binding Components

S e c u r i t y


ent (TPA)








Directory Service

Messaging


Backend Integration


ent (TPA)

S e c u r i t y











Backend Integration

Backend Integration

Definition:Provides hooks into the backend enterprise systemsthrough API or shared messaging bus. Includesfunctions like business logic processing (execution ofthe private process) and format transformation.

Examples:� SAP Adapter

Notes:

• Fewer opportunities for standardization

• Need to work with ERP vendors to build seamlessconnections

Current:� Out of scope.

Future:� Mostly out of scope.








Directory Service

Messaging


Backend Integration


ent (TPA)

S e c u r i t y











Service-oriented Architecture


Definition:Development platform for web-basedservices.

Examples:� .NET� J2EE

Notes:

• ISVs comprise the primary stakeholdersfor this layer, who should be able to buildcompetitive solutions based on XMLstandards.

Current:� Out of scope.

Future:� Out of scope.








Directory Service

Messaging


Backend Integration


ent (TPA)

S e c u r i t y











Messaging

Messaging

Definition:This layer addresses the need for session andcommunication coordination between parties ina business transaction, including ReliableMessaging, Secured Messaging, etc.

Examples:� BizTalk/SOAP� ebXML TRP� RNIF

Notes:

• Session management and transactioncoordination in a loosely-coupled environmentwill be necessary for multi-organizationalbusiness operations where the E-Businesssolutions may not be readily accessible at alltimes.

Current:� RNIF 2.0.

Future:� ebXML Messaging Service.








Directory Service

Messaging


Backend Integration


ent (TPA)

S e c u r i t y











Core XML


Definition:Building blocks of XML content, used tospecify the representation of business (andany other) documents.

Examples:� XML DTD� XML Schema� XForms� XSL/XSLT

Notes:

• Core XML Standards from W3C

Current:� XML DTD.

Future:� XML Schema.








Directory Service

Messaging


Backend Integration


ent (TPA)

S e c u r i t y







(Definitions, format,(Definitions, format,structure, andstructure, andchoreographychoreography))






Definition:Standardized document structure and layoutdefinitions, which have specific businesspurposes.

Examples:�RosettaNet PIP Service Content�OAGI Business Object Documents

Notes:

• Dictionary terms are bound together tocreate these documents.

Current:� RosettaNet-defined Documents.

Future:� Possible Third-Party Documentsubstitutions.� Further development of PIP-specificdocuments.








Directory Service

Messaging


Backend Integration


ent (TPA)

S e c u r i t y










and toolsand tools))

Business Dictionary Structure


Definition:Schema for storing Business Dictionaryterms, including their definitions, datastructures, data types, constraints andcode lists.

Current:� RosettaNet Business DictionaryStructure.

Future:� Structure changes based on RosettaNetCore Components analysis anddevelopment.








Directory Service

Messaging


Backend Integration


ent (TPA)

S e c u r i t y











Universal Business Dictionary Content


Definition:Specifies business terminology and acceptedvalues that may be commonly used in anybusiness message; the vocabulary used toconstruct the business content of amessage.

Examples:� RosettaNet Business Dictionary� ebXML Core Components

Current:� RosettaNet Business Dictionary 2.0.

Future:� Changes and composition of complexterms based on RosettaNet CoreComponents analysis and development.








Directory Service

Messaging


Backend Integration


ent (TPA)

S e c u r i t y











Technical Dictionary Structure


Definition:Schema used to store definitions, structure,format and constraints of supply chainspecific technical dictionary terms.

Examples:

Current:� Si2/RosettaNet CIDS (ComponentInformation Dictionary Specification).

Future:� No changes planned.








Directory Service

Messaging


Backend Integration


ent (TPA)

S e c u r i t y











Vertical Technical Dictionary Content

Vertical TechnicalDictionary Content Definition:

Industry- or supply chain-specifictechnical lexicon (terms, properties,values, taxonomic structures) to be usedto construct the content of a domain-specific business document.

Current:� RosettaNet Technical Dictionary.

Future:� Further development of RNTD.








Directory Service

Messaging


Backend Integration


ent (TPA)

S e c u r i t y













Definition:This layer addresses the need forsession and communicationcoordination between parties in abusiness transaction. Sessionmanagement and transactioncoordination in a loosely-coupledenvironment are necessary for multi-organizational business operationswhere the E-Business solutions maynot be readily accessible at all times.

Examples:� WSDL, WSFL� XLANG

Current:� None.

Future:� To be based on further research.

Directory Service








Directory Service

Messaging


Backend Integration


ent (TPA)

S e c u r i t y











Directory Service


Directory Service

Definition:Specifies the structure and accessprotocol of registries and repositoriesthat trading entities can access todiscover each other’s capabilities andservices.

Examples:� UDDI�ebXML req/rep�Si2 Registry Service

Notes:

• Enables electronic discovery andconfiguration of business processes, orweb services, between tradingpartners.

Current:� Si2 Registry, UDDI (in progress).

Future:� UDDI, other technologies based onresearch.








Directory Service

Messaging


Backend Integration


ent (TPA)

S e c u r i t y













Definition:Specifies the way in which any businessprocess (whether universal or specific innature) is recorded, such that is understoodand executable in a repeatable fashion by awide array of humans and/or applications.

Examples:�ebXML BPSS�BPML�UML

Current:� UML Models, but no machine-sensibleformat published.

Future:� ebXML BPSS.








Directory Service

Messaging


Backend Integration


ent (TPA)

S e c u r i t y











Universal Business Processes


Definition:Specifies business processes that areapplicable to all businesses,regardless of the vertical industrywithin which the business operates orof the specific characteristics of thebusiness.

Examples:� Invoicing process� Purchasing process� Base level Purchase Order

Current:� ??

Future:� Improved modeling and compositioncapabilities.








Directory Service

Messaging


Backend Integration


ent (TPA)

S e c u r i t y













Definition:

Specifies business processes that are notuniversally applicable, but instead arespecific to a business with specificcharacteristics such as non-profit; small;huge, etc. where the universal processcannot be used. These processes can be:

• simple processes that are unique to abusiness model (e.g., non-profit), or

• higher-level composites or sequences ofspecified Universal Business Processes thatare unique to a business model.

Examples:� Purchase Order tax modules added to a(universal) Base Purchase Order

Current:� ??

Future:� Improved modeling; ability to inheritfrom Universal Business Processes.








Directory Service

Messaging


Backend Integration


ent (TPA)

S e c u r i t y











Vertical Business Processes


Definition:Specifies business processes that are notuniversally applicable but instead are specificto a business operating within a specificindustry or supply chain (such as ElectronicComponents, Pharmaceuticals, Automotive)where the universal process cannot be used.These processes can be:

• simple processes that are unique to asupply chain, or

• higher-level composites or sequences ofspecified Universal Business Processes thatare unique to a supply chain

Examples:� Purchase Order extensions to a (universal)Base Purchase Order for capital equipment inthe Semiconductor Manufacturing industry

Current:� ??

Future:� Improved modeling; ability to inherit fromUniversal Business Processes.








Directory Service

Messaging


Backend Integration


ent (TPA)

S e c u r i t y











Security

S e c u r I t y

Definition:This layer spans a wide range ofabstractions from basic encryption,authentication and authorization onthe core XML layer to non-repudiationand digital signature, and securitypolicies in the business process layer.

Examples:� Digital Signatures� Encryption� Digital Certificate Usage

Current:� S/MIMEv2 Signature� S/MIMEv2 Enveloping� SSLv3

Future:� XML Signature.








Directory Service

Messaging


Backend Integration


ent (TPA)

S e c u r i t y











Trading Partner Agreement


ent (TPA)

Definition:Dynamic creation and managementof trading partner agreements betweenpartners. Profiles of trading partner’s B2Binfrastructure, protocols, contractualagreement for transactions.

Examples:� ebXML CPPA

Current:� No formal specification; individuallydeveloped agreements.

Future:� Standard TPA and Collaboration Profilespecification, possibly ebXML CPPA.








Directory Service

Messaging


Backend Integration

S e c u r i t y












ent (TPA)

Conceptual ArchitectureConceptual Architecture

Standards Convergence


Convergence OpportunitiesConvergence Opportunities

• Not all standards efforts are created equal!

• We need to better utilize existing standards notcreate new ones

• Of the various standards components moststandards efforts focus on business content

• Creating business process standards is verydifficult

• RosettaNet has created and published aproduction-ready framework based on XML


RosettaNet Position on StandardsConvergenceRosettaNet Position on StandardsConvergence

• RosettaNet will continue to track newhorizontal standards efforts…

• Rosettanet is committed to adoptingelements of the architecture when theybecome broadly accepted horizontalstandards…

• Rosettanet will provide smooth transitionto new horizontal standards as adopted…


Standards TransitionStandards Transition

Announced• Future releases of RNIF will include support for

the ebXML’s TRP (Messaging ServiceSpecification). May 2001.

• 83 RosettaNet PIP s registered within the UDDIUniversal Business Registry, April 2001.

Ongoing• RosettaNet contributing to ebXML’s BPSS

(Business Process Specification Schema) fordocumenting PIP s in XML.

• RosettaNet contributing to UN/CEFACT BL (corecomponents)


AcknowledgementsAcknowledgements

• RosettaNet– Pete Wenzel Chief Architect– Jennifer Hamilton, CEO– Paul Tearnen, VP Standards

• WebMethods– Mitch Shue, former RosettaNet Chief Architect

• Intel:– Jackson He,

– Steve Agritelley

• Business Internet Consortium

Appendix: Glossary


Glossary of TermsGlossary of Terms

authXML Authentication and AuthorizationInformation in XML

BIC Business Internet Consortium

BPML Business Process Modeling Language

BPMI Business Process Management Initiative

BTP Business Transaction Protocol

cXML Commercial Extensible Mark-up Language

ebXML E-business XML Initiative

ECIX Electronic Component Information Exchange

IEC International Electrotechnical Commission

JETIA Japan Electronics and Information TechnologyIndustries Association

NEMI National Electronic Manufacturing Initiative


Glossary of TermsGlossary of Terms

OAG Open Applications Group

OASIS Organization for Advancement of StructuredInformation Standards

OBI Open Buying on the InternetS2ML Security Services Mark-up LanguageSi2 Silicon Integrated InitiativeSOAP Simple Object Access ProtocoltpaML Trading Partner Agreement Mark-up LanguageUDDI Universal Description Discovery and IntegrationUCC Uniform Code CouncilUN United NationsVFIIP Virtual Factory Information Interchange ProjectW3C World Wide Web ConsortiumXAML Transaction Authority Mark-up LanguagexCBL XML Common Business Library