Surfside (Florida), 2021. When a building fails, there is almost always a long pre-history – years of degradation that rarely shows up as clear numbers until it’s late. In the Champlain Towers South case, public updates have repeatedly pointed attention toward the pool deck area and the slab–column connection, while earlier public materials referenced waterproofing/water intrusion issues and concrete damage beneath the deck.

If I had to choose only one first sensor layer that most often provides an early, measurable signal in these scenarios, it would be water and moisture monitoring.

1) Which sensors

A. Leak sensor (rope/spot) Captures “wet/dry” states and logs discrete leak events.

B. Moisture-in-material / concrete moisture Shows that moisture didn’t just pass through – it is persisting inside the material.

C. RH/T (relative humidity + temperature) + dew point calculation Helps distinguish leaks from condensation, and reveals when the space lives in a “constantly damp” regime.

2) Where to place them

The goal is to cover water pathways and accumulation zones:

• Under the pool deck / garage ceiling (where water above can migrate into slabs, joints, and interfaces).
• Low points and drainage zones (where water sits the longest).
• Expansion joints, penetrations, transitions, entry/drive-in areas, and planter-adjacent zones (common sources of chronic moisture).

Why this matters: in real buildings, failed or degraded waterproofing rarely produces a single dramatic incident – it produces repeated exposure. Repeated exposure is the pattern that drives long-term damage.

3) What the dashboard must show

Three outputs turn moisture into an управляемый, engineering-grade risk signal:

1) Wet persistence (hours/days “wet” over a period) If a zone is wet for 2–3 hours after a storm, that’s one thing. If it’s wet for tens of hours every week, that is a degradation regime.

2) Recurrence (event frequency) How often the same zone returns to “wet” status each week/month.

3) Zone hotspot map A heat map of “where it stays wet the longest and most often,” so remediation is targeted, not scattered.

4) What operations should do when the system flags a “bad pattern”

A dashboard shouldn’t produce anxiety – it should produce action:

• “Zone A: wet persistence > X hours/week” → inspect waterproofing, joints, drainage, slope/ponding.
• “Zone B: recurrence rising month-over-month” → trace the leak source and confirm the pathway.
• “RH/T indicates a condensation regime” → ventilation/dehumidification + verify surface temperatures and thermal bridges.

Why I start with water/moisture

Because it’s the most common primary driver that:

• accelerates rebar corrosion (especially in coastal environments),
• increases the probability of degradation at critical connections,
• and almost always appears before large, obvious deformations show up.

Next post

I’ll cover the second layer: rebar corrosion monitoring (half-cell + LPR/ER) – how to measure corrosion as a rate and trend, not as an opinion, and how to link it to moisture exposure into a single, clear risk picture.