Create and Edit a Storm Model

A storm model defines when a storm will come and estimates how long it will take to restore power to customers who lose power as a result of the storm. Storm models are typically created before a storm enters the service territory and remain in a Draft state until shortly after restoration activities begin.

After you create a storm model, you can edit its details and add one or more Estimated Restoration Timelines (ERTs) to it. The ERT results in a graphical chart for tracking and analysis.

Create a Storm Model

  1. Sign in to Storm ERT.
  2. From the Storm ERT dashboard, click Create Storm Model.
  3. In the Storm Model Details page, complete the following fields:
    • Name: Add a distinct name for the storm model, such as Sally or Mark, or something based on an established convention in your organization.
    • Start Date: Set the date and time when the storm will enter your service territory.
    • Cut-Off Date: Set the date and time after which new outages will be excluded from the storm model. This is usually the date and time when the storm leaves your service territory. However, you may want to set the cut-off date and time to a time later than when the storm leaves. For example, if a storm leaves the area at 2 a.m., you may want to set the cut-off date and time to a time later in the morning, such as 11 a.m. on the same day. This way, any outages caused by the storm that customers report when they wake up in the morning will be included in the storm model.
    • End of Restoration (optional): Set the estimated date and time when you expect all outages will be fully restored. The date and time should be later than the Cut-Off Date. Even though this field is marked optional, it is highly recommended, since it is a way to indicate a definite end to the restorations even if there are still a few outages left. Refer to About Setting the End of Restoration for more details. You can set this field later if you want. For example, you can set it one or two weeks after the storm model has been approved and most of the outages have been restored.
    • Operating Company: Choose an operating company. This determines what storms will be listed on the Similar Storm Events page.
    • Crew Allocation Strategy: Choose a crew allocation strategy. This determines whether to base the crew assignment on feeders or outages. You might prefer "Feeder-first" for storms where localized efficiency is key, while "Outage-first" is ideal for situations where addressing high-priority outages quickly, regardless of location, is the top concern.
      • Feeder-first (Default): Crews will focus on fixing all outages on one feeder (a specific power distribution line) before moving to the next. This approach is efficient for utilities that prioritize completing work in a single area before moving on, even if it means temporarily skipping higher-priority outages on other feeders.
      • Outage-first: Assigns crews based on the priority of individual outages, such as those affecting hospitals or critical infrastructure, regardless of the feeder they’re on. This strategy ensures the most urgent outages are addressed first, even if it means crews move between different areas more frequently.
    • Exclude Single Customer: Select this option if you want to exclude any outages that affect a single customer rather than multiple customers simultaneously. It is recommended that you select this option if you want to exclude outliers that may skew the results of a storm ERT.
  4. Click Continue.
  5. In the Similar Storm Events page, select storm events that can be used as a basis for the ERT calculation. You must select at least one storm event.

    Optionally, you can adjust the Weight of any storm events that have been selected. This will prioritize the ERT calculations of that storm relative to the other storm events. For example, you can increase the weight of recent storms above those that occurred in the more distant past. Note that higher numbers give greater weight to the storm while lower numbers give less weight (assigning a storm a weight of 10 indicates that the storm will have the maximum weight, whereas a weight of 1 is the lowest weight).

    You can use the search bar to find a specific storm, or you can use one of the available filters:
    • State: The list of storms is pre-filtered to exclude storms in a Cancelled or Draft state.
    • Type: The type of storm. It is recommended that you choose a type so that you can more easily search by it later or make comparisons to other storms of the same type.
    • Level: The severity level of the storm. The meaning for each level varies by utility due to regional differences in weather patterns, so consult your internal documentation if you need guidance on which level to choose. (For example, in some regions a few inches of snow are considered a major snow storm, while in other regions it is considered minor.)
  6. Click Continue.
  7. In the Derived Properties page, review the properties derived from the previously selected similar storm events and update if needed:
    • Type: The type of storm.
    • Level: The severity level of the storm.
    • Estimate Customers: The estimated number of customers who may lose power.
    • Estimate Outages: The estimated number of outages that may occur.
  8. Click Continue.
  9. In the Affected Zones page, select the zones in your service territory that will be affected by the storm based on the forecasted path of the storm.

    Note:

    Only the zones under the operating company you selected in the Storm Model Details page will appear in the list.
  10. Click Continue.
  11. Optional. In the ERT Details page, complete the fields below.

    Note:

    If you do not want to create an ERT at this point, then you can click Cancel. Your storm model will be saved as a Draft and added to the dashboard. You can create an ERT for it later.
    • Name: Enter a distinct and concise name for the ERT. For example, you could use ERT1 to indicate that it is the first ERT created for the storm model. This name will be used as a label for the ERT after it is created.
    • Crew Schedules: If necessary, edit or adjust the prepopulated columns for the crew schedules of each zone. You will be able to update this information later. Initial crew shifts are split into two 12-hour periods of the day: 7 a.m. and 7 p.m. (The Global zone row is editable except for Efficiency.)
      • Estimated Customers: Adjust the estimated number of customers in the zone who are expected to lose power.
      • Estimated Outages: Adjust the estimated number of outages anticipated in the zone.
      • Day 1 AM Crews, Day 1 PM Crews, etc: Adjust the number of crews dispatched in each 12-hour period of a day as needed for each zone. (Day 1 AM Crews refers to the first 12 hours of day 1, Day 1 PM Crews refers to the second 12 hours of day 1, and so on.) The number you choose will likely depend on factors such as the storm class. For example, you may want to increase the number of crews planned for a class 2 storm as opposed to a class 1 storm. Changing a global crew number refreshes the zone level number with the new allocation where the values are proportional to the number of sub-zones.
      • Efficiency: The default efficiency is 5. Adjust the efficiency with which crews are able to restore outages, based on your knowledge of historical storms. Efficiency basically refers to how quickly the crews can work. The default efficiency values displayed are derived from predefined, utility-specific configurations for each storm class. For additional guidance on this action, see the correspond step in Create and Edit a Storm ERT.
  12. In the Restoration Rates page (appears only if the storm model is in "tail mode", wherein the Cut-Off Date is in the past and there are active outages), review at a zone-level detail the devices which were affected by the current storm. The estimated restoration rates and crew requirements are used to predict and display restoration milestones in the ERT Details page.
    • Zone: A drop-down menu that lets you view restoration rates associated with the different zones in your service territory.
    • Device Type: The name of the device type associated with the storm event.
    • Current Storm Outages: The total number of devices of this type which failed during the storm event.
    • Current Storm Restored: The total number of devices of this type which has been restored so far.
    • Current Storm Hours Needed: The average number of hours needed to repair the device type. This number is calculated by subtracting on-site time (the time spent by the crew repairing the device) or en route time (the time that the crew gets on the road) from restore time (the time when the device was restored). If on-site time or en route time is not available, then "off time" is subtracted from restore time.
    • Current Storm Crews Needed: The average number of crews needed to repair the device type. A value of "0" may indicate that power was restored without sending a crew. For example, power may have been routed from a different location to restore the outage.
    • Similar Storm Hours Needed: The average number of hours needed to repair the device type in the selected similar storm.
    • Similar Storm Crews Needed: The average number of crews needed to repair the device type in the selected similar storm.
    • Estimated Hours Needed: The predicted number of hours to repair the device type, based on an average of the data in Hours Needed and Hours Needed from Similar Storms. However, a weight of 80% is given to the current storm data, whereas a weight of 20% is given to the data from similar storms.
    • Estimated Crews Needed: The predicted number of crews to repair the device type, based on an average of the data in Crews Needed and Crews Needed From Similar Storms. However, a weight of 80% is given to the current storm data, whereas a weight of 20% is given to the data from similar storms.
  13. Click Create ERT.

    The storm model and an associated ERT are created, and the storm model view opens.

About Setting the End of Restoration

The End of Restoration field is an optional field which allows you to specify a date and time when all outages were restored, and after which no remaining outages are counted. You can set the field when you first create the storm model or at a later time, such as one or more weeks after the storm has passed.

It is highly recommended that you set this field even if there are a few outages left. Sometimes those outages are outliers, and sometimes they are results of errors in the data. If the End of Restoration is not set, and a few outages remain, then the storm will be considered not fully restored.

A storm that is not fully restored can have several negative effects in the application. One effect is that the storm will skew the predictions of other storm models whose calculations are based on it. A second effect is that the ERT Details step in the Create ERT editor, as well as Workplan tab of another storm model, could display an inordinately large number of crew shifts for any similar storm that was not fully restored, since the application will assume that outages from such storms still need to be addressed. A third effect is that the storm restoration chart could display a graph that continues on indefinitely.

About Post-Storm Estimated Restoration

The Post-Storm Estimated Restoration calculation logic automatically updates all ERTs and generates more accurate predictions by averaging historical device type restoration rates and adjusting these rates based on the current restoration rates. For example, the calculation logic can predict that after four hours of the cut-off date, it will take 14 hours and two crews to repair seven (out of the 16) broken device types.

Edit a Storm Model

You can edit a storm model's details as long as no ERTs have been created for it. If an ERT has already been created and you realize you need to edit the storm model details, then you must create a new storm model with the correct details. (You can cancel the storm model that has erroneous details.)
  1. Sign in to Storm ERT.
  2. From the Storm ERT dashboard, search for and click the name of the storm model you want to edit.
  3. In the storm view that opens, click Edit.
  4. On the Edit Storm Model page, edit the Storm Model Details and Affected Zones, and click Save.