PIP 7B1 — Distribute Work in Process

RosettaNet choreography in cluster 7 (Manufacturing), covering the XML exchange between Manufacturer ↔ Customer. Operational unit for manufacturing on RNIF V02.00.

PIP purpose

PIP 7B1 distributes the progress of an in-process manufacturing run (Work in Process — WIP) between a manufacturer or an OSAT and its customer. Current step (Fab, Assembly, Test, Pack), yielded and scrapped quantities, estimated output dates. Key unit of semiconductor supply-chain visibility.

Message structure

The 7B1 choreography follows the one-action (notification) RosettaNet model:

Action: Distribute Work in Process 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-7B1.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>7B1</GlobalProcessIndicatorCode>
</ServiceHeader>

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

<!-- payload PIP 7B1 ci-dessus -->

--RN-BOUNDARY-2026--

Simplified XML example

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

xml pip-7B1.xml

<?xml version="1.0" encoding="UTF-8"?>
<Pip7B1DistributeWorkInProcess xmlns="http://www.rosettanet.org/PIP7B1">
  <fromRole>
    <PartnerRoleDescription>
      <GlobalPartnerRoleClassificationCode>Manufacturer</GlobalPartnerRoleClassificationCode>
    </PartnerRoleDescription>
  </fromRole>
  <toRole>
    <PartnerRoleDescription>
      <GlobalPartnerRoleClassificationCode>Customer</GlobalPartnerRoleClassificationCode>
    </PartnerRoleDescription>
  </toRole>
  <thisDocumentGenerationDateTime>
    <DateTimeStamp>20260515T101500Z</DateTimeStamp>
  </thisDocumentGenerationDateTime>
      <WorkInProcess>
        <WorkOrderIdentifier>
          <ProprietaryDocumentIdentifier>WO-2026-118277</ProprietaryDocumentIdentifier>
        </WorkOrderIdentifier>
        <productionStep>
          <GlobalProductionStepCode>WaferTest</GlobalProductionStepCode>
        </productionStep>
        <yieldedQuantity>
          <ProductQuantity>48800</ProductQuantity>
          <unitOfMeasure>EA</unitOfMeasure>
        </yieldedQuantity>
        <estimatedCompletionDate>
          <DateStamp>20260620</DateStamp>
        </estimatedCompletionDate>
      </WorkInProcess>
</Pip7B1DistributeWorkInProcess>

Transport and acknowledgment

Periodic emission (daily or intra-day), RNIF V02.00 over HTTPS POST or AS2. Potentially high volume (a lot can generate hundreds of WIP transitions per day).

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

TSMC distributes to AMD every evening the WIP status of lots manufactured for its orders. PIP 7B1 carries per lot: step (Fab, CP, Assembly, FT), yielded quantities, estimated completion date. AMD updates its master scheduler without manual inquiry.

Foundations

Standards

Flagship messages

Tools