PIP 6C1 — Distribute Engineering Change Order

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

PIP purpose

PIP 6C1 distributes an Engineering Change Order (ECO) that modifies a bill of materials, a part number, or a product parameter. It targets downstream suppliers so they can adjust their BOM and manufacturing process.

Message structure

The 6C1 choreography follows the RosettaNet action model:

Primary action: Engineering Change Order 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-6C1.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>6C1</GlobalProcessIndicatorCode>
</ServiceHeader>

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

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

--RN-BOUNDARY-2026--

Simplified XML example

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

xml pip-6C1.xml

<?xml version="1.0" encoding="UTF-8"?>
<Pip6C1EngineeringChangeOrderNotification xmlns="http://www.rosettanet.org/PIP6C1">
  <fromRole>
    <PartnerRoleDescription>
      <GlobalPartnerRoleClassificationCode>Manufacturer</GlobalPartnerRoleClassificationCode>
    </PartnerRoleDescription>
  </fromRole>
  <toRole>
    <PartnerRoleDescription>
      <GlobalPartnerRoleClassificationCode>Supplier</GlobalPartnerRoleClassificationCode>
    </PartnerRoleDescription>
  </toRole>
  <thisDocumentGenerationDateTime>
    <DateTimeStamp>20260516T101500Z</DateTimeStamp>
  </thisDocumentGenerationDateTime>
    <EngineeringChangeOrder>
      <ecoIdentifier>
        <ProprietaryDocumentIdentifier>ECO-2026-A29-rev03</ProprietaryDocumentIdentifier>
      </ecoIdentifier>
      <changeType>MaskRevision</changeType>
      <ProductReference>
        <GlobalProductIdentifier>00614141555557</GlobalProductIdentifier>
        <previousRevision>rev02</previousRevision>
        <newRevision>rev03</newRevision>
      </ProductReference>
      <effectiveDate><DateStamp>20260701</DateStamp></effectiveDate>
    </EngineeringChangeOrder>
</Pip6C1EngineeringChangeOrderNotification>

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

Intel distributes to its 11 foundries via PIP 6C1 an ECO on wafer part 14nm-A29 (litho mask revision), effective 2026-07-01.

Foundations

Standards

Flagship messages

Tools