Untitled Document

An Introduction

Partner Interface Process (PIPs™)

PIP Is the heart of RosettaNet Standard and a key differentiator

How PIPs Look Like:
Categorizes by high-level business functions called CLUSTERS and sub-functions known as SEGMENTS
[View example]

What PIPs Do:
Define business processes (public) between trading partners. They encapsulate business processes, specify structure and format of business document payloads,

and specify activities, decisions, interactions and roles for each trading partner involved. It enables trading partners to extend their proprietary private processes using RosettaNet PIPs [View example]

Two different type of PIPs:
Document Type Definition (DTD) based PIPs also known as Monolithic PIPs (Version 01.xx.xx specifies it is a DTD version)
XML Schema based PIPs also known as Modular (Version 11.xx.xx specifies it is a XML Schema version)

How PIPs Work:
Importantly, the PIP is supported by a robust framework of Dictionaries, Product & Partner Codes, and an implementation framework. [View example]

.

Dictionaries

RosettaNet Dictionaries provide a common set of properties for PIP™s & designates the properties used in basic business activities

It ensure consitent information exchange for partner identification and product identification during PIP™ execution.

RosettaNet Technical Dictionary [Form, Fit, Function]
It specifies common product properties

RosettaNet Business Dictionary
It specifies common partner properties
It enables partners to identify one another

RosettaNet Implementation Framework

RosettaNet Implementation Framework (RNIF) is an open, common networked-application framework that defines RosettaNet Object (RNO).

It provides common exchange protocols that enable the implementation of PIP™ thru speifying how to transport RosettaNet Object between trading partners' network applications

RNIF Version 2.0 Features and Benefits
HTTP and SMTP transfer protocols better support for e-marketplaces
Support for sending complext documents such as .pdf, .gif files
Support for S/MIME v.2 which provide greater security, privacy and authentication