InduIndex turns the exports and files you already have into
rule-cited analyses, tracked issues and generated documents.
The alarm analyzer is free to try in early access,
and the rest of the bench is powering on.
Your data is never used to train models, and a zero-retention
path keeps nothing after the report. Decision support: you sign off, not the tool.
induindex.com/quick-analyzeREADY
line3_export.csv event log · 84,213 rows · parsed
PEAK RATE14.2/op·10 min
IN FLOOD9%target <1%
CHECKS2/6pass
flood
Alarm flood: 9% of time above threshold ISA-18.2 §5.3
Bad actor TAG_4711: 31% of all events Pareto
Chattering group: 5 tags inside 60 s EEMUA-191
✓ added as issue #12
01 // THE TOOLS
Built like it's already running.
The alarm analyzer is free to try today, shown here upload to findings.
The rest are on the bench, each screen below a working preview of where the hub goes next.
THE ANALYZER · 01 UPLOAD FREE · EARLY ACCESS
Drop in the export you already have.
CSV, EU semicolons, XLSX from WinCC, FactoryTalk, Ignition or
anything that writes a table. Delimiter, encoding and timestamps are detected; you confirm
the column mapping. Nothing connects to running equipment: it reads the exported file only.
A deterministic rules engine benchmarks it against ISA-18.2 /
EEMUA-191: rate and flood KPIs, chattering and stale alarms, the bad-actor Pareto. Every
finding cites the rule it broke, and accepted findings become tracked issues that
de-duplicate on the next upload.
…/projects/line-3/analyses/12READY
AVG RATE14.2/op·10 min
IN FLOOD9%target <1%
CHECKS2/6pass
Flood window 06:20–06:50 ISA-18.2 §5.3✓ #12
TAG_4711 drives 31% of load Pareto✓ #13
62% alarms missing descriptions config hygiene
re-upload line3_v2.csv → 4 already handled · 2 new
Troubleshooting assistant COMING SOON
An issue workspace like a pull request for a machine fault: a
timeline of everything tried, attached scopes and files, suggested checks as a todo list,
and an assistant grounded in the issue's own data and the supplier manuals, citing the
page it read.
…/issues/34 · servo fault F7-1284SOON
TIMELINE
Fault raised: drive F7-1284
Scope trace attached
3 checks suggested → todos
ASSISTANT
F7-1284 on the filler servo, where do I start?
F7 is a following-error family. Check load after the gearbox, then encoder feedback wiring. Manual §7.4
Document generation COMING SOON
The busywork engineers gladly hand over: IO lists, FAT documents,
alarm lists and function descriptions generated from the project's own data, reviewed by
you, exported to XLSX and PDF, versioned in the project.
…/documents/io-list · rev ASOON
IO LIST · LINE 3 142 signals · from project data
DITAG_1102Guard door closed
DOTAG_1140Conveyor 3 run
AITAG_1207Zone 2 temperature
AOTAG_1290Dosing valve setpoint
generating… export XLSX / PDF
Chat with your project COMING SOON
Ask across everything a project holds: uploaded files, analyses,
supplier manuals, and get answers with citations that link back to the source, never a
guess. Scoped to your project's own data, vendor-neutral by design.
…/projects/line-3/chatSOON
Max torque for the MDX-61B on axis 4 during homing?
150% of rated for max. 5 s during homing, per the drive's parameter P302 limits. MDX-61B manual p. 214
And what did we set in this project?
P302 = 130% in axis4_params.xml, below the manual's ceiling. project file
02 // HOW IT WORKS
No integration. No connection to running equipment.
An offline file flow by design, matching how OT security actually works.
01
Upload what you export
CSV or XLSX from your DCS, HMI or historian: EU semicolons,
odd timestamps and all. Up to ~1 million rows.
02
Confirm the mapping
The file is detected as a configured alarm list or an event log;
you confirm the column mapping with per-system presets.
03
The rules engine runs
Deterministic ISA-18.2 / EEMUA-191 math computes every KPI and
finding. The language model narrates; it never decides a number.
04
Findings become work
A benchmark report with rule-cited findings; accept them as
tracked issues. The next upload de-duplicates against what's already handled.
03 // DATA SECURITY
Your files are your customers' IP. Handled like it.
TRAININGYour data is never used to train models. Ever.
RETENTIONZero-retention path: nothing kept after the report is delivered.
DATABASEBulk rows never enter the primary database; object storage only, under your retention mode.
ISOLATIONPer-tenant row-level security enforced in the database, not just the app.
ENTERPRISEOn-premise storage and local models on the roadmap for enterprise.
04 // WHY THIS EXISTS
The pain is real, and it's handled by hand today.
Alarm rationalization, where InduIndex starts, is standardized
in EEMUA 191 and ISA-18.2. In practice it's Excel and VBA, or a $150–200K consulting
program. What practitioners say:
“I've never been in a control room where the ‘Silence Alarm' button isn't the most worn down on the panel.”
“If you've ever seen a process upset at a console and see 100+ alarms come in at once… Yeah, what do you do?”
“Nuisance alarms that require engineering support to correct is probably a billion dollar problem.”
05 // PRICING
On the page. Every alarm incumbent hides theirs.
Monthly plans with credits: an analysis spends credits, chat is cheap.
EUR, excl. VAT. New accounts get free credits once your email is verified — no card
needed.
CSV and text exports, including EU semicolon-delimited files, and XLSX. Delimiter,
encoding and timestamp format are detected for you; you confirm the column mapping.
Do you store my alarm data?
Raw exports go to object storage under a retention mode you choose, and a
zero-retention path keeps nothing after the report. Bulk rows never enter the primary
database, and nothing is ever used to train models.
Is this a certification or sign-off tool?
No. It's decision support: explainable, rule-cited findings you review and act on.
The engineer verifies; the tool doesn't sign off.
Which standards does it benchmark against?
ISA-18.2 and EEMUA-191. Each finding cites the specific clause or band it relates to,
so a reviewer can trace it.
Do I connect it to my control system?
No. You upload an export you already have. Nothing connects to running equipment;
it's an offline file flow by design.
07 // TELL US WHAT TO BUILD
Want the tools still on the bench? Tell us what you need.
The analyzer is free to try today. For the tools still on the bench,
leave your email and say which ones you'd actually use (or what's missing), and you'll
hear the moment they ship. Pilots run free.