Short Line Railroad Operations Software: Build Custom or Buy RailConnect

What the off-the-shelf railroad products actually do well

The honest answer for a single property is license something and get back to the track. If you run one railroad, one connecting carrier and a customer list you can name from memory, a packaged system is the right purchase, and a bespoke build is money that should be in ties and ballast.

RMI RailConnect is the default for good reasons. It handles the industry messaging properly, the connecting Class I carriers know it, and the waybilling and car management model matches how a conventional short line actually operates. PS Technology brings genuine Class I operating pedigree as a Union Pacific subsidiary, which shows in the depth of its dispatch and operating products. Bourque Data Systems is lean and well regarded on waybilling and billing for smaller properties, and for a railroad whose main problem is invoicing accuracy it is often the shortest path.

What all three buy you is the part you should never write yourself: conformance with the Association of American Railroads message set and the Railinc infrastructure around it. Waybill and shipment information, advance interchange consists, car disposition, car handling events, terminal and ramp activity, equipment characteristics drawn from Umler, and the interline settlement path. Those formats are documented and rigid, and getting a message accepted and acted on by a Class I is a different achievement from getting it to validate.

There is also a floor below the product. A tourist or excursion operation running weekends, or an industrial switcher with two customers, needs a disciplined switch list and a spreadsheet. Buying a railroad operating platform for that is a subscription with no problem attached.

Where they stop: the switching agreement nobody has written down

Here is the workflow packaged products model badly, and it is where your margin lives. 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 at a divisional rate that changes annually. A fourth sits on a track lease with an embedded switching allowance. The industrial park runs a reciprocal switch arrangement that applies only to certain commodities. Somewhere there is a paper agreement from 2009 whose terms live in the general manager memory.

Packaged systems handle the common rate structures well and handle the unusual ones through workarounds, which in practice means a spreadsheet open next to the invoice. Every accessorial that depends on a judgement rather than a rule leaks: the spot that looked like a repositioning move, the second placement nobody billed, the storage clock that started when somebody remembered.

The second workflow they model badly is constructive placement. Demurrage and car hire are the same clock read in two directions, and both turn on precise placement, constructive placement and release times. When the customer track is full and the car waits on your siding, whether the clock runs depends on notification and on your tariff terms. If the notification was a phone call, you have nothing, and the Surface Transportation Board demurrage billing rules expect specific supporting information on the invoice you send. A switch list transcribed at the end of a shift produces event times that will not survive a dispute with a carrier whose systems are automated and whose position is the default.

The arithmetic: per car licensing against an amortised build

Run this with your own numbers. Take your annual licence, support and hosting, add the loaded cost of clerical hours spent keying switch lists and reconciling interchange, and divide by carloads. That is your true system cost per car.

Worked example to replace with yours. A property at 12,000 carloads a year paying $55,000 in licence and support, plus one and a half clerical roles at a loaded $52,000 each spent mostly on data entry and reconciliation, carries roughly $133,000 a year, or about $11 per car. Across five years that is $665,000.

A first release build at $140,000, with year two at 17 percent annually, runs about $435,000 across the same five years, and the marginal cost of the fourth property is close to zero rather than another licence. The crossover in this category is roughly 25,000 to 30,000 carloads a year on a single property, and it arrives far sooner across a holding company: two properties on different agreement structures usually cross at about 15,000 combined carloads, because the second property adds process variety rather than volume.

The line nobody models is recovered revenue. Storage, weighing, transloading and second placements that never reached an invoice are not a cost saving, they are revenue that was never recognised. Sample thirty days of switch lists against thirty days of invoices before you build the model.

What a custom build actually costs

In Digital Heroes delivery experience, a first release covering waybilling, offline field event capture, automatic generation of the industry messages, interchange reporting with acknowledgement monitoring, and the car hire and demurrage clocks runs $90,000 to $200,000 in 14 to 20 weeks. A full platform adding agreement based billing, a 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.

Data migration runs 10 to 25 percent of the build. Customers, tracks, equipment and open waybills move cleanly. Historical billing usually does not, because rates were edited in place in the old system and last year invoices are no longer reproducible. Load closed history as read only archive and start clean with versioned, effective dated rate rules.

Year two is 15 to 20 percent of build cost annually. That covers hosting, support during a Sunday outage rather than office hours, and outside change: a connecting carrier altering what it expects, a Railinc service revision, a new customer agreement that does not fit any existing rule shape.

What drives the number up on short lines specifically: the number of properties and whether they share a rate structure, transload and warehousing, passenger or excursion operations, locomotive and car maintenance depth if you bill outside work, and the number of connecting carriers, since each relationship has its own reporting expectations and settlement quirks.

The four situations where building wins

Regulatory fit comes first. Your operating record is also your legal record. Federal Railroad Administration accident and incident reporting, hours of service records, mechanical inspection evidence and drug and alcohol programme records all have to be produceable years later, and the same event capture that bills a switch can carry them. A railroad that builds this puts its evidence and its invoices on one timestamped foundation instead of two.

Scale economics is second, at the carload figures above.

Third is a workflow that is your competitive advantage. Short lines win business on responsiveness, and a customer portal showing car location, placement history and storage exposure removes the phone call that eats a clerk morning. Shippers choosing between a short line and a truck notice which railroad can answer without calling anyone back.

Fourth is integration sprawl. Count them: the operating system, accounting, the Railinc services you consume, the connecting carrier interfaces, a mechanical or shop system, and a fuel or locomotive management tool. When three or more must agree before a settlement is right, and the agreement happens in a workbook, the build is already being paid for in salary.

How to decide in a week

Pull thirty consecutive days of switch lists. Take every event on them and try to find the matching line on an invoice or a car hire record. Give a clerk one day for it and stop when the day is over.

Then count three numbers: events that reached an invoice, events that should have but did not, and events whose recorded time differs from the handwritten time by more than two hours. The third number is the one that predicts how a dispute with a Class I will go. If unbilled events exceed roughly three percent of the total, or if half your event times were transcribed hours after the coupling, configuration will not fix it and you have your answer.

Run a second, faster test on agreements. Ask your general manager to hand you every switching, haulage and track lease agreement in force. If any of them exists only on paper, or only in memory, writing them down as versioned rules is the real project and it takes weeks of somebody time regardless of who builds the software.

Then buy the cheapest thing that ends the argument, a paid discovery phase. Digital Heroes writes a signed product requirements document before any code exists, covering the event model, agreement rule structures, message generation, integrations and acceptance criteria, and you own it whichever firm you appoint. Contracts run through our India LLP, US LLC or UK LTD entity, so the intellectual property assignment sits under law your own counsel already reads. We are wrong for you if you want a bench of anonymous contractors, or if you run one property at 4,000 carloads and want permission to build. We will tell you to license.

Book a 30-minute call with Digital Heroes and get a written plan and a fixed quote within 48 hours.