This action might not be possible to undo. Are you sure you want to continue?
Barbara Heikkinen firstname.lastname@example.org Nokia Research Center 28th of May 2002 XML Finland Seminar “XML databases and XML in the public sector”
• What is RosettaNet? • RosettaNet structure • The Next Generation Architecture of RosettaNet • Links: more information on XML and UML • Contents of the slides are gathered from two sources • The External Communications set, Nokia, February 2002 • The NextGen PIP Tutorial for Reviewers, RosettaNet, November 2001
http://www.rosettanet.org/rosettanet/Rooms/DisplayPages/LayoutInitial?Contain er=com.webridge.entity.Entity%5BOID%5B7F2298D440526043A453A67B27BE F776%5D%5D
RosettaNet-Nokia-BH-2002-05-28.ppt/ Barbara Heikkinen
creating a common language and open ebusiness processes that provide measurable benefits and are vital to the evolution of the global.The RosettaNet Vision. Mission Vision: The Leader in global e-business standards Mission: RosettaNet drives collaborative development and rapid deployment of internet-based business standards. high-technology trading network 3 © NOKIA RosettaNet-Nokia-BH-2002-05-28.ppt/ Barbara Heikkinen .
ppt/ Barbara Heikkinen .It's all about integrated business processes RosettaNet PIPs 4 © NOKIA RosettaNet-Nokia-BH-2002-05-28.
E-Business Exchange Telephone Telephone Business Process Business Process Dialog DIALOG Grammar Words Alphabet Sound human-to-human business exchange 5 © NOKIA RosettaNet-Nokia-BH-2002-05-28.ppt/ Barbara Heikkinen Ecom Application eBusiness Process RosettaNet PIP™ Framework Dictionary XML Internet Partner-to-Partner eBusiness exchange .
ppt/ Barbara Heikkinen .eBusiness Tools for doing business with Nokia Exists Electronic Data Interchange Existing standard. Nokia recongises that EDI is needed by some partners. but does not deliver a system to system connection Under deployment Rosettanet is a nonproprietary XML protocol allowing system to system connections. Nokia is committed to integrate business process with Rosettanet standard.and will be supported accordingly In production Nokia Global Supply Web NGSW is Nokia's web marketplace. Easy to set up and operate. 6 © NOKIA RosettaNet-Nokia-BH-2002-05-28.
ppt/ Barbara Heikkinen .Final Goal: Integrated Business Processes Conducted On-line SUPPLIER On-line Business processes between: •Human-to-human Millions of components every hour NOKIA •System-to-human/human-to-system (WEB) •System-to-system (RosettaNet) 7 © NOKIA RosettaNet-Nokia-BH-2002-05-28.
Purpose of RosettaNet work in Nokia • Use RosettaNet standard for business process and system integration with external business partners • Use RosettaNet processes and process interfaces as a guideline for Nokia internal process development and modular business platform development • Actively participate to RosettaNet work and drive standard development to make sure it is supporting Nokia business requirements and needs • Emphasize Nokia business partners to join RosettaNet and apply that as a standard for business process and system integration RosettaNet-Nokia-BH-2002-05-28.ppt/ Barbara Heikkinen 8 © NOKIA .
there are seven Partner Interfaces Processes (PIP) in use between Nokia and its business partners. Sourcing & Procurement. • Currently. • order management. • transportation and distribution. They cover • collaborative forecasting. and our target is to have 40% of Nokia's purchasing volume involved in RosettaNet interfaces already this year. ranging from component suppliers to customers and contact manufacturers.ppt/ Barbara Heikkinen Press Release.• Jean-Francois Baril. and • finance. Nokia Mobile Phones • In 2001. we concentrated on gaining experiences from RosettaNet with a selected number of business partners. • 9 © NOKIA RosettaNet-Nokia-BH-2002-05-28. senior vice president. February 26. We are convinced that RosettaNet is the right choice for our business integration. 2002: Nokia continues to drive the implementation of RosettaNet standards .
ppt/ Barbara Heikkinen . •Nokia is represented in this board as well EC • Solution Provider Board •System solution providers Supply Chain Boards Solution Provider Board •i2. IT SM • Supply chain boards •EC. Information Technology •SM. Electronic components (Nokia) Nokia •IT. etc. SAP.Rosettanet structure • Rosettanet Executive board (Nokia) Nokia Rosettanet Executive Board •Rosettanet overall management and admin. Semiconductor Manufacturing • Role of supply chain boards •Drive and prioritize the standard development according to business requirements of this particular supply chain 10 © NOKIA RosettaNet-Nokia-BH-2002-05-28.
Molex PASSIVE SUPPLIER AVX. Samsung. TI. Kemet 11 © NOKIA RosettaNet-Nokia-BH-2002-05-28. FCI..ppt/ Barbara Heikkinen . National. Intel. Hitachi. Bourns. Xilinx. NEC. Nokia RosettaNet EC Managing Board DISTRIBUTOR Arrow. CUSTOMER Agilent. Solectron. ST. Pioneer. Lucent. Avnet. CISCO. IBM. Toshiba.Extensive representation from Electronics Industry SEMICONDUCTOR SUPPLIERS Altera. VEBA CONNECTOR SUPPLIER Tyco. Sony Process integration takes two.. AMD. Philips. Motorola. Future. Micron.
provide a common set of properties for PIP™s & designates the properties used in basic business activities. • Product & Partner Codes .Working in conjunction with RosettaNet dictionaries are product and partner codes. • RNIF . the RosettaNet Implementation Framework (RNIF) provides common exchange protocols that enable the implementation of PIP™s.ppt/ Barbara Heikkinen . including the Data Universal Numbering System (D-U-N-S).An open. Global Trade Item Number (GTIN) and United Nations/Standard Product and Services Code (UN/SPSC). common networked-application framework. 12 © NOKIA RosettaNet-Nokia-BH-2002-05-28.The Key Elements of RosettaNet • PIP™s – Partner Interface Processes – define business processes between supply-chain companies. providing the models and documents for the implementation of standards • Dictionaries .
Service Packages and Contract Services Segment 6B: Provide and Administer Asset Management Segment 6C: Technical Support and Service Management Cluster 7: Manufacturing Segment 7A: Design Transfer Segment 7B: Manage Manufacturing WO & WIP Segment 7C: Distribute Manufacturing Information Segment 1B: Product and Service Segment 2B: Product Change Review Notification Segment 2C: Product Design Information 13 © NOKIA RosettaNet-Nokia-BH-2002-05-28.ppt/ Barbara Heikkinen . decisions and interactions that fulfill a business transaction • Specify structure and format of business document payloads • Organized by clusters and segments Cluster 0: RosettaNet Support Cluster 1: Partner.Partner Interface Process™ (PIP™) • Depict activities. Product and Service Review Segment 1A: Partner Review Cluster 2: Cluster 3: Product Information Order Management Segment 2A: Preparation for Distribution Segment 3A: Quote and Order Entry Segment 3B: Transportation and Distribution Segment 3C: Returns and Finance Segment 3D: Product Configuration Segment 0A: Administrative Cluster 4: Inventory Management Segment 4A: Collaborative Forecasting Segment 4B: Inventory Allocation Segment 4C: Inventory Reporting Segment 4D: Inventory Replenishment Segment 4E: Sales Reporting Segment 4F: Price Protection Cluster 5: Marketing Information Management Segment 5A: Lead Opportunity Management Segment 5B: Marketing Campaign Management Segment 5C: Design Win Management (EC) Segment 5D: Ship from Stock and Debit (EC) Cluster 6: Service and Support Segment 6A: Provide and Administer Warranties.
ppt/ Barbara Heikkinen .. Global Trade Item Number (GTIN) 14 © NOKIA RosettaNet-Nokia-BH-2002-05-28.RosettaNet Business & Technical Dictionaries • Ensures consistent information exchange during PIP™ execution • Technical dictionary (form.g. fit. function) • Specifies common product properties • Business dictionary • Specifies common partner properties • Enables partners to identify one another • Shares common standards • E.
CEO. see http://www.can send complex documents • Support for S/MIME v. privacy and authentication • Future: “RosettaNet plans to integrate support for the ebXML Messaging Services Specification in future releases of RosettaNet's Implementation Framework (RNIF)”.RosettaNet Implementation Framework (RNIF) Core • Defines RosettaNet Object (RNO) • Specifies how to transport RosettaNet Object between trading partners’ network applications • Version 2. .2 .org/endorsements.0 features and benefits: • HTTP and SMTP transfer protocols better support for emarketplaces • Support for .htm#rosetta 15 © NOKIA RosettaNet-Nokia-BH-2002-05-28. Jennifer Hamilton.gif files . RosettaNet.greater security.pdf.ebxml.ppt/ Barbara Heikkinen .
ROSETTANET PIP DOCUMENTATION PIP SPECIFICATION • word document • one per PIP • defines the process • players & roles www.org standards PIPs • activities PIP DOCUMENTATION TO BE DOWNLOADED XML MESSAGE GUIDELINE (+DTD) • messages • HTML document • one per each message • defines the message • structure 16 © NOKIA RosettaNet-Nokia-BH-2002-05-28.rosettanet.ppt/ Barbara Heikkinen • data entities • cardinalities .
ppt/ Barbara Heikkinen . where it was discovered in July 1799 by Pierre François Xavier Bouchard.Why RosettaNet is called RosettaNet? The name of RosettaNet originates from Hieroglyphs The Rosetta Stone (196 Demotic the everyday script of literate Egyptians BC). which provided the key to solve the mystery of hieroglyphs. The Rosetta stone is now located at British Museum in London. The Rosetta Stone was probably originally erected at the temple of the city of Sais. Demotic and Hieroglyphs. later in the medieval period moved to Rosetta (aka el-Rashid). The Rosetta Stone is the only surviving fragment of a stella bearing a decree written in three languages: Greek. Greek the language of the government 17 © NOKIA RosettaNet-Nokia-BH-2002-05-28.
ppt/ Barbara Heikkinen .The Next Generation Architecture of RosettaNet • PIP® process specifications: choreography and message controls • To use Business Process Specification Schema (BPSS) from ebXML • Re-architected business content • Standard and reusable PIP “components” • UML as a message design notation • PIPs defined in machine-sensible XML Schema • Choreography and message controls in a BPSS document • Each business document defined by a schema 18 © NOKIA RosettaNet-Nokia-BH-2002-05-28.
ppt/ Barbara Heikkinen .PIP® Business Document Specification • Major change from current PIP specification • Design in terms of small cohesive “core objects” • Organize components into domain specific reusable packages • Build larger grained elements by composing them from core objects • Capture the unique requirements of business scenarios by specializing elements • XML Schema can be generated from the UML class diagrams (via MOF and XMI) • Single XML Schema defines document instead of Message Guidelines+DTD 19 © NOKIA RosettaNet-Nokia-BH-2002-05-28.
ppt/ Barbara Heikkinen . but defined differently in same PIP document and across multiple PIP documents Elements with different names.. e.Motivations • Transition from DTDs to XML Schemas • Going towards applying software development methodologies for building and maintaining XML vocabularies • Trying to repaire structural problems like • Inconsistencies. • • • • • • • • • • Optionality Elements with same name.g. but having the same definition Message guideline and DTD not the same Implementers must create agreements with each trading partner on how and when to use optional elements Optionality should be used carefully Lack of formal requirements that resulted in PIP documents and document content Ambiguous or undefined constraints in PIP documents PIP documents structures are not consistent Specifications are not machine-readable • Complexity 20 © NOKIA RosettaNet-Nokia-BH-2002-05-28.
ppt/ Barbara Heikkinen .org/nextgen/businessdocheader namespace http://www.org/nextgen/financialdoc 21 © NOKIA RosettaNet-Nokia-BH-2002-05-28.rosettanet.roset tanet.org/ next gen/tax namespace http://www.roset tanet.org/ next gen/pip3c3/invoicenotificat ion FinancialDoc BusinessDocHeader Tax Primitives XML Schema for Document namespace http://www.org/nextgen/primitives Packages used in this Business Document namespace htt p:/ /www.rosettanet.rosettanet.Reuse Structure of Business Document Package containing UML Design for Business Document PIP 3C3 Notification of Invoice namespace htt p:/ /www.
n PIP3C3_ LineItem 1 PIP3C3_ FinancialDocument LineItemProduct product 1 PurchaseOrderLine OrderComponent Reference componentReference Classes correspond to elements 1 PurchaseOrder Reference Invoice 1 type 1 InvoiceTypeRef (from Primitives) Financing 0.Structure of Business Document <<Abstract>> PIPNotification (from BusinessDocHeader) <<Abstract>> FinancialDocument (from FinancialDoc) <<Abstract>> FinancialDocument LineItem (from FinancialDoc) <<Abstract>> FinancialDocument LineItemProduct (from FinancialDoc) PIP3C3_ InvoiceNotification 1 <<Abstract>> PIP3C3_Financial Document 1.ppt/ Barbara Heikkinen Classes defined in Business Dictionary ...1 “is a” InvoiceMemo 1 type InvoiceMemo TypeRef (from Primitives) colored nodes = reused from other packages 1 originalInvoice InvoiceReference “is composed of” or “has a” 22 © NOKIA RosettaNet-Nokia-BH-2002-05-28.
Links • RosettaNet http://www.org/XML/Schema • XML Schemas.org • ebXML. W3C http://www.cetus-links.org/oo_uml.omg.ebxml.org/schemas.com/BestPracticesHomepage.html • XML Schemas: Best Practices Homepage http://www.html 24 © NOKIA RosettaNet-Nokia-BH-2002-05-28.org/uml/ • UML Forum http://www.ppt/ Barbara Heikkinen .xfront.com/uml/ • Cetus Links on UML http://www. OMG http://www.coverpages.html • XML Schema. The XML Cover Pages http://xml.org • UML (Unified Modeling Language).w3.celigent. UN/CEFACT and OASIS http://www.rosettanet.
sdmagazine. David Carlson http://xmlmodeling.org/workshop/proceedings/Carlson.htm • Conceptual Modeling and Markup Languages.coverpages.org/conceptualModeling.org/technology/documents/formal/xmi.com/examples/uddi/ o Modeling XHTML with UML http://xmlmodeling.html o Online article: Modeling XML Applications (Software Development Magazine) http://www.More information on XML and UML • XML Metadata Interchange (XMI).com/documents/s=815/sdm0206e/ o Presentation: Analysis and Design of XML Vocabularies with UML http://swradio.omg. the XML Cover Pages http://xml.ppt o Modeling the UDDI Schema with UML http://xmlmodeling.omg. OMG http://www.org/ni2001-04-19-a.com/ o Book: Modeling XML Applications with UML (Addison-Wesley) http://xml.coverpages.html • XML Modeling.com/examples/xhtml/ 25 © NOKIA RosettaNet-Nokia-BH-2002-05-28.ppt/ Barbara Heikkinen .
ibm.edu/~melnik/rdf/uml/ • RosettaNet Next Generation Architecture http://www. IBM http://www-106.pdf • XMI and UML combine to drive product development.org/projects/ • OASIS Universal Business Language (UBL) TC http://www.pdf • Representing UML in RDF.ppt/ Barbara Heikkinen .org/SWWS/program/full/paper1.rational.oasis-open.More information on XML and UML • Migrating from XML DTD to XML Schema using UML.html • UML and the Semantic Web.stanford. SWWS 2001 http://www.org/rosettanet/Rooms/DisplayPages/LayoutInitial?Contai ner=com. UN/CEFACT http://www.com/developerworks/xml/library/x-xmi/index.com/media/whitepapers/TP189draft.org/committees/ubl/ 26 © NOKIA RosettaNet-Nokia-BH-2002-05-28.ebxml. S. Cranefield.Entity%5BOID%5B04E190566686B54EACA0A2E69 2A8A8B5%5D%5D • ebXML Technical Architecture http://www.ebtwg.webridge. Rational http://www.org/specs/ebTA.entity. S.semanticweb. Melnik http://www-db.rosettanet.pdf • The eBusiness Transition Ad-Hoc Working Group (eBTWG).
This action might not be possible to undo. Are you sure you want to continue?
We've moved you to where you read on your other device.
Get the full title to continue listening from where you left off, or restart the preview.