Reference · built on requestOperator by FibricSafety, security & compliance

Severe Weather Notice

Matches severe weather, wildfire, and earthquake alerts to your sites and who is badged in, then proposes the notice your plan calls for.

Request accessPricing ↗

About

Severe Weather Notice is an operator for the sites in your emergency action plan. It reads active alerts from the National Weather Service by zone or point, earthquakes from the USGS feeds as they post, and satellite fire detections from NASA FIRMS inside a box you draw around each site. It matches each one to a site by location, reads who is badged in from your access control platform, and picks the response your plan names for that event and severity: shelter in place, stop work, or evacuate.

It then proposes the notice, the channels it would go to, and the people it would reach. A person approves it before anything is sent. The operator does not sound the building alarm and does not write the plan; it follows the one you wrote.

This is a reference listing. It documents what Fibric would read from Severe Weather Notice and what it could propose, based on the vendor's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • Active alerts from api.weather.gov for each site's zone or point, with event, severity, urgency, certainty, onset, expires, and instruction
  • Earthquakes from the USGS GeoJSON feeds, updated every minute, with magnitude, place, time, and the tsunami flag
  • Fire detections from NASA FIRMS inside the area you draw around each site, from the VIIRS and MODIS sources you select
  • Badge-in events at each site from Verkada, Brivo, or Genetec Security Center, for a count of who is on site now
  • Site coordinates, the alert zone each sits in, and the response your emergency action plan assigns to each event type
  • Alert updates, expiries, and cancellations, so a notice is not proposed twice for one event and an all-clear can follow

Proposed actions

  • Target capability: propose a shelter-in-place notice to the people badged in at the affected site, for your approval
  • Target capability: propose a stop-work notice to site leads through Microsoft Teams or Slack when an alert crosses the threshold your plan sets
  • Target capability: propose an evacuation notice by SMS through Twilio, naming the assembly point from your plan, once a person approves
  • Target capability: propose a page to the incident lead through xMatters or PagerDuty, with the alert text and the on-site count
  • Target capability: propose an all-clear when the alert expires or is cancelled, and a record of who was accounted for

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Shelter a warehouse before the tornado warning lands

    A Tornado Warning covers a site's zone. The operator proposes an SMS through Twilio to everyone badged in through Brivo, with the shelter location from your plan. A person approves it before it is sent.

    With Weather & Severe Alerts, Twilio, Brivo Access

  • Stop outdoor work when a fire detection is near

    FIRMS reports a VIIRS detection inside the box around a yard. The operator proposes a stop-work notice to the site lead in Microsoft Teams with the distance and the detection time.

    With Wildfire Detection, Microsoft Teams

  • Account for people after an earthquake

    A USGS event posts near a site. The operator proposes an evacuation notice to the badge-in list from Verkada, a page to the incident lead through xMatters, and a roll-call record a person fills in at the assembly point.

    With Seismic Activity, Verkada, xMatters

  • Send the all-clear only once

    When the NWS alert expires, the operator proposes one all-clear to the same Slack channels the notice used. The record shows who was reached, when, and who approved it.

    With Weather & Severe Alerts, Slack

Requirements

  • At least one hazard or weather signal: Weather & Severe Alerts, Seismic Activity, or Wildfire Detection
  • One access control connector that reports badge events, such as Verkada, Brivo, or Genetec Security Center
  • One messaging connector for the notice: Twilio for SMS, Microsoft Teams or Slack for channels, xMatters or PagerDuty for pages
  • A written emergency action plan with each site's coordinates, alert zone, assembly point, and the response for each event type
  • A free FIRMS map key if wildfire detections are in scope
Authentication
Public feeds are read with the free NWS, USGS, and FIRMS access your signal connectors hold. Notices go out through the credentials of your messaging and access control connectors; the operator is granted none of its own.

Limits

  • It reads public feeds. If the NWS or USGS host is unreachable, no alert is seen, and the operator says so rather than guessing.
  • Badge-ins count who entered, not who left. A site without exit readers gives an upper bound, not a roll call.
  • A satellite fire detection is a hot spot, not a fire boundary. Distance to a site is measured from the detection point.
  • The notice is a message. It does not trigger the building's alarm system, which your plan keeps as a distinct signal.

Access and pricing

Reference listing. Fibric builds the operator under a managed deployment when you request it. Your quote covers the build, capabilities, usage, and support.

Request Severe Weather Notice ↗

Questions and answers

What does a person approve before a notice goes out?
Each notice: the alert that triggered it, the site matched, the count of people badged in, the response the plan names, the message text, and the channels. Approve it, change the text, or dismiss it. Nothing is sent, and no alarm sounds, until a person approves.
What record is left for each alert?
One record per alert per site: the alert identifiers and text, the badge-in count at the time, the notice sent, who approved it, and who was accounted for at the assembly point. Each notice keeps a receipt: what was sent, to whom, why, and how to follow it with a correction.
Does it ever send a notice or sound an alarm on its own?
No. It reads feeds and badge events and proposes. A person approves every notice, including the all-clear. It never sounds the employee alarm system your plan requires, never releases doors, and never contacts emergency services.
Ask about Severe Weather Notice

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This operator is developed, published, and supported by Fibric. Third-party names and logos identify the systems an integration connects to; they are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy