Bourque Data Systems Alternatives for Short Line Operations and Railcar Fleet Management

The question behind the search

When a general manager searches for an alternative to an established rail software supplier, the surface reason is usually a feature request that went nowhere or a screen that looks its age. The real question underneath is almost always about dependence. You are running your billing, your car records and your interchange on a product from a company far smaller than the railroads it serves, and somebody on the board has asked what happens if the people who know the code retire, or if the company is acquired, or if the platform stops being modernised. That is a fair question and it deserves a fair answer rather than a sales pitch.

The second driver is growth or acquisition. A short line group buying properties finds itself running two or three different systems, each fine on its own, none of them producing a comparable picture of carloads, revenue, car hire and customer service across the group. The third is the customer, who now expects self service visibility as a baseline and does not much care that rail interchange data arrives on a schedule set by other railroads. These three drivers point at different solutions, so decide which one you actually have before spending anything.

What long-tenured niche vendors do better than expected

Small sector vendors survive for decades for a reason, and the reason is rarely marketing. They know the work. Waybilling, interchange, per diem, demurrage, repair billing and customer invoicing in short line railroading are full of specific practice that is written nowhere convenient, learned only by doing it, and unforgiving when it is wrong. A supplier who has processed this data for a hundred railroads has absorbed exceptions that a new platform would rediscover expensively, one dispute at a time.

The economics are also usually in your favour, which buyers forget while comparing screenshots. Small vendors carry small overheads, and the annual cost of a mature niche product is frequently less than the annual maintenance on something you would build to replace it. Support tends to be direct: you call a person who knows your railroad rather than opening a ticket in a queue. That is worth a great deal at two in the morning when a billing run failed and cars are already moving. Weigh that honestly before you weigh anything else.

The four honest concerns

Data portability is the first and most important. Ask now, while you are happy, for a documented full export of your data in an open format, and test it. If the answer is slow, expensive or vague, you have learned something important about your position, and you should fix that before it becomes urgent. Ownership of your operating history is not a favour, it is basic risk management.

Continuity is second. Small vendors are acquired, merged and eventually succeeded. Ask about the support model, the size of the development team, and what a transition would look like. Third, the modern surface: customer portals, mobile crew reporting and analytics require investment cadence that is difficult for a small team maintaining a stable core, and this is where niche products most often sit behind. Fourth, integration. Your accounting, your maintenance records, your fuel and your customer systems all want the same data, and if the only route in and out is a report, you are paying people to retype numbers. None of these four is a reason to leave on its own. Together they are a reason to own your data layer.

What is actually on the menu

Stay and secure the data. Negotiate a documented export and, better, a regular automated feed into a store you control. That single change converts vendor risk into a manageable dependency and unlocks everything else on this list. Stay and extend, which follows directly: with your own data store, build customer visibility, group reporting and analysis without touching the operating system. Most short lines should stop here, because the value is high and the risk is close to zero.

Switch vendors. RMI RailConnect and PS Technology are the other established options for short line and regional operations, and switching is justified when a functional gap is structural, when support has genuinely deteriorated, or when a holding company wants a single platform across properties. Understand the trade: you exchange one specialist dependency for another, so the data portability question applies equally to whoever you move to. Build entirely, which is defensible at group scale or for railcar fleet management, and rarely for a single small property's core operations.

The custom build case for railcar fleets

Railcar fleet management is the strongest custom case in this sector, and it is stronger for car owners, lessors and shippers with private fleets than for railroads. The reason is contractual variety. Repair billing under industry interchange rules, mileage credits, lease terms with different responsibility splits, regulatory inspection and requalification dates, storage arrangements and damage claims all combine differently for every fleet, and standard products necessarily model the common shape. Fleet owners consistently maintain spreadsheets to handle the difference, and those spreadsheets are where money leaks: a missed rebill, an inspection date that surfaced late, a lease renewal nobody flagged.

A custom fleet system that ingests movement and repair data, applies your specific contract logic and drives exception alerts is a bounded project with a directly measurable return. The same argument holds at holding company level for operations: one data layer, one customer portal, one set of comparable metrics across properties, with each railroad still clerking in whatever system it uses today. What does not justify custom is replacing the waybilling and interchange core of a single small railroad. That work is unglamorous, industry governed, changes without asking you, and is genuinely cheaper to rent.

How to leave without breaking billing

If you do decide to move, revenue is the risk. Billing sits at the end of a chain that starts with a movement event, and every link has to survive the transition, so plan around the billing cycle rather than the calendar. Export first and completely: customers with contracts and rate structures, waybill and movement history, car ownership, hire and repair records, demurrage agreements and history, equipment and location reference data, and at least several years of invoices with their supporting detail.

Run parallel through two complete billing cycles and reconcile invoice by invoice, not in aggregate, because aggregate totals can match while individual customers are wrong. Verify car hire settlement separately, since it is the quiet one. Keep an inventory of every external connection and message type, confirm each partner contact, and test rejections deliberately rather than hoping. Pilot on the smallest property if you own several. Train clerks one at a time with a documented manual fallback, keep the old system readable for years for disputes and audits, and never schedule cutover into a seasonal peak or a large customer's shutdown period.

Cost bands

Niche rail products are usually priced per railroad, scaled by size, and the annual number is often modest by software standards, which is exactly why replacing one on principle is poor economics. Get the cost of a data export written into your agreement. On the custom side, from Digital Heroes delivery experience: a railcar fleet management and repair billing layer with contract logic, inspection tracking and exception alerts runs roughly $50k to $120k over 10 to 16 weeks. A customer visibility portal fed from your existing operating data runs roughly $40k to $90k. A holding company data and reporting layer across several properties runs roughly $45k to $100k. A full operations and billing platform, with interchange messaging left to a specialist, runs $140k to $350k and should only be undertaken at group scale with a technical owner in post. Hosting at this scale is a small monthly infrastructure cost.

What I would tell a general manager

Do not replace a working niche system because it looks dated. Do secure a tested, documented export of your own data this quarter, whatever else you decide, because that is the difference between a supplier relationship and a hostage situation. Spend your discretionary budget on the customer portal and, if you own or manage cars, on fleet and repair billing, because both produce measurable returns and neither touches anything that moves a train. Consider switching vendors only when you can name the structural gap in a sentence, and consider a full custom build only at group scale or when your fleet contracts have outgrown what any packaged product models. Leave interchange messaging and car hire settlement alone in every scenario.