C Mapss

Predicting the failure before the anomaly: what remaining-useful-life forecasting needs that the reference stack does not have

Detection tells a plant that a machine is behaving abnormally now. Prediction claims to tell it how many days remain before the machine fails, and the vendor pitch treats that as the same problem solved one step earlier. It is not. Remaining-useful-life forecasting is a supervised problem that needs run-to-failure histories the reference stack has never recorded, and the published literature reaches its published accuracy on a benchmark of engines run deliberately to destruction. This issue separates the two questions the pitch fuses, models what a real plant can and cannot forecast from the history it actually keeps, and prices the two ways the forecast is wrong: retiring a healthy part early and missing the failure it promised to catch.

The prior issue put a small language model on the gated alert and enforced the one rule that kept it useful, that it may quote the manual and may never infer the cause. This issue takes the next and larger claim in the agentic-maintenance pitch, predictive maintenance, which promises to forecast the failure before the anomaly ever appears and to schedule the repair against a countdown rather than an alarm. The pitch presents prediction as detection solved one step earlier, the same competence pointed slightly further into the future, and that framing hides a change in the kind of problem being solved and the kind of data it requires. Anomaly detection, the capability the reference stack already has, is unsupervised. The Isolation Forest built across the early issues learns the shape of normal operation from healthy running data and flags departures from it, and healthy running data is the one thing every plant has in abundance. Remaining-useful-life forecasting is supervised and needs the opposite kind of data. To learn how many operating days remain before a failure, a model must be trained on examples of machines observed continuously from healthy through degradation to the failure itself, with the failure point labeled, and it needs many such examples to generalize, because a single run to failure teaches the model one machine's one death rather than the distribution of deaths. That run-to-failure history is precisely what a competently run plant does not keep, because competent maintenance intervenes before the failure and the record ends at the repair, not at the breakdown, so the endpoint the supervised model must learn from is the endpoint good operations is designed to prevent. The canonical public dataset that anchors most of the published RUL literature, NASA's C-MAPSS turbofan set, resolves the shortage the way a lab can and a plant cannot, by simulating engines run deliberately all the way to destruction under controlled fault injection, which is why the published accuracy figures describe forecasts on manufactured death and not on the interrupted, incomplete histories real plants accumulate. The issue separates the two questions the pitch fuses, models what a real stack can honestly forecast from the history it actually holds, which is narrower than a full RUL number and closer to a trend and a rate than a date, and then prices the asymmetry that governs the economics of any forecast: an estimate that retires a healthy component early converts unused remaining life into scrap and buys unnecessary labor, an estimate that overshoots and misses the failure it was purchased to prevent spends the unplanned downtime the whole program was justified by, and the two errors are not symmetric in cost, so the forecast's usefulness depends less on its average accuracy than on which direction it errs and what each direction costs on the specific asset. The numbers in this issue are modeled from published third-party benchmarks and the public prognostics literature, cited inline.