Transcription
Agenda RosettaNet Why Standardize XML? RosettaNet PIPTMs RosettaNet B2B ArchitectureB2B StandardsDerek Coleman, Chief Technologist RosettaNetOn loan from Hewlett-Packard2Standards Convergence COPYRIGHT 2001 ROSETTANET. ALL RIGHTS RESERVED.About 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.RosettaNet4Standards Convergence COPYRIGHT 2001 ROSETTANET. ALL RIGHTS RESERVED.
RosettaNet Governing ProcessRosettaNetExecutive Board Provide overallguidance Addressprioritization andintegration acrossboardsIndividualSupply ChainBoards Address SMsupply chainspecific issues Prioritization Resources Implementationand adoptionInformation Technology (IT)Supply Chain Board3ComRosettaNetPartnersArrow ElectronicsAvnetCisco Systems Vote onCompaqstandardsCompUSA Participate inworkshopsDell ImplementFederal ntTechnologiesNECNetscapeOffice DepotPioneerQuantumSAPSiemensSolectronTech DataTrilogyUPSX36Electronic Components (EC)Supply Chain BoardAgilentIntelAlteraKemetArrow ElectronicsLucentTechnologiesAvnetAVXBournsCisco SystemsFCIFuture ElectronicsHitachiIBM7Standards Convergence COPYRIGHT 2001 ROSETTANET. ALL RIGHTS RESERVED.Semiconductor Manufacturing (SM)Supply Chain BoardPioneerAir Products &ChemicalsSamsungAgilent TechnologiesSolectronMicron TechnologySumitomo MetalMotorolaTexas InstrumentsAmkor TechnologyNationalSemiconductorTOKMemecSonyApplied MaterialsNECTokyo ElectronMicron TechnologySTMicroelectronicsASETexas iconductorSamsung su HandoutaiTSMCNokiaTyco ElectronicsJSRShinko ElectronicsUMCNECXilinxLSISPILLucent TechnologiesSumitomo BakeliteNationalPhilipsSemiconductorsStandards Convergence COPYRIGHT 2001 ROSETTANET. ALL RIGHTS RESERVED.8Standards Convergence COPYRIGHT 2001 ROSETTANET. ALL RIGHTS RESERVED.WinbondXilinx
What 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 butIndustry RecognitionIn a special year-end issueof tomorrow’s LEADERS,RosettaNet is named aTOP 10 WINNEROF 2000 by“RosettaNet is arguablythe MOTHER OF ALLindustry-specific XML ettaNet's e-businesscommunications standardsare GIANT STEPS onthe journey towardMOST AMBITIOUSSOLVING someinter-enterprise contentofthese problems.”and process integrationCRNefforts currently underway.”3.19.01Patricia Seybold GroupRosettaNetis “one of theinstead works with industry thought leaders todevelop business process specifications4.3.019Standards Convergence COPYRIGHT 2001 ROSETTANET. ALL RIGHTS RESERVED.10Standards Convergence COPYRIGHT 2001 ROSETTANET. ALL RIGHTS RESERVED.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 protocolsWhy Standardize XML12Standards Convergence COPYRIGHT 2001 ROSETTANET. ALL RIGHTS RESERVED.
Why Standardize?Why Standardize? Competitive pressure to achieve extremeTransition from linearsupply chain operational efficiency Competitive pressure to create additionalbusiness value Makes integration efforts efficient and repeatable Promotes loose coupling of trading partners, to dynamic supplyweballowing for rapid reconfiguration of supply webs Leverages expertise and experience of those thathave come before youStandards Convergence COPYRIGHT 2001 ROSETTANET. ALL RIGHTS RESERVED.14Standards Convergence COPYRIGHT 2001 ROSETTANET. ALL RIGHTS RESERVED.Partner Interface Processes (PIPs )SupplierCustomerPrivate process(Company -specific)ProcessPOReceive POPublic process(Standard)Send POCustomerPublic process(Standard)Send POSupplierRequestPORosettaNet PIPs Figure provided by Vitria Systems13SelectSupplierGenerateRFQSend POReceive POAcknowledgeReceive POSend POAcknowledgeSendRFQSelect RFQResponseSendPOClosePrivate process(Company -specific)ProcessSales OrderReceive POCheckCustomerCheckAvailabilityReceive POResponseSend POResponseSend POResponseAcknowledgeReceive POResponseAcknowledgeCRMCheckCreditSCMCreate SalesOrderSend POResponseCloseERP
30,000 ft View of the Technology30,000 ft View of the Technology It is conceptually very simple.Trading PartnerTrading PartnerCreate contentCreate contentWrap itSend it17Standards Convergence COPYRIGHT 2001 ROSETTANET. ALL RIGHTS RESERVED.30,000 ft View of the TechnologySend it18Payload is placed inside XMLand MIME-based transportenvelope Standards Convergence COPYRIGHT 2001 ROSETTANET. ALL RIGHTS RESERVED.30,000 ft View of the TechnologyTrading PartnerTrading PartnerTrading PartnerCreate contentCreate contentReceive itWrap itUnwrap itWrap itSend it19Wrap itInitiating trading partnerprepares business documentpayload. and sent to trading partnerURI using an agreed-upontransport: HTTP(S), SMTP,others in the future.Standards Convergence COPYRIGHT 2001 ROSETTANET. ALL RIGHTS RESERVED.Trading partner receivesincoming envelope.Send it20Process contentStandards Convergence COPYRIGHT 2001 ROSETTANET. ALL RIGHTS RESERVED.
30,000 ft View of the TechnologyTrading PartnerTrading PartnerTrading PartnerTrading PartnerCreate contentReceive itCreate contentReceive itWrap itUnwrap itWrap itUnwrap itEnvelope is “opened” tovalidate and exposeprocessing information andSend itbusiness document payload.2130,000 ft View of the TechnologyPayload is validated andprocessed according toSenditRosettaNetspecifications Process contentStandards Convergence COPYRIGHT 2001 ROSETTANET. ALL RIGHTS RESERVED.30,000 ft View of the Technology22Standards Convergence COPYRIGHT 2001 ROSETTANET. ALL RIGHTS RESERVED.30,000 ft View of the TechnologyConversation (exchangeTrading protocolPartneror choreography)Trading Partnerbetween trading partnerscontinues according toCreate contentReceive itRosettaNet specifications andmay require several iterations.Trading Partnerand a response isTradingwrappedPartnerand returned to the initiating23Process contenttrading partner.Create contentReceive itWrap itUnwrap itWrap itUnwrap itSend itProcess contentSend itProcess contentStandards Convergence COPYRIGHT 2001 ROSETTANET. ALL RIGHTS RESERVED.24Standards Convergence COPYRIGHT 2001 ROSETTANET. ALL RIGHTS RESERVED.
Implementation TodayImplementation SuccessesPartner Connections with at least one PIP 700600IT BoardRepresents a500% increaseEC BoardSM .2001projectionNote: 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-bycompany and partners may reportconnections inconsistently, thesenumbers are estimates based ondata gathered. Numbers do not reflectadditional volume of multi-PIP activities.IMPLEMENTATION SUCCESS25Standards Convergence COPYRIGHT 2001 ROSETTANET. ALL RIGHTS RESERVED.PartnersImplementationResultsArrow &CarrierUp and running in six weeksReduced a 5-day batched delivery cycle toovernight; results in inventory reduction,improved customer satisfactionBourns &TTIImplemented PIP 3A2 intwo weeksNew process converted access to inventoryinformation from a week’s delay to real-timedata; improved customer serviceCompaq &DeltaImplemented PIP 3A4 andPIP 3A7Reduced 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 timeImplemented PIP 3A4 andPIP 3A7Automated process reduced the cycle time fororder processing between the companiesFirst implementationbetween Korea- andJapan-based partnersMoved into production this month; expected toshorten lead time(Taiwan)Intel & WPI(Taiwan)Samsung &SonyIMPLEMENTATION SUCCESS26Standards Convergence COPYRIGHT 2001 ROSETTANET. ALL RIGHTS RESERVED.Conceptual ArchitectureBusiness DictionaryStructureVertical TechnicalDictionary ContentTechnicalDictionaryStructureBusiness Document DefinitionUniversal BusinessProcessesProcess Description LanguageDirectory ServiceProcess Coordination FrameworkService-oriented ArchitecturesBackend Integration28(Definitions, format,structure, andchoreography)Business Model Business ProcessesMessagingB2B Conceptual ArchitectureBusinessConceptual ModelVertical (SupplyBusiness ProcessesBusiness ModelVertical(e.g. esStandards Convergence COPYRIGHT 2001 ROSETTANET. ALL RIGHTS RESERVED.S e c u r i t yCore XML Format StandardsTrading Partner Agreement (TPA)Universal BusinessDictionary ContentTechnicalConceptual Model(Standards, protocolsand tools)
Business Conceptual LayerTechnicalDictionaryStructureBusinessBusiness DocumentDocument DefinitionDefinition(Definitions, format,structure, andchoreography)Business Model Business ProcessesUniversal BusinessDictionary ContentVertical TechnicalDictionary ContentBusiness versal ry ServiceProcess Coordination FrameworkCore XMLXML FormatFormat StandardsStandardsCoreTechnicalConceptual Model(Standards, protocolsand tools)Messaging29Process Description LanguageDirectory ServiceProcess Coordination FrameworkService-oriented ArchitecturesArchitecturesService-orientedBackend Standards, protocolsBusinessConceptual Model(Definitions, format,structure, andchoreography)Universal BusinessDictionary ContentVertical TechnicalDictionary ContentBusiness versal BusinessProcessesProcess Coordination FrameworkCore XML Format StandardsTechnicalConceptual Model(Standards, protocolsand tools)MessagingUniversalUniversal BusinessBusinessProcessesProcessesProcess Description LanguageDirectory ServiceProcess Coordination FrameworkMessagingService-oriented ArchitecturesBackend IntegrationBackend Integration32(Definitions, format,structure, andchoreography)Business Model Business ProcessesService-oriented ArchitecturesStandards Convergence COPYRIGHT 2001 ROSETTANET. ALL RIGHTS RESERVED.BusinessConceptual ModelVerticalBusinessBusiness ModelVerticalVertical(Supply(Supply nessBusinessProcessesProcessesProcessesStandards Convergence COPYRIGHT 2001 ROSETTANET. ALL RIGHTS RESERVED.S e c u r i t yDirectory ServiceBusiness Document DefinitionTrading Partner Agreement (TPA)Vertical (Supply Business ModelChain) Business SpecificProcessesProcessesProcess Description LanguageStandards Convergence COPYRIGHT 2001 ROSETTANET. ALL RIGHTS RESERVED.Business Process StackS e c u r i t yCore XMLXML FormatFormat StandardsStandardsCoreTrading Partner Agreement al Modeland tools)Backend IntegrationBusinessBusiness DocumentDocument DefinitionDefinition31Universal BusinessProcessesService-oriented ArchitecturesBusiness Document StackBusinessBusiness , format,structure, andchoreography)MessagingMessagingStandards Convergence COPYRIGHT 2001 ROSETTANET. ALL RIGHTS RESERVED.Universal BusinessBusinessUniversalDictionary ContentContentDictionaryBusinessConceptual ModelVertical (Supply Business ModelChain) Business SpecificProcessesProcessesS e c u r i t yProcess Description LanguageBusiness Document DefinitionS e c u r i t yCore XML Format StandardsBusinessConceptual ModelVerticalBusinessBusiness ModelVertical(Supply(Supply ding Partner Agreement (TPA)BusinessBusiness ontentTrading Partner Agreement (TPA)UniversalUniversal BusinessBusinessDictionaryDictionary ContentContentTechnical Conceptual LayerTechnicalConceptual Model(Standards, protocolsand tools)
Execution Component StackBusiness iness Document Definition(Definitions, format,structure, andchoreography)Universal BusinessDictionary ContentVertical TechnicalDictionary ContentBusiness versal BusinessProcessesDirectory ServiceProcess Coordination FrameworkCore XML Format StandardsTechnicalConceptual Model(Standards, protocolsand tools)Process Description LanguageDirectory ServiceProcess Coordination FrameworkService-oriented ArchitecturesBackend IntegrationStandards Convergence COPYRIGHT 2001 ROSETTANET. ALL RIGHTS RESERVED.34TechnicalDictionaryStructureBusiness Document DefinitionService-oriented ArchitectureBusinessVertical (Supply Business ModelConceptual ModelSpecificChain) ooks into the backend enterprisesystems format,Processesstructure, andthrough API or shared messaging bus. Includeschoreography)functions like business logic processing (executionofthe private process) and format transformation.Universal BusinessDictionary ContentVertical TechnicalDictionary ContentBusiness versal BusinessExamples:ProcessesNotes:Business Document DefinitionProcess DescriptionLanguagefor standardization Fewer opportunities Need to work with ERP vendors to build seamlessDirectoryServiceconnectionsCurrent:Process CoordinationFramework Out of scope.MessagingFuture: Mostly out of scope.Core XML Format StandardsTechnicalConceptual Model(Standards, protocolsand tools)BusinessVertical (Supply Business ModelConceptual ModelChain) Business SpecificDefinition:(Definitions, format,Development platform for web-basedProcessesProcessesstructure, andservices.Notes: ISVs comprise the primary stakeholdersProcess Description Languagefor this layer, who should be able to buildcompetitive solutions based on XMLstandards.Directory ServiceMessagingService-oriented ArchitecturesBackend IntegrationBackend Integration36Current: Out of scope.Process Coordination FrameworkService-oriented ArchitecturesStandards Convergence COPYRIGHT 2001 ROSETTANET. ALL RIGHTS RESERVED.choreography)Examples: .NETUniversal BusinessProcesses J2EES e c u r i t y SAP AdapterS e c u r i t yCore XML Format Standards(Standards, protocolsStandards Convergence COPYRIGHT 2001 ROSETTANET. ALL RIGHTS RESERVED.Trading Partner Agreement (TPA)Business DictionaryStructureTrading Partner Agreement (TPA)Vertical TechnicalDictionary ContentTechnicalConceptual Modeland tools)Backend IntegrationIntegrationBackendBackend Integration35Universal BusinessProcessesService-oriented l BusinessDictionary Content(Definitions, format,structure, essConceptual ModelVertical (Supply Business ModelChain) Business SpecificProcessesProcessesS e c u r i t yProcess Description LanguageBusiness Document DefinitionS e c u r i t yCore XML Format StandardsBusinessConceptual ModelVertical (Supply Business ModelChain) Business SpecificProcessesProcessesTrading Partner Agreement (TPA)Vertical TechnicalDictionary ContentTrading Partner Agreement (TPA)Universal BusinessDictionary ContentBinding ComponentsStandards Convergence COPYRIGHT 2001 ROSETTANET. ALL RIGHTS RESERVED.Future: Out of scope.TechnicalConceptual Model(Standards, protocolsand tools)
MessagingBusiness iness Document DefinitionConceptual Model(Definitions, format,structure, andchoreography) ebXML TRP RNIFUniversal BusinessDictionary ContentVertical TechnicalDictionary ContentBusiness versalNotes:BusinessProcesses Session management and transactionDirectory ServiceCurrent: RNIF 2.0.Process Coordination FrameworkFuture: ebXML Messaging Service.Core XMLXML FormatFormat StandardsStandardsCoreTechnicalConceptual Model(Standards, protocolsand tools)BusinessProcesses Core XML Standards from W3CCurrent: Description LanguageProcess XML DTD.Future: Directory XML Schema.Standards Convergence COPYRIGHT 2001 ROSETTANET. ALL RIGHTS RESERVED.38Business Dictionary StructureBusinessConceptual ModelDefinition:Vertical(Supply Business ModelStandardized document structure and layoutSpecificChain)Businessdefinitions,which havespecific businessProcessespurposes.Processes(Definitions, format,structure, andchoreography)choreography)Examples: RosettaNet PIP Service Content OAGIUniversalBusiness ObjectDocumentsBusinessNotes:Universal BusinessDictionary ContentCurrent: RosettaNet-definedDocuments.Directory ServiceFuture: PossibleThird-Party DocumentProcessCoordinationFrameworksubstitutions. Further development of PIP-specificdocuments.Current:Business Document DefinitionUniversal BusinessProcesses RosettaNet Business DictionaryStructure.Core XML FormatTechnicalConceptual ModelProcess Description LanguageFuture: Structure changes based on RosettaNetCore Components analysis andDirectory ServiceStandardsdevelopment.(Standards, protocolsand tools)MessagingProcess Coordination FrameworkMessagingService-oriented ArchitecturesService-oriented ArchitecturesBackend IntegrationBackend IntegrationStandards Convergence COPYRIGHT 2001 ROSETTANET. ALL RIGHTS RESERVED.40(Definitions, format,structure, andchoreography)terms, including their definitions, dataDictionarystructures, data types, constraints andStructurecode lists.Standards Convergence COPYRIGHT 2001 ROSETTANET. ALL RIGHTS RESERVED.S e c u r i t y Dictionary terms are bound together tocreate these documents.Process Description LanguageBusinessConceptual ModelVertical (Supply Business ModelChain) Business SpecificDefinition:ProcessesSchema for storingBusiness DictionaryProcessesTechnicalVertical TechnicalDictionary ContentBusinessBusiness DictionaryDictionaryStructureStructureProcessesS e c u r i t yCore XML Format Standards(Standards, protocolsStandards Convergence COPYRIGHT 2001 ROSETTANET. ALL RIGHTS RESERVED.Trading Partner Agreement (TPA)BusinessBusiness DocumentDocument DefinitionDefinitionTrading Partner Agreement al Modeland tools)Backend IntegrationBusiness DictionaryStructureServiceProcess Coordination FrameworkService-oriented ArchitecturesBusiness Document Definition39Notes:Backend IntegrationVertical TechnicalDictionary Content(Definitions, format,structure, andchoreography) XML Schema XForms XSL/XSLTUniversalService-oriented ArchitecturesUniversal BusinessDictionary ContentBusinessConceptual ModelChain) Business SpecificExamples:ProcessesProcesses XML g blocks of XML content, used tospecify the representation of business (andBusiness ModelVertical(Supplyany other)documents.S e c u r i t yProcessBusiness Document Definitioncoordination in a loosely-coupled environmentwill be necessary for multi-organizationalbusiness operations where the E-BusinessDescriptionsolutions may Languagenot be readily accessible at alltimes.S e c u r i t yCore XML Format StandardsVerticalSpecificChain) BusinessExamples:ProcessesProcesses BizTalk/SOAPCore XMLTrading Partner Agreement (TPA)Vertical TechnicalDictionary ContentTrading Partner Agreement (TPA)Universal BusinessDictionary ContentDefinition:This layer addresses the need for ses
Implementation 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 a 500% increase Note: A percentage increase of partner connections is the best quantitative indicator of speed and
