OneTrack requires operator-level transaction data to be pushed FROM the WMS TO OneTrack. This is a one-way data exchange that is typically automated through an automated export-push.
In other words, the activity records of the associate on the forklift should be transmitted to OneTrack to combine them with information about the physical activity of the lift
- SFTP file upload.
- Dedicated email address with automatedingestion (provisioned by OneTrack).
- API callAWS S3 file upload.
JSON, CSV, fixed-width field files, TXT
This depends on customer’s requirements. Typically, customers push once every 5-15 minutes with the latest transaction data and some overlap between pushes.
OneTrack handles all deduplication during data ingestion. We prefer files be sent with crossover transactions (e.g., sending files every 15 minutes with the last hours data)
OneTrack does not write data back into the WMS. However all reporting and data needed is available through exporting. Please contact your dedicated Implementation Engineer for additional needs.
All data is encrypted at rest and in transit, isolated by customer, and stays within OneTrack infrastructure (databases, data storage). All data stays in North America, backed up across at least 2 regions.
-We strive to support any WMS. So far, we have ingested data from: SAP EWM, HighJump, BlueYonder, custom/home-grown AS400 systems.
- As long as there is a transaction-level view of operator activity, we are confident we can support the WMS.
Customer’s IT team is responsible for setting up the data export from your WMS to the OneTrack endpoint. Depending on the WMS capabilities, this may require only a few clicks, or several weeks of work to configure and set up.