GCRI · Foundry
Hesabkirin û qiraxê
Risk analysis needs compute in very different places: a large cloud allocation for a national ensemble, a ministry’s own servers for records that may not leave, a field laptop that keeps a model running when the network fails. This page sets out how compute risk develops, from capacity shortfall and concentration in a few providers to jurisdiction, energy and degraded connectivity, and how cloud, local nodes and edge devices are designed to be scheduled as one capacity.
Compute and edge on the record.
Compute and edge: how the risk develops.
Cloud, local nodes and edge technical capacity. The dossier below sets out how the risk develops, what is measured, where the data come from, how it is modelled and who decides.
Capacity fails when needed
Demand for compute peaks during events, exactly when shared capacity is contested, networks are degraded and power is unstable. Queues lengthen, ensembles shrink and forecasts arrive after the decision window has closed.
Concentration
Many institutions rely on a few cloud providers, regions and chip suppliers. An outage, sanction, price change or supply shortage reaches all of them at once, which makes compute concentration a systemic dependency in its own right.
Jurisdiction and data location
Where data may be processed is set by law and contract. Moving analysis to the data keeps records in place, but constrains which methods can run and can still leave results open to inference about the inputs.
Disconnection and reconciliation
Edge nodes keep working offline and reconcile later. Conflicting edits, clock skew and stale models accumulate during an outage, and reconciliation after a long disconnection may need human judgement rather than an automatic merge.
How compute and edge is modelled, measured and tested.
Model, texmînên wî, daneyên wî û nediyariya wî, bi şeweyê ku zanyar an endezyar kontrol bike. Avahî rêbazên weşandî dişopînin. Nirxên hatine xêzkirin nimûneyî ne, ne encam in.
Model, hevkêşe û texmîn
The model structure used for compute and edge, the assumptions it makes and how each is tested.
Ri = f(Hi, Ei, Vi, Ci)metirsî, rûbirûbûn, lawazî û kapasîteya serederiyêEAL = ∑k pk · Lkover events k with annual probability pkxt+1 = A xt + B ut + εtA carries the couplings, u the shock, ε the error| Texmîn | Çima tê çêkirin | Çawa tê ceribandin |
|---|---|---|
| Metirsî û rûbirûbûn di nav bûyerekê de serbixwe ne | Entegrala windahiyê ji hesabkirinê re maqûl dihêle | Bi lihevhatineke copula li ser tomarên hevbeş re bidin ber hev |
| Girêdan li nêzî xala xebatê xêzik in | Dihêle şok di A de belav bibin | Ji derveyî rêza xêzik tevlihev bike û bide ber hev |
| Xêzên lawaziyê di navbera cihan de têne veguhastin | Xêzikên herêmî kêm tên dîtin | Li hember windahiyên çavdêrîkirî erê bike li cihê ku hene |
- Têketin
- danehevên bi guhertoyan û çavkaniyê
- Derketin
- belavkirin, tu carî jimarên tenê
- Kod
- bi qerta modelê û ceribandinan re hat weşandin
- Zêdebûn
- heman dane, kod, jîngeh û tov
Compute is designed to serve each domain’s heaviest models.
Compute readiness is designed for the Foundry Build and Readiness series. Energy efficiency is reported with ISO/IEC 30134 indicators; no hardware specifications are summed into performance claims.
- Workload profiles.
- Efficiency measurements.
What is measured, and how well.
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.
| Nîşane | Yekîne | Rîtm | Source type | Nîşan |
|---|---|---|---|---|
| Queue wait time | minutes, median and tail | daily | Scheduler accounting | ÇAVDÊRÎKIRÎ |
| Service availability | proportion of scheduled time | mehane | Availability monitoring | ÇAVDÊRÎKIRÎ |
| Workloads placed outside permitted jurisdiction | count | per placement | Placement policy logs | ÇAVDÊRÎKIRÎ |
| Edge reconciliation conflicts | count per resynchronisation | per event | Synchronisation logs | ÇAVDÊRÎKIRÎ |
| Energy use per workload | kilowatt-hours | per run | Power telemetry or provider estimates | TEXMÎNKIRÎ |
| Carbon intensity of electricity used | grams CO2 equivalent per kilowatt-hour | hourly | Grid operator and provider data | TEXMÎNKIRÎ |
| Capacity offered against capacity allocated | core-hours or GPU-hours | mehane | Offer and allocation register | DECLARED |
| Recovery time in failover exercises | minutes | per exercise | Exercise records | ÇAVDÊRÎKIRÎ |
Where the evidence comes from.
Named public datasets and institutional records, each with its licence class. Sources by agreement are used only under their terms and never republished.
| Çavkanî | What it gives | Licence class |
|---|---|---|
| TOP500 and Green500 lists | Published performance and energy efficiency of large systems | Free, terms of the project |
| Ember electricity data | Generation mix and carbon intensity of electricity by country | CC BY 4.0 |
| Copernicus Data Space Ecosystem | Earth observation archives with processing next to the data | Free and open, attribution |
| NASA Earthdata Cloud | Earth science archives in cloud object storage for in-region analysis | Free and open, NASA data policy |
| Public cloud region and status records | Region locations, availability history and incident reports | Provider terms |
| Kubernetes release and deprecation records | Version support windows and API removals that affect workload portability | CC BY 4.0 |
Who decides, and what the evidence serves.
Foundry prepares evidence. The decisions below are taken by the authorities named, under their own rules, and never by the platform.
| Kî biryarê dide | Pirs | Evidence this page serves |
|---|---|---|
| Data owners and data protection authorities | Where data may be processed, and whether results may leave | Placement logs, the jurisdiction of each tier, federated execution records |
| Project owners | How to prioritise workloads within an allocation during an event | Queue state, allocation remaining, deadlines |
| Infrastructure contributors and operators | What capacity to offer and on what terms | Offer register, utilisation, energy and support load |
| Ministries responsible for digital infrastructure | How far national risk analysis depends on foreign or concentrated providers | Provider and region dependency map; exit and failover plans |
Outputs this topic produces
- Placement policies by data class, jurisdiction, urgency and cost
- Workload packages portable across cloud, private and edge tiers
- Failover and degraded-operation runbooks with exercise records
- Register of capacity offered, allocated and used, kept apart
What computing engineers and data owners ask.
- Where is the data legally and contractually allowed to be processed?
- Which workloads need burst capacity, and which need steady, local availability?
- How does work continue when connectivity is degraded or lost?
- How is offered capacity distinguished from capacity actually allocated and used?
One control plane across three tiers.
NXS-COR (compute, nodes and runtimes) is designed as the compute control plane across cloud, private infrastructure and edge. Workloads are packaged with their dependencies so they can run on any tier that the project’s policy allows, and the scheduler places them according to data location, sensitivity, cost and urgency. Where data cannot move, the analysis is designed to run where the data is held and only permitted results leave.
Edge capacity matters most when it is hardest to provide: during the events risk work is about. Field kits, observatory nodes managed through NXS-OPS (instruments, sensors and calibration) and offline operation of NXS-NST (civilian common operating picture) are designed so that coordination continues through outages, synchronising when connectivity returns. Energy use, cooling and hardware supply are part of the engineering, and the platform’s computing questions connect to the energy and data-centre analysis at Data and Compute.
What is engineered, and what remains hard.
Compute to data
Federated execution keeps sensitive data in place and moves code and permitted results.
Degraded operation
Edge nodes continue locally and reconcile later, with conflicts flagged rather than silently overwritten.
Offer is not allocation
Contributed infrastructure is recorded as an offer until it is separately allocated.
Limits: federated analysis constrains which methods can run, edge devices have little capacity, and reconciliation after long disconnection can need human judgement. No hardware specifications are summed into performance claims.
How it is studied, and what the methods cannot say.
- 01High-performance, cloud and edge computingEnsemble scheduling across tiers · Federated execution next to the dataApplied here
- 02Systems engineeringCanonical system inventory · Contract-first interfaces · Requirements traced to evidenceApplied here
- 03Software and safety-critical systems engineeringFail-closed policy gates · Build provenance and bills of materials · Assurance casesApplied here
- 04Data engineering, interoperability and stewardshipValidation at the ingest boundary · Frozen data cuts for reproducible productsApplied here
- 05Geospatial information systemsImagery catalogues through STAC · Exposure overlays with stated aggregationApplied here
Where this page’s references lead.
Sazî û belgeyên ku ev rûpel li hember wan tê xwendin. Rewş û çap diguherin; her girêdan diçe ba saziya derxistinê.
Pirs û bersiv.
Why move analysis to the data instead of the reverse?
What happens to edge work during an outage?
Can my institution contribute servers?
Is energy use reported?
Does membership include compute?
Is any compute allocation open?
Ji vê rûpelê delîl bidin.
Reports weşana sê mehane ya Konsorsiyûmê ye. Tiştê ku tu li ser vê mijarê dizanî dikare di çapa pêş de bibe delîl, dosya an rastkirin, bi navê te û di bin CC BY 4.0 de weşandî li cihê ku karê te bi xwe be.
- E-nameDergeh GW-GCRIJi vê rûpelê bişîninDelîl, rastkirin, doz, rêbaz, nirxandin, wergerandin an têketina profîlê. Bi nîşana vê rûpelê digihîje, ji ber vê yekê edîtorê xwediyê wê wê bistîne.
- 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.
- rêzeya Pergalên StratejîkGCRIHemû rêyên beşdariyê bibîneCureyên beşdariyê, her yek çawa tê nirxandin, tu çi navlêkirinê distînî, lîsans û tiştê ku qet nayê qebûlkirin.
Tu carî daneyên şexsî, hûrgiliyên binesaza hesas an tiştekî ku mafê we yê parvekirinê tune ne neşînin. Beşdarî berî bikaranînê tê nirxandin; şandina wê nivîskarî an mafên edîtorî nade û sponsorî tu carî encamekê nakire.
Rêbazek, danehevek an pirsek bîne.
Agahî û pirs îro vekirî ne. Pirsek referansekê distîne û gava piştî wê dide nasîn; serlêdan, drav, veqetandina hesabkirinê û tomarkirin tenê dema ku tîm, mercên wê û kapasîteya vekolînê hebin vedibin.
Belgeyên hiqûqî.
Nexşe, dane û jimarên vê malperê ji bo çarçoveyê û agahiyên giştî têne nîşandan. Ew ne şîret, ne pêşbînî û ne hişyarî ne; sînorên agahiyê di Daxuyaniyên Berpirsiyariyê û Daxuyaniyên Daneyê de hatine diyarkirin.