sub-symbolic level, through specific procedures.
The “situation” Ontology. Once the domain
ontology has been populated, we can use our knowl-
edge on the scenario to identify the set of Relevant
Situation classes (see Sec.2), and organize them in
a second taxonomy. Each relevant situation class is
defined with constraints expressed in DL formalism,
using the terms (concepts, relations) included into
the domain ontology. Note that these definitions are
not rules expressed in an external formalism, but
DL defined concepts (rules are not included in the
system).
At this point, we are able to use automatic reasoning
and DL capabilities (Nardi and Brachman, 2003)
on the available knowledge to classify the current
situations instances. Now, the assessment of the
situation is simply the most specific classification of
each situation instance among the relevant situation
classes.
From the point of view of the extensional knowledge,
we must address carefully the creation of the correct
number of situation instances. We decided to have
as many situation instances as many independent
circumstances are present in the world, and examine
them separately. In this way, different aspects of
the same global situation are perceived as different
instances. Moreover, separating independent situa-
tion instances gives us a substantial advantage when
we would start dialogues among different agents to
compare their classifications.
Defining the right number of situation instances is
not easy to solve. For example, if we would declare
different situation instances for each location of
the environment, then we would not be able catch
those relationships (situation classes) which are
aggregation of events in different locations. The
solution we propose consists in identifying a subset
E of event classes which trigger the generation of
a new situation instance. When a new event e
i
∈ E
is detected, a new situation instance s
i
is created, is
declared as being a member of the generic Situation
class, and it is connected through a relation (hasOb-
ject in Fig.1) with the event e
i
. Whenever events are
detected and for agent p verify the definition of a
certain situation class S, s
i
is classified as member of
S, and K
p
(s
i
∈ S) holds.
4 VALIDATION IN A HARBOUR
SURVEILLANCE SCENARIO
Experiments have been performed on a middle size
italian harbour, in which an average of 80 vessels
Figure 2: A splitting situation. Two boats (red circles) per-
formed a splitting close to a surveilled area (red arc) and
one of them is directed to the critical point (in purple).
(military or civil) were moving at the same time with
different goals. A radar was able to perceive on a
10km x 10km area.
We considered 2 suspect operations to be detected:
Splitting: it is the manoeuver of remaining hidden
staying close to another vessel, then suddenly move
away directed to a critical area (see Fig.2).
Suspect Approach: it is verified if a suspect vessel
is approached by other vessels. A suspect vessel is a
vessel whose identification is not known, which stays
near the border of a surveilled zone.
We compared the performances of human opera-
tors, provided with 5 different support systems. Every
test session had a lenght of about 15 minutes.
In the first configuration, that we will call Agent
Support, we provided the operator with the agent
based system which performs autonomous Situation
Assessment as described in this paper. The situa-
tion Splitting is defined by the constraint “classify as
member, if and only if current situation contains a
track, which was first detected close to a zone bor-
der and close to another vehicle, and either one or the
other vehicle approaches a critical area”, expressed
with the DL formalism.
Whenever a vehicle v
1
is detected as appear-
ing close to another vehicle v
2
, a new situation in-
stance s
v
1
is created, and it is populated the relation
hasObject(s
v
1
, v
1
). When the other properties which
are in the definition are verified, s
v
1
will be classified
as splitting. A similar constraint is used for the class
suspect approach.
The 4 other configurations are:
No Support: the operator is provided with the out-
put of a multi-tracking system, with no elaboration to
support Situation Assessment.
Still Tracks Visualization: the system provides an
additional information, visualizing the still vehicles
with a different colour.
Story Vis: the system graphically shows also the tra-
jectory, average and current speed.
1/3 Tracks: the same as the previous policy, but the
AGENT APPROACH TO SITUATION ASSESSMENT
289