[Back]

[Index]

[Next]
Air Operations Center (AOC) Standard Operating Procedure (SOP)
Twelfth Air Force (12AF) Air Force Forces (AFFOR)

 

ANNEX E TO CHAPTER 3

CHIEF ATO PRODUCTION

 

1. GENERAL The Chief of ATO Production is responsible for translating the MAAP into an executable ATO. ATO Production completes the ATO during the last 12 hours of the planning cycle. This process is continued on a daily basis. The night shift will begin the ATO build until relieved by the day shift. ATO Production is responsible for completing, reviewing and transmitting the final ATO that is usually distributed before 1800L.

2. RESPONSIBILITIES.

A. To successfully build the daily ATO, the Chief, ATO Production must thoroughly understand the JFC's guidance/apportionment/intent and successfully gather unit data, theater communications and airspace control plan. In addition, he must keep track of how the night ATO planners intend to meet the JFCs objectives. After the MAAP is built, the ATO planners will use the automated or manual system as appropriate to input the planning data. For major contingencies, ATO Production will use Contingency Theater Automated Planning System (CTAPS) with Automated Planning System (APS) as the primary planning tool and Computer Assisted Force Management System (CAFMS) will be used as a secondary manual backup to APS, until CAFMS goes away with the release of CTAPS 5.2. The Chief, ATO Production monitors the process of the daily planning and data entries via the mission line summary worksheet, package summary worksheet and the display sortie flow worksheet. Part of this process occurs during the shift change brief which includes the following information from the off-going Chief of Campaign Plans:

(1). Units, bases, aircraft types, numbers of aircraft, Standard Conventional Loads (SCLs) and the sortie utilization rate used to create the MAAP

(2). The final cut line on the JIPTL from the MAAP

(3). Army update on schedule of maneuver, probable FSCL, priority of effort and distribution of CAS sorties

(4). Any logistical LlMFACs from the LRC, i.e., shortage of AGM-65s

(5). Any SOF activity/No Strike areas near assigned targets within the ATO

(6). Any airspace control means that will impact the ATO

(7). How goes it from the Combat Ops perspective

(8). Any last minute Intel assessment of enemy COA and BDA from previous strikes

B. ATO Production is responsible for acquiring and maintaining the following data for ATO planning:

- Unit identifiers

- Home and staging bases

-- ICAO indentifiers

-- latitude, longitude and elevation

- Aircraft types and performance characteristics

- Numbers of aircraft

- Sortie utilization rate (sustained and surge)

- Plain language addresses (PLAs) for AUTODIN transmission

- Standard Conventional Loads (SCLs)

- Comm data

-- callwords for units or aircraft and control agencies

-- frequencies for aircraft and control agencies

C. The Assistant Chief of ATO Production and the NCOIC of ATO Production, report to the Chief of

ATO Production

3. The Chief, ATO Production ensures that augmentees and assigned planners are briefed on their duties in order to complete the building of the ATO.

A. The Chief ATO Production reviews the approved JIPTL and the weaponeering data from the Target Nomination List (TNL) in order to become familiar with the information being placed upon the MAAP/ATO worksheets. Each planner reviews the work done for each unit/mission for which they are responsible. Information provided includes: unit, type and number aircraft, call sign, base, UTE rate, ASD, projected total sorties, turn time, expanded target information (location information) to accompany the target numbers, mission commanders, and EC/AR/escort requirements. The JIPTL review insures that proper targets were identified and entered correctly in the present ATO. There may be cases where it is required to bypass some targets higher on the TNL and hit some lower priority ones because of location, lack of assets to complete the job, etc.

B. Packages/ missions developed by Campaign Plans, usually will hit numerous targets within the same area. This gets the greatest synergy out of limited force enhancement assets. Planning will continue until the ATO is completed.

C. Once all missions are input, mission planners will check missions for accuracy and the ATO will be transferred from APS to CAFMS Plans within CTAPS. After Transfer, the ATO mission data will be rechecked by all mission planners for accuracy.

D. When the mission data within the ATO is complete and accurate, and the General Remarks (SPINS), the ACO, the theater and strategic airlift mission data (Air Movement Schedule - AMS) have been loaded into the ATO, the ATO will be collated, processed through the JMAPS ATO Check (JAC) module, corrected, and then transmitted/transferred to all the tasked units.

E. The method of transmission will be IAW the following JCS/J6 guidance (JCS/J6 MSG, DTG 251935Z JAN 95, SUBJ: AIR TASKING ORDER (ATO) TRANSMISSION):

QUOTE

A. ORIGINATOR - AIR OPERATIONS CENTERS (AOC), JFACC (IF DESIGNATED)

B. ADDRESSEE - CTAPS REMOTES (NORMALLY MINIMUM OF CINC, CJTF, AFFOR, NAVFOR, ARFOR

AND MARFOR).

C. METHOD OF TRANSMISSION

(1). PRIMARY - CTAPS HOST TO REMOTE; UNIT-TO-FORCE LEVEL (UFLINK) CTAPS TO WING COMMAND AND CONTROL SYSTEM (WCCS); UFLINK CTAPS TO STANDARD THEATER ARMY COMMAND AND CONTROL SYSTEM (STACCS)

(2). SECONDARY - IN ORDER OF PREFERENCE:

(A). WWMCCS/GCCS

(B). DSNET (IF AVAILABLE)

(C). THEATER UNIQUE C2 SYSTEMS

(D). PC TO PC FILE TRANSFER (STU lll)

(E). HANDCARRY

(F). AUTODIN - LAST RESORT

D. ATO SHOULD BE TRANSMITTED TO AN ADDRESSEE BY ONE MEANS ONLY.

E. TO LESSEN THE BURDEN LARGE ATOS PLACE ON TRANSMISSION SYSTEMS, ADDRESSEES MUST BE LIMITED TO THOSE WHO ABSOLUTELY REQUIRE A COPY OF THE ATO.

F. FREQUENCY OF TRANSMISSION UPDATE. NORMALLY ON A DAILY BASIS, 12 HOURS PRIOR TO THE START OF THE AIR TASKING DAY OR IN ACCORDANCE WITH THE ESTABLISHED OPERATIONS PLANS FOR THE THEATER OF OPERATIONS. THE AIR TASKING DAY WILL NORMALLY CONSIST OF CONSECUTIVE 24-HOUR TASKING PERIODS WITH START AND END TIMES AS SPECIFIED BY THE COMJTF.

UNQUOTE

4. The following figure depicts the ATO build process flow:

 

 

 

FIGURE 1. ATO PRODUCTION PROCESS

 

 

APPENDIX 1 - ATO Production (APS)

APPENDIX 2 - ATO Production (CAFMS/CAFMS-X)

 

APPENDIX 1 TO ANNEX E TO CHAPTER 3

ATO PRODUCTION - ADVANCED PLANNING SYSTEM (APS) OPERATION

1. GENERAL. The primary software to build the Air Tasking Order (ATO) in 12 AF is the Advanced Planning System (APS). The alternate means or backup is the Plans Section of the Computer Assisted Force Management System (CAFMS) within CTAPS. In addition, even though APS is primary, both APS and CAFMS data bases need to be built/populated when APS is being used.

2. Crisis Action Phase.

A. During the Crisis Action Phase (CAP) of an operation/exercise, ATO Production personnel coordinate for sourcing and inputting of necessary data to ensure preparation/updating of the CTAPS planning system databases and obtain the following data for entry into the Advanced Planning System (APS) from the CAP meeting from which to build a base line database in APS (Tab A)

- Units

- Bases with ICAO and LAT/LONG information

- Aircraft types

- Numbers of aircraft

- Updated Standard Conventional Loads (SCLs) by aircraft type needed for Air Battle planning

- Sortie utilization rate (total number of available sorties, by units and by aircraft)

- IFF/SIF assignments based on force list for unit or aircraft type

- Callwords by unit or aircraft type and for control agencies

- Frequencies for aircraft and control agencies

- Comm plan developed by DOXP/DOXC based on freqs and callwords from SYSCON

- Plain language addresses (PLAs) married to each unit requiring the ATO

B. ATO Production inputs the ATOís General Remarks section information that it receives from Campaign plans via floppy disk in ASC ll format. See the General Remarks/SPINS section contained in Appendix 11 to Annex B to this chapter, for details on what is contained in the SPINS.

C. ATO skeleton worksheets (ASWs) will be available for campaign planners. These worksheets may be filled in for mission planning by campaign planners and augmentees. The primary worksheets that will be used by planners are the mission planning worksheets developed by DOXP. The various types of worksheets follow:

- Target/Orbiter Missions (Tab B)

- Air Refueling Missions (Tab C)

D. An ATO distribution plan will be developed in coordination with SYSCON based on the JCS guidance, unitís geographical location, and unit hardware/comm capability (see Tab D this appendix).

E. The ATO planning cycle and the ATO production timeline will be established.

- Strive for the initial ATO release 36 hours prior to initial ATO effective time

- Establish ATO deadlines for inputs/changes (approximately six hours prior to ATO transmission deadline)

F. In coordination with SYSCON, send out a test message using the ATO message addressee list and Multiple Address Code (MAC) "ATO" requesting a response in order to check the PLA list and office symbols for accuracy and receipt.

3. ATO Construction Phase: (ATO Production Checklist Tab E)

A. Preplanning prior to building the first ATO and generally occurs well prior to exercise or contingency and involves ensuring that the APS and CAFMS data base is current and ready for planning. This involves the following:

- Create an ATO shell

- Update and proof the ATO database (ATO Database proofing checklist Tab F)

-- Units

Bases

-- Aircraft types and numbers

-- SCLs

Sortie utilization rate

-- Call signs and IFF/SIF assignments

- Items provided to ATO Production for import into the ATO

-- Airspace Control Order (ACO) provided by Airspace Control Center (Tab G)

-- Target Nomination List (TNL) provided by Plans Intelligence Branch

-- Order of Battle (OB) provided by Plans Intelligence Branch

-- General Remarks/SPINS provided by Campaign Plans

-- Theater Airlift Mission Data provided by the ALCC

-- Strategic Mobility Air Movement Schedule provided by the AME

B. Daily planning/ATO development. Generally, a separate backup mini-LAN is provided by the TBMCS System Manager to ensure continuity in operations within the AOC. With CTAPS V5.1.1, Combat Plans has the ability to take a snap-shot of the ATO, while in Air Battle Planning. When used with the backup system, this provides for a fairly capable backup process for the ATO planning process. This snap-shot backs up the setup data and the planned missions onto a disk and/or file as required. The following general procedures will be used daily in producing an ATO:

(1). APS:

a. ATO Production will:

- Do an hourly backup of the planned missions

- Backup will be done on the hour, and will be transparent to the planners (Tab H

- Record the backup on the "CTAPS diskette/LAN backup procedures log"(Tab I)

-- include: time, # sorties, # missions, highest APS reference # and disk #

-- initial log

- The Chief of ATO Production must monitor the progress of on-going inputs and planning efforts by the mission line summary worksheet, package summary worksheet and the display sortie flow worksheet.

b. ATO Development planning chiefs will:

- Monitor the tasking of units by the augmentees

-- ensure augmentees know the DO's and Dont's for using CTAPS

- Proof the missions

- Do a review of each unit they are responsible for (found in ABP under ATO generation) specifying unit and format

-- with remarks, if remarks are done in APS

-- without remarks, if remarks are done in CAFMS

- If the mission are good for that unit

-- print out a hard copy

-- initial it

-- hand it to the ATO coordinator on duty

-- include unit remarks worksheet if applicable (Unit Remarks Worksheet Tab K)

- Once all units have been planned and the Chief of ATO Production has a signed copy of the review, export the ATO into CAFMS.

(2). CAFMS

- After the export, collate, jack, and review the ATO

-- ATO Development branch chiefs must now review the ATO in CAFMS ATO review

-- ATO Development branch chiefs and augmentees are ultimately responsible for ensuring the correctness of the mission data in the CAFMS product

- Correct any mission data and USMTF errors

- Import Airlift Mission Data

-- First review the error log for fatal errors before importing

-- Once there are no fatal errors, import the airlift mission data

- Correct any other errors in the Airlift mission data once imported

- Input Unit Remarks into a dummy ATO

- Import the ACO into the same dummy ATO

- Import the Air Movement Schedule (theater and strategic airlift data) into the dummy ATO

- Import the General Remarks/SPINS into the dummy ATO

- Collate and JAC the dummy ATO

-- Correct all USMTF errors in the dummy ATO

- Clone the Unit remarks, General remarks/SPINS, Air Movement Schedule and ACO into the current ATO for the planning cycle

(3). Combat Plans LAN or APS Failure Procedures

a. If during the APS process APS does crash a determination will have to be made to wait for the main LAN to come back up, or to continue planning on the backup LAN. This decision includes several factors. The biggest factor is which part of the system crashed. The decision may take at least 15 to 20 minutes to determine the cause and course of action. If the decision is made to continue planning by going to the backup LAN, Campaign Plans planners will be informed when the backup system has been prepared and they can proceed with planning.

b. If the APS server on the backup mini-LAN fails

-Planners and Augmentees will build their missions on CAFMS worksheets (Appendix 2)

- Planners and Augmentees will give the worksheets to the ATO Coordinator or Team Chief on duty for manual input by CAFMS technicians

- Planners will not leave until a final proof has been printed out, reviewed, initialed by planner and handed in to the ATO Coordinator or Team Chief

4. Data Export Phase: Upon completion of missions planned in APS the ATO is exported to CAFMS.

A. ATO Production exports the data planned in APS into CAFMS

B. Quality checks are accomplished by using proof sheets and the ATO collate and JAC

5. General Remarks Import Phase. During this phase, the ACO, airlift mission schedule, and General remarks are added to the ATO

A. Campaign Plans collects the General Remarks/SPINS information and uploads it on a floppy disk in ASC ll format and provides it to ATO Production for input into the General Remarks/SPINS section of the ATO.

B. Airspace Control Center (ACC) builds the Airspace Control Order (ACO) and exports it to the appropriate ATO where ATO Production personnel incorporated into the ATOís General Remarks/SPINS section.

C. The ALCC will provide the airlift mission schedule in a floppy disk format for import into the SPINS, unless the C2IPS early operational interface (EOI) is being used. In this case, the ALCC will coordinate with the Chief, ATO Production for which CTAPS/TBMCS workstation will be used as a destination for the electronic file to be used for uploading the data (via the floppy).

6. ATO Review and Distribution Phase:

A. ATO Review includes the following:

- Verify all targets on the JIPTL are in the ATO

- Review the general remarks for completeness and grammatical errors

- Ensure General Remarks are in ASC ll format on a floppy disk and uploaded in APS or CAFMS

- Collate the ATO (Collate brings all files together)

- Ensure ATO is arranged together in USMTF format

- JAC the ATO (searches for any USMTF errors) and correct errors

B. ATO distribution process (see Tab D - ATO Distribution Plan) provides all users with a copy of the daily ATO and includes the following in order:

- The ATO dissemination data is built to identify the ATO

- The JFACC, or his designated representative (normally the AOC Director or Chief of Combat Plans) authorizes the release of the ATO

- The ATO is scheduled which releases it to Combat Operations

- The ATO is transferred to remote CTAPS/WCCS terminals

- The ATO is downloaded to a floppy disk to transmit over Worldwide Military Command and Control System (WWMCCS)/Global C2 System (GCCS) by a 1C3XO Command Post Controller

- The ATO is transmitted to JMPP (the ATO Header is built using JMPP which includes addresses of whom it should be sent)

- The ATO is nominated to the Standalone Operational Message Processing Systems (STOMPS) which transmits the ATO over AUTODIN

- The ATO is printed and copied for distribution within the AOC

TAB A - Crisis Action Phase Data

TAB B - ATO Skeleton Worksheet (ASW) - Target/Orbiter Missions

TAB C - ATO Skeleton Worksheet (ASW) - Air Refueling Missions

TAB D - ATO Distribution Plan

TAB E - ATO Production Checklist

TAB F - ATO Database Proofing Checklist

TAB G - Airspace Mapping During ADS to APS Import

TAB H - ATO Backup Procedures

TAB I - CTAPS Diskette/LAN Backup Procedure Log

TAB J - Unit Remarks Worksheet

 

TAB A TO APPENDIX 1 TO ANNEX E TO CHAPTER 3

CRISIS ACTION PHASE (CAP) DATA

 

CRISIS ACTION PHASE (CAP) DATABASE WORKSHEET

The following information is required for the construction of the database.

BASE NAME__________________________________________________________________________

ICAO (BASE I.D.) _________ LAT/LONG _________________________________________________

BASE ELEVATION_________________ REMARKS ____________________________________

 

UNIT___________________ #OF AIRCRAFT_________ TYPE OF A/C________________________

UTE RATE: SUSTAINED _________ SURGE ___________ MX TURN TIME ____________

PLA_________________________________________________________________________________

OFFICE SYM _____________________________ RI ________________________________________

 

UNIT___________________ #OF AIRCRAFT_________ TYPE OF A/C________________________

UTE RATE: SUSTAINED _________ SURGE ___________ MX TURN TIME ____________

PLA_________________________________________________________________________________

OFFICE SYM _____________________________ RI ________________________________________

 

UNIT___________________ #OF AIRCRAFT_________ TYPE OF A/C________________________

UTE RATE: SUSTAINED _________ SURGE ___________ MX TURN TIME ____________

PLA_________________________________________________________________________________

OFFICE SYM _____________________________ RI ________________________________________

 

UNIT___________________ #OF AIRCRAFT_________ TYPE OF A/C________________________

UTE RATE: SUSTAINED _________ SURGE ___________ MX TURN TIME ____________

PLA_________________________________________________________________________________

OFFICE SYM _____________________________ RI ________________________________________

 

*OFFICE SYM -- THE OFFICE SYMBOLS THAT NEED TO RECEIVE THE ATO. *PLA -- PLAIN LANGUAGE ADDRESS REQUIRED FOR MESSAGE TRAFFIC. *RI -- ROUTING INDICATOR. *UTE RATE -- NUMBER OF SORTIES PER DAY - SUSTAINED AND SURGE RATE. *MX TURN TIME-- TIME IT TAKES TO REFUEL, LOAD ORDNANCE AND TAKE-OFF (i..e. FROM LANDING TO SUBSEQUENT TAKEOFF)

TAB B TO APPENDIX 1 TO ANNEX E TO CHAPTER 3

ASW - TARGET/ORBITER MISSIONS

 

ATO SKELETON WORKSHEET

TARGET/ORBITER MISSION

 

_______ _______ _______ __________

ATO ID MONTH BASE UNIT

_______ _____ __________ ____ ____ _________

MSN NO PKG CALLSIGN C/S # #AC AC TYPE

______ _____ ________ ______ ______ ______ ______

AMSN ALRT MSNLEN SCL1 SCL2 IFF/SIF1 IFF/SIF2

COMMENTS: ___________________________________________________________________________________________

SUPPORT MSN #íS ___________, ___________, ___________, __________, __________, ___________,

UNIT REMARK(s) ID ______, ______, ______, ______, ______, ______, _______ (letters only)

------------------------(USE EITHER PRIMARY MSN STATION OR TGT LOCATION (MULT TGT DATA))------------------------

PRIM MSN STATION_________________ TOS_________ TFS_________ ARMY REQ#__________

ALT______ COORD:_______________ _______________ _______________

(additional) MSN STATION______________ TOS________ TFS________ ARMY REQ#__________

ALT______ COORD:_______________ _______________ _______________

------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

TANKER REQUEST DATA (IF REQUIRED)

MSSNO ARCT FUREQ DESIRED TRACK

_______ _____ _______ ____________________________

_______ _____ _______ ____________________________

------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

TARGET/MULTIPLE TGT DATA:

TGT REF NO TOT TFT ARMY REQ# RECCE REQ#

________________ __________ ________ ____________ _______________

________________ __________ ________ ____________ _______________

________________ __________ ________ ____________ _______________

------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

CONTROL INFO:

CONTROL TYPE________ C/S____________ PRI FRQ_______ SEC FRQ_________

RPT PNT________ COMMENTS_____________________________________________________

------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

FAC INFO:

C/S___________ PRI FRQ_______ SEC FRQ________ RPT PNT___________

SPRT UNIT____________ COMMENTS______________________________________________

------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

ELECMBT:

C/S__________________ PRTY____________ SEC FRQ_________ RPT PNT___________

MSN LOC_________________ ALT__________ TOS_________ TFS_________

------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

TARGET INFO (EXERCISE ONLY) TGT#_______ ID_______ TGT NAME_____________________

TGT COORD_____________________ TGT COMMENTS______________________________

TAB C TO APPENDIX 1 TO ANNEX E TO CHAPTER 3

ASW - AIR REFUELING MISSIONS

 

ATO SKELETON WORKSHEET

AIR REFUELING MISSION

_______ ______ _______ _________

ATO ID MONTH BASE UNIT

_______ _____ __________ ____ ____ _________

MSN NO PKG CALLSIGN C/S # #AC AC TYPE

______ _____ ________ ______ ______ ______ ______

AMSN ALRT MSNLEN SCL1 SCL2 IFF/SIF1 IFF/SIF2

COMMENTS______________________________________________________________________________________

SUPPORT MSN #íS __________, __________, __________, __________

UNIT REMARK(s) ID ______, ______, ______, ______, ______ (letters only)

PRIM MSN STATION_________________ TOS_________ TFS_________ ARMY REQ#__________

ALT______ COORD:_______________ _______________ _______________

(additional) MSN STATION______________ TOS________ TFS________ ARMY REQ#__________

ALT______ COORD:_______________ _______________ _______________

TANKER DATA:

FREQUENCY AIR/AIR TACAN OFFLOAD

PRI / SEC RCVR / TANKER AVAIL SCHED DIFF

______/______ ________/_______ ______ ______ ______

REFUELING SYS (CIRCLE ONE) FUEL TYPE TOTAL RVCR AC

BOM DROG BOTH ___________ _____

MSSNO ARCT FUREQ ASSIGNED TRACK

_______ _________ ______ ___________________________

_______ _________ ______ ___________________________

_______ _________ ______ ___________________________

_______ _________ ______ ___________________________

_______ _________ ______ ___________________________

_______ _________ ______ ___________________________

CONTROL INFO:

CONTROL TYPE_________ C/S___________ PRI FRQ_________ SEC FRQ______

RPT PNT_______________ COMMENTS__________________________________________________________________

 

 

TAB D TO APPENDIX 1 TO ANNEX E TO CHAPTER 3

ATO DISTRIBUTION PLAN

 

 

 

 

 

 

 

 

 

TAB E TO APPENDIX E TO CHAPTER 3

ATO PRODUCTION CHECKLIST

ATO DESIGNATION: APS________/ VERSION_______; CAFMS_______

YEAR_________ MONTH_________ ATO PERIOD: FM__________z TO___________z

Z-TIME = L+_______ HRS; ATO SHELL WINDOW: FM__________z TO___________z

EVENT TIME DONE DONE BY

ACO DRAFT COMPLETED ____________ _________

TNL TRANSFERED TO CIDB ____________ _________

ATO SHELL CREATED ____________ _________

ACO IMPORTED (ACMs________) ____________ _________

INITIAL TNL IMPORTED ____________ _________

(DMPIs___________/WPNR OPTIONS_________)

OB IMPORTED ____________ _________

FEBA CREATED IN APS/ ADS ____________ _________

ATO SHELL TURNED TO ORBIT PLANNERS ____________ _________

FINAL TNL IMPORTED ____________ _________

ATO SHELL TURNED TO ATTACK PLANNERS ____________ _________

UNIT REMARKS CREATED ____________ _________

GENERAL REMARKS CREATED ____________ _________

APS ATO DONE (MSN_________/ SORTIES_________) ____________ _________

TRANSFERED TO CAFMS (AS REQUIRED) ____________ _________

ATO CORRECTED AS NECESSARY ____________ _________

(BASED ON ADE MISSION FILE ERRORS. iF NECESSARY, CORRECT ATO IN ETIHER APS OR CAFMS. IF CORRECTED IN APS, IT WILL REQUIRE ATO ADB OF CAFMS ATO FOLLOWED BY ADE REPEAT)

CREATE AIR (CAFMS ONLY ATO) ____________ _________

CREATE/ MODIFY ADD ____________ _________

CREATE/MODIFY MISSIONS ____________ _________

AIRLIFT MSN DATA RECEIVED ____________ _________

AIRLIFT MSNs UPLOAD (MDU) ____________ _________

COLLATE ATO (MSNs__________) ____________ _________

JAC ATO ____________ _________

CORRECT ERRORS (AS NECESSARY) ____________ _________

ATO RE-COLLATED (AS NECESSARY) ____________ _________

ATO RE-JACíd (AS NECESSARY) ____________ _________

ATO SCHEDULED TO COMBAT OPS ____________ _________

ATO TRANSFERRED TO REMOTES ____________ _________

(SEE ATTACHED REMOTE DISTRO W/SHEET)

ATO TRANSFERRED TO WCCS ____________ _________

ATO TRANSMITTED TO JMPP/STOMPS ____________ _________

ATO PRODUCTION COMPLETED ____________ _________

ATO SIZE:

ATO REVIEW PAGES _________

BYTES (K) _________

JMPP SECTIONS _________

CHIEF, ATO PRODUCTION __________

CHIEF, COMBAT PLANS __________

NOTES: ______________________________________________________________________

TAB F TO APPENDIX 1 ANNEX E TO CHAPTER 3

PROOFING THE DATABASE

 

1. THEATER DATA

A. Ensure every aircraft has an assigned aircraft role.

B. Ensure each aircraft has a mission type and assigned SCLs.

2. SCENARIO DATA

A. Ensure each base has a latitude, longitude, and an elevation.

B. Under friendly units:

(1). Ensure each unit has the correct service code

(2). Ensure each unit has the correct base

(3). Ensure each unit has the correct aircraft type

(4). Ensure each aircraft has a mission type

C. Under tactical information

(1). IFF/SIF service code and unit service code need to match

(2). Make sure every unit has a callword(s) to meet mission requirements

(3). IFF/SIF and aircraft types must match in IFF/SIF field

(4). Callword number and mission paired correctly at the top

(5). Mission number and Mode number must be paired correctly at top

 

 

 

 

 

TAB G TO APPENDIX 1 ANNEX E TO CHAPTER 3

AIRSPACE MAPPING DURING ADS TO APS IMPORT

 

1. The following airspace types will be used in building the airspace control order (ACO) database in ADS with the APS correlating types:

ADS Type APS Type

AR= Air Routes Other

AIRBASE= Air Base Other

AIRPRT= Airport Other

AIRREF= Air Refueling Refueling Airspace (Tankers)

BDZ= Base Defense Zone Other

BORDER= FLOT FSCL, etc. LOD

CA= Coordinating Altitude Other

CAP= Combat Air Patrol CAP

CAS= Close Air Support Other

C2= Command and Control Platforms C2

CFL= Coordinated Fire Line LOD

CP= Control Point Other

EA= Engagement Area Other

EC= Electronic Combat Platforms EC

FEZ= Fighter Engagement Zone Other

FFA= Free Fire Area Other

HIDAZ= High Density Airspace Control Zone Other

IFF= IFF On/Off Line LOD

MEZ= Missile Engagement Zone Other

MRR= Minimum Risk Rate Other

NAVAID= Navigational Aid Other

NFA= No Fire Area Other

PROHIB= Prohibited Area Other

REGION= Air Defense Region Other

RFA= Restricted Fire Area Other

RFL= Restricted Fire Line LOD

ROZ= Restricted Operations Zone Other

SAAFR= Standard Army Aviation Flight Route Other

SECTOR= Air Defense Sector Other

2. Refrain from using any other types if possible. If not possible, coordinate with the Chief, ATO Production and the Chief, Airspace Control Center for additions/deletions/changes to the above list.

 

TAB H TO APPENDIX 1 ANNEX E TO CHAPTER 3

ATO BACKUP PROCEDURES

 

1. PROCEDURES: The ATO data base will be backed up to a floppy every hour on the hour from 2300L - 1200L each day, at a minimum. This will ensure that we retain current mission planning data on the current days ATO and will also be used to bring up the ATO on the back-up Local Area Network (LAN). Preceding the back-up operations, attain the highest APS Reference Number and annotate this number using pencil on the diskette. You can get this number by entering Air Battle Planning in APS; then select plan status on the U/I; then selecting "Mission Line Summary ", Then highlight APS REF # and sort by descending order on the utilities sub-menu. Upon completion of that task, the following procedures will be used for back-up diskettes and storage operations:

A. Temporary back-up diskettes: Back-up of the ATO will begin at 2300L and every hour thereafter until 1200L. A separate diskette will be used for each hour and will be so annotated (i.e. 2300, 2400, 0100, and etc.), for a total of 13 diskettes. These diskettes will be reused each day. Another diskette will be used to back-up each hour as noted above, however, this diskette will be overwritten each time on an hourly back-up. In other words, two back-up disks for each hour of the ATO production; one is updated each hour with the new data and the other diskettes are used for each individual hour of the ATO period.

B. Permanent back-up (historical) diskettes: Prior to the ATO being transmitted, a back-up copy of the ATO, including general remarks, will be saved to a diskette. Each 3.5" diskette should only hold one ATO. These diskettes will be retained by ATO Production for file copies.

2. SECURITY: All diskettes will be classified SECRET and marked appropriately with classification , title, date, and APS REF #. They will be stored in ATO Production area within the AOC in a diskette storage carrier properly marked. All temporary diskettes will be declassified via one of the two following methods:

A. Use an officially approved degausser

B. Use Norton Utilities/Wipeinfo utiliy

(1). Wipeinfo utility must be run three times on the disk

(2). Disk must then be reformatted

3. LOGGING: Log all diskette back-ups, back-up LAN recoveries, and CTAPS/APS reloads on the provided log sheets with all pertinent information, including the highest APS REF #.

4. RESPONSIBILITY: The designated Team Chief is responsible for conducting procedures listed in this policy letter. Other team members may conduct the actual operation, however, the team chief is to ensure procedures are adhered to unless rescinded or revised.

5. JAC/COLLATE: The ATO will be JACíd in APS prior to each back-up of the ATO and a JAC file will be saved to a separate floppy diskette. A floppy diskette with JAC errors will be accomplished in CAFMS also, once the ATO has been pushed into CAFMS daily.

 

TAB I TO APPENDIX 1 TO ANNEX E TO CHAPTER 3

CTAPS DISKETTE/LAN BACK-UP OPS LOG

DATE:_____________

CTAPS DISKETTE/ LAN BACK-UP OPS LOG

TIME

# SRTS

# MSNS

APS REF #

DISK #

COMMENTS/REMARKS

INIT

             
             
             
             
             
             
             
             
             
             
             
             
             
             
             
             
             
             
             
             
             
             
             
             
             
             
             
             
             
             
             
             
             
             
             
             
             

 

TAB J TO APPENDIX 1 TO ANNEX E TO CHAPTER 3

UNIT REMARKS WORKSHEET

 

DATE _______ UNIT _______ ATO _____ CHG _____

Unit Remark ID Unit Remark

A ___________________________________________________

___________________________________________________

___________________________________________________

B ___________________________________________________

___________________________________________________

___________________________________________________

C ___________________________________________________

___________________________________________________

___________________________________________________

D ___________________________________________________

___________________________________________________

___________________________________________________

E ___________________________________________________

___________________________________________________

___________________________________________________

Mission # Applicable Remark IDs Mission # Applicable Remark IDs

_______ __________________ _______ __________________

_______ __________________ _______ __________________

_______ __________________ _______ __________________

_______ __________________ _______ __________________

_______ __________________ _______ __________________

_______ __________________ _______ __________________

_______ __________________ _______ __________________

_______ __________________ _______ __________________

_______ __________________ _______ __________________

_______ __________________ _______ __________________

_______ __________________ _______ __________________

_______ __________________ _______ __________________

_______ __________________ _______ __________________

_______ __________________ _______ __________________

APPENDIX 2 ANNEX E TO CHAPTER 3

ATO PRODUCTION - CAFMS

1. GENERAL. In the event that 12 AF is unable to plan and build the ATO using the Advanced Planning System (APS), the backup procedure is to use CAFMS. Although CAFMS procedures are also addressed in Appendix 1 to Annex E to Chapter 3 in conjunction with APS, this Appendix further delineates the additional procedures on how we plan to build the ATO built exclusively using CAFMS

2. RESPONSIBILITIES.

A. Crisis Action Team (CAT) Phase: During the CAT phase of a campaign/exercise, ATO Production must acquire the following necessary information to build a base line database in CAFMS (see Tab A to Appendix 1, this Annex) in order to produce the initial theater ATO:

- Units

- Bases with ICAO and LAT/LONG information

- Aircraft types and numbers (all aircraft, to include helicopters of all services )

- Updated Standard Conventional Loads (SCL) and performance characteristics by aircraft type

- Call signs and IFF/SIF assignments

- Plain Language Addresses (PLAs) married to each unit requiring the ATO

(1). ATO Production receives the General Remarks via floppy disk from Campaign Plans during the CAT phase for entry into the ATO. See the General Remarks/SPINS section contained in Appendix 11 to Annex B to this chapter, for details on what is contained in the SPINS.

(2). ATO skeleton worksheets (ASWs) will be provided for campaign planning to the augmentees. These worksheets are filled out for all missions and returned to CAFMS technicians for entry into the ATO. The various types of ASWs follow:

- Target/Orbiter Missions (Tab B to Appendix 1, this Annex)

- Air Refueling Missions (Tab C to Appendix 1, this Annex)

(3). Support CTAPS/combat plans training sessions for aircrew augmentees held by Campaign Plans

(4). Establish the ATO planning cycle and the ATO production timeline

- Strive for initial ATO release 36 hours prior to initial ATO effective time

- Establish deadlines for inputs/changes (normally six hours prior to ATO transmission deadline)

(5). Send out test message using the ATO message addressee list requesting a response in order to check the PLA list and office symbols for accuracy

B. ATO construction phase begins by creating the ATO and ensuring that the CAFMS database is current and ready for planning inputs

(1). Create the ATO identification record (AIR). The AIR contains the valid times that the ATO covers and also contains comments such as the operation/exercise name and the ATO day. Creating the AIR is mandatory prior to inputting mission data

(2). Create the ATO Dissemination Data (ADD). The ADD provides the message originator (CP/CCP), acknowledgment YES or NO, downgrade instructions, operation/exercise name and narrative information. Additionally, ensure the first line of the ADD Remarks section (bottom block) contains the ATOís ID and classification repeated across the first line to form a banner. Example:

"ATO-A/SECRET ATO-A/SECRET ATO-A/SECRET ATO-A/SECRET ATO-A/SECRET "

(3). Worksheet handling procedures

- IN, OUT and DONE boxes are placed near CAFMS technicians

- Augmentees place completed worksheets into the IN box

-- Supervisor and/or coordinator review worksheets for completeness and accuracy

- CAFMS technicians input data from the worksheets into the ATO

- CAFMS technicians collate the ATO and print out a copy of missions by unit using ATO review

- The ATO review by unit and augmentee worksheets are stapled together with the newest one on top and placed into the OUT box for the augmentee to review

- The process continues until the augmentee initials the final review and places the review and worksheets into the DONE box

C. General Remarks/SPINS import phase: During this phase, the ACO provided by the Airspace Control Center is exported into CAFMS from the Airspace Deconfliction System (ADS). The Chief, ATO Production will be notified via an auto SMA when the ACO has been exported to CAFMS (or is available for importing into APS). The ACO is then imported into the ATO general remarks section of the ATO by way of the CAFMS AGR screen. The Chief of Airspace and the CAFMS Team Chief will review the ACO to ensure it has imported accurately. In addition, the General Remarks/SPINS which are provided by Campaign Plans in ASC II format on a floppy disk are input into the ATO and reviewed for accurate entry. The airlift mission schedule is the final product (provided by the ALCC) for inclusion in the SPINS.

D. ATO Review Phase: This Phase occurs after all units have initialed their worksheets, placed them in the DONE box and all information has been input into the ATO. Then, a final collate is accomplished and the JMAPS ATO check (JAC) is performed which checks for any USMTF errors. Any errors found are corrected and JACs are performed until corrections have been made

E. ATO Distribution Phase:

(1). The AOC Director, or the Chief of Combat Plans, if so designated, approves the ATO and authorizes its release

(2). The ATO is Scheduled which releases it to Combat Operations

(3). The ATO is transferred to remote CTAPS terminals

(4). The ATO is downloaded to a floppy disk to transmit over the Worldwide Military Command and Control System (WWMCCS) or via the Global Command and Control System (GCCS) by a 1C3XO Command Post Controller

(5). The ATO is transmitted to JMPP where the ATO header is built which includes addressees to whom it should be sent (see ATO Distribution Plan, Tab D to Appendix 1, this Annex)

(6). The ATO is nominated to the Standalone Tactical Operational Message Processing System (STOMPS) which transmits the ATO over AUTODIN

(7). The ATO is printed and copied for distribution within the AOC

3. CAFMS Team Chief responsibilities

A. Works directly with Chief, ATO Production and oversees all ATO Production

B. Establishes work area responsibilities

C. Establishes work schedules and coordinates billeting and transportation, and ensures manning for peak periods is met

D. Responsible for setting up the ATO Production work area using materials from nesting box including the IN/OUT/DONE boxes

E. Control the IN/OUT/DONE boxes to maintain continuity and ensure all inputs are received prior to established deadlines

 

APPENDIX 3 TO ANNEX R TO CHAPTER 3

STANDARDS FOR IDENTIFYING CONVENTIONAL LOADS

 

1. GENERAL. The STANDARD CONVENTIONAL LOAD (SCL) in the ATO are recommended loads based on desired effect, weather, guidance and tactics based on the weapons system expert, (i.e., unit representative to the AOC). Any questions by units need to be taken care of through unit POCs within the AOC.

2. STANDARD CONVENTIONAL LOADS. The following is the standard for identifying conventional loads. It is meant to be as simple as possible, however, since it is a 5 character code it has its limitations. Consequently, the code is broken up for 3 types of aircraft/missions. The first section (A) is Air to Air, second section (B) is Air to Ground (except B-52s and B-1s) and section (C) is B-52s and B-1s.

3. SCL ID descriptions.

A. Air-to-Air

(1). 1ST CHARACTER - X indicates air to air weapons load

(2). 2ND-4TH CHARACTERS - number of missiles from long range to short respectively

a. 2ND CHARACTER - AIM-120 for Air Force, AIM-54 for Navy

b. 3RD CHARACTER - AIM-7s

c. 4TH CHARACTER - AIM-9s

(3). 5TH CHARACTER - number of external fuel tanks

(4). Examples of air-to-air SCLs:

X8000 - AIR-AIR, 8 X AIM-120, 0 X AIM-7, 0 X AIM-9, 0 TANKS

X6201 - AIR-AIR, 6 X AIM-120, 2 X AIM-7, 0 X AIM-9, 1 TANK

X4222 - AIR-AIR, 4 X AIM-120, 2 X AIM-7, 2 X AIM-9, 2 TANKS

X0263 - AIR-AIR, 0 X AIM-120, 2 X AIM-7, 6 X AIM-9, 3 TANKS

B. Air-to-Ground (except B-52s/B-1s larger weapons loads)

(1). 1ST CHARACTER - number of weapons (amounts greater than 9 start with alphabet - see below)

A - 10 N - 23

B - 11 O - 24

C - 12 P - 25

D - 13 Q - 26

E - 14 R - 27

F - 15 S - 28

G - 16 T - 29

H - 17 U - 30

I - 18 V - 31

J - 19 W - 32

K - 20 X - indicates air-to-air load

L - 21 Y - not used at this time

M - 22 Z - full load for amounts above 32

(2). 2ND - 4TH CHARACTERS - consists of 3 alpha-numeric characters. Use the following steps to describe the weapon:

a. Determine if it is a high/low drag optional weapon, use

H - high drag

L - low drag

b. Determine how many numbers are used to normally describe the weapon (I.E., MK82 vs MK117 or AGM65 vs AGM142). If it has 3 numbers (117 and 142) drop the hundreds (17 and 42).

c. If it is a high/low drag weapon place the H or L after the number without any prefix (82H or 82L). WAALAA - you now have a three character code.

d. If it is any other type of air to ground weapon, use the following guide and put the alpha character as a prefix to the numbers (I.E., A65 or C89 for AGM65 and CBU89)

(3). 2ND CHARACTER - WEAPONS TYPE

L - LAU B - BLU

A -AGM G - GBU

I -AIM S - SUU

C -CBU M - MK

Exceptions - UK1 - three character code for UNITED

KINGDOM 1000 (UK1000)

WE1 - Walleye I - MK1 (NAVY unique)

WE2 - Walleye II - MK5 (NAVY unique)

Note for 2ND - 4TH CHARACTERS: as stated, GP bombs that are high/low drag such as MK 82/84/117 will not be preceded by an "M". Instead, they will be indicated as follows:

82H OR 82L example 882L0 - 8 X MK82 low drag and 0 tanks

84H OR 84L example 884H1 - 8 X MK84 high drag and 1 tank

Note: EXCEPTION: If the 2nd -4th characters are "CBU"-"GBU"-"BLU"-"AGM" then a mixed load is indicated for each of those munition and must be specified in the unit remarks. (ei., "8CBU0" would be 8 CBU of some mix and zero tanks; the combination of CBU - 4xCBU58 and 4xCBU89 - needs to be specified in unit remarks).

If there is not an SCL for the aircraft you want, you need to write it down with a description so that it can be added to the theater setup in order for it to be ready before the planning starts.

(4). 5TH CHARACTER - number of external fuel tanks

(5). Examples of air-to-ground SCLs:

682H3 - 6 X MK82 high drag GP bombs and 3 external fuel tanks

4C870 - 4 X CBU87 cluster bombs and 0 external fuel tanks

6L681 - 6 X LAU68 rockets and 1 external fuel tank

2A652 - 2 X AGM65 Mavericks and 2 external fuel tanks

2M200 - 2 X MK20 Rockeye and 0 external fuel tanks

ZUK10 - full load (36) x United Kingdom 1000 and 0 tanks

 

C. B-52s AND B-1s

(1). 1ST AND 2ND CHARACTERS - number of weapons (01-99, because of larger loads this is different than para b, 1st character for number of weapons)

(2). 3RD-5TH CHARACTERS - weapons type (same as process step 2b, 2nd-4th characters for weapons type)

(3). Examples:

H - 51 X MK82 high drag GP bombs

0 - 08 X MK60 bombs

Note 1: Any clarification required for specific weapons types such as AGM65A/B vs AGM65C/D will be indicated in the unit remarks

NOTE 2: Unless otherwise noted in the ATO, loading of AIM-7/9 missiles, ECM pods, gun, chaff, flares and laser pods are at unit discretion.

NOTE 3: Any questions should be addressed to 12AF/612CPS/DOXA (DSN 228-2259/5184/3981).



[Back]

[Index]

[Next]
Air Operations Center (AOC) Standard Operating Procedure (SOP)
Twelfth Air Force (12AF) Air Force Forces (AFFOR)