Line execution and proof at production speed
DXT Tracker coordinates serialized production events across printing, inspection, rejects, rework, recovery, and reconciliation.
What Tracker Proves
- Unit-level execution history
- Reject and rework accountability
- Batch-aligned reconciliation
Tracker / Line Execution
Machine-native line control
Where production identity becomes line truth
Tracker operates directly within the production workflow, coordinating serialized identity with printers, cameras, scanners, sensors, triggers, reject devices, encoders, and material-flow events. It validates, reconciles, and records the configured execution sequence so production history can be investigated, recovered, and defended.
Execution Coordination
Keep serialized print, inspection, movement, reject, and recovery events aligned with the approved job.
Production Evidence
Create unit-event streams, inspection results, reject reasons, rework linkage, batch reconciliation, and recovery history.
Capabilities
Line execution and proof
Capabilities vary by deployment — not every configuration includes every module.
Serialization Control
Unit identity, print events, code exchange, execution status, and serialized production history.
What Tracker proves — and where it sits in the stack
Tracker is the Level 2 execution layer. It receives identity from Facility Control, drives the physical line, and emits the audit-grade records below as proof — flowing upward into Insight and the enterprise.
Creator owns identity definition · Allocator owns custody · SiteCentral owns plant command · Tracker owns line execution truth · Insight owns enterprise observability · Verify owns downstream verification.
Control stack
DXT Insight
Observability + intervention
Creator · Allocator · SiteCentral
Identity, custody, plant command
DXT Tracker
Execution + proof
Printers · Cameras · Reject gates
Physical line hardware
Records emitted by Tracker
- Unit event streamEvery print, scan, and inspection captured at line speed with a timestamp and unit identity.Record
- Inspection resultPass/fail outcomes from cameras and sensors, linked to the unit that produced them.Record
- Reject recordEach rejected unit logged with reason, station, and reject-gate confirmation.Record
- Rework linkageReintroduced units tracked from removal through re-verification, preserving identity custody.Record
- Batch reconciliationIssued vs. consumed vs. rejected totals closed out per batch for audit and release.Record
- Recovery evidenceInterruption, restart, and reproduction events preserved as a continuous audit trail.Record
- Production execution historyUnit- and batch-level history retained for investigation, release, and downstream exchange.Record
Integrated Ecosystem
Tracker in the Delta-X Trust ecosystem
Approved identity enters the line, machine-native control coordinates the production event, and line truth becomes usable evidence.
Approved identity enters the line
Creator defines rules, Allocator governs custody, and SiteCentral supplies approved job and plant context for Tracker execution.
Machine-native control coordinates the production event
Tracker and the configured DXT Controller coordinate printers, cameras, scanners, sensors, triggers, encoders, reject devices, and line signals.
Line truth becomes usable evidence
Tracker returns execution status to SiteCentral, supplies trusted events to Insight, and exchanges approved data with configured enterprise or downstream systems.
FAQ
Frequently Asked Questions
Common questions about line serialization and inspection with DXT Tracker.
Engineer your production future
Talk to the team that's built identity infrastructure for manufacturers, converters, and regulated brands across four continents.
Resources
Production Identity Insights
Research, implementation guidance, and application perspectives for teams responsible for production identity, verification, and evidence.


