PIP 2A1 — Distribute New Product Information

RosettaNet choreography in cluster 2 (Product Introduction), covering the XML exchange between Product Information Provider ↔ Product Information Receiver. Operational unit for product introduction on RNIF V02.00.

PIP purpose

PIP 2A1 distributes a new or updated product datasheet in push mode between a manufacturer and its distribution partners. It carries the product identification block (GTIN, MPN — Manufacturer Part Number), classification, technical attributes, availability dates, and lifecycle status.

Message structure

The 2A1 choreography follows the one-action (notification) RosettaNet model:

Action: Distribute New Product Information Action
Signal: Receipt Acknowledgment

Each action is wrapped in a multipart MIME RNIF V02.00 envelope signed with S/MIME. Here is a condensed view of the envelope:

text rnif-envelope-2A1.eml

MIME-Version: 1.0
Content-Type: multipart/related; type="application/xml";
  boundary="RN-BOUNDARY-2026"

--RN-BOUNDARY-2026
Content-Type: application/xml
Content-Location: RN-Preamble.xml

<Preamble xmlns="http://www.rosettanet.org/RNIF/V02.00">
  <standardName>RosettaNet</standardName>
  <standardVersion>V02.00</standardVersion>
</Preamble>

--RN-BOUNDARY-2026
Content-Type: application/xml
Content-Location: RN-ServiceHeader.xml

<ServiceHeader xmlns="http://www.rosettanet.org/RNIF/V02.00">
  <GlobalProcessIndicatorCode>2A1</GlobalProcessIndicatorCode>
</ServiceHeader>

--RN-BOUNDARY-2026
Content-Type: application/xml
Content-Location: Pip2A1DistributeNewProductInformation.xml

<!-- payload PIP 2A1 ci-dessus -->

--RN-BOUNDARY-2026--

Simplified XML example

Minimal PIP 2A1 payload for didactic purposes. The structural elements (fromRole, toRole, thisDocumentGenerationDateTime, and the PIP-specific business block) are required in any conformant implementation.

xml pip-2A1.xml

<?xml version="1.0" encoding="UTF-8"?>
<Pip2A1DistributeNewProductInformation xmlns="http://www.rosettanet.org/PIP2A1">
  <fromRole>
    <PartnerRoleDescription>
      <GlobalPartnerRoleClassificationCode>ProductInformationProvider</GlobalPartnerRoleClassificationCode>
    </PartnerRoleDescription>
  </fromRole>
  <toRole>
    <PartnerRoleDescription>
      <GlobalPartnerRoleClassificationCode>ProductInformationReceiver</GlobalPartnerRoleClassificationCode>
    </PartnerRoleDescription>
  </toRole>
  <thisDocumentGenerationDateTime>
    <DateTimeStamp>20260515T101500Z</DateTimeStamp>
  </thisDocumentGenerationDateTime>
      <ProductInformation>
        <ProductIdentification>
          <GlobalProductIdentifier>00614141000017</GlobalProductIdentifier>
          <ProprietaryProductIdentifier>INTEL-XEON-6928P</ProprietaryProductIdentifier>
        </ProductIdentification>
        <ProductLifeCycleStatus>
          <GlobalProductLifeCycleStatusCode>Active</GlobalProductLifeCycleStatusCode>
        </ProductLifeCycleStatus>
        <ProductDescription>
          <FreeFormText>Xeon 6 P-core, 72-core, 350W TDP</FreeFormText>
        </ProductDescription>
      </ProductInformation>
</Pip2A1DistributeNewProductInformation>

Transport and acknowledgment

RNIF V02.00 over HTTPS POST or AS2, mandatory S/MIME signature (the product datasheet is legally binding on the manufacturer side).

The transport channel is typically AS2 or direct HTTPS (RNIF over HTTP). For a reference of the security layers in use, see the AS2 on ediverse page.

Use case

Intel publishes a new Xeon family. It pushes via PIP 2A1 to its authorised distributors (Arrow, Avnet, WPG) the full datasheet: MPN, GTIN, package, TDP, lifecycle status, introduction date. Distributors sync their PIMs within hours, with no manual intervention.

Foundations

Standards

Flagship messages

Tools