Project Basics in DCS AOC Tools
After creating a project in DCS AOC Tools, a few essential operations must be completed before the project can be fully used for operational planning and documentation.
The project setup is based on three mandatory steps: uploading the DCS World mission file, configuring the ATO Header, and creating and assigning missions to Task Units.
Once these steps have been completed, additional sections can be configured to expand the operational planning capabilities of the project.
1. Upload or Update the Mission File (.miz)
The DCS World .miz file is the operational source of the project. An initial mission file is uploaded when the project is created, but an updated .miz file can also be uploaded from the Project Dashboard.
DCS AOC Tools uses the mission file to extract the information available in the DCS World mission. This information provides the initial data used throughout the project, including aircraft, groups, waypoints, mission information and other elements configured in the DCS World Mission Editor.
For this reason, the mission should be prepared correctly in the DCS World Mission Editor before being imported into DCS AOC Tools. The dedicated Mission Editor guides explain how to configure mission elements so that the maximum amount of useful information can be extracted from the .miz file.
2. Configure the Air Tasking Order (ATO) Header
The ATO Header defines the general and administrative parameters of the Air Tasking Order and is a prerequisite for processing the project's operational data.
Configuring the ATO Header is therefore the foundational step of the project setup. Once the header has been configured, the ATO can be processed and the project can be populated with the mission information required for the subsequent planning stages.
The ATO Header establishes the general operational context used by the Air Tasking Order and its associated mission data.
3. Create and Assign Missions to Task Units
After the mission data has been imported and the ATO Header configured, missions can be organized into Task Units.
Task Units are used to organize the order of battle and provide the structure required for operational planning and flight-related calculations.
At present, only missions that belong to a Task Unit and have the status "Tasked" on the Missions page are included in the ATO.
Correctly assigning missions to Task Units is therefore essential if they are to appear in the generated Air Tasking Order.
Optional Project Configuration
After completing the mandatory project setup, additional sections can be configured to provide more complete operational planning and documentation.
- Airspace Control Order (ACO): Create and manage airspace control measures such as restricted areas, corridors and other airspace elements.
- Special Instructions (SPINS): Define special instructions and operational information for the mission.
- Comm Plan: Configure radio communication plans, frequencies and callsigns, and manage Challenge and Reply tables.
- Personnel Management: Assign personnel to specific operational roles, missions and functions such as ATC and AWACS.
- Reset Transponders and Laser Codes: Generate new IFF transponder and laser codes for the selected coalition as part of the mission preparation process.
- Joint Integrated Prioritized Target List (JIPTL): Associate a prioritized target list with the project for the selected coalition.
Project Configuration Workflow
The recommended basic workflow is therefore:
- Upload the current DCS World
.mizmission file. - Configure the ATO Header.
- Create and organize Task Units.
- Assign missions to the appropriate Task Units.
- Set the required missions to Tasked status.
- Configure optional sections such as ACO, SPINS, Comm Plan, Personnel Management and JIPTL as required.
Once the mandatory configuration is complete, the project provides the foundation for preparing the operational products used by the mission planners and participants of a DCS World operation.