A Machine Risk Inspection of your Ignition system. Send one gateway backup. Five business days later you get a report of every risk we found, ranked by severity, each with an honest read on how much work it is to fix. Free, and the report is yours.
An MRI finds what a check-up can't: the thing you didn't know to ask about. Ignition systems are the same. The gateway runs and the screens load, while underneath a timer script fails silently, a query has no parameters, an alarm pipeline notifies nobody, and a password sits in plain text. Nobody finds those by looking at the screens.
We run your backup through the same tools our engineers use on every rescue and review, then a senior engineer reads every finding before it goes to you. You get a ranked list of what we found, with evidence, and a plain statement of what's fine.
It's free because it's how we meet people who run Ignition. Some ask us to fix what we found. Most just sleep better. Either is fine with us.
The places Ignition systems collect risk quietly.
Error handling that hides the error, scope mistakes, and code that runs but can never succeed.
Roles, permissions, passwords in plain text, and what a logged-in user can reach that they shouldn't.
Timer scripts that read every tag each tick, unbounded queries, and what gets slow at twice today's load.
Unparameterized SQL, connection names that don't exist, and queries that return nothing instead of an error.
Inconsistent conventions, dead tags, and historian or alarm settings that don't do what they seem to.
Floods, alarms that can never clear, and pipelines that notify nobody.
Views nobody opens, scripts nobody calls, queries nobody runs, and the ones that only look dead.
Version-specific behavior your project leans on, and what breaks on the next release.
What you could actually restore, how fast, and what you'd lose.
A document your plant manager can read and your engineer can act on.
The effort rating is our engineer's honest read of how much work each fix is, so you can decide what to do yourselves and what to hand off. It's an estimate, not a quote. If you want a price, we'll scope it and put a real number in writing.
Tell us about your system on the contact form. An engineer replies within a business day with a secure upload link.
Upload a gateway backup. That's all we need. If parts are sensitive, tell us and we'll work around them.
The same tools our engineers use work through the whole backup. A senior engineer reviews every finding before it reaches you.
Your report arrives within five business days. We're glad to walk through it on a call, and just as glad if you never call.
The scan reads what's in your backup: projects, scripts, queries, tags, alarms, gateway config. It can't see the PLC at the far end of a device connection, the database your queries run against, or the operator who clicks the wrong thing at shift change. Some risks only show up under load. The report says where it looked and where it couldn't.
Every finding cites its evidence so your engineers can check it. The report is provided AS IS. Effort ratings are our estimate of the work involved and are a guide only.
Sometimes the structure is the real constraint. That points to an Architecture Blueprint. If the report shows a system in real trouble, the next step is a Project Rescue. If your team just needs more hands, that's engineering support.
It's how we meet people who run Ignition, and it's a fair sample of how we work. Some ask us to fix what we found. Nobody has to, and the report is just as useful if you fix everything yourselves.
You upload it through a secure link we send. Only the Artek engineers on your report can access it. We delete it within 30 days of delivering the report unless you ask us to keep it. We never share it and don't use it to train anything. A backup can contain passwords, so tell us what's sensitive and we'll skip it. Details are in our privacy policy.
No. The scan is thorough about what's in the backup, and whole classes of risk live outside it. The report tells you where it looked and where it couldn't.
No. It's an engineer's honest read of how much work a fix is, so you can plan. If you want a price, ask and we'll scope it.
8.1 and 8.3. On something older? Ask. An upgrade-readiness read is often the most useful part of the report anyway.
We use it too. AI-written work gets scanned like everything else. It tends to produce code that works but drifts from the project's own conventions, so that's where we look hardest.
Then you have that in writing, which is worth something before an expansion, a hand-over, or a rollout to another site.
A senior engineer reads every report by hand, so we take a limited number each month. If we're full, we'll tell you when the next slot is.
Ignition® is a registered trademark of Inductive Automation, LLC. The Ignition MRI is an Artek service for systems built on that platform; Artek is an independent integrator and the service is not affiliated with or endorsed by Inductive Automation.
One backup, five business days, a report you'll actually read.
Get my free Ignition MRI →