8.1 - The Ground Vehicle Entity Behavior Model

Table of Contents

• 8.1.1 Core Elements of Ground Vehicle Entities
• 8.1.2 Component Systems that Make Up a Ground Vehicle
  • 8.1.2.1 A specific Example: BMP2
  • 8.1.2.2 Systems
  • 8.1.2.3 Other Simulation Components
    • Sensors
    • Controllers
    • Actuators

Ground vehicles are simulated as platform-level entities in VR-Forces.

Examples include M1A2, HMMWV, civilian vehicle, trucks, LCAC. They share a number of the same sub-systems (tracked-vehicle system, ballistic weapon system, damage, etc.).

8.1.1 Core Elements of Ground Vehicle Entities

Ground vehicles in VR-Forces share certain common elements. A typical ground vehicle in VR-Forces is always configured with the following:

• DtGroundVehicleStateRepository – Holds state information specific to ground vehicles
• DtSimIndividualLocalEntityNetInterface – Handles network publishing of individual (platform-level entities)

8.1.2 Component Systems that Make Up a Ground Vehicle

Ground vehicles also share many of the same systems and simulation components (sensors, controllers, and actuators). To examine the systems typically configured on a ground vehicle, we'll look at a specific instance of a ground vehicle, the BMP2 entity. It is a representative example that includes many of the common systems and components that make up ground vehicle.

Differences arise between the various types of entities as a function of which particular sub-systems are configured on the vehicle, and the parameter values it is configured with. For example, a civilian vehicle shares the same kinematics model as an M1A2, but it does not include a ballistic weapon system.

8.1.2.1 A specific Example: BMP2

Defined in parameter files BMP-2_AFV.entity and Ground_Vehicle.ope.

The figure below shows what systems and simulation components are configured as part of a BMP2 entity. The boxes (nodes) represent either a system of components (DtComponentSystem) or indivdiual DtSimComponent classes. The edges connecting the boxes indicate port or port group connections between components. Information such as detected targets and control inputs is exchanged between components through ports.

8.1.2.2 Systems

Major sub-elements of an entity's capabilities are organized into systems.

• Tracked Movement – The kinematics model for movement and the associated sensors and controllers that implement movement behaviors for tracked vehicles.
• Visual Sensor – What can I see?
• 30 mm Cannon – Ballistic gun
• Ground armor damage – Determine damage as a result of direct and indirect fire
• Spot Report Generator – Produce spot reports.
• Spot Report Receiver – Listen for spot reports.

8.1.2.3 Other Simulation Components

Individual DtSimComponents (not organized as part of a system) that make up the rest of entity:

Sensors

• DtUnderFireDeterminationSensor – Am I under fire?

Controllers

• DtOrganizationController – Maintain my position in the aggregate organizational hierarchy.
• DtLocalEntitySetController – Respond to DtSetDataRequest messages such as set location, set heading.
• DtContactFusionController – Fuse contact information from various sources into a single list.
• DtTargetSelectionController – Choose target for weapon system.
• DtOccupancyDirectorController – Allocate/reserve embarkation slots on the entity.
• DtEmbarkationController – Support entity's ability to embark on other entities.
• DtSendRadioMessageController – Send text or task messages through the radio.

Actuators

There are no actuators directly configured as part of this entity. However, actuators may be configured as part of the systems.

[Home] [Top of Page] [The Human Entity Behavior Model >>]