DI-SESS-82368

Simulated Tactical Environment Algorithm Descriptions (STEAD)

This report provides a description of the model algorithms used to generate the performance of entities within a tactical simulated environment.

Approval DateJanuary 5, 2022

AMSC NumberN10287

Preparing ActivityAS

Project NumberSESS-2022-002

OPR—

DTIC ApplicableNo

GIDEP ApplicableNo

Limitation—

Applicable FormsNone

Approval Limitation—

Form Version—

DID Formatfree_text

963C CompliantYes

DISTRIBUTION STATEMENT A: Approved for public release; distribution is unlimited.

Supersedes

—

Description & Purpose

—

Application & Interrelationship

—

Use & Relationship

This report provides a description of the model algorithms used to generate the performance of entities within a tactical simulated environment.

This Data Item Description (DID) contains the format, content, and intended use information for the data deliverable resulting from the work task described in the solicitation.

Preparation Instructions

1Reference DocumentsThe applicable issue of the documents cited herein, including their approval dates and dates of applicable amendments, notices, and revisions, shall be as specified in the contract.

2FormatThis DID contains the format and content preparation instructions for the data product generated.

3ContentThe report shall contain the following:

3.1Record of ChangesIdentify the version, release date, and other relevant management and configuration control information associated with the current version of the document. Include a change history, highlighting changes from version to version.

3.2Table of Contents

3.3Acronym ListPresent the definitions of acronyms used in the report.

3.4PurposeExplain the overall purpose of the report.

3.5System OverviewPresent a general description of the system's operational and functional capability. An example breakdown for a simulated tactical environment may include:

3.5.1An overview of the environment

3.5.2An overview of the scenario as a whole

3.5.3An overview of the players and their objects

3.6Organization of SubsectionsMajor subsections of this report and the algorithms contained shall be organized as listed below. Each algorithm within the following subsections shall include the information defined in section 3.7 and its subsections.

3.6.1Player CharacteristicsThis section shall describe the descriptive data relevant to player entities. An example breakdown for this section may include:

3.6.1.1Radar cross section

3.6.1.2Infrared (IR) signature

3.6.1.3Target presented area

3.6.1.4Initial player object state vector

3.6.1.5Thrust, mass, and aerodynamic coefficients

3.6.2Motion Object FunctionalityThis section shall describe how the motion model works for each player class. An example breakdown for this section may include:

3.6.2.1Trajectory-based motion modeling

3.6.2.2Surface and ground motion

3.6.2.3Dead player motion

3.6.3Sensor ObjectsThis section shall describe the algorithms required to obtain simulated sensor performance, including the effects of the medium in which the sensor is operating. An example breakdown for this section may include:

3.6.3.1Sensor object overview

3.6.3.2Sensor control routine

3.6.3.3Sensor scan routine

3.6.3.4Sensor detection routine

3.6.3.5Sensor processing routine

3.6.3.6Specific sensor detection algorithms

3.6.4Weapon EffectsThis section shall describe the interactions of a weapon with a target, how probability of kill is determined based on the weapon, the target and its presented area, and the point of closest approach or miss distance. An example breakdown for this section may include:

3.6.4.1Miss distance

3.6.4.2Explosive weapons

3.6.4.3Gunfire lethality

3.6.5CountermeasuresThis section shall describe countermeasure functionality and algorithms used to model the effects of countermeasures on seekers. An example breakdown for this section may include:

3.6.5.1IR jammers

3.6.5.2Chaffs

3.6.5.3Flares

3.6.6Behavioral Role ModelsThis section shall describe the role models that determine the behavior of player entities that are in motion, controlling assets, or using assets. Examples of assets include sensors, countermeasures, weapons, etc. Each role model description shall include situation assessment, response selection, and command generation for that role model. An example breakdown for this section may include:

3.6.6.1Air player role model

3.6.6.2Surface/ground player role model

3.6.6.3Air defense network functionality for ground/surface role model

3.6.6.4Early Warning/Electronic Warfare (EW) site role model

3.6.7Other Subsections as RequiredThis section shall contain all descriptions and algorithms required for the simulated training environment that are not covered in one of the above subsections.

3.7Model Algorithm Description and DefinitionEach modeling algorithm shall contain the following:

3.7.1Name of the AlgorithmEach algorithm shall have a unique title or name with version control.

3.7.2AbstractPresent a brief overview and technical description of the algorithm.

3.7.3MethodologyDescribe the methodology of the algorithm in detail. Describe and explain the parameters, equations, and coordinate systems used for the computations. Present geometric/graphic illustrations, flow diagrams, force diagrams, and references that help improve understanding of the algorithm. Any equations, symbols, and general nomenclature shall follow the nomenclature standards used in American textbooks and professional journals.

3.7.4AssumptionsDescribe the assumptions made which the algorithm is based on.

3.7.5LimitationsDescribe the limitations for the algorithm and the operational impacts of these limitations.

3.7.6InterfacesDescribe how the algorithm interfaces with other algorithms or users for input and output.

3.7.7Analysis ResultsDescribe the expected results of all quantitative or qualitative analyses that must be performed.

3.8ReferencesIdentify all the citations for each reference document in the standard format (author(s), year, title, title of journal, volume number, page number, etc.).

References

—

Schema v3.0Community-maintained · Verify against ASSIST

Community-maintained — not an official government database.
Verify against ASSIST·GitHub·About·Disclaimer