papiNet® is a global paper, forest products and bioproducts industry e-Business initiative. papiNet consists of an XML set of standard electronic documents that facilitates the flow of information among parties engaged in buying, selling, and distribution of paper, forest and bio related products. papiNet serves as an enabler for collaborative electronic business.

 

 

 

 

 

papiNet is a joint effort supported by papiNet Europe, a consortium of European paper and forest products companies, and papiNet NA, a group of North American paper and forest products companies, distributors, printers, and customers.

papiNet Europe

papiNet started as a project within the Publishing part of the paper industry. A number of major paper suppliers, large German publishers and printers worked together to create a common standard for electronic business transactions. Soon there was a requirement to develop supporting software for handling the transactions via the Internet. This work turned out so well, that it was decided to enlarge the pilot project to encompass other parts of the industry.

American Forest & Paper Association

The American Forest & Paper Association (AF&PA) is the national trade association in the United States of the forest, paper, and wood products industry. AF&PA members include manufacturers of over 80 percent of the paper, wood and forest products produced in the United States. AF&PA acts as the clearinghouse for statistical information, as the leading force in technical, regulatory and policy issues, and as the national voice for the forestry, wood, and paper industries. More information about the AF&PA can be found at www.afandpa.org.

IDEAlliance was also a founding organization of papiNet NA. About 2019, IDEAlliance was integrated into Printing United Association. At that time, IDEAlliance/Printing United Association no longer are participants in the papNet organization.

 

 

 

 

 

 

 

 

 

 

It‘s important to understand that papiNet is simply a specification for a standard method for communication. It is not in itself a database, a software application, or a product or service that you can purchase.

The specification and associated documents are available and usable without charge. It is freely available on www.papinet.org.

The benefits of membership in papiNet are significant. Participation in the Segment Implementation Groups is a key benefit and you would be missing out on some very helpful tools. Joining papiNet saves you time and money and allows you to better spend your time as you are not reinventing the wheel.

 

It‘s important to understand that papiNet is simply a specification for a standard method for communication. It is not in itself a database, a software application, system, or a product or service that you can purchase.

The specification and associated documents are available and usable without charge. It is freely available on www.papinet.org.

 

 

 

 

 

 

papiNet was developed for the paper, forest and bio related products industry. The standard could be utilized in other industries however in its current state if those industries identify their products or services with an identifier. papiNet would consider expanding the specification to include new product characteristics and specifications. If you are interested, please use the Contact” tab on www.papinet.org home page

You have the prospect for influencing the standard whether you are a member or not. We pay attention to the feedback that is provided by members and non-members. Additionally, we truly are interested in the penetration of the papiNet standard throughout the entire paper and forest products supply chain.

If you are interested in becoming a member, please use the CONTACT tab on www.papinet.org home page.

 

 

 

 

The User Groups are made up of participants that represent the geographic and specific market segment within the paper, forest and bio products industry.

The UGs provide assistance implementing the standard, implementation groups within the business areas of the industry have been formed. Their mission is to agree upon the general business rules, processes and then a suggested implementation (a reference implementation that can be used as a template) of the standard that is applicable for the particular segment.

If you are interested in becoming a member or merely would like to obtain more information on a particular User Group, please use the CONTACT link on each of the User Group home pages under INFO on the right hand side of the page. Each of the User Group home pages may be accessed from www.papinet.org home page.

 

Have a look at our ROI spreadsheet to help quantify the benefits. The papiNet standard enables the following benefits:

• Accurate data
• Reduce transactional costs
• Consistent information througout the supply chain
• Interact between business partners in an uniform manner
• Support for change reuests due to business needs
• Simplify the process for dealing with multiple suppliers and customers through use of common business solutions
• Reduced manual work, resulting in fewer entry errors and improved supplychain management (e.g. replenishment, VMI)
• Real-time exchange of information and greater electronic information availability
• Everyone can participate in e-business transactions, irrespective of company size or technical expertise.

 

The use of a QR code is a simple and easy way to exchange B2B information without computer to computer connection. papiNet has created a  version of a schema defining the content of a papiNet QR code. papiNet will define QR codes for various Use Cases by adding their contents to the papiNet QR schema. Currently a QR code (DMM) is defined for supplying information to a Measuring Party based on the DeliveryMessage.

Additional information may be obtained by dowloading the QR Documentation from  www.papinet.org -> The Standard -> Download Current Version -> QR -> Documentation link

 

 

 

 

 

 

papiNet has achieved its initial charter, to deliver e-documents supporting the full supply chain. Our efforts now are to ensure that the standard is implemented and to enable market segments to fully support their business requirements. We currently are publishing a new build of the current release on a bi-annual basis.

Changes arrive from a variety of sources. As papiNet is an open standard anyone can submit a request to improve the standard. Changes are categorized, organized, and reviewed by the papiNet CWG Change Control Group. This group meets minimally twice annual but has the flexibility to meet as often as required.

Most often, changes are submitted by the papiNet User Groups because these are the market specific segments participants working with and implementing the standard. Those not currently engaged within one of these User Groups, may submit a change request via www.papinet.org -> The Standard -> Questions or Requests link.

 

 

 

 

 

The current version the papiNet standard is V2.40 if using Namespace and V2.31 if using non-Namespace.   These version are backward compatible to V2.0. They are not backward compatible to any release of V1.  Any subsequent publication of updates will contine to be applied to V2.31 and V2.40 in the form of new build dates. There are currently no plans to upgrade the standard to a version 3.

A papiNet e-Document is an electronic business document that can be processed by computers as well as read by human beings or printed after applying a stylesheet

 

 

 

 

 

The papiNet standard supports e-Documents needed in a business supply chain, for example from a Request For Quotation to an Invoice. Currently there are 40+ different e-Documents.  All papiNet e-Documents are listed on www.papinet.org -> The Standard -> Download Current Version -> V2R31 non-namespaced version -> Documentation link.

Documentation of papiNet e-Documents can be downloaded from www.papinet.org -> The Standard -> Download Current Version -> V2R31 non-namespaced version -> Documentation link. There is documentation describing each e-Document as well as a Data Dictionary with definitions of all items in the e-Documents.

 

 

 

 

 

 

Sample e-Documents can be found in use cases documented by the papiNet User Groups. The use cases are published on the User Group home pages on www.papinet.org.

Yes, papiNet User Groups have documented use cases. The use cases are published on the User Group home pages on www.papinet.org.

Do I need to include all elements listed in a papiNet e-Document?

No, papiNet User Groups have worked out subsets fulfilling the needs for their market segments. The content of the e-Documents vary by the use cases. Use cases documented by the User Groups are published on the User Group home pages on www.papinet.org.

 

 

 

 

 

No, papiNet User Groups have worked out subsets fulfilling the needs for their market segments. The content of the e-Documents vary by the use cases. Use cases documented by the User Groups are published on the User Group home pages on www.papinet.org.

 

papiNet Central Work Group is responsible for maintaining the standard. Change requests for improving the standard are coming from member companies of the User Groups and other companies implementing papiNet. The User Groups review change requests for their market segments and give recommendations to the Central Work Group. The Central Work Group harmonises change requests across User Groups and decides what to add to the standard.

 

 

 

 

 

There is documentation describing each papiNet e-Document. Definitions of all items in the papiNet standard are listed in a Data Dictionary.

Documentation can be downloaded from www.papinet.org -> The Standard -> Download Current Version -> V2R31 non-namespaced version -> Documentation link.

The User Groups have documented use cases and business rules as well as other helpful material.   

User Group documentation can be downloaded from the User Group home pages on www.papinet.org.

 

 

To use the papiNet XML files, your IT system must have

• capability to send and receive xml files over a telecommunications network
• software to handle information contained in the xml files so that it can be made available in the IT systems implemented to support your business processes

 

More information about xml can be found here 

 

o   https://en.wikipedia.org/wiki/XML

 

o   http://www.w3schools.com/xml/

 

 

It is not possible to estimate cost or duration of implementations in general.

Cost and duration depend on what information exchange between IT systems and.or organizations you want to automate using papiNet. Implementation projects vary from exchanging information using one papiNet e-Document to orchestrating an integration solution that requires the exchange of several papiNet e-Documents.

 

 

 

 

 

 

Yes, papiNet has published an implementation guide.  It is available for download under Materials->papiNet Tools->Implementation Guide

 

 

 

 

 

 papiNet advises to use the latest version & build available.

You need to consider if you need the namespace or non-namespace version of the schemas

 

 Any communication method can be used to communicate papiNet e-Documents.

Some examples include FTP, AS/2, via a VAN, HTTP and others

 

 

 

 

To validate that your e-Document is valid you can check it against the papiNet xsd schema definition 

 

 

 

 

 

 

 

 

 

 You do not need to use the papiNet Envelope. However, it is recommended that it is always used as this makes it possible to clearly define the technical aspects of communicating the e-Document.

The papiNet Envelope also facilitates sending attachments with the papiNet e-Document.

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 Using the papiNet Envelope as part of your solution will facilitate sending attachments with the papiNet e-Document.

 

 

 

 

 

 

 

 

 In some cases, papiNet has defined pairs of e-Documents to support this. For example

• PurchaseOrder & OrderConfirmation

In other scenarios, papiNet has defined two e-Documents to facilitate this functionality

• BusinessAcceptance, to enable the receiver to reply with a technical confirmation that the e-Documet has been received
• BusinessAcknowledgement, to enable replying with a confirmation that the e-Document has been received into the receiver's business IT system
  

 

 

 

Documentation of the papiNet e-Documents describe some typical use cases.

PapiNet has also documented use case descriptions for specific business areas.

These can be located on the User Group pages with www.papinet.org

 

 

 

-