FEATURE: ATO-Generator

[132ndNeck]

Is there a way to create a ATO-generator? Either tied to the new website (preferred) or stand-alone.

Features:

• Mission Host/event Host (AOC) should have a setting where they can assign a percentage of missions to be generated
• Missions: CAP, SWEEP, ESCORT, SEAD, DEAD, CAS, AR, SCAR, FAC(A), AI, STRIKE, CASEVAC, AIR ASSAULT, AERIAL DELIVERY, CSAR, BDA, RECON
• A easy way for mission host/event hosts to add mission to an excisting ATO (from missions above)
• ATO lasts 24 hours (0000Z-2359Z), and is published 72 hours before the ATO day.
• ATO is tied to target list, and AAR after other missions/ATO days (ADD FEATURE REQUEST ON TARGET LIST + AAR with INTEL and BDA assessment)
• ATO generates automaticly a ACO (Airspace Control Order), which activates airspace for the taskings that are active
• A userfriendly interface and easy readability for the ATO. Clear distinction on flights with personell (flights that are flown) and flights that are on the ATO but not currently manned.
• A easy way for pilots to create ad-hoc taskings (select area, and mission).
• ATO tied into database that gives callsign, frequency, TACAN, Lasercode, datalink/SADL, IFF, etc (To ensure that no flights is using the same information)

STRIKE: Attack against any target on the target list, based on the status of the target (ADD FEATURE REQUEST ON TARGET LIST)

AR/CAS/SCAR/FAC(A): IF possible to have any sort of interaction with DCS, have a rule to indicate where AR/CAS/SCAR/FAC(A) missions should be conducted.

CAP: Supporting AR/CAS/SCAR/FAC(A) + AWACS and Tankers

SWEEP: In enemy territory, preferably as part of package operations, supporting a STRIKE (SWEEP, STRIKE+SEAD/DEAD)

SEAD/DEAD: Pre-planned against certain regions/threats. Or airborne alert

CASEVAC: Task for RW, adding a script to create CASEVAC situations close to friendlies (ADD FEATURE REQUEST ON CASEVAC SCRIPT)

AIR ASSAULT: Task for RW , package operation too insert infantry to take an objective behind enemy lines. Supported by CAS, CAP and SEAD.

BDA: Tied to status on other missions, to provide BDA if BDA is uncertain

CSAR: If aircraft is shot down, create a CSAR script for a CSAR situation. (ADD FEATURE REQUST ON CSAR Script)

AERIAL DELIVERY: Movement of cargo on the battlefield. Ammunition to artillery batteries. Ammunition to airfields/FARPs

[132ndNeck]

ATO generator need to be able to airspace deconfliction in a basic way, ensuring that not too many fligts are tasked into the same area.

ATO should be shown in the following way: It should show the ATO of the 24 hours we are in. This is flights tasked this day. Here a good seperation of "manned" flights, unmanned flights, and AI flights (AWACS and Tankers) should be present.

• Manned flights: Flights that have pilots assigned/signed up and will be flown by human pilots
• Unmanned flights: Flights that are planned, but where not pilots have signed up.
• AI flights: Any AI flights that is supporting the campaign.

The website should also view planned ATO's for the next 72 hours.

So at any time, a total of 4 ATO's is visible. The current one, and the 3 next planned ATO cycles. The ATO's in the future is then used for planning and signups for human pilots, and will contain the necessary information to plan, signup and coordinate the flights.

Anyone can create a new tasking to add to both the current ATO but also the future ATO's

[132ndNeck]

Some references: https://apps.dtic.mil/dtic/tr/fulltext/u2/a438397.pdf

[jkhoel]

I have created a project for this, and started creating issues in the web-page and web-backend repos.

[jkhoel]

From @132ndNeck on Discord: Overview with basic info

• There should be three of these, showing current ATO cycle, as well as the next two (3 in total)
• Should maybe see if it is possible to work a timeline into the overview as well

Detailed view of tasking Required fields etc. to the above Filled out example of Detailed view