NXS-NST
NXS-NST, the civilian common operating picture, incidents and coordination system of the Nexus ecosystem: purpose, rooms, inputs and outputs, areas, standards and boundaries.
NXS-NST is one of the twenty systems of the Nexus ecosystem: the civilian common operating picture, incidents and coordination system. It is described here as a system of the ecosystem, with its purpose, its rooms, what it receives and provides, the areas it serves, the standards that apply and its boundaries.
Earlier pages may use the retired name NorthStar.
Purpose and context
Civilian operating-picture records and coordination views. Its domain is civilian common operating picture and field coordination. A typical setting is a flood-affected port incident spanning facilities, access routes and response resources.
What it is the authority for
operational period
Validate start/end and preserve the observation chronology across operational periods.
incident
Resolve one incident and its relation to the project; merging needs an audit trail.
resource refs
Availability, reservation, assignment and acknowledged deployment are different states.
coordination zone
Record CRS, boundary version and handling restrictions for precise locations.
observation confidence
Keep reporter identity, source independence and corroboration separate from a confidence score.
Rooms and areas of work
Every system has ten rooms: eight shared rooms, which work the same way across systems with this system's domain, and two specialist rooms.
Station
Shared
The system's home: posture of the system's own records, freshness, refusals and next actions; never a summary of another system's truth
Mission
Shared
Mission and task work for the system's domain, linked to Universe missions and Project OS plans
Builder
Shared
Composition of the system's artifacts and configurations from admitted packages (NXS-STU, NXS-FAC and NXS-NXQ boundaries apply)
Maps
Shared
Spatial views of the system's records and NXS-GRX products, under the boundary licence gate
Data
Shared
The system's datasets, sources and lineage as NXS-GRX products or system-owned records
Commons
Shared
Shared methods, standards, templates and reusable artifacts, including Nexus Standards (NXS, a programme of the Nexus Consortium) participation
Reports
Shared
Reports and editions built from the system's evidence, with cutoffs and correction history
Knowledge
Shared
Institutional knowledge, records, runbooks and learning linked to NXS-HUB
Incidents
Specialist
Records: incident, incident observation binding, impact assessment, situation snapshot
FieldOps
Specialist
Records: field resource, field assignment, resource reservation, field receipt
Kinds of work it carries: Incident operations; Field coordination plans; Common Operating Picture; Case Product; Resource Availability; Route Assessment; Field Observation; Situation Report; Search & rescue operations; Mass-gathering events; Utilities restoration operations; Outbreak responses; Industrial / hazmat incidents; Field team deployments; Assistance & case desks; Damage assessment campaigns; Community responder networks; Hospital & health-facility networks; Shelter networks; Port & terminal operations; Airports & transport hubs; Response fleets; Logistics corridors; Evacuation route networks; Relief supply pipelines; Regional operating pictures; Situation reporting cells.
This system in the Nexus model. Generated from the Nexus Standards index and the programme spine; statuses are registry statuses, never adoption or certification.
Descriptor
Civilian common operating picture, incidents and coordination
In the programme
Built, simulated and prepared in the Foundry pillar; its records serve the other pillars through the handoffs of the programme year, and the competent authority decides outside the programme.
System profile
NRS-S2: NXS-NST (Civilian common operating picture) (status OPEN)
Nexus Risk Standards that apply
Nexus Reports technology streams
None
Inputs
What it receives, and from whom. Each interface carries its context (estate, tenant, workspace, purpose, jurisdiction, time and place) and is checked under the policy authority.
Outputs
What it provides, and to whom. Consumers read projections; the system stays the authority for its own records and their corrections.
Areas it serves
Standards that apply
Every record of the system is identified through the UNI identifier fabric of Nexus Standards (NS-1), and its public name follows the Nexus Standards naming rules. The areas it serves reference these external standards; naming a standard records where it is referenced and is not a claim of certification, accreditation, conformance or endorsement.
ISO 22361 Security and resilience, Crisis management, Guidelines
ISO
2022
Crisis capability and decision-making
ISO 22320 Emergency management, Guidelines for incident management
ISO
2018
Incident command and coordination
National Incident Management System, third edition
United States Federal Emergency Management Agency (FEMA)
2017
Comparator for scalable incident structures
Sendai Framework 2015-2030, Global Target G
UNDRR
2015
Availability of and access to early warning
Early Warnings for All initiative
United Nations Secretary-General with WMO, UNDRR, ITU and IFRC
2022
Four pillars of people-centred early warning, to 2027
Common Alerting Protocol (CAP) 1.2
OASIS, adopted as ITU-T X.1303
2010
Interoperable alert message format
Multi-Hazard Early Warning Systems: A Checklist
World Meteorological Organization (WMO)
2018
Structured readiness review
Homeland Security Exercise and Evaluation Program (HSEEP)
FEMA
2020
Design, conduct, evaluation and improvement
WHO Simulation Exercise Manual
World Health Organization (WHO)
2017
Health-emergency exercise types
ISO 22301, clause 8.5 (exercising and testing)
ISO
2019
Exercising continuity arrangements
IEC 31010 Risk management, Risk assessment techniques
International Electrotechnical Commission and ISO (IEC/ISO)
2019
Choosing assessment techniques
IPCC Sixth Assessment Report, Working Group II
Intergovernmental Panel on Climate Change (IPCC)
2022
Risk as hazard, exposure, vulnerability and response
Words into Action: National Disaster Risk Assessment
UNDRR
2017
National assessment process
Principles for Resilient Infrastructure
UNDRR
2022
Six principles for resilient systems
ISO 37123 Indicators for resilient cities
ISO
2019
Measuring urban resilience
IEC 62443 Industrial communication networks, security
IEC
2018
Security of control systems
SpatioTemporal Asset Catalog (STAC) 1.0
STAC community, an Open Geospatial Consortium community standard
2021
Searchable geospatial catalogues
OGC API, Features, Part 1: Core
Open Geospatial Consortium (OGC)
2019
Web access to geospatial features
CEOS Analysis Ready Data (CEOS-ARD)
Committee on Earth Observation Satellites (CEOS)
2017
Analysis-ready product specifications
International Health Regulations (2005), amendments adopted 2024
World Health Organization (WHO)
2024
International health law framework
WHO Pandemic Agreement
World Health Assembly
2025
Pandemic prevention, preparedness and response
Joint External Evaluation tool, third edition
WHO
2022
Assessing core health-security capacities
One Health Joint Plan of Action
FAO, UNEP, WHO and WOAH (Quadripartite)
2022
Human, animal and environmental health
Post-Disaster Needs Assessment guidelines
European Union, United Nations and World Bank
2013
Joint assessment methodology
Fund for responding to Loss and Damage, operationalised
UNFCCC, COP28
2023
Loss and damage finance architecture
Santiago network for averting, minimizing and addressing loss and damage
UNFCCC
2019
Technical assistance for loss and damage
Sendai Framework 2015-2030, Priority 4 (Build Back Better)
UNDRR
2015
Safer recovery and reconstruction
In the programme
Governance boundaries
Policy authority for the system sits with NXS-NSF; identifiers come from the UNI identifier fabric. The system exports read projections and commands through typed contracts, and no other system writes its records.
It does not own, and never stands in for:
compute lifecycle (NXS-NXS-COR)
edge-node lifecycle (NXS-NXS-COR/NXS-OPS)
cluster replication (NXS-NXS-COR)
hardware management (NXS-NXS-COR/NXS-OPS)
decision analysis (NXS-DSS)
warnings (NXS-EWS)
risk indexes (NXS-NXS-GRX)
Method boundary. Reconcile reports by source lineage and event time. Repeated forwarding of one report is not independent corroboration; route feasibility must use contemporaneous restrictions and resource constraints. Do not turn reported field status into an observed dispatch, or assume repeated reports are independent.
Generated page. It records names, roles and design for reading, not readiness: release is on hold, and nothing here is presented as ready, certified or official.
Last updated
Was this helpful?