Capacity planning for peaks
Systems serving whole populations are sized for peak demand, such as benefit surges, with load testing and autoscaling verified.
GCRI · Digital Public Infrastructure
Computing for DPI
High-performance, cloud and edge computing host the public digital infrastructure that whole populations use. In this field the questions are capacity, availability, hosting choices, concentration and the ability to move systems between providers.
01Register
Computing for DPI on the record.
Method recordSTEM method
- MethodHigh-performance, cloud and edge computing
- StewardData and Compute
- Applied inDigital Public Infrastructure
- Data3 inputs
- Checks3 validation steps
- Canonical pageSTEM Commons
02Application
What high-performance, cloud and edge computing does here.
High-performance, cloud and edge computing provide the processing and storage capacity for simulation, analytics and digital services. They are both an enabler of risk analysis and a critical dependency for society. In digital public infrastructure and cyber and digital resilience, computing capacity determines how fast and at what resolution risks can be modelled. Its concentration is itself a systemic dependency for finance, health and government services. The canonical description is on the STEM Commons.
Multi-site and multi-provider hosting
Critical services are designed to run across sites or providers so that one failure does not stop them.
Portability engineering
Systems use open standards and containerisation so that they can be moved between hosting environments when needed.
03Monitor
Compute workload.
The screen a team would use to follow this method: its measures, states and decisions. Names are examples and values are illustrative.
Compute workload
Digital public infrastructure · Computing for DPI · Run R-3135
- Channels reporting92of 100Normal
- Median latency226ms
- Records failing checks0.5per 1,000Watch
- Backlog30min
Gaps on 4 channelsGCRI · Digital Public Infrastructure
Latency, p95
Events
- 06:46WarnChannel C-59 stale
- 07:56InfoSchema v4 accepted
- 08:13ErrorChecksum mismatch, batch quarantined
- 08:43DoneReplay complete
04Data
What the method consumes.
Datasets and records used by high-performance, cloud and edge computing on this platform, with the role each plays and the label its values carry. Sources are listed in the source register.
| Data | Role | Label |
|---|---|---|
| Load test results | Capacity | OBSERVED |
| Hosting inventories | Dependencies | DECLARED |
| Availability monitoring | Performance | OBSERVED |
05Methods and evidence
How Computing for DPI is modelled, measured and tested.
The model, its assumptions, its data and its uncertainty, in the form a scientist or engineer would check. Structures follow published methods. The values drawn are illustrative, not findings.
Datasets and provenance
The data classes behind Computing for DPI and what is recorded about each before it is used.
| Data class | Provenance recorded | Resolution stated | Licence checked |
|---|---|---|---|
| Satellite imagery, optical and radar | sensor, processing level, acquisition date | pixel size and revisit | per scene |
| Reanalysis and climate model output | model, experiment, member, version | grid and time step | per release |
| In-situ sensors and gauges | station, instrument, calibration record | point and sampling rate | per network |
| Population and asset exposure | method, vintage, input sources | cell size and unit | per release |
| Boundaries and reference geography | producer, edition, date | scale | per edition |
- Lineage
- W3C PROV record from source to figure
- Principles
- FAIR: findable, accessible, interoperable, reusable
- Gaps
- shown as missing, never filled silently
FAIR guiding principles · GO FAIR and FORCE11W3C PROV · World Wide Web ConsortiumGuidance on consistent treatment of uncertainties · IPCCCEOS Analysis Ready Data · Committee on Earth Observation Satellites
06Validation
How results are checked.
Systems are tested through benchmarks, load testing and failover exercises. Numerical reproducibility is checked across hardware and software configurations.
| Check | How it is done |
|---|---|
| Failover testing | Failover between sites is tested regularly |
| Peak verification | Capacity is verified against realistic peak scenarios |
| Portability trial | Moving a component to another environment is trialled |
Concentration in few providers or regions creates shared points of failure. Energy, water and supply chain constraints limit capacity growth.
07Process
How the process runs.
Process explorer · Process
Computing for DPI: Build, sign and accept
10 steps·4 stages·2 gates
Process
Computing for DPI: Build, sign and accept
An admitted mission becomes a cycle project; the build is pinned, verified and signed, and the Global Risks Forum (GRF) records acceptance for exercise, not permission to deploy.
01 Request and sources
- 01Admitted mission becomes a cycle projectRecord · Universe to FoundryAn admitted mission becomes a cycle project with a decision case.
- 02Qualify data sources and resourcesStep · the Global Centre for Risk and Innovation (GCRI)GCRI qualifies data sources and resource offers and builds the scenario models. An offer is not an allocation.
02 Build and verify
- 03Source snapshotRecord · NXS-FAC (blueprints, builds and signing)The snapshot pins the commit, dependencies and generator versions.
- 04Build contractRecord · NXS-FAC (blueprints, builds and signing)The build contract declares the artefact kind, environment and reproducibility envelope.
- 05Integrate and buildModel · GCRIGCRI integrates software and data, signs builds, and tests security and interoperability.
- 06Verification suiteGate · NXS-FAC (blueprints, builds and signing)Required and advisory checks stay separate. Reproducibility needs pinned inputs, declared nondeterminism and independent rebuilds.
03 Sign and admit
- 07Sign the exact artefactStep · NXS-FAC (blueprints, builds and signing)NXS-FAC builds, attests and requests a signature via a scoped signer identity. It holds no key material.
- 08Package admissionStep · NXS-NXQ (software, models and capability lifecycle)NXS-NXQ receives the signed package and keeps admission evidence that binds the task, data class, evaluation suite and expiration.
04 Accept
- 09Core Build ReportRecord · GCRIThe Core Build Report is the go or no-go record. Universe assembles the Core and holds the decision for the exercise.
- 10G3 · Build accepted for exerciseGate · The Global Risks ForumGRF records whether the build is accepted for exercise. A signed build or release candidate is not permission to deploy to production.
The programme year · NXS-FAC · UniverseDesigned programme process, not a record of operation. No cycle has run and every programme is at service level R0. A gate is a programme decision, never a public-authority approval, certification or deployment authorisation. The record order follows the Builds and Releases room lists of NXS-FAC.
08Connections
Topics that rely on this method.
09Stewardship
Who maintains the method.
Data and Compute stewards high-performance, cloud and edge computing for the Consortium and reviews how it is applied across platforms.
10Connected
Where this page leads across the Consortium.
11Questions
Questions and answers.
What are the limits of high-performance, cloud and edge computing in this field?
Concentration in few providers or regions creates shared points of failure. Energy, water and supply chain constraints limit capacity growth.
How are results checked?
Systems are tested through benchmarks, load testing and failover exercises. Numerical reproducibility is checked across hardware and software configurations.
Are the values on this page real?
The data names, roles and checks are real descriptions of practice. The canvas shows a design of the method's use, not a run; no result is reported here.
Where else is this method applied?
The canonical method page lists every platform that applies it.
ReportsContribute
Contribute evidence from this page.
Reports is the Consortium's quarterly publication. What you know about this subject can become evidence, a case or a correction in the next edition, credited to you and published under CC BY 4.0 where it is your own work.
GCRIDigital Public InfrastructureStrategic SystemsExponential Technology
- EmailGateway GW-GCRISend it from this pageEvidence, a correction, a case, a method, a review, a translation or profile input. It arrives tagged with this page, so the editor who owns it receives it.
- ZenodoOpen depositDeposit it and submit to the communityPublish your own record on Zenodo with your ORCID iD, then submit it to the Reports community there. Curators review it; the DOI stays yours.
- ReportsGCRISee every way to contributeThe contribution types, how each is reviewed, what credit you receive, the licence and what is never accepted.
Never send personal data, sensitive infrastructure detail or anything you have no right to share. A contribution is reviewed before use; sending it confers no authorship or editorial rights, and sponsorship never buys a finding.
Digital Public Infrastructure
Bring a method, a dataset or a question.
Information and enquiries are open today. 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.
Legal
Legal documents.
Maps, data and figures on this site are shown for context and general information. They are not advice, forecasts or warnings; the limits of the information are set out in the Disclaimers and Data Notices.