Is this program behind, or was it never fundable?
Seven questions for anyone accountable for a capital program that is behind.
The question this Read asksHow much of the program, in units, was decided before the first gang went to work?
Exposure Read 6 · The Program
A program that is behind and a program that was never fundable look identical in a monthly report. They require opposite responses, and the cost of confusing them compounds every period.
A program that is behind responds to pressure, resequencing, force and overtime. A program that was never fundable responds to none of those, because the constraint is not effort — it is that the units, the window and the money were never reconcilable at the rate this property can actually produce. Applying the first remedy to the second condition burns the only thing that was still recoverable, which is the window in which saying so is credible.
A program runs on its production rate, not on its budget. Money, schedule, force and material are all downstream of one number: units per shift, by this gang, on this property, under these conditions. Programs fail because that number was assumed rather than demonstrated — and because nothing in an ordinary reporting cycle audits it.
Run them yourself.
Six of these seven can be answered from your own data by your own people inside a week, and they are yours to run.
What production rate did the plan assume, and where did the number come from?
Units per shift, per gang, at what force, under what track time, on what territory. Then trace the number to its origin. A system average, a vendor figure or last year’s plan carried forward is not a rate — it is a placeholder that acquired authority by being written down. Only performance demonstrated on this property, in these conditions, is a rate.
How much usable track time does the plan assume, and how much is actually being delivered?
Not the length of the curfew. The working time inside it — after protection is established and the gang is on the ground, before tie-up begins. Programs are planned on the window and executed in the fraction.
Was the scope estimated from records, or from a walk?
Tie counts from the database, surfacing from the cycle, turnouts from a diagram, structures from an inspection two years old. Every one of those is a reasonable planning input and every one of them is a chart. A scope built on the chart and executed on the ballast produces an overrun that gets reported as execution and was actually estimation.
What is the material position — in units, on the property, by location?
Not ordered. Not committed. Not in a yard four hundred miles away. On the ground, at or distributable to the work location, with the equipment and the window to place it. Material in a purchase order has never produced a tie in the track, and material staged in the wrong place consumes the same window twice.
Who is telling you why it is late, and what would it cost them to say something else?
Every readily available cause is external and defensible. The causes that implicate the plan cost the reporter something to raise, and they are raised by nobody in an ordinary reporting line. Ask what the true cause would have to be for somebody in this chain to be the one who names it — and if the answer is that nobody in the chain can, you have located the actual reporting defect.
Does the remaining scope fit the remaining window at the demonstrated rate?
Not the planned rate. The rate achieved to date, this year, on this property. Multiply it by the shifts that remain. If the result is short, that is not a forecast and it is not an opinion. It is arithmetic — and its value to everybody above you falls every week it goes unstated.
What happens to the units that do not get done, and who has written that down?
They are deferred into next year’s program, which was already full when it was built. Or carried as a speed restriction. Or absorbed silently as condition. A program that ends short does not end. It transfers — and the transfer is almost never priced, almost never recorded where next year’s planner will find it, and compounds into the deferral that eventually gets discovered by somebody buying the railroad.
Six of these are answered from your own data inside a week. The remaining one — question 03 — requires somebody to go out on the property, which is why it is the one that is never answered and the one that is usually the cause.
How much of the program was decided before execution began.
Where it is more than half, the pressure applied to execution all year was applied to the smaller half of the problem.
What arrives.
The demonstrated rate, by gang and by territory
Units per shift as actually achieved, separated from the planned rate and from the system figure, with the conditions that produced it stated. This is the number the whole program is built on and in most organizations nobody owns it.
Usable track time, measured rather than asserted
Granted window against working time, by shift, with the loss allocated to its causes — protection, travel, set-up, tie-up, interference. Reported as one line that operating and engineering can both read without either being blamed.
The scope reconciled to the ground, by sample
What the records say against what is out there, on a sample large enough to be defended, with the difference priced. Either it confirms the plan — which is a finding worth having — or it locates the overrun in estimation, where it can still be fixed for next year.
An arithmetic answer on whether the program fits
Remaining scope, remaining shifts, demonstrated rate. Including the answer that the program does not fit and must be re-scoped or re-funded — delivered in a form that can be taken upward, because a finding nobody can carry into a room is not a finding.
And what it is not
It is not an audit, it is not a claim position, and it does not arrive with anybody’s name attached to a failure. The object is a program that can be delivered or honestly re-scoped — and that outcome is impossible if the read produces a defendant.
The seven questions above are the test of the firm that wrote them. Run them, and judge the firm by what they find.
If you run them and the program is sound, that is a week well spent and you owe nobody anything.
The reason they frequently are not run internally has nothing to do with capability. Question 05 is the reason — the answers implicate a plan that everyone in the chain approved, and there is no comfortable position from which to raise them. An outside read is sometimes worth exactly one thing: it is the only party in the room with nothing to lose by saying what the arithmetic says.
Our bench of career railroaders brings better than 160 years of combined field experience. Nobody we send learns railroading on your property. That is a standard, not a résumé.
Write and say what you found.
Write and say what you found, or call 928.605.7984 and say it. Not an impression — what the seven returned on a program you are running now: your score, and which one your own reporting would not answer. The one you could not answer is the finding. It is worth more than anything this firm could tell you before seeing it, and on most programs it is the whole matter.
You will have a reply within one business day, from the principal and not from a form. Writing puts you on no list. If what comes back says you have no problem, you will be told so. What comes back sets the next stage, or the work stops there. The full Exposure Read, with its worksheet, comes from the same address.
This page is general information about railroad practice. It is not legal, engineering or financial advice, it does not replace counsel or an inspection of your property, and reading it does not engage SteelWheels.Co.
solutions@steelwheels.co · 928.605.7984 · What happens when you write back