sat-nms database
For some applications its required to store additional data on the M&C system. For these purposes our platform provides a reliable and scalable database service that enables customers to securely store and manage data. By handling database provisioning, configuration, and maintenance in the background, we allow users to focus entirely on their operations instead of database management.
The solution is designed to integrate seamlessly into your existing environment. Whether you’re running a small installation on a single sat-nms MNC server or using a fully redundant database cluster, you have complete flexibility.
We rely on PostgreSQL, the world's most advanced open-source relational database - proven, stable and powerful to ensure reliability, scalability and long-term support.
We deliver our systems with a pre-installed and pre-configured database, including automated migration scripts to handle future schema updates, eliminating the need for manual database administration. For customers already operating PostgreSQL clusters, our platform can easily connect to existing database environments.
Features
- Satellites and antennas: store satellites and their positions together with TLE or i11 elements, beacons and more
- Channels: manage satellite and IP streaming channels and push related settings directly to the equipment
- Stream key: store BISS and Streaming keys to inject them easily into IRDs and Encoders
- Inventory: keep track of your equipment and maintenance information to your devices
- Measurement records: store and analyze any kind of parameter coming from your devices in a time series database(*)
Data recorder
Our integrated data recorder is powered by TimescaleDB, a leading time-series database built on PostgreSQL, enabling efficient storage and analysis of telemetry and sensor data at scale.
- Efficient data collection: Capture relevant parameters, at defined intervals or on value changes.
- Optimized storage: store large volumes of historical data efficiently using compression and scalable architecture.
- Real-Time & historical analytics: query and analyze both live and historical data to gain operational insights.
- Visualization & correlation: explore data through flexible graphs and correlate multiple parameters for deeper analysis.
- Data export: export queried data as CSV files for further analysis or external use.
- Alerting & thresholds: define thresholds, trigger alarms, and measure duration of critical conditions.
- Data lifecycle management: manage retention policies and database behavior to balance performance and storage requirements.
Antenna Management
Data for all required satellites is stored in the central database and is then available to move every connected antenna. This ensures consistent naming and eliminates the need to save data multiple times for each antenna. Together with the Antenna-Management logical device you can use ephemeris data like Norad TLE Two-Line elements or Intelsat I11 elements stored in the database to perform antenna tracking through the sat-nms MNC system.
- central database for all satellites
- central store for ephemeris data
- table tracking from imported file
- integrated antenna scheduling
- update database via REST-API
- TLE bulk import (e.g. Celestrak's geo.txt)
- satellite operator contact details
For each satellite additional information can be stored to configure receive or transmit equipment when moving to a new satellite. This includes:
- multiple satellite beacons per satellite
- tele-command and telemetry channels
Satellite and IP/Streaming Channels
The Channel Database is a central store for receive and transmit channels. Its supports RF/Satellite channels as well as IP/Streaming channels. Channel devices using entries from the database to configuring RX equipment like IRD's, satellite demodulators or decoders and TX equipment like encoders or satellite modulators with one click.
- centralized channel management
- for satellite and streaming channels
- for transmitters and receivers
Workflows
Filter by channel
- Search for a channel in the database and select it
- Shows matching matrix ports for selected channel
- Selecting a port configures matrix and equipment
- Automatic antenna selection for receive channels
Filter by satellite
- Select antenna first and then one of the available satellites
- Every selection reduces the number of available channels
- Select a channel and antenna is moved to satellite
- Equipment is configured to receive or transmit the channel
Activation based
- Search for a receive channel in the database and select it
- A matching antenna is automatically selected and moved to the satellite
- Receive equipment and matrix is configured
- Receivers and antennas are locked
Stream keys
Store credentials for streaming or broadcast applications directly in the M&C system and send the keys with one click to the equipment if needed. No need to enter cryptically keys again and again, just assign a name and select it from a drop down list.
- BISS-1 and BISS-E keys with length and syntax check
- Any kind of password or passphrases
- for Encoders, IRD, DVB modulators etc.
Inventory and Logbook
The Inventory Database provides two main functions: Tracking of equipment and assigning documents to devices. Devices can be identified and tracked by the system using their serial number and device type. This creates an inventory of equipment connected to the sat-nms MNC systems.
- automatically add new devices to the inventory
- tracks devices across MNC systems
- create logbook of state changes (online / offline)
- add user defined logbook entries (e.g. repairs)
Additionally, documents can be uploaded to provide fast access to for example user manuals for equipment or test protocols for a specific device. Documents can be assigned to the overall system, a MNC system, or to a device driver.
Redundancy Options
In simple Standalone M&C systems the PostgreSQL database runs directly on the same server and all modules communicate directly - no additional configuration required. Database redundancy is achieved by enabling the PostgreSQL built-in logical replication between main and backup database. All elements which needs to access the database like backend service, antenna management devices or channel devices are designed to use a fallback server if the main database is not reachable.
In this case all operations are read-only to avoid any complicated database management. After restoring the main database work can continue directly.
The current state of the database will be also show in the WebUI on system status page and in case of a main database failure directly in the top tool bar.