PIP 4A1 — Notify of Strategic 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 4A1 distributes a long-term demand forecast (typically 6 to 18 months) between a buyer and its strategic supplier. It is the high-frequency counterpart of EDIFACT DELFOR, central to semiconductor S&OP (Sales & Operations Planning) loops.

Message structure

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

Action: Notify of Strategic 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-4A1.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>4A1</GlobalProcessIndicatorCode>
</ServiceHeader>

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

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

--RN-BOUNDARY-2026--

Simplified XML example

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

xml pip-4A1.xml

<?xml version="1.0" encoding="UTF-8"?>
<Pip4A1NotifyOfStrategicForecast xmlns="http://www.rosettanet.org/PIP4A1">
  <fromRole>
    <PartnerRoleDescription>
      <GlobalPartnerRoleClassificationCode>Buyer</GlobalPartnerRoleClassificationCode>
    </PartnerRoleDescription>
  </fromRole>
  <toRole>
    <PartnerRoleDescription>
      <GlobalPartnerRoleClassificationCode>Seller</GlobalPartnerRoleClassificationCode>
    </PartnerRoleDescription>
  </toRole>
  <thisDocumentGenerationDateTime>
    <DateTimeStamp>20260515T101500Z</DateTimeStamp>
  </thisDocumentGenerationDateTime>
      <StrategicForecast>
        <ForecastIdentifier>
          <ProprietaryDocumentIdentifier>FCST-2026-Q3</ProprietaryDocumentIdentifier>
        </ForecastIdentifier>
        <ProductLineItem>
          <ProductIdentification>
            <GlobalProductIdentifier>00614141999996</GlobalProductIdentifier>
          </ProductIdentification>
          <ForecastPeriod>
            <startDate><DateStamp>20260801</DateStamp></startDate>
            <endDate><DateStamp>20261031</DateStamp></endDate>
          </ForecastPeriod>
          <forecastedQuantity>
            <ProductQuantity>150000</ProductQuantity>
            <unitOfMeasure>EA</unitOfMeasure>
          </forecastedQuantity>
        </ProductLineItem>
      </StrategicForecast>
</Pip4A1NotifyOfStrategicForecast>

Transport and acknowledgment

Periodic emission (monthly or weekly), RNIF V02.00 over HTTPS POST or AS2. Often duplicated by an Excel / REST API share for human planning teams.

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 shares with its Taiwanese foundry a Q3 2026 quarterly forecast: 150,000 wafers over three months, segmented by MPN. PIP 4A1 feeds the foundry capacity planning without direct contractual commitment.

Foundations

Standards

Flagship messages

Tools