How to Automate RSI Logistics Rail Command

Rail Command is where a shipper finally sees its own fleet

Rail is the one mode where the shipper does not hold the information. A truckload has a driver with a phone. A container has a tracking page. A railcar reports through Car Location Messages, generated as the car passes the railroads' reporting points, and until somebody assembles those messages a shipper has a hundred assets loose in North America and a general sense of west.

Rail Command is RSI Logistics' rail transportation management system, built for shippers and receivers rather than railroads: manufacturers, chemical and petroleum companies, agricultural producers and distributors. It takes the CLM feed, GPS where the fleet carries it and the railroads' own reporting, and turns it into a fleet somebody can look at.

Inside sit the things a rail group works with daily: electronic bills of lading and orders, railcar tracking with its ETAs, lease and maintenance records, and the freight bills from every railroad that touched the move.

The disputes all have a deadline and a login

Rail bills for time, and time is where the arguments are.

A car sits at your plant past its free time and demurrage accrues, at a rate set in a tariff published on the railroad's website and revised without notice. A freight bill arrives carrying accessorials: switching, weighing, storage, a reconsignment somebody authorised verbally in March. Deciding whether each is right means opening the railroad's customer portal, reading what it says happened to that car, and setting that against your records. Disputes have windows, and a window that closes has settled the question.

The fleet has its own version. A lessor's portal holds the lease expiry and mileage credits. A repair shop bills for work on a car before the estimate arrives. The customer at the far end will not release a proof of delivery until somebody signs into their receiving system and asks.

Every one is a different website, and not one of them sends anything anywhere.

RSI Logistics Rail Command

Accessorials questioned while it matters Each charge on a freight bill set against what the railroad's own portal says happened to that car, the week the bill lands.

Demurrage argued from evidence Placement and release records compared with the charge before the dispute window closes, with the arguable ones separated from the fair ones.

Lease dates that count themselves down Expiries and mileage credits read from the lessor's portal, so no car rolls past its lease end without anyone noticing.

Freight audit and demurrage reporting run on the feeds that arrive

None of that is a gap in the product. Rail Command handles the data it receives better than a spreadsheet ever did.

Railcar tracking with enhanced ETAs turns raw location messages into an arrival estimate a planner can use. Automated exception logs surface the cars that stopped moving, so a delay is a worklist entry instead of a phone call from a customer. Demurrage reporting calculates accrual against your own rules and produces invoice-ready output, with a dashboard showing which cars are in actual placement and which are accruing. Freight audit checks the bills against the rates it holds, with tariff and fuel surcharge updates applied. Rail rate management, lease management and railcar maintenance keep those records in one place.

The boundary is the feed. All of that runs on Car Location Messages, GPS, railroad reporting and the rates you loaded, which is precisely what the industry publishes to shippers in machine-readable form. The rest of rail life is published to a screen instead: a railroad's customer portal, a lessor's site, a repair shop's invoice, a terminal operator's inventory page, a customer's receiving system. No feed carries any of it.

Every accessorial gets questioned while the window is open

Which disputes get raised is currently decided by who had a free afternoon. It could be decided by which ones are worth raising.

Each accessorial on a freight bill set against what the railroad's own portal says happened to that car, in the week the bill arrives, not the quarter it is reviewed. Demurrage charges compared with your placement and release records before the window closes, with the ones worth arguing separated from the ones that are simply true. Tariff and fuel surcharge pages read on the railroad's site, so a rate change is a note on Monday, not a surprise at audit.

The fleet side takes the same discipline. Lease expiries and mileage credits read off the lessor's portal and counted down, because a car past its lease end costs money quietly. Repair invoices matched against the shop's own record. Proofs of delivery collected from each customer's receiving system and filed against the shipment, so a cargo claim opens with its evidence attached.

The line stays where it always is. Gathering, comparing and preparing a dispute is safe every morning. Filing that dispute, or telling a customer their claim is denied, is a person's signature.

The clock runs whether or not anyone is watching

Demurrage accrues on a Sunday. A dispute window closes on a day nobody was in. The work that protects the money is not analysis. It is somebody opening six railroad portals and reading dates.

WebRun is an AI agent that works a real Chrome browser, signed in as you. It opens the railroad's customer portal, the lessor's site or the customer's receiving system, reads the screen, and writes it next to the car in the sheet your rail group works from.

It runs on your schedule in your own private environment, and you can watch a run and stop it mid-way. Anything that files a dispute or answers a customer is drafted and waits for a person.

The workflows below are already built, and each one names the sites it opens.