NOS Platform: Coordination Across Organizations, Without Handing Over Your Data
NOS is a coordination protocol being developed for independent organizations that depend on one another. It is designed to help them recognize an emerging shared condition while each retains control of its own underlying operational data.
Share limited signals under agreed rules. Recognize what is changing together. Keep people responsible for decisions.
The Coordination Challenge
Each organization can see a valid piece of an event. The developing condition may only become clear when those pieces are considered together.
The Problem Lives Between Organizations
A port, utility and hospital can each see part of the same developing disruption.
Read briefingPooling Data Is Not an Option
Operators need control of sensitive operational data and who may use it.
Read briefingCustom Connections Do Not Scale
Adding each new partner through a separate integration can slow coordination.
Read briefingPosting Can Come Too Late
Shared systems receive an update only after somebody recognizes and posts it.
Read briefingPrewritten Rules Have Limits
Unexpected combinations of conditions can fall outside anticipated scenarios.
Read briefingIsolated Views
Each organization understands its own situation, but may miss the collective change.
Read briefingWhat NOS Is
NOS is a proposed protocol for coordination among independent organizations. It is being designed to work alongside the systems operators already use.
Each participant would retain its underlying operational data within its own boundary and authorize limited, purpose-bound signals for agreed coordination. The specific mechanism and its performance remain matters for research and testing.
Across those signals, NOS is intended to help people recognize when a shared operational condition is emerging and decide what to do next.
The NOS Strategic Principle
Four commitments guide the design: local control, limited sharing, earlier shared recognition and human decisions.
What Makes NOS Different
These are design goals for a network of independent operators, subject to technical validation.
Local Data Control
Underlying operational records remain with the organization that owns them.
Open layerPurpose-Bound Signals
Participants would authorize constrained signals for a defined coordination purpose.
Open layerShared Recognition
The network is intended to surface a material change visible across participants.
Open layerExisting Systems
NOS is designed to complement incident management, notification and operational systems.
Open layerHuman Authority
People evaluate the emerging picture and decide on action.
Open layerSecurity at Every Node
Security tools secure each participant’s environment. NOS is designed to coordinate across the network.
Open layerHow NOS Relates to the Wider Work
The proposed protocol has a distinct role alongside QGuard and existing operator systems.
The Problem We Are Testing
Can independent operators recognize a materially changing collective condition sooner than through their established coordination process?
The proposed research examines whether limited signals can support that recognition without moving underlying operational data into a shared environment.
The timing, accuracy, information boundaries and practical value of this approach must be measured against a defined baseline.
NOS in Context
NOS is intended to complement established operational and security systems while addressing the gap between independent organizations.
NOS and WebS
WebS describes future infrastructure services. NOS addresses coordination between participating operators, regardless of where each runs its systems.
They have separate purposes and development paths.
Explore WebSNOS and QGuard
QGuard gives one organization a clearer picture of potential operational consequences. NOS is designed to help several organizations recognize an emerging shared condition.
Explore QGuardNOS and Existing Security Tools
Each participant remains responsible for securing its own systems, access and communications.
NOS is designed to coordinate permitted signals across participants. It does not replace their cybersecurity controls.
Recognition Across Boundaries
A changing condition can affect several independent operators before any one has the whole picture.
NOS is designed to help participants identify that shared change earlier while retaining their separate responsibilities and information boundaries.
The intended output is a clearer question for the people responsible: what is developing, who may be affected, and what should be checked or decided?
The Long Horizon Vision
Critical infrastructure becomes more interdependent as the information describing it remains in separate hands.
NetQube is exploring a coordination layer that could respect those boundaries and improve recognition across them, if the proposed mechanism proves effective.
Our long-term ambition is a useful protocol that independent operators can adopt without surrendering control of their own systems or data.
Coordinate Without Surrendering Control
Discuss a specific operational dependency, the existing coordination baseline and what a bounded NOS experiment would need to prove.
The Problem Lives Between Organizations
The collective condition can emerge between valid local observations.
A port may see access pressure while a utility sees load instability and a hospital sees staffing risk. Together these observations may warrant attention before any one operator recognizes the whole change.
- Each view is locally valid.
- The relationship between views can matter.
- NOS is being tested for earlier shared recognition.
Pooling Data Is Not an Option
Sensitive records remain under local control.
Independent operators have legal, operational and trust reasons to keep underlying data within their own environments. NOS is being designed around limited, agreed signals.
- Retain underlying records locally.
- Agree what may be shared and why.
- Evaluate the information boundary in a pilot.
Custom Connections Do Not Scale
Coordination needs repeatable rules.
Connecting every pair of operators through bespoke integrations can be slow and fragile. A protocol could provide a repeatable way to coordinate agreed signals.
- Define a shared coordination purpose.
- Limit bespoke point-to-point work.
- Test compatibility with existing systems.
Posting Can Come Too Late
A post follows a person’s recognition.
Incident platforms are valuable for sharing recognized information. The research question is whether NOS can surface a changing collective condition before someone would normally choose to post it.
- Record the existing recognition baseline.
- Measure when participants see a shared condition.
- Keep human review in the process.
Prewritten Rules Have Limits
Unexpected combinations deserve investigation.
Rules can work well for known conditions. NOS research examines whether the interaction of ordinary local changes can signal a new collective state.
- Describe what current rules catch.
- Test previously unseen combinations.
- Measure false alarms as well as early recognition.
Isolated Views
An operator sees its own world first.
Each participant understands its own operations. NOS is intended to add a bounded view of what may be changing across participants without removing local control.
- Preserve individual authority.
- Share only agreed signals.
- Surface the collective picture for people.
Local Data Control
The organization remains responsible for its records.
The proposed design keeps underlying operational information within the owner’s environment while permitting only agreed signal sharing.
- Keep records under local governance.
- Set and enforce participation rules.
- Test that boundaries hold.
Purpose-Bound Signals
Share what is needed for a defined purpose.
A signal should be constrained to the coordination question and authorized by the participant. The specific design remains to be validated.
- Limit scope and recipients.
- Define the purpose and duration.
- Audit what was shared.
Shared Recognition
Look for a material collective change.
NOS is intended to bring an emerging cross-organization condition to authorized people’s attention. A pilot must determine how early and how reliably it can do so.
- Specify what counts as recognition.
- Compare with the baseline.
- Report misses and false alarms.
Existing Systems
Work with operator tools.
The concept is to complement established incident management, notification and operational systems rather than require their replacement.
- Respect current workflows.
- Define the handoff to people.
- Test integration in a bounded setting.
Human Authority
People remain the decision makers.
A shared signal should prompt assessment by authorized operators. It is not an automatic command to take operational action.
- Show the source and scope of a signal.
- Leave decisions to accountable people.
- Record when a decision was made.
Security at Every Node
Security remains a local responsibility.
Security tools protect each participant’s environment. The NOS research question concerns coordination among those independently secured environments.
- Keep local access controls.
- Protect communications and provenance.
- Test the coordination boundary.