G09 · PAGE · northstarGCRI dossier · service level R0
GCRINexus FoundryEstablished
Nexus Foundry · NorthStar

NorthStar

NorthStar is the civilian common operating picture: one shared view of an unfolding situation, its resources and its tasks, for the agencies coordinating a response.

Publisher
The Global Centre for Risk and Innovation
Field
Data and compute, Methods and modelling
Status
Established
Service level
R0: information and enquiries

Pipeline

NorthStar · Workspace WS-70

One stage waitingGCRI · Nexus Foundry

Stages

  1. Ingest3 sources
  2. Validateschema · licence
  3. Transformversioned
  4. ModelHigh-performance,…
  5. Testheld-out
  6. Releasewith limits

Artefacts

Job scheduler logv3.7OpenOBSERVED
Model registryv2.3To checkOFFICIAL
Tile cache manifestv3.2OpenVERSIONED
Usage meterv2.4OpenOBSERVED

Compute quota

share used vs alert level

CPU hours88 used · limit 80Storage60 used · limit 90GPU hours50 used · limit 70

Nexus Foundry · PipelinePipeline, in outline: domain structure with placeholder names and illustrative values, not a record.

01In brief

The short answer.

NorthStar Common Operating Picture is the Nexus Foundry system for situational awareness: a shared map and timeline for civilian operations and field coordination. It serves 8 platforms, among them Energy Nexus as well as Disaster Resilience and Recovery, and its stated limit is that its scope is civilian only, and no map in it is an official warning. Access is through an authorized project with an accountable owner, data terms and a review plan.

02Geography

Infrastructure networks in Ukraine.

Major roads, railways, ports and airports, and the density of the transport network, shown for Ukraine as an example geography for this subject.

Major roads, railways, ports and airports, and the density of the transport network.Indicator derived from Natural Earth at map scale; a screening view, not an assessment.
GCRI · Nexus Foundry · fieldDESIGN FIGURE
04The problem it addresses

Agencies responding together each see a different picture.

In a multi-agency incident, the fire service, utilities, health authorities and local government hold separate maps and logs. Incident management practice calls for a common operating picture so that decisions rest on the same facts, with clear ownership of each layer.

  • Shared situational layers with source and time.
  • Task and resource tracking across agencies.
  • A record that supports after-action review.
05Reference practice

The standards a design like this is read against.

ReferenceRelevance
ISO 22320Incident management, including command and coordination
ISO 22301Business continuity management
OGC standardsInteroperable map layers across agencies
06Neighbouring systems

What it exchanges with the other systems.

  • Takes observation layers from EOP and warnings support from EWS.
  • Hands decision questions to DSS.
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
Common operating pictureA shared, regularly updated view of the situation, resources and actions that coordinating agencies all use.
Incident command systemA standard organisational structure for response with defined roles for command, operations, planning, logistics and finance.
GeolocationRecording the geographic coordinates of an asset or collateral so it can be linked to hazards.
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?