MRI stands for Mapped Risk Inspection. You send one gateway backup. Within five business days you receive a report of every risk we found, ranked by severity, with an estimate of the effort each fix requires. The inspection is free, and the report is yours to keep.
Many of the problems in an Ignition project never appear on a screen. The gateway runs and the screens load while a timer script fails silently, a query is assembled by concatenating strings, an alarm pipeline notifies no one, and a password sits in plain text. Clicking through the application will not reveal these. Someone has to read the project.
The MRI does that. We run your backup through the same tools we use on rescue and review work, and a senior engineer reads every finding before the report goes to you. You receive a ranked list of findings, the evidence for each, and a list of what is in good order.
We offer it free because it is how we meet the people who run Ignition systems. If you want help with the fixes, we will quote them. If your own team prefers to do the work, the report is written so they can.
The scan covers nine areas. If an area comes back clean, the report says so.
Error handling that hides the error, scripts running in the wrong scope, and code that runs on every call and never succeeds.
Roles and permissions, passwords stored in plain text, and what a logged-in user can reach beyond their role.
Timer scripts that read every tag on every run, and queries with no limit on the rows they return.
SQL assembled by concatenating strings, references to database connections that don't exist, and queries that fail by returning nothing instead of an error.
Naming conventions that change partway through the project, unused tags, and history or alarm settings that don't do what they appear to do.
Alarm floods, alarms that can never clear, and notification pipelines that reach no one.
Views no one opens, scripts no one calls and queries no one runs. We also flag resources that only appear unused, so nothing still in use gets deleted.
Behavior your project relies on that is specific to its current version, and what is likely to break on upgrade.
If the server failed tomorrow, what could you restore, and what would be lost?
One document: a summary your plant manager can read, and the detail your engineers need to make the fixes.
The effort rating is our engineer's estimate of the work each fix requires, so you can decide what your team handles and what you hand off. It is not a quote. If you want a price on any item, we will scope it and give you the number in writing.
Complete the contact form with a short description of your system. An engineer replies within one business day with a secure upload link.
Upload one gateway backup. Nothing else is required. If parts of it are sensitive, tell us which, and we will exclude them. If you need an NDA, send it to us and we will sign it before you upload anything.
We scan the whole backup with the same tools we use on rescue and review work. A senior engineer reads every finding before it goes to you.
You receive the report within five business days. If you would like to review it with us, we will schedule a call.
That covers your projects, scripts, queries, tags, alarms and gateway settings. It cannot see the PLC at the other end of a device connection, the database your queries run against, or what an operator does at shift change. Some problems appear only under load, and a backup does not capture them. The report states where we looked and where we could not.
Every finding cites its evidence, so your engineers can verify our work. The report is provided AS IS. The effort ratings are our estimate of the work involved and are a guide only.
If the problems stem from how the system is structured, the next step is an Architecture Blueprint. If the system is in serious trouble, the next step is a Project Rescue. If your team needs more engineering capacity, it is engineering support.
It is how we meet the people who run Ignition systems, and it shows you how we work before you spend anything. There is no obligation to hire us afterward. The report is equally useful if your own team makes every fix.
You upload it through a secure link we send you. Only the Artek engineers working on your report can open it. We delete it within 30 days of sending you the report, unless you ask us to keep it. We do not share it with anyone, and we do not use it to train anything. A backup can contain passwords, so tell us what is sensitive and we will exclude it. Details are in our privacy policy.
Yes. Many of our customers ask for one, and we sign them routinely. Send us yours, and nothing is uploaded until it is signed.
No. We review everything in the backup, but some risks sit outside it: in the PLCs, the database and the way people use the system. The report states where we looked and where we could not.
No. It is our engineer's estimate of the work a fix requires, for planning. If you want a price, ask and we will scope it.
8.1 and 8.3. If you run an older version, ask us. On an older system, the upgrade-readiness section is often the most useful part of the report.
We use AI as well, and AI-written code is scanned like everything else. It usually works, but it tends to drift from the conventions the rest of the project follows, so that is where we look most closely.
Then you have that confirmed in writing, which is valuable before an expansion, a handover to a new team, or a rollout to another site.
A senior engineer reads every report, so we accept a limited number each month. If we are at capacity, we will tell you when the next opening 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.
The report comes back within five business days. If you would rather talk first, call us at the number below.
Get my free Ignition MRI →