EQUIPMENT TRACKING · WAREHOUSING AND 3PL

The forklift count your WMS shows is always wrong.

At shift start, your supervisor allocates forklifts and reach trucks before knowing how many are serviceable. The unit marked available is on charge in the corner. The one marked in-use is idle in Aisle 7. We capture the real state from radio, WhatsApp, and maintenance channels, and write it back to your WMS. Personalized software to run your warehouse.

Runs on Manhattan WMS, SAP EWM, Blue YonderForklift, reach truck, order picker, dock equipmentWhatsApp + Teams + radio capturePay only after go-live

THE MONDAY MORNING COUNT

I start every peak shift with a mental count that is 8 hours old. By 06:15 I have already promised Zone 4 a reach truck that is still on charge.

How the night actually went

22:00 Night shift ends. Three forklifts and one reach truck go on charge. No live update reaches the WMS.
05:45 Outgoing night supervisor leaves a handover note: 'FL-03 hydraulic issue, RT-03 may still be on charge.'
06:00 Inbound supervisor reads the note. WMS still shows FL-03 and RT-03 as Available.
06:10 Zone 4 picker assigned to RT-03. Driver walks to the charger bay. Truck is still at 40%.
06:20 Zone 4 falls behind. Supervisor calls around trying to find an available unit.
07:05 Night tech returns to clarify FL-03 status. Work order eventually entered from memory, fault code best-guess.

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

The off-system gap

Every equipment status change that does not reach your WMS in real time becomes a hole in the data your shift runs on. Zone assignments, pick route efficiency, and maintenance scheduling are all based on records filled in hours later, from memory.

Shift starts on an equipment count that is 8 hours old

Dispatch runs blind

Your WMS still shows the dead forklift as Available. Zone assignments are made on a count that does not match the floor. The supervisor discovers the discrepancy when a picker walks back empty-handed.

Peak throughput lost while supervisor reconstructs real availability

PM drifts into corrective

When battery faults and hydraulic issues are logged hours after the fact, PM schedules drift behind reality. Deferred maintenance slips into the next breakdown. You pay corrective repair rates on equipment you should have maintained.

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 the channels your warehouse floor already uses.

We integrate with the systems you already run. WMS (Manhattan, SAP EWM, Blue Yonder, Körber), your CMMS (Maximo, others), WhatsApp Business, Teams, and your radio transcript source. Nothing for operators or mechanics to install. Nothing in their workflow changes.

WMS equipment-status update (Manhattan, SAP EWM, Blue Yonder, Körber)
CMMS work-order creation (Maximo, SAP PM, others)
WhatsApp Business, Teams, Slack, SMS ingest
Radio transcription API
Phase output
LISTEN · DELIVERABLE
WMS equipment-status update (Manhattan, SAP EWM, Blue Yonder, Körber)
LISTEN · ARTIFACT
CMMS work-order creation (Maximo, SAP PM, others)
2
Spec

A working session with the people who run the shift.

Your warehouse manager, maintenance lead, and IT walk us through one real equipment failure. We capture asset classes (forklifts, reach trucks, order pickers, dock levelers, sorter lanes), fault categories, escalation paths, and the WMS fields you need updated. 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
Spec + mockup written from your team's own language
Asset classification, fault rules, and WMS field map captured
Phase output
SPEC · DELIVERABLE
Structured working session, no IT ticket required
SPEC · ARTIFACT
Spec + mockup written from your team's own language
3
Build

Real code, in staging, on your data.

The workflow is built end to end in a staging environment connected to your real systems. Ingest, classification, WMS write, CMMS work order, zone reassignment logic. 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 WMS and CMMS
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 WMS and CMMS
4
Go-live

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

IT promotes the workflow to production. We run it with you on real shifts until it produces what we agreed on: captures every equipment status change, updates the WMS, opens the work orders, and keeps zone assignments honest. You pay only after it goes live and the count in the system matches the floor.

One-click production deploy, one-click rollback
Run-with-you period on real shifts
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 shifts

Equipment tracking, on your existing WMS and CMMS.

Without Opsima
  • WMS equipment count 8 hours old at every shift start
  • Forklifts marked available are on charge or in maintenance
  • Zone assignments made on a count nobody can verify
  • CMMS work orders entered at shift end, from memory
  • Dock leveler faults radioed to the wrong team, 90-minute holds
  • Maintenance scheduling based on incomplete, late-logged records
With Opsima
  • WMS updated from radio and WhatsApp the moment status changes
  • Every available unit confirmed serviceable before zone assignment
  • Supervisor sees real equipment count at shift start in under 2 minutes
  • CMMS work order opened automatically with correct timestamp and fault code
  • Dock and sorter faults visible to maintenance and operations simultaneously
  • PM schedules based on timestamped, complete maintenance records
<3 min
WMS updated after status change
0
Manual steps for capture
100%
Shift equipment events captured

Numbers we have actually measured.

Industry-typical
~60%
Share of equipment status changes that never reach the WMS without a structured capture layer
Off-system operational reality observed across warehouse and 3PL operations
Industry-typical
8 hrs
Typical gap between last overnight status change and a supervisor seeing it at shift start
Shift-start knowledge gap observed across warehouse operations
Field-observed
<3 min
WMS and CMMS updated after equipment status change, on the agreed spec
Field-observed across Opsima warehouse deployments
Field-observed
0
Manual steps the supervisor takes during equipment status capture
Field-observed across Opsima deployments

Before, and after.

I start every Monday peak with a mental count that's 8 hours old. By 06:15 I've already promised zone 4 a reach truck that's still on charge.

W
Warehouse Operations Manager
Regional DC, 3PL operator

We held three inbound trailers for 90 minutes because the leveler fault was radioed to the wrong team. Nobody knew who was fixing it.

S
Site Maintenance Supervisor
Fulfillment center

No one needs to feed the system. It feeds itself.

H
Hagai Shenar
Deputy CEO, Taavura Earth Moving
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