papiNet Is…

Download Report

Transcript papiNet Is…

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
papiNet XML Benefits
Under the Covers
• Interoperability
- ISO 15000 (ebXML)
• If we have time…
- Documentation
2
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.
3
What is papiNet?
papiNet Executive
Committee
Segment
Implementation
Groups
Publication
Papers
4
Board
papiNet NA
Membership
Board
papiNet Organization
papiNet Euro
Membership
Central Work
Group
Packaging
Wood Products
Label Stock
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
5
Implementation Status
Current 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.
Trading Partner Linkages
300
250
107
200
150
100
50
61
34
69
150
103
0
2002 Q3
2003 Q2
2004 Q1
Short-Term
- Our target for 2005 is 230 linkages.
Production
6
Implementation Status
Current 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
7
Implementation Status
Production Use of Each Message
• The most prevalently implemented message remains the Delivery
Message followed by the Purchase Order, Order Confirmation, and
Invoice.
8
papiNet Standard
Just 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
9
papiNet Standard
Business Process Overview
Paper
Producer
The goal is to
remove cost
from the supply
chain
Publisher/
Cataloger
10
Agreement
Planning (Forecast)
Planning (Production Plan)
Inventory Status (summary)
Goods Receipt
Usage
Printer/
Converter
papiNet Standard
Collaboration 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
11
papiNet Standard
papiNet 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
12
papiNet Standard
Timing Your Migration to XML
13
papiNet Standard
papiNet Versions Complete the Set
Purchase Order
RFQ
Usage
Availability
Order Confirmation
RFQ Response
Order Status
Planning
Call Off
Goods Receipt
Inventory Status
Product Performance
Delivery Message
Credit Debit Note
Inventory Change
Product Quality
Invoice
Business Ack
Information Request
Complaint
Product Attributes
Complaint Response
14
V1.0
V1.1
V2.0
V2.1
June 2001
Feb 2002
August 2002
April 2003
Release
Release
Release
Release
papiNet Standard
Brief Review of our Structure
Messages have a very uniform structure
with the common definitions contained
in file that is shared amongst all the
Message
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.
15
Message
Common
Definitions
Message
papiNet Standard
A Bit More Detail
16
papiNet Standard
A 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
17
Interoperability
A 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).
ERP
Sender
Integration
Information
papiNet Document
<PurchaseOrder>
<Header>
<LineItem>
<Summary>
18
Any Messenger
Any Messenger
ebXML
envelope
ebXML
envelope
papiNet Document
papiNet Document
<PurchaseOrder>
<Header>
<LineItem>
<Summary>
<PurchaseOrder>
<Header>
<LineItem>
<Summary>
Receiver
Integration
Information
papiNet Document
<PurchaseOrder>
<Header>
<LineItem>
<Summary>
ERP
Interoperability
The 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.
Communications Protocol Envelope
SOAP with Attachments MIME envelope
Message
Service
SOAP-ebXML Envelope
Message
Service
SOAP-ebXML Header
SOAP-ebXML Body
Payload
Middleware
Firewall
19
The
Net
Middleware
Firewall
If we have time…
Message Documentation
20
If we have time…
Business Scenarios
21
If we have time…
Data Dictionary
22
If we have time…
Data Dictionary
23