Quick summary
- In ARMS™, a click can move a real car, release a transload, post a shipper’s accrual, or reach a connecting railroad. Reliability has to mean more than “the site stays up.”
- ARMS is built so the live operation only moves when someone means it to, whether that’s a railroad, a shipper, a transload terminal, a car owner, a switching operation, or an intermodal terminal. That includes who can see what and how far automation is allowed to go.
- It also includes the sandbox: a working copy of your actual data, sealed so a practice move can’t become someone else’s inbound message.
- The result isn’t a slower team. It’s one that can try a setting or train a new hire and still trust that production, and everyone outside the building, will stay untouched.
The problem: uptime isn’t the whole reliability story
Ask most software vendors what “reliable” means and you’ll get an uptime number. Percent availability. A status page.
That’s not the whole answer anywhere ARMS runs. The click is different in each business. The consequence is a real move, a real invoice, or a real message.
On a railroad, move a car and a real car moves. Send an interchange and a connecting railroad may already be acting on the message.
At a transload terminal, record a transfer just to see the screen, and both the inventory and the customer’s invoice can move.
For an industrial shipper, the waybill and the accrual are the books. Approve one by accident and finance is working from a number nobody meant.
For a car owner, car hire is money in or money out. It doesn’t stay a figure on the screen.
In industrial switching, a plan can become the move the crew performs, and the bill that follows.
At an intermodal terminal, a gate move is a container leaving the yard, tied to a charge.
Flip a billing setting “just to look,” in any of these, and the next shift works under that setting.
There’s no undo button for the industry. Reliability can’t only mean the system stayed up. It has to mean the system did only what someone meant it to do.
What railroad software reliability actually requires
A stable server is necessary. It’s not sufficient.
- Access that matches the operation, not a generic role list, so a dispatcher, a transload clerk, a shipper’s accounting team, and a customer on the Customer Portal each see what they should and nothing more.
- A place to practice that behaves like the real operation, with no path back to production.
- Automation that knows its own limits, so a scheduled job can’t quietly chew through live work, and a change gets logged instead of living in someone’s memory.
The sandbox: a worked example
We could give you a demo railroad with fake cars. That’s easier to build. It’s a poor rehearsal for your day: your customers, your tracks, your exceptions.
We could keep the sandbox connected to the industry’s network, and count on people to be careful.
So ARMS includes the sandbox: a working copy of your actual data. The railroad case makes it clearest: cars, interchange, Railinc. The bar is the same at a terminal or a shipper. Two things about it matter more than the button in the header.
It’s your operation, not a toy. The cars, customers, inventory, and screens are the ones your team already knows.
It can’t leave. The sandbox can’t notify a connected carrier. A training move doesn’t become a real interchange. A practice click doesn’t notify another railroad. The same rule holds for the rest of ARMS: a practice click shouldn’t become a live invoice, a live inventory move, or a message to someone outside the building.
Want to see exactly how it works? The sandbox guide covers entering and exiting, how fresh the copy stays, and what happens when two people are working in it at once.
Why this matters beyond the checklist
A railroad, a terminal, and a shipper are already balancing enough risk in the physical world: car placement, a truck at the rack, crew safety, interchange timing. The software underneath shouldn’t add a risk you can’t see coming.
Once a team knows ARMS won’t send something by accident, they stop treating every click like it might. That’s the reliability Cedar AI actually cares about.
One platform. Only the moves you meant.
Curious what reliability looks like for your operation? Schedule a demo
Already running ARMS? Reach out to Cedar AI support to turn on the sandbox for your railroad.