Guide ATO

Avatar de l’utilisateur

Topic author
Kima
Pilote Philanthrope
Pilote Philanthrope
Messages : 506
Inscription : 02 juin 2020

Guide ATO

#1

Message par Kima »

Comme vous l'avez vu dans les briefings pour Persian Gulf, j'essaie d'aménager les Air Task Order (ATO) utilisés par l'OTAN dans un format adapté à nos besoins

Je me suis inspiré pour cela du travail réalisé par GOSLIN de la VBF-12 ( https://vbf12.proboards.com/thread/2805 ... task-order ) et nous allons la faire évoluer encore.

L'idée est de reproduire le côté ops de ces messages, tout en permettant au joueur d'utiliser la machine/armement/stratégie de son choix

Par exemple, dans un champ appelant une quantité d'appareils d'un type précis, je n'indiquerai que FW (avion) ou RW (hélico). Pareil pour l'armement, le nombre d'appareils, ...

Je vous mets dans le post suivant un premier jet de ce guide, histoire de se plonger dedans. Un autre support que le forum sera peut-être mis en place à l'avenir (ou pas)

Edit: C'est un copié-collé d'un document plus propre en PDF ;)
Avatar de l’utilisateur

Topic author
Kima
Pilote Philanthrope
Pilote Philanthrope
Messages : 506
Inscription : 02 juin 2020

Re: Guide ATO

#2

Message par Kima »

Guide des ATO (Air Tasking Orders)

Les ATO sont des messages utilisés par les forces de l’OTAN qui renseignent sur les ordres de mission à venir. Ces missions sont planifiées avec en tête la coordination des différents éléments. Les ATO réels sont émis pour le jour suivant, ce qui permet aux équipages de briefer leur mission du lendemain. A l’EVM, ils seront listés de façon permanente, tel un catalogue, et accompagnés des informations supplémentaires telles que le briefing des services de renseignement (Intel) qui renseignent sur la cible et les menaces, ou encore la météo.

La partie ATO est la partie formelle dans laquelle l’équipage trouvera les détails sur la façon dont va se dérouler la mission. Un ATO est un message militaire abbrégé pour le rendre efficace.

Dans le cadre de notre activité simulée et pour garantir la jouabilité, la Wing Support se permet de modifier le format OTAN pour l’adapter au jeu, d’ajouter des codes, ou d’étendre les informations et consignes pour que le joueur vive la meilleure expérience possible, dans une ambiance opérationnelle.

La Wing Support de l’EVM veut laisser aux joueurs présents la liberté de choisir ce qu’ils veulent faire. Les briefings de missions sont donc là pour permettre aux joueurs de comprendre l’objectif ainsi que d’appréhander la difficulté de celle-ci.

Dans ce catalogue, nous ne prenons pas en compte la coordination des flights, n’imposons pas l’armement ou les callsigns, et restons volontairement dans une description simpliste à un flight pour que la mission soit jouable par une seule patrouille.

Des ATO émis pour des événements spécifiques pourront comprendre plusieurs blocs et des instructions spécifiques à chaque flight, mais cela sort du cadre du catalogue standard et fera l’objet d’un ATO séparé.


Voici un guide de décryptage des messages ATO, repris de Gosling (VBF12), traduit et adapté.

Un ATO (Air Task Order) comprend plusieurs blocs d’information:

- Un en-tête, comprenant les informations liées à la classification de l’ATO
- Des corps de messages (blocs). Il y en a un pour chaque mission (chaque package).

Le contenu de ces blocs est divisé en groupes, représentant une catégorie d’information. Le contenu d’un groupe comprend plusieurs informations, séparées par une barre oblique / Par souci de clarté dans ce document les barres obliques sont séparées par un espace. Ces informations sont écrites en majuscules. Les groupes se terminent par une double barre oblique //. Certains champs sont obligatoires et d’autres, en fin de ligne, n’apparaissent qu’en cas de besoin. Les champs vides apparaissent avec un tiret -. La longueur d’un groupe n’est pas limité mais devrait pas dépasser deux lignes.

Détaillons l’en-tête :
    EXER / exercise name / additional identifier //
    or
    OPER / operation name / plan originator and number / option name / second option name //
    MSGID / ATO classification* / originator / message serial number / month / qualifier / qualifier serial number //
    REF / serial letter / (usmtf message short title) or (type of reference) / originator / date-time group / (msg ser number) / special notation / (sic) or (filing number) //
    AMPN / free text to explain preceding reference set//
    NARR / free text to explain preceding reference set//
    PERID / FM: time from / TO: time to / ASOF: as of time //
    AIRTASK / air tasking / air tasking comments //

    * ATO classification :
    COSMIC - Squadron Command Only
    TS - Top Secret - Squadron Command and Command of Associated Squadrons for that event Only
    SEC - Secret - Squadron Members Only
    CONF - Confidential - Squadron Members and Squadrons working together
    REST - Restricted - Any DCS Players
    UC - Public

    Le corps du message (les champs soulignés sont obligatoires). Les champs seront détaillés plus bas :

    TASKUNIT - Unit tasked with the following mission
    MSNDAT - Mission Basic Data

    MSNLOC - Mission Location
    TGTLOC - Target Location
    RECDAT - Reconnisance Data
    So each mission has one of MSNLOC, TGTLOC or RECDATA

    Other Sets may include any or all of the following. This is an incomplete list.
    TRCPLOT - Trace Plot information
    CONTROL - Flight Safety and Fighter Controllers - The Air Traffic Controllers normally in the AWACS
    FACINFO - Forward Air Controller information
    ELECMBT - Electronic Combat Support Information
    REFUEL - Details of the Tanker
    AMPN - Amplifying Remarks

    Detail des corps de message :

    TASKUNIT - TASKED UNIT - Unit tasked with the following mission
    TASKUNIT / The tasked unit designator / ICAO location / comments //

    MSNDAT - The MiSsioN DATa Set is the basic data for aircraft to be allocated to the mission.
    Format
    MSNDAT / mission number / package identification / aircraft call sign / number and type aircraft / mission type / alert status / primary configuration code / secondary configuration code / iff-sif code and mode //
    MSNDAT / MSNNO / PKG / CALLSIGN / n ACFT / MSN / ALRT / SCL1 / SCL2 / SIF1 / SIF2 // - Spaces have been added for clarity
    Example
    MSNDAT / 1630 / A / SKYBOLT5-1 / 2F18C / SEAD / AL15 / 4A881 / - / 25541 / 43441 //

    Abbreviations :
    ACFT - Aircraft
    CALLSIGN - Callsign of leader. The rest of the aircraft follow on. The next package needs to take into account the number of aircraft in the previous package. So our next package is SKYBOLT5-3 or SKYBOLT6-1. It cannot be SKYBOLT5-2 as that has been used.
    ALRT - Alert State - Aircraft have defined alert states like; AL0 (Airborne), AL5 (5 mins to launch), AL15 (15 mins to launch), etc
    MSN - Mission Type (SEAD - Suppression of Enemy Air Defence)
    MSNNO - Mission Number - Starts with the date that the ATO applies to. There is one ATO issued a day for tomorrow.
    PKG - Package (Grouping of aircraft prior to conducting specific mission I think - these seem to be just letters “A”
    SCL - Standard Combat Load - What the Aircraft will be armed with. These are defined in our Standard Combat Load Thread to be added - 4A881 = 4 x AGM88C + 1 x Centreline Tank
    - = Field not used
    SIF - Successor Identification Friend or Foe - Modern burst transmission IFF that is much more secure than Civilian IFF. IFF is not functional yet

    MSNLOC - MiSsioN LOCation. This would be for a mission like a Combat Air Patrol (CAP) or a Tanker mission where the mission requires the aircraft to be airborne and available for a period of time.
    Format
    MSNLOC / mission start day-time / mission stop day-time / mission location name / (altitude) or (flight level) / air support request number / area coordinates //
    MSNLOC / TOS / TFS / MSNLOC / ALT / REQNO / AREA COORD //
    Example
    MSNLOC / 161500Z / 161900Z / N5434.00E02245.50 / 27000 / 2 / As Directed //

    Abbreviations
    TOS = Time On Station = Start of period on station - Format: ddhhmmz
    TFS = Time Off Station = End of period on Station - Format: ddhhmmz
    MSNLOC = Mission Location - Format N/S nnnn.nn E/Wnnnnn.nn (degs, mins, secs for input)
    ALT = Altitude of the station in feet or Flight Level
    REQNO = No. of aircraft request number - This is a reference to the Air support request that caused this mission to be generated
    AREA COORD = Area Coordinates or As Directed

    TGTLOC - TarGeT LOCation. This defines a location for the aircraft to execute its mission. This might be a strike or resupply or evacuation etc. I think the example from the first post might be confusing as it seemed to have errors The format we will use is:
    TGTLOC / day-time on target / day-time off target / target identifier / target type / desired mean point of impact / air support request number / target comments //
    TGTLOC / TOT / TFT / TGTID / TGT TYPE / DMPI / REQNO / RMKS //
    Example
    TGTLOC / 161600Z / 161604Z / A004 / SA-10 / N5427.00 E02223.56 / ?-? / - //

    Abbreviations
    TOT = Time On Target - ddhhmmz
    TFT = Time Off Target - ddhhmmz - Four min window for a strike
    TGTID = Target Identification from a Target List
    TGT TYPE = Description of Target, more in RMKS if reqd
    DMPI = Desired Mean Point of Impact - Lat/Lon or grid
    REQNO = Request Number - Reference to the Air Support Request that caused this target to get on the Target List and so generate this mission.
    RMKS = Amplifying remarks.

    RECDAT - RECONNAISSANCE DATA. We can see using this to get target images and have them in as links. In the example at the top the format is:
    RECDATA / request number / mission priority / day-time on target / latest time information of value / reconnaissance mission type //
    Additional items as below:
    RECDAT / REQNO / PRIORITY / TOT / LTIOV / MSN TYPE / TYPE RECON / IMAG TYPE / IMAG QUAL / COVRG EXT / TGT CODES / SCALE / DELIV TO //
    Example
    RECDAT / R001 / 4HR / 161600Z / 161500Z / CAS / PHOT / THERM / 8 / R2 / SA-10 / 1:25000 / VAQ-131 //

    Abbreviations
    REQNO = Request No.
    PRIORITY = Priority against other Recon tasks I suspect
    TOT = TIme on Target of the Strike I think giving the Recon guys the window to get the required recon to the Strike package
    LTIOV = Latest Time Information Of Value
    MSN TYPE = Type of Mission to be executed using the recon
    TYPE RECON = The type of information required, Phots, terrain, etc
    IMAG TYPE = Not sure of the options. IR, VIS, RDR, SAR (Synthetic Aperture Radar), ISAR (Inverse Synthetic Aperture Radar)
    IMAG QUAL = Image quality 0 - 9. NIIRS (National Image Interpretability Rating Scales)
    COVRG EXT = Coverage Extent as a Radius, Width or Ellipse in nm
    TGT CODES = Probably the codes of the mission going to strike it. Still, we can use this as the target
    SCALE = Again there is probably a standard but we can use standard map scales.
    DELIV TO = Delivery of the recon to a unit that will be conducting the mission - In our case this will be a link

    TRCPLOT - TRACE PLOT. The set seems to be associated with a RECDAT as it appears to describe the start and finish point of a trace. This might be a photo, a SAR, an ISAR scan, etc. Not sure what the track plot is all about and I am trying to find out, I’ll get back to you on this one.
    Format
    TRCPLOT / location of initial point / type area / tracepoint location //
    TRCPLOT / TRCID / Radius or Width or Ellipse / Corridor //
    Example
    TRCPLOT / TR01 / E / 2 /

    Abbreviations
    TRCPLOT = Trace Plot
    TRCID = Trace Identification Number
    R or W or E = Radius or Width or Ellipse
    CORRIDOR = Width of trace in nautical miles

    CONTROL - AIR TRAFFIC CONTROL will be available during the operation. Often this is very standard and would be in a reference. There are two general sets of services. Air Traffic and Operational.
    The Air traffic Ones are:
    Basic Service - Just an information service
    Traffic Service - Where the controller will warn you of other traffic
    Deconfliction Service - Where the controller will give you avoiding action if you are not visual with opposing traffic
    Procedural Service - Where you must follow the controller's instructions but he can't see you and thus relies on your reported positions
    Radar Control - The controller can see you on radar and you must follow his instructions
    The Operational ones are :
    Broadcast - Information services like Air Safety
    Loose Control - Where you have the freedom to maneuver as required but the controller gives you instructions
    Close Control - Where the controller will give you instructions you should follow
    Format:
    CONTROL / type of control / callsign / (primary frequency) or (primary frequency designator) / (secondary frequency) or (secondary frequency designator) / report-in point / control comments //
    Example
    CONTROL / BROADCAST / EAGLE / 125.275 / 135.275 / AIRBORNE / - //

    FACINFO - FORWARD AIR CONTROLLER INFORMATION - This Set provides information on the Forward Air Controller to contact for detailed target information running in to strike.
    Format
    FACINFO / call sign / primary (frequency) or (frequency designator) / secondary (frequency) or (frequency designator) / report- in point / support unit identity / control comments //
    Example
    FACINFO / FINGER22 / 119.255 / 244.125 / 10NM TO IP / HS-4 / - //

    ELECMBT - ELECTRONIC COMBAT INFORMATION - This is very much a VAQ-131 think once we get jammers etc.... The format below seems a bit limited as it does not describe the types of Electronic Combat... Also, I’m not sure what the priority is for...
    Format
    ELECMBT / aircraft call sign / priority / mission location / (altitude) or (flight level) / time on station / time off station / primary (frequency) or (frequency designator) / secondary (frequency) or (frequency designator) //
    Example
    ELECMBT / SKYBOLT5-1 / ?-? / N50240W002269 / FL20 / 161200R / 161500R / 125.275 / 200.225 //

    Abbreviations
    FL = Flight Level

    REFUEL - REFUEL INFORMATION - Now here is an important set. Burned up a bit much over the target. The need to take a short stop at the tanker should always be available.
    Format
    REFUEL / tanker call sign / tanker mission number / air refueling control point / (altitude) or (flight level) / air refueling control time / total off-load of fuel / (primary frequency) or (frequency designator) / secondary (frequency) or (frequency designator) //
    Example
    REFUEL / TEXACO9-1 / F001 / N443100E0221515 / FL230 / 162300R / 248000G / 124.225 / 134.225 //

    Abbreviations
    ARCP = Air Refueling Control Point. - The geographic point where the receiver arrives in the pre-contact position with respect to the tanker
    ARCT = Air Refueling Control Time - The time the receiver and tanker arrive at the air refueling control point.
    FL = Flight Level
    Répondre

    Revenir à « Wing Support »