Plant-floor material visibility means being able to answer a practical question: which material is available for this job, where is it, what condition is it in, and how current is that information? Build the answer from identifiable events and reconcile it with physical production.
This guide helps planners, material handlers, and manufacturing-systems owners define a small work-in-progress tracking pilot. Start with one material route, its locations, lot or serial identification rules, units, and the decisions a shortage or quality hold should trigger.
Give the material and location a consistent identity
Define the level of tracking needed: a part type, lot, serialized item, container, or handling unit. A reusable tote and its contents have separate identities. When contents change, the system must record that relationship; scanning the tote alone can otherwise imply the wrong material is inside.
GS1's EPCIS and Core Business Vocabulary overview describes a common way to share events about what happened, when, where, why, and how. These dimensions provide a useful checklist even for a small internal pilot. An interoperable implementation requires the actual standards and partner agreements.
On a narrow screen, scroll the table horizontally. Keyboard users can focus it and use the arrow keys.
| Field | Example question | Why the answer matters |
|---|---|---|
| Identity | Which material, lot, item, and container were involved? | A location observation must refer to the correct physical thing. |
| Quantity and unit | How many pieces, kilograms, or other defined units changed state? | A quantity has meaning only with its unit and conversion rules. |
| Place | Which read point and business location apply? | A scanner location can differ from the location assigned after the event. |
| Time | When did it happen, and when was it received? | Delayed uploads must remain distinguishable from current observations. |
| Context and status | Was material received, moved, consumed, produced, held, or scrapped? | The event changes a planning decision, not just a dot on a map. |
| Evidence and ownership | Which event ID, source device, job, and responsible role apply? | Duplicates and exceptions can be investigated and resolved. |
Distinguish movement, grouping, and transformation
Moving a tote changes its location. Packing items into a handling unit establishes a relationship between parent and children. Consuming inputs to produce an output creates a different traceability relationship. The GS1 implementation guideline explains these event distinctions; its version 1.2 examples are useful conceptual background, while new implementations should use their selected current standard release.
Agree on what each event changes in your application. A quality hold may reduce available material without reducing physical stock. A reservation may reduce stock available to other jobs without consuming anything. Scrapping an input and producing a good output need separate quantities and identities where required for traceability.
Document split lots, rework, partial consumption, and returns before the pilot encounters them. Keep unit conversions in controlled master data and preserve the source unit in the event record. An unexplained negative balance should enter an exception queue, with the affected job and an owner visible.
Reconcile a missing consumption event
Retain event time and receipt time separately. Define how the receiving system recognizes a repeated transmission and handles an out-of-order event. EPCIS 2.0.1 specifies event and record-time semantics and error declarations. Its correction mechanism preserves prior assertions and identifies their error; application-specific recovery needs to implement those semantics carefully.
The example is a teaching ledger, not an EPCIS payload. In a real system, correct an erroneous event through the approved event or audit mechanism, preserve the evidence, and recompute affected views. Record who reviewed the reconciliation and whether any production commitment depended on the earlier balance.
Turn visibility into an owned response
Choose a few actionable exceptions for the pilot: material in an unexpected location, a stale observation, a shortage before a scheduled operation, an unidentified container, or held material offered to production. Each needs a responsible role, a resolution method, and a way to confirm the physical situation.
For a shortage, show the job, required material and quantity, available quantity under the agreed rules, location evidence, and age of the last relevant event. The planner can then choose whether to investigate, replenish, resequence, or escalate. Keep the decision and its reason with the exception.
Report event delay, unresolved discrepancies, and time to resolution alongside location coverage. A high scan count can coexist with poor material accuracy. Review a sample of tracked items against physical stock and trace a sample of completed jobs back through material consumption.
Start with one complete route
- Walk the route with operators and agree on identities, locations, units, and ownership.
- Map normal movements plus rework, scrap, split lots, and offline operation.
- Test duplicate messages, missed scans, delayed uploads, and device restarts.
- Reconcile the event ledger with physical stock at agreed checkpoints.
- Review whether the exceptions produced useful decisions before expanding coverage.
The industrial gateway guide addresses reliable device messages. Operations monitoring covers production states and performance measures, while supply chain planning explains the wider planning decisions that consume material information.
Use the event and reconciliation worksheet
Download the material visibility record and example ledger. It includes the 100-piece example, identity and unit fields, duplicate-handling questions, and a reconciliation sign-off. Use it to agree on the pilot's behavior before configuring a dashboard.