FlowsBook a callSign inCreate free accountSign up
Workflows by industry

Heavy rain alerts for field crews: one weather note per depot, before the shift

Sewer and stormwater crews need to know where rain will fall hardest, not just that it will rain. How a water utility sends each depot its own forecast and standby note.

Part of the guide Workflow automation

By the xMap team · · 4 min read

Heavy rain alerts for field crews work best when each depot gets its own forecast, not one message for the whole region. A crew in the hills and a crew by the river face different storms on the same day. The method is simple: keep a table of your depots, plants and known trouble spots, read the forecast for each position every morning, keep only those where the rain crosses your threshold, and send each depot manager a short note with the hours to watch and what to prepare.

This is for water and wastewater utilities, drainage contractors, municipal works departments and anyone who sends crews to drains, pumping stations or flood-prone streets. It covers choosing a threshold, the shape of a good note, a worked example and the limits of a forecast.

Set the threshold from your own history

Every network has a level of rain at which things start to go wrong: a combined sewer overflows, a pumping station needs a second pump, a known street floods. That number comes from your incident records, not from a weather service. Look back at the last few storms that caused call-outs and note the rain that fell over a few hours and over the day. Many teams end up with two levels: one to put crews on standby, a higher one to pre-position equipment.

The Weather forecast block gives, for each place that reaches it, the rain expected over the days you ask for, the total in millimetres, the number of rain days, the next rain day and a one-line summary. It counts a rain day as one with 0.5 mm or more, which is far below most operational thresholds, so the Filter on rain in millimetres is where your own level goes.

What a useful crew note says

  • Where. The depot or site by the name your team uses, not a coordinate.
  • When. The hours the heaviest rain is expected, from the hour-by-hour forecast.
  • How much. The expected millimetres, compared with your threshold in plain words.
  • What to do. Your own checklist for that level: clear the screens at a named inlet, check the standby pump, keep a jetting truck back from routine work.
  • When it was read. So nobody acts on yesterday's outlook.

A worked example (made up)

Say a utility around Bogota runs crews from five depots and watches twelve pumping stations and inlets that overflow in heavy rain. Its table in My data holds each site with a name, a position, the depot that serves it and the manager's email.

  1. Schedule: every day at 05:00, and every 3 hours during the wet season.
  2. My data: the seventeen depots and sites.
  3. Weather forecast, Each incoming place: the next 2 days, rain included.
  4. Filter: rain total of 25 mm or more (the standby level from the utility's history).
  5. xMap LLM: a five-line note per site, using only the forecast it was given and the checklist for that level from a reference file.
  6. Email, one email per item, sent to each site's manager from the email column; a copy of all of them to the duty manager.

On a dry morning nothing is sent, which is the point: crews learn that a message means something. On a stormy one, the depot in the south might receive: "San Cristobal pumping station: about 38 mm expected, heaviest between 14:00 and 18:00. Above your standby level. Check the second pump and clear the inlet screen before noon." The north depot hears nothing, because its sites stay under 25 mm.

Mistakes to avoid

  • One alert for everyone. A region-wide message trains crews to ignore it. Send per site, only when a site crosses its level.
  • The weather service's threshold. 0.5 mm is a rain day, not a problem. Use your own number.
  • Only the daily total. 30 mm over a day and 30 mm in an hour are different storms. Use the hour-by-hour forecast for sites that flash-flood.
  • No owner for the message. Each site needs a named person. Keep the email or phone in the table and update it when people change.

Ready-made flows

Heavy rain hour by hour: stormwater crews on standby is the hourly version for wet days; Rain at our treatment plants: overflow risk reads your table of plants each morning; Storm drains to clear before the rain plans clearing ahead of a storm. For more on alerts in day-to-day operations, see the field operations guide.

Questions

How far ahead can the forecast look?

Up to 16 days, but for crew planning the next one to two days are the useful part. Further ahead, use it for rough planning only.

Can each depot get only its own message?

Yes. Keep the manager's email in your site table and set the Email block to one email per item, sent to that field.

What rain threshold should we use?

Your own, from past call-outs and overflows. The forecast's rain day starts at 0.5 mm, which is far too low for an operational alert.

Can it replace our rain gauges?

No. A forecast helps crews get ready; gauges and telemetry tell you what is actually falling and should trigger action on the day.

Templates that do this

Read next

More on workflows by industry · Every article · Templates

Put it to work

An AI employee in xMap Flows does this on live data, on its own timetable. Start from a template or describe it in plain words.