Event Model & Data Lineage

Reference for how the Nedap Inventory Engine turns raw RFID reads into EPCIS-aligned business events, reconciled facts and gold-layer metrics.

Priority briefing

Automatic

Adopt this catalogue as the reference contract for all downstream reconciliation and reporting builds.

Zone-resolution logic v2.3 shipped, reducing ambiguous-read escalations by 14%.

Owned by Data Engineer · Platform

EPCIS bizSteps modelled

commissioning → decommissioning

Curated tables

bronze → silver → gold

Lineage stages

raw reads to metrics

Quality rules documented

active in pipeline

Click a stage to see how data is transformed at that step

Raw reads

bronze.rfid_reads — immutable reader observations

bizStep / disposition pairs emitted by the engine

Event type	bizStep	Disposition	Description
ObjectEvent	commissioning	active	EPC encoded and validated against GTIN at source-tagging vendor.
ObjectEvent	receiving	in_progress	Units verified against ASN at DC or store dock door.
ObjectEvent	stocking	sellable_accessible	Item moved from back room to sales floor.
ObjectEvent	picking	reserved	Item reserved for an order in OMS.
ObjectEvent	shipping	in_transit	Item leaves an origin location on an outbound shipment.
ObjectEvent	retail_selling	sold	POS transaction confirms sale.
ObjectEvent	cycle_counting	active	Zone sweep observation reconciled with system of record.
ObjectEvent	returning	returned	Item returned by customer, pending restock decision.
ObjectEvent	decommissioning	decommissioned	EPC retired at end of item lifecycle.

Why exceptions get raised, not silently dropped

Duplicate suppression
Same EPC + reader + antenna inside a configurable short window collapses to one logical observation; raw records retained with read count and strongest RSSI.
Weak or ambiguous reads
Configurable zone-level RSSI thresholds. Uncertain observations are held for corroboration rather than discarded; an ambiguity issue is raised if confidence stays low.
Zone determination
Combines reader/antenna, RSSI, direction, recency, zone geometry, historical reader performance and corroborating reads.
Late events
Original event_ts drives state reconstruction; record_ts is kept for audit. State is recalculated when late evidence changes the conclusion — never silently discarded.
Unknown EPC
Event is retained and quarantined; a product-master or serialization issue is created rather than dropping the record.
Duplicate or reused EPC
Compared against lifecycle state; an EPC in incompatible locations or states is routed to serialization review.
Ownership
Physical presence is kept separate from inventory ownership. Partner-owned concession/consignment stock is never added to VF-owned inventory.
Item state validation
Proposed state transitions are validated against an item-level state machine before being committed.

Select a table to view its schema

One row per serialised item (EPC/SGTIN).