Solutions / Transport KRITIS
Voice Loops for operations control centers
Operations control, dispatch and fault service talk on separate loops instead of one broadcast channel. Anyone who needs several loops hears them at the same time.
Diagram, not a screenshot. Two positions talk at the same time, the server mixes.
Loop example
A typical operations control center
An operations control center in public transport dispatches vehicles, takes fault reports and organizes replacement services. Over radio, only one position talks at a time and everyone else waits.
- OPERATIONS
- Dispatchers in the control center
- DRIVER DESK
- Service management and coordination of drivers
- FAULT SERVICE
- Engineering and maintenance, listening
- SECURITY
- Security staff, joins when needed
What openvocs contributes
Separate loops
Each task has its own loop. Dispatchers monitor several at once and talk via Push-to-Talk on the one they need.
Recorder
Signed multichannel recording where recording is required, for example on rail under § 16(2) EBO. The operator needs a legal basis under the GDPR and works council approval.
Neighboring control centers
Neighboring control centers and partners share loops without shared hardware.
Multi-site network
Distributed control rooms and partners share loops without shared hardware.
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 |
|---|---|---|
| Transport | BSIG, KRITIS ordinance; rail also § 16(2) EBO | Recorder with signed recording where recording is required |
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