(totalAircraftInTankerCell ?CELL ?NUMBER) means that the total
number of aircraft involved in the AirTankerCellMissionPlan ?CELL is
the PositiveInteger ?NUMBER.
(earliestTime ?EARLIEST ?TIMESET) means
that the TimePosition ?EARLIEST is the earliest time in the set of
TimePositions ?TIMESET.
(airLaunchPointOfATOPlan ?MISSIONPLAN ?LOCATION) means that in the
ATOMissionPlan ?MISSIONPLAN, a weapons launch is planned at the
GeographicArea ?LOCATION.
(aircraftRefuelsAircraft ?PROVIDER ?RECEIVER) means that the
MilitaryAircraft ?PROVIDER offloads fuel to the MilitaryAircraft
?RECEIVER.
(earliestTime ?EARLIEST ?TIMESET) means
that the TimePosition ?EARLIEST is the earliest time in the set of
TimePositions ?TIMESET.
(firstDepartureBase ?PLAN ?DEPLOC)
means that in the ATOMissionPlan ?PLAN, the first departure base is
the location ?DEPLOC.
(groundTargetOfATOMission ?MISSIONPLAN ?TARGET) means that in the
ATOMissionPlan ?MISSIONPLAN, the Object ?TARGET is a ground target.
(lastArrivalBase ?PLAN ?ARRLOC)
means that in the ATOMissionPlan ?PLAN, the last arrival base is
the location ?ARRLOC.
(missionAirdropLocation ?PLAN ?PLACE) means that in the air Plan
?PLAN, the mission aircraft is to complete an AirdropMission at the location
?PLACE. The location may be specified for a particular mission leg of an
AirMovementReSupplyPlan using the function MissionLegFn, e.g.,
(missionAirdropLocation (MissionLegFn ?NTH ?ATOPLAN) ?PLACE).
(missionLegArrivalBase ?LEG ?BASE) means that in the
MissionLegOfATOMission ?LEG, the assigned mission aircraft is tasked
to stop at the MilitaryAirport ?BASE.
(missionLegDeliverable ?LEG ?OBJECT) means that in the mssion leg or
leg segment ?LEG, the assigned mission aircraft are tasked to deliver or
airdrop ?OBJECT to the specified location.
(missionLegTimeIn ?LEG ?TIME)
means that in the mission leg or leg segment ?LEG, the assigned mission
aircraft is tasked to be at the stopover (or airdrop) point at or after
the TimeInterval ?TIME.
(missionLegTimeOut ?LEG ?TIME)
means that in the mission leg or leg segment ?LEG, the assigned
mission aircraft is tasked to leave the stopover (or airdrop) point
at or before the TimeInterval ?TIME.
(missionUtilizingCOMAOTimepoint ?PLAN ?ROUTE) means that the
MilitaryAircraft of the ATOMissionPlan ?PLAN utilize the
TimingReferencePoint ?TRP.
(requestNumber ?REQ ?SYMBOL) means that
the Requesting ?REQ has the SymbolicString ?SYMBOL assigned to it or
to the associated Request which it conveyed.
(shipAssignedToATOMission ?PLAN ?SHIP) means that the
NavyFlightOperationsMissionPlan ?PLAN includes an assignment for the
Ship ?SHIP. The ships assigned are AircraftCarriers.
(shipTargetOfATOMission ?MISSIONPLAN ?TARGET) means that in the
ATOMissionPlan ?MISSIONPLAN, the targeted Object ?TARGET is a Ship.
(tankerCellDuration ?CELL ?INTERVAL)
means that in the AirTankerCellMissionPlan ?CELL, the time period between
the tanker cell start and end times is the TimeInterval ?INTERVAL.
(totalAircraftInTankerCell ?CELL ?NUMBER) means that the total
number of aircraft involved in the AirTankerCellMissionPlan ?CELL is
the PositiveInteger ?NUMBER.
(totalAircraftInTankerCell ?CELL ?NUMBER) means that the total
number of aircraft involved in the AirTankerCellMissionPlan ?CELL is
the PositiveInteger ?NUMBER.
AirCorridor is the subclass of
AirTransitways that are restricted areas of air travel, specified for
use by friendly aircraft and established for the purpose of preventing
friendly aircraft from being fired on by friendly forces (source: JEL).
An AirCorridor may contain multiple AirTransitways designated in
CompositeAirOperationsMissionPlans that are used to manage traffic
in the corridor.
AirMovementReSupplyMission
is the subclass of ATOMissions that implement
AirMovementReSupplyMissionPlans.
AirMovementReSupplyMissionPlan is a subclass of AirliftMissionPlan.
The Air Movement Re-Supply mission model is used for airlift mission
objectives that deliver supplies and personnel to a base by landing at
that base to offload and/or onload materials. Unlike all other missions,
the air movement re-supply mission (airlift and support helicopter) have
multiple takeoffs and landings and the mission retains its mission number,
callsign and IFF/SIF modes and codes throughout all of the scheduled
mission takeoffs. (FLOMM, p. 33).
AirStationTankerMission is a subclass of AirTankerMission.
An AirStationTankerMission is the implementation of an
AirStationTankerMissionPlan.
AirStationTankerMissionPlan is a subclass of AirTankerMissionPlan.
The Air Station (Non-Cell) Tanker mission model is used when the mission
objective is to perform aerial refueling at one location. The mission is
assigned to a location for a specific time period and altitude to provide
airborne refueling of other air missions at this location (FLOMM, p. 12).
AirTankerCellAirspace is the
subclass of AirStations that are used by an AirTankerCellMissionPlan.
An AirTankerCellAirspace includes all of the locations for the
individual AirStationTankerMissionPlans that make up the cell.
AirTankerCellMission is the subclass
of ATOMissions that execute AirTankerCellMissionPlans.
AirTankerCellMissionPlan is a subclass of ATOMissionPlan. The air
tanker cell model is used for refueling missions that are composed of a
group of tanker missions. The formation of a cell allows the concentration
of missions in an assigned airspace by reducing the intercell mission
altitude separation for members in the cell. (FLOMM, pp. 14-15).
AirborneAlertMissionPlan is
a type of mission plan that applies when mission aircraft are equipped,
airborne, and ready for immediate action. Also called 'air alert'.
Diverse kinds of ATOMissionPlans may stand by on air alert as
AirborneAlertMissionPlans, including attack, reconnaissance, and
refueling plans.
AirborneBattleDirection is the
subclass of Managing processes carried out from an aircraft that is
equipped with communications, data link, and display equipment.
AirborneEarlyWarning is the subclass
of Communications involving the detection of enemy air or surface units
by radar or other equipment carried in an airborne vehicle, and the
transmitting of a warning to friendly units.
AirborneElementsTheaterAirControlSystemMission is the subset of
ATOMissions that are specified in an
AirborneElementsTheaterAirControlSystemMissionPlan.
AirborneElementsTheaterAirControlSystemMissionPlan is a subclass
of ATOMissionPlan. The Airborne Elements of the Theater Air Control
System (AETACS) mission model is used for air missions that provide
control capabilities beyond line of sight from the Ground Elements of the
Theater Air Control System (TACS). These missions provide early warning
(AEW) and command and control functions such as flight-following and air
battle direction (ABC). As a forward air control capability, they provide
the interaction with the supported forces and the controlled mission (FAC).
They are a subset of the station missions and as such inherit the
assumptions from that mission model with the additional information
concerning their control actions. (FLOMM, p. 37).
AircraftCarrier is the subclass of
Ships that are designed to house, transport, launch, and
retrieve MilitaryAircraft and their crews, with supporting ground
(i.e. deck) personnel.
AircraftCatapult is the subclass of
Devices that are designed to impel JetAirplanes off the decks of
AircraftCarriers.
AircraftLaunch is the class of events that
involve the TakingOff of a JetAirplane from an AircraftCarrier.
AircraftLaunches differ from TakingOff on land in that on the Ship
an AircraftCatapult is used to compensate for the short runway .
AircraftLaunchCycle is a subclass of
DeckCycle consisting of deck cycles during which AircraftLaunches are
performed.
AircraftOfTankerCell is a class
of Collections of all the MilitaryAircraft assigned to missions of
an AirTankerCellMissionPlan. Such a group is a way of considering
together all of the aircraft assigned to the different missions that
make up the AirTankerCellMissionPlan.
AircraftRecovery is the class of events
that involve the Landing of a JetAirplane on an AircraftCarrier.
AircraftRecovery differs from Landing on dry land in that on the Ship
an AircraftTripWire is used to compensate for the short runway.
AircraftRecoveryCycle is a subclass
of DeckCycle consisting of deck cycles during which AircraftRecovery is
performed.
AircraftRepositioning is a subclass of ATOMissionPlan. An aircraft
repositioning mission is the execution of a RepositioningMissionPlan.
AircraftTripwire is the class of Wire
devices installed on AircraftCarrier flight decks to catch the Tailhooks
of aircraft during landing in order to arrest their movement on the short
carrier runway.
AirdropMission is the subclass of
ATOMissions that are executions of AirdropMissionPlans.
AirdropMissionObjective is a
subclass of AirliftMissionObjective. Instances of AirdropMissionObjective
are goals for AirdropMissionPlans.
AirdropMissionPlan is a subclass of AirliftMissionPlan to which
all the conditions of AirMovementReSupplyMissionPlan also apply.
An Airdrop is a airlift mission objective which defines a leg segment of
an airlift mission. The mission releases supplies and personnel from the
aircraft at a specified location (i.e., air drop location) without
landing. (FLOMM, p. 35).
Airland is the subclass of Transportation
events which execute a leg of an AirliftMission in which the cargo or
personnel are delivered to their destination by a Landing. Contrast
with AirdropMission.
AltitudeBlock is the subclass of
AirTransitways reserved as ExclusiveUseAirspace, as for an
AirStationTankerMissionPlan. An Altitude block is defined by the
tanker altitude reservation above the tanker base altitude plus the
intercell or mission separation distance (FLOMM, p. 12).
ArmyTacticalMissileSystem is
a subclass of ModernMilitaryMissile. The Army Tactical Missile System
(ATACMS) covers a group of ground-based long-range guided missiles that are
fired from the Multiple Launch Rocket System M270 launcher.
A BuddyMissionStationSequence
is the part of a BuddyTankerMissionPlan during which the air refueling
is to take place. A BuddyMissionStationSequence consists of one or more
BuddyTankerOffloads.
BuddyTankerMission is the subclass of ATOMissions that are executions
of BuddyTankerMissionPlans.
BuddyTankerMissionObjective
is the subclass of AirTankerMissionObjectives that apply to
BuddyTankerMissionPlans.
BuddyTankerMissionPlan is a subclass of ATOMissionPlan. The buddy
tanker mission model follows the air station tanker mission model with the
exception that the tanker moves with the receiver aircraft much like an
Escort mission and provides refueling support to the associated group of
aircraft or missions only. (FLOMM, pp. 17).
A BuddyTankerOffload is the part of a
BuddyMissionStationSequence consisting of refueling at one location.
CarrierAircraft is the subclass of
military JetAirplanes that are designed for takeoff and landing on
board an AircraftCarrier.
CompositeAirOperations is the
subclass of ATOMissions which involves Managing of a named air route
allowing the safe flow of multiple missions through an air corridor.
CompositeAirOperationsMissionPlan is a subclass of ATOMissionPlan
and Managing. The composite air operations (COMAO) is a named route
with a Timing Reference Point (TRP) as part of the route. The COMAO allows
the flow of missions through a corridor and provides mission spacing and
safety separation. In support of these corridors, defense suppression and
jamming assets may be employed to allow for a COMAO to occur. Each COMAO
has an associated entry and exit points with the intervening points
described in the COMAO Plan and shown as Airspace Control Measures (ACMs)
in the Airspace Control Order (ACO). The active times of the COMAO are also
part of the plan and shown as effective times in the ACO. (FLOMM, p. 39).
CompositeAirOperationsRoute is the subclass of AirTransitways that are
associated with CompositeAirOperations.
ComputedAirReleasePoint is the
subclass of AtmosphericRegions where the first paratroop or cargo item
is released to land on a specified impact point (source: JEL).
ControlAndReportingCenter is
a subclass of MilitaryUnits that are subordinate air control elements of
the tactical air control center from which radar control and warning
operations are conducted within its area of responsibility (source: JEL).
CRC support to theater air operations includes radar surveillance and
tracking on a priority basis, direction of sector air defense, providing
radar service to tactical aircraft, supervision of subordinate deployed
air control units, and data link of a combined air picture to higher
headquarters (source: FAS).
ControlAndReportingElement
(CRE) is a subclass of MilitaryUnits that are subordinate air control
elements of the tactical air control center from which radar control
and warning operations are conducted within its area of responsibility.
CREs are similar to but smaller than ControlAndReportingCenters
(source: FAS).
DeckCycle is a subclass of Managing processes
which are subProcesses of NavyFlightOperations. A DeckCycle is a
process during which MilitaryAircraft are either launched or recovered
(but not both) on an AircraftCarrier.
DirectAttackGroundTargetMission is the subclass of
DirectAttackMissions which execute DirectAttackGroundTargetMissionPlans.
DirectAttackGroundTargetMissionPlan is a subclass of
DirectAttackMissionPlan. The ground attack model is used for missions
that approach a ground target to deliver ordnance on the target. Mission
types which may be DirectAttackGroundTargetMissionPlans include
InterdictionMissionPlans, OffensiveCounterAirMissionPlans, and
OffensiveAirSupportMissionPlans (FLOMM, p. 6).
DirectAttackShipTargetMission
is a subclass of DirectAttackMission. A DirectAttackShipTargetMission is
a mission that executes a DirectAttackShipTargetMissionPlan.
DirectAttackShipTargetMissionPlan is a subclass of DirectAttackMissionPlan.
The Ship Target model is used for a direct attack mission for which the intended
target is a ship. The mission model differs from the Ground Target model in that
the tasking contains additional data about the target's movement and location at
a specific time. Note: This requires the planner to investigate the specific
location for the attack if the time between target identification, i.e., 'as of'
time and the attack TOT exceeds about one hour (FLOMM, p. 8).
DropZone is the subclass of Regions upon which
airborne troops, equipment, or supplies are airdropped (source: JEL).
ElectronicCombatCorridorOperationsMission is the subclass
of ATOMissions that are executions of
ElectronicCombatCorridorOperationsMissionPlans.
ElectronicCombatCorridorOperationsMissionPlan is a subclass of
ATOMissionPlan. The Electronic Combat (EC) corridor operations
mission model follows the Escort mission model except for the additional
data contained in the ATO (6EWDATA[52] or CHAFF[56]) which provides
electronic combat tasking information for the mission aircraft to do their
EC corridor operations tasks. (FLOMM, p. 20).
ElectronicCombatStationMission is the subclass of ATOMissions that
are executions of ElectronicCombatStationMissionPlans.
ElectronicCombatStationMissionPlan is a subclass of ATOMissionPlan.
The Electronic Combat (EC) station mission model, whether collection
(e.g., ESM) or jamming (EW), follows the Station Air Location model except
for the additional data contained in the ATO (6EWDATA[52] or CHAFF[56])
which provides electronic combat tasking information for the mission
aircraft performing EC tasks. (FLOMM, p. 19).
FlightFollowing is the subclass of
Communications consisting of the task of maintaining contact with
specified aircraft for the purpose of determining en route progress or
flight termination (source: JEL).
ForwardAirControl is the subclass of
CommandAndControlProcesses that involve control from the air of aircraft
engaged in close air support of ground troops. See
ForwardAirControllerAirborne.
ForwardAirControllerAirborne is the subclass of agents who exercise
control from the air of aircraft engaged in close air support of ground
troops. Normally, the forward air controller (airborne) (or 'FACA') is
an airborne extension of the tactical air control party (source: JEL). A
ForwardAirControllerAirborne may be either a MilitaryUnit or an
individual MilitaryOfficer.
GroundAlertMission is the subclass of
ATOMission consisting of GroundAlertMissionPlans.
GroundAlertMissionObjective
is the subclass of MissionObjectives for maintaining ground alert.
During ground alert status, aircraft are on the ground (or deck) fully
serviced and armed, with combat crews in readiness to take off within a
specificed short period of time (usually 15 minutes) after receipt of a
mission order (source: JEL).
GroundAlertMissionPlan is
a type of mission plan that applies when mission aircraft are equipped
and ready for action, but not yet airborne. Diverse types of missions
may stand by on air alert as GroundAlertMissionPlans, including attack,
reconnaissance, and refueling plans.
GroundAlertMissionPlan is a subclass of ATOMissionPlan.
The ground alert mission model is very similar to the air location with
the exception that the location for the mission is a ground location and
the resource, although tasked, does not consume resources till scrambled
or committed. The aircraft and its aircrew are not available for additional
tasking during the alert period. The mission remains in an alert response
based on its tasked response time (e.g., 1 minute, 30 minutes, 1 hour)
posture from the on station time until the off station time. (FLOMM, p. 27).
GroundStationTankerMission is a subclass of AirliftMission.
A ground tanker mission is executed when a tanker or airlift aircraft
flies to a forward location, lands and then provides fuel to aircraft on
the ground at that location (i.e., FARP). A ground station tanker is
modeled as a special case of an airmove mission. (FLOMM, p. 36).
GroundStationTankerMissionObjective is a subclass of
AirliftMissionObjectives whose instances are goals of providing
ground tanker refueling.
GroundStationTankerMissionPlan is a subclass of AirliftMissionPlan.
A ground tanker mission model is used when a tanker or airlift aircraft
flies to a forward location, lands and then provides fuel to aircraft on
the ground at that location (i.e., FARP). A ground station tanker is
modeled as a special case of an airmove mission. (FLOMM, p. 36).
GroundTheaterAirControlSystem (GTACS) is a subclass of
ComputerBasedInformationSystems that are used to rapidly detect and
identify airborne targets with minimal or no outside support. GTACS are
deployed as either ControlReportingCenters or ControlReportingElements.
Battle management elements of a GroundTheaterAirControlSystem include
AirOperationsCenter, ControlAndReportingCenter,
ControlAndReportingElement, AirSupportOperationsCenter,
and TacticalAirControlParty (source: JEL).
GroundTheaterAirControlSystemMission is the subclass of ATOMissions
in which friendly ground units provide radar facilities or command and
control capability. See also GroundTheaterAirControlSystemMissionPlan.
GroundTheaterAirControlSystemMissionPlan is a subclass
of ATOMissionPlan. The GTACS are friendly ground units whose mission is
to provide command and control capability as Radar facilities such as the
Control and Reporting Center and Control and Reporting elements (CRC, CRE),
and Tactical Air Control Parties (TACP) providing FAC capabilities. These
units are identified to the controlled missions as their controlling
agencies. (FLOMM, p. 39).
IndividualLocationReconnaissanceRequestMission is the subclass of
ATOMissionPlans that are executions of
IndividualLocationReconnaissanceRequestMissionPlans.
IndividualLocationReconnaissanceRequestMissionPlan is a subclass of
ATOMissionPlan. The Individual Reconnaissance (RECCE) Request model is
used to task a RECCE asset to go to specific locations to gather specific
intelligence information. The type of RECCE dictates the form of the
product obtained by the mission. The RECCE request provides the specifics
of the information to be gathered and a portion of the request is
forwarded to the tasked organization in the ATO. The mission model is
similar to the Primary Attack but differs in that the tasking for a single
RECCE objective may encompass a series of locations (i.e., trace plot )
to perform its mission objective. (FLOMM, p. 30).
MissileWeaponAttackMission is
a subclass of ATOMission. A MissileWeaponAttackMission is one that
executes a MissileWeaponAttackMissionPlan.
MissileWeaponAttackMissionPlan is a subclass of
ATOMissionPlan. The missile weapon attack model is used for a standoff
attack where the fly out range of the weapons system employed against the
target exceeds a specific distance. With this weapon selection for the
target, the attacking aircraft does not fly to the target but stands-off
the flyout distance to release the weapon. There is then a launch point
described in the tasking of these missions. The target may be any facility
or unit (i.e. ground or ship targets) for which the SCL has identified an
air launched cruise class of munitions. (FLOMM, p. 10).
MissionEscortMission is the subclass of ATOMissions that are
executions of MissionEscortMissionPlans.
MissionEscortMissionPlan is a subclass of ATOMissionPlan. The escort
mission model is used when a mission provides escort support to another
mission. The missions usually associated with this objective are Defensive
Counter Air or Suppression of Enemy Air Defenses. The mission purpose is
to assist in assuring the accomplishment for supported mission objectives.
(FLOMM, p. 21).
MissionLegOfATOMission is the
subclass of Plans that constitute one segment of an ATOMissionPlan.
NavyFlightOperations is the
subclass of Managing processes that are performed by Navy flight deck
units to launch and recover aircraft on an $AircraftCarrier. Thus,
NavyFlightOperations involve a Ship as well as MilitaryAircraft.
NavyFlightOperationsMissionPlan is a subclass of ATOMissionPlan.
The Naval Flight Operations model serves to describe the scheduling of
aircraft missions from an aircraft carrier class. It is not a mission
employment model but is included to have a complete description of the
planning models for TBMCS. (FLOMM, p. 42).
NavyFlightOperationsPeriod
is the class of TimeIntervals during which NavyFlightOperations take
place or are planned to take place.
PackageEscortMission is a subclass
of ATOMission. A PackageEscortMission is a mission that executes a
PackageEscortMissionPlan.
PackageEscortMissionPlan is a subclass of ATOMissionPlan. The
PackageEscortMissionPlan is used when an escort mission supports an
escorted mission which is part of a package. The escort mission may be
separated from its original escorted mission to attach to a different
mission in the same or another package (FLOMM, p. 23).
ReceiveAerialRefueling is the
subclass of Plans that specify AerialRefueling events to take place
during the execution of ATOMissionPlans. These refueling events are
correlated with a plan to deliver fuel (see AirTankerMissionPlan).
ReconnaissanceRequest is the
subclass of Requestings that ask for IntelligenceAcquisition about
a specified objective.
RepositioningMissionPlan is a subclass of ATOMissionPlan. A
repositioning mission is a mission that flies to a landing location and
then starts a new mission. An example might be an A10A aircraft that
flies to a Forward Operating Location (FOL), lands, and becomes a Ground
Alert Close Air Support (GCAS) mission. (FLOMM, p. 32).
RouteValidation is the subclass of
ConstraintChecking in which fuel and time contraints are checked
against the aircraft route.
StationAirLocationMission is the subclass of ATOMissions that
execute StationAirLocationMissionPlans.
StationAirLocationMissionPlan is a subclass of ATOMissionPlan.
The Station Air Location Mission model supports missions which maintain an
orbit at a location. The mission may be in orbit to await further tasking
as an air alert mission (e.g., XCAS, XCAP, XDCA, XAR, and others) while
other missions are in orbit to perform their major mission objective (e.g.,
JSTAR, CAP, EW, ESM AEW, ABC, FAC, RECCE (collection), and others) from
the time on station until the time off station. The station missions
which perform control functions (AETACS) and are not on air alert are
addressed in the Control mission model. RECCE for specific location
requests, for example, BDA pinpoint, route RECCE, etc., are covered
in the Individual RECCE Collection Request mission model while RECCE
station collection is contained in this model. The mission models are
the same from the planning perspective for all air locations, the
associated ATO mission sets are dependent on the type of air mission.
These differences are specified in the ATO-98 Message Sets section below.
(FLOMM, p. 25).
StationCollectionReconnaissanceMissionPlan is a subclass of
ATOMissionPlan. The Station Collection Reconnaissance (RECCE)
mission model is the same as the StationAirLocationMissionPlan model
and supports reconnaissance (RECCE) missions that orbit to collect
intelligence data from a named airspace. The ATO tasking is to be
in the orbit at a specific altitude for the station times. The specific
collection requirements for the mission for security reasons may not be
disseminated in the ATO. (FLOMM, p. 29).
SurfaceToSurfaceMissileMissionPlan is a subclass of ATOMissionPlan.
The Surface-to-Surface Missile model is used for the TLAM and ATACMS
missiles which are under the command responsibility of the Joint Force Air
Component Commander (JFACC). (FLOMM, p. 42).
TomahawkLandAttackMissile
is a subclass of ModernMilitaryMissile. The Tomahawk Land Attack
Missile (TLAM) is a long-range, submarine or ship-launched cruise missile
used for attacking land targets or ships.
Timing Reference Point
AirMovementReSupplyMissionPlan is a subclass of AirliftMissionPlan.
The Air Movement Re-Supply mission model is used for airlift mission
objectives that deliver supplies and personnel to a base by landing at
that base to offload and/or onload materials. Unlike all other missions,
the air movement re-supply mission (airlift and support helicopter) have
multiple takeoffs and landings and the mission retains its mission number,
callsign and IFF/SIF modes and codes throughout all of the scheduled
mission takeoffs. (FLOMM, p. 33).
AirStationTankerMissionPlan is a subclass of AirTankerMissionPlan.
The Air Station (Non-Cell) Tanker mission model is used when the mission
objective is to perform aerial refueling at one location. The mission is
assigned to a location for a specific time period and altitude to provide
airborne refueling of other air missions at this location (FLOMM, p. 12).
AirTankerCellMissionPlan is a subclass of ATOMissionPlan. The air
tanker cell model is used for refueling missions that are composed of a
group of tanker missions. The formation of a cell allows the concentration
of missions in an assigned airspace by reducing the intercell mission
altitude separation for members in the cell. (FLOMM, pp. 14-15).
AirborneElementsTheaterAirControlSystemMissionPlan is a subclass
of ATOMissionPlan. The Airborne Elements of the Theater Air Control
System (AETACS) mission model is used for air missions that provide
control capabilities beyond line of sight from the Ground Elements of the
Theater Air Control System (TACS). These missions provide early warning
(AEW) and command and control functions such as flight-following and air
battle direction (ABC). As a forward air control capability, they provide
the interaction with the supported forces and the controlled mission (FAC).
They are a subset of the station missions and as such inherit the
assumptions from that mission model with the additional information
concerning their control actions. (FLOMM, p. 37).
AirdropMissionPlan is a subclass of AirliftMissionPlan to which
all the conditions of AirMovementReSupplyMissionPlan also apply.
An Airdrop is a airlift mission objective which defines a leg segment of
an airlift mission. The mission releases supplies and personnel from the
aircraft at a specified location (i.e., air drop location) without
landing. (FLOMM, p. 35).
BuddyTankerMissionPlan is a subclass of ATOMissionPlan. The buddy
tanker mission model follows the air station tanker mission model with the
exception that the tanker moves with the receiver aircraft much like an
Escort mission and provides refueling support to the associated group of
aircraft or missions only. (FLOMM, pp. 17).
CompositeAirOperationsMissionPlan is a subclass of ATOMissionPlan
and Managing. The composite air operations (COMAO) is a named route
with a Timing Reference Point (TRP) as part of the route. The COMAO allows
the flow of missions through a corridor and provides mission spacing and
safety separation. In support of these corridors, defense suppression and
jamming assets may be employed to allow for a COMAO to occur. Each COMAO
has an associated entry and exit points with the intervening points
described in the COMAO Plan and shown as Airspace Control Measures (ACMs)
in the Airspace Control Order (ACO). The active times of the COMAO are also
part of the plan and shown as effective times in the ACO. (FLOMM, p. 39).
DirectAttackGroundTargetMissionPlan is a subclass of
DirectAttackMissionPlan. The ground attack model is used for missions
that approach a ground target to deliver ordnance on the target. Mission
types which may be DirectAttackGroundTargetMissionPlans include
InterdictionMissionPlans, OffensiveCounterAirMissionPlans, and
OffensiveAirSupportMissionPlans (FLOMM, p. 6).
DirectAttackShipTargetMissionPlan is a subclass of DirectAttackMissionPlan.
The Ship Target model is used for a direct attack mission for which the intended
target is a ship. The mission model differs from the Ground Target model in that
the tasking contains additional data about the target's movement and location at
a specific time. Note: This requires the planner to investigate the specific
location for the attack if the time between target identification, i.e., 'as of'
time and the attack TOT exceeds about one hour (FLOMM, p. 8).
ElectronicCombatCorridorOperationsMissionPlan is a subclass of
ATOMissionPlan. The Electronic Combat (EC) corridor operations
mission model follows the Escort mission model except for the additional
data contained in the ATO (6EWDATA[52] or CHAFF[56]) which provides
electronic combat tasking information for the mission aircraft to do their
EC corridor operations tasks. (FLOMM, p. 20).
ElectronicCombatStationMissionPlan is a subclass of ATOMissionPlan.
The Electronic Combat (EC) station mission model, whether collection
(e.g., ESM) or jamming (EW), follows the Station Air Location model except
for the additional data contained in the ATO (6EWDATA[52] or CHAFF[56])
which provides electronic combat tasking information for the mission
aircraft performing EC tasks. (FLOMM, p. 19).
ExclusiveUseAirspace is a
TransitwayState attribute used to describe an area that can be
used by only one ATOMissionPlan.
GroundAlertMissionPlan is
a type of mission plan that applies when mission aircraft are equipped
and ready for action, but not yet airborne. Diverse types of missions
may stand by on air alert as GroundAlertMissionPlans, including attack,
reconnaissance, and refueling plans.
GroundAlertMissionPlan is a subclass of ATOMissionPlan.
The ground alert mission model is very similar to the air location with
the exception that the location for the mission is a ground location and
the resource, although tasked, does not consume resources till scrambled
or committed. The aircraft and its aircrew are not available for additional
tasking during the alert period. The mission remains in an alert response
based on its tasked response time (e.g., 1 minute, 30 minutes, 1 hour)
posture from the on station time until the off station time. (FLOMM, p. 27).
GroundStationTankerMissionPlan is a subclass of AirliftMissionPlan.
A ground tanker mission model is used when a tanker or airlift aircraft
flies to a forward location, lands and then provides fuel to aircraft on
the ground at that location (i.e., FARP). A ground station tanker is
modeled as a special case of an airmove mission. (FLOMM, p. 36).
GroundTheaterAirControlSystemMissionPlan is a subclass
of ATOMissionPlan. The GTACS are friendly ground units whose mission is
to provide command and control capability as Radar facilities such as the
Control and Reporting Center and Control and Reporting elements (CRC, CRE),
and Tactical Air Control Parties (TACP) providing FAC capabilities. These
units are identified to the controlled missions as their controlling
agencies. (FLOMM, p. 39).
IndividualLocationReconnaissanceRequestMissionPlan is a subclass of
ATOMissionPlan. The Individual Reconnaissance (RECCE) Request model is
used to task a RECCE asset to go to specific locations to gather specific
intelligence information. The type of RECCE dictates the form of the
product obtained by the mission. The RECCE request provides the specifics
of the information to be gathered and a portion of the request is
forwarded to the tasked organization in the ATO. The mission model is
similar to the Primary Attack but differs in that the tasking for a single
RECCE objective may encompass a series of locations (i.e., trace plot )
to perform its mission objective. (FLOMM, p. 30).
MissileWeaponAttackMissionPlan is a subclass of
ATOMissionPlan. The missile weapon attack model is used for a standoff
attack where the fly out range of the weapons system employed against the
target exceeds a specific distance. With this weapon selection for the
target, the attacking aircraft does not fly to the target but stands-off
the flyout distance to release the weapon. There is then a launch point
described in the tasking of these missions. The target may be any facility
or unit (i.e. ground or ship targets) for which the SCL has identified an
air launched cruise class of munitions. (FLOMM, p. 10).
MissionEscortMissionPlan is a subclass of ATOMissionPlan. The escort
mission model is used when a mission provides escort support to another
mission. The missions usually associated with this objective are Defensive
Counter Air or Suppression of Enemy Air Defenses. The mission purpose is
to assist in assuring the accomplishment for supported mission objectives.
(FLOMM, p. 21).
NavyFlightOperationsMissionPlan is a subclass of ATOMissionPlan.
The Naval Flight Operations model serves to describe the scheduling of
aircraft missions from an aircraft carrier class. It is not a mission
employment model but is included to have a complete description of the
planning models for TBMCS. (FLOMM, p. 42).
PackageEscortMissionPlan is a subclass of ATOMissionPlan. The
PackageEscortMissionPlan is used when an escort mission supports an
escorted mission which is part of a package. The escort mission may be
separated from its original escorted mission to attach to a different
mission in the same or another package (FLOMM, p. 23).
RepositioningMissionPlan is a subclass of ATOMissionPlan. A
repositioning mission is a mission that flies to a landing location and
then starts a new mission. An example might be an A10A aircraft that
flies to a Forward Operating Location (FOL), lands, and becomes a Ground
Alert Close Air Support (GCAS) mission. (FLOMM, p. 32).
StationAirLocationMissionPlan is a subclass of ATOMissionPlan.
The Station Air Location Mission model supports missions which maintain an
orbit at a location. The mission may be in orbit to await further tasking
as an air alert mission (e.g., XCAS, XCAP, XDCA, XAR, and others) while
other missions are in orbit to perform their major mission objective (e.g.,
JSTAR, CAP, EW, ESM AEW, ABC, FAC, RECCE (collection), and others) from
the time on station until the time off station. The station missions
which perform control functions (AETACS) and are not on air alert are
addressed in the Control mission model. RECCE for specific location
requests, for example, BDA pinpoint, route RECCE, etc., are covered
in the Individual RECCE Collection Request mission model while RECCE
station collection is contained in this model. The mission models are
the same from the planning perspective for all air locations, the
associated ATO mission sets are dependent on the type of air mission.
These differences are specified in the ATO-98 Message Sets section below.
(FLOMM, p. 25).
StationCollectionReconnaissanceMissionPlan is a subclass of
ATOMissionPlan. The Station Collection Reconnaissance (RECCE)
mission model is the same as the StationAirLocationMissionPlan model
and supports reconnaissance (RECCE) missions that orbit to collect
intelligence data from a named airspace. The ATO tasking is to be
in the orbit at a specific altitude for the station times. The specific
collection requirements for the mission for security reasons may not be
disseminated in the ATO. (FLOMM, p. 29).
SurfaceToSurfaceMissileMissionPlan is a subclass of ATOMissionPlan.
The Surface-to-Surface Missile model is used for the TLAM and ATACMS
missiles which are under the command responsibility of the Joint Force Air
Component Commander (JFACC). (FLOMM, p. 42).
(airLaunchPointOfATOPlan ?MISSIONPLAN ?LOCATION) means that in the
ATOMissionPlan ?MISSIONPLAN, a weapons launch is planned at the
GeographicArea ?LOCATION.
(aircraftRefuelsAircraft ?PROVIDER ?RECEIVER) means that the
MilitaryAircraft ?PROVIDER offloads fuel to the MilitaryAircraft
?RECEIVER.
(earliestTime ?EARLIEST ?TIMESET) means
that the TimePosition ?EARLIEST is the earliest time in the set of
TimePositions ?TIMESET.
(firstDepartureBase ?PLAN ?DEPLOC)
means that in the ATOMissionPlan ?PLAN, the first departure base is
the location ?DEPLOC.
(groundTargetOfATOMission ?MISSIONPLAN ?TARGET) means that in the
ATOMissionPlan ?MISSIONPLAN, the Object ?TARGET is a ground target.
(lastArrivalBase ?PLAN ?ARRLOC)
means that in the ATOMissionPlan ?PLAN, the last arrival base is
the location ?ARRLOC.
(missionAirdropLocation ?PLAN ?PLACE) means that in the air Plan
?PLAN, the mission aircraft is to complete an AirdropMission at the location
?PLACE. The location may be specified for a particular mission leg of an
AirMovementReSupplyPlan using the function MissionLegFn, e.g.,
(missionAirdropLocation (MissionLegFn ?NTH ?ATOPLAN) ?PLACE).
(missionLegArrivalBase ?LEG ?BASE) means that in the
MissionLegOfATOMission ?LEG, the assigned mission aircraft is tasked
to stop at the MilitaryAirport ?BASE.
(missionLegDeliverable ?LEG ?OBJECT) means that in the mssion leg or
leg segment ?LEG, the assigned mission aircraft are tasked to deliver or
airdrop ?OBJECT to the specified location.
(missionLegTimeIn ?LEG ?TIME)
means that in the mission leg or leg segment ?LEG, the assigned mission
aircraft is tasked to be at the stopover (or airdrop) point at or after
the TimeInterval ?TIME.
(missionLegTimeOut ?LEG ?TIME)
means that in the mission leg or leg segment ?LEG, the assigned
mission aircraft is tasked to leave the stopover (or airdrop) point
at or before the TimeInterval ?TIME.
(missionUtilizingCOMAOTimepoint ?PLAN ?ROUTE) means that the
MilitaryAircraft of the ATOMissionPlan ?PLAN utilize the
TimingReferencePoint ?TRP.
(requestNumber ?REQ ?SYMBOL) means that
the Requesting ?REQ has the SymbolicString ?SYMBOL assigned to it or
to the associated Request which it conveyed.
(shipAssignedToATOMission ?PLAN ?SHIP) means that the
NavyFlightOperationsMissionPlan ?PLAN includes an assignment for the
Ship ?SHIP. The ships assigned are AircraftCarriers.
(shipTargetOfATOMission ?MISSIONPLAN ?TARGET) means that in the
ATOMissionPlan ?MISSIONPLAN, the targeted Object ?TARGET is a Ship.
(tankerCellDuration ?CELL ?INTERVAL)
means that in the AirTankerCellMissionPlan ?CELL, the time period between
the tanker cell start and end times is the TimeInterval ?INTERVAL.
(totalAircraftInTankerCell ?CELL ?NUMBER) means that the total
number of aircraft involved in the AirTankerCellMissionPlan ?CELL is
the PositiveInteger ?NUMBER.