Certified Ignition integrator

Ignition SCADA and BMS, end to end - from a certified integrator.

Ignition runs plants as SCADA and buildings as their BMS. We supply the licences, build the screens, history and alarms, and support it, from a single panel to a fleet of sites. And because we also build the Volts platform, the data can carry on to energy reports, tenant charges and AI agents when you need it.

We use your email only to contact you about Volts. No newsletter, no sharing. Privacy Policy

Ignition Perspective on a tablet and a phone, showing the same alarm analysis screen at both sizes
Certified
integrator
Ignition Perspective. Image: Inductive Automation.

by Inductive Automation

140+

countries with Ignition installations

69%

of Fortune 100 companies use Ignition

2003

Inductive Automation founded

Figures published by Inductive Automation, September 2026.

Why Ignition

What makes Ignition different from classic SCADA and BMS.

Classic SCADA and BMS software is often priced per tag or point, installed workstation by workstation and tied to its own historian. Ignition, from Inductive Automation, takes the opposite approach on all three.

Licensing

Licensed per server. Grow without reopening the licence.

One Ignition Standard licence covers a server, with unlimited tags, device connections, screens and clients. More tags, screens or operators do not change the price.

  • A one-time licence, with modules added only when the project needs them.
  • Unlimited Designers, so every engineer on the project works in the same tool.
  • The full platform runs as a free two-hour trial you can reset, so the proof of concept comes first.
Licence cost What growth costs Tags, screens and users →
  • Per-tag or per-client licensing
  • Ignition: one licence per server
Illustrative shapes, not prices. Classic SCADA licensing varies by vendor and contract.

Build and run

Build it once in the Designer. Run it on every screen.

Engineers build screens, tags, alarms and scripts in one Designer. The gateway serves the result to control-room desktops, panels, browsers and phones.

  • Perspective screens run in a web browser and on phones and tablets, with nothing to install.
  • Vision runs the classic control-room desktops.
  • Templates and data types keep a hundred pumps consistent, and Python covers the logic a template does not.
  • Changes are published from the gateway, not reinstalled screen by screen.
The Ignition Designer on a laptop, with a process screen of fans, dye tanks, a storage tank and a cooler being built
Ignition Designer. Image: Inductive Automation.

Open by design

Every brand on the floor. One open platform.

Core drivers for Siemens, Allen-Bradley, Modbus, BACnet, DNP3, Omron, Mitsubishi and IEC 61850, plus OPC UA and MQTT, so equipment from different vendors meets on one system.

  • History and production data in standard SQL databases your IT team can back up and query.
  • MQTT Sparkplug to central gateways, clouds and other platforms.
  • A built-in REST API and configuration your team can keep in Git, from Ignition 8.3.
OPC UA Siemens S7 Modbus BACnet Allen-Bradley SQL databases IEC 61850 DNP3 MQTT REST API

Ignition as a BMS

It runs buildings, too. Without the per-point licence.

The platform that runs a production line can be a building's BMS: plant graphics, schedules, setpoints, alarms and trends for heating, cooling, ventilation and lighting. It talks BACnet and Modbus to the controllers already in the building, so a closed BMS front end can be replaced without replacing the field.

Before

A typical closed BMS front end

  • Often licensed by the point
  • Changes go through the original installer
  • Screens on one workstation in the plant room
  • Data that is hard to get out

After

Ignition as the BMS

  • Unlimited points on one server licence
  • Any Ignition integrator can maintain it
  • Screens in a browser and on phones and tablets
  • History in standard SQL databases
Kept

The BACnet and Modbus controllers, sensors, valves and drives already in the building. Control loops stay in them, and MS/TP networks connect through a BACnet router.

What it runs
Air handling & ventilation Heating & heat pumps Chillers & cooling Lighting Energy meters Floor plans & zones

Happy with the BMS you have? Ignition can work next to it instead, finish what it never did and leave every writable point with one owner.

From one panel to a fleet

Edge where it is enough. Standard where the site needs it.

Ignition Edge runs on a panel or small PC at each site. A central Ignition Standard gateway brings every site together, and the Enterprise Administration Module backs them up and upgrades them from one place. We size each site to the smallest edition that does the job.

Select a box to open its edition below.
One device

Ignition Edge

For a machine, a panel or a small site.
Screens
Up to two at a time, with Edge Panel
History
35 days on the device, forwarded when the link is back
Tags and devices
Unlimited
Databases and reports
None on the device; data goes to a central gateway or the cloud
Licence
Per device, one-time
One server

Ignition Standard

For a plant, a campus or a central gateway for many sites.
Screens
Unlimited clients and sessions
History
Historian and SQL databases, kept as long as you need
Tags and devices
Unlimited
Databases and reports
SQL, transaction groups, reporting and the full module range
Licence
Per server, one-time, with modules added as needed
AWS or Azure

Ignition Cloud Edition

For central services in AWS or Microsoft Azure.
Screens
Perspective, served from the cloud
History
Historian and databases in the cloud
Tags and devices
No device drivers; data arrives over MQTT or from site gateways
Databases and reports
Bundled, including SQL and reporting
Licence
Billed by the hour through the cloud marketplace

When we recommend Standard over Edge: more than two people need live screens at the same time, the site needs its own database, transaction groups or reports, or one gateway has to run several projects.

Ignition + Volts

Ignition runs the site. Volts runs the business on top of it.

SCADA data rarely leaves the control room. Follow one reading from the plant floor to the monthly report.

  1. Rows of controllers and gateways on DIN rails inside an automation cabinet

    On the plant floor

    A controller reports a temperature

    PLCs, BMS controllers and meters already measure the plant. Ignition reads them over OPC UA, Modbus, BACnet or the vendor's own protocol.

  2. An Ignition process screen with fan speeds, dye tank levels and temperatures, and a tank status table
    Image: Inductive Automation

    On the operator's screen

    Ignition shows it, trends it and alarms on it

    Operators see it live, the historian keeps every value, and the right person is called when it drifts. Control stays on site, with or without an internet connection.

  3. A Volts board with electricity cost for the month, daily averages, live power readings and CO2 per meter

    In the monthly report

    Volts turns it into cost, CO₂ and work

    Over MQTT, the same reading reaches Volts: energy and ESG reports, tenant charges, maintenance work orders and AI agents that act only where you allow it.

Ignition works on its own. Volts is there when the data needs to leave the control room, and every writable point has one owner, agreed before commissioning.

See building automation in Volts

Why work with us

An Ignition integrator that also builds the layer above it.

SCADA projects usually stop at the control room. We are certified on Ignition and we build Volts, so the same plant data can go on to the people who pay the bills, report the energy and fix the equipment.

An engineer in a high-visibility jacket testing a heating manifold with a handheld meter

Certified, with in-house engineering

We are a certified integrator in Inductive Automation's Integrator Program. The team that scopes your project is the team that builds and supports it.

Control and operations, one team

Ignition runs the site in real time. Volts, which we also build, carries the same data to energy reports, tenant charges, maintenance and AI agents. One team owns the line between them.

Plants and buildings

Process lines and building services both, from PLCs and BMS to meters on Modbus, M-Bus and BACnet. Where a signal is missing, we add a meter or relay we design and make ourselves.

We finish what was started

Where a BMS or SCADA was bought and never fully used, we complete the scope over Ignition instead of replacing what already works.

Licences sized honestly

Ignition Edge where it is enough, Standard where the site needs it. Each proposal names the reason, so you buy the licence the site requires and nothing more.

One owner for every control point

Before commissioning, every writable point gets exactly one owner, so Ignition, the BMS and Volts do not fight over the same setpoint.

What we deliver

The whole Ignition stack, from licence to long-term support.

Take one service or the full project. Each scope states what we deliver, what you receive and what stays with your team.

Architecture & licensing

Edition, modules, servers, redundancy and network security, sized to the site. We supply the licences as part of the project.

Edge Standard Cloud Edition Redundancy

SCADA & HMI screens

Overviews, faceplates and operator screens in Perspective for browsers and phones, or Vision for control-room desktops, built on reusable templates.

Perspective Vision Mobile Templates

Device connectivity

PLCs, drives, meters, BMS and legacy systems, connected through Ignition's drivers, OPC UA or MQTT and organised into reusable data types.

OPC UA Siemens S7 Allen-Bradley Modbus BACnet MQTT

Historian & reports

Process history, trends, scheduled PDF reports and KPI dashboards, kept in a historian or SQL database your IT team can back up and query.

Historian SQL Reports Dashboards

Alarming & notification

Alarm pipelines, on-call rosters and escalation by email, SMS or voice call, so each alarm reaches someone who can act on it.

Alarm pipelines On-call rosters SMS & voice ISA-18.2 metrics

Production & MES data

OEE, downtime reasons, counts, recipes and batch records, collected from the line and written to the database the business reports from.

OEE Downtime Recipes Batch records

Edge, IIoT & multi-site fleets

Ignition Edge at remote or unmanned sites, store-and-forward buffering, MQTT to a central gateway, and EAM to back up and upgrade every gateway from one place.

Edge IIoT Edge Panel MQTT Sparkplug EAM

Migrations & upgrades

Replace a legacy SCADA, HMI or BMS front end area by area, running side by side until each one is signed off, or upgrade an existing Ignition system to 8.3.

Legacy SCADA BMS front ends HMI replacement Upgrade to 8.3

Support & training

Support agreements, remote and on-site help, operator and engineer training, and documentation your team can work from.

Support Training Documentation Handover

Already running Ignition? We also audit, document and take over systems built by someone else. Tell us about your gateway

How a project runs

Visibility first. Control once it is proven.

Each phase ends with something your team can inspect and sign off before the next one starts.

1. Audit the site

1
A site visit maps controllers, BMS points, meters, network and access, and tests representative connections.

You receive: the inventory and a point-ownership matrix.

2. Design and quote

2
Edition, modules, servers and screens are sized against the audit.

You receive: the architecture, with licences and engineering quoted as separate lines.

3. Build and test off site

3
Tags, screens, history and alarms are built and tested before installation, then walked through with your team.

You receive: a system your team has already seen working.

4. Commission, loop by loop

4
Monitoring goes live first. Control follows loop by loop, with the existing system as the fallback.

You receive: a sign-off on each loop before the next one starts.

5. Support and grow

5
Training, handover documents and a support agreement.

You receive: one architecture that new sites and modules join.

FAQ

Ignition questions, answered before the first call.

Are you a certified Ignition integrator?

Yes. We are a certified integrator in Inductive Automation's Integrator Program, and the Ignition engineering on your project is done by our own team. We share the current certification details at scoping.

Do we need Volts to work with you on Ignition?

No. An Ignition project with us is a standard Ignition system that runs on its own. Volts is an option for when the same data needs to reach energy, finance or property teams.

Can you supply the Ignition licences?

Yes. We quote the licences with the project, sized to the edition and modules the site needs. Standard and Edge licences are one-time purchases, with optional annual support plans from Inductive Automation.

Ignition Edge or Ignition Standard?

Edge suits a single machine, panel or small site. Standard suits a plant, a campus or a central gateway for many sites. Where Edge is enough we start there, and the proposal names the trigger that would justify Standard.

Can Ignition replace our BMS?

Yes. Ignition can be the building's BMS: plant graphics, schedules, setpoints, alarms and trends, talking BACnet and Modbus to the controllers. Where the field controllers are sound they stay, and only the front end changes. Control loops stay in the controllers, and every writable point has one owner.

Will Ignition work with our existing PLCs, BMS and SCADA?

Usually, yes. Ignition has drivers for Siemens, Allen-Bradley, Modbus, BACnet and other common protocols, and connects to OPC UA servers. The audit tests representative connections before the scope is priced.

Can you take over an Ignition system someone else built?

Yes. We audit the gateway and its projects, document what is there, fix what is risky and take over support, including upgrades to Ignition 8.3.

What happens if the internet connection drops?

Ignition runs on site, so local screens, alarms and control carry on. Ignition Edge buffers up to 35 days of data and forwards it when the link returns, so central history and Volts reports catch up.

Who owns the project and the licence?

You do. The licence is yours, and the project is a standard Ignition project, documented at handover, so your own engineers or another Ignition integrator can maintain it.

Can we try Ignition before buying it?

Yes. Ignition is free to download and runs with every feature in a two-hour trial that can be reset as often as needed. We can build a proof of concept on the trial before any licence is bought.

Keep exploring
Building Automation Smart Control Integrations For industrial sites For hotels How we deploy

Bring the system list. Leave with an Ignition plan.

Share the controllers, BMS or SCADA you run today and what you need Ignition to do. We will tell you which edition and modules fit, what can stay and how the first site would be built.

Scope an Ignition Project Email Us the System List