The Global Centre for Risk and Innovation (GCRI)
Standards, codes and safety management systems set the level of protection infrastructure provides. They cover design loads, materials, inspection intervals, process safety, security and continuity. This page sets out how standards shape infrastructure risk, where they lag behind changing hazards, and what evidence serves the standards bodies, regulators and asset owners who apply them.
GCRI · In development · service level R0
Infrastructure standards are the codes, specifications and management systems that set the level of protection assets provide, from design loads to inspection intervals. They rest on historical hazard data, so they can lag behind a changing climate, and they protect only when applied, inspected and maintained.
For asset standards and safety, in GCRI's spatial-intelligence reading, the map opens on night lights, population density and true-colour imagery, framed on Western Europe; 3 further NASA layers wait in the list.
The interactive map needs JavaScript; the layer list and sources are below.
Layers 3
Activity and exposure, for this page
Keyboard, with the map focused
Hold Ctrl or ⌘ and scroll to zoom
Latest available
NASA GIBS / EOSDIS · ASTER GDEM (METI, NASA) · Blue Marble (NASA) · © OpenStreetMap contributors (ODbL) · Natural Earth
Loading the latest NASA imagery.
Drag to move. Ctrl or ⌘ and scroll, pinch or the buttons to zoom; hover for the values under the pointer; reset returns to the region.
For asset standards and safety, in GCRI's spatial-intelligence reading, the map opens on night lights, population density and true-colour imagery, framed on Western Europe; 3 further NASA layers wait in the list.Satellite and model products as NASA publishes them, each with its own date; indicators, not assessments of any place; claim ceiling INTEGRATED.
Layers and dates
The working screen behind this subject: its structure, terms and states. Names are placeholders and values illustrative.
Asset standards and safety · Lifeline system A · Register v4
| SS-12 | Electricity | Tier 1 | Flood 1-in-100 | 8 |
| WTW-2 | Water | Tier 1 | Flood 1-in-100 | 30 |
| DX-1 | Telecom | Tier 2 | Heat | 8 |
| H-Campus | Health | Tier 1 | Earthquake | 91 |
| PN-3 | Transport | Tier 2 | Storm surge | n/a |
red: SS-12 and its dependants
Operator authority and engineering assurance. The dossier below sets out how the risk develops, what is measured, where the data come from, how it is modelled and who decides.
Codes specify design loads from wind, flood, earthquake and heat based on historical data. As hazards change, assets built to past assumptions may be under-designed.
Standards protect only when applied, inspected and maintained. Gaps between the standard and practice are often larger than gaps between standards.
Defects are found only when assets are inspected. Long intervals and visual-only inspection miss deterioration that sensors or detailed testing would find.
Asset management, safety management and continuity management systems connect standards to decisions about maintenance, renewal and investment.
Each term as this page uses it. Where a standard-setting body defines the term, the wording follows that body.
| Term | Definition |
|---|---|
| Design load | The force or condition, such as wind or flood, that a structure is designed to resist. |
| Inspection interval | The maximum time allowed between successive inspections of an asset, set by a standard or regulator. |
| Safety management system | An organized approach to managing safety, including policies, accountabilities, procedures and assurance. |
Each indicator carries its unit, its cadence, the kind of source behind it and the evidence label a value would carry. No values are shown: a programme supplies them under its own authority.
| Indicator | Unit | Cadence | Source type | Label |
|---|---|---|---|---|
| Assets designed to current hazard standards | percent of asset base | per assessment | Asset registers | ESTIMATED |
| Inspections completed on schedule | percent of planned inspections | annual | Inspection records | REPORTED |
| Overdue safety-critical maintenance | count of items | monthly | Maintenance management systems | OBSERVED |
| Standards revised for climate change | count of design standards updated | per revision cycle | Standards body records | OFFICIAL |
| Regulatory enforcement actions | count by type | annual | Regulator records | OFFICIAL |
| Process safety events | count by tier | annual | Operator safety reporting | REPORTED |
The topic as a computational graph: named sources feed the methods, an evidence review gates the outputs, and the decisions stay with the authorities that hold them.
Fig. 02Nodes carry their type, two metric rows and a state; connectors show what feeds what; dashed frames name the owners; the timeline is the cadence. Design of the pipeline, not a record of a run.
Named public datasets and institutional records, each with its licence class. Sources by agreement are used only under their terms and never republished.
| Source | What it gives | Licence class |
|---|---|---|
| ISO 55000 series | Asset management principles and requirements | Licensed standards, purchase required |
| National building and infrastructure design codes | Design loads and requirements | Licence per standards body |
| Regulator inspection and enforcement reports | Compliance and enforcement records | Public records, licence per regulator |
| Safety investigation board reports | Investigations of infrastructure failures | Public records, terms per board |
| Standards body work programmes on climate adaptation | Revisions of standards for changing hazards | Public summaries, terms per body |
Critical Infrastructure prepares evidence. The decisions below are taken by the authorities named, under their own rules, and never by the platform.
| Who decides | The question | Evidence this page serves |
|---|---|---|
| Standards bodies and code committees | Which design values need revision for changing hazards | Hazard evidence compared with code assumptions |
| Infrastructure regulators | Where inspection and enforcement should focus | Inspection performance; enforcement records |
| Asset owners | Which maintenance and renewal to prioritise | Overdue maintenance; asset condition |
Engineering standards translate experience and research into rules for design, construction, operation and maintenance. They specify loads, materials, safety factors and testing. Many rest on historical hazard records, so a changing climate can make design assumptions outdated before assets reach the end of their lives. Standards are also revised slowly, through consensus processes, while technologies such as distributed energy and digital control evolve quickly.
Safety assurance in high-hazard industries uses structured arguments, often called safety cases, that show how risks have been identified and reduced. Process safety disciplines, described in process and industrial safety engineering, emphasize layers of protection and learning from incidents. The weakest points are often organizational: maintenance deferred, warnings normalized, or responsibility divided between parties.
Fault tree, event tree and reliability methods from reliability and resilience engineering quantify how systems fail.
Hazard projections are compared with design assumptions to identify where standards may need revision.
Investigations of failures and near misses identify gaps in standards and practice.
Quantified risk estimates depend on data that is sparse for rare events. Standards cannot anticipate every combination of failures, and compliance with a standard is not the same as resilience.
The current service level is R0: information and enquiries. An enquiry receives a reference and names the next step; applications, payments, compute allocations and registrations open only when their team, terms and review capacity exist.