A Step-by-step Guide To Connecting Ignition To Your CMMS

Ignition collects asset data. Your CMMS manages the work on that asset. But somewhere between an alert firing and a technician picking up a wrench, things fall apart. Emails pile up, creating work orders manually becomes a bottleneck, and equipment issues turn into unplanned downtime.

Connecting Ignition directly to your CMMS closes that gap. This guide walks through the practical steps for integrating Ignition tags with a CMMS, from choosing which tags to connect first, to mapping them to meters and setting thresholds that actually improve maintenance outcomes.

Key takeaways

• Email-based Ignition alerts create manual bottlenecks, while direct CMMS integration automates work order creation and gives technicians a single system of record.
• A phased approach—starting with runtime hours, prioritizing critical assets, then adding condition-based monitoring—drives early wins and avoids overwhelming teams with noisy data.
• Continuous improvement comes from setting baseline thresholds, validating results with downtime and wrench-time metrics, and refining triggers over multiple PM cycles to better prevent failures.

Why email alerts from Ignition are not enough

Many teams using Ignition rely on email alerts to flag equipment issues. When a motor hits a certain amp reading or a machine reaches a runtime threshold, Ignition sends an email that is meant to kick off a maintenance workstream. But that’s usually where the problems start.

Brett Pyper, who leads reliability efforts at Hudsonville Ice Cream, describes his issues with this workflow, "I would receive that email and I would have to manually create a work order and assign it to a technician." 

That manual step created a bottleneck for Brett and his team as it does with a lot of others. One person becomes the gatekeeper between machine data and maintenance action, and if that person is busy, sick, or on vacation, alerts pile up.

The goal is what Brett calls "a single point of truth" for technicians. Instead of checking Ignition dashboards or waiting for forwarded emails, technicians receive work orders automatically when equipment conditions warrant attention. They work from one system, and the data does the heavy lifting.

What you need before connecting Ignition to your CMMS

Team roles and responsibilities

Connecting Ignition to a CMMS involves both technical setup and maintenance decisions. At Hudsonville, the work split across teams:

• Controls team: Handles the Ignition side, including creating folders and moving tags.
• Reliability or maintenance lead: Decides which tags to connect, sets thresholds, and validates outcomes over time.
• Implementation specialist: A person or team well-versed in the technical aspects of the CMMS, usually a representative from the vendor itself, provides support for data migration and setup during onboarding.

You don't have to do everything yourself. Brett relied heavily on his controls team for the technical pieces while he focused on which data points would actually drive better maintenance decisions.

Technical prerequisites

A few essential elements need to be in place before connecting systems: 

1. Your CMMS needs an asset hierarchy. Brett describes a tiered system at Hudsonville: plant level, then production rooms, then individual equipment within those locations.
2. Ignition needs to be collecting the data points you want to use, whether that's runtime hours, amps, temperatures, or other metrics. 
3. You'll need an API token from your CMMS to establish the connection. 
4. There needs to be a dedicated folder structure in Ignition for tags that will flow to your maintenance software.

Tag rollout order: Which Ignition tags to connect first

Connecting every available tag at once sounds efficient, but it creates noise. A deliberate sequence helps teams build confidence and see results quickly.

1. Start with runtime hours

Runtime hours are the easiest starting point because they align with how most OEM manuals specify maintenance intervals. If a manufacturer recommends service every 500 hours, you can trigger that PM based on actual usage rather than guessing with calendar dates.

"We started with hour-based PMs first because that's the easiest for everyone to grasp," Brett explains. 

This is also one of the best ways to score some early wins. Calendar-based PMs often miss the mark as equipment that runs constantly gets maintained too infrequently, while equipment that sits idle gets maintained too often. Hour-based triggers fix both problems.

2. Prioritize critical assets

After deciding to start with runtime hours, the next filter is criticality. Focus first on equipment where unplanned downtime hits hardest. Brett's team started with their most critical assets and the data points from those assets that they could effectively use.

3. Layer in condition-based tags

Once hour-based triggers are working reliably, add condition-based monitoring for temperature, amps, pressure, or other operating parameters. This sequencing matters because condition-based thresholds require baseline data.

"There are very few manufacturer recommendations for what to do with this type of data," Brett notes. To make progress, you first have to collect data to understand what normal operation looks like, then set thresholds based on those trend lines. Jumping straight to condition-based monitoring without that baseline leads to false alarms or missed issues.

How to map Ignition tags to CMMS meters

Create the Ignition folder structure

The technical connection is simpler than it sounds. Hudsonville's controls team created a specific folder in Ignition dedicated to tags that would flow into MaintainX. Using the API token provided by their MaintainX, they established the connection.

From there, the process is straightforward: copy and paste tags from your existing Ignition locations into the CMMS folder where they should automatically populate without the need for custom coding.

Use AI-assisted tag mapping

Once tags arrive in your CMMS, they still require mapping to specific assets and meters. For example, MaintainX's Smart Tag Mapping feature uses AI to detect the unit of measurement from imported Ignition tags and suggests which asset the meter belongs to.

Brett tested both approaches: manual mapping before the feature existed, and AI-assisted mapping during beta testing, saying that the AI approach accelerated adoption. Any AI tool you use will rely on data hygiene, so clean naming conventions in Ignition improves accuracy. But even with imperfect data, it saves significant time compared to mapping everything by hand.

Setting up meter-based work order triggers

Hour-based PM triggers

Set up PMs to trigger based on equipment runtime rather than calendar dates. Set a threshold, say 100 hours, and a work order generates automatically when that count is reached. In this scenario, the maintenance matches the actual wear on the machine.

Condition-based triggers

For condition-based readings, like motor amp, temperature, or pressure, set thresholds that indicate abnormal operation. When readings exceed those thresholds, a work order generates automatically for investigation.

This reduces the need for someone to constantly monitor Ignition dashboards. Technicians receive work orders when something warrants attention, not when someone happens to notice a trend line moving in the wrong direction.

Using calendar backstops

One common concern: what if the hour-based trigger never fires because equipment sits idle? The solution is a calendar backstop.

"You set up for your hour-based, but you also set a calendar base behind the scenes," Brett explains. Set up triggers as "100 hours OR at least once a year" to ensure PMs happen regardless of usage patterns. This provides confidence during the transition from calendar-based to usage-based scheduling. You know the work will get done either way.

How to set and improve condition-based thresholds

Start with OEM recommendations

Manufacturer guidelines provide a reasonable starting point for hour-based thresholds. If the manual says service every 500 hours, start there. Your specific environment may differ, but it's a defensible baseline.

For condition-based thresholds like amps or temperature, OEM guidance is rare. You'll establish your own baselines by collecting data during normal operation and identifying what the ideal condition looks like for your equipment.

The five-cycle adjustment rule

Don't adjust thresholds after one or two PM cycles. Brett's team waits until a PM has triggered three to five times before making changes.

"If it's a 100-hour PM, we'll wait until it's triggered three to five times before we'll make an adjustment," he explains. This provides enough data to identify patterns rather than reacting to anomalies. One unusual reading doesn't mean the threshold is wrong.

Using PM flags and failures as feedback

If a PM never finds anything, it may not have value. When PMs consistently find no issues, you should incrementally extend the interval, moving from, for example, 100 hours to 110, then 120. When reactive work occurs that would have been caught by a PM, you can shorten the interval. The goal is PMs that regularly catch problems before failures occur.

Validating your integration between Ignition and your CMMS

Comparing historical downtime data

Use historical records migrated into your CMMS to establish a baseline. Compare downtime incidents for specific failure modes before and after integration.

Brett describes tracking pump rebuilds as an example: "During this period we had so many downtime incidents for rebuilding this pump, and then we can look at the next period and we had significantly fewer because we were able to rebuild it outside of those windows because we caught it early."

Tracking wrench time improvements

Measure whether technicians spend more time on actual maintenance versus administrative work. Hudsonville conducted time studies before implementation and again after a few months in the system.

"We were able to validate that we did improve—and we actually improved more than we anticipated," Brett reports. The team gained 10% to 15% more wrench time than expected. That's time technicians spent fixing equipment instead of printing work orders, entering data into computers, or tracking down information.

Results from connecting Ignition to MaintainX

Hudsonville's experience shows what's possible when Ignition data flows directly into maintenance workflows:

• Paper reduction: No more printed work orders in the maintenance department
• Tag expansion: Started with approximately 500 tags, now approaching 1,000
• Visible asset health improvement: Noticeable difference in overall equipment condition year-over-year
• Team adoption: Even initially resistant technicians became strong users after training
• Operations buy-in: The operations team embraced the system because it benefits equipment care.

How MaintainX simplifies Ignition integration

MaintainX provides several features that simplify the connection between Ignition and maintenance:

• Smart Tag Mapping: AI-assisted tool that detects units of measurement and suggests asset associations, reducing manual mapping time.
• Mobile-first design: Technicians work from one system instead of checking Ignition dashboards separately.
• Flexible meter triggers: Set up hour-based, condition-based, or hybrid triggers with calendar backstops.
• Procedure Generator: When creating new usage-based PMs, AI helps generate baseline procedures quickly.

Sign Up for Free