Automatic identification and data capture is not one technology. It is the layer that turns physical things - a pallet, a patient, a meter, a vehicle - into records a system can act on. When that layer is designed well nobody notices it. When it is designed badly, every system above it inherits the error.
Identification and barcode
Symbology selection, print and verification quality, application standards, and the identifier schemes that make a code mean the same thing to two organisations.
Where it breaks. A code that scans on the bench and fails on the dock. Identifiers that are unique inside one company and collide the moment goods move between two.
What we teach. Curriculum covering GS1 identification keys, symbology and print quality grading, plus applied labs that verify against a real acceptance bar rather than a screenshot.
Data capture
The readers, scanners, mobile computers, printers and sensors that turn an identifier into a record, and the workflows that run on them.
Where it breaks. Devices bought as hardware and never managed as a system, so the estate fragments and the workflow breaks on a subset nobody can identify.
What we teach. Device selection and lifecycle, print and verification quality, and the read-zone planning that decides whether capture survives a real operation.
RFID and RTLS
Passive and active radio identification, reader and antenna planning, tag selection against materials, and real-time location where position rather than presence is the question.
Where it breaks. Pilots that read at 99% in a demo room and 60% over a loaded dock door, because nobody modelled the material, the orientation or the interrogation zone.
What we teach. Physics-first teaching: what the material does to the field, why read rate collapses, and how to plan a zone that survives contact with a real operation.
Enterprise mobility
Rugged and consumer capture devices, operating-system lifecycle, device management, battery and charging estates, and the workflows that run on them.
Where it breaks. A device estate bought as hardware and never managed as a system - so the fleet fragments across OS versions and the workflow breaks on a subset nobody can identify.
What we teach. Device integration taught as a lifecycle, from selection and provisioning to management, replacement and the total cost that procurement usually misses.
Machine vision
Fixed and handheld imaging for identification, presence, dimensioning and condition, and the lighting that determines whether any of it works.
Where it breaks. Vision projects specified on camera resolution and delivered without a lighting design, then blamed on the algorithm.
What we teach. Imaging fundamentals alongside the practical trade between optical decode, imaging and a model - including when a barcode is simply the cheaper answer.
Automation and AI
Where automated decisions belong in a capture workflow, what data quality they assume, and how to keep a human accountable for an outcome a model influenced.
Where it breaks. Models deployed onto a capture layer that was never trusted, inheriting every identifier collision and timestamp gap underneath them.
What we teach. A governance-first treatment: what the technology can carry, what it cannot, and the assurance a deployment needs before it is allowed to act.
Enterprise integration
Getting captured events into the systems that run the business - ERP, WMS, MES, EHR - and back out again, with the interfaces and error handling that implies.
Where it breaks. A capture project that works perfectly and delivers nothing, because the integration was scoped as a file drop and the exceptions had nowhere to go.
What we teach. Interface patterns, event models and the failure handling that decides whether an integration degrades safely or silently.
Identity and traceability
Event-level traceability across organisations: what was observed, when, where, and why - shared in a form a trading partner can query rather than a report they have to read.
Where it breaks. Two partners who are both right and cannot prove it, because each holds a private truth in a private layout.
What we teach. EPCIS event modelling, GS1 Digital Link and the discovery problem - taught as the reason the standard exists, not as vocabulary.
The capability is the same. What changes is the cost of
getting it wrong.
Logistics and warehousing
Receiving, put-away, picking, dispatch and proof of delivery, where capture accuracy sets the ceiling on every downstream promise.
Healthcare and life sciences
Patient, specimen and medication identification, where a misidentification is a clinical event and not a data quality metric.
Manufacturing
Work-in-progress visibility, component genealogy and the recall question: which units contain this batch, answered in minutes.
Retail and distribution
Inventory accuracy, replenishment and the gap between what the system holds and what is on the shelf.
Public sector
Identity, customs, ports and asset registers, where the record is the entitlement and an error is a citizen turned away.
Banking and financial services
Document, device and asset custody, and the audit evidence that the custody chain was never broken.
Energy and utilities
Asset registers, field inspection and maintenance records for estates that are distributed, remote and hard to re-survey.
Courier, express and postal
Item-level tracking and delivery evidence at a volume where a one percent exception rate is thousands of parcels.
