PIP 3B3 — Distribute Shipment Status

RosettaNet choreography in cluster 3 (Order Management — Shipment), covering the XML exchange between Carrier ↔ Receiver. Operational unit for order management — shipment on RNIF V02.00.

PIP purpose

PIP 3B3 distributes the transit status of a shipment by the carrier or a 3PL operator: milestones (Picked up, In transit, Customs cleared, Out for delivery, Delivered), with exception weighting (delay, suspected damage).

Message structure

The 3B3 choreography follows the one-action (notification) RosettaNet model:

Action: Distribute Shipment Status 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-3B3.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>3B3</GlobalProcessIndicatorCode>
</ServiceHeader>

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

<!-- payload PIP 3B3 ci-dessus -->

--RN-BOUNDARY-2026--

Simplified XML example

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

xml pip-3B3.xml

<?xml version="1.0" encoding="UTF-8"?>
<Pip3B3DistributeShipmentStatus xmlns="http://www.rosettanet.org/PIP3B3">
  <fromRole>
    <PartnerRoleDescription>
      <GlobalPartnerRoleClassificationCode>Carrier</GlobalPartnerRoleClassificationCode>
    </PartnerRoleDescription>
  </fromRole>
  <toRole>
    <PartnerRoleDescription>
      <GlobalPartnerRoleClassificationCode>Receiver</GlobalPartnerRoleClassificationCode>
    </PartnerRoleDescription>
  </toRole>
  <thisDocumentGenerationDateTime>
    <DateTimeStamp>20260515T101500Z</DateTimeStamp>
  </thisDocumentGenerationDateTime>
      <ShipmentStatus>
        <ShipmentIdentifier>
          <ProprietaryDocumentIdentifier>ASN-2026-019823</ProprietaryDocumentIdentifier>
        </ShipmentIdentifier>
        <GlobalShipmentStatusCode>InTransit</GlobalShipmentStatusCode>
        <statusDateTime>
          <DateTimeStamp>20260711T084500Z</DateTimeStamp>
        </statusDateTime>
        <LocationInformation>
          <City><FreeFormText>Singapore</FreeFormText></City>
        </LocationInformation>
      </ShipmentStatus>
</Pip3B3DistributeShipmentStatus>

Transport and acknowledgment

Asynchronous push, RNIF V02.00 over HTTPS POST or AS2. Often multi-recipient: the same PIP 3B3 is routed in parallel to buyer, insurer, visibility provider.

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

A carrier distributes to several partners (buyer, insurer, 3PL) the passage in international transit of a wafer container in Singapore. PIP 3B3 unifies the event and synchronises downstream ERPs.

Foundations

Standards

Flagship messages

Tools