Skip to content
RoomAMD

RoomAMD Fleet

Every asset. Accounted for.

Every vehicle and machine on one timeline: where it is, what it's booked for, and when it's back. Two jobs that want the same machine show up as a conflict, with the fix.

Built by RoomAMDBuilt in LinkedTracks

Build something like this
The Fleet demo, built from the real LinkedTracks screens

The problem

What goes wrong without it

Spreadsheets can't see overlaps
Two planners book the same machine for overlapping weekends and nobody notices until the night.
Bookings ignore the journey
Most calendars show the hours of work, so a machine still in transit or waiting at the hub looks free.
Maintenance lives elsewhere
A unit goes to the shop and still shows as available in the plan.

Live demo

Two jobs want the same machine. See what clears it.

One machine's journey back from the first job overlaps its loading for the next. The system says why, offers a free unit of the same type, and books it in one step. Switch industries to see the same tool on utility and construction fleets.

RoomAMD FleetConflicts
The same timeline for locomotives, cars and track machines.
BR-04Ballast regulatorboth blocks claim it · Mar 12 → Mar 12, 2027 · 1 d overlap Available Ballast regulator: BR-07

NLR-W13: Travel out Thu, Mar 4, 2027 · 08:00 to Sat, Mar 6, 2027 · 23:00, 2 d 15 h; Closure Sat, Mar 6, 2027 · 23:00 to Mon, Mar 8, 2027 · 05:00, 1 d 6 h; Travel back Mon, Mar 8, 2027 · 05:00 to Fri, Mar 12, 2027 · 14:00, 4 d 9 h. NLR-W14: Travel out Fri, Mar 12, 2027 · 08:00 to Sat, Mar 13, 2027 · 23:00, 1 d 15 h; Closure Sat, Mar 13, 2027 · 23:00 to Mon, Mar 15, 2027 · 05:00, 1 d 5 h; Travel back Mon, Mar 15, 2027 · 05:00 to Tue, Mar 16, 2027 · 16:00, 1 d 11 h.

Releasing BR-04 or swapping in a free one, or moving a weekend's dates, clears it.

KJNLR-W13Signed off
closure Mar 6 → Mar 8, 2027
Holds itMar 4 → Mar 12, 2027
Travel out / back2 d 15 h / 4 d 9 h
Planning100% ready · train plan signed off
Lead to callPriya Raman
Booked byJun Park
closure Mar 13 → Mar 15, 2027
Holds itMar 12 → Mar 16, 2027
Travel out / back1 d 15 h / 1 d 11 h
Planning92% ready · consist confirmed (T-12)
Lead to callJun Park
Booked byAisha Mensah

No proposals yet · either corridor team or the unit’s own support team can propose a fix, and the leads approve it.

Pick a fix and the schedule updates. In LinkedTracks this is a proposal both leads sign.
UnitTypeStatus
Locomotives
LO-21Locomotive
Eastfield Yard · NLR-W13 · NLR-W14
Good · working
Railcars
BC-118Ballast car
Eastfield Yard · NLR-W14
Good · working
BC-121Ballast car
Eastfield Yard · NLR-W14
Good · working
BC-126Ballast car
Eastfield Yard · —
Good · working
Track machines
TM-12Tamper
Eastfield Yard · NLR-W13 · NLR-W14
Good · working
TM-15Tamper
Eastfield Yard · MNT-TM15
At shop
BR-04Ballast regulator
Eastfield Yard · NLR-W13 · NLR-W14
Good · working
BR-07Ballast regulator
Kestrel Junction · —
Good · working
ST-03Stabilizer
Eastfield Yard · NLR-W14
Good · working
Small plant
HR-07Hi-rail truck
Eastfield Yard · —
Good · working

Interactive demo on invented data. Nothing here connects to a live system.

Why calendars miss it

A booking is a journey, not a date.

A unit is committed from the moment it's loaded until it's back home. Fleet books that whole hold, so the overlap between one job's return and the next job's loading shows up as a conflict even when the work itself is days apart. Holds that only touch still count.

Live demo

Ask for a unit. See which ones are free.

A request names a type and a hold, from loading to return. Every unit of that type is checked against every other booking, including maintenance. The equipment lead confirms the request and the unit is held for that job and nothing else.

RoomAMD FleetBookings · NLR-W14

Pick a unit for NLR-W14

Hold of 4 d 7 h, loading to back home · Toronto time.

Ballast regulator · 1 of 2 free

Available Ballast regulator: BR-07

Interactive demo on invented data. Nothing here connects to a live system.

Capabilities

What Fleet does

Fleet inventory
Locomotives, cars, heavy plant, small plant and attachments, with specs, owners, locations and status.
Availability timeline
Units as rows, days as columns, every booking drawn as a bar. Overlaps stack and turn red.
Conflict detection
The same unit booked by two jobs whose windows overlap, or even touch, is a conflict.
Full booking windows
A booking holds the unit from loading to return, not just the hours of work.
Maintenance windows
Maintenance is booked like any other job, so the same conflict rule catches it.
Shortage warnings
"You are asking for 3 · 2 available · remove 1": requests are checked against what is actually free.
Return dates
A unit that's out of service still counts if it's due back before it's needed.
Booking requests
Ask for a resource for a window and see straight away which units are free. Requests move from requested to confirmed, or are released.
One booking per job
A unit can only be claimed once per job, enforced at the moment it's booked.
Agreed fixes
Each conflict comes with its fix in plain words: release the unit, swap in a free one, shorten the loading, shift the window, or cover it another way. Both sides agree before a fix is applied, and the decision is recorded.
Any fleet
Rail work trains, utility vehicles, construction plant: the same register, timeline and rules.

The fleet register, timeline, bookings, conflict rule and resolution flow are built in LinkedTracks. The demo on this page runs the same overlap and window logic on invented data.

Where it fits

Use cases

  • Rail and transitDe-conflict work trains and track machines across several weekend closures.
  • ConstructionShare cranes and excavators across sites without double-booking.
  • LogisticsSee trailer and vehicle availability across depots on one timeline.

Connected

Works with

Build your combination in the Platform Builder

See Fleet with your own operation in mind.

We'll walk through how it would fit your people, assets and processes, and what configuration it would need.