Merge pull request #260 from vatpac-technology/tyler-dev

Added SOP for CPDLC Functionality with vatACARS

docs/controller-skills/cpdlc.md

@@ -0,0 +1,160 @@
+---
+title: CPDLC
+---
+
+--8<-- "includes/abbreviations.md"
+
+In the real world, CPDLC operations are generally used by aircraft within airspaces in Class A airspace above `F245`.
+
+CPDLC Functionality may also be used by pilots to request a PDC.    
+PDC's utilising vatACARS are initiated by the pilot however the standalone VATSYS functionality can be used in lieu of vatACARS without a pilot initated request.
+
+!!! Note
+    **CPDLC in it's enroute capacity should only be used by Enroute (C1) controllers or above.**
+
+    PDC's may be issued using the vatACARS Client by any controller.
+
+## Setup
+
+The vatACARS client can be downloaded by clicking [here](https://vatacars.com/).  
+
+The vatACARS client requires controllers to have a [Hoppies ACARS](https://www.hoppie.nl/acars/system/register.html) account and logon code, plus a [vatACARS Token](https://vatacars.com/me).
+
+If the client is installed correctly there will be an *ACARS* drop-down box available.
+
+<figure markdown>
+![vatACARS Dropdown](../controller-skills/img/vatacarsbar.png){ width="700" }
+</figure>
+
+## Pre Departure Clearance
+
+To utilise vatACARS for issuing PDC's, the controller must be logged into a VATPAC TCU, ADC, SMC or ACD position.
+
+After logging onto the network the controller should open the *Setup* window, fill in the relevent details and click *Save & Connect*
+
+<figure markdown>
+![vatACARS Setup](../controller-skills/img/vatacarslogon.png){ width="700" }
+</figure>
+
+**Station Code:** Must be the identifier of the airport which is being controlled.          
+**vatACARS Token:** Must be your unique vatACARS Token, found [Here](https://vatacars.com/me).          
+**Logon Code:** Must be your [Hoppies ACARS](https://www.hoppie.nl/acars/system/register.html) Code.            
+
+Controllers **MUST** note in their controller remarks section that PDC's are available in the format below.
+
+<figure markdown>
+![vatACARS Continfo](../controller-skills/img/vatacarscontinfo2.png){ width="700" }
+</figure>
+
+Once connected and with CPDLC enabled, pilots will connect to the vatACARS plugin via their aircraft's CPDLC system. The controller will normally recieve a *'Request PDC'* message through vatACARS.         
+The controller should left click their callsign to issue the PDC. A self explanitory window will appear, fill in the relevent data and send this back to the aicraft.       
+Once the aircraft has recieved their PDC, the pilot will usually respond with *'Roger'* or similar to show they have recieved the clearance. 
+
+<figure markdown>
+![vatACARS Setup](../controller-skills/img/vatacarspdc.png){ width="700" }
+</figure>
+
+!!! Note
+    If providing a Top-Down service as an enroute position, the pilots will be required to connect to the your Enroute Station Code. Eg: YISA, etc
+
+## Enroute
+
+To utilise CPDLC the controller must be logged into a VATPAC Enroute or Oceanic Position.
+
+**CPDLC (Expect for PDC's) must not be used below `F245`.**
+
+After logging onto the network the controller should open the *Setup* window, fill in the relevent details and click *Save & Connect*
+
+<figure markdown>
+![vatACARS Setup](../controller-skills/img/vatacarslogon.png){ width="700" }
+</figure>
+
+**Station Code:** Must be the identifier of the airport which is being controlled.          
+**vatACARS Token:** Must be your unique vatACARS Token, found [Here](https://vatacars.com/me).          
+**Logon Code:** Must be your [Hoppies ACARS](https://www.hoppie.nl/acars/system/register.html) Code.            
+
+Controllers **MUST** note in their controller remarks section that CPDLC is available in the format below.
+
+<figure markdown>
+![vatACARS Continfo](../controller-skills/img/vatacarscontinfo.png){ width="700" }
+</figure>
+
+Some major Enroute positions do not use CPDLC as a primary means of communication, however controllers may use CPDLC in lieu of voice when applicable.
+
+### Station Codes
+
+| Position | Station Code | Primary Communication Method |
+| --- | ---- | ----- |
+| ARL | YARL | Voice |
+| HWE | YHWE | **CPDLC** |
+| INL | YINL | Voice |
+| ISA | YISA | **CPDLC** |
+| KEN | YKEN | Voice |
+| TRT | YTRT | **CPDLC** |
+| ASP | YASP | **CPDLC** |
+| BIK | YBIK | Voice |
+| ELW | YELW | Voice |
+| HUO | YHUO | Voice |
+| OLW | YOLW | **CPDLC** |
+| PIY | YPIY | Voice |
+| TBD | YTBD | Voice |
+| YWE | YYWE | Voice |
+| TSN | YTSN | **CPDLC** |
+| FLD | YFLD | **CPDLC** |
+| IND | YIND | **CPDLC** |
+| NFFF | NFFF | **CPDLC** |
+| NZZO | NZZO | **CPDLC** |
+| KZAK | KZAK | **CPDLC** |
+
+!!! Note
+    If a non-standard subsector is online, the Station Code will be required to change to match the controlled subsector.
+
+### Accepting an Aircraft
+
+Once connected and with CPDLC enabled, pilots will connect to the vatACARS plugin via their aircraft's CPDLC system. The controller will normally recieve a *'Logon Request'* message through vatACARS.         
+The controller should left click their callsign to respond to this initial message and respond with a *'Accept Logon'*  to show the pilot that they have successfully connected. 
+
+<figure markdown>
+![vatACARS Setup](../controller-skills/img/vatacarsdispatch.png){ width="700" }
+</figure>
+
+This aircraft will now be automatically added to your Dispatch window to allow a controller ulilise their CPDLC.
+
+### Message Editor
+
+When either a pilot sends a request or ATC requires to send a message to the pilot, left clicking the callsign in the dispatch window will open the message editor.         
+This is used to select from a group of pre-coded messages to send back to the pilot.        
+
+<figure markdown>
+![vatACARS Setup](../controller-skills/img/vatacarseditor2.png){ width="700" }
+</figure>
+
+If the response to the pilot is not shown in this initial dispatch window, the controller should click the *Edit* button, this will bring the controller to a broarder range of messages to send to the pilot.
+
+<figure markdown>
+![vatACARS Setup](../controller-skills/img/vatacarseditor1.png){ width="700" }
+</figure>
+
+Left clicking the number next to the text box will change the line of text forward up to 5 different lines, Right clicking the number will go to the previous line. 
+
+### Handing over Aircraft
+
+#### ENR/OCN
+
+When transferring between Enroute or Oceanic sectors, ATC will right click on the aircraft which will bring up a handover window. The controller should select the next ATC unit the aircraft is going, this will transfer the aircraft through CPDLC to the next ATC unit.
+
+<figure markdown>
+![vatACARS Setup](../controller-skills/img/vatacarshandoff.png){ width="700" }
+</figure>
+
+#### ENR/TCU
+
+Standard Voice frequency transfers must be used for aircraft below `F245` and between ENR to TCU Positions. 
+
+### Terminating CPDLC
+
+If CPDLC is no longer available or required, ATC will right click on the aircraft which will bring up a logoff window. By clicking *'LOGOFF'* the aircraft will be sent a Logoff message.
+
+<figure markdown>
+![vatACARS Setup](../controller-skills/img/vatacarshandoff.png){ width="700" }
+</figure>

docs/enroute/Brisbane Centre/ARL.md

@@ -15,6 +15,18 @@
 | Ocean† | Brisbane Centre | 128.600 | BN-OCN_CTR |
 
 † *Non-standard positions* may only be used in accordance with [VATPAC Air Traffic Services Policy](https://vatpac.org/publications/policies)
+
+### CPDLC
+
+The Primary Communication Method for ARL is Voice.
+
+[CPDLC](../../controller-skills/cpdlc.md) may be used in lieu when applicable.
+
+The CPDLC Station Code is `YARL`.
+
+!!! tip
+        Even though ARL's Primary Communication Method is Voice, CPDLC may be used for Overfliers.
+
 ## Airspace
 
 <figure markdown>

docs/enroute/Brisbane Centre/HWE.md

@@ -9,6 +9,14 @@
 | ---- | -------- | --------- | -------- |
 | Howe | Brisbane Centre | 124.950 | BN-HWE_CTR |
 
+### CPDLC
+
+The Primary Communication Method for HWE is [CPDLC](../../controller-skills/cpdlc.md).
+
+The CPDLC Station Code is `YHWE`.
+
+Voice may be used in lieu when applicable.
+
 ## Airspace
 
 <figure markdown>

docs/enroute/Brisbane Centre/INL.md

@@ -17,6 +17,18 @@
 
 † *Non-standard positions* may only be used in accordance with [VATPAC Air Traffic Services Policy](https://vatpac.org/publications/policies)
 
+### CPDLC
+
+The Primary Communication Method for INL is Voice.
+
+[CPDLC](../../controller-skills/cpdlc.md) may be used in lieu when applicable.
+
+The CPDLC Station Code is `YINL`.
+
+!!! tip
+        Even though INL's Primary Communication Method is Voice, CPDLC may be used for Overfliers.
+
+
 ## Airspace
 
 <figure markdown>

docs/enroute/Brisbane Centre/ISA.md

@@ -16,6 +16,14 @@
 
 † *Non-standard positions* may only be used in accordance with [VATPAC Air Traffic Services Policy](https://vatpac.org/publications/policies){target=new}
 
+### CPDLC
+
+The Primary Communication Method for ISA is [CPDLC](../../controller-skills/cpdlc.md).
+
+The CPDLC Station Code is `YISA`.
+
+Voice may be used in lieu when applicable.
+
 ## Airspace
 
 <figure markdown>

docs/enroute/Brisbane Centre/KEN.md

@@ -15,6 +15,17 @@
 
 † *Non-standard positions* may only be used in accordance with [VATPAC Air Traffic Services Policy](https://vatpac.org/publications/policies)
 
+### CPDLC
+
+The Primary Communication Method for KEN is Voice.
+
+[CPDLC](../../controller-skills/cpdlc.md) may be used in lieu when applicable.
+
+The CPDLC Station Code is `YKEN`.
+
+!!! tip
+        Even though KEN's Primary Communication Method is Voice, CPDLC may be used for Overfliers.
+
 ## Airspace
 
 <figure markdown>

docs/enroute/Brisbane Centre/TRT.md

@@ -12,6 +12,14 @@
 
 † *Non-standard positions* may only be used in accordance with [VATPAC Air Traffic Services Policy](https://vatpac.org/publications/policies)
 
+### CPDLC
+
+The Primary Communication Method for ISA is [CPDLC](../../controller-skills/cpdlc.md).
+
+The CPDLC Station Code is `YISA`.
+
+Voice may be used in lieu when applicable.
+
 ## Airspace
 
 <figure markdown>

docs/enroute/Melbourne Centre/ASP.md

@@ -17,6 +17,14 @@
 
 † *Non-standard positions* may only be used in accordance with [VATPAC Air Traffic Services Policy](https://vatpac.org/publications/policies){target=new}
 
+### CPDLC
+
+The Primary Communication Method for ASP is [CPDLC](../../controller-skills/cpdlc.md).
+
+The CPDLC Station Code is `YASP`.
+
+Voice may be used in lieu when applicable.
+
 ## Airspace
 
 <figure markdown>

docs/enroute/Melbourne Centre/BIK.md

@@ -13,6 +13,17 @@
 
 † *Non-standard positions* may only be used in accordance with [VATPAC Air Traffic Services Policy](https://vatpac.org/publications/policies)
 
+### CPDLC
+
+The Primary Communication Method for BIK is Voice.
+
+[CPDLC](../../controller-skills/cpdlc.md) may be used in lieu when applicable.
+
+The CPDLC Station Code is `YBIK`.
+
+!!! tip
+        Even though BIK's Primary Communication Method is Voice, CPDLC may be used for Overfliers.
+
 ## Airspace
 
 <figure markdown>

docs/enroute/Melbourne Centre/ELW.md

@@ -13,6 +13,17 @@
 
 † *Non-standard positions* may only be used in accordance with [VATPAC Air Traffic Services Policy](https://vatpac.org/publications/policies)
 
+### CPDLC
+
+The Primary Communication Method for ELW is Voice.
+
+[CPDLC](../../controller-skills/cpdlc.md) may be used in lieu when applicable.
+
+The CPDLC Station Code is `YELW`.
+
+!!! tip
+        Even though ELW's Primary Communication Method is Voice, CPDLC may be used for Overfliers.
+
 ## Airspace
 
 <figure markdown>

docs/enroute/Melbourne Centre/HUO.md

@@ -9,6 +9,17 @@
 | ---- | -------- | --------- | -------- |
 | Huon | Melbourne Centre | 122.600 | ML-HUO_CTR |
 
+### CPDLC
+
+The Primary Communication Method for HUO is Voice.
+
+[CPDLC](../../controller-skills/cpdlc.md) may be used in lieu when applicable.
+
+The CPDLC Station Code is `YHUO`.
+
+!!! tip
+        Even though HUO's Primary Communication Method is Voice, CPDLC may be used for Overfliers.
+
 ## Airspace
 
 <figure markdown>

docs/enroute/Melbourne Centre/OLW.md

@@ -16,6 +16,15 @@
 | Menzies† | Melbourne Centre | 134.300 | ML-MZI_CTR |
 
 † *Non-standard positions* may only be used in accordance with [VATPAC Air Traffic Services Policy](https://vatpac.org/publications/policies)
+
+### CPDLC
+
+The Primary Communication Method for OLW is [CPDLC](../../controller-skills/cpdlc.md).
+
+The CPDLC Station Code is `YOLW`.
+
+Voice may be used in lieu when applicable.
+
 ## Airspace
 
 <figure markdown>

docs/enroute/Melbourne Centre/PIY.md

@@ -16,6 +16,18 @@
 | Geraldton† | Melbourne Centre | 134.200 | ML-GEL_CTR |
 
 † *Non-standard positions* may only be used in accordance with [VATPAC Air Traffic Services Policy](https://vatpac.org/publications/policies)
+
+### CPDLC
+
+The Primary Communication Method for ELW is Voice.
+
+[CPDLC](../../controller-skills/cpdlc.md) may be used in lieu when applicable.
+
+The CPDLC Station Code is `YPIY`.
+
+!!! tip
+        Even though PIY's Primary Communication Method is Voice, CPDLC may be used for Overfliers.
+
 ## Airspace
 <figure markdown>
 ![Pingelly Airspace](../assets/piy.png){ width="700" }

docs/enroute/Melbourne Centre/TBD.md

@@ -12,6 +12,17 @@
 
 † *Non-standard positions* may only be used in accordance with [VATPAC Air Traffic Services Policy](https://vatpac.org/publications/policies)
 
+### CPDLC
+
+The Primary Communication Method for TBD is Voice.
+
+[CPDLC](../../controller-skills/cpdlc.md) may be used in lieu when applicable.
+
+The CPDLC Station Code is `YTBD`.
+
+!!! tip
+        Even though TBD's Primary Communication Method is Voice, CPDLC may be used for Overfliers.
+
 ## Airspace
 
 <figure markdown>