Set Up Condition-Based Maintenance
Condition-based maintenance triggers work from an asset's real-time condition, such as temperature, vibration, or pressure, instead of from a fixed calendar schedule. For example, a motor running hot or a pump vibrating beyond its normal range may need attention today, regardless of when it was last serviced. When a condition signal reaches MaintainX® as a meter reading, you can use an automation to trigger a work request or a work order the moment that reading crosses a threshold you define. With Asset Intelligence, you can also use a monitor to detect an unusual pattern in a signal, without defining a threshold yourself.
Choose Your Approach​
MaintainX offers two ways to set up condition-based maintenance:
| Approach | Use it when | What MaintainX does |
|---|---|---|
| Anomaly monitor | You want MaintainX to detect unusual behavior, without defining a threshold. | Raises an alert for your team to review. |
| Threshold automation | You know the value that matters, such as a temperature above 80°C. | Creates a work request or a work order when a meter reading crosses the threshold you define. |
To set up an anomaly monitor, follow the monitor-based path. To set up a threshold automation, follow the manual configuration path.
Requirements​
- Assets in MaintainX for the equipment you want to monitor.
- For the monitor-based path, a data source that streams your equipment's signals into MaintainX, typically an OT data connector. When you set up the monitor, MaintainX matches the signals to each asset. For more information, see About Smart Tag Mapping.
- For the manual configuration path, meters created in MaintainX and mapped to your condition-monitoring tags (for example, temperature, vibration, or pressure), typically fed by an OT data connector or the REST API. For more information, see Map Tags to Meters.
Monitor-Based Path​
Use this path to have an anomaly monitor watch your equipment's signals for unusual behavior, so you don't build the rule yourself.
Step 1: Choose Your Monitor​
For condition-based maintenance, use an anomaly monitor. Anomaly monitors detect anomalies in temperature, current, or the signals that are specific to pumps, fans, and compressors (beta). When a monitor detects an anomaly, MaintainX raises an alert that your team can review and turn into work. Choose the monitor that matches the condition you want to watch.
Start with one monitor on a small set of critical assets, so you can validate the results before you scale.
Step 2: Set Up Your Monitor​
Create a monitor from Asset Monitoring > Monitors, and select the anomaly monitor for your use case. Work through the setup steps:
- Choose what to monitor: Select the assets that the monitor will watch. A Signal match of Matched means MaintainX found a tag it can use.
- Confirm the signals: Confirm the tag path that carries each asset's signal.
- Activate: Review what the monitor turns on, and then select Enable Monitor.
For more information, see Create a Monitor.
Step 3: Validate Your Monitor​
Before you add more assets, pilot the monitor on one or two critical assets. Confirm that the alerts it raises match what you see in the asset's readings. Anomaly monitors need about two weeks to learn what's normal before they raise alerts. For more information, see Anomaly Monitors.
On the monitor's details page, check Last alert triggered, Triggered alerts (24h), and Recent Alerts. For more information, see Review a Monitor's Activity. Once you're satisfied with the results, use Manage Assets to add more assets. For more information, see Change What a Monitor Does.
Monitors don't replace automations. If you need a custom condition, such as sending an email when a temperature crosses a specific threshold, keep using an automation. Automations and monitors can run on the same asset without conflict.
Manual Configuration Path​
Use this path to trigger work from a meter reading that crosses a threshold you define, using an automation.
Step 1: Identify Your Conditions and Thresholds​
Determine which signals and threshold values represent a meaningful maintenance state for each asset. A typical mapping might look like this:
| Condition | Threshold | Severity | MaintainX Action |
|---|---|---|---|
| Temperature | Above 80°C | Warning | Create a Work Request |
| Temperature | Above 100°C | Critical | Create a Work Order |
| Vibration | Above 12 mm/s | Warning | Create a Work Request |
| Pressure | Below 30 PSI | Critical | Create a Work Order |
Each automation evaluates one meter, so define one threshold for each automation. If you need a calculated value, such as a rate of change, calculate it in your data source before it reaches MaintainX.
Keep your initial scope narrow. Start with one or two condition types on a small set of critical assets, such as pumps, motors, or compressors, so you can validate signal accuracy and tune thresholds before scaling.
Step 2: Set Up Your Automation​
Once your meters are mapped and your thresholds are defined, create an automation that connects them and configure these settings for your condition-based use case:
-
Trigger: Select the Asset that corresponds to your condition tag, or select Add multiple assets to apply the same rule to up to 250 similar assets at once. Select the Meter that corresponds to your condition tag, then set the trigger condition that represents your threshold. For example, Is above 80 to detect a high-temperature warning. Use the For setting to control how sensitive the trigger is:
- One reading: Triggers on every reading that crosses the threshold, which suits critical conditions where you want to know about each occurrence.
- One reading, then reset: Triggers once, then won't trigger again until the reading clears the threshold and crosses it again, which avoids repeat work requests or work orders while a condition stays active.
- Multiple readings: Requires multiple readings to cross the threshold (for example, 3 of the last 5), reducing false positives from a transient spike. Recommended for most warning-level conditions.
- A reading longer than: Triggers only once a condition persists for a set duration, which is useful for conditions such as sustained high temperature.
-
Conditions: Optionally add a condition to refine when the rule runs. For example, limit it to production hours, or to when the asset's status is Online.
-
Actions: Choose what MaintainX should do. For warning-level conditions, select Create a Request. For critical conditions, select Create a Work Order. By default, MaintainX assigns the asset that triggered the automation to the request or work order. In the description, state the condition and the threshold that triggered it, such as "Temperature above 80°C", so a technician can act on it without checking the source meter. Select Settings on the action to set how often it can rerun. For condition-based triggers, consider a longer interval to avoid duplicate tasks while a signal stays above threshold. For a work order, you can also select Create only if previous Work Order generated from Automation is closed, so MaintainX doesn't create a new work order while the previous one is still open.
Step 3: Validate Your Automation​
Before expanding to your full asset list, pilot the automation on one or two assets using a single condition type, ideally one where you can observe real signal behavior over a few days. Confirm that:
- Work requests or work orders are created at the right threshold values.
- The automation isn't re-triggering repeatedly for a condition that's continuously above threshold.
- The generated work request or work order's description includes the condition and threshold that triggered it, so a technician can act on it without checking the source meter.
Check the automation's Action History to review every run, skip, and failure, along with timestamps and links to any work orders created. Once you're satisfied, duplicate the automation and adjust it for additional assets, condition types, or severity tiers.
Reconcile Your Automation and Your Calendar-Based Maintenance Plans​
Condition-based automations and calendar-based maintenance plans are separate mechanisms, so you can't convert one directly into the other. A condition-based automation doesn't necessarily replace every calendar-based preventive maintenance task for an asset.
Whether a condition-based automation can replace a given preventive maintenance task depends on whether the condition you're monitoring covers the same failure modes the task was written to catch. Use the following phases to decide whether an existing plan still needs to run at its current frequency, or at all.
Run the Automation Alongside Your Plan​
Keep the existing calendar-based maintenance plan running for the asset while you set up the condition-based automation for the same condition. The plan continues to generate its regular work orders while you confirm the automation catches what it's supposed to.
Confirm the Automation Works​
Pilot the automation as described in Step 3: Validate Your Automation. Keep the calendar-based plan running during the pilot as a safety net in case the automation misses something.
Decide Whether to Keep, Adjust, or Delete the Plan​
Once the automation reliably catches the condition at the right threshold, review whether the calendar-based plan is still providing value. If the automation covers what the plan was catching, you can delete the calendar-based maintenance plan for that asset. Deleting a plan is reversible, so you can restore it if you need to fall back to the calendar schedule.
If the plan also covers failure modes the automation doesn't, keep it in place or adjust its frequency to complement the automation instead of duplicating it.
Common Issues​
Watch for the following common issues as you configure and monitor condition-based maintenance:
- Poorly tuned thresholds: A threshold set too close to the normal operating range generates a high volume of low-value tasks. Start conservatively and adjust based on real signal behavior and technician feedback.
- Transient spikes: A short-lived anomaly, such as a brief temperature spike during startup, can trigger an automation unnecessarily. Use Multiple readings or A reading longer than to filter these out.
- Sustained conditions: If an asset stays above a threshold for an extended period, MaintainX continues to act based on your configured rerun interval. Set that interval appropriately, and use conditions to prevent duplicate work from stacking up.
- Asset mapping errors: If a meter is mapped to the wrong asset, work requests and work orders are misrouted. Verify your tag mappings before going live.
- Startup and transition states: Some assets show abnormal readings during startup, cooldown, or mode transitions that don't reflect a real maintenance need. Configure your automations to exclude these periods where possible.