vOCC
Backoffice path: backoffice/occ/vocc
Available to roles: System Administrator, Administrator
Overview
The Virtual Operations Control Center (vOCC) is an AI-powered dispatch system built on OpenRouter. It provides real-time operational support to pilots through proactive advisories, route optimization suggestions, and an interactive chat interface. Administrators use the vOCC backoffice page to toggle features, monitor activity, and configure language settings.
Master Toggle
The entire vOCC system is controlled by a single master toggle:
VOCC_ENABLED-- enables or disables all vOCC functionality. When disabled, no AI features will trigger and pilots will not receive vOCC messages.
Feature Toggles
Each vOCC capability can be independently enabled or disabled:
| Toggle | Description |
|---|---|
VOCC_WEATHER_ADVISORY | When enabled, vOCC sends a weather advisory to pilots at approximately 60 minutes before estimated arrival. The advisory includes relevant METAR/TAF data and any weather-related concerns for the destination. |
VOCC_ARRIVAL_INFO | When enabled, vOCC sends arrival information to pilots at approximately 30 minutes before estimated arrival. This includes runway information, approach procedures, and other arrival-relevant data. |
VOCC_CHAT_AI | When enabled, pilots can chat directly with the vOCC AI. The chat uses the AI's native function calling with up to a 50-iteration tool loop, allowing the AI to gather information, run analyses, and provide detailed responses to pilot queries. |
VOCC_DCT_SUGGESTIONS | When enabled, vOCC suggests direct-to (DCT) route optimizations based on the pilot's current position and Flight Information Region (FIR). These suggestions help pilots request more efficient routing from ATC. Runs as part of Flight Following (requires VOCC_FLIGHT_FOLLOWING). |
VOCC_FLIGHT_FOLLOWING | When enabled, vOCC continuously monitors active flights for holding patterns, excessive fuel burn, overweight landing risk, fuel starvation, and DCT shortcut opportunities. Alerts are sent once per flight per condition. Requires SimBrief OFP data for fuel and route analysis. |
Default Language
The vOCC default language is configurable, controlling which language the AI uses for proactive messages sent to pilots. Per-language configurations can be managed on the vOCC Language page.
AI Tool Access
The vOCC AI has access to over 30 tools organized into the following categories:
| Category | Tools |
|---|---|
| Weather | METAR reports, TAF forecasts for airports along the route and at the destination. |
| Airport Information | Airport details, runway data, frequencies, facilities, and operational status. |
| Navigation | Waypoints, airways, FIR boundaries, and navigation aid data. |
| Aircraft Data | Aircraft specifications, performance data, and current status. |
| Flight Operations | Flight plan details, progress tracking, fuel state, and ETA calculations. |
| Fuel Analysis | Fuel burn rates, remaining fuel calculations, and diversion fuel analysis. |
| Safety | Safety events, NOTAMs (real-world and company), airspace restrictions, and hazard information. |
| SimBrief | Integration with SimBrief for operational flight plan data. |
| Alternates | Alternate airport suggestions based on weather, fuel, and distance. |
| Network | Active ATC positions, live traffic in the area, and network status. |
| Action Tools | Send messages to pilots, create tech log entries, and perform operational actions. |
This extensive toolset allows the AI to provide comprehensive, context-aware assistance to pilots across all phases of flight.
Dashboard
The vOCC backoffice dashboard is organized into three sections:
Feature Toggle Cards
A set of cards displaying the current state of each vOCC feature toggle. Administrators can quickly see which features are active and toggle them as needed.
Recent Triggers
A table showing the last 20 vOCC triggers -- events that caused the AI to activate (e.g., a pilot reaching the 60-minute weather advisory threshold, or a DCT suggestion opportunity). Each entry shows:
| Column | Description |
|---|---|
| Time | When the trigger fired |
| Pilot | Pilot name (snapshotted at trigger time) |
| Callsign | Full callsign (e.g., TST100) |
| Route | Departure → Arrival ICAO codes |
| Aircraft | Aircraft registration |
| Trigger | Color-coded trigger type badge |
Flight data is snapshotted when the trigger fires, so pilot names, callsigns, and airports remain visible even after the associated booking has been completed or deleted.
Interaction Log Flyout
Clicking any trigger row opens a detail flyout showing:
- Trigger metadata -- type badge and timestamp
- Flight context -- pilot, callsign, route, and aircraft
- Full AI interaction log -- the complete prompt sent to the AI, any tool calls made during the interaction (for tool-loop triggers), and the final response delivered to the pilot
This allows administrators to review exactly what the AI saw, what actions it took, and what message it generated -- useful for quality assurance and debugging.
Recent vOCC Messages
A table showing the last 20 messages sent by the vOCC system to pilots. This provides a quick audit trail of what the AI has been communicating, including weather advisories, arrival information, and chat responses.
Data Retention
vOCC trigger records are automatically pruned after 30 days. This includes the snapshot data and interaction logs. The pruning runs daily via the DispatchPruneVoccTriggers scheduled job, which iterates all tenants and removes expired records.
vOCC Language Configuration
The vOCC Language page allows administrators to manage per-language configurations for proactive messages. This is useful for airlines operating in multilingual environments where pilots may prefer to receive advisories in their native language. Each language configuration controls the tone, format, and content of the AI's proactive messages.