How to Evaluate Condition Monitoring Solutions for a Chemical Manufacturing Portfolio

A Plant Manager evaluating condition monitoring for a single site is asking: "Does this platform work on my assets and fit my maintenance workflow?" A Plant Director evaluating the same decision for a portfolio of sites is asking a materially different question.

The portfolio question is: "Does this platform provide consistent, standardized, audit-ready data across all sites in a single view, in certified configurations suitable for classified chemical process areas, at a program cost that is defensible against the aggregate financial exposure it protects?"

Those are different evaluation criteria. Most condition monitoring platforms are designed for site-level buyers. A Plant Director applying portfolio-level criteria will find that many options that perform well in isolated site evaluations fail the portfolio test.

This guide provides the evaluation framework, the non-negotiable requirements, the red flags that disqualify a platform for portfolio deployment, and the portfolio ROI structure that makes the business case defensible to a CFO or capital review board.

Non-Negotiable Requirement 1: Hazardous Area Certification

Chemical process plants contain classified locations: areas where flammable or explosive atmospheres may be present under normal operating conditions or in the event of equipment failure. Under NFPA 70 (National Electrical Code) in the United States, these locations are classified as Class I Division 1 or Class I Division 2 depending on the frequency and duration of hazardous atmosphere presence. Under IEC standards used in Europe and internationally, equivalent classifications are Zone 0, Zone 1, and Zone 2.

Any electronic device installed in a classified location (including condition monitoring sensors) must carry appropriate certification for the specific location classification:

North American installations: UL (Underwriters Laboratories) or CSA (Canadian Standards Association) listed for the applicable Class/Division classification. ATEX certification from European programs is not a substitute for UL/CSA listing for North American installations.

European and international installations: ATEX certification for the applicable Zone classification.

Dual-listed requirements: For multinational portfolios with sites in multiple regulatory jurisdictions, verify that sensors carry the appropriate certifications for each jurisdiction's classified area requirements.

Why this matters for the evaluation: the assets with the highest process safety consequence in a chemical plant are typically located in classified areas. A reactor agitator, a charge gas compressor, and the associated process pumps are not in general-purpose electrical areas. If the monitoring platform's sensors are not certified for the specific classification of those installation locations, the platform cannot be deployed on the highest-priority assets, which defeats the purpose of the program.

Verify certification before any other evaluation criterion. A platform with uncertified sensors for your classified areas should not advance to technical evaluation regardless of its other capabilities.

Non-Negotiable Requirement 2: Single Platform, Standardized Data Across Sites

Portfolio-level condition monitoring requires a platform architecture that presents data from all sites in a standardized, comparable format through a single access point.

This requirement has four components:

Common data model: Vibration, temperature, and operating parameter data collected at each site must be stored in a common schema that allows direct comparison across sites. A platform that allows each site to customize its data structure produces the same portfolio visibility problem as having each site use a different vendor.

Standardized alert taxonomy: The platform must support a common alert classification system: severity levels, threshold criteria, and escalation triggers, applied consistently across all sites. This is what enables the Plant Director to look at a portfolio alert summary and know that a "Severity 2" alert at Site C means the same thing as a "Severity 2" alert at Site H.

Portfolio-level reporting: The platform must provide a portfolio view: all sites, key metrics, and current alert status in a single interface. Site plant managers need site-level operational views. The Plant Director needs the portfolio view that the challenges article's monthly review structure requires.

Cross-site benchmarking: The platform should allow comparison of asset health performance across sites. If Site A's compressors have consistently healthier vibration profiles than Site D's equivalent compressors, that observation should be visible at the portfolio level and should inform capital allocation and best-practice sharing decisions.

A per-site data silo architecture (where each site's data lives in a separate system even if the same vendor supplies all sites) does not meet this requirement. Verify the platform's multi-site data architecture specifically, not just its single-site capabilities.

Non-Negotiable Requirement 3: Deployment Without Process Interruption

In continuous chemical manufacturing, taking a non-redundant process asset offline for sensor installation is not a trivial operational decision. Depending on the asset and the process configuration, stopping the asset for sensor installation can require:

• A partial unit shutdown affecting multiple upstream and downstream process steps
• A minimum restart sequence of four to twelve hours before the unit returns to steady-state production
• Production quality qualification to confirm product specification is met after restart
• Utilities consumed during the restart transient period

For a charge gas compressor in a continuous ethylene unit, the cost of a planned shutdown for sensor installation can run into the hundreds of thousands of dollars in lost production and restart costs. A monitoring platform that requires process shutdown for installation creates an adoption barrier that many continuous chemical sites will resist, or defer indefinitely.

The platform must support sensor installation during normal operation. This requires both hardware design (sensors that can be installed on running equipment without the installation process creating a hazard or vibration disruption) and commissioning process (the platform vendor must have documented installation procedures for classified areas during production operation).

Verify this capability with reference customer interviews at chemical or continuous process sites. A vendor that claims "installation possible during operation" but has no reference installations at continuous chemical facilities should be questioned carefully on the specifics.

Non-Negotiable Requirement 4: Audit-Grade Data Retention for PSM Documentation

OSHA 29 CFR 1910.119(j) requires that mechanical integrity programs maintain records of inspections and tests, including deficiencies found and corrective actions taken. For the monitoring data to serve as mechanical integrity documentation, the platform must meet specific data retention and accessibility requirements:

Retention duration: PSM records must be retained for the life of the process. A platform with rolling data retention that discards historical data after 12 or 24 months does not meet PSM documentation requirements. Verify the platform's data retention policy and whether historical data is exportable in a format that can be archived independently of the platform.

Tamper-evident records: PSM audit requirements are met by records that demonstrate the data was collected as part of a systematic inspection program, not generated or modified after the fact. The platform must provide timestamps and data integrity assurances that support an audit defense.

Export capability: The platform should allow export of asset health history, alert records, and corrective action documentation in formats usable by a regulatory auditor or legal team. A platform that only presents data through its own interface creates dependency on that platform's continued operation for compliance record access.

Corrective action linkage: When an alert is generated and a corrective action is taken, the platform should create a linkage between the alert record, the corrective action documentation, and the resolution status. This linkage is the PSM mechanical integrity documentation chain: deficiency identified, corrective action taken, resolution confirmed.

A monitoring platform that generates good operational alerts but cannot provide the documentation chain for PSM compliance purposes is solving half the problem in a chemical operating environment.

Red Flags That Disqualify a Platform for Portfolio Deployment

These criteria, if present, should remove a vendor from consideration for a multi-site chemical manufacturing portfolio:

No ATEX/UL/CSA certification for the relevant classified area classifications. If the sensors cannot be legally installed in your classified process areas, the platform cannot be deployed on your highest-priority assets.

Per-site data architecture with no portfolio view. A platform that requires site-by-site data access cannot support portfolio-level visibility or standardized PSM documentation.

Installation requires process shutdown. As described above: in continuous chemical, this is a significant cost and adoption barrier.

No chemical or continuous process industry reference customers. General industrial monitoring platforms are not always designed for the chemical environment. A vendor without verified reference installations in chemical or continuous process operations has not demonstrated the solution works in your environment.

Pricing that makes multi-site expansion economically prohibitive. A platform priced on a per-asset or per-site license model that produces increasing unit cost as you scale creates a perverse incentive against portfolio-wide deployment. The financial argument for a portfolio program requires a cost structure that makes comprehensive coverage economically rational.

Alert systems that cannot be standardized across sites. If the platform allows each site to configure its own alert thresholds and classification independently with no portfolio-level override capability, it cannot deliver the standardized alert taxonomy a Plant Director requires.

Portfolio ROI: How to Frame the Financial Argument

The portfolio ROI calculation for a condition monitoring program in chemical manufacturing has three layers. Each layer is independently sufficient to justify the program; together they produce the most defensible capital case.

Layer 1: Aggregate Avoided Unplanned Downtime Cost

Pull historical unplanned event records across all sites for the last 24 months. 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 from unplanned failures on the assets a monitoring program would cover.

For a portfolio of five continuous chemical sites, this number typically falls in the range of $10M to $50M per year, depending on site scale and historical reliability performance.

Layer 2: Aggregate TAR Scope Optimization Value

Across all sites, identify the upcoming TAR cycle for each facility and the estimated cost of interval-based scope items that could be deferred or validated by condition data. Apply a conservative 15 to 20% deferral rate across all such items across all sites.

This layer represents deferred capital spend, not recurring annual savings; in chemical portfolios with multiple TAR cycles across sites in any given three-year window, the aggregate TAR scope optimization value often exceeds the Layer 1 number over a three-year horizon.

Layer 3: Regulatory Incident Avoidance

Estimate the portfolio's PSM incident probability over a three-year horizon based on current compliance posture. Multiply by the estimated cost of a PSM incident at any site (direct penalties + enhanced inspection burden at related facilities + management and legal costs + production loss).

Apply a reduction factor for the monitoring program: continuous monitoring on critical rotating assets in classified areas materially reduces the probability of the undetected catastrophic failure scenario that produces the most severe PSM incidents.

The risk-adjusted value of this reduction belongs in the portfolio business case even if it is difficult to quantify precisely. Present it as a range based on conservative and moderate assumptions.

Portfolio program cost vs. aggregate exposure: For most chemical portfolios, the monitoring program cost (capital for sensors plus annual platform and support costs) represents 1 to 5% of the aggregate financial exposure across all three layers. That ratio is the financial argument.

Structuring the Vendor Evaluation Process

For a portfolio-level evaluation, the process should have two distinct phases.

Phase 1: Portfolio requirements gate. Evaluate all vendors against the four non-negotiable requirements and the red-flag criteria before any site-level technical evaluation. Vendors that do not pass the portfolio gate are removed from consideration before consuming site plant manager time in technical evaluations.

Phase 2: Site-level technical evaluation with portfolio criteria maintained. For vendors that pass the portfolio gate, conduct site-level technical evaluations at two or three representative sites covering different classified area classifications, asset configurations, and CMMS environments. The site evaluation confirms operational fit. The portfolio criteria remain non-negotiable.

Involve site plant managers in Phase 2 for their operational expertise. Maintain the portfolio evaluation criteria at the Plant Director level throughout. The final selection decision should be made by the Plant Director, not by site consensus.

Request proof of PSM documentation capability specifically: ask vendors to provide a sample data export in the format they would provide for a regulatory audit, with alert history, trend data, and corrective action records linked to specific assets. This is a differentiating request that separates vendors who have built compliance capability into their platform from those who describe it as a theoretical feature.

CapEx lifecycle and turnaround capital deferral evidence: Evaluate whether the platform retains 12–24 months of continuous condition trend data per asset, exportable for turnaround scope planning and CapEx justification. For a Plant Director managing expensive rotating equipment with multi-year turnaround cycles, condition trend data is the evidence base for every major capital replacement decision. Components with documented remaining service life can be deferred; components with degradation trajectories can be planned for replacement rather than emergency-sourced. Evaluate trend data retention and export specifically for turnaround scope engineering and board-level CapEx presentations.

Headcount force multiplier, Auto Diagnosis™: Evaluate whether the platform provides automated failure mode identification, bearing faults, rotor unbalance, misalignment, impeller damage, seal degradation, on process-critical rotating equipment without requiring a specialist with PSM experience to interpret the data. For Plant Directors who face a structural shortage of certified rotating equipment engineers, Auto Diagnosis™ embeds specialist-level diagnostic capability in the platform. A maintenance technician in a classified process area receives the fault classification and recommended action. PSM mechanical integrity program quality does not depend on whether a specialist is currently employed at the facility.