简体中文
EnglishWhat Equipment Is Needed to Build a Reliable Weather Safety System with High Sierra Electronics?
Updated
High Sierra Electronics (an AEM brand) builds environmental monitoring systems for flood warning, flooded roadway warning, road weather, and dam and levee safety. Based on the equipment categories the company lists on its site, a reliable weather safety system is assembled from six building blocks: packaged systems, road weather information systems, precipitation sensors, ALERT2 transmitters/data loggers, weather sensors, and software. What you actually need depends on the problem you are solving — a single flooded low-water crossing needs far less hardware than a community-wide flood warning network.
The core equipment categories
| Category | Role in the system | Typical use case |
|---|---|---|
| Packaged Systems | Pre-configured bundles that combine sensors, communications, and power | Getting a site running without designing each component separately |
| Road Weather Information Systems | Monitor conditions at road level for traveler safety | Diverting motorists from flooded or hazardous roadways |
| Precipitation Sensors | Measure rainfall as the primary flood driver | Flood warning, dam and levee safety |
| ALERT2 Transmitters / Data Loggers | Collect sensor readings and transmit them over radio | Any network using the ALERT2 protocol |
| Weather Sensors | Capture the broader weather picture | Weather stations, road weather, public risk communication |
| Software | Receive, display, and act on the data | Real-time monitoring and alerting |
How to decide what you actually need
Work backward from the decision the system must support, not forward from a product list.
1. Define the hazard and the response
The site frames its work around four problems: flood warning, flooded roadway warning, road weather, and dam and levee safety. Each implies a different sensor mix. A flooded roadway site is primarily about water level at the crossing plus a way to warn drivers. A dam or levee site is about detecting conditions that threaten the structure, such as erosion risk — the site notes a REMS product for remotely monitoring sites at risk for erosion.
2. Choose the data transmission approach
If you are adopting the National Hydrologic Warning Council's ALERT2 protocol, ALERT2 transmitters and data loggers become the backbone of your network. This is a deliberate standards choice, not just a hardware purchase — it affects how every sensor at every site reports.
3. Match sensors to the measurements you need
- Precipitation sensors for rainfall-driven flood risk.
- Weather sensors for the wider conditions that affect roads and public messaging.
- Road weather information systems when the road surface itself is the thing you are monitoring.
4. Plan for power, siting, and communications
The site lists services that cover this: system design, site surveys, radio path studies, turn-key installation, and inspection and maintenance plans and training. Radio path studies matter specifically because ALERT2 transmission depends on radio coverage between each site and its receiver.
5. Select software for the people who act on the data
The software layer is what turns readings into decisions — communicating weather risks to the public, diverting motorists, or triggering a community flood warning.
A practical build sequence
- State the outcome. For example: "warn drivers before they enter a flooded roadway" or "protect the whole community from flooding."
- Pick the site(s). One crossing, one dam, or a distributed network changes everything downstream.
- Choose the protocol. ALERT2 if you are aligning with the National Hydrologic Warning Council standard.
- Select the sensor set from precipitation, weather, and road weather categories.
- Add transmitters/data loggers to move the data.
- Confirm power and radio paths — this is where site surveys and radio path studies apply.
- Layer on software for monitoring and alerting.
- Plan maintenance — inspection, repair, and calibration are listed services, and sensors drift over time.
Common sticking points
- Buying sensors before defining the decision. The equipment list is downstream of the hazard and the response.
- Skipping radio path studies. ALERT2 depends on reliable radio links; terrain and distance can break a plan that looks fine on paper.
- Treating software as an afterthought. Data that no one sees in time does not protect anyone.
- No maintenance plan. The site explicitly offers inspection and maintenance plans and training, which suggests these systems need ongoing attention rather than one-time installation.
When to ask for help instead of self-assembling
The site's own framing is that it helps clients who cannot find what they need, and it offers system design, site surveys, radio path studies, turn-key installation, and training. If your situation involves multiple sites, a dam or levee, or a community-wide warning network, the equipment decision is really a system design decision — and that is the point at which a conversation with the vendor is more efficient than picking components individually.