LOGISTICS AND TRANSPORTATION

Personalized software to run your yard and dock.

Production-grade ops software, built to fit on top of Blue Yonder TMS, Manhattan TMS, Trimble, or whichever fleet and yard system you already run. We build it. We deploy it. You pay only after it goes live.

  • Built to fit your yard
  • Live in weeks, not quarters
  • Pay only when it works
Opsima ops layer reading live data from Blue Yonder TMS, Manhattan TMS, and Trimble, surfacing yard fill, door scheduling, and dwell time for Yard 12.

Time spent at the gate is the biggest cost no one is tracking.

Detention at shipping and receiving facilities is the single largest measurable productivity loss in U.S. for-hire trucking, and it lands on the yard and dock teams managing the gate.

39.3%

of all truck driver stops at customer facilities resulted in detention in 2023, with delays exceeding two hours

135M+

industry-wide hours lost to driver detention across U.S. trucking in 2023 alone

$11.5B

in lost productivity to the trucking industry from driver detention in 2023, on top of $3.6B in direct expenses

Source: American Transportation Research Institute (ATRI), "Costs and Consequences of Truck Driver Detention," September 2024 (truckingresearch.org).

What changes in your yard and dock operation, week one.

Each capability runs on top of your existing TMS, YMS, and dispatch tools. Nothing rip-and-replace. Nothing your dock crew has to learn from scratch.

DOCK DOORS

Every door shows its trailer, dwell, and next slot

Receiving, shipping, and cross-dock doors in one board. Yard jockeys see where to spot the next trailer without calling the dock office.

ROUTE PROGRESS

Every truck on the road shows stop count and ETA

Dispatchers see route progress with completed stops, remaining stops, and projected delivery window. Late alerts fire before the customer calls.

DRIVER AVAILABILITY

Available, on-route, and off-duty in one view

Hours of service, next available window, and current load. Dispatch assigns the next run in seconds, not a round of phone calls.

TRACTOR UPTIME

Fleet health updated continuously, not after breakdown

Every tractor and trailer reports status. Maintenance sees MTTR per unit class. Dispatch sees available power units per yard zone.

SHIFT HANDOVER

Night dispatcher hands off a dashboard, not a notepad

Stuck loads, late pickups, downed tractors, and open dock doors. All current, all live. The morning dispatcher starts executing, not reconstructing.

BREAKDOWN ALERTS

Roadside events surface to dispatch and maintenance together

Driver reports breakdown. Dispatch sees location and load status. Maintenance sees unit history and nearest service point. One event, two views, zero phone tag.

Three breakdowns that compound every shift.

The Chassis Pool Blindspot

A driver arrives at the gate for a chassis pull. The chassis designated in the TMS was flagged defective by the yard tech three hours ago on the radio. The gate still shows it as available.

"We sent a driver 40 miles to pick up a chassis that was deferred for a brake inspection. Nobody updated the system. The radio call was the system."

Yard Operations Manager

The Overnight Breakdown Nobody Saw

A yard truck breaks down on the back row at 23:00. The night operator radios it in. By 07:00, pre-trip inspections start and the same truck is dispatched until the driver calls in from the fuel lane.

"The biggest source of morning chaos is equipment that broke down overnight and never made it into the dispatch board. The radio call existed. The record didn't."

Fleet Manager

The Gate Release Delay

When a container release depends on a specific yard truck or top loader that is down, the delay propagates to the driver, the import team, and the freight forwarder as a chain of phone calls.

"I'm calling five people to figure out why a gate release isn't happening. One call could replace all of them if someone could just see the board."

Terminal Manager

A live equipment status board built from field communication.

Every status update sent over WhatsApp, radio, or email becomes a tile on this board. Operations knows what is available right now: not what was available an hour ago.

Yard Operations Overview LIVE
Available: 0
In Maintenance: 0
Breakdown: 0
Reserved: 0
YT-01
Yard Truck
Available
YT-02
Yard Truck
Available
YT-03
Yard Truck
In Maintenance
YT-04
Yard Truck
Breakdown
YT-05
Yard Truck
Available
CH-A
Chassis Pool A
Available
CH-B
Chassis Pool B
In Maintenance
CH-C
Chassis Pool C
Available
CH-D
Chassis Pool D
Reserved
TL-01
Top Loader
Available
TL-02
Top Loader
Breakdown
FT-01
Fuel Truck
Available
FT-02
Fuel Truck
In Maintenance
RS-01
Reach Stacker
Available
RS-02
Reach Stacker
Available
GS-01
Gate Scanner Unit 1
Available
GS-02
Gate Scanner Unit 2
Breakdown
HT-01
Hostler Truck
In Maintenance
HT-02
Hostler Truck
Available
ST-01
Straddler
Available

The repair gets reported. The record writes itself.

Field communication flows through Opsima and becomes a structured work order automatically. No forms. No data entry. No end-of-shift catch-up.

Yard Maintenance
Yard Tech
YT-04 down, left air bag blown, back row B4
23:07
Supervisor
Logged. Parts ordered?
23:09
Yard Tech
Ordered from supplier, ETA tomorrow AM
23:11
Asset YT-04
Fault type Air bag failure
Location Back row B4
Technician Yard Tech
Parts ordered Air bag (ETA AM)
Fault reported 23:07
Work Order Record Created
Asset YT-04
Fault type Air bag failure
Location Back row B4
Technician Yard Tech
Parts ordered Air bag (ETA AM)
Fault reported 23:07
Synced to CMMS

What changes when operations and maintenance share one source of truth.

TMS shows chassis as available. Yard tech deferred it 3 hours ago by radio
Chassis status updated from yard tech communication; TMS pool reflects actual availability
Yard truck breaks down overnight. Dispatched at 07:00 by mistake
Overnight breakdowns visible in dashboard at shift start from radio reports logged in real time
Gate release delayed. Coordinator makes 5 calls to isolate cause
Equipment blocking the release is visible on the status board in one screen
Fleet maintenance records compiled from paper forms at week end
Records structured from technician messaging at time of repair, with timestamps
Driver wait time tracked manually by gate operators
Equipment readiness KPIs calculated automatically from status change events
Maintenance supervisor has no view of repairs in progress across the yard
Live view of every repair: who is working on it, what part is pending, estimated return

Every information gap between a yard breakdown and the dispatch board is a delay propagating outward.

The delay hits the driver, the importer, and the freight forwarder. One screen could prevent all of it.

Without Opsima
07:00
YT-01
Available
YT-04
?
CH-B
?
TL-02
?
GS-02
?
HT-01
?
YT-02
Available
RS-01
Available
YT-04 had an issue last night. Check with night operator. TL-02 might be down. Gate scanner 2 was flagged.
Handover complete: 30 minutes
With Opsima
06:45
YT-01
Available
YT-04
Breakdown
CH-B
In Maintenance
TL-02
Breakdown
GS-02
Breakdown
HT-01
In Maintenance
YT-02
Available
RS-01
Available
3 active breakdowns (YT-04, TL-02, GS-02)
CH-B maintenance since 22:30
Parts on order: YT-04 air bag (ETA AM)
Handover complete: 2 minutes

Overlays your existing TMS and YMS. Live in 3 days.

Opsima does not replace Oracle TM, SAP, or Kaleris YMS. It captures unstructured yard communication and feeds structured records back in.

Integrates with Oracle TM, SAP, Kaleris YMS, Navis eModal

Chassis and yard equipment status flows into your existing systems. No migration.

No new tools for drivers, yard operators, or technicians

They communicate as normal. Opsima reads the output. No behavior change.

Handles mixed fleets of owned, leased, and third-party equipment

All equipment tracked on one board regardless of ownership. Attribution maintained in reporting.

Live in 3 days

No hardware. Connect to existing communication channels and see structured equipment data within 72 hours.

Questions from operations and maintenance teams

Can Opsima track third-party leased equipment alongside owned fleet?
Yes. All equipment is tracked by asset ID regardless of ownership. Leased and owned equipment appear on the same board with ownership attribution in reporting.
How does it handle chassis that move between multiple depots?
Opsima tracks chassis by ID. When a chassis is reported at a different depot via field communication, its location updates automatically.
Does it integrate with our existing YMS?
Yes. Opsima can feed structured equipment availability data into Kaleris, Navis, and other YMS platforms via API.
How does it work for 24/7 operations with rotating maintenance crews?
Opsima captures communication continuously. Every shift's updates are captured and timestamped automatically. The board is always current.
Can yard operators report issues directly through the same communication channels?
Yes. That is exactly how it works. Operators radio or message issues as they always have. Opsima reads those messages and creates structured records.
Ready to ship

Personalized ops software for your yard. Live in weeks, paid for when it works.

Book a working session with our solution team. We map the yard, the integrations, and the timeline before anything else.

SSO Isolated environments Audit trails Dev → Review → Prod