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.

01تۆمارکردن

Systems engineering at Foundry on the record.

Method recordSTEM method
  1. MethodSystems engineering
  2. Applied inFoundry
  3. Canonical pageSTEM Commons
02بەکارهێنان

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چاودێری

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

هێڵکاری پشتبەستن

nodes: assets · edges: dependencies

Most central nodes

N30.228Critical
N40.114ئاسایی
N50.4010ئاسایی
N60.355ئاسایی

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.
04داتا

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.

داتاڕۆڵناونیشان
System registryOwnership and boundariesDECLARED
Interface contractsCompatibility analysisDECLARED
Test and verification recordsRequirement evidenceچاودێریکراو
Configuration management recordsChange and baseline controlچاودێریکراو
05ڕێگا و بەڵگە

How Systems engineering at Foundry is modelled, measured and tested.

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

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

The model structure used for Systems engineering at Foundry, 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
06پشتڕاستکردنەوە

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.

بپشکنەHow 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.

07پرۆسە

چۆن پرۆسەکە کار دەکات.

Process explorer · Process

Systems engineering at Foundry: Cascade across systems

8 هەنگاو4 قۆناغ

پرۆسە

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.

09پارێزەرایەتی

Who maintains the method.

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

10پەیوەست

ئەو شوێنانەی ئەم لاپەڕەیە لە ناو کۆنسۆرتیۆم بۆیان دەبات.

11پرسیارەکان

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

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.
ڕاپۆرتەکانبەشداربە

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

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.