PIP 7B6 — Distribute Work in Process Detail

RosettaNet choreography in cluster 7, transported on RNIF V02.00 and signed with S/MIME. Operational unit between ContractManufacturer and Manufacturer across the high-tech supply chain.

PIP purpose

PIP 7B6 distributes a Work in Process (WIP) detail at a granular level — lot, operation, machine, expected completion date. Detailed counterpart of PIP 7B1 which stays at an aggregate level.

Message structure

The 7B6 choreography follows the RosettaNet action model:

Primary action: Work in Process Detail Notification Action
Signal: Receipt Acknowledgment (RNIF)
Response action: Receipt Acknowledgment

The 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-7B6.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>7B6</GlobalProcessIndicatorCode>
</ServiceHeader>

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

<!-- PIP 7B6 payload above -->

--RN-BOUNDARY-2026--

Simplified XML example

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

xml pip-7B6.xml

<?xml version="1.0" encoding="UTF-8"?>
<Pip7B6WorkInProcessDetailNotification xmlns="http://www.rosettanet.org/PIP7B6">
  <fromRole>
    <PartnerRoleDescription>
      <GlobalPartnerRoleClassificationCode>ContractManufacturer</GlobalPartnerRoleClassificationCode>
    </PartnerRoleDescription>
  </fromRole>
  <toRole>
    <PartnerRoleDescription>
      <GlobalPartnerRoleClassificationCode>Manufacturer</GlobalPartnerRoleClassificationCode>
    </PartnerRoleDescription>
  </toRole>
  <thisDocumentGenerationDateTime>
    <DateTimeStamp>20260516T101500Z</DateTimeStamp>
  </thisDocumentGenerationDateTime>
    <WorkInProcessDetail>
      <reportIdentifier>
        <ProprietaryDocumentIdentifier>WIP-DETAIL-2026-138</ProprietaryDocumentIdentifier>
      </reportIdentifier>
      <reportPeriod><DateStamp>20260516</DateStamp></reportPeriod>
      <WorkInProcessLineItem>
        <lotIdentifier>LOT-2026-A29-014</lotIdentifier>
        <ProductIdentification>
          <GlobalProductIdentifier>00614141777771</GlobalProductIdentifier>
        </ProductIdentification>
        <currentOperation>WireBond</currentOperation>
        <expectedCompletionDate><DateStamp>20260520</DateStamp></expectedCompletionDate>
        <quantityInProcess>2000</quantityInProcess>
      </WorkInProcessLineItem>
    </WorkInProcessDetail>
</Pip7B6WorkInProcessDetailNotification>

Transport and acknowledgment

Core of the standard: HTTPS POST to the partner endpoint or via AS2. S/MIME signature and Receipt Acknowledgment are systematic. PIP 7B6 is typically transported asynchronously.

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

ASE Group distributes to TSMC via PIP 7B6 a detail of the 47 WIP lots in assembly: for each lot, current operation (probe, dice, attach, wire bond, encapsulation) and expected completion date.

Foundations

Standards

Flagship messages

Tools