Communications Resilience#

Jon Brewer (Telco2)

• Why: Physical-infrastructure risk modeling is squarely in the "running networks" skillset: knowing that your fiber routes share a road, a transformer, or a liquefaction zone is the difference between claimed and actual redundancy. This is a practical methodology talk for infrastructure dependency mapping.
• What: An approach to mapping telecom infrastructure to identify vulnerabilities and assess risk: data collection and maintenance strategies, dependency mapping (shared power transformers, single-road access routes), and visualization of natural hazards (fault lines, liquefaction zones, landslide-prone areas). (from abstract only)
• How: Correlate asset location data with shared-dependency and geohazard datasets, visualize overlap, and use the resulting map to drive risk assessment and hardening priorities.
• Where applicable: Methodology is broadly applicable to any operator or large enterprise with physical plant; the hazard layers shown are NZ-specific (fault/liquefaction data), but the technique transfers anywhere geohazard data exists.