EPCIS & Sensor MetaData: Connecting Events

September 6, 2026

A learning journey through EPCIS 2.0 - how product identity, events, location, and environmental conditions come together for complete product visibility.

[email protected]

The Core Challenge

No Visibility in Motion

Products move through supply chains with no record of what actually happened to them between handoffs.

Invisible Conditions

Temperature, humidity, and handling events are unrecorded yet they determine product quality and authenticity.

Proof, Not Just Location

Regulatory and customer demands require evidence of what conditions existed, not just where a product was.

EPCIS 2.0

EPCIS: The Foundation

EPCIS (Electronic Product Code Information Services) is the global GS1 standard for sharing supply chain event data.

Three Pillars of EPCIS 2.0

EPCIS 2.0 is built on three interdependent pillars. Each pillar is necessary, but none is sufficient alone. Together they create a complete, machine readable account of supply chain reality.

Pillar 1: Identity

Every product, location, and party in an EPCIS system is assigned a globally unique identifier. For physical items, this is an Electronic Product Code (EPC) a structured identifier that encodes the product type, the company that made it, and a unique serial number for that specific instance.

Why it matters: Without unambiguous identity, events cannot be reliably attributed to the right object. A barcode tells you the product type; an EPC tells you this specific unit, distinguishing one vial of vaccine from the one next to it on the same shelf.


Pillar 2: Events

An EPCIS event is a structured record of something that happened to one or more identified objects at a specific time and place. Events are the atomic units of supply chain narrative, each one captures a discrete moment of operational reality.

Why it matters: Traditional EDI messages describe planned or expected transactions. EPCIS events record what actually happened. This distinction is fundamental to compliance and dispute resolution.


Pillar 3: Context

Context is the organizational and operational metadata that makes events interpretable and trustworthy. An event without context is a data point; with context it becomes evidence.

Why it matters: Regulators, trading partners, and auditors need to understand not just what happened but under whose authority, in what facility, and within what regulatory framework. Context fields in EPCIS provide exactly this accountability layer.

How the Three Pillars Work Together

The power of EPCIS is not in any single conceptual pillar but in their integration. Consider a real world scenario: a batch of temperature sensitive biologics is manufactured, distributed, and delivered to a hospital pharmacy.

  • Identity assigns unique EPCs to every vial at commissioning. Each vial, each case, and each pallet has a globally unique, unambiguous identifier tied to its lot number and expiry date via ILMD.
  • Events record every operational moment: commissioning at the manufacturer, aggregation into cases and pallets, a TransformationEvent if secondary packaging occurs, ObjectEvents at each custody transfer manufacturer to 3PL, 3PL to wholesale distributor, wholesaler to pharmacy each with precise timestamps and bizStep classifications.
  • Context wraps each event with accountability: which facility performed the operation, which regulatory authority governs it, what the environmental conditions were via SensorElement data, and which business parties transferred custody via sourceList/destList.

The result is a complete, queryable audit trail, enabling product security. If a cold chain excursion is detected, investigators can query the EPCIS repository to identify exactly which events occurred during the suspect time window, which specific units were affected, who had custody, and what the sensor data shows, all from a single, standardized data structure. This is not theoretical as EPCIS is the mandated data standard for pharmaceutical traceability under the U.S. Drug Supply Chain Security Act (DSCSA), the EU Falsified Medicines Directive (FMD), and emerging food traceability regulations under FDA's FSMA 204.

Sensor Data: Closing the Visibility Gap

Core Structure

Identity + Conditions = Product Security

The sensorElementList is embedded directly inside the EPCIS event alongside the epcList product identity and environmental conditions are always linked, never siloed.

Multiple formats are supported: individual readings, time-series trends, or aggregated statistics (min/max/mean) choose what fits your use case.

Connected JSON Structure

"epcList": [
 "urn:epc:id:sgtin:4012345.011111.9876"
],
"sensorElementList": [
 {
 "sensorReport": [
 {
 "type": "Temperature",
 "value": 26,
 "uom": "CEL"
 }
 ]
 }
]

How It Works: Real Examples

ObjectEvent : Pharmaceutical Vial

"sensorReport": [
  {
    "type": "Temperature",
    "value": 26,
    "uom": "CEL"
  },
  {
    "type": "AbsoluteHumidity",
    "value": 12.1,
    "uom": "A93"
  }
]

Benefit: Vial inspected with full environmental proof enables cold chain compliance verification at every handoff.

AggregationEvent : Chemical Batch

"sensorReport": [
  {
    "type": "Molar_concentration",
    "chemicalSubstance":
      "inchikey:CZMRCDWAGMRECN",
    "value": 0.18,
    "uom": "C35"
  }
]

Benefit: 52kg batch combined with contamination levels recorded prevents quality failures before processing begins.

Impact: Traceability, Security & Quality

Traceability

Follow products from manufacture to customer with a complete environmental history attached to every event — not just a location log.

Security

Detect tampering through sensor anomalies — unexpected temperature spikes, device ID mismatches, or impossible condition sequences.

Quality

Correlate environmental conditions with product outcomes — understand exactly what causes failures and intervene before they reach customers.

Enterprise Data Governance

GS1 EPCIS 2.0

One Standard, Every Partner

The standardized GS1 EPCIS 2.0 format eliminates proprietary data silos across supply chain partners, everyone speaks the same language.

Structured metadata including device IDs, timestamps, and processing methods is machine readable and fully auditable, enabling automated compliance checks without manual interpretation.

The extensible design allows custom sensor types and sector specific data fields to be added without breaking the standard future-proof by design.

From Data to Insight

CUSTOMIZABLE Sensor Intelligence
1

Individual Reading

{
  "type": "Temperature",
  "value": 26,
  "time": "2019-04-02T14:05:00"
}

Snapshot at one precise moment, the baseline observation.

2

Time-Series Trend

26°C → 26.1 → 26.2
→ 26.3 → 26.4 → 26.5°C
(over 50 minutes)

Six readings reveal a heating pattern, detect equipment failure early before product is compromised.

3

Statistical Summary

{
  "type": "Temperature",
  "minValue": 26,
  "maxValue": 26.2,
  "meanValue": 26.1,
  "sDev": 0.1
}

Predictive models identify which ranges correlate with defects, reducing material waste.

Why This Matters

Complete Visibility

Every product has an identity, every event is timestamped and located, every condition is measured nothing is invisible.

Actionable Intelligence

Faster recalls, premium positioning through authenticity proof, and measurable waste reduction across the supply chain.

Seamless Data Flow

Partners share information using one standard, not multiple incompatible formats.

EPCIS Sensor Data: The Complete Picture

One Source of Truth

EPCIS connects essential elements that together create complete supply chain intelligence:

The Transformation

By embedding sensor readings directly into EPCIS events whether individual measurements, time series trends, or statistical summaries - organizations gain complete visibility into product journeys.

This transforms EPCIS from a simple record of events into a source of truth for traceability, quality assurance, and authenticity verification across the entire supply chain.

Product Security. Visibility. Context. Traceability. These are not separate goals, they are the same goal, achieved through one standardized process.

01

Identity - What moved

The EPC uniquely identifies every item or batch, from a single pharmaceutical vial to a bulk chemical shipment.

02

Event - What happened

Observe, pack, transform, every action is captured with a defined type and action code.

03

Location & Timing - Where and when

Business location, read point, and precise timestamp anchor every event in space and time.

04

Sensor Conditions - Under what circumstances

Environmental and physical readings embedded directly in the event such as temperature, humidity, concentration, and more.

What I Bring to an Employer

I help organizations interpret complex regulatory and technical standards and turn them into practical governance, security, quality, and operational structures.

Data Governance

I connect identifiers, master data, lineage, data quality, and owenership into structured governance models that improve accuracy, traceability, and accountability.

Product Security

I translate product requirements, risks, and security standards into practical controls and structures that support secure products throughout their lifecycle.

Quality Management

I connect quality standards, process controls, data integrity, and traceability to help ensure products and operations consistently meet defined requirements.

International Standards

I explore how GTINs, GLNs, SSCCs, serialization, and EPCIS create a shared language for commerce.


Made with