Home Forum RosettaNet Primer
   
PDF Print E-mail

 

 

TABLE OF CONTENTS

What is RosettaNet?

What eBusiness standards does RosettaNet publish?

What is a RosettaNet Partner Interface Process (PIP)?

What is a RosettaNet Implementation Guide (RIG)?

What is RosettaNet Automated Enablement (RAE)?

What do I need to implement RosettaNet?

What is the RosettaNet Standards Methodology (RSM)?

Where can I learn more about RosettaNet?




 

RosettaNet Primer

Part 2: What eBusiness standards does RosettaNet publish?

B2B Process Standards

B2B process standards specify how a business-process workflow and collaboration is managed across two or more companies, commonly referred to as trading partners (TPs).

Partner Interface Process (PIP)

The RosettaNet Partner Interface Process® (PIP®) is a standards package specifying both ebusiness information and process flow.  PIPs are typically the first RosettaNet standard discussed when companies begin using RosettaNet for B2B processing. Each PIP defines a very specific ebusiness process and the document(s) that are exchanged between trading partners.

Over 75 PIPs have been published covering a wide range of ebusiness processes.

For more information about the RosettaNet PIP, view RosettaNet Primer Part 3.

B2B Vocabulary Standards

B2B vocabulary standards specify the information that is required for each business transaction.

PIP Business Documents

Each Partner Interface Process (PIP) specification includes either one or two PIP Business Documents.  This is the portion of the PIP that describes the structured business information that is exchanged between trading partners.

RosettaNet Business Dictionary (RNBD)

The RosettaNet Business Dictionary is a standardized terminology dictionary.  All business terms used the PIP Business Documents are clearly defined in the RNBD.

The RNBD is not a single, consolidated static document.  The complete set of RNBD data elements are maintained in the RosettaNet engineering environment.  The specific terms used in an individual PIP will be included in the PIP’s own RNBD section included within the Message Guidelines file.

RosettaNet Technical Dictionary (RNTD)

The RosettaNet Technical Dictionary is a standardized characteristic dictionary.  The terms included in the RNTD provide an informational structure along with detailed definitions used for describing a wide range of items in a standardized way.  The RNTD specifies hundreds of properties helping the RosettaNet community efficiently describe complex products.

B2B Technology Standards

B2B technology standards define how to code, secure and exchange information between companies.  These standards are used by software engineers developing and implementing B2B solutions.

RosettaNet Implementation Framework: Core Specification (RNIF)

The RosettaNet Implementation Framework defines how to securely exchange ebusiness information across the internet. The RNIF Core Specification applies many proven technology standards along with some RosettaNet unique standards to automate ebusiness processes.

RNIF 1.1 was first published in 1999 when the Internet was beginning to replace telephone lines as the primary B2B messaging pathway.  In 2001, RNIF 2.0 was published to include additional messaging features such as an ability to send file attachments as part of a PIP.

RNIF 2.0 is NOT backwards compatible with RNIF 1.1.  Trading partners must use the same RNIF version for exchanging PIP Business Documents.

Multiple Messaging Services (MMS) Profiles for AS2, ebMS, and Web Services

The RosettaNet Multiple Messaging Services (MMS) standards specify how to exchange PIP Business Documents (PIPs) using standards other than RNIF.

MMS Specifications describe how to exchange Partner Interface Processes (PIPs) using these popular messaging platforms:

AS2 - MIME-Based Secure Peer-to-Peer Business Data Interchange using HTTP, Applicability Statement 2 (AS2) is published by ISOC and approved as an IETF standard.

ebMS - ebXML Message Service Specification is published by OASIS

Web Services includes a set of specifications published by OASIS, W3C and WSI.

Trading Partner Implementation Requirements (TPIR)

RosettaNet recognizes that each company must adapt PIP specifications for their individual processes and trading network.  The Trading Partner Implementation Requirements for a PIP (TPIR-PIP) details the rules describing how the community-agreed PIP can be simplified by reducing (constraining) the PIP to include only the data elements required for the process.  The TPIR-PIP specifications are used to create a smaller PIP that follows all the rules (compliant). The TPIR-PIP is a machine-readable specification that supports individual company needs.

There are currently four different TPIR specifications:

TPIR-PIP Design Specifications to constrain a single PIP to include only a subset of optional data elements.

TPIR-PIP for Engineering Information to constrain a PIP and to add Engineering Information Property Sets (EIPS)

TPIR-PF Core Specifications for presentation format used to create PIP-based forms for manual data entry.

TPIR-Registry Interface for making TPIR-PIPs available through a structured registry for automated distribution and updates of TPIR-PIPs and TPIR-PFs.

For more information about the RosettaNet TPIR’s, view RosettaNet Primer Part 5.

Engineering Information Management (EIM)

The RosettaNet Engineering Information Management specifications are used to effectively exchange complex product information supporting different engineering processes.  EIM processes use selected PIPs along with the RosettaNet Technical Dictionary (RNTD) specification.

Four RosettaNet Partner Interface Processes are used to support Engineering Information Management:

PIP 2A9 - Query Technical Product Information

PIP 2A10 - Distribute Design Engineering Information

PIP 2A12 - Distribute Product Master

PIP 2A16 - Distribute Engineering Information Inquiry

EIM standards include:

RosettaNet EIPS XSD Specifications to create standardized Engineering Information Property Sets (EIPS)

TPIR-PIP for Engineering Information to constrain a PIP and to add Engineering Information Property Sets (EIPS)

Using the EIPS XSD Specification, new Vocabulary Standards will be created called Engineering Information Property Sets (EIPS) specifying a pre-structured set of properties used for describing common products.  Using EIPS will simplify implementation efforts by creating common subsets of the total RNTD for describing engineering information.  The EIPS are in development and therefore specific EIPS vocabulary standards are not currently available.

   
Last Updated on Monday, 27 July 2009 15:01