Skip to content

GCRI · Foundry

Systems engineering at Foundry

Systems engineering keeps a many-system environment coherent: one owner per record type, explicit interfaces, requirements traced to evidence, and boundaries that say what each system must never do. In this field it is how a change in one system is kept from reaching another unannounced.

01Qeyd

Systems engineering at Foundry on the record.

Method recordSTEM method
  1. MethodSystems engineering
  2. Applied inFoundry
  3. Canonical pageSTEM Commons
02Serlêdan

What systems engineering does here.

Systems engineering is an interdisciplinary approach to designing and managing complex systems over their life cycle. It focuses on requirements, interfaces and interactions so that the whole performs as intended. In data and compute and methods and modelling, systems engineering exposes interfaces where failures propagate between components and organisations. It supports designing interconnected infrastructure with explicit dependency management. The canonical description is on the STEM Commons.

Canonical system inventory

Each system is defined by one contribution, one boundary, the record types it owns and those it only reads, so duplicate ownership is caught in review rather than in production.

Contract-first interfaces

Service contracts are written in Protobuf and OpenAPI before implementation, versioned, and checked for breaking change on every build against the consumers that depend on them.

Requirements traced to evidence

Each requirement links to the test, analysis, inspection or demonstration that verifies it, and the evidence record is kept separate from the claim that the requirement is met.

03Çavdêrî bike

Network analysis.

The screen a team would use to follow this method: its measures, states and decisions. Names are examples and values are illustrative.

Network analysis

Foundry · Systems engineering at Foundry · Run R-3266

Single point of failureGCRI · Foundry

Grafika girêdayîbûnê

nodes: assets · edges: dependencies

Most central nodes

N30.228Critical
N40.114Normal
N50.4010Normal
N60.355Normal

Cascade size under removal

Network analysis: the screen’s structure, terms and states for Foundry.Example names and illustrative values; a design, not a record or a live system.
04Dane

What the method consumes.

Datasets and records used by systems engineering on this platform, with the role each plays and the label its values carry. Sources are listed in the source register.

DaneRolNîşan
System registryOwnership and boundariesDECLARED
Interface contractsCompatibility analysisDECLARED
Test and verification recordsRequirement evidenceÇAVDÊRÎKIRÎ
Configuration management recordsChange and baseline controlÇAVDÊRÎKIRÎ
05Rêbaz û delîl

How Systems engineering at Foundry 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 Systems engineering at Foundry, the assumptions it makes and how each is tested.

Xetera hêmana iRi = f(Hi, Ei, Vi, Ci)metirsî, rûbirûbûn, lawazî û kapasîteya serederiyê
Windahiya salane ya hêvîkirîEAL = ∑k pk · Lkover events k with annual probability pk
Pergalên girêdayîxt+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 neEntegrala windahiyê ji hesabkirinê re maqûl dihêleBi lihevhatineke copula li ser tomarên hevbeş re bidin ber hev
Girêdan li nêzî xala xebatê xêzik inDihêle şok di A de belav bibinJi derveyî rêza xêzik tevlihev bike û bide ber hev
Xêzên lawaziyê di navbera cihan de têne veguhastinXêzikên herêmî kêm tên dîtinLi 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
Formulasyonên standard ên xetereyê û qada rewşê; texmînên navborî ji bo rêbazê tîpîk in, ji bo nirxandinê hatine diyarkirin, ne encam in.
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
06Erêkirin

How results are checked.

Each requirement is traced to verification evidence from analysis, inspection, demonstration or test. Independent reviews check completeness at life cycle gates.

Kontrol bikinHow it is done
Single ownership reviewEach record type is checked for exactly one declared owning system
Compatibility gateBreaking interface changes fail the build unless a versioned migration is declared
Traceability auditA sample of requirements is followed to current verification evidence
Independent gate reviewLife-cycle gates are reviewed by people outside the delivering team

Emergent behaviour in open or socio-technical systems may not be captured by requirements. Rigid processes can slow adaptation to change.

07Pêvajo

Pêvajo çawa dimeşe.

Process explorer · Process

Systems engineering at Foundry: Cascade across systems

8 gav4 qonax

Pêvajo

Systems engineering at Foundry: Cascade across systems

An initial hazard can trigger later risks and events; this illustration draws one cascade across systems such as energy, water, ICT, health and transport.

  1. 01 Hazard

    1. 01Initiating hazardDataset · Security officerCascading risk is the risk that hazard events trigger later risks and events, through chains of interrelated hazards or impacts.
  2. 02 First-order systems

    1. 02Example system: energyModel · System operatorAn example of a system a hazard can hit first. What depends on it is set by a dependency survey.
    2. 03Example system: waterModel · System operatorA second example of a system a hazard can hit first. Its links to other systems are shown as examples only.
  3. 03 Second-order systems

    1. 04Example system: ICTModel · System operatorAn example of a system that may depend on others, for example on backup power. Survey data set the real dependencies.
    2. 05Example system: health servicesModel · System operatorAn example of a system that may depend on water, power and data. Survey data set the real dependencies.
    3. 06Example system: transportModel · System operatorAn example of a system that may depend on ICT, fuel and logistics. Survey data set the real dependencies.
  4. 04 Limiting the cascade

    1. 07Buffers and redundancyStep · Security officerBuffers, redundancy and restoration can limit how far an impact spreads. The OECD report moves from single assets to system resilience.
    2. 08Restoration prioritiesDecision · Security officerThe responsible party sets which services are restored first, under its own rules.

Outline of an external standard or method, from its public sources. It describes what the framework says, not a record of any run. It does not show that Nexus or any partner performs, certifies or approves a step. A gate is a step of the method, never a Nexus approval. The dependencies are examples. A dependency survey for the place sets them.

09Parastin û serperiştî

Who maintains the method.

Systems Science and Modelling stewards systems engineering for the Consortium and reviews how it is applied across platforms.

11Pirs

Pirs û bersiv.

What are the limits of systems engineering in this field?
Emergent behaviour in open or socio-technical systems may not be captured by requirements. Rigid processes can slow adaptation to change.
How are results checked?
Each requirement is traced to verification evidence from analysis, inspection, demonstration or test. Independent reviews check completeness at life cycle gates.
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.
rêzeya Pergalên StratejîkTevkarî bike

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.

GCRIFoundryFoundry Build and Readiness
Foundry

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.

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.