Pilot
Test one agreed area or workflow. Confirm the critical assumptions and record the acceptance results.
Need to track assets?
Tag assets, scan them with a handheld or fixed reader and keep an asset register with last-seen location and movement history.
Manual asset checks can leave the register behind the real operation. Define the observation you need: the asset identity, last-seen location, timestamp and the action after an exception.
A tag identifies the asset. Handheld scans or defined fixed reading points produce observations that the application associates with an asset record. A controlled workflow handles unexpected, missing or duplicate observations.
Quoted as a package after scope review. Hardware, engineering, site work and any recurring charges are stated separately in the proposal. Final quantities, exclusions and deliverables are confirmed in the quotation.
Agree the acceptance criteria before work starts. A trial establishes the limits of the tested application.
No. This package records observations at handheld scans or fixed reading points. Continuous precise positioning requires a separate feasibility assessment.
Tag selection and mounting matter. Suitable on-metal tags should be tested on representative assets before rollout.
Yes, subject to its import or API capabilities. We will agree identifiers, required fields and update rules first.
A few details help us recommend a starting configuration. This is a scope recommendation; engineering and pricing follow a review.