PIP 4A3 — Notify of Threshold Release Forecast

RosettaNet choreography in cluster 4 (Inventory Management), covering the XML exchange between Buyer ↔ Seller. Operational unit for inventory management on RNIF V02.00.

PIP purpose

PIP 4A3 is a short-term threshold-triggered forecast: the buyer defines a minimum stock threshold under which automatic replenishment is triggered. The seller can anticipate the order without waiting for a formal PO — the basis of high-tech VMI (Vendor Managed Inventory) models.

Message structure

The 4A3 choreography follows the one-action (notification) RosettaNet model:

Action: Notify of Threshold Release Forecast 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-4A3.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>4A3</GlobalProcessIndicatorCode>
</ServiceHeader>

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

<!-- payload PIP 4A3 ci-dessus -->

--RN-BOUNDARY-2026--

Simplified XML example

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

xml pip-4A3.xml

<?xml version="1.0" encoding="UTF-8"?>
<Pip4A3NotifyOfThresholdReleaseForecast xmlns="http://www.rosettanet.org/PIP4A3">
  <fromRole>
    <PartnerRoleDescription>
      <GlobalPartnerRoleClassificationCode>Buyer</GlobalPartnerRoleClassificationCode>
    </PartnerRoleDescription>
  </fromRole>
  <toRole>
    <PartnerRoleDescription>
      <GlobalPartnerRoleClassificationCode>Seller</GlobalPartnerRoleClassificationCode>
    </PartnerRoleDescription>
  </toRole>
  <thisDocumentGenerationDateTime>
    <DateTimeStamp>20260515T101500Z</DateTimeStamp>
  </thisDocumentGenerationDateTime>
      <ThresholdReleaseForecast>
        <ForecastIdentifier>
          <ProprietaryDocumentIdentifier>THR-2026-W21</ProprietaryDocumentIdentifier>
        </ForecastIdentifier>
        <ProductLineItem>
          <ProductIdentification>
            <GlobalProductIdentifier>00614141999996</GlobalProductIdentifier>
          </ProductIdentification>
          <currentInventoryLevel>
            <ProductQuantity>3200</ProductQuantity>
            <unitOfMeasure>EA</unitOfMeasure>
          </currentInventoryLevel>
          <reorderThreshold>
            <ProductQuantity>5000</ProductQuantity>
            <unitOfMeasure>EA</unitOfMeasure>
          </reorderThreshold>
        </ProductLineItem>
      </ThresholdReleaseForecast>
</Pip4A3NotifyOfThresholdReleaseForecast>

Transport and acknowledgment

Event-driven emission, RNIF V02.00 over HTTPS POST or AS2. Paired with a PIP 4A1 for the long-term strategic context.

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

An OEM operates a VMI program on a few critical MPNs. When the under-threshold warehouse stock falls below 5,000 units (at 3,200 here), a PIP 4A3 is generated; the distributor can mirror-trigger a replenishment to 5,000 or more, without an intermediate formal PO.

Foundations

Standards

Flagship messages

Tools