The work includes MES and ERP integration, multi-site rollouts, React web applications, and systems that nobody on staff can fully explain. If you are not ready for a full project, three smaller engagements are described below.
Most engagements cover a whole system or a major part of one. Projects run for months, often across more than one site, and end with a system that is commissioned, documented and running.
A new Ignition system, or a full replacement for your current platform. We design, build and commission it, then hand it over with documentation your team can use.
The engineer who scopes it carries it through commissioning and startup.
Most of our engineering hours are spent here. Senior Ignition engineers join your project and work to your standards, from your backlog and on your schedule.
You run the project, and the system remains yours.
This is usually an MES layer, an ERP interface, a multi-site rollout or a move off an older platform. We are most often called in when one of these has stopped a project.
We can take on this piece alone, even when someone else built the rest.
It may be one stalled project or an entire platform that nobody can explain. We establish where it stands, stabilize it and finish it.
Any size, regardless of who built it.
We build these from scratch, take on one part of a larger project, or work on them inside a project your own team runs.
Perspective screens that work on phones and tablets and show equipment status where operators already look. Screens that are easy to read require less training.
OEE, SPC, and track and trace in one system, so the plant floor and the front office work from the same numbers. We build it ourselves or deliver it on Kanoa MES or Sepasoft.
Two-way, real-time links between the plant floor and your ERP, so the schedule reflects actual production.
Historian design and context for process data come first. Analytics and AI are built on that foundation. How we approach it →
Data from every plant in one place, so headquarters sees what the floor sees.
Custom web applications in React, with or without an Ignition backend: portals, internal tools and dashboards that sit outside the plant-floor HMI.
Each one puts senior engineers on your system for a short, defined piece of work and ends with a written deliverable that you keep, whether or not you hire us for the next phase.
When you are planning a new system, an expansion, a migration or a multi-site rollout, we settle the architecture before anyone starts building.
Send us one gateway backup. Five business days later you receive every risk we found, ranked by severity and by the work needed to fix it.
When a system needs more than an MRI, we review it with your team, map the risks, and deliver a costed plan that sets the order of repairs.
If you need a one-off PLC swap, a standalone panel build, or the lowest hourly rate, another firm will likely serve you better. We will say so on the first call and suggest who to call instead.
If data from your plant floor drives how you run the business, we are likely a good fit.
Inductive Automation's own classes are good, but they are not always scheduled when your team needs them, and they do not cover your system. In that case, we build a class for your team.
We plan each class around the people in the room, from operators seeing Perspective for the first time to engineers who need scripting and tags in depth.
Where possible, we teach on your own system, so the screens in class are the same ones your team uses in production.
On site or remote, timed around your shutdowns and go-live dates.
Classes are taught by the engineers who build these systems for us, including former Inductive Automation engineers. Our aim is a team that can run its system without us. Teams that know their systems well tend to bring us back for larger builds.
Each of these is written into the contract.
On fixed-price work, the quote is the price. Scope changes only one way: you request a change, we quote it, and you approve it. Time-and-materials work is billed every two weeks against a PO you have approved.
Every project, tag structure, script and document we build for you is yours from the moment we create it, not at the end of the engagement.
Every engagement is divided into phases. At the end of any phase you can stop, keep all completed work, and owe nothing further.
Where downtime has a direct cost, a support agreement sets our response and restoration times in writing. Without one, call us whenever you need us.
Call us to set up twenty minutes with an engineer. By the end of that call, you will know whether there is a project worth pursuing.
Get in touch →