How to Calculate ROI on Condition Monitoring for a Multi-Site Chemical Operation
A Plant Manager building a ROI case for condition monitoring is solving a single-facility financial problem. A Plant Director building the same case is solving a portfolio capital allocation problem, and the structure of that argument is different in ways that matter to the people who approve the capital.
A CFO reviewing a monitoring program proposal for a single site is asking: "Does the avoided downtime cost at this facility justify the program cost?" At the portfolio level, the CFO is asking: "Does this program justify the capital allocation across all sites, how does it compete with other portfolio investment priorities, and what is our exposure if we don't act?" Those are different questions. They require a different financial structure.
The three-layer business case in this guide is built specifically for the portfolio conversation. Each layer is independently sufficient to justify the program. Together, they produce a capital case that is difficult to decline on financial grounds, because it addresses production risk, capital efficiency, and regulatory risk exposure simultaneously.
This guide provides the methodology for each layer, a worked calculation approach, and a copyable multi-site business case template you can bring to a CFO or board capital review.
- What Most Plant Directors Get Wrong When Building the Portfolio Business Case
- Layer 1: Aggregate Unplanned Downtime Cost
- Layer 2: Turnaround Cycle Extension Value
- Layer 3: Regulatory Incident Avoidance
- Presenting the Combined Case
- Your Multi-Site Chemical Business Case Template
- How Tractian Helps Plant Directors Build and Defend the ROI Case
What Most Plant Directors Get Wrong When Building the Portfolio Business Case
The most common failure is building a site-level maintenance ROI case and multiplying it by the number of sites. Finance teams immediately recognize this as an estimation, not a calculation, and apply the scrutiny accordingly.
A portfolio business case requires portfolio-level data, not site-level data scaled up. The specific mistakes that undermine approval:
Using hypothetical downtime costs instead of historical data. Every chemical plant has a CMMS or maintenance records showing actual unplanned events with actual durations. Using that historical record produces a credible number. Using industry averages or hypothetical scenarios produces a number the CFO cannot verify and will discount heavily.
Presenting the program as a maintenance efficiency improvement. In chemical manufacturing, maintenance efficiency is not the budget priority. Capital protection and regulatory risk management are. A business case framed as "this will reduce our maintenance labor by 15%" will compete with dozens of other operational improvement proposals. A business case framed as "this protects $40M of annual production exposure across the portfolio and reduces our PSM regulatory risk" sits in a different category.
Omitting the TAR capital connection. The turnaround is the single largest capital event in a continuous chemical facility's budget cycle. A monitoring program that generates the condition data to optimize TAR scope is not just a reliability improvement; it is a capital efficiency program. Missing this layer leaves the strongest argument for chemical manufacturing off the table.
The corrective is three layers, each calculated from the portfolio's own data, each presented in the language the approving executive uses to evaluate capital decisions.
Layer 1: Aggregate Unplanned Downtime Cost
Calculation Method
Pull 24 months of unplanned failure event records from the CMMS at each site. For each event on a critical rotating asset (compressors, boiler feedwater pumps, agitators, critical process fans, and equivalent non-redundant assets), calculate the total event cost across three components:
Production loss component:
Event duration in hours x facility production value per hour
For a large continuous petrochemical facility, production value per hour runs from tens of thousands to hundreds of thousands of dollars depending on plant scale, product margin, and market conditions. Use a conservative estimate if the exact figure requires process economics modeling; a defensible floor number is better than a precise number that invites challenge.
Restart cost component:
Restart labor (scheduled and overtime) + utilities consumed during the transient startup period + production quality qualification time (hours spent returning product to specification after restart, valued at production value per hour) + emergency contractor premium if outside services were required
Emergency repair premium component:
Actual emergency repair cost minus the estimated cost of the same repair performed as planned work. Unplanned repairs in chemical plants run 40 to 60% above planned repair cost because of expedited parts procurement, overtime labor, and HAZLOC-certified contractor mobilization outside of contracted cycles.
Sum all three components for each event. Sum across all events at all sites for 24 months. Divide by two for the annual average. This is the portfolio's Layer 1 baseline: the annual financial exposure from unplanned failures on the assets a monitoring program would cover.
The Payback Calculation
If Layer 1 annual exposure is $25M and the portfolio monitoring program costs $1.5M per year, the Layer 1 payback argument alone is: one avoided average-cost unplanned event at one site recovers approximately 20 days of program cost. The program pays back in the equivalent of one major avoided event per year, with every additional avoided event representing pure financial return above the program cost.
This calculation is the foundation. Layers 2 and 3 are the strategic dimensions.
Layer 2: Turnaround Cycle Extension Value
Why TAR Interval Extension Is the Largest Financial Lever
Turnarounds at large continuous chemical facilities are budgeted in the range of $10M to $100M+ depending on plant scale, process complexity, and scope. The TAR interval (how often the facility shuts down for the turnaround) is typically set based on regulatory requirements, equipment manufacturer recommendations, and conservative calendar estimates of equipment degradation rates.
With continuous condition monitoring data, two things become possible that the calendar-based approach cannot support:
First, scope optimization within the existing interval: condition data shows which components actually need replacement versus which are on the scope because the interval says it is time, not because the health data says they are degraded. Scope optimization at one TAR cycle can defer $1M to $5M in component replacement costs at a large facility.
Second, interval extension: if condition data demonstrates that critical assets are operating within specification as the scheduled TAR approaches, there is a factual basis for extending the TAR interval by six to twelve months beyond the calendar default. Each month of extension defers the entire TAR capital cost by one month's equivalent.
Portfolio-Level Calculation
For a portfolio of five continuous chemical sites, each with TAR cycles of different lengths and different upcoming TAR dates:
Identify the TAR cycle, next planned TAR date, and estimated TAR cost for each site.
Calculate the interval extension value for each site: estimated TAR cost divided by 12 months, multiplied by the number of months of defensible interval extension the monitoring program could support. Use a conservative 3 to 6 month extension estimate for a first presentation. Once the program is running, actual data will allow more precise calculations.
Calculate the scope optimization value for each upcoming TAR: apply a conservative 10 to 15% deferral rate across interval-based scope items to estimate the condition-based scope reduction that monitoring data would support.
Sum the interval extension value and scope optimization value across all sites. Over a three-year capital planning window with multiple TAR cycles across the portfolio, this number often represents several years of monitoring program cost in deferred capital spend.
The Capital Efficiency Argument
Present Layer 2 to the CFO as a capital efficiency argument, not a maintenance argument. "This program is a turnaround capital optimization investment. Over the next three years, condition-based TAR management across our portfolio is projected to defer $X in capital spend that would otherwise be required on calendar alone. That deferral reduces our capital requirements in years two and three and improves our capital allocation flexibility."
That framing puts the monitoring program in the capital planning conversation rather than the maintenance budget conversation.
Layer 3: Regulatory Incident Avoidance
Why This Layer Belongs in the Chemical Business Case
In chemical manufacturing, condition monitoring is not purely an operational reliability investment. It is a risk management investment against a category of loss that has no equivalent in most other industries: the process safety incident that creates portfolio-wide regulatory, legal, and reputational consequences.
The Layer 3 calculation is a risk-adjusted financial argument. It requires three inputs:
Estimated PSM incident probability across the portfolio over three years.
This is based on current compliance posture, asset age, monitoring coverage gaps, and historical near-miss data. A portfolio with multiple sites at early-stage PSM maturity, significant inspection backlog, and no continuous monitoring on critical rotating assets in classified areas has a materially higher incident probability than a portfolio with mature programs and comprehensive monitoring coverage. Use conservative and moderate scenarios, not optimistic ones.
Estimated cost of a PSM incident at any portfolio site.
Direct costs: OSHA PSM civil penalties (up to $156,259 per violation under 2025 penalty schedules), EPA RMP civil penalties (up to $70,117 per day per violation), emergency response and investigation costs. At the affected site: production loss during investigation and restart, remediation costs, legal and consulting fees for regulatory response.
Indirect costs: enhanced inspection burden at all related facilities under the same operating company (3 to 6 months of elevated management, compliance, and legal costs across the portfolio), reputational costs with customers and insurers, and the internal capital diversion required to respond to the regulatory investigation.
For a multi-site chemical portfolio, the full cost of a single PSM incident including direct and indirect categories regularly exceeds $10M to $30M, with severe incidents producing much larger numbers.
Risk reduction factor from the monitoring program.
Continuous monitoring on critical rotating assets in classified areas materially reduces the probability of the undetected catastrophic failure scenario that produces PSM-triggering events. Use a conservative 40% reduction in incident probability as the Layer 3 assumption. This is supportable by the mechanism: a fault that would have developed undetected to failure in an unmonitored asset is detected early when continuous monitoring is in place, allowing a planned intervention before the failure event occurs.
Layer 3 Calculation
Layer 3 value = (Estimated incident probability without monitoring x Estimated incident cost) minus (Estimated incident probability with monitoring x Estimated incident cost)
= Risk-adjusted cost reduction from the monitoring program
Present this as a range using conservative and moderate probability and cost assumptions. Even the conservative estimate will typically produce a Layer 3 value that exceeds the annual monitoring program cost by a significant multiple.
The Risk Language
At the board level, this argument is presented as: "Our portfolio's current monitoring posture creates a risk-adjusted exposure of $X to $Y from a PSM incident at any site over the next three years. The monitoring program we are proposing reduces that exposure by a conservative 40%, representing $X to $Y in risk-adjusted value. The annual program cost is $Z."
Presenting the Combined Case
A combined three-layer business case for a portfolio of five continuous chemical sites with total annual production value of $500M might look like this (hypothetical illustration):
Layer 1 (historical): 8 unplanned events across portfolio in last 24 months. Average event cost: $2.1M (production loss + restart + emergency repair premium). Annual average: $8.4M in unplanned event costs.
Layer 2 (capital deferral): Three TARs across the portfolio in the next 36 months with a combined estimated cost of $75M. Conservative condition-based scope deferral estimate: 12% = $9M in capital deferral over the period. TAR interval extension across two sites: estimated $4M in deferred capital from 4-month average extension.
Layer 3 (regulatory risk): Conservative three-year PSM incident probability across portfolio (based on two sites with early-stage monitoring coverage in classified areas): 8%. Estimated incident cost: $15M. Risk-adjusted exposure without program: $1.2M per year. Conservative 40% reduction with program: $480K per year in risk-adjusted savings. Three-year value: $1.4M.
Program cost: $1.8M per year, $5.4M over three years.
Combined three-year value: $25.2M (Layer 1) + $13M (Layer 2) + $1.4M (Layer 3) = $39.6M vs. $5.4M program cost.
Payback: The Layer 1 payback alone is 2.6 months. The three-year combined return is approximately 7x program cost.
Your Multi-Site Chemical Business Case Template
Layer 1: Aggregate Unplanned Downtime Baseline (last 24 months):
| Site | Unplanned Events | Avg Event Duration (hrs) | Production Value/Hr | Restart Cost/Event | Emergency Repair Premium | Total Event Cost |
|---|---|---|---|---|---|---|
| Site A | [X] | [X] | [$X] | [$X] | [$X] | [$X] |
| Site B | [X] | [X] | [$X] | [$X] | [$X] | [$X] |
| Site C | [X] | [X] | [$X] | [$X] | [$X] | [$X] |
| Portfolio Total | [$X] |
Annual average portfolio unplanned event cost: [$X / 2]
Layer 2: TAR Scope Optimization and Interval Extension Value:
| Site | Next TAR Date | Estimated TAR Cost | Conservative Scope Deferral (12%) | Interval Extension Potential | Combined TAR Value |
|---|---|---|---|---|---|
| Site A | [MM/YYYY] | [$X] | [$X] | [$X / month x months] | [$X] |
| Site B | [MM/YYYY] | [$X] | [$X] | [$X / month x months] | [$X] |
| Site C | [MM/YYYY] | [$X] | [$X] | [$X / month x months] | [$X] |
| Portfolio Total | [$X] |
Layer 3: Regulatory Incident Avoidance (3-year):
Estimated PSM incident probability across portfolio (3 years): [X%]
Estimated incident cost (direct + indirect): [$X]
Risk-adjusted exposure without program: [$X]
Conservative 40% reduction with program: [$X x 0.40]
3-year risk-adjusted value: [$X]
Program Cost:
Annual monitoring program cost (all sites): [$X]
One-time implementation investment: [$X]
Total 3-year investment: [$X]
Return Summary:
| Value Layer | 3-Year Value |
|---|---|
| Layer 1: Avoided unplanned downtime | [$X x 3] |
| Layer 2: TAR scope and interval extension | [$X] |
| Layer 3: Regulatory risk reduction | [$X] |
| Total 3-year value | [$X] |
| 3-year program cost | [$X] |
| Return multiple | [Xх] |
| Payback (Layer 1 alone) | [X months] |
Narrative for capital review:
"One avoided unplanned event at any portfolio site recovers [X] months of full program cost. TAR scope optimization across three upcoming TARs is projected to defer [$X] in capital spend, approximately [X] years of program cost. The combined three-year return at conservative assumptions is [X]x program cost. This program protects [$X] in annual production exposure, improves capital efficiency across the TAR cycle, and reduces our portfolio's PSM regulatory risk exposure."
How Tractian Helps Plant Directors Build and Defend the ROI Case
Tractian gives Plant Directors the data infrastructure to populate all three layers of the business case from actual portfolio data, not estimates.
For Layer 1: Tractian sensors on critical rotating assets at each site generate the continuous vibration and temperature data that, when a fault develops, provides the documented event: fault detected, corrective action scheduled, repair completed, production loss avoided. That documentation is what converts the business case from theoretical to historical after the first year of operation. A Plant Director presenting Layer 1 at a capital review two years after program deployment has actual avoided event records, not probability estimates.
For Layer 2: Tractian's platform provides 12 to 18 months of asset health trend data for each monitored asset, exportable for TAR scope planning. Before each site's TAR planning freeze, the Plant Director has condition-based evidence for scope decisions on every monitored asset. The documentation chain that supports a scope deferral decision is in the platform.
For Layer 3: Tractian's HAZLOC-certified sensors in classified chemical process areas address the specific failure scenarios most likely to produce PSM-triggering events. The continuous monitoring coverage in classified areas is the mechanism by which the program reduces the incident probability in the Layer 3 calculation.
Unplanned downtime converted to planned maintenance, TAR capital optimized by condition data, and regulatory risk reduced by continuous coverage in classified areas: these three outcomes map directly to the three layers of the financial argument.
See how Tractian supports multi-site chemical manufacturing operations
See how Tractian supports multi-site chemical manufacturing operations
Tractian continuously monitors equipment health in real time, detecting faults early and preventing unplanned downtime.
Explore the PlatformWhat are the three financial layers in a multi-site chemical condition monitoring business case?
The three layers are: aggregate unplanned downtime cost across the portfolio (from historical CMMS records); turnaround cycle extension value (condition-based evidence supporting interval extension and scope deferral); and regulatory incident avoidance (risk-adjusted cost of a PSM incident at any site including penalties, enhanced inspection at related facilities, and production loss). Each layer is independently sufficient to justify the program.
How does a Plant Director calculate aggregate unplanned downtime cost across a chemical portfolio?
Pull 24 months of unplanned failure event records from the CMMS at each site. For each event on a critical rotating asset, calculate production loss (event duration x production value per hour) + restart cost + emergency repair premium over planned repair cost. Sum across all sites. This is the portfolio's annual financial exposure.
How does TAR cycle extension create financial value at the portfolio level?
When condition monitoring data demonstrates that critical assets are performing within specification, it provides the factual basis to extend the TAR interval beyond the calendar default. Across a portfolio of five to ten sites each with multi-million-dollar TAR cycles, portfolio-wide interval extension creates capital deferral that can represent hundreds of millions of dollars in a five-year capital plan.
How do you quantify regulatory incident avoidance in a chemical monitoring ROI model?
Estimate the PSM incident probability across the portfolio over three years based on current compliance posture. Multiply by estimated incident cost (direct penalties + legal fees + production loss + enhanced inspection burden at related facilities). Apply a 40% reduction factor for the monitoring program. The risk-adjusted value of this reduction is a conservative but defensible line in the business case.
What is the most effective way to present a monitoring ROI case to a CFO in chemical manufacturing?
Lead with historical cost of inaction from your own CMMS records. Present program cost against that number as a payback calculation. Add TAR capital optimization as the strategic capital efficiency argument. Add regulatory risk reduction as the risk management layer. CFOs in chemical approve programs when they see three independent financial rationales, each of which would justify the program alone.
How long does a condition monitoring program need to run before it can generate TAR scope optimization data?
A minimum of 12 months of continuous monitoring data is needed for a defensible TAR scope deferral argument. Twelve months captures a full seasonal operating cycle and provides enough data points to distinguish genuine degradation trends from normal operating variability. The monitoring program should be running at least 12 months before the TAR planning freeze date to contribute condition-based scope data.
How does the ROI calculation differ for continuous process sites vs. batch chemical sites?
In continuous process sites, the unplanned stoppage layer dominates the ROI model because any non-redundant asset failure is immediately a production loss event. In batch sites, the stoppage cost is more variable and TAR scope optimization often contributes more proportionally. When building a portfolio business case, calculate each layer separately by site type and present the composition, not just the total.