✈️ AeroOps Unified Slot Engine & Messaging Operational Manual

Welcome to the AeroOps Unified Slot Engine Operational Manual. This document serves as the comprehensive technical reference for flight operations officers, airport slot coordinators, and airline scheduling specialists (OCC / Airport Coordinators / Airline Scheduling Specialists) to analyze, generate, and process standard airport slot messages under IATA SSIM Chapter 6 and Worldwide Airport Slot Guidelines (WASG / WSG).

---

🏛️ 1. IATA Airport Coordination Levels

IATA categorizes airports into three operational coordination levels based on capacity constraints:

1. Level 1 (Non-Coordinated Airport): Open airport capacity with no slot allocation requirements.
2. Level 2 (Facilitated Airport): Facilitated airport experiencing congestion during specific peak hours. Managed by a Schedule Facilitator using SMA and WMA messages for voluntary timetable alignment.
3. Level 3 (Coordinated Airport): Fully coordinated, highly congested facility (e.g., Cairo CAI, London Heathrow LHR, Dubai DXB, Paris CDG). Managed by an official Slot Coordinator, where prior slot approval via SCR, SAL, SHL, SAQ, and WCR messages is legally mandatory for all flights.

---

📑 2. Full 10 Standard IATA Message Types Catalog

The AeroOps engine supports full parsing, syntax validation, and real-time generation for all 10 standard IATA message types:

1️⃣ SCR (Slot Clearance Request / Response)

• Description: Primary message used to request, modify, or delete airport slots at Level 3 Coordinated Airports.
• Valid Syntax (New Turnaround Request):

SCR
S26
14JUN
CAI
NMS0778 MS0777 01JUN30OCT 1234567 180320 LHR0630 0830LHR JJ
SI SEASONAL DAILY SCHEDULED PASSENGER SERVICE
GI BRGDS EGYPTAIR OCC

2️⃣ SCR Retiming Request

• Valid Syntax (Deleted D-line + Revised R-line):

SCR
S26
20JUL
CAI
DMS0778 MS0777 01JUN30OCT 1234567 180320 LHR0630 0830LHR JJ
RMS0778 MS0777 01JUN30OCT 1234567 180320 LHR0715 0915LHR JJ
SI RETIMING ARRIVAL AND DEPARTURE SLOTS BY 45 MINS
GI BRGDS EGYPTAIR OCC

3️⃣ SMA (Schedule Movement Advice)

• Description: Timetable schedule advice message sent to data facilitators at Level 2 Facilitated Airports.
• Valid Syntax:

SMA
S26
15MAY
SSH
NMS0312 MS0313 01JUN15SEP 0000067 165320 CAI1000 1115CAI JJ
SI WEEKEND DOMESTIC SCHEDULE ADVICE
GI BRGDS EGYPTAIR SCHEDULING

4️⃣ SIR (Schedule Information Request)

• Description: Information query message to request schedule or slot details without modifying existing allocations.
• Valid Syntax:

SIR
S26
10JUN
CAI
QMS0778 15JUL15JUL 0030000 LHR
SI SLOT INFORMATION QUERY FOR SPECIFIC FLIGHT
GI BRGDS EGYPTAIR OPS

5️⃣ SAQ (Slot Availability Query)

• Description: Pre-flight inquiry to check remaining available slot capacity before submitting formal SCR requests.
• Valid Syntax:

SAQ
S26
20MAY
CAI
NMS0778 MS0777 01JUN30OCT 1234567 180320 LHR0800 0930LHR JJ
SI INQUIRING AVAILABLE SLOT CAPACITY FOR MORNING PEAK
GI BRGDS EGYPTAIR PLANNING

6️⃣ SHL (Slot Historical List)

• Description: Coordinator-issued baseline list detailing historical slot precedence (Grandfather Rights) under the 80/20 rule.
• Valid Syntax:

SHL
W25
15SEP
CAI
H MS0778 MS0777 01NOV30MAR 1234567 180320 LHR0630 0830LHR JJ
SI HISTORICAL BASELINE ELIGIBLE FOR GRANDFATHER RIGHTS
GI BRGDS CAI SLOT COORDINATOR

7️⃣ SAL (Slot Initial Status Baseline)

• Description: Initial baseline allocation status published by coordinators prior to the bi-annual IATA Slot Conference.
• Valid Syntax:

SAL
S26
01OCT
CAI
K MS0778 MS0777 01MAY31OCT 1234567 180320 LHR0630 0830LHR JJ
SI INITIAL SLOT ALLOCATION STATUS PRIOR TO SLOT CONFERENCE
GI BRGDS CAI SLOT COORDINATOR

8️⃣ WCR (Waitlist Clearance Request)

• Description: Slot request queued on the coordinator waitlist seeking improved arrival/departure timings during peak hours.
• Valid Syntax:

WCR
S26
18AUG
CAI
WMS0778 MS0777 01SEP30OCT 0204060 300333 LHR1100 1230LHR JJ
SI WAITLIST REQUEST FOR PEAK HOUR IMPROVED SLOTS
GI BRGDS EGYPTAIR SCHEDULING

9️⃣ WMA (Waitlist Movement Advice)

• Description: Schedule waitlist update notification for Level 2 facilitated airports.
• Valid Syntax:

WMA
S26
12JUN
SSH
W MS0898 MS0897 01JUL31AUG 0000067 220321 CAI1200 1330CAI CC
SI WAITLIST MOVEMENT ADVICE FOR LEVEL 2 FACILITATED TIMETABLE
GI BRGDS SSH FACILITATOR

🔟 WSH (Waitlist Schedule History) & WIR

• Description: Audit trail log for waitlisted slot requests and schedule position inquiries.
• Valid Syntax (WSH):

WSH
S26
05AUG
CAI
H MS0778 MS0777 01JUN30OCT 1234567 180320 LHR0630 0830LHR JJ
SI HISTORICAL RECORD AUDIT TRAIL OF WAITLIST QUEUE
GI BRGDS CAI SLOT COORDINATOR

---

🧩 3. Anatomy of a SSIM Schedule Line

An IATA SSIM slot line is constructed using fixed fields:

$$ \text{[Action]} \quad \text{[ArrFlt]} \quad \text{[DepFlt]} \quad \text{[Period]} \quad \text{[Days]} \quad \text{[Config]} \quad \text{[ArrRouting]} \quad \text{[DepRouting]} \quad \text{[Service]} $$

Line Breakdown Example:

NMS0778 MS0777 01JUN30OCT 1234567 180320 LHR0630 0830LHR JJ

| Field | Value | Operational Definition | | :--- | :--- | :--- | | Action Code | N | New schedule line request. | | Arrival Flight | MS0778 | Inbound flight designator (EgyptAir). | | Departure Flight| MS0777 | Outbound flight designator (Turnaround). | | Period of Ops | 01JUN30OCT | Start and end date of operation (June 1 to October 30). | | Days of Ops | 1234567 | Frequency days of week (1=Monday, 7=Sunday). | | Aircraft Config | 180320 | 180 passenger seats + Airbus A320 subtype. | | Arrival Details| LHR0630 | Origin airport LHR and arrival time 06:30 UTC. | | Dep Details | 0830LHR | Departure time 08:30 UTC and destination airport LHR. | | Service Type | JJ | Inbound/Outbound passenger service type (J = Scheduled Passenger). |

---

📋 4. IATA Action Codes Reference

• N (New): Request a brand new slot allocation.
• C (Change): Modify an existing slot allocation (requires a D delete line and an R revised line).
• D (Delete): Cancel or delete a previously allocated slot.
• R (Revised): New proposed schedule timings accompanying a D line.
• K (Confirmation): Coordinator confirmation of allocated slot.
• U (Unable): Coordinator clearance refusal due to lack of capacity.
• O (Offer): Alternative slot timing offered by coordinator.
• P (Pending): Request pending coordinator technical evaluation.
• Z (Decline): Airline decline of coordinator offer.
• F (Historical): Slot protected under historical precedence (Grandfather Rights).
• H (Holding): Slot held under review status.
• W (Waitlist): Slot placed on waitlist for timing improvement.

---

🛠️ 5. Operating the AeroOps Slot Engine

The AeroOps Slot page features 3 integrated operational modes:

1️⃣ Extract & Analyze Mode

1. Paste Message: Paste raw message text or email content, or use Insert Mock Message... dropdown to pick pre-configured test scenarios.
2. Hover Tooltips Guide: Hover over any message type badge (SCR, SMA, SIR, SAQ, SHL, SAL, WCR...) to read instant simplified explanations.
3. Click "Analyze & Extract Data":
   • Parses the message string into structured fields instantly.
   • Computes minimum turnaround times (MCT) and warns against turnaround violations.
   • Evaluates Grandfather Rights and 80/20 compliance rules.
   • Generates official coordinator response templates.

2️⃣ Manual Route Builder Mode

• Generates 100% compliant IATA SCR syntax as you fill in flight parameters.
• Supports multi-segment routing, turnaround validation, and 1-click dispatch to Radar Simulator.

3️⃣ Historical & JNUS Archive Mode

• Archive and audit historical slot allocations across seasons (S25, W25, S26).
• Seamless integration with FIDS engine and airport master schedule.

---

🔘 6. Interactive Controls & Buttons Guide

The AeroOps Slot Coordinator interface provides granular, rapid control across all phases of the message lifecycle:

🎛️ Analysis & Input Controls

• 📝 Insert Mock Message...: Dropdown menu allowing instant insertion of realistic, industry-standard test telegrams (Turnaround flights, Retiming requests, Cargo, General Aviation) for immediate verification and sandbox evaluation.
• 🧹 Clear Text: Clears the input box to start a fresh parsing session.
• ⚡ Extract & Analyze: Triggers the intelligent aviation parser; reads SSIM lines, matches clearance airport codes, verifies Turnaround Minimum Connect Time (MCT), and evaluates IATA WASG rules.
• 📋 Copy Formatted: Copies the formatted, IATA-compliant message string to clipboard for dispatch via email or SITA/AFTN telex.
• 📡 Send to Radar Simulator: Direct bridge dispatching parsed flight legs into the interactive Radar Simulator for live visual flight tracking.

🚀 Action Toolbar (Sync, Save & Export)

• ☁️ Save to Cloud: Uploads the entire analyzed message with all its segments to the central Supabase cloud database linked by a unique batch ID (message_ref_id), establishing official coordination records.
• 🔄 Sync to Master: Decompresses and explodes the message segments into individual calendar flights, injecting them immediately into the local OCC Live Schedule for apron stand allocation and ground ops.
• 📊 Export to Excel: Generates a structured .xlsx spreadsheet detailing flight dates, flight numbers, turnaround times, and seat capacities.
• ✉️ Generate Coordinator Reply: Formats the official IATA response message (K for confirmed slots, U for unavailable capacity, or O for retimed offers) ready for airline notification.

🗄️ Recent Analysis History Table Controls

• 🔵 Local Database (IndexedDB): Displays slot records cached locally inside your browser. An offline-first, completely isolated safety sandbox.
• 🔘 Cloud (Supabase): Switches to view official enterprise slot records stored on the central database shared across the airport coordination team.
• 🗑️ Clear All History: Clears the active history list.
• ➕ Select (+): Checkbox selector for batch processing or group export.
• 🟢 Approve: Approves the slot request (APPROVED), triggers flight explosion, and propagates scheduled flight records.
• 🔴 Reject: Declines the slot request (REJECTED) and marks it as unauthorized for operations.
• 🔄 Load: Re-loads the historical record and its raw message back into the top analysis workbench for revisions, reply generation, or cloud promotion.
• 🗑️ Delete Icon: Permanently removes the selected record from the archive.

---

🧠 7. Dual Storage Architecture & Flight Explosion (Local vs. Cloud)

AeroOps implements an enterprise-grade military-isolated architecture balancing Personal Sandbox Freedom with Centralized Production Integrity:

💥 1. What is "Flight Explosion" (Slot Expansion)?

In IATA SCR messaging, airlines provide condensed seasonal schedule strings:

NMS2333 MS0777 05SEP04DEC 1234567 320180 LHR2145 2345LHR JJ

• The Challenge: Apron controllers, stand assignment engines, and NOTAM conflict detectors cannot operate on date ranges; they need individual flights on specific calendar dates.
• The Explosion: AeroOps algorithms explode this single seasonal rule into hundreds of distinct daily flight instances with exact ISO timestamps. Multi-segment messages with dozens of legs are expanded concurrently without dropping any sector.

🛡️ 2. Local Database vs. Cloud Database: Why the Air-Gap?

• 💻 Local Database (IndexedDB):
  • Your personal Safety Sandbox.
  • Operates 100% offline.
  • Air-gapped isolation ensures coordinators can stress-test heavy aircraft (e.g. A380s) and simulate complex timetables without polluting live production systems.
• ☁️ Cloud Database (Supabase):
  • The airport's Official Production OCC.
  • Real-time synchronization across all dispatchers, coordinators, and apron managers via WebSockets.

⚖️ 3. Approval Behavior: Cloud vs. Local

| Aspect | Approved in Cloud (Supabase) | Approved in Local (IndexedDB) | | :--- | :--- | :--- | | Slot History Status | Marked APPROVED centrally on the server. | Marked APPROVED only inside your local browser. | | OCC Live Flights | Exploded flights injected into live database for all users. | Exploded flights stored only inside your local session. | | Cloud Impact | Persisted to official flight_records table. | Zero cloud impact; completely isolated. | | Live Broadcast | Realtime broadcast to all connected team members. | No broadcast; stays strictly on your workstation. |

👑 4. Single Source of Truth & Conflict Resolution

[!IMPORTANT] The Cloud is Always the Supreme Source of Truth:

• If you reject a flight locally but approve it on the cloud: Once online, OCC synchronizes with the server, overriding your local rejection and activating the flight as officially confirmed.
• When does Local prevail? Exclusively during catastrophic internet outages (Offline Fallback), allowing airport operations to proceed uninterrupted from local IndexedDB storage until connectivity is restored.

🔄 5. Promoting a Local Record to Cloud

To promote a tested local slot into an official cloud schedule:

1. Click the teal Load button on the flight row in the Local Database tab.
2. The complete message loads into the active analysis workbench.
3. Click the blue Save to Cloud button.
4. The slot is committed to the cloud and is now ready for enterprise approval and airport-wide broadcast.

---

💡 Operational Tip: Always verify that the Clearance Airport in the message header matches the active airport selected in your OCC header; AeroOps segregates schedules by ICAO/IATA station code to guarantee operational separation.