Skip to content

System Architecture & Overview

Jump to bottom
Sam S edited this page May 8, 2026 · 1 revision

STUDSYS24

Welcome to the Central Documentation Hub for StudSys24.

StudSys24 is a high-performance, multi-platform technical suite designed to revolutionize the vatSys radar environment. It is more than a simple plugin; it is a unified ecosystem that bridges professional air traffic control (ATC) software with enterprise-grade server hosting and automated communication gateways.

This wiki serves as the definitive technical manual for the architecture, deployment, and operation of the entire StudSys24 project.

1. MISSION STATEMENT & PROJECT SCOPE

The primary objective of StudSys24 is to provide a "Single Pane of Glass" experience for virtual controllers. By consolidating radar telemetry, voice communications, and backend data logging into one synchronized stream, the project eliminates the technical friction often found in complex vATC operations.

  • Radar Fidelity: Real-time synchronization of aircraft tracks via high-speed WebSockets.

  • Voice Integration: A native Voice Communication System (VCS) interface that drives external Discord protocols.

  • Data Persistence: 24/7 logging and metrics processing hosted on dedicated enterprise hardware.

  • Reliability: A "Zero-Local-Failure" build philosophy powered by cloud-based CI/CD automation.

2. CORE ARCHITECTURAL PILLARS

The StudSys24 ecosystem is divided into three primary tiers, ensuring that failure in one module does not compromise the integrity of the entire system.

A. THE FRONTEND (Plugin Tier)

Developed in C# and targeting the .NET Framework 4.8, the frontend is the user-facing component. It operates as a dynamic link library (.dll) that extends the native capabilities of vatSys.

  • Custom UI Windows: Draggable, dockable panels for VCS and CDS management.

  • Coordinate Engine: A bespoke transformation layer that maps global geodetic coordinates to local radar projection.

B. THE BACKEND (Server Tier)

The "Heart" of the system, hosted on a Lenovo ThinkSystem SR630 running Ubuntu Server 22.04 LTS.

  • Dual Intel Xeon Silver 4114 Performance: Overkill processing power ensures zero-latency handling of incoming VATSIM data packets.

  • Database Management: Long-term storage of flight data, controller sessions, and system logs.

  • Process Persistence: Managed by PM2, ensuring that even in the event of a system reboot, the CDS services resume immediately.

C. THE BRIDGE (Gateway Tier)

The communication layer that connects the local workstation to the wider network.

  • Discord RPC (Remote Procedure Call): Controls the local Discord client for voice channel switching.

  • WebSocket Uplink: The primary data pipe for aircraft positions and flight plan updates.

3. TECHNICAL SPECIFICATIONS & ENVIRONMENT

To maintain the high performance required for professional vATC simulation, StudSys24 adheres to the following technical standards:

Feature | Specification -- | -- Development Language | C# (Latest) Runtime Environment | .NET Framework 4.8 Host Hardware | Lenovo SR630 (Dual Xeon / 16GB+ RAM) Target OS | Windows 10/11 (Client) / Ubuntu Server (Host) Build System | GitHub Actions (MSBuild / NuGet) Third-Party APIs | Discord RPC, Newtonsoft.Json, vatSys SDK

4. SYSTEM REPOSITORY STRUCTURE

The repository is organized to separate the various domains of the project clearly:

  • /CDS: Contains the Control Display System logic, including the Discord VCS window and the RPC bridge code.

  • /Properties: Manages system-level metadata, including the project GUID and assembly versioning.

  • .github/workflows: Houses the YAML build scripts that manage the automated cloud compilation.

  • StudSys24.sln: The master Solution file for Visual Studio 2022.

5. DEPLOYMENT & MAINTENANCE

StudSys24 is designed for continuous deployment.

  1. Code: Developers push updates to the repository.

  2. Build: GitHub Actions automatically compiles the code into a production-ready .dll.

  3. Release: The user downloads the artifact and places it in the vatSys Plugins directory.

  4. Host: The Ubuntu backend runs 24/7, managed by the PM2 process manager, providing a stable backbone for all connected clients.

6. DOCUMENTATION INDEX

For detailed guides on specific modules, navigate to the following chapters:

  • [Technical Setup & Installation]: How to prepare your environment for the StudSys24 plugin.

  • [VCS Configuration]: Setting up the Discord Developer Portal and RPC scopes.

  • [Server Administration]: managing the Lenovo SR630 Ubuntu host.

  • [Data Ingestion Math]: A deep dive into coordinate transformation and JSON parsing.

"Precision Control. Unified Communication. Absolute Reliability."

Clone this wiki locally