QGuard: Know What an Event Means for Your Operations

A static continuity plan describes expected scenarios. QGuard is designed to connect unfolding conditions to an operator’s actual facilities, people and commitments.

• Consider the implications for static plans.
• Keep the organization’s operational context in view.
• Support a decision by the responsible people.

External feeds can produce many updates. The proposed QGuard workflow relates relevant signals to operational impact and priority.

• Consider the implications for alert overload.
• Keep the organization’s operational context in view.
• Support a decision by the responsible people.

Suppliers, utilities and partners can affect service continuity. QGuard is designed to surface the dependency and its potential consequence.

• Consider the implications for hidden dependencies.
• Keep the organization’s operational context in view.
• Support a decision by the responsible people.

QGuard is designed to help operators recognize developing consequences earlier than manual coordination may allow. That advantage remains to be tested.

• Consider the implications for late recognition.
• Keep the organization’s operational context in view.
• Support a decision by the responsible people.

Facilities, operations and leadership may see different aspects of a situation. QGuard is designed to provide a common operational context.

• Consider the implications for siloed views.
• Keep the organization’s operational context in view.
• Support a decision by the responsible people.

When updates move through calls and email, the developing picture can lag. QGuard is designed to present relevant consequences for human evaluation.

• Consider the implications for manual coordination.
• Keep the organization’s operational context in view.
• Support a decision by the responsible people.

An organization should retain authority over its own underlying operational records and decide what signals may be shared.

• Consider the implications for local data control.
• Keep the organization’s operational context in view.
• Support a decision by the responsible people.

A changing external event can affect facilities, access, staffing and service delivery in different ways.

• Consider the implications for facility readiness.
• Keep the organization’s operational context in view.
• Support a decision by the responsible people.

QGuard is designed to inform responsible people. It does not replace their authority to assess and decide.

• Consider the implications for people and roles.
• Keep the organization’s operational context in view.
• Support a decision by the responsible people.

Through NOS, participants are intended to share limited signals for defined purposes under rules they control.

• Consider the implications for partner signals.
• Keep the organization’s operational context in view.
• Support a decision by the responsible people.

Operational consequence includes which services may be interrupted, when and with what dependencies.

• Consider the implications for service continuity.
• Keep the organization’s operational context in view.
• Support a decision by the responsible people.

QGuard is designed to present relevant context and priorities to people responsible for continuity decisions.

• Consider the implications for human decisions.
• Keep the organization’s operational context in view.
• Support a decision by the responsible people.

The proposed workflow starts with an external signal that matters to the operator’s own activities.

• Consider the implications for recognize.
• Keep the organization’s operational context in view.
• Support a decision by the responsible people.

A signal becomes useful when it can be related to the organization’s facilities, people, dependencies and commitments.

• Consider the implications for context.
• Keep the organization’s operational context in view.
• Support a decision by the responsible people.

The proposed workflow is designed to inform the right human decision makers with a clear picture.

• Consider the implications for decision.
• Keep the organization’s operational context in view.
• Support a decision by the responsible people.

People choose actions using their established responsibilities and procedures.

• Consider the implications for action.
• Keep the organization’s operational context in view.
• Support a decision by the responsible people.

After an event, operators can use the lessons to improve their continuity plans and information pathways.

• Consider the implications for learning.
• Keep the organization’s operational context in view.
• Support a decision by the responsible people.

QGuard is designed to connect external conditions to an operator’s own operating context.

• Consider the implications for connect.
• Keep the organization’s operational context in view.
• Support a decision by the responsible people.

Translate a relevant signal into possible effects on people, sites, commitments and dependencies.

• Consider the implications for translate.
• Keep the organization’s operational context in view.
• Support a decision by the responsible people.

QGuard is designed to present consequences in a useful order, with reasons that people can assess.

• Consider the implications for prioritize.
• Keep the organization’s operational context in view.
• Support a decision by the responsible people.

The purpose is to support responsible human decisions rather than automate them.

• Consider the implications for inform.
• Keep the organization’s operational context in view.
• Support a decision by the responsible people.

NOS is designed to share constrained signals among independent participants without centralizing underlying records.

• Consider the implications for coordinate.
• Keep the organization’s operational context in view.
• Support a decision by the responsible people.

Bring event signals that matter to continuity into the operator’s view.

• Consider the implications for observe.
• Keep the organization’s operational context in view.
• Support a decision by the responsible people.

Relate those conditions to the organization’s own people, facilities and commitments.

• Consider the implications for interpret.
• Keep the organization’s operational context in view.
• Support a decision by the responsible people.

The organization remains responsible for its information and decisions.

• Consider the implications for preserve.
• Keep the organization’s operational context in view.
• Support a decision by the responsible people.

Present the changing picture clearly to the people who need to decide.

• Consider the implications for brief.
• Keep the organization’s operational context in view.
• Support a decision by the responsible people.

Constrained signals can support coordination with participating organizations through NOS.

• Consider the implications for coordinate.
• Keep the organization’s operational context in view.
• Support a decision by the responsible people.

Use what happened to strengthen continuity planning and future recognition.

• Consider the implications for improve.
• Keep the organization’s operational context in view.
• Support a decision by the responsible people.

Continuity planning needs to account for services that may be essential even when they are not prominent in existing plans.

• Consider the implications for untracked services.
• Keep the organization’s operational context in view.
• Support a decision by the responsible people.

Older systems can remain essential. Their operational dependencies should be understood when evaluating consequences.

• Consider the implications for legacy dependency.
• Keep the organization’s operational context in view.
• Support a decision by the responsible people.

Useful information can sit in different teams and systems. The goal is to relate it to an operator’s responsibilities.

• Consider the implications for separate information.
• Keep the organization’s operational context in view.
• Support a decision by the responsible people.

A clear operational picture needs ownership, escalation and communication pathways.

• Consider the implications for people and handoffs.
• Keep the organization’s operational context in view.
• Support a decision by the responsible people.

A supplier disruption may change what an operator can deliver, even when its own facilities remain intact.

• Consider the implications for supply chain.
• Keep the organization’s operational context in view.
• Support a decision by the responsible people.

An evolving condition may cross organizational boundaries in ways a predefined scenario did not anticipate.

• Consider the implications for changing conditions.
• Keep the organization’s operational context in view.
• Support a decision by the responsible people.

A change in weather, power, access or transport can affect vessel movements and connected operators.

• Consider the implications for ports and logistics.
• Keep the organization’s operational context in view.
• Support a decision by the responsible people.

Changes in power and water availability can create consequences for dependent organizations.

• Consider the implications for energy and utilities.
• Keep the organization’s operational context in view.
• Support a decision by the responsible people.

Agencies can benefit from earlier recognition of how independent conditions combine.

• Consider the implications for emergency management.
• Keep the organization’s operational context in view.
• Support a decision by the responsible people.

Hospitals and public services need to understand when outside disruptions may affect delivery.

• Consider the implications for healthcare and public services.
• Keep the organization’s operational context in view.
• Support a decision by the responsible people.