Every order, every BOL, every receive event, every exception, and every month of forecast-versus-actual — on one screen, in the same tool, by the same person who has to answer for all of it. No new server. No IT project. Open the browser.
The aggregate stockpile is the heart of the plant. Without it, nothing runs. Mix designs need every aggregate fraction in the right ratio — and running out of one fraction halts production even when the others are full. A morning of missing #78 doesn't slow the plant down. It stops it.
And the pipeline of inbound rail is fragmented across at least four systems: the supplier's portal, the railroad's portal (ShipCSX, AccessNS, MyUPRR — pick the one your supplier ships on), an inbox of forwarded BOLs, and an internal spreadsheet that drifts out of sync the moment two people open it. When numbers don't reconcile, the usual answer is a multi-hour call chain across the supplier, the Class I railroad, and plant operations — with no definitive documentation at the end.
Meanwhile, demurrage accrues against held rail cars, billing follows whatever the BOLs say, and the plant absorbs the cost of any reconciliation it can't document. Without a single source of truth, that documentation has to be reconstructed every time a number gets questioned.
"Death by a thousand cuts." — Cargill, testifying to the Surface Transportation Board on rail accessorial charges
Rail Command tracks the full lifecycle — order → BOL → in-transit → receive → reconcile — for every rail car feeding the plant. Built around the workflow of whoever owns the rail terminal: plant manager, QC manager, or materials coordinator — not the workflow of an enterprise ERP.
Every open order, every loaded BOL, every BOL in transit, every receive — on a single dashboard with derived status. No manual state-toggling, no spreadsheet drift.
Suppliers load cars by mine, not by order number. Rail Command allocates each BOL's cars to the oldest open order for that mine automatically — and splits a BOL across multiple orders when it needs to. The bookkeeping just happens.
Build your monthly forecast and import it into Rail Command. The tool reconciles tons-to-tons against what actually shipped. Switch between "what you forecasted before the month started," "latest revision," or any specific issuance — all three views, on demand.
Short cars, broken or held cars, and missed deliveries are documented at the moment they happen, with the BOL they came in on. The audit trail is built as you work — not reconstructed after the fact.
If your supplier uses the stockyard to sell to third parties, Rail Command tracks the retail BOLs, sales, and inventory as a separate ledger — with a billing-dept-formatted monthly report that fits a single letter page.
Nine report types grouped by audience: Daily (operator), Management (executive summary, forecast vs actual), Accountability (exceptions, BOL manifest), Audit (drill-down). PDF export on every one.
Existing aggregate-receiving plants don't lack tools — they have too many of them. Enterprise dispatch/scale platforms cover the outbound truck side. Class I rail portals cover their own trains. The supplier portals cover their own mines. No single product unifies the inbound rail pipeline at the consignee. That's the gap Rail Command fills.
Rail Command was built inside an operating asphalt plant — by the lab manager responsible for the rail terminal and the aggregate stockpile — and runs in daily production. Every feature exists because the person managing the terminal needed it that morning. No imaginary workflows. No "future roadmap" features in the live tool. When something breaks, it's fixed the same day — because the person who wrote the code is the person logging tomorrow's BOLs.
Click in. Place an order. Log a BOL. Receive it. Run a report. Pull up the Forecast vs Actual view. Everything that runs at the live plant runs in the demo — just with fabricated data and generic mine names instead of operational records.