Incident Management Software for Energy & Utilities

Incidents in energy and utilities: one-hour notices, electrical occurrences and asset context

Energy and utility incidents often have two reporting audiences at once: the safety regulator for injuries and dangerous occurrences, and a sector regulator for the asset event itself. A US gas pipeline operator must notify the National Response Center no later than one hour after confirming an incident; in Great Britain an explosion or fire caused by an electrical short circuit or overload that stops the plant for more than 24 hours, or causes a significant risk of death, is a reportable dangerous occurrence. The first record created in the field has to be good enough to start those clocks.

Incidents here also belong to assets and places: a feeder, a pump station, a pipeline section. Test whether the incident can carry the asset identifier your network or asset system uses, and whether a travelling crew can report from a remote asset without signal.

Where contractors do field work on your networks, make sure that a contractor's incident on your asset is recorded against the asset and investigated with you, not only in the contractor's own system.

The written follow-up matters as much as the first call. After the one-hour telephone notice, a US gas operator revises or confirms it within 48 hours with estimates of gas released, deaths and injuries; a distribution operator then files a PHMSA form within 30 days and supplements it when new facts emerge, so an investigation that keeps finding things must keep the regulator's copy in step. In the EU, a control-system outage at a grid or water operator may also be a significant cyber incident, with its own 24-hour, 72-hour and one-month reports to a national CSIRT or authority. One event can start three clocks, each owned by a different team.

Gas networks add a public dimension. In Great Britain the conveyor of gas through a distribution system must notify HSE without delay when told that someone died, lost consciousness or was taken to hospital because of an injury connected with that gas, then report within 14 days. That first notice may come from a member of the public or the emergency services rather than your own crew, so check that an incident can be opened from a call-centre note as easily as from the field app.

Rules that shape this evaluation

• 49 CFR 191.5, US PHMSA gas pipelines: operators give notice of each defined incident at the earliest practicable moment and no later than one hour after confirmed discovery, by telephone to the National Response Center, stating the location and time of the incident and any fatalities or injuries; within 48 hours of confirmed discovery, to the extent practicable, the operator revises or confirms that notice with estimates of product released and of fatalities and injuries, or confirms the first estimates if nothing changed. (read 26 September 2026)
• RIDDOR 2013, Schedule 2, paragraphs 3 and 4 (Great Britain): an explosion or fire caused by an electrical short circuit or overload that stops the plant for more than 24 hours or causes a significant risk of death is a dangerous occurrence; so is any plant or equipment unintentionally touching an uninsulated overhead line above 200 volts, or coming close enough to cause an electrical discharge. (read 26 September 2026)
• 29 CFR 1904.39, US OSHA: a work-related death is reported to OSHA within 8 hours; an employee admitted to hospital as an in-patient, an amputation or an eye lost within 24 hours, by telephone, in person at the nearest Area Office or electronically. (read 26 September 2026)
• 49 CFR 191.9, US PHMSA gas distribution incident report: a distribution operator submits Form PHMSA F 7100.1 as soon as practicable and no more than 30 days after detecting an incident reportable under 191.5, and files supplementary reports that refer to the original by date and subject when relevant information arrives later; master meter operators are exempt. (read 26 September 2026)
• RIDDOR 2013, regulation 11 (Great Britain): a conveyor of flammable gas through a fixed pipe distribution system that receives notification of a person's death, loss of consciousness or being taken to hospital because of an injury arising in connection with that gas notifies HSE without delay and sends a report within 14 days of the incident, unless the event is notifiable or reportable elsewhere in the Regulations. (read 26 September 2026)
• Directive (EU) 2022/2555 (NIS2), Article 23(4) and Annex I: an essential or important entity (Annex I covers, among others, electricity undertakings, district-heating operators and water suppliers) sends the CSIRT or competent authority an early warning within 24 hours of becoming aware of a significant incident, a notification within 72 hours with an initial assessment of severity and impact, interim reports on request, and a final report no later than one month after that notification, as each Member State transposes it. (read 26 September 2026)

Summarised from the linked official texts, read on 25 September 2026 unless a rule shows its own date. This is buyer context, not legal advice: have the responsible specialists confirm which requirements apply to your sites.

Questions to settle for this combination

1. Can the first field report capture the time of discovery precisely enough to evidence a one-hour notice?
2. Can an incident carry the asset identifier from your network or asset register, and who maintains that list?
3. Can one event be reported to both the safety and the sector regulator without re-keying?
4. Can a crew report offline from a remote asset, and how is the notification escalated once the device reconnects?
5. Can contractor incidents on your assets be recorded and investigated alongside employee incidents?
6. When one event is both an injury and a significant cyber or service incident, can reports with different deadlines hang off the same record, each with its own owner, due time and sent date?

What the records should show

• The time of confirmed discovery and the time of each external notice, who made it and any reference number received, so the gap can be shown against the one-hour limit, plus the time of the 48-hour revision or confirmation and what changed in it.
• For a US gas distribution incident: the date the PHMSA form was filed, and each supplementary report with the date and subject of the original it updates.
• For a gas-related injury reported to you in Great Britain: who told you and when, the person's outcome (death, loss of consciousness or taken to hospital) and the date of the 14-day report.
• For an event that is also a significant incident under national NIS2 law: the early-warning, notification and final-report dates, the severity and impact assessment, and whether a malicious cause or cross-border impact was suspected.
• The asset identifier and network location as your register holds them, whether the asset was running, isolated or under a permit when the event happened, and for a line strike the voltage and whether contact or a discharge occurred.
• For contractor incidents on your assets: the contractor company, the work package, and a link to the investigation run jointly with them.

Which documented capabilities matter most here

Signals in the researched records of the listed products:

• Matched through a sourced tag or a documented capability rather than the primary category: EHS Insight, 1Life, Emex, Intelex, Synergi Life (DNV), Cority, Enablon, ERA-EHS, Benchmark Gensuite, Ideagen EHS, Onspring, Optial and Procore Quality & Safety.
• Offline use, as classified in the records: a documented offline workflow: EHS Insight, Emex, Intelex, Cority and Enablon; a partial offline workflow: 1Life, Synergi Life (DNV), ERA-EHS, Benchmark Gensuite, Ideagen EHS and Procore Quality & Safety. No classification yet for 2 of the 13.
• A published price amount is on record for EHS Insight, 1Life, Emex, Intelex, Synergi Life (DNV) and ERA-EHS; the other 7 need a quote.
• A free trial is documented for EHS Insight, 1Life and Synergi Life (DNV).

Vendor-material signals, not test results; the commercial partner is not counted; no signal means not established.

A demo script for this combination

Ask each vendor to run these steps with synthetic data. They are demo requests, not observed vendor results.

1. Report a synthetic electrical fault that stops a plant, from a remote asset without signal, recording the time of discovery.
2. Reconnect and show when the office was alerted relative to that time.
3. Attach the asset identifier from your register and route the event to both the safety and asset owners.
4. Record the external notification as a timed step with who made it.
5. Add a new fact to the synthetic incident three weeks later and show how the supplementary regulator report points back to the original.
6. Open a second, linked record for a control-system outage caused by the same fault, carrying its own 24-hour and 72-hour deadlines.