Information Technology Reference
In-Depth Information
Order-Event
The Order-event is sent to the warehouse manager agent and denotes
the receipt of a new order.
Additionally, endogenous events within single agents may occur.
A.2 Case study: Joint Fire Support
Joint Fire Support (JFS) is a military term for providing lethal
engagements in an ad-hoc manner in highly dynamic warfighting
scenarios. JFS requests are typically launched in tactical situations by
military ground units confronted with non-predictable threats which
can not be engaged by organic engagement means of these ground
units. JFS is realized by military engagement, reconnaissance and on
scene coordination means provided by army, air force and navy units.
These functional nodes are assigned and combined ad-hoc.
A typical JFS request shall be executed within few minutes in-
cluding the following tasks: determine adequate reconnaissance and
engagement assets, check rules of engagement, task and reposition
assets, collect and provide adequate target data, conduct and assess
the (lethal) engagement. A lot of military command nodes on dif-
ferent command levels may be involved in processing JFS requests
properly and in accordance with the given rules of engagement. As
JFS requests can not be exactly forecasted in time, target location or
class nearly everything has to be coordinated ad-hoc.
A variety of national coordination patterns has evolved in western
countries including israeli armed forces to handle this JFS prob-
lem domain. A coordination pattern describes the command and
control communication structure of command-, engagement- and
reconnaissance-nodes in order to collectively provide JFS services.
None of the existing coordination patterns seems to be adequate in
every situation. Each one has advantages as well as disadvantages.
An optimal JFS coordination pattern has to consider the extent and
landscape of the operational area of own forces, the amount of expec-
ted JFS requests, defined areas of responsibilities of command nodes,
