PIP 6C2 — Distribute Manufacturing Status

RosettaNet choreography in cluster 6, 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 6C2 distributes a consolidated manufacturing status from EMS to manufacturer: WIP lots, completed lots, yield rate, material shortages. Core MES-level cross-enterprise visibility building block.

Message structure

The 6C2 choreography follows the RosettaNet action model:

Primary action: Manufacturing Status 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-6C2.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>6C2</GlobalProcessIndicatorCode>
</ServiceHeader>

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

<!-- PIP 6C2 payload above -->

--RN-BOUNDARY-2026--

Simplified XML example

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

xml pip-6C2.xml

<?xml version="1.0" encoding="UTF-8"?>
<Pip6C2ManufacturingStatusNotification xmlns="http://www.rosettanet.org/PIP6C2">
  <fromRole>
    <PartnerRoleDescription>
      <GlobalPartnerRoleClassificationCode>ContractManufacturer</GlobalPartnerRoleClassificationCode>
    </PartnerRoleDescription>
  </fromRole>
  <toRole>
    <PartnerRoleDescription>
      <GlobalPartnerRoleClassificationCode>Manufacturer</GlobalPartnerRoleClassificationCode>
    </PartnerRoleDescription>
  </toRole>
  <thisDocumentGenerationDateTime>
    <DateTimeStamp>20260516T101500Z</DateTimeStamp>
  </thisDocumentGenerationDateTime>
    <ManufacturingStatusReport>
      <reportIdentifier>
        <ProprietaryDocumentIdentifier>MFG-STATUS-2026-D138</ProprietaryDocumentIdentifier>
      </reportIdentifier>
      <reportPeriod><DateStamp>20260516</DateStamp></reportPeriod>
      <ProductIdentification>
        <GlobalProductIdentifier>00614141666664</GlobalProductIdentifier>
      </ProductIdentification>
      <wipQuantity><ProductQuantity>248000</ProductQuantity></wipQuantity>
      <completedQuantity><ProductQuantity>215000</ProductQuantity></completedQuantity>
      <yieldPercentage>97.8</yieldPercentage>
    </ManufacturingStatusReport>
</Pip6C2ManufacturingStatusNotification>

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 6C2 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

Foxconn distributes to Apple via PIP 6C2 the daily iPhone manufacturing status at the Zhengzhou site: 248,000 WIP units, 215,000 completed, 97.8% yield rate.

Foundations

Standards

Flagship messages

Tools