G09 · PAGE · nexusGCRI dossier · service level R0
GCRINexus FoundryEstablished
Nexus Foundry · Nexus

Nexus

Nexus is the command home of the Foundry: where an institution sees its portfolio of programmes and projects, their posture and the decisions pending, in one governed place.

Publisher
The Global Centre for Risk and Innovation
Field
Data and compute, Methods and modelling
Canvas · the Nexus cycleDesign, not a record
The Nexus cycle on Nexus FoundryA question from a programme becomes evidence, a governed build, an organized community, a controlled test, a reviewed publication and a decision taken by the competent authority. Design of the cycle, not a record of a run.

Fig.The Nexus cycle, from question to renewal. Design, not a record of a run.

01In brief

The short answer.

Nexus Command Home is the Nexus Foundry system for an executive console for posture, authority and coordinated response across institutional projects. It serves 3 platforms, among them Nexus Agency and Systemic Risk Management, and its stated limit is that it is no substitute for external decision authority. Access is through an authorized project with an accountable owner, data terms and a review plan.

02Geography

Digital demand and connectivity in Japan and Korea.

Urban demand centres and the hubs that anchor digital and data infrastructure, shown for Japan and Korea as an example geography for this subject.

Urban demand centres and the hubs that anchor digital and data infrastructure.Indicator derived from Natural Earth at map scale; a screening view, not an assessment.
GCRI · Nexus Foundry · fieldDESIGN FIGURE
04The problem it addresses

Portfolios that span sectors lose sight of their own dependencies.

A ministry or programme office running water, energy and health projects at once needs to see which projects share data, assets or staff, and which decisions are blocked on others. Without a portfolio view, the systemic risk inside the portfolio itself goes unmanaged.

  • Portfolio posture: what is planned, active, paused or closed, with evidence.
  • Dependencies between projects and the systems they draw on.
  • Decisions pending, with the authority that holds each.
05Reference practice

The standards a design like this is read against.

ReferenceRelevance
ISO 21500 seriesProject, programme and portfolio management
ISO 31000Integrating risk into governance and decision-making
06Neighbouring systems

What it exchanges with the other systems.

  • Draws scenario results from DSS and situational views from NorthStar.
  • Records commitments and handoffs through Rails.
07Access

Authorized projects only.

Access requires an authorized project with an accountable owner, data terms and a review plan. Enquiries go to contact@therisk.global.

08Key terms

Terms used on this page.

Each term as this page uses it. Where a standard-setting body defines the term, the wording follows that body.

TermDefinition
Decision rights matrixA table showing which body proposes, approves, executes and oversees each decision.
Delegation chainThe sequence of agents, from board to consultant to manager, through which investment decisions pass.
Audit trailA record of who accessed or changed data, when and why.
09Sources

Where this page's references lead.

The bodies and documents this page is read against. Status and editions change; each link goes to the issuing body.

10Questions

Questions and answers.

Is the system available now?
Allocations open when their terms and review capacity exist; the current service level is R0, information and enquiries.
Nexus Foundry

Bring your expertise to this field.

The current service level is R0: information and enquiries. 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.

Have questions?