Storm Prep

What you can build

• Open a hurricane checklist in Corrigo from a watch

  A hurricane watch for the property's zone arrives from the NWS API. The operator proposes the checklist as Corrigo work orders, each with a WorkZone and a due time before onset, for the manager to approve in one pass.

  With Weather & Severe Alerts, Corrigo Enterprise

• Put snow vendors on standby

  A winter storm warning triggers a MaintainX work order per plow and salt vendor, plus a Twilio SMS to each. Approval sends both; the receipt records who was asked and when.

  With Weather & Severe Alerts, MaintainX, Twilio

• Check sump pumps before a flood warning

  When a flood warning is active, the operator reads pump run state over BACnet/IP. A pump that should be running and is not becomes a proposed MaintainX work order with the point value attached.

  With Weather & Severe Alerts, BACnet / IP, MaintainX

• Notify residents by email and SMS

  One notice per property is proposed with the alert headline and your standing text. On approval it is sent through SendGrid and Twilio, and delivery events are kept against the alert.

  With Weather & Severe Alerts, Twilio SendGrid, Twilio

Requirements

• The NWS zone, county, or point for each property, so alerts and forecasts can be filtered to it
• A work order connector: Corrigo Enterprise or MaintainX, with a user that may create and assign work orders
• A checklist per alert type per property, with the vendors and the notice text, entered in the configuration
• Optional: BACnet/IP reach to the building network with a read allow-list; Twilio SendGrid or Twilio for notices

Authentication

No credential of its own. NWS data is public; work orders, building points, and messages go through the connectors you bind under the access each holds.

Limits

• It reads NWS alerts for locations in the United States. Warnings from other agencies need a different signal
• The checklist is yours. The operator does not decide what a warning means for a building; it runs the list you wrote
• It reads BACnet points; it does not write setpoints or start equipment. A point that reads wrong becomes a task for a person
• A notice goes out once per alert per property after approval. An alert update raises a new proposal rather than a resend

Questions and answers

What is approved, and by whom?

Three things, separately: the work orders, the vendor standby requests, and the resident notice. Each proposal shows the alert behind it, the checklist items, the assignees, and the message text. Approve all, edit, or decline any one.

What does the record show after the storm?

The alert as received with its onset and expiry, the checklist version used, the work orders and standby requests as created, the notice text and its delivery status, each approval with name and time, and the close-out when the alert ended.

What happens when a warning arrives at night?

The proposal is raised and waits. Nothing is created or sent until a person approves it. The on-call manager is told through your messaging connector, and the proposal is there when they open it.