Skip to content

GCRI · Foundry

کۆمپیوتەر و لێوار

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.

02پرسیارەکە

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.

03ڕێگا و بەڵگە

How compute and edge is modelled, measured and tested.

مۆدێلەکە، گریمانەکانی، داتاکانی و نادڵنیاییەکەی، بەو شێوەیەی زانا یان ئەندازیارێک دەیپشکنێت. پێکهاتەکان ڕێگا بڵاوکراوەکان دەگرنەبەر. بەهاکانی کێشراو نموونەییە، نەک دۆزینەوە.

مۆدێل، هاوکێشەکان و گریمانەکان

The model structure used for compute and edge, the assumptions it makes and how each is tested.

مەترسیی توخمی iRi = f(Hi, Ei, Vi, Ci)مەترسیدەر، ڕووبەڕووبوون، لاوازی و توانای مامەڵەکردن
زیانی ساڵانەی چاوەڕوانکراوEAL = ∑k pk · Lkover events k with annual probability pk
سیستەمە هاوبەستەکانxt+1 = A xt + B ut + εtA carries the couplings, u the shock, ε the error
گریمانەبۆچی دروست دەکرێتچۆن تاقی دەکرێتەوە
مەترسیدەر و ڕووبەڕووبوون لە ناو پێشهاتێکدا سەربەخۆنئینتێگراڵی زیان بە ئاسانی دەهێڵێتەوەبەراورد بکە لەگەڵ گونجاندنی کۆپیولا لەسەر تۆمارە هاوبەشەکان
هاوبەستییەکان لە نزیک خاڵی کارکردن هێڵینڕێگە دەدات شۆکەکان بڵاو ببنەوە لە Aلە دەرەوەی مەودای هێڵیی شڵەژێنە و بەراورد بکە
چەمکەکانی لاوازی لە شوێنێکەوە بۆ شوێنێکی تر دەگوازرێنەوەچەمکی ناوخۆیی بە دەگمەن بەردەستەلەگەڵ زیانە چاودێریکراوەکان پشتڕاستی بکەرەوە کە هەن
تێکردنەکان
کۆمەڵە داتای وەشانکراو لەگەڵ ڕەسەنایەتی
دەرچووەکان
دابەشبوون، نەک یەک ژمارە
کۆد
بڵاوکراوەتەوە لەگەڵ کارتی مۆدێل و تاقیکردنەوەکان
بەرهەمهێنانەوە
هەمان داتا، کۆد، ژینگە و تۆو
فۆرمۆلەکردنی مەترسی و دۆخ-بۆشایی ستاندارد؛ ئەو گریمانانەی لیست کراون ئاسایین بۆ ڕێگاکە، بۆ پێداچوونەوە ڕاگەیەندراون، نەک ئەنجام.
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
04In the five domains

Compute is designed to serve each domain’s heaviest models.

05نیشاندەرەکان

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.

نیشاندەریەکەڕیتمSource typeناونیشان
Queue wait timeminutes, median and taildailyScheduler accountingچاودێریکراو
Service availabilityproportion of scheduled timeمانگانەAvailability monitoringچاودێریکراو
Workloads placed outside permitted jurisdictioncountper placementPlacement policy logsچاودێریکراو
Edge reconciliation conflictscount per resynchronisationper eventSynchronisation logsچاودێریکراو
Energy use per workloadkilowatt-hoursper runPower telemetry or provider estimatesمەزەندەکراو
Carbon intensity of electricity usedgrams CO2 equivalent per kilowatt-hourhourlyGrid operator and provider dataمەزەندەکراو
Capacity offered against capacity allocatedcore-hours or GPU-hoursمانگانەOffer and allocation registerDECLARED
Recovery time in failover exercisesminutesper exerciseExercise recordsچاودێریکراو
06سەرچاوەکان

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.

سەرچاوەWhat it givesLicence class
TOP500 and Green500 listsPublished performance and energy efficiency of large systemsFree, terms of the project
Ember electricity dataGeneration mix and carbon intensity of electricity by countryCC BY 4.0
Copernicus Data Space EcosystemEarth observation archives with processing next to the dataFree and open, attribution
NASA Earthdata CloudEarth science archives in cloud object storage for in-region analysisFree and open, NASA data policy
Public cloud region and status recordsRegion locations, availability history and incident reportsProvider terms
Kubernetes release and deprecation recordsVersion support windows and API removals that affect workload portabilityCC BY 4.0
07بڕیارەکان

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.

کێ بڕیار دەداتپرسیارەکەEvidence this page serves
Data owners and data protection authoritiesWhere data may be processed, and whether results may leavePlacement logs, the jurisdiction of each tier, federated execution records
Project ownersHow to prioritise workloads within an allocation during an eventQueue state, allocation remaining, deadlines
Infrastructure contributors and operatorsWhat capacity to offer and on what termsOffer register, utilisation, energy and support load
Ministries responsible for digital infrastructureHow far national risk analysis depends on foreign or concentrated providersProvider 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
08Core questions

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?
09Mechanisms

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.

10Methods and limits

What is engineered, and what remains hard.

Federation

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.

Accounting

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.

11میتۆدەکان

How it is studied, and what the methods cannot say.

12Where this page’s references

Where this page’s references lead.

ئەو لەش و بەڵگەنامانەی ئەم لاپەڕەیەیان لەگەڵ دەخوێنرێتەوە. دۆخ و وەشانەکان دەگۆڕێن؛ هەر بەستەرێک دەچێتە لای لەشی دەرکەر.

13پرسیارەکان

پرسیار و وەڵام.

Why move analysis to the data instead of the reverse?
Because some data may not legally or contractually leave its location, and some is too large to move. The code goes to the data, runs under the owner’s policy, and only permitted results come back.
What happens to edge work during an outage?
The node continues locally with the model and data it holds. When connectivity returns it synchronises and flags conflicts for a person to resolve rather than overwriting either side.
Can my institution contribute servers?
Offers can be described to the Consortium Secretariat. An offer is recorded as an offer, not as allocated or used capacity, until a separate allocation is agreed.
Is energy use reported?
The design records energy and carbon per workload where telemetry or provider estimates exist, with a label stating which. Estimates are never presented as measurements.
Does membership include compute?
No. Neither membership nor sponsorship secures a compute allocation.
Is any compute allocation open?
Not yet. Allocations open when their terms and review capacity exist.
ڕاپۆرتەکانبەشداربە

لەم لاپەڕەیەوە بەڵگە پێشکەش بکە.

Reports بڵاوکراوەی وەرزیی کۆنسۆرتیۆم ـە. ئەوەی تۆ لەسەر ئەم بابەتە دەیزانیت دەتوانێت لە وەشانی داهاتوودا ببێتە بەڵگە، کەیس یان ڕاستکردنەوە، بە ناوی خۆتەوە و لەژێر CC BY 4.0 بڵاو دەکرێتەوە کاتێک کاری خۆتە.

GCRIFoundryFoundry Build and Readiness
Foundry

ڕێگایەک، کۆمەڵە داتایەک یان پرسیارێک بهێنە.

زانیاری و پرسیار ئەمڕۆ کراوەن. پرسیارێک ژمارەی ئاماژەی پێدەدرێت و هەنگاوی دواتر دیاری دەکات؛ داواکاری، پارەدان، تەرخانکردنی کۆمپیوتەر و تۆمارکردن تەنیا کاتێک دەکرێنەوە کە تیم، مەرج و توانای پێداچوونەوەیان هەبێت.

The Global Centre for Risk and Innovation (GCRI Canada) is a Canadian not-for-profit organisation, not a registered charity, with its registered office in Ontario.