Solutions / Space NIS-2 · Space
Voice Loops for mission control
openvocs was developed at the German Space Operations Center of DLR. In 2023 it ran in its first mission, a MORABA research campaign in Kiruna.
Diagram, not a screenshot. Two positions talk at the same time, the server mixes.
Loop example
Distributed control rooms
A mission is often run from several control rooms, with ground stations and partners at other sites. Each role hears the loops of its task. Partners should be able to join without a voice system of their own.
- FLIGHT DIRECTOR
- Mission lead
- GROUND STATION
- Ground stations, including remote sites
- FLIGHT DYNAMICS
- Orbit determination, listening
- PARTNER
- Partner organizations, connected for the campaign
What openvocs contributes
Proven in mission operations
First mission in 2023 with MORABA in Kiruna, presented at SpaceOps 2023.
Partners without special hardware
Partners join with a laptop, a headset and a browser. No client software, no voice system of their own.
Roles and loops
The configuration defines which loops a role hears. Mixing runs on the server.
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 |
|---|---|---|
| Space | NIS-2, Annex 1, space sector | proven in mission operations at GSOC |
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