8.6 - The Subsurface Entity Behavior Model

Table of Contents

• 8.6.1 Core Elements of Surface Entities
• 8.6.2 Component Systems that Make Up a Subsurface Entity
  • 8.6.2.1 A specific Example: Los Angeles Class Submarine
  • 8.6.2.2 Systems
  • 8.6.2.3 Other Simulation Components
    • Sensors
    • Controllers
    • Actuators

Subsurface vessels are simulated as platform-level entities in VR-Forces.

These entities include manned submarines and unmanned submersible entities.

8.6.1 Core Elements of Surface Entities

Subsurface entities in VR-Forces share certain common elements. A typical subsurface entity in VR-Forces is always configured with the following:

• DtVrfMovingObjectStateRepository – Holds state information specific to subsurface entities.
• DtSimIndividualLocalEntityNetInterface – Handles network publishing of individual (platform-level entities).

8.6.2 Component Systems that Make Up a Subsurface Entity

Subsurface entities share many of the same systems and simulation components (sensors, controllers, and actuators). To examine the systems typically configured on a subsurface entity, we'll look at a specific instance of a ground vehicle, the LOS Angeles class submarine. It is a representative example that includes many of the common systems and components that make up a subsurface entity.

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 AN_BLQ-11_UUV.entity shares the same kinematics model as an LOS Angeles class submarine, but it does not include a weapon system.

8.6.2.1 A specific Example: Los Angeles Class Submarine

Defined in parameter files Los_Angeles-Class_Submarine.entity and Subsurface_Vehicle.ope.

The figure below shows what systems and simulation components are configured as part of a LOS Angeles class submarine. 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.6.2.2 Systems

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

• Subsurface movement system.
• Sonar sensor system.
• Torpedo launcher.
• Periscope system.
• Subsurface entity damage system.
• Spot Report Generator – Produce spot reports.
• Spot Report Receiver – Listen for spot reports.

8.6.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

• DtScriptMultiTaskController – The controller for scripted tasks.
• DtScriptReactiveTaskController – The controller for reactive scripted tasks.
• DtOrganizationController – Maintain my position in the aggregate organizational hierarchy.
• DtLocalEntitySetController – Respond to DtSetDataRequest messages such as set location, set heading.
• DtOccupancyDirectorController – Allocate/reserve embarkation slots on the entity.
• DtSendRadioMessageController – Send text or task messages through the radio.
• DtContactFusionController – Fuse contact information from various sources into a single list.
• DtTargetSelectionController – Choose target for weapon system.
• DtIndirectFireController – Processes fire for effect tasks.
• Depth controller

Actuators

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

[<<The Surface Entity Behavior Model] [Home] [Top of Page] [The Missile Entity Behavior Model >>]