Ignition is powerful and open, which is exactly why who builds your system matters as much as the platform itself. A good integrator leaves you with a maintainable, well-documented system your own team can grow. A weak one leaves you with screens that work today and a tag model nobody can touch. Here's how to tell the difference before you sign.
What an Ignition integrator actually does
An Ignition integrator designs and builds your supervisory system on Inductive Automation's platform: standing up gateways, connecting PLCs and devices over OPC UA, designing the tag model and UDTs, building Vision or Perspective screens, configuring alarms and notifications, wiring up the historian and reporting, and often adding MES or custom modules. The best ones also do the unglamorous parts — documentation, version control, redundancy, and handover — so the system outlives the project.
What to look for
Real Ignition depth, not a logo. Ask how many Ignition projects they've shipped, on which modules, and whether they're a registered Inductive Automation integrator. Tag-model discipline. The single biggest predictor of a maintainable system is a clean UDT-based tag model — ask to see how they structure one. References in your world. A water district wants someone who's done water; a dairy wants food-and-beverage experience. A support story. What happens at 2 a.m. when a gateway goes down? Ownership. You should end up owning your project, source and documentation — not be locked to the integrator.
Questions worth asking
A few that quickly separate strong from weak: How do you structure UDTs and naming for a system this size? Do you use source control on Ignition projects? How do you handle a phased cutover and parallel run? What does handover and documentation include? Who supports it after go-live, and how? Can we host and maintain this ourselves afterward? Vague answers here are a warning.
Red flags
Be cautious if you hear: heavy reliance on copy-pasted screens instead of templates and UDTs; no source control; "we'll figure out the tag model as we go"; reluctance to hand over project files or document the system; or a pitch that's all graphics and no data architecture. Pretty screens on a messy tag model are a maintenance bill waiting to land.
Local vs. remote
For commissioning, operator training and walkdowns, on-site presence matters — being close enough to show up is real value. For design, build, configuration and support, remote work covers the full lifecycle well. The right mix depends on the project; what matters is that the integrator is honest about which parts need boots on the ground.
How we work
We build Ignition systems with a clean, UDT-based tag model, source control, documentation and a handover that leaves your team able to maintain and grow the system. We're on-site across California's Central Valley — based in Merced — and remote nationwide, across food & beverage, dairy, water and remote sites. To talk through a project, get in touch or see our Ignition development services.
Frequently asked questions
What's the most important thing to check in an Ignition integrator?
A clean, UDT-based tag model and that you'll own the project and source. Those determine whether your own team can maintain and grow the system later.
Should I hire a local or remote Ignition integrator?
On-site presence matters for commissioning, operator training and walkdowns. Design, build, configuration and support work well remotely. A mix is common and usually the most cost-effective.
Do I need a registered Inductive Automation integrator?
Registration signals commitment and training, but project references and tag-model discipline matter more than the badge alone.