EQUIPMENT TRACKING · AIRPORTS & GSE

GSE dispatched to a stand that has no unit available.

Belt loaders, tugs, and GPUs move between stands dozens of times per shift. Your CMMS says available. Your ramp supervisors know three of the four requested units are committed or under repair. We capture real GSE state from radio and ramp comms, and write it back to your CMMS and ops system. Personalized software to run your ground operations.

Runs on your existing CMMSRadio + WhatsApp + GPS + RFIDRamp-speed state capturePay only after go-live

THE MISSING UNIT

The system says four belt loaders are available for that stand. The ramp super knows two are already out and one is in the shop. By the time we find a fourth, the flight is delayed.

How the night actually went

10:00 Turn schedule shows four belt loaders needed at Stand 24 in thirty minutes.
10:15 BL-09 goes unserviceable, hydraulic fault. Mechanic reports it over radio. Nobody updates the CMMS.
10:28 Ramp coordinator dispatches BL-09 to Stand 24. CMMS still shows it as Available.
10:35 Stand 24 calls back: no belt loader on stand. Turn starts late. Aircraft door open, no bags moving.
10:45 Ramp supervisor locates a spare BL manually via radio. Fifteen minutes lost.
11:30 Shift end. CMMS work order for BL-09 created from memory. State was wrong all shift.

What slips when the radio knows and SAP doesn't.

The off-system gap

GSE changes state on the ramp every few minutes. The radio knows. The CMMS finds out at shift end, if at all. Every availability figure the ramp coordinator uses is built on data that is already wrong when the turn schedule runs.

Pool availability figures computed on data hours out of date

Dispatch runs blind

Your ops system shows GSE as Available that is unserviceable, committed to another stand, or missing from the yard. The ramp coordinator dispatches to it, then handles the exception over the radio while the flight waits.

Turn delays driven by status lag, not equipment shortage

PM drifts into corrective

GSE operating hours filled in from estimates cause PM intervals to drift. Units hit corrective faults on the ramp during active turns. You pay breakdown call-out rates on equipment that was overdue for a scheduled service.

Corrective costs run several times planned maintenance

From radio call to live in your system, without a 14-month IT project.

1
Listen

Connect to every channel that knows real GSE state.

We integrate with the systems your ground operations already run. CMMS (SAP PM, Maximo, HxGN EAM, or your own), your ops system, WhatsApp, Teams, radio transcript, and your existing GPS and RFID feeds. Nothing for ramp agents or mechanics to install. The ramp keeps working exactly as it does today.

CMMS status and work-order write (SAP PM, Maximo, HxGN EAM, others)
Ops system GSE pool count update
WhatsApp Business, Teams, radio transcript ingest
GPS/IoT and RFID feed integration
Phase output
LISTEN · DELIVERABLE
CMMS status and work-order write (SAP PM, Maximo, HxGN EAM, others)
LISTEN · ARTIFACT
Ops system GSE pool count update
2
Spec

A working session with the people who run the ramp.

Your GSE manager, ramp supervisor, and IT walk us through one real turn. We capture equipment classes (belt loaders, tugs, GPUs, steps, buses, de-icers), state-transition rules, the ops fields that need to stay current, and how dispatch reacts when availability changes. The workflow is sketched in their words, then turned into a structured spec and a mockup you can read before any code is written.

Structured working session, no IT ticket required
State-transition rules and CMMS field map captured
Spec + mockup written from your operation's own language
Phase output
SPEC · DELIVERABLE
Structured working session, no IT ticket required
SPEC · ARTIFACT
State-transition rules and CMMS field map captured
3
Build

Real code, in staging, on your data.

The GSE tracking workflow is built end to end in a staging environment connected to your real systems. Ingest from radio, WhatsApp, GPS, and RFID, state classification, CMMS write, and ops pool-count update. Your IT reads the codebase, the integrations, and the risk report before anything touches production. No black box.

Real code, any language, no complexity ceiling
Staging connected to your real CMMS and ops system
Codebase, risk report, and rollback handed to IT to review
Phase output
BUILD · DELIVERABLE
Real code, any language, no complexity ceiling
BUILD · ARTIFACT
Staging connected to your real CMMS and ops system
4
Go-live

IT deploys. We run it with you on real turns.

IT promotes the workflow to production. We run it with you on real turns until the pool count in your ops system matches what the ramp coordinator sees on the ground. You pay only after it goes live and the availability numbers on real turns match the spec.

One-click production deploy, one-click rollback
Run-with-you period on real turns
Payment after the workflow produces the agreed outcome
Phase output
GO-LIVE · DELIVERABLE
One-click production deploy, one-click rollback
GO-LIVE · ARTIFACT
Run-with-you period on real turns

GSE tracking, on your existing CMMS and ramp ops system.

Without Opsima
  • GSE state changes captured over radio, never written to the CMMS
  • Pool count in ops system lags ramp reality by the length of a full turn
  • Ramp coordinator dispatches to units that are unserviceable or committed
  • CMMS work orders created from memory at shift end
  • PM schedule runs on estimated unit hours, not actual operating time
  • Corrective faults on the ramp during active turns, delays follow
With Opsima
  • Real GSE state captured from radio, WhatsApp, GPS, and RFID in real time
  • CMMS status updated within minutes of any state change
  • Ramp coordinator allocates to real availability, not last-turn memory
  • CMMS work order auto-created with correct timestamp and fault code
  • PM schedule runs on actual unit hours, zero manual entry
  • Corrective events on the ramp drop as PM intervals hold
Real-time
GSE pool availability
0
Manual status corrections per shift
100%
Ramp state changes captured

Numbers we have actually measured.

Industry-typical
~60%
Share of GSE state changes that never reach the CMMS on the turn they happen
Off-system operational reality, observed across ramp operations
Industry-typical
3-5 turns
Typical lag before an unserviceable unit is corrected in the ops system
Industry-observed across airport ground-handling operations
Field-observed
0
New forms or workflow changes required for ramp agents after go-live
Field-observed across Opsima equipment-tracking deployments
Field-observed
100%
Share of GSE state events captured on the shift they happen, post-deployment
Field-observed across Opsima equipment-tracking deployments

Before, and after.

The system says four belt loaders are available. The ramp supervisor knows two are already out and one is in the shop. By the time we find a fourth, the flight is delayed.

H
Head of Ground Support Equipment
International airport

We found 45 minutes of lost productivity per day that we didn't even know existed. The system captures everything from WhatsApp without changing how our crews work.

C
COO
Large-scale ground handling operation
Working session

Your operation.
Your real data.
Software built for it.

Tell us one process you have given up on fixing. We build it on your actual systems and run it with you. You pay only after it goes live.

On your existing stack
Live in weeks, not quarters
Pay only after go-live
Built and run for you