1 / 23

papiNet from Top to Bottom

papiNet from Top to Bottom. An introduction to papiNet. Agenda. What is papiNet? Charter Organization papiNet Goals Implementation Status Current and Planned Implementations What Messages are Being Implemented? papiNet Standard Business Process Overview What the Standard Contains

farteaga
Download Presentation

papiNet from Top to Bottom

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. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. papiNet from Top to Bottom An introduction to papiNet

  2. Agenda • What is papiNet? • Charter • Organization • papiNet Goals • Implementation Status • Current and Planned Implementations • What Messages are Being Implemented? • papiNet Standard • Business Process Overview • What the Standard Contains • papiNet XML Benefits • Under the Covers • Interoperability • ISO 15000 (ebXML) • If we have time… • Documentation

  3. What is papiNet? papiNet Is… • An international paper and forest products industry e-business initiative. • A set of standard electronic documents that facilitates the flow of information among parties engaged in the buying, selling, and distribution of paper and forest products. • Enabler for collaborative electronic business using the internet.

  4. papiNet NA Membership papiNet Euro Membership Board Board What is papiNet? papiNet Organization papiNet Executive Committee Central Work Group Segment Implementation Groups Wood Products Label Stock Packaging Publication Papers

  5. What is papiNet?papiNet Goals • To increase efficiencies in transaction and marketplace activities through • documented business processes, with • Supporting standard XML messages, and • consistent data definitions, common terminology and formats • “real-time” exchange of information through the internet • To ensure that the standards are interoperable • Between trading partners in the paper and forest products industry. • Between trading partners in other industries • ebXML envelope • Engage other standards initiatives • To provide standards that are open and freely available

  6. Implementation StatusCurrent and Planned Implementations • Trading partner linkages in production and scheduled to be in production in the upcoming six months. • A link is defined as a from-to trading partner relationship for a given continent. • Companies who report using papiNet for internal communication are not included in this analysis, only their external linkage. • Besides the outstanding growth in production use this chart also illustrates the high degree conversion of planned implementation to actual use. • Our target for 2005 is 230 linkages. Short-Term Production

  7. Implementation StatusCurrent and Planned Implementations by Message Short-Term Production • Basic messages are used most frequently including Delivery Message, Purchase Order, Invoice, Order Confirmation, and Goods Receipt • There is still a long way to go on Basic messages before other messages will be implemented

  8. Implementation StatusProduction Use of Each Message • The most prevalently implemented message remains the Delivery Message followed by the Purchase Order, Order Confirmation, and Invoice.

  9. papiNet StandardJust what is the papiNet Standard? • Set of common electronic formats and terminology for the paper and forest products industry • Designed to facilitate application-to-application information exchange • Interoperability guidelines based on the ebXML message service specification (ISO 15000) • Designed to facilitate system-to-system information exchange • Stylesheets, currently through version 2.10 • Designed to facilitate human understanding of message content • Implementation Guidelines • Designed to facilitate rapid use • Case Studies (Business Scenarios) • Answers to common situations • Sample XML • What the XML would look like papiNet is not an eCommerce portal and there is no charge to use papiNet!

  10. Agreement Agreement Inventory Status (reel) Planning (Forecast) Planning (Production Plan) Delivery Goods Receipt Delivery Usage Agreement Planning (Forecast) Planning (Production Plan) Inventory Status (summary) Goods Receipt Usage papiNet StandardBusiness Process Overview Paper Producer The goal is to remove cost from the supply chain Invoice Publisher/ Cataloger Printer/ Converter

  11. papiNet StandardCollaboration Benefits • Simpler, cost effective and efficient business transactions using agreed-upon language • Increased data accuracy through less human intervention • Increased supply chain visibility • Less paper work

  12. papiNet StandardpapiNet and XML Benefits • International XML message standard • Common language for the industry • Easy to understand messages • Less errors due to schema and data-typing • Comprehensive messages for today’s and future processes • XML tools support • Generic XML tools provide support for more than just papiNet

  13. papiNet StandardTiming Your Migration to XML

  14. RFQ RFQ Response Goods Receipt Credit Debit Note Business Ack Usage Order Status Inventory Status Inventory Change Information Request Product Attributes Availability Planning Product Performance Product Quality Complaint Complaint Response Purchase Order Order Confirmation Call Off Delivery Message Invoice V1.1 V2.0 V2.1 V1.0 Schema June 2001 Release Feb 2002 Release August 2002 Release April 2003 Release papiNet StandardpapiNet Versions Complete the Set

  15. Message Message Message Common Definitions papiNet StandardBrief Review of our Structure • Messages have a very uniform structure with the common definitions contained in file that is shared amongst all the message schema files. • You can depend on a consistent definition regardless of where the element is used. Common definitions are shared amongst all the messages providing a consistent, universal approach and easy implementation.

  16. papiNet StandardA Bit More Detail

  17. papiNet StandardA Look at the XML Output • XML allows you to predefine and restrict choices for the content. In this case we’ve restricted the content to a predefined list of values. You can also: • Impose a constant format for dates • Define patterns to be applied

  18. Any Messenger Any Messenger ebXML envelope ebXML envelope Integration Information IntegrationInformation papiNet Document <PurchaseOrder> <Header> <LineItem> <Summary> papiNet Document <PurchaseOrder> <Header> <LineItem> <Summary> papiNet Document <PurchaseOrder> <Header> <LineItem> <Summary> papiNet Document <PurchaseOrder> <Header> <LineItem> <Summary> InteroperabilityA Standard Approach • ebXML is a UN/CEFACT and OASIS standard that has achieved ISO standard status (ISO 15000) • There are several distinct parts to the standard, papiNet has only formally accepted the Message Service and Collaboration (CPPA) aspects. • The ebXML Message Service Specification includes the definition of the envelope as well as how the Message Service should behave • The ebXML envelope acts as a common interface between systems • Your internal integration information will be used to determine how the ebXML envelope is used (when received) and how you will create the ebXML envelope (when sending). Sender Receiver ERP ERP

  19. Communications Protocol Envelope SOAP with Attachments MIME envelope Message Service Message Service SOAP-ebXML Envelope SOAP-ebXML Header SOAP-ebXML Body Payload Middleware Middleware The Net Firewall Firewall InteroperabilityThe papiNet Scope • papiNet Interoperability Guidelines are designed to assure that regardless of the messaging service used any trading partner can open a message (payload) sent to them.

  20. If we have time…Message Documentation

  21. If we have time…Business Scenarios

  22. If we have time…Data Dictionary

  23. If we have time…Data Dictionary

More Related