PIP 7C1 — Distribute Production Status Report

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 7C1 distributes a periodic consolidated production report: planned volume, produced volume, variance, alerts. Macroscopic counterpart of PIP 6C2 focused on weekly or monthly reporting.

Message structure

The 7C1 choreography follows the RosettaNet action model:

Primary action: Production Status Report 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-7C1.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>7C1</GlobalProcessIndicatorCode>
</ServiceHeader>

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

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

--RN-BOUNDARY-2026--

Simplified XML example

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

xml pip-7C1.xml

<?xml version="1.0" encoding="UTF-8"?>
<Pip7C1ProductionStatusReportNotification xmlns="http://www.rosettanet.org/PIP7C1">
  <fromRole>
    <PartnerRoleDescription>
      <GlobalPartnerRoleClassificationCode>ContractManufacturer</GlobalPartnerRoleClassificationCode>
    </PartnerRoleDescription>
  </fromRole>
  <toRole>
    <PartnerRoleDescription>
      <GlobalPartnerRoleClassificationCode>Manufacturer</GlobalPartnerRoleClassificationCode>
    </PartnerRoleDescription>
  </toRole>
  <thisDocumentGenerationDateTime>
    <DateTimeStamp>20260516T101500Z</DateTimeStamp>
  </thisDocumentGenerationDateTime>
    <ProductionStatusReport>
      <reportIdentifier>
        <ProprietaryDocumentIdentifier>PROD-W20-2026-GDL</ProprietaryDocumentIdentifier>
      </reportIdentifier>
      <reportingPeriod>
        <forecastStartDate><DateStamp>20260511</DateStamp></forecastStartDate>
        <forecastEndDate><DateStamp>20260517</DateStamp></forecastEndDate>
      </reportingPeriod>
      <plannedQuantity><ProductQuantity>285000</ProductQuantity></plannedQuantity>
      <producedQuantity><ProductQuantity>281200</ProductQuantity></producedQuantity>
      <variancePercentage>-1.3</variancePercentage>
    </ProductionStatusReport>
</Pip7C1ProductionStatusReportNotification>

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 7C1 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

Jabil distributes to Cisco via PIP 7C1 a weekly production progress report at the Guadalajara EMS: 285,000 boards planned, 281,200 produced, variance −1.3%.

Foundations

Standards

Flagship messages

Tools