The stack
Layer 1 · Track

OptiTrack

Field capture. What actually happened, recorded where it happened: a card at shift start, a task confirmed on the handheld, a unit's position and idle time on the apron.

Field events
ONE STREAM
09:14:02 CARD Shift start · crew room
09:14:20 TAG Handler on site · gate B12
09:15:11 QR Task confirmed · washroom L1
09:15:40 TAG Equipment at stand · GSE-12
09:16:03 SENS Passenger flow up · washroom L1
several device types, one feed
illustration, not a screenshot
The problem

Most operations only know what someone wrote down

Every layer above this one is only as good as the record it starts from. If the record is a timesheet filled in at the end of the shift, the plan, the report and the optimizer all inherit its gaps.

  • The provider reports on itself

    Completion is whatever the person doing the work says it was. Nobody else holds an independent record.

  • Inspection is a sample

    People walk a hand-picked fraction of the floor. Everything they did not walk is assumed to be fine.

  • Positions are guesses

    Where a crew or a unit actually is, and how long it stood idle, is known by radio and memory.

  • Nothing to plan against

    Without true durations, the next plan is built on the same estimates as the last one.

What it captures

Three kinds of input

Trackers, card readers, scanners

Where the resources are and who did what. Card in at shift start, task confirmed on the handheld, proof by QR or RFID badge at the room itself. Indoor trilateration trackers rather than GPS.

Cleaning and washroom sensors

Passenger flow, consumables, door line and air. No cameras in a washroom.

A managed device estate

Every device is enrolled and managed from one place. Each one is also maintenance and lifecycle cost, so we take the few inputs the algorithm needs and refuse the nice-to-have ones. Remote sites get a local maintainer.

Lawful by design

Personal data is handled to GDPR, and to Canadian and US privacy requirements. Fewer inputs is a deliberate policy, which is also the first answer a works council wants to hear.

What changes

Useful on its own

Track is the bottom of the stack and the cheapest layer to approve. It pays for itself as a record, and it produces the data every layer above it needs.

Your own record

One record, written by the sensors and the badge. Neither side of the contract can edit it afterwards.

Who, what, where, when

Every event carries the person, the place and the time, so an argument about the shift can be settled from data.

True durations

How long tasks really take, measured on the floor. This is what a plan should be built on.

Ready for the next layer

Everything OptiTrack captures lands in OptiSight, next to the systems you already run.

Start with your own record

Tell us what you verify today and how. The first call is thirty minutes and needs no system access.