Know how long every part has been waiting, and where it sits.

Metal environments need the right tag types; on-metal tags exist for exactly this. During setup we spec tags for your materials and verify every read point before you rely on the data. If a read point is weak, we move the reader and verify it again.

Yes, through a documented REST API. Push scans in, pull part history and analytics out, and connect your ERP, MES, or reporting stack. API access is part of the subscription. Connectors are scoped per customer against the documented API, in writing, before you commit.

Because a tracked floor works as one system. Antennas are tuned per location, and the board is read by everyone from the floor lead to the front office. A site price keeps it whole: add people freely, put the board on the wall, and adding tracked locations later is a written line item you can price before you commit.

That's the intended path. We start with a scoped pilot on a single line: prove the board tells the truth about that line, then expand across the floor in writing, at your pace.

Yes. Handheld scans at each stage boundary feed the same board and start the same clocks, so wait time is measured from the first day, sized by where you scan. Fixed readers add hands-free coverage where the traffic justifies them, and a work-order link through the API adds step-level timing when routings revisit a station. The board, the alerts, and the history work the same at every step.

A pilot has a clean walk-away: it runs against success criteria agreed in writing before it starts, and if they are not met the agreement ends there, with the pilot fee as the whole commitment. Either way your data is yours: export part records and scan history through the API at any time. We build to earn the expansion, and the door stays open the whole time.

The floor-facing side is a board and a search box; operator training typically takes a couple of hours. On-site commissioning stands the system up in a few days, including training.