1. Fleet Provisioning
Each device is registered with a unique identity and mapped to a site, role, and policy profile. MQTT topics scope what each Droid can publish and subscribe to from day one.
QDatDroid
Share a few details so we can support your RFID deployment and keep your team up to date.
QDatDroid enables mobile RFID for QDat workflows on Android phones, tablets, and Zebra RFID handhelds. Submit the form below to access the APK and get deployment support.
Provisioning Architecture
QDat uses MQTT as a command and telemetry backbone so device identity, app configuration, and workflow policy can be rolled out consistently across a large frontline fleet without manual per-device setup.
Each device is registered with a unique identity and mapped to a site, role, and policy profile. MQTT topics scope what each Droid can publish and subscribe to from day one.
The QDatDroid app receives remote configuration packages over MQTT: endpoints, feature flags, scan rules, validation logic, and offline sync behavior. Updates propagate in near real time.
Every frontline worker follows the same guided capture flow, with identical event schema and quality controls, reducing data drift between facilities and shifts.
Device checks in, receives credentials, and binds to approved MQTT channels for its assigned operation.
App-level provisioning pushes the exact workflow package needed for the frontline role, including required fields and scan thresholds.
Reads, timestamps, geospatial context, and operator actions are emitted through consistent payload contracts into the QDat ingestion pipeline.
Teams can roll out configuration changes centrally and verify adoption quickly, enabling reliable ingestion from thousands of active workers.
Complete the form to receive QDatDroid download and onboarding details.