FoxALM
Alarm management with the evidence attached.
A rationalization workshop gives you opinions and a report. FoxALM reads three to twelve months of your alarm history and gives you changes your engineers can implement, each one backed by the analysis that justifies it and verified after it goes in.
- You send
- Three to twelve months of alarm and event history
- Turnaround
- Five business days
- Site visit
- None for the baseline assessment
- You receive
- A change package in your DCS vendor’s import format
- Coverage
- 29 of 30 ISA-18.2 / IEC 62682 measurable requirements in full, the 30th in part
- Beyond
- 17 capability areas neither standard requires
- Standards
- ISA-18.2-2016, IEC 62682:2022, EEMUA 191 (2024), API RP 1167
What you send
One export. No network connection to your plant, and no one from FoxIQ on site for the baseline.
Three to twelve months of alarm and event history
A standard export from your historian or DCS. Three months is enough to start. Twelve captures seasonal operation, turnarounds and the rare upsets that matter most, so send as much as you have.
- OSIsoft PI
- Emerson DeltaV
- Honeywell Experion
- CSV export
Sent through our client files area
Each client gets its own access-controlled upload area. Files are encrypted at rest and deleted automatically after the retention period you choose. We sign your NDA before any data changes hands, and confirm in writing when your files are deleted.
What you get back, within five business days
An engineering change package. Every item states what to change, why, and how confident the analysis is.
Three reports, three audiences
A board summary with an ISA-18.2 grade from A to D, a shift manager brief on operator workload, and the full technical report.
ISA-18.2 KPI audit
Alarm rate, peak rate, floods, chattering, fleeting and standing alarms, top-10 contribution and priority distribution, each against the standard’s target.
Cascade map
Your worst floods traced to their initiating alarm, with the alarms that follow from it and how often they do.
Suppression rules
State-based suppression in Honeywell Experion or Emerson DeltaV native import format, each with its safety basis stated.
PID retuning parameters
Kp, Ti and Td for the loops driving chattering alarms, with gain and phase margins confirming stability.
Rationalization worksheets
One per tag, pre-filled from the analysis, with a column for your team’s review notes.
MOC records
Management of Change records for every proposed alarm change, ready for your MOC committee.
Audit trail
Per-tag traceability to the evidence behind each recommendation, for PSM and regulatory review.
Verified improvement
After implementation, a before and after comparison with statistical testing, so improvement is documented rather than assumed.
Floods, traced to the first alarm
During an upset one event sets off dozens of alarms. The cascade map shows which one started it and which follow from it, so suppression targets the consequences and the operator sees the cause.
- TIC-303 HIGHKerosene draw temperature
- TIC-304 HIGHDiesel draw temperature
- TIC-1001 HIGHFurnace outlet temperature
- P-401 HIGHBottoms pump vibration
Proven on real offshore wells
Field data from offshore oil wells, one sample per second, every event labelled by experts. Checks written from those labels before any run.
Three ways to engage
Baseline assessment
The full change package from one historian export, delivered in five business days.
For a first look, an audit finding or a PSM action item.Continuous improvement
Everything in Tier 1, re-run monthly against your live historian, with improvement verified run to run and MOC tracking.
For sites keeping an alarm program healthy over time.Enterprise program
Multiple units, cross-unit benchmarking, HAZOP safeguard validation and a dedicated analyst.
For multi-unit sites and consent-agreement or inspection preparation.
Questions engineers ask
How much history do you need?
Three months is enough for a baseline assessment. Up to twelve months captures seasonal swings, turnarounds and rare upsets, so the more you can send, the more the analysis can see.
Do you need access to our network?
No. You send an export through our client files area. We never connect to your control or business systems.
What export format do you need?
The standard alarm and event export from your historian or DCS. If you are unsure which one, we will tell you exactly what to pull.
Our DCS is not Experion or DeltaV. Can you still help?
Suppression rules come in native import format for Honeywell Experion and Emerson DeltaV. For any other platform you get the same rules as a structured file with every field your engineers need to enter them, plus the full analysis.
Does this replace a rationalization workshop?
It replaces most of the work. You get the data and the changes up front, so any decisions that still need operations are few and quick to settle.
What do we need to do on our side?
Pull the export, review the package with your engineers, and implement through your normal MOC process.
Start with the baseline assessment.
Tell us your site, DCS platform and roughly how many tags. We reply the same day, seven days a week, with a scope and a secure upload link.