HPKB Movement Analysis Ontology
Draft of February 10, 1998
The following summarizes the main points of the partial ontology
developed by the Movement Analysis group participants in the second
HPKB Battlespace challenge problem SME meeting. The main shape of the
structure given below was worked out on February 6, 1998 by Eric
Domeshek, Eric Jones, John Gennari, Bill Long, myself, and the UMass
representative (my apologies for forgetting the name). I've added a
bit of annotation in spots, and based the following on notes taken by
Bill Long, myself, and John Gennari. I've revised some of the entries
as well, with annotations to explain the changes. This draft
supercedes the first draft advertised
earlier, mainly by adding information about spatiotemporal patterns of
movements, distinguishing military from nonmilitary units and
movements, and elaborating the structure of trends somewhat.
The main entities described below are reports, units, sites,
occupations of sites by units, movements, and trends. Each of these
entities may have internal and external parameters. This partial
ontology does not cover major areas including vehicles, weapons,
equipment, trafficability notions, etc.
The aim is that reports appear in the same form, whether they are
system inputs given in the stream of simulated intelligence reports or
system outputs given in the stream of notifications. Input reports
will provide order of battle information about relevant units,
information about known sites, and observations of vehicles,
movements, and sites. Output reports (notifications) will mainly
concern sites sites, movements, and trends. Input and output reports
may be partial. Input reports typically will identify the time at
which an event occurs with some precision. Output reports may start
out very partial and abstract, but be followed up by refined reports
of increasing detail and accuracy.
This ontology only covers most of the main points; some main points
and many details may have been omitted. Some are under development by
other HPKB groups.
- REPORTS of events
This form for reports needs to be elaborated to allow making
disjunctive reports that indicate a probability distribution (or
other weighting information).
- Report ID
- Report time
This is the time at which the report is issued. It
normally is no earlier than the time of the event being
reported. The time or duration of the event being
reported will be described in a manner appropriate to the
report subclass (e.g., occupations reported with a
duration, unit strength reported at some particular time).
Other subclasses may appear in simulated input stream,
the SASIS (Simulated All-Source Intelligence Stream)
Units may be either abstract, as in doctrine, or concrete, as in
units actually deployed. Concrete units will have properties
that vary with time, and the needed descriptions refer to both
properties holding initially of the unit and at the current (or
- Nominal or initial properties
This describes the order of battle (OB), the
constitution of the unit (OPCOM); types
of vehicles, equipment, personnel, the numbers
of each of these, and their command and control
A list of vehicle type/count pairs
Number of vehicles in unit.
Are there others?
- Mechanized infantry
- Actual or time-varying properties
A list of OPCONed units (often same as OB)
A list of vehicle type/count pairs
The current number of vehicles expressed as a
percentage of the initial number of vehicles.
- Battle position
- First echelon
- Second echelon
- Are there others?
This needs to be elaborated
This includes roads and road segments.
This may be either a point, line, or area, in GIS format.
- Terrain character
There is a large subvocabulary here for different
terrain characteristics, GIS type info.
The number of vehicles on site.
This is correlated with unit strengths by the
This includes revetments, drainage, etc.
Alphatech is developing a vocabulary for damage
- Command post
Battalions don't have rear command
posts, but division and corp echelons do.
- Special ammo
This means nuclear, chemical, or
- Field train
- Combat train
- Long range
- Multiple rocket launchers (MRL)
- Short range
- Surface to surface missles (SSM)
- Land based cruise missle (LBCM)
- Air defense artillery (ADA)
- Battle positions
Is this category of function placed
properly or needed?
- Tank units
- Mechanized units
- Combat engineer units
- Assembly/staging area
- Area of operations (AO)
- Major Supply Route (MSR)
This is a relation or reified association between units and
sites for periods of time. For example, one might report a
command post as an occupation of a site by a command company.
Movements have several main subtypes. Any of these subtypes may
exhibit the variety of properties.
The three dimensions of organized, military, and unit
can be combined as needed. Examples include military
convoys, police formations, and flight of civilians.
This indicates motion occurring in some regular
This includes police, firefighters, etc., as well as
- Unit movement
This subtype is for a unit moving in its entirety.
- Unit fragment
This subtype is for a part of a unit moving on its own.
Number of vehicles
List of vehicle type/count pairs
- List of sites
- Intermediate sites
- List of occupations
This list encodes ordering of sites occupied,
including both motion and rest.
- Start time
- End time
Put units into position
Move units to new positions to avoid targeting
Bring supplies to or from deployed units
- Qualitative type
- Traffic trend
A site that is a road segment
- Traffic volume
- Traffic speed
- Traffic congestion
Last modified: Mon Feb 9 15:19:40 EST 1998