RosettaNet

The XML EDI standard that orchestrates semiconductor and high-tech supply chains since 1998. Choreographed PIPs on top of RNIF, signed and shipped over HTTPS or AS2.

What is RosettaNet?

RosettaNet is an XML-based EDI standard targeted at the high-tech supply chain. Where EDIFACT and X12 encode messages in compact segments, RosettaNet encodes each business interaction (order, forecast, shipment notice) as a self-describing XML document wrapped in a signed MIME envelope. The standard is process-centric: every interaction is defined as a two- or three-step choreography — request, acknowledgment, sometimes confirmation — between a buyer and a seller role.

The founding consortium gathered Compaq, HP, IBM, Intel and Microsoft. It expanded to about 500 member companies, mainly across the United States, Taiwan, Singapore, Japan, China and Malaysia. Adoption remains thin in Europe, where EDIFACT still dominates the same retail, automotive and chemical use cases.

Architecture: PIPs on RNIF

The RosettaNet stack has three layers:

1. PIP — Partner Interface Process: the business layer. Each PIP is identified by a four-character code (e.g. 3A4 for Purchase Order Request) that combines its numeric cluster and its segment. The PIP defines the XML payload, the choreography between roles, and the business validation rules.
2. RNIF — RosettaNet Implementation Framework: the envelope layer. RNIF V02.00 packages the PIP inside a MIME multipart object containing a Preamble, a DeliveryHeader, a ServiceHeader and the PIP payload itself. The whole envelope is S/MIME-signed (default RSA + SHA-1, SHA-256 in modern profiles).
3. Transport: HTTPS directly (POST to the partner endpoint), or AS2 to interoperate with integrators already standardised on it. The acknowledgment signals (RNIF Acknowledgment / Exception) flow back over the same channel.

This stratification is visible on the wire: the outer MIME envelope holds four parts, each an XML fragment conformant to an RNIF schema, plus the business PIP in the middle.

Anatomy of a PIP 3A4

PIP 3A4 — Purchase Order Request is the most-exercised PIP in the standard. It carries a purchase order from buyer to seller, who usually responds with a PIP 3A7 Notify of Purchase Order Update or a synchronous Acknowledgment of Receipt. Here is a simplified PIP 3A4:

<?xml version="1.0" encoding="UTF-8"?>
<Pip3A4PurchaseOrderRequest xmlns="http://www.rosettanet.org/PIP3A4">
  <fromRole>
    <PartnerRoleDescription>
      <ContactInformation>
        <contactName><FreeFormText>Procurement — TSMC</FreeFormText></contactName>
      </ContactInformation>
      <GlobalPartnerRoleClassificationCode>Buyer</GlobalPartnerRoleClassificationCode>
    </PartnerRoleDescription>
  </fromRole>
  <toRole>
    <PartnerRoleDescription>
      <ContactInformation>
        <contactName><FreeFormText>ASE Group — Sales</FreeFormText></contactName>
      </ContactInformation>
      <GlobalPartnerRoleClassificationCode>Seller</GlobalPartnerRoleClassificationCode>
    </PartnerRoleDescription>
  </toRole>
  <PurchaseOrder>
    <GlobalPurchaseOrderTypeCode>Standard</GlobalPurchaseOrderTypeCode>
    <PurchaseOrderIdentifier>
      <ProprietaryDocumentIdentifier>PO-2026-987654</ProprietaryDocumentIdentifier>
    </PurchaseOrderIdentifier>
    <thisDocumentGenerationDateTime>
      <DateTimeStamp>20260514T101500Z</DateTimeStamp>
    </thisDocumentGenerationDateTime>
    <ProductLineItem>
      <LineNumber><FreeFormText>1</FreeFormText></LineNumber>
      <ProductIdentification>
        <GlobalProductIdentifier>00614141999996</GlobalProductIdentifier>
      </ProductIdentification>
      <requestedQuantity>
        <ProductQuantity>50000</ProductQuantity>
        <unitOfMeasure>EA</unitOfMeasure>
      </requestedQuantity>
    </ProductLineItem>
  </PurchaseOrder>
</Pip3A4PurchaseOrderRequest>

Three elements structure every PIP request: fromRole / toRole qualify the business actors of the choreography (Buyer / Seller in 3A4); PurchaseOrder carries the payload aligned with the RosettaNet dictionary (RNBPV, RosettaNet Business Process Vocabulary); and each line of the order is a ProductLineItem identified by a GTIN-14 (GlobalProductIdentifier), inherited directly from the GS1 convention for product codes.

Most-used PIPs

The standard ships more than 100 specified PIPs, but most of the global traffic flows through about a dozen of them. The most-encountered ones in real integrations:

Documented PIP catalogue

Detailed pages available on ediverse for 35 representative PIPs, from failure notifications (cluster 0) up to production flows (cluster 7):

PIP clusters

PIPs are organised into clusters (numbered 0 to 7) that group the choreographies by functional domain. This taxonomy lets an integrator identify the intent of an exchange at a glance, and remains the historical reading grid of the standard.

Transport: HTTPS, S/MIME, AS2

The PIP payload never travels alone. It is wrapped in an RNIF MIME multipart envelope containing Preamble, DeliveryHeader, ServiceHeader and the PIP body, signed with S/MIME and pushed via HTTPS POST to the partner endpoint or through AS2. A condensed RNIF envelope, for illustration:

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-DeliveryHeader.xml

<DeliveryHeader xmlns="http://www.rosettanet.org/RNIF/V02.00">
  <messageTrackingID>PO-2026-987654-RN</messageTrackingID>
  <isSecureTransportRequired>Yes</isSecureTransportRequired>
</DeliveryHeader>

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

<ServiceHeader xmlns="http://www.rosettanet.org/RNIF/V02.00">
  <GlobalPartnerClassificationCode>Buyer</GlobalPartnerClassificationCode>
  <GlobalProcessIndicatorCode>3A4</GlobalProcessIndicatorCode>
  <GlobalProcessVersionIdentifier>V02.02</GlobalProcessVersionIdentifier>
</ServiceHeader>

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

<!-- PIP 3A4 payload as above -->

--RN-BOUNDARY-2026--

Industry adoption

The historical core market for RosettaNet is the semiconductor supply chain: foundries (TSMC, GlobalFoundries), OSAT — Outsourced Semiconductor Assembly and Test (ASE, Amkor), discrete and passive component makers, equipment vendors (ASML, Applied Materials). Standardisation here is driven by the Intel / TSMC cooperation and their subcontractors.

Beyond semi, the standard is still used at the contract manufacturer layer (Foxconn, Flex, Jabil) for brand-owner / EMS coordination, in the component distribution world (Arrow, Avnet, WPG), and across parts of telecom and data center where the cadence of weekly forecasts (PIP 4A5) remains critical. Consumers brush against it without noticing every time a high-tech maker publishes an updated lead time: more often than not, a PIP 3A7 has just travelled upstream to refresh the schedule.

Governance and GS1 US

The RosettaNet consortium, created in 1998, evolved into a non-profit covering about 500 member companies at its peak. In 2013, the independent rosettanet.org website was decommissioned: the programme is now hosted as a sub-programme of GS1 US (formerly the Uniform Code Council). The standards keep evolving under the umbrella of the RosettaNet Standards Programme, with a dedicated governance committee and member-only access to the specification packages.

Further reading

Reference resources to read before any integration:

• GS1 US — RosettaNet Standards Programme — the current custodian of PIPs and RNIF.
• Wikipedia — RosettaNet — consortium history, founders, sector adoption.
• AS2 on ediverse — alternate transport protocol compatible with RNIF.
• EDIFACT on ediverse — direct competitor of RosettaNet on order / invoice flows, dominant in Europe.