> For the complete documentation index, see [llms.txt](https://docs.therisk.global/organization/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.therisk.global/organization/systems/nxs-ops.md). # NXS-OPS NXS-OPS, the physical instruments, sensors, calibration and primary observation evidence system of the Nexus ecosystem: purpose, rooms, inputs and outputs, areas, standards and boundaries. {% hint style="info" %} This page is generated from the twenty-system charters, the system profiles, the interface and authority registers, the room register, the areas of work, the systems article of the constitution set and the programme spine. Do not edit it in GitBook: change the source and export again. {% endhint %} **NXS-OPS** is one of the twenty systems of the Nexus ecosystem: the physical instruments, sensors, calibration and primary observation evidence 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 `OP`. ## Purpose and context Physical observation infrastructure lifecycle. Its domain is instruments, sensors, observatories, calibration and primary measurement. A typical setting is an environmental sensor estate with scheduled calibration and field campaigns. ## What it is the authority for | Record | What the system must keep | | ------------------ | ---------------------------------------------------------------------- | | instrument | Separate physical serial number, installation and replacement history. | | calibration | Validate applicability at measurement capture time, not merely today. | | measurement method | Carry units, range, sampling protocol and detection limits. | | custody | Retain source, technician and handling evidence for observations. | | sampling plan | Respect duty cycles, maintenance windows and measurement objectives. | ## 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. | Room | Kind | Purpose | | ----------- | ---------- | ----------------------------------------------------------------------------------------------------------------------------------------------- | | 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 | | Instruments | Specialist | Records: instrument, instrument installation, sampling configuration, instrument work order, observation stream binding | | Metrology | Specialist | Records: calibration procedure, reference artifact, calibration run, measurement uncertainty budget, measurement fitness decision | **Kinds of work it carries:** Observation estates; Observation campaigns; Sensor Registry; Calibration Product; Observation Stream; Site Measurement Product; Instrument Health; Observatory sites; Sensor inventories; Structural health monitoring; Weather station networks; Hydrometric networks; Coastal sea-level networks; Seismic and geodetic networks; Air-quality networks; Weather radars; Farm sensor networks; Camera networks; Community observer networks; Calibration programmes; Calibration laboratories; Field maintenance programmes; Telemetry estates; Instrument health watches; Site measurement surveys. **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 | Physical instruments, sensors, calibration and primary observation evidence | | In the programme | Built, simulated and prepared in the [Foundry pillar](/organization/programme/foundry.md); its records serve the other pillars through the handoffs of [the programme year](/organization/programme/the-programme-year.md), and the competent authority decides outside the programme. | | System profile | [NRS-S11](https://nexustandards.com/standards/nrs/#nrs-s11): NXS-OPS (Instruments, sensors and calibration) (status OPEN) | | Nexus Risk Standards that apply | 4 in 3 series: system: [NRS-S11](https://nexustandards.com/standards/nrs/#nrs-s11); technology: [NRS-T4](https://nexustandards.com/standards/nrs/#nrs-t4), [NRS-T6](https://nexustandards.com/standards/nrs/#nrs-t6); cross-cutting: [NRS-X12](https://nexustandards.com/standards/nrs/#nrs-x12) | | Nexus Reports technology streams | GSP Earth observation and space; SNS Sensing, timing and positioning | ## Outputs What it provides, and to whom. Consumers read projections; the system stays the authority for its own records and their corrections. | To | What it provides | | ------------------------------------------- | --------------------------------------- | | [NXS-GRX](/organization/systems/nxs-grx.md) | physical observations | | [NXS-EWS](/organization/systems/nxs-ews.md) | sensor observations | | [NXS-NSF](/organization/systems/nxs-nsf.md) | authorization/policy evaluation request | | the evidence fabric | append consequential receipt/evidence | ## Interfaces with other systems Beyond its interfaces, it relies on fact families owned elsewhere: consent authority ([NXS-NSF](/organization/systems/nxs-nsf.md)); delegation authority ([NXS-NSF](/organization/systems/nxs-nsf.md)). ## Areas it serves | Area | Category | What the area covers | | ----------------------------------------------------------- | ---------- | ----------------------------------------------- | | [Infrastructure resilience](/organization/systems/areas.md) | Technology | Energy, water, transport and essential services | ## 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. | Standard | Issuer | Year | Use | | ----------------------------------------------------- | ------ | ---- | ------------------------------------ | | 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 | ## Governance boundaries Policy authority for the system sits with [NXS-NSF](/organization/systems/nxs-nsf.md); 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: * signal analysis (NXS-SIG) * network topology primary source (NXS-NET) * NXS-NSF legal attestation authority * mining / tokens / investment rewards **Method boundary.** Uncertainty propagation must include covariance where relevant. Calibration validity depends on capture time and operating range; out-of-range or below-detection observations need explicit qualifiers. Do not accept a measurement using the latest calibration when a different calibration applied at capture time. [All twenty systems](/organization/systems.md) ยท [Areas](/organization/systems/areas.md) *** *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.* --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.therisk.global/organization/systems/nxs-ops.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.