Reference · built on requestOperator by FibricEnergy & demand

Storm Reserve

Reads NWS alerts, battery state of charge, and generator status, and proposes a reserve hold and readiness checks before an outage risk.

Request accessPricing ↗

About

When the National Weather Service issues a watch or warning for your county, the battery should be full and the generator ready before the lines go down. On an ordinary day the battery is busy earning against the tariff and the generator sits until its next exercise.

Storm Reserve watches active alerts for each site's zone, the battery's state of charge and reserve setpoints over Modbus TCP, and the generator controller's state, alarms, and fuel level over the same link. When an alert on your list is issued, it proposes a hold: raise the battery reserve to the storm level, suspend the dispatch schedule, and run the readiness checks the site keeps for its generator. A person approves each step, and the hold is proposed for release when the alert is cancelled.

This is a reference listing. It documents what Fibric would read from Storm Reserve 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 watches, warnings, and advisories for each site's county or zone from the NWS alerts API, as issued, extended, and cancelled
  • The NWS hourly forecast for the site: wind, precipitation, and temperature through the alert window
  • SoC, ChaSt, State, SocRsvMin, and the alarms in Evt1 from SunSpec model 802 over Modbus TCP
  • Generator controller registers over Modbus TCP: run state, run hours, fuel level, battery voltage, and active alarms
  • The dispatch schedule Battery Dispatch has approved for the day, so the hold knows what it suspends
  • Backup reserve as a monitoring platform reports it: SolarEdge battery backup reserve, or Enphase battery settings

Proposed actions

  • Target capability: propose raising SocRsvMin to the storm reserve you set and suspending the day's dispatch schedule while the alert stands
  • Target capability: propose a battery settings change through the Enphase API where the battery's reserve is managed there
  • Target capability: propose the generator readiness checklist as a work order in your CMMS, with the controller's readings attached
  • Target capability: propose a fuel delivery request to Fuel Reserve when the controller's fuel level will not cover the alert window
  • Target capability: propose releasing the hold and restoring the reserve setpoint once NWS cancels or expires the alert

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

What you can build

  • Fill the battery before a hurricane watch

    Read the NHC and NWS alerts for a coastal site, and get a proposed hold that raises SocRsvMin over Modbus TCP and pauses dispatch until the watch clears.

    With Weather & Severe Alerts, NHC GIS Data, Modbus TCP

  • Get the generator checked before the ice arrives

    When a winter storm warning is issued, the operator proposes the readiness checklist as a MaintainX work order with the controller's fuel, battery, and alarm readings attached.

    With Weather & Severe Alerts, Modbus TCP, MaintainX

  • Hold reserve on an Enphase site

    Where the battery is managed through Enphase, the hold becomes a proposed battery settings change, with the readiness checks filed in Fiix.

    With Enphase API, Weather & Severe Alerts, Fiix

Requirements

  • The NWS weather signal with each site's county or forecast zone
  • A Modbus TCP connector reaching the battery controller and the generator controller, with the registers named in a point map
  • The storm reserve you want held, and the list of alert types that should trigger a hold, in writing
  • A CMMS connector such as Fiix or MaintainX where the generator's readiness checklist lives
Authentication
Reads NWS alerts with no key, reads and writes battery registers only through the Modbus connector's per-device allow-list as approved proposals, and files work orders through the account your CMMS connector holds.

Limits

  • NWS alerts cover counties and zones, not sites. A warning for the county triggers a proposal whether or not your feeder is exposed.
  • Generator registers vary by controller make. The point map you supply decides what it can read, and it infers nothing beyond it.
  • A hold costs tariff savings for as long as it stands. The receipt shows the schedule it suspended so the trade is visible.
  • It does not start the generator, transfer load, or test the transfer switch. Those stay with the people on site.

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 Storm Reserve ↗

Questions and answers

What do you approve when an alert comes in?
Each hold and each release: the alert that triggered it, the reserve setpoint it will write, the dispatch schedule it suspends, and the checklist it files. You can hold without filing, file without holding, or dismiss both. Nothing is written until you choose.
What record does it leave?
A receipt per alert: the NWS alert id and text, the battery and generator readings at the time, the setpoint before and after, the work order id, who approved each step, and when the hold was released. The record is kept whether the outage came or not.
Will it start the generator?
It will not. It reads the controller and proposes a checklist for people to run. Starting, load transfer, and the transfer switch test are not among its proposals, and it writes nothing to the generator controller.
Ask about Storm Reserve

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