PIP 6A1 — Distribute Manufacturing Resources Plan

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

PIP purpose

PIP 6A1 distributes a Manufacturing Resources Plan (MRP) between a manufacturer and its contract EMS. The plan aggregates machines, weekly capacity, and assigned lines over a 13-week rolling horizon.

Message structure

The 6A1 choreography follows the RosettaNet action model:

Primary action: Manufacturing Resources Plan 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-6A1.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>6A1</GlobalProcessIndicatorCode>
</ServiceHeader>

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

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

--RN-BOUNDARY-2026--

Simplified XML example

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

xml pip-6A1.xml

<?xml version="1.0" encoding="UTF-8"?>
<Pip6A1ManufacturingResourcesPlanNotification xmlns="http://www.rosettanet.org/PIP6A1">
  <fromRole>
    <PartnerRoleDescription>
      <GlobalPartnerRoleClassificationCode>Manufacturer</GlobalPartnerRoleClassificationCode>
    </PartnerRoleDescription>
  </fromRole>
  <toRole>
    <PartnerRoleDescription>
      <GlobalPartnerRoleClassificationCode>ContractManufacturer</GlobalPartnerRoleClassificationCode>
    </PartnerRoleDescription>
  </toRole>
  <thisDocumentGenerationDateTime>
    <DateTimeStamp>20260516T101500Z</DateTimeStamp>
  </thisDocumentGenerationDateTime>
    <ManufacturingResourcesPlan>
      <planIdentifier>
        <ProprietaryDocumentIdentifier>MRP-2026-W20-PEN</ProprietaryDocumentIdentifier>
      </planIdentifier>
      <planningHorizon>
        <forecastStartDate><DateStamp>20260518</DateStamp></forecastStartDate>
        <forecastEndDate><DateStamp>20260816</DateStamp></forecastEndDate>
      </planningHorizon>
      <ResourceLineItem>
        <resourceCode>SMT-LINE-3</resourceCode>
        <reservedCapacity unitOfMeasure="UnitsPerWeek">160000</reservedCapacity>
      </ResourceLineItem>
      <ResourceLineItem>
        <resourceCode>SMT-LINE-5</resourceCode>
        <reservedCapacity unitOfMeasure="UnitsPerWeek">140000</reservedCapacity>
      </ResourceLineItem>
    </ManufacturingResourcesPlan>
</Pip6A1ManufacturingResourcesPlanNotification>

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

Cisco distributes a weekly PIP 6A1 to its EMS Flex Penang, breaking down reserved SMT line 3 and 5 capacity (300,000 boards / week) over the next 13 weeks.

Foundations

Standards

Flagship messages

Tools