Skip to main content
For AI agents: a documentation index is available at https://docs.coverbase.com/llms.txt. This page is also available in markdown by appending .md to the URL.
This guide is part of the User Guides collection. It covers the natural hazard sources specifically; for reading and triaging the signals they produce, see the Radar signals guide. For where your vendors’ sites are, see the Risk geography map. For every source Coverbase draws on, see the source library.
A hazard feed never names your vendor. An earthquake report says “M 6.1, 2 km SW of Sakai, Japan”, not “your wafer supplier”. Coverbase connects the two through where your vendors’ sites are: each hazard is turned into an area on the map, and any vendor with a site inside that area is in scope. The most common reason these sources produce nothing is that the vendor has no located site. Add sites with addresses before you rely on this.

​
What Coverbase monitors

The Natural Hazards group in the source library holds seven sources. Each source only collects what is worth reading. Coverbase skips earthquakes below magnitude 4.5, GDACS green alerts, weather service alerts below Severe, and Meteoalarm yellow warnings and warnings that have already expired.
Hail has no feed of its own anywhere. It arrives inside US severe thunderstorm warnings and Meteoalarm thunderstorm warnings, which name hail when it is expected.

​
How a hazard reaches a vendor

Coverbase draws an area for each hazard and checks it against every active site of your active vendors. How a site is matched depends on how precisely you have located it: A located site is judged by distance only. A hurricane in Mexico does not reach a plant in Mexico City just because both are in Mexico. The areas are deliberately generous, because the detector judges how serious the hazard is for the site. The area only decides which vendors it is asked about.
Enter full addresses rather than a country alone. Coverbase converts addresses to coordinates on a schedule, so a site added minutes ago gets its own position shortly after. A site with only a country is reached by very few hazards.

​
Step 1. Locate your vendors’ sites

Open a vendor and add its sites on the Locations card, with a street address or at least a city. The card appears when the Risk module is on. The Risk geography map shows which sites have been located: a solid dot is a located site, and a country with only a hollow mark holds sites Coverbase cannot place yet.

​
Step 2. Turn on the detector

Go to Configuration → Radar, open the Detectors tab, and click Add detector → From detector library. Search for Natural Hazard Near a Supplier Site (it sits in the Geopolitical & External segment) and click Configure to add it and open it for editing, or Add detector to add it with its defaults. Enabling it adds the seven natural hazard sources to your sources where you do not have them already, and scopes the detector to them. You can also add the sources yourself from Sources → Add source → From Source Library, in the Natural Hazards segment, but nothing alerts until a detector reads them.
Only a detector scoped to these sources judges a vendor that a hazard reached through its site. Your other detectors keep reading what names the vendor, so they do not all start evaluating every storm near a supplier.
In the editor, check two settings:
  • Sources. Remove the sources for regions you have no suppliers in. Keeping them costs nothing, but removing them keeps the source list readable.
  • Severity threshold. The default is Medium. High limits alerts to destructive events at or very near a site, such as a strong shallow earthquake, a hurricane landfall or a red alert.

​
Step 3. Check what arrives

Go to Radar → Signals. A hazard signal names the sites it reached and how far each one is from the hazard, for example “inside the hazard area, 36 km from its centre”. The signal’s exposure lists each of those vendors as directly exposed. How the detector grades a hazard: Triaging what arrives works the same way as any other signal, which the Radar signals guide covers. A useful first step on a Medium or High signal is to ask the vendor to confirm the site’s status and its continuity plan.

​
What to know when reading these signals

The signal is about a place, not a company. The source will not mention your vendor. The link is the site, so check that the site is still in use before you act. The first report is not revised. Coverbase reads each earthquake and storm once, when it first appears. A later revision of the magnitude, or a storm that moves, does not create a new signal. GDACS publishes a new episode when an alert level changes, and each new episode is read. Several sources can report one event. A hurricane can appear in GDACS, NASA EONET and a US weather warning. Each source produces its own signal. Only the countries listed have Meteoalarm. Weather warnings elsewhere in Europe reach you only when GDACS or NASA EONET reports the event.

​
Troubleshooting

Working Radar signals

Reading the signal queue and turning a signal into work.

Risk geography map

Where your suppliers are, and which sites have been located.

Source library

Every source Coverbase draws on, across all tiers.

Detector library

The full catalog of detectors and what each one looks for.