Use cases
Monitor natural disasters
Monitor natural disasters with SUZU Monitor. Combine earthquake, disaster, fire, and weather reports to prepare a local business continuity monitoring note.
Who this workflow helps
Business continuity analysts and operations teams monitoring facilities or regional dependencies.
When to start
An earthquake, flood, wildfire, cyclone, or weather alert near a location on the watch list.
What you will produce
A hazard watch note with source timestamps, potentially exposed locations, confirmed impacts, and local follow-up actions.
End-to-end workflow
- Define locations and dependencies
List the facilities, transport links, and service areas that matter. Open the natural-event, fire, and weather layers. Keep an exact facility location in your own operations record when the public map does not contain it.
- Inspect the original hazard report
Read the event type, observation time, severity, and source. USGS earthquake reports, GDACS alerts, NASA EONET events, and FIRMS detections describe different observations. Do not treat their categories as interchangeable.
- Check exposure and local impact
Compare the reported hazard area with the monitored location. Consult local authority notices and facility contacts for impact. An epicentre or fire point is not the full affected area.
- Assign the continuity follow-up
Record confirmed damage separately from possible exposure. Name the local contact, the next source update to check, and the review time. Use official emergency instructions for immediate protective action.
Worked example
Illustrative scenario: an earthquake appears near a supplier city. Record the earthquake time and magnitude, then check official impact information and the supplier contact. A nearby epicentre does not prove that the facility has stopped operating. Keep the supplier response pending until confirmed.
Provenance, freshness, and limits
Reporting latency and geographic coverage vary by hazard. Satellite fire detections are not evacuation boundaries. SUZU Monitor is a situational-awareness tool and does not issue emergency instructions or certify a location as safe.
Check the observation time and original source before each decision. This guide describes a repeatable procedure, not a live incident report. Data availability depends on provider coverage and the selected product view.
Common question
Does an empty map mean there is no hazard?
No. A provider can be delayed, filtered, or missing coverage. Check the source timestamp and local authority information before treating a quiet map as evidence.