Ops · Alarm Rationalization — Product Overview

End-to-End Workflow

One system. The complete alarm management lifecycle.

From the moment an updated alarm source export is imported to the moment a compliance officer signs the monthly review — every step happens inside a single application, with a complete audit trail at every stage.

Start

🔄

Alarm Source Onboarding

New alarm configs imported. Only changed alarms flagged for review.

→

📋

Rationalization

ISA-18.2 classification, consequence matrix, priority calc. Single or bulk.

→

🛡

Safety Reviews

Monthly review of designated safety-related alarms. Overdue escalation.

→

📊

AMR Report

Full ISA-18.2 KPI report with AI narrative. Compliance officer signed.

→

🔗

P2P Verification

Field setpoint verification. Two-phase sign-off: operator + CO.

→

Output

📁

Doc Control

Every document auto-registered. Inspector walk-in ready, always.

Dashboard

Your compliance posture — the moment you open the app.

No clicking around to find out where you stand. Rationalization completeness, pending alarms, safety review status, and overdue items are front and center every session.

Total alarms vs. rationalized — percentage complete by site
Pending alarms surface immediately after any alarm source import
Overdue safety reviews escalate to red automatically
Recent activity log — who changed what, when

Pending Draft Approved Deferred Overdue

Core Workflow

Alarm Rationalization — Single and Bulk

Single Alarm

Every ISA-18.2 field. One screen. No spreadsheet.

Double-click any alarm to open the rationalization dialog. Classification, consequence severity matrix, automatic priority calculation, cause/consequence/response documentation — all in one place. Save as Draft or Approve with a timestamped signature.

Alarm Class — Safety / Abnormal / Diagnostic
Consequence severity rated across Safety, Environmental, Financial, Operational
Priority auto-calculated from Class × highest Consequence — derivation shown inline
Site-specific priority overrides applied and documented in the record
Cause, consequence, and corrective action text fields with character guidance
Full rationalization history — every prior version preserved

Priority Calculation

Transparent, defensible, auditor-visible.

Priority is never a guess. The formula — Class × highest consequence tier — is displayed inline on every record. No inspector has to take your word for it; they can follow the logic without opening a manual.

Site-specific override matrices are configurable in Settings and any applied override is documented within the alarm record itself, creating a self-contained justification chain.

Full derivation shown on every rationalization record
Per-site override matrices — no code changes required
Override justification auto-documented in the record

Bulk Rationalization

Hundreds of alarms. One workflow. One signature.

Filter to a group — same type, same site category, same class. Select all. Open bulk rationalization. Field-level checkboxes give you surgical control: apply classification and consequence ratings across the group while leaving individually-documented notes untouched.

Select any subset of alarms from the filtered list
Checkbox controls per field — apply only what you intend
Scenario templates pre-fill the group in one step
Exact count confirmed before any records are written
Approve All — one action, one signature, N records locked

Scenarios

Build once. Apply to any alarm — individually or in bulk.

Scenarios are pre-configured rationalization templates for common alarm types: High Pressure, Gas Detection, Tank Level, Low Flow, ESD, and any others specific to your operation. Select a scenario and the classification, consequence ratings, and response procedure pre-fill automatically.

New scenarios are created and managed in Settings — no developer involvement, no deployment. Add a scenario for a new instrument type and it's available immediately.

Unlimited scenario templates, fully configurable
Apply in single-alarm dialog or bulk rationalization
Scenario applied is recorded in the rationalization history

AI-Assisted Rationalization

Cause. Consequence. Corrective Action.
Three fields that used to take hours.

Every alarm rationalization requires documented answers to three critical questions: Why does this alarm fire? What happens if it's ignored? What must the operator do? These are the compliance fields auditors read first — and the hardest to write for a fleet of hundreds of alarms. The AI writes the first draft, grounded in the alarm's classification, impact scores, and your existing rationalization history. Requires a customer-provided LLM account — see AI Requirements below.

Single Alarm — Full Dialog

Complete the impact matrix. The AI does the writing.

Set the alarm classification (Class, Type), then rate the five impact dimensions — Safety, Environmental, Financial, Operational, Regulatory — on the ISA-18.2 0–4 scale. The calculated priority updates instantly.

Click Suggest next to any documentation field and the AI drafts a Cause, Consequence, or Corrective Action statement using:

The alarm's classification and alarm type
The full impact assessment just entered
Similar alarms already rationalized in your own database
Your indexed compliance documents — CRM plan, SOPs, procedural references
PHMSA 49 CFR 192.631 / 195.446 regulatory framing where applicable

Review the draft. Refine it with plain-language instructions. Condense it for brevity. Accept it into the field. Every edit stays yours — the AI never writes directly to any record without a deliberate Accept click by a named, logged user.

Quick Disposition — For disabled alarms (No Equipment Installed, Operator Only, Decommissioned), one radio button + Apply & Approve auto-fills all documentation fields and approves in a single click. No AI needed, no manual entry. Clears the disabled-alarm backlog fast without sacrificing documentation.

Bulk Rationalization — Dozens at Once

One rationalization. Applied to every similar alarm in your fleet.

Filter to a group of similar alarms — all High Pressure alarms at a site, all BS&W sensors across a gathering system, all Comm Fail points of the same type. Select them all. Open Bulk Rationalization.

Set the classification, impact matrix, and documentation once. Check which fields to propagate. Click Apply — the same rationalization stamps every selected alarm in seconds.

Select by site, type, class, or free-text search — any filter combination
Field checkboxes control exactly which values propagate — partial updates are fine
AI-drafted Cause / Consequence / Corrective Action applies across all selected alarms
Quick Disposition handles disabled alarms in mixed selections automatically
Preview before apply — review every field that will change across all N alarms
Bulk Approve after review — moves the entire group to APPROVED in one pass

A rationalization effort that would take a team weeks manually documenting 300 similar alarms clears in hours — with audit-grade, field-specific documentation on every record.

The AI Suggestion Workflow

Every suggestion is generated, reviewed, and accepted by a named human — never written directly to a compliance record

✎

Generate

Click Suggest on any field. The AI drafts Cause, Consequence, or Corrective Action using the alarm's classification, impact ratings, matching records from your database, and your indexed compliance documents.

💬

Refine

Type plain-language feedback in the same dialog: "Make it specific to high BS&W conditions" or "One sentence max, operator language." Multi-turn refinement until it reads exactly right.

📋

Condense

One click compresses verbose output to operator-ready brevity. The full draft is saved — switch back anytime if the condensed version loses a critical detail.

✓

Click Accept. The text moves into the documentation field under your name and timestamp. Nothing enters a compliance record without this deliberate step — AI involvement is logged on every accepted suggestion.

Scenarios — Quick-Fill Templates

Save any completed rationalization as a reusable Scenario. Common alarm types — High Pressure, High Temperature, Leak Detection, Comm Fail — rationalize in seconds when a Scenario pre-fills the full impact matrix and documentation fields. Combine with AI refinement for the last 10%.

Full Audit Trail on Every Record

Every rationalization — who wrote it, when saved, when approved, every field that changed — is logged to the Rationalization Database. AI-drafted text is flagged. If a PHMSA auditor asks how a priority was justified, the complete history is in the record. Nothing is ever overwritten or deleted.

Primary Working View

The Alarms Tab — Every Alarm. Every Site. Always Current.

The Alarms tab is the primary workspace. Every alarm across every site, filterable in seconds. The detail panel on the right shows the alarm configuration from your latest imported snapshot and the full rationalization record for any selected alarm — without opening a dialog.

Filter, find, and act — at any scale.

Works equally well with 50 alarms or 50,000. Every filter combination is remembered between sessions so you don't reset your view every time you open the application.

Filter by site, alarm type, alarm class, priority level, or rationalization status — any combination
Status color coding: Pending (amber) · Draft (blue) · Approved (green) · Deferred · Overdue (red)
Click any row — alarm configuration from your latest imported snapshot appears in the right panel instantly
Right panel shows setpoints, class, and enabled state as of the last imported snapshot
Right panel also shows the complete rationalization record: class, consequences, priority derivation, cause/consequence/response, who approved it and when
Double-click any row to open the full rationalization dialog
Multi-select for bulk rationalization — select all filtered results in one click
Sort by any column — site, tag, type, priority, status, last modified, approved by
Export the current filtered view to Excel for reporting or external review

Alarm Source Onboarding

Your alarm database. Any platform.
OPS builds the bridge.

Ops works from a normalized alarm record — name, path, type, priority, enabled state, setpoint configuration. The rationalization engine itself is platform-agnostic. Getting your alarm database into that format is a separate implementation step, and it looks different for every platform and every customer configuration. How that bridge gets built is your choice — OPS offers two options.

Option A — OPS Builds the Bridge

OPS scopes and delivers the alarm source bridge for your specific environment as a separate implementation engagement. No two alarm system configurations are alike — even on the same platform — so this work is always scoped to your actual data. We engineer the mapping layer from your alarm source export to the Ops normalized record format, validate it against your real alarm inventory, and hand you an import process that runs the same way every time going forward. Works with Ignition, ClearSCADA, FactoryTalk View, Wonderware, or any platform that can produce a structured alarm or tag export.

Option B — Your Team Builds It

For customers who want to own the integration layer internally, OPS provides the complete import framework — the normalized alarm record schema, field mapping specification, validation rules, and import interface documentation your team needs to build and maintain the bridge on your own timeline. You handle the source extraction and transformation; Ops handles everything from the point of import forward. OPS is available to validate your first import and answer questions through initial onboarding.

Intelligent Change Detection

Knows exactly what changed. Doesn’t make you re-rationalize what didn’t.

When alarm configurations change in your source system and a new export is imported, Ops automatically classifies what’s new, what was deleted, and what was modified — at the field level. Only alarms whose configuration actually changed are flagged as Needs Review. Every already-approved record remains approved.

New alarms — queued as New
Modified configs — only changed alarms flagged as Needs Review
Deleted alarms — flagged for review and removal
Setpoint changes separated from structural config changes
Bulk accept or review individual changes before committing

Snapshot History & Changelog

Every configuration. Every change. Preserved permanently.

Every imported snapshot is stored in full. The Configuration panel shows exactly what any alarm’s parameters looked like at any point in time. The Changelog panel shows the field-by-field diff between every consecutive snapshot — what changed, from what value, to what value, and when.

This is what answers inspector questions on the spot, without hunting through backup files or emailing the engineering team.

Infinite snapshot history — no rolling purge
Field-level diff between any two snapshots
Per-alarm configuration at any historical date
Changelog exportable as part of audit package

Ongoing Alarm Management

Rationalization doesn’t end at Approval.
The database runs the program.

Initial rationalization is a project. Alarm management is a program — one that runs continuously, every time your alarm configuration changes, every month when PHMSA compliance reviews are due, every time an inspector walks in the door. Ops is built around a compliance database that maintains the complete, unbroken history of your alarm rationalization program from day one forward. Nothing is overwritten. Nothing is deleted. Every action is logged. Every state is reconstructable.

Alarm Master List — Always Current

Every import of your alarm source is compared against the prior state at the field level. New alarms are queued. Modified alarms are flagged as Needs Review only for the fields that changed. Removed alarms are tracked, not deleted. The master list reflects your current configuration at all times — with full history of every version before it.

Append-Only History — No Lost Data

Every rationalization record, every field change, every approval — captured in full before and after. The database never overwrites; it appends. Any alarm’s complete rationalization history is always accessible. Point-in-time reconstruction lets you show exactly what a record said on any date — the date of a prior inspection, a prior incident, a prior change request.

Change Detection — Between Every Import

Each new alarm source import triggers a field-level comparison against the last known state. What changed? Which setpoints were adjusted? Which alarms were added or removed? The diff is surfaced for review before anything is committed — with full control over what to accept, investigate, or flag for re-rationalization.

Complete Traceability — Every Step, Every User, Every Timestamp

When a PHMSA inspector asks how a priority was assigned, who approved it, what it was before, and when it changed — the answer is in the database, not in someone’s memory.

User Actions

Every create, edit, approve, defer, and bulk operation is logged with the acting username, timestamp, and before/after field values. No anonymous changes.

AI Involvement

Every field where an AI suggestion was accepted is flagged in the record. The original suggestion, refinements, and final accepted text are all retained. Full accountability, no black box.

Approval Chain

Every approval records who reviewed, who signed, what version was current at approval time, and what compliance period it covers. Approvals cannot be backdated.

Priority Changes

Priority change requests are tracked as discrete events — requested by, justification, approved by, effective date. The full trail from original configured priority to current assigned priority is always visible.

Defensible at Any Moment

The database is the answer to every auditor question — not a printout prepared the week before the inspection. Because every record, every decision, and every approval has always been there, the audit package reflects what actually happened, not what someone reconstructed after the fact.

Database-Driven by Design

Ops is designed to work with any standard relational database your organization prefers or already has in place. The compliance schema is purpose-built for long-term record-keeping — soft deletes, append-only history tables, and point-in-time query capability from the start. No data is ever physically removed. Database platform is an implementation decision made at onboarding, not a constraint imposed by the software.

Alarm Monthly Review

ISA-18.2 Monthly KPI Report — Generated, Narrated, Signed, Registered.

The AMR is not a spreadsheet export. It's a complete, signed compliance document — cover page, KPI analysis, nuisance alarm tables, chattering analysis, standing alarm tracking, AI-drafted performance narrative, and compliance officer signature — auto-registered in Document Control.

What's Generated

Every metric ISA-18.2 and PHMSA expect to see.

Total alarm event count with month-over-month trend
Priority distribution — P1/P2/P3/P4 breakdown and percentages
Top nuisance alarms table with event counts and recommended actions
Chattering alarms — identified, counted, tracked against prior months
Standing alarms — alarms active longer than threshold, named
Flood event log — periods of abnormally high alarm rates
Safety-related alarm performance — review compliance status
AI-drafted narrative — plain-language interpretation of trends
Compliance officer signature — reviewed, approved, timestamped

View Full AMR Report →

Alarm Monthly Review — ISA-18.2 Compliance

OPS-AMR-2026-04 — April 2026

Dorado Crude Gathering · Optimal Pipeline Solutions

OPS-AMR-2026-04

ACTIVE

Total Events

3,847

↑ 4.2% vs prior

Priority 1

142

3.7% of total

Nuisance Rate

12.4%

Threshold <15%

Chattering

↓ 2 vs prior

Top Nuisance Alarms

#	Alarm Tag	Events	Priority	Action
1	Tank_101_LVL_HI	218	P2	Setpoint review
2	Pump_A_DISC_PRS	187	P1	Deadband review
3	Compr_1_SUCT_LO	143	P3	Monitor
4	Separator_HI_LVL	119	P2	Setpoint review

AI Performance Narrative

April 2026 showed a modest 4.2% increase in total alarm events relative to March. The nuisance rate of 12.4% remains within ISA-18.2 thresholds (<15%) but warrants continued attention to Tank_101_LVL_HI, which generated 218 events — a 31% increase. Chattering alarms decreased from 5 to 3, indicating effective follow-through on March corrective actions. Recommend setpoint review for Tank_101_LVL_HI before the next reporting cycle.

Compliance Officer Sign-Off

R. Calloway

Compliance Officer · Optimal Pipeline Solutions

2026-05-03 08:14 CST

✓ Signed & Registered

Document Control Registration

OPS-AMR-2026-04
Registered automatically on signing
Status: ACTIVE
Retrievable in OPS Document Control

In the Application

Select a site. Select a month. Generate. Sign.

Any site, any historical month. Reports are generated from your imported alarm journal data — the same data your SCADA system exported, stored in your confidential Rationalization Database. No connection back to Ignition is required at report time.

Historical reports re-generatable from preserved journal data
AI narrative drafted automatically — reviewed and edited before signing
Compliance officer signs directly in the application
Signed report saved as PDF and registered simultaneously
Prior AMR reports browsable and downloadable from Document Control

Point-to-Point Verification

Field Verification — Two Signatures. Zero Manual Filing.

P2P verification confirms that alarm setpoints configured in Ignition match the physical instrumentation in the field. The OPS workflow enforces the regulatory two-party requirement: the field operator verifies physically; the compliance officer signs off independently.

Phase 1 — Field Operator

Every instrument. Every setpoint. Confirmed in the field.

The field technician works through device cards in the live HTML report. For each instrument, they record actual physical readings against Ignition-configured setpoints, confirm within-tolerance status, and check off each point as verified. Progress is tracked live — the status bar shows exactly how many devices and permissives remain.

Device cards pre-populated from imported alarm config — no re-typing setpoints
Analog readings, discrete states, and permissive logic all on one form
Live progress: devices verified / total, permissives verified / total
Each verification timestamped and attributed to the technician
Notes field on every device for exceptions and field observations

Phase 2 — Compliance Officer

Independent review. Independent sign-off. One registered document.

After the operator completes field verification, the compliance officer conducts an independent review of all readings and exceptions before signing. The two signatures are physically separate and timestamped independently — no shared sign-off, no rubber-stamp workflow.

Compliance officer sees full operator verification before signing
Any flagged exceptions visible for CO review and disposition
CO signature with timestamp — separate from operator verification
Document automatically registered as OPS-P2P-YYYY-NNNN on CO signing
PDF saved to the designated Reports/P2P folder automatically
Registered record retrievable in OPS Document Control

View Full P2P Report →

P2P — Dorado Crude Devices:17 / 17 Permissives:28 / 28 Overall:100% ✓ All Points Verified

PT-101A Discharge Pressure — Pump A ANALOG · SAFETY

[Dorado]Tag_Providers/Pump/PT-101A/PV

Ignition SP

450 PSIG

Field Reading

449.3

Tolerance

✓ Pass

HI — 450 PSIG✓ Match

HIHI — 480 PSIG✓ Match

☑ Verified — J. Smith · 2026-04-17 09:42

FT-204 Crude Outlet Flow ANALOG

[Dorado]Tag_Providers/Flow/FT-204/PV

Ignition SP

2,500 BPD

Field Reading

2,498

Tolerance

✓ Pass

HI — 2,500 BPD✓ Match

LO — 500 BPD✓ Match

☑ Verified — J. Smith · 2026-04-17 10:15

Phase 1 — Field Operator

John Smith

Field Technician · 2026-04-17

✓ 17 / 17 Devices Verified

Phase 2 — Compliance Officer

R. Calloway

Compliance Officer · 2026-04-22

✓ OPS-P2P-2026-0047-R0

Embedded AI Analysis

An analyst that knows your alarm program — and only your alarm program.

The AI assistant works exclusively from two sources you control: the alarm master records imported into Ops, and the Rationalization Database — the rationalizations your team has completed, historical master alarm lists, and change history within the program. That is the full extent of its access — the rationalization database, nothing else. No connection to your SCADA system, your broader network, or any data source outside the Ops program. see.

What it does:

Draft rationalization narratives based on similar alarms already rationalized in your own database
Interpret AMR KPI trends in plain language for the monthly review narrative — working from your imported alarm journal data
Identify patterns across sites in your historical rationalization records — nuisance alarm trends, priority distribution shifts, chattering history
Explain ISA-18.2 methodology in the context of your own alarm types and classifications
Draft response procedures based on how your team has documented similar alarms historically

What it doesn't do:

No connection to your SCADA system, live plant, or any real-time data source
No AI output enters any compliance record without human review and explicit approval
No AI-generated text is submitted without a named user clicking Accept
Your alarm data and rationalization records are never used to train any model
Full usage and cost tracking built in — no surprise bills, no hidden consumption

AI Infrastructure Requirement. The AI suggestion capabilities require a customer-provided LLM account and appropriate API infrastructure. The large language models used for alarm rationalization assistance — drafting Cause, Consequence, and Corrective Action narratives from complex technical context — require a subscription to a capable LLM provider (such as OpenAI, Azure OpenAI, Anthropic, or a compatible on-premise deployment). OPS provides the integration layer, prompt architecture, and usage tracking. The customer establishes and owns the AI account and bears the associated usage costs. AI features are optional — every other function of Ops operates without an AI subscription.

You control what it sees. The AI works from your exported alarm records and your Rationalization Database — a confidential, internally-controlled repository of every alarm record, every rationalization, and every historical change. Nothing is sourced from external systems or real-time feeds.

The AI helps compliance teams work faster. It does not make compliance decisions.

Export & Audit Packages

Inspector Walk-In Ready — Any Time, Not Just Audit Season.

Export any combination of alarm records, rationalization history, safety reviews, and compliance certificates in seconds. Scoped to exactly what was asked for — not your entire database.

Scope it. Export it. Hand it over.

The export dialog lets you build a precise package: select the site, date range, alarm class, and status. A PHMSA inspector asking for "all Priority 1 safety-related alarms for Station 14, last 24 months" gets exactly that — no manual filtering, no pivot tables.

Alarm Master Export — full rationalization records for any filtered subset: tag, class, priority, consequences, response procedures, approval history
Rationalization History — every prior version of every record, showing what changed and who changed it
Safety Review History — all designated safety alarm reviews for the period, signed and timestamped
Ignition Config Snapshot — point-in-time Ignition configuration for any historical snapshot date
Compliance Certificate — summary PDF showing rationalization completion percentage, signing authority, and date
Format options — PDF for compliance documents, Excel/CSV for data analysis
Every export timestamped and labeled with the snapshot it was generated from
Exports are non-destructive — re-generate the same package any number of times

Settings & Configuration

Every Policy Decision — Configurable Without a Developer.

The application adapts to your operation's classification rules, consequence definitions, priority matrices, and site structure — all through a settings UI, with no code changes and no redeployment.

Settings panels — one per domain, all instantly effective.

Classification — define and label your alarm classes; add custom class types for your operation
Consequence Matrix — configure consequence categories, severity labels, and the priority derivation matrix
Priority Overrides — per-site priority override matrices; any override documented automatically in the rationalization record
Scenarios — create and manage rationalization scenario templates for any alarm type
Disposition & Response — pre-defined response procedure options and corrective action templates
Compliance Configuration — compliance officer designation, signing authority rules, review schedule intervals
Regulatory References — link specific CFR citations to alarm types for automatic inclusion in rationalization records
Reports — configure report headers, site names, output paths, and AI narrative behavior
Database — connection configuration and health status; test connection inline
Backup & Restore — automated backup schedule, manual backup, and restore from any backup point
Display & Window Sizes — per-user UI preferences retained across sessions
System Reset — admin-level data reset capabilities for test and staging environments

Consequence & Priority Matrix

Rationalization Scenarios

Compliance Configuration

Log & Audit Trail

A Complete Record of Every Action — For You and For Inspectors.

Nothing happens in the application without a trace.

The Log tab captures every significant action with user identity, timestamp, and before/after values. This isn't application debugging output — it's a compliance audit trail built for inspectors and compliance officers.

Rationalization History — every change to every alarm record, who made it, what it was before
System History — application-level events: syncs imported, reports generated, exports run, settings changed
AI Log — every AI interaction: prompt, response, what was accepted vs. discarded, cost per query
Error Log — connectivity issues, failed operations, and resolution status
All log panels are filterable and exportable
Log data is stored in the database — survives application updates and reinstallation
At inspection: "When was this alarm's priority changed and by whom?" — answered in seconds from the rationalization history panel

Document Control

Every document numbered. Every document retrievable. Forever.

OPS Document Control is a separate module within the OPS CRM suite — a dedicated compliance document registry that assigns permanent numbered IDs, manages the full document lifecycle, and serves as the single retrieval point for every controlled document across all OPS applications. When Ops Alarm Rationalization generates a compliance report, it registers that document in OPS Document Control automatically. The number is assigned by Document Control. The document is retrievable there. No manual filing. No lost documents. No “I thought someone saved that.”

AMR

OPS-AMR-YYYY-MM

Monthly alarm performance review. Generated per site per month. Auto-registered when compliance officer signs.

P2P Verification

OPS-P2P-YYYY-NNNN

Field setpoint verification. Registered when compliance officer completes Phase 2 sign-off. Revisions tracked as R1, R2, etc.

Alarm Reports

OPS-ARR / OPS-ASR

Alarm rationalization and safety review reports. Full revision lifecycle — draft, sign, revise, void — all tracked.

At a PHMSA inspection: The inspector asks for the alarm monthly review for March 2025. The compliance officer opens Document Control, searches OPS-AMR-2025-03, and opens the PDF — in under 30 seconds, with a complete chain of custody showing who generated it, who signed it, and when. No email chains. No shared drive hunting.

Complete Feature Reference

Everything the application does.

🔄

Alarm Source Onboarding & History

Alarm source import & onboarding bridge
Intelligent diff — only changed alarms flagged as Needs Review
Setpoint changes separated from config changes
Unlimited snapshot history, never purged
Field-level changelog between snapshots
Export configuration history for audit

📋

Alarm Rationalization

Full ISA-18.2 rationalization dialog — single alarm
Alarm Class: Safety / Abnormal / Diagnostic
Consequence severity matrix (4 categories)
Automatic priority calculation — derivation shown
Site-specific priority override matrices
Cause / consequence / corrective action documentation
Draft → Approve lifecycle with signatures
Full rationalization history per alarm

⚡

Bulk Rationalization

Multi-select any filtered subset of alarms
Field-level checkbox control — apply selectively
Scenario templates applied to groups
Count confirmed before any write
Approve All — single signature, N records
Bulk history tracked per alarm

🎯

Scenarios & Templates

Pre-configured templates for common alarm types
Classification + consequence + response pre-filled
Apply in single or bulk rationalization
Unlimited scenarios — managed in Settings
No code changes required to add/modify
Scenario used recorded in rationalization history

🛡

Safety-Related Reviews

Designate alarms as safety-related (CO action)
Monthly review schedule tracked per alarm
Overdue escalation to dashboard
Review record: findings + disposition + signature
CO sign-off required per review cycle
49 CFR 192.631 / 195.446 compliant workflow

📊

Alarm Monthly Review (AMR)

Total events with month-over-month trend
P1/P2/P3/P4 distribution and rates
Top nuisance alarms table with action tracking
Chattering alarm identification and trending
Standing alarm log
Flood event detection and logging
AI-drafted performance narrative
CO signature + auto-registration (OPS-AMR)

🔗

P2P Verification

Device cards pre-populated from imported alarm config
Analog readings, discrete states, permissive logic
Live progress tracking (devices + permissives)
Phase 1: operator field verification
Phase 2: independent CO sign-off
Exception flagging with CO review required
Auto-registration as OPS-P2P on CO signing

🤖

AI Assistant

Works from your Rationalization Database — exported alarm records, full rationalization history, all change records
Draft rationalization narratives from similar alarms
AMR performance narrative drafting
Pattern analysis across sites and periods
All output requires human review before acceptance
Full usage and cost tracking built in
Configurable per operation — prompts and context

📁

Document Control

Auto-registration on every document sign-off
Numbered document IDs (AMR, P2P, ARR, ASR)
Full revision lifecycle — R0, R1, R2, void
CO appointment and authority tracking
Inspector-ready search and retrieval
PDF saved + registered simultaneously

Why OPS

How does this compare to the alternatives?

Most operations manage alarm rationalization in spreadsheets, shared drives, or nothing at all. Here's what that means at inspection time.

Capability	Ops · Alarm Rationalization	Spreadsheets + Shared Drive	Nothing / Ad-hoc
ISA-18.2 consequence matrix	✓ Built in, enforced per record	Manual — if someone remembers	✗ Not tracked
Automatic priority calculation	✓ Formula shown, auditor-visible	Formula in a cell, easily broken	✗ Guessed or skipped
Monthly ISA-18.2 KPI report	✓ Generated from your imported alarm journal data	Manually assembled — hours of work	✗ Not produced
AI performance narrative	✓ Drafted automatically, human reviewed	✗ Written from scratch each month	✗ Not produced
P2P two-phase sign-off	✓ Operator + CO signatures enforced	Paper form — may or may not exist	✗ Not tracked
Document auto-registration	✓ Numbered ID, instant on signing	✗ Manual — folder somewhere	✗ No registry
Ignition config snapshot history	✓ Every snapshot, field-level changelog	✗ Not captured	✗ Not captured
Safety review overdue tracking	✓ Automatic escalation, dashboard alert	Calendar reminder — if maintained	✗ Missed silently
PHMSA inspection readiness	✓ Inspector walk-in ready, always	Days of prep work at inspection time	✗ Hope the inspector is lenient

Every alarm rationalized.Every audit ready.

One system. The complete alarm management lifecycle.

Alarm Source Onboarding

Rationalization

Safety Reviews

AMR Report

P2P Verification

Doc Control

Your compliance posture — the moment you open the app.

Alarm Rationalization — Single and Bulk

Every ISA-18.2 field. One screen. No spreadsheet.

Transparent, defensible, auditor-visible.

Hundreds of alarms. One workflow. One signature.

Build once. Apply to any alarm — individually or in bulk.

Cause. Consequence. Corrective Action.Three fields that used to take hours.

Complete the impact matrix. The AI does the writing.

One rationalization. Applied to every similar alarm in your fleet.

The AI Suggestion Workflow

The Alarms Tab — Every Alarm. Every Site. Always Current.

Filter, find, and act — at any scale.

Safety-Related Alarm Monthly Reviews — Nothing Slips.

Your alarm database. Any platform.OPS builds the bridge.

Knows exactly what changed. Doesn’t make you re-rationalize what didn’t.

Every configuration. Every change. Preserved permanently.

Rationalization doesn’t end at Approval.The database runs the program.

Complete Traceability — Every Step, Every User, Every Timestamp

ISA-18.2 Monthly KPI Report — Generated, Narrated, Signed, Registered.

Every metric ISA-18.2 and PHMSA expect to see.

OPS-AMR-2026-04 — April 2026

Select a site. Select a month. Generate. Sign.

Field Verification — Two Signatures. Zero Manual Filing.

Every instrument. Every setpoint. Confirmed in the field.

Independent review. Independent sign-off. One registered document.

An analyst that knows your alarm program — and only your alarm program.

Inspector Walk-In Ready — Any Time, Not Just Audit Season.

Scope it. Export it. Hand it over.

Every Policy Decision — Configurable Without a Developer.

Settings panels — one per domain, all instantly effective.

A Complete Record of Every Action — For You and For Inspectors.

Nothing happens in the application without a trace.

Every document numbered. Every document retrievable. Forever.

Everything the application does.

Alarm Source Onboarding & History

Alarm Rationalization

Bulk Rationalization

Scenarios & Templates

Safety-Related Reviews

Alarm Monthly Review (AMR)

P2P Verification

AI Assistant

Document Control

How does this compare to the alternatives?

Stop preparing for inspections.Be ready for them.

Every alarm rationalized.
Every audit ready.

Cause. Consequence. Corrective Action.
Three fields that used to take hours.

Your alarm database. Any platform.
OPS builds the bridge.

Rationalization doesn’t end at Approval.
The database runs the program.

Stop preparing for inspections.
Be ready for them.