Solutions / Energy and utilities KRITIS
Voice Loops for grid control centers
Grid operations, on-call staff and field crews talk in fixed loops, in parallel and on the operator’s own network. The phone system connects through the SIP gateway.
Diagram, not a screenshot. Two positions talk at the same time, the server mixes.
Loop example
A typical grid control center
A municipal utility with its own grid runs power, gas and often water or district heating from one control center. During an outage, grid operations, on-call staff and field crews talk at the same time. When the situation grows, the crisis team joins.
- GRID OPS
- Shift supervisor and grid operators for power, gas and water
- ON-CALL
- On-call staff, also reachable by phone through the SIP gateway
- CREW NORTH
- Field crew on site, with laptop and headset
- CRISIS TEAM
- joins during a major outage
What openvocs contributes
On the operator’s network
The server runs in the utility’s data center and therefore within the scope of its own ISMS. No internet connection is needed.
SIP gateway
On-call staff and external parties reach the loops through the phone system, encrypted with SIPS and SRTP.
Self-assessment
For evidence based on BDEW/OE/VSE white paper 3.0, which names VoIP explicitly.
On-site control room
Installed in the operator’s data center, as a container or as a .deb or .rpm package.
Requirements for the operator
The obligations lie with the operator. The right-hand column shows how openvocs supports them.
| Area | Legal basis for the operator | Contribution of openvocs |
|---|---|---|
| Energy, grid operation | §§ 5c to 5e EnWG, IT security catalog, ISO 27001 certificate of the operator | Operation on the operator’s own network; self-assessment based on BDEW/OE/VSE white paper 3.0, which names VoIP explicitly |
| Water, district heating | BSIG, § 30 | secured voice and emergency communication (§ 30(2) no. 10) |
Not legal advice. More on the page Security and compliance.
Request a demo
The demo runs in the browser and takes about 45 minutes. Afterwards we work out loops, roles and integrations for the control room in question.
Direct: sales@spacecomms.com