Short Line Railroad Operations Software: Why Half Your Switching and Car Hire Revenue Never Reaches an Invoice

Why a short line loses revenue it has already earned

A crew works an industry lead on a Tuesday morning. They pull four loads and spot six empties, one of which is a bad order they set out on the house track. The conductor writes it on a switch list. At the end of the shift the list goes to the office, where a clerk keys the moves into the system, reports the interchange to the connecting Class I, and updates the customer's car list. Except the bad order set out never got reported, so car hire keeps accruing against the railroad on a car it does not have working for it. The spot on Tuesday for a customer whose contract charges per placement did not get billed because it looked like a repositioning move. And the storage clock on two cars that have been sitting since the fourteenth started whenever somebody remembered to start it.

None of that is dramatic. It is a few hundred dollars a day, every day, across a property that runs on thin margins and a general manager who is also the safety officer and half the sales department. Multiply by four properties in a holding company and you have a real number that never appears anywhere, because it is not a loss on a report. It is revenue that was never recognised in the first place.

The second failure mode is louder. Miss an interchange report to the connecting carrier, or send one with the wrong event time, and the car hire and interline settlement fall out of alignment. Now you are arguing with a Class I whose systems are automated and whose position is the default. You will lose that argument unless you can produce the event with a timestamp, and a switch list in a filing cabinet is not that.

Problem 1: industry messaging is rigid, and manual reporting is where the money escapes

Short lines live inside a fixed messaging vocabulary. Waybill and shipment information, advance interchange consists, car disposition, car handling events, terminal and ramp activity: each has a defined format, and the connecting carrier's systems consume them without sympathy. Railinc sits in the middle of the industry as the registry and clearing infrastructure, and equipment characteristics come from Umler whether you like the data or not.

The rigidity is not the problem. The problem is the gap between what happens on the ground and what gets into the message. A conductor radios a move, the office keys it later, and the event time is when the clerk typed rather than when the coupling happened. That is fine until a demurrage or car hire dispute turns on a four hour difference. A build closes that gap by capturing the event where it occurs, on a tablet or phone in the cab, offline capable because there is no signal in the cut, then generating the industry message from that record automatically. The event and the message become the same fact rather than two versions of it.

Problem 2: every short line's switching agreement is different, and generic billing cannot hold it

One customer pays per car switched with the first two moves free. Another pays a monthly minimum against a per car rate with a volume break. A third has a haulage arrangement where you move cars for the connecting carrier at a divisional rate that changes annually. A fourth is on a track lease with an embedded switching allowance. The industrial park has a reciprocal switch arrangement that only applies to certain commodities. Somewhere there is a paper agreement from 2009 that only the general manager remembers the terms of.

Packaged short line systems handle the common rate structures well and handle the unusual ones through workarounds, which in practice means a spreadsheet next to the invoice. The custom answer is to model the agreement as versioned rate rules attached to the customer and the track, applied automatically to the movement events the crew already captured, with an effective date so a rate change does not corrupt last month's history. The result is that switching, storage, weighing, transloading and any other accessorial is on the invoice because the event happened, not because a clerk remembered.

Problem 3: car hire and demurrage are opposite sides of one clock nobody runs

Car hire runs against you while a foreign car sits on your property. Demurrage and storage run in your favour while a customer holds a car beyond free time. These are the same underlying clock read in two directions, and most short lines run neither one properly because both depend on precise placement, constructive placement and release times.

The specific killer is constructive placement: the customer's track is full so the car waits on your siding, and whether the clock runs depends on notification and on the terms in your tariff. If the notification was a phone call, you have nothing. A build makes notification a system event with a timestamp and a delivery record, which converts an argument into a document. On the other side, prompt and accurate release reporting to the connecting carrier stops car hire accruing on cars you have already handed back. Both of these are unglamorous and both pay for the project.

Where RMI RailConnect, PS Technology and Bourque actually stop

RMI RailConnect is the default for a reason. It handles the industry messaging properly, it is known to the connecting carriers, and for a conventional short line it is a sound choice. Its limit is that the operating model is the vendor's, so when your property does something unusual, the change request goes into a queue with everyone else's and you wait. PS Technology brings genuine Class I operating pedigree, being a Union Pacific subsidiary, and that is exactly the tension: the products reflect big railroad practice and scale down with more process than a three person office wants. Bourque Data Systems is lean and well regarded on the billing and waybilling side for smaller properties, and correspondingly lighter when you want mechanical, track and crew management in the same system.

None of these is a bad product. The build case is not that they are deficient, it is that a holding company running five properties with five different switching agreement structures, two transload facilities and a car repair shop is running a business none of them were shaped for, and the difference gets absorbed by people and spreadsheets.

What a custom short line platform must include

Waybill and shipment management with proper handling of interline moves and rate divisions, because a division that is wrong by a small percentage across every car is the quietest revenue leak there is. Event capture in the field, offline first, with a switch list the conductor can actually work from in poor light and gloves. Automatic generation of the required industry messages from those events, with a monitor that shows unacknowledged and rejected messages rather than assuming success. Interchange reconciliation against the connecting carrier's view, so you find the mismatch the same week rather than at settlement.

Then car hire and demurrage with constructive placement handling and documented notification. Then customer billing driven by the agreement rules. Then a customer portal, because your shippers currently phone the office to ask where their cars are and that call is a person's whole morning. Then the mechanical side if you run a shop: bad order tracking, repair records and the industry repair billing files, since a shop that repairs foreign cars and does not bill for it correctly is running a charity.

What it costs, how long it takes, and what drives the number

Across the 2,000 plus projects Digital Heroes has delivered, this is the honest shape. A first release covering waybilling, field event capture, industry message generation and interchange reporting, plus car hire and demurrage clocks, runs $90,000 to $200,000 and ships in 14 to 20 weeks. A full platform adding agreement based billing, customer portal, mechanical and bad order management, crew and train sheets, and transload runs $250,000 to $600,000 phased over 8 to 15 months.

What drives the price up on short lines specifically: the number of properties and whether they share a rate structure, since each one tends to arrive with its own history. Transload and warehousing, which is a separate inventory business bolted to a railroad. Passenger or excursion operations, which brings ticketing and an entirely different safety and reporting posture. Locomotive and car maintenance depth, particularly if you bill outside work. And the number of connecting carriers, because each relationship has its own reporting expectations and its own settlement quirks.

What keeps it down: start with one property, the waybill and event core, and the two clocks. That is where the recoverable money is, and it funds the rest.

How to choose a developer for short line software

Ask them to explain constructive placement and how it affects the demurrage clock. This takes two minutes and it tells you immediately whether you are talking to a railroad software team or a general logistics team who will learn on your budget. Follow it with a question about how they would handle a car that is set out bad order and later repaired on your property, because that single scenario touches car hire, mechanical, the repair billing files and the interchange report at once.

Ask which industry message types they have generated and had accepted in production, and by which connecting carrier. The formats are documented, but a message that validates and a message a Class I actually accepts and acts on are different achievements. Ask how their field application behaves with no signal for six hours, because that is a normal Tuesday.

Ask how rate agreements are stored and what happens to last year's invoices when a rate changes. If the answer is that rates are edited in place, your historical billing is now unreproducible and your first audit will be unpleasant. Then get ownership in writing before kickoff: the repository, the infrastructure accounts and the right to hire anyone else. At Digital Heroes the client owns the code from the first commit, and for a railroad whose operating record is also its legal record, owning the system that holds it is not a negotiable point.