PIP 3B12 — Request Shipping Order

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

PIP purpose

PIP 3B12 books transport with a carrier (FedEx, UPS, DHL, maritime carriers): pickup, destination, content, additional services (insurance, signature, refrigerated). The carrier confirms with a PIP 3B12 confirmation including the tracking number.

Message structure

The 3B12 choreography follows the two-action (request / response) RosettaNet model:

Primary action: Shipping Order Request Action
Signal: Receipt Acknowledgment
Response action: Shipping Order Confirmation Action

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-3B12.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>3B12</GlobalProcessIndicatorCode>
</ServiceHeader>

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

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

--RN-BOUNDARY-2026--

Simplified XML example

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

xml pip-3B12.xml

<?xml version="1.0" encoding="UTF-8"?>
<Pip3B12ShippingOrderRequest xmlns="http://www.rosettanet.org/PIP3B12">
  <fromRole>
    <PartnerRoleDescription>
      <GlobalPartnerRoleClassificationCode>Shipper</GlobalPartnerRoleClassificationCode>
    </PartnerRoleDescription>
  </fromRole>
  <toRole>
    <PartnerRoleDescription>
      <GlobalPartnerRoleClassificationCode>Carrier</GlobalPartnerRoleClassificationCode>
    </PartnerRoleDescription>
  </toRole>
  <thisDocumentGenerationDateTime>
    <DateTimeStamp>20260515T101500Z</DateTimeStamp>
  </thisDocumentGenerationDateTime>
      <ShippingOrder>
        <ShippingOrderIdentifier>
          <ProprietaryDocumentIdentifier>SO-2026-007761</ProprietaryDocumentIdentifier>
        </ShippingOrderIdentifier>
        <PickupLocation>
          <City><FreeFormText>Hsinchu</FreeFormText></City>
        </PickupLocation>
        <DeliveryLocation>
          <City><FreeFormText>Austin</FreeFormText></City>
        </DeliveryLocation>
        <ServiceLevel>
          <GlobalServiceLevelCode>Express</GlobalServiceLevelCode>
        </ServiceLevel>
      </ShippingOrder>
</Pip3B12ShippingOrderRequest>

Transport and acknowledgment

Synchronous or asynchronous cycle, RNIF V02.00 over HTTPS POST or AS2. Often paired with a carrier REST API for real-time tracking.

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 Taiwanese foundry books express transport Hsinchu → Austin for five wafer containers via FedEx. PIP 3B12 pre-books the slot; the PIP 3B12 confirmation response returns the tracking number that will later feed PIP 3B3.

Foundations

Standards

Flagship messages

Tools