FoxALM alarm management for high-consequence operationsFoxALM alarm management
Three to twelve months of alarm data in. A change package back in five business days.
We turn your historian export into DCS-ready suppression rules, PID retuning parameters and an ISA-18.2 KPI audit. Every finding arrives with the evidence behind it, so your engineers can check the work instead of trusting it.
DCS-ready suppression rules, PID retuning parameters and an ISA-18.2 KPI audit, each with the evidence behind it.
No network access to your systems. No site visit for the baseline assessment.
- Assessed against
- ISA-18.2-2016
- IEC 62682:2022
- EEMUA 191
- API RP 1167
How an engagement works
Three steps. You do the first one, and it takes an afternoon.
- Step 1, your team
You export your alarm history
Three to twelve months of alarm and event data as a standard export from PI, DeltaV, Experion or equivalent. You send it through our access-controlled client files area. We never connect to your systems.
Three to twelve months from PI, DeltaV, Experion or equivalent, sent through our client files area. We never connect to your systems.
- Step 2, FoxIQ
We analyse every alarm
More than 25 independent analytical methods trace floods to their first alarm, separate chattering caused by tuning from chattering caused by the instrument, and measure every ISA-18.2 KPI.
Floods traced to their first alarm, chattering separated by cause, every ISA-18.2 KPI measured.
- Step 3, within five business days
You receive a change package
Suppression rules in your DCS vendor’s native import format, PID parameters ready for faceplate entry, and the KPI audit. Each recommendation carries its evidence and a confidence measure.
Suppression rules in your DCS import format, PID parameters and the KPI audit, each with its evidence.
Proven on real offshore oil wells.
We ran FoxALM end-to-end on sensor data from offshore oil wells, one sample per second, with every event labelled by experts. All ten event classes. Every check written from those labels before the first run. Every one passed.
Read the field validationWhat lands on your desk
Three reports written for three audiences, plus the files your engineers implement from. Not a report to file: changes to review, approve and put through MOC.
- Board summaryAn ISA-18.2 grade from A to D, the costliest problems in plain language, and what to do first.
- Shift manager briefThe alarms loading your operators, and workload by shift.
- Technical reportEvery finding, per tag, with its evidence, confidence and the clause it answers to.
KPI audit against ISA-18.2 §16.4
| Metric | ISA-18.2 target | Result |
|---|---|---|
| Mean alarm rate per operator | ≤ 6 / h | 1.5 / h |
| Peak alarms in any 10 min | ≤ 10 | 12 |
| Flood events | Minimise | 4 |
| Chattering tags | 0 | 2 |
| Standing alarms | Few, reviewed | 3 |
suppression_rules.csv
root FIC-901 cooling water flow low
suppress P-401 bottoms pump vibration high
basis When the root is active, downstream
alarms are consequences. The root
alarm covers the hazard state.pid_tuning_recommendations.csv
tag FIC-301 Kp -0.315 Ti 1338 s Td 207 s gain margin 3.52 phase margin 59.1° stable
Every run also writes a manifest: fingerprints of the files you sent, the exact pipeline version, and every output produced. Anyone can check that a result came from your data and reproduce it.
Compared with a traditional rationalization workshop
| Traditional workshop | FoxALM | |
|---|---|---|
| Time to first results | Three to six months to mobilise, facilitate and document | Five business days from your export |
| Your people on site | Weeks of facilitated sessions with operations and engineering | None for the baseline assessment |
| What you receive | A rationalization report | A change package in your DCS vendor’s import format |
| Proof it worked | Not usually part of the scope | Before and after statistical comparison, included |
Built for high-consequence operations
Process industries where alarm system failure has a measurable cost.
- Refining and petrochemicalPSM-grade rationalization and SIS trip correlation for units where alarm counts have grown with decades of modifications.ISA-18.2 OSHA PSM
- LNG and gas processingFlood analysis under short time-to-consequence, with KPIs split by startup, steady state and shutdown.ISA-18.2 IEC 61511
- Pharmaceutical and biotechBatch-phase alarm analysis with the audit trail preserved through every step.ISA-18.2 21 CFR Part 11
- Pipeline SCADAControl-room workload modelling and long-line response time analysis.API RP 1167
- Power generationUnit trip and black-start alarm sequence audits with response time documentation.ISA-18.2 NERC
- Datacenters and critical facilitiesBMS and EPMS alarm rationalization and cascade analysis for Tier III and IV facilities.ISA-18.2
PLC code review
Code, narratives, cause-and-effect matrix and as-configured controller, checked against each other. Every mismatch shown, interlocks verified, logic proven efficient and correct scan by scan.
About PLC code reviewL5 Studio
Our own development environment for Rockwell Logix projects. We use it on every code review and standardization job: whole projects read and written losslessly, ladder and Structured Text in full.
About L5 StudioInsights
All insightsSend us your historian export. We'll show you what's in it.
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.