Petroleum safety alarms for depots and stations
Safety alarms are the part of the fuel module a depot buys as an obligation, not a feature. Trakora ships a vapour alarm, a high-temperature alarm, and a grounding alarm tied to tanker discharge — the events an operator under EWURA and fire-safety scrutiny must be able to see and record, rather than discover after an incident.
Fuel safety alarms at a glance
- Rules it owns
- fuel_vapor · fuel_high_temp · fuel_static_ground
- What they cover
- Vapour · over-temperature · discharge grounding
- Vapour threshold
- —1 set per site
- Temperature threshold
- —1 set per product
- fuel_static_ground trigger
- —2 grounding-continuity, inferred
- Alarm lifecycle
- Raised · acknowledged · escalated
- Reporting output
- Safety events on the compliance record
- Regulatory framing
- EWURA petroleum · fire safety
- Who it's for
- Depots, terminals and stations under safety scrutiny
Vapour, temperature, grounding
These three read as fire-safety obligations more than product stories. Two have clear, gauge-based triggers; the third is described here attributively, with its exact trigger source confirmed per installation rather than asserted.
Vapour detected where it should not be
A vapour concentration is picked up in an interstitial space, a sump or a manhole — the early sign of a leak or a build-up before it becomes an ignition risk on the forecourt.
A vapour alarm named to the location, so the forecourt or bay can be checked and ventilated while it is still a warning, not an incident.
Investigate the source, restrict the area if needed, and keep the event on the safety record for the fire and EWURA file.
Product temperature above its limit
The product temperature rises above the threshold set for it — relevant both for temperature-corrected volume and as a safety signal in its own right.
A high-temperature alarm that separates a genuine hazard from a volume-correction quirk, named to the tank.
Check the cause — a hot delivery, sun load, or something worse — and record the reading, rather than letting an unexplained rise pass unseen.
Grounding during tanker discharge behaviour unverified
The fuel module ships a rule named fuel_static_ground, associated with static-discharge safety during tanker offloading. Its exact trigger source — most plausibly a grounding or bonding continuity input on the discharge bay — is —2 and is confirmed against the installation, not asserted here.
Static discharge during offloading is a recognised ignition risk, which is why an earthing and bonding step is part of a safe discharge. An alarm on that step is the distinctive, uncontested part of this cluster.
Attributively. On this page the specifics of what the sensor reads and at what point it fires are marked as figures to be confirmed, so nothing is stated as fact that has not been read from the rule evaluator.
An obligation, recorded
A depot under EWURA and fire-safety scrutiny does not shop for "features" — it shops for the ability to see a hazard early and to prove it managed one. These alarms are built for that reading.
Seen early, not after
Vapour and temperature alarms turn a slow-building hazard into a warning on a screen, so a discharge or a forecourt can be stopped before an incident, not investigated after one.
/ leak-alarmsOn the discharge bay
The grounding alarm sits with the riskiest routine moment at a depot — a tanker offloading — where a missed earthing step is the classic static-ignition scenario.
/ tank-monitoringAcknowledged and escalated
A safety alarm is not just raised; it is acknowledged and escalated through the chain, so a serious event cannot sit unseen on one idle screen.
/ hardware-gatewayOn the compliance record
Every safety event lands in the record, so when a regulator or an insurer asks how an event was handled, the answer comes from the log, not from memory.
/ reports-complianceArming the safety alarms
Each alarm needs its sensor fitted and its threshold set for the site.
Fit the sensor for each alarm
A vapour sensor, a temperature probe, and — for the grounding alarm — the discharge-bay input the rule reads. Each alarm depends on its sensor being present.
Set the thresholds per site
The vapour and temperature limits are configured for the site and product, not shipped as one fixed value across every depot.
Raise, acknowledge, escalate
When a threshold is crossed the alarm is raised, then acknowledged and escalated through the chain so it cannot sit unseen.
Keep the safety record
Every event is stamped into the compliance record for the fire, EWURA and insurance file.
What this cannot do
What to expect
- These raise operational safety alarms. Trakora is not a certified fire-detection, gas-detection or earthing-verification device, and does not replace a certified detection system, a suppression system, or a formal grounding test where one is mandated.
- The fuel_static_ground rule is described attributively: the alarm exists in the module, but its exact trigger source is treated as a figure to be confirmed and read from the rule evaluator per installation, never stated as fact here.
- Vapour and temperature thresholds are configured per site and product and are not fixed defaults — no concentration or temperature value is quoted on this page.
- Each alarm depends on its sensor being fitted and reporting. A vapour or grounding alarm cannot fire without the sensor the rule reads, and a silent device is flagged by fuel_device_offline.
- Alarms report over the gateway; a coverage or power interruption delays delivery, so these complement — they do not replace — the local safety systems a depot is required to have.
Values marked — are figures to be confirmed: the vapour concentration and product-temperature thresholds are configured per site and product rather than shipped as module defaults. No concentration or temperature value is stated as fact on this page.
Behaviour unverified. The fuel_static_ground rule ships in the module, but its precise trigger source is inferred from the rule name and is marked — until read from the rule evaluator in code. The plausible reading — a grounding or bonding continuity input on the tanker-discharge bay — is stated as a possibility, not a fact, and is confirmed per deployment before any specific behaviour is claimed.
Frequently asked questions
What safety alarms does the fuel module ship?
Three: a vapour alarm, a high-temperature alarm, and a grounding alarm tied to tanker discharge. Each raises, is acknowledged and escalates, and lands on the safety record.
What exactly does the grounding alarm detect?
The fuel_static_ground rule is associated with static-discharge safety during offloading. Its exact trigger source is confirmed per installation and marked as a figure to be confirmed here, rather than asserted as a fact.
Is this a certified fire or gas detection system?
No. These are operational alarms. They do not replace a certified fire-detection, gas-detection or suppression system, or a formal grounding test where one is required.
What thresholds do the alarms use?
The vapour and temperature thresholds are set per site and product, so no concentration or temperature figure is published here — they are not fixed module defaults.
Why is the temperature alarm on this page and the ATG page?
Temperature matters twice: for temperature-corrected volume on the gauging page, and as a safety signal here. The same reading is used for both, framed for each audience.
Do these replace my depot's local safety systems?
No. They complement the local safety systems a depot is required to have by making hazards visible early and keeping them on the record. They are not a substitute for certified equipment.
More in fuel management
fuel_leak and fuel_high_water shell-integrity cluster.
Put safety alarms on the record
Tell us about your depot or station and we will scope the safety alarms in TZS, with a TRA-EFD VAT invoice and Swahili support.