8.5 - The Surface Entity Behavior Model

Table of Contents

• 8.5.1 Core Elements of Surface Entities
• 8.5.2 Component Systems that Make Up a Surface Entity
  • 8.5.2.1 A specific Example: DDG-51 Arleigh Burke
  • 8.5.2.2 Systems
  • 8.5.2.3 Other Simulation Components
    • Sensors
    • Controllers
    • Actuators

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

Examples include destroyers, aircraft carriers, speedboats, and sailboats. They share a number of the same sub-systems.

8.5.1 Core Elements of Surface Entities

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

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

8.5.2 Component Systems that Make Up a Surface Entity

Surface entities 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 surface entity, the DDG-51 Arleigh Burke entity. It is a representative example that includes many of the common systems and components that make up surface 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 generic surface vehicle shares the same kinematics model as an DDG-51, but it does not include a ballistic weapon system.

8.5.2.1 A specific Example: DDG-51 Arleigh Burke

Defined in parameter files DDG-51_Arleigh_Burke.entity and Surface_Ship.ope.

The figure below shows what systems and simulation components are configured as part of a DDG-51 Arleigh Burke 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.5.2.2 Systems

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

• Surface large ship movement system.
• Active radar sensor system.
• Sonar sensor system.
• Exocet Cruise missile vertical missile launcher.
• Vertical Missile Launcher system.
• Surface multiple hit damage system.
• MK45 Naval gun.

• Spot Report Generator – Produce spot reports.
• Spot Report Receiver – Listen for spot reports.

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

Actuators

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

[<< The Rotary-wing Entity Behavior Model] [Home] [Top of Page] [The Subsurface Entity Behavior Model >>]