Energy & electric grid | Modelled case study
Rotate substation device certificates inside narrow outage windows
Can relay, gateway, and engineering trust change without creating a protection or visibility gap?
The modelled organisation
A recognisable problem reaches the operating agenda
This composite scenario follows the Substation Engineering · PKI · Field Operations functions. It is grounded in the cited problem context but does not identify a real customer.
Operating environment
An electric utility coordinates control centres, substations, protection systems, field communications, market interfaces, recovery sites, and specialist suppliers.
What is at stake
Security work must fit narrow operating windows and preserve safe control, restoration capability, and accountable remote access to critical assets.
Situation
Remote assets may require truck rolls, vendor tools, synchronized trust updates, and rollback under strict operational switching plans.
Event that forces action
Certificate expiry, CA migration, merger of utility trust domains, or compromise response.
Concrete system boundary
Systems this case study puts in scope
The model is specific about the operational surfaces that must be discovered, changed, or independently checked.
protection and control devices
substation PKI
engineering access tools
outage-window activation and rollback
Modelled case study walkthrough
How this organisation would use QNSI
The walkthrough connects the real-world problem to a bounded QNSI contribution and an independently reviewable result.
Recognise the operating condition
Remote assets may require truck rolls, vendor tools, synchronized trust updates, and rollback under strict operational switching plans.
Frame the decision the owners must make
Can relay, gateway, and engineering trust change without creating a protection or visibility gap?
Apply QNSI to the controlled boundary
Use QNSI lifecycle records to group assets by issuer, mechanism, access path, outage window, and rollback readiness.
Leave the team with a concrete result
A substation rollover schedule with field package, trust overlap, pretest, abort criteria, and post-change proof.
Prove the result in the organisation's environment
Grid operations validates relay behavior, remote access, fail-safe state, communications, and restoration procedure.
What useful success looks like
A decision artifact plus proof from the real environment
The model stops at a target result. It becomes an actual case study only when a customer produces and independently validates this evidence in production.
Decision artifact
A substation rollover schedule with field package, trust overlap, pretest, abort criteria, and post-change proof.
Independent validation boundary
Grid operations validates relay behavior, remote access, fail-safe state, communications, and restoration procedure.
Real-world problem grounding
Primary sources behind the model
These sources establish the external requirement, failure mode, or risk context used to model this case. They do not endorse HEOSSI or prove that QNSI completed the scenario.
Customer evidence status
This is modelled, not a customer claim
The organisation is a composite and the result is a target state. This page does not prove a deployment, customer outcome, certification, legal conclusion, regulator endorsement, or completed control.