Your machines may already be warning you. The question is whether anyone is listening. Your core downtime exposure comes from your numbers. Scenario costs use clearly marked assumptions that you can replace.
In continuous process operations the restart is often more expensive than the stoppage — off-spec output, purge losses and a stabilisation window nobody logs against downtime.
These drive the scenario cost section only. Fields still on SolidPro defaults are marked — replace any that you know.
Fixed screening multipliers, stated openly: earlier-detection improvement = 0.25 + (1 − detection maturity) × 0.40 · readiness to act = 0.40 + response maturity × 0.30 · risk weighting = maturity 45% / availability strain 35% / detection 20%. Note that your detection answer also carries weight 22 inside the maturity score and 30% of the maintenance-strategy dimension, so it influences the risk band through three routes. That is a deliberate SolidPro modelling choice reflecting the centrality of warning time — it is not an industry-standard weighting · availability strain is measured against a SolidPro screening reference of 95% (editable above), not an industry benchmark. Annual unplanned downtime = monthly unplanned downtime × 12 × critical machine count. These are SolidPro screening assumptions, not measurements.