• Add a Schedule Event fact to the knowledge base for either the JFACC or JTFHQ (see Note below)
  • Reminder that the scheduled event can only be renamed when first created, and it must start with “ScheduleEvent” or the rule won’t evaluate correctly

• Enter Time of Scheduling
  • Enter the time when fact should evaluate as true
    • If uncertain about the time it can be changed later
  • The rule for that new event will read something like:

if [ { currentTime } = 0.0]

then true

• If desired, change that time to whenever that rule should evaluate as true (note it is case sensitive)
• Add a new Action with key name assigned as “true” (versus “#IN_EVERY_CASE” or “New Key”)
• » Modify BSEs » Move an Air Unit to a new air base
• Select the squadron and new base
• Select the timing for the move
• Immediate (when the rule is evaluated as true)
  • Incremental (time offset from the time above based on a number or a fact)
  • Absolute Timing (based on a number or a fact)
• At the time selected:
• The fact will evaluate as true in C4ISR_KNOWLEDGEBASE_FACTS
  • C4ISR_KNOWLEDGEBASE_ACTIONS will show the actions triggered as a result of the fact becoming true
  • The Air Unit will deregister from the JFACC and immediately re-register
  • (see AIR_ATO_JFACC_CONTROLLED_—UNITS) and will show as resident with the air base installation (see GEN_BSE_RESIDENTS)

During the duration of the air unit’s move to the new location all launches will cancel, and all Flights will return to land at the squadron’s original location when they launched. As soon as the relocation is complete, and the squadron registers with the JFACC, flying can resume if all the normal criteria are met (range, fuel, munitions, weather, runway, etc), with launches and landings from the new location (as shown in AME Arrival and video playback). Expect to see many of the remaining takeoffs for that day's flights to cancel (AIR_ATO_EXEC_ORDER_CX) for “LaunchBaseAndOrTgtMovedOutOfRange”, since the squadron is now in a different location than when the flights were planned (especially during retrograde). Planning and execution will resume normally with the next planning cycle.

Users are allowed to select the time it will take for the air unit to make the move. The parameter “Specify Down Time (hours)” in the Campaign Planning View GUI is deactivated (see figure above), but users can edit it in the Data View GUI (see figure below). However, read the note in the figure above for reasons why the value shouldn’t be edited unless absolutely sure.

Notes:

• The example here uses a Schedule Event; actually, any fact can be used to trigger the “Move an Air Unit to a new air base” action. These facts can be more dynamic than a scripted hour. For example, a squadron might move based on transition to a new state, or attrition, or arrival of more aircraft.
• Since squadrons deactivate while moving, they must register with the JFACC in time for planning for the following cycle or they won’t be used for that 24 hour cycle. This should be reviewed for potential enhancement allowing planning to be conducted even while the unit is moving in anticipation of it being able to fly during the next cycle.
• If the squadron moves while it still has aircraft airborne, those aircraft will return to land at the location where the squadron had been when they took off.
• The transfer of aircraft to the new location is implicit (i.e. they can’t be adjudicated, and feasibility of an aircraft making the relocation isn’t evaluated).

Limitations: The planned flights can cancel (as described above) even if they are of the utmost priority. The JFACC would have planned the high priority missions to be conducted either by another squadron or at another time than during the squadron move.