DID FinderBack
Source
DI-MSSM-82158A

Synthetic Environment Database Design Document (SEDDD)

The SEDDD provides a detailed description of the design and content of the visual, sensor, and Semi-Automated Forces (SAF) databases used on a simulator, for verifying database content, designing training curriculums, and future improvements.

Approval DateOctober 27, 2022
AMSC NumberN10364
Preparing ActivityAS
Project NumberMSSM-2022-001
OPR—
DTIC ApplicableNo
GIDEP ApplicableNo
Limitation—
Applicable Forms—
Approval Limitation—
Form Version—
DID Formatfree_text
963C CompliantYes
DISTRIBUTION STATEMENT A: Approved for public release; distribution is unlimited.
Supersedes
DI-MSSM-82158
Related
—

Description & Purpose

—

Application & Interrelationship

—

Use & Relationship

The Synthetic Environment Database Design Document (SEDDD) provides a detailed description of the design and content of the visual, sensor, and Semi-Automated Forces (SAF) databases used on a simulator. The SEDDD is used to verify database content, design training curriculums, and as a reference for future database improvements.

This data item description (DID) contains the format, content, and intended use information for the data product resulting from the work task described in the contract Statement of Work.

This DID supersedes DI-MSSM-82158.

Preparation Instructions

1Reference documents.The applicable issue of the documents cited herein, including their approval dates and dates of any applicable amendments, notices, and revisions, shall be as specified in the contract.
1.1Common Image Generator Interface (Version 3.3)(Copies of documents are available online at http://sourceforge.net/projects/cigi/files/ ).
1.2NPSI-1019-002.2 - NAVAIR PORTABLE SOURCE INITIATIVE (NPSI) DATA PREPARATION STANDARD (DPS)(Version 2.2, dated 22 May 2012), (Copies of this document are available online at http://www.dtic.mil/docs/citations/ADA570726 or from Naval Air Warfare Center, Training Systems Division, Code 4625, 12350 Research Parkway, Orlando, FL 32826-3275.).
2Format.Contractor format is acceptable while the document outline shall follow Section 3.5.
3Content.The SEDDD shall contain the following sections:
3.1The SEDDD shall have a title page providing the following information, as applicable:
3.1.1Document number;
3.1.2Version/revision indicator;
3.1.3Security markings or other restrictions on the handling of the document;
3.1.4Date;
3.1.5Document title;
3.1.6Name, abbreviation, and any other identifier for the systems, subsystems, or items to which the document applies;
3.1.7Contract number;
3.1.8Contract data requirements list (CDRL) item number;
3.1.9Organization for which the document has been prepared;
3.1.10Name and address of the preparing organization;
3.1.11Distribution statement;
3.1.12Signature blocks for the developer representative authorized to release the document, the acquirer representative authorized to approve the document, and the dates of release/approval.
3.2Revision history page.
3.3Table of Contents and List of Figures.
3.4Acronym list.
3.5Document detail:
3.5.1Introduction (to an introduction explaining the overall approach to the database development and top level description of content and fidelity).
3.5.2Database projection.
3.5.3Task regions/Operating areas.
3.5.3.1A complete list and description of new, modified, and unmodified task region/operating areas that are in the database and used on the trainer.
3.5.3.2Geographic region definition.
3.5.4Airfields.
3.5.4.1A complete list and description of new, modified, and unmodified airfields that are in the databases.
3.5.4.2Definition of airfield types (primary, secondary, divert, generic, etc.) and the features included in each type of airfield model.
3.5.4.3List all runway and taxiway features (landing thresholds, elevation, length, width, heading, FLIP chart, landing aids, lighting, signage, arresting gear, wind socks, helipads, carrier boxes, beacon, building locations, etc.) at each airfield.
3.5.5Low-level /TERF/Course rules routes.
3.5.5.1A complete list and description of new, modified, and unmodified low-level routes that are in the databases.
3.5.5.2Geographic region definition.
3.5.5.3Identify way point features along routes, including screenshots.
3.5.5.4Definition of the features included in the route areas.
3.5.6Landing areas/CAL sites.
3.5.6.1A complete list and description of new, modified, and unmodified landing areas that are in the databases.
3.5.6.2Definition of the features included in the landing areas.
3.5.6.3Definition of the type of landing zone/CAL site (wooded, ridgeline, open, parking lot, baseball/football field, helipad, oilrig, etc.).
3.5.7Urban areas.
3.5.7.1A complete list and description of new, modified, and unmodified urban areas that are in the databases.
3.5.7.2Geographic region definition.
3.5.7.3Definition of the features included in the urban areas.
3.5.8Target/Range areas.
3.5.8.1A complete list and description of new, modified, and unmodified target areas that are in the databases.
3.5.8.2Geographic region definition.
3.5.8.3Definition of the features included in the range areas.
3.5.9Cultural models.
3.5.9.1A complete list and description of the generic and geo-typical feature library used to populate the synthetic environment databases.
3.5.9.2A complete list and description of the geo-specific/Landmark feature library used to populate the synthetic environment databases.
3.5.10Moving models.
3.5.10.1A complete list, description, and screenshot of new, modified, and unmodified moving models that are used on the trainer, to include models built into the terrain (ex. drawbridges).
3.5.10.2Intended use of each moving model (e.g., OTW, FLIR, EO, NVG, and Radar).
3.5.10.3Model mapping definition/ID and correlation across all synthetic environment databases.
3.5.10.4Detailed design and control for model damaged and destroyed states.
3.5.10.5A complete list and description of articulated parts, controls, ship hull numbers, country, etc. associated with each model.
3.5.10.6Definition of how the model articulations are identified and controlled in the model to include control method, naming convention, units, valid range, and other specific details.
3.5.10.7Definition of model levels of detail (LOD) to include number of levels, polygon/lights per LOD, switching ranges, identification of light naming convention and control.
3.5.11Sensor simulation.
3.5.11.1Sensor terrain database design and development criteria and information.
3.5.11.2Sensor material encoding data for the database and models.
3.5.11.3Sensor 3D model design, development, and control criteria and information.
3.5.11.4Correlation details.
3.5.12Radar simulation.
3.5.12.1Radar terrain database design and development criteria and information.
3.5.12.2Radar target model design and development criteria and information.
3.5.12.3Synthetic Aperture Radar (SAR) design and development criteria and information.
3.5.12.4Inverse SAR (ISAR) design and development criteria and information.
3.5.12.5Radar material encoding data for the database and models.
3.5.12.6Correlation details.
3.5.13Semi-Automated Forces (SAF) database.
3.5.13.1Terrain database design and development criteria and information.
3.5.13.2Shape files, vector data, and point feature design and development criteria and information.
3.5.13.3Material encoding data for the database and models.
3.5.13.4Entity model definition and design information.
3.5.13.5Correlation details.
3.5.14Test and alignment patterns.
3.5.14.1A complete list and thumbnail of all provided patterns.
3.5.14.2Design and development criteria and information.
3.5.15Animations and special effects.
3.5.15.1A complete list, thumbnail, and description of all image generator provided animations and special effects.
3.5.15.2Design and development criteria and information.
3.5.16Simulation maps.
3.5.16.1A complete list and description all provided or generated maps and their source.
3.5.16.2Provide all map geographic region definition and features.
3.5.16.3Provide all design and development criteria and information used to create the maps.
3.5.16.4Correlation details.
3.5.17Synthetic environment database build process (visual and sensors).
3.5.17.1Process used to create run-time versions of the synthetic environment databases.
3.5.17.2Terrain and model runtime naming conventions.
3.5.18Software, scripts, supplemental files, configuration files, and tools used in the creation of the synthetic environment databases.
3.5.19Data license and right information.
3.5.19.1Data License/Rights for all source data, NAVAIR Portable Source Initiative (NPSI) data, and runtime databases.
3.5.20A complete list and description of the synthetic environment deliverables.
3.5.21Synthetic environment database integrated product team (IPT) meeting minutes.
3.5.22NPSI description to include import, export (new or modified areas), and any issues/concerns.
3.6The following content shall be included within the above sections:
3.6.1Source data.
3.6.1.1Maps of the entire geographic regions depicting the various resolutions of imagery and coverage and material encoding/classification.The map shall utilize color coded outlines and color coded points to indicate coverage throughout the geographic region.
3.6.1.2Resolution, source, and acquisition date of new, reused, and modified imagery.
3.6.1.3Resolution, source, and acquisition date of new, reused, and modified terrain elevation information.
3.6.1.4Resolution, source, and acquisition date of new, reused, and modified shape files, vector data, and point feature information.
3.6.1.5Resolution, source, and acquisition date of new, reused, and modified 3D model information.
3.6.1.6Resolution, source, and acquisition date of new, reused, and modified material encoding data.
3.6.1.7Notes detailing suitability analysis of Government Furnished Information (GFI) data (NPSI, SECORE, NGA, etc.).
3.6.1.8Notes detailing any changes and adjustments to the GFI data.
3.6.1.9List and description of all GFI data used.
3.6.2Design data on all airfields, target regions and low-level routes shall be included along with photos, graphics and charts.
3.6.3Features.
3.6.3.1Thumbnail pictures of moving models, geo-specific/landmark/navigation features, animations, and special effects.
3.6.3.2For each moving model, a list of the articulated parts, lights and their associated controls to include Instructor Operator Station (IOS) and host controls.
3.6.3.3A complete list and description of all airfield lights and light groups and their associated controls to include Instructor Operator Station (IOS) and host controls at each airfield.
3.6.3.4A complete list and description of all light groups and their associated controls to include Instructor Operator Station (IOS) and host controls.
3.6.3.5Describe and list all flight deck director controls to include Instructor Operator Station (IOS) and host controls.
3.6.3.6Latitude and longitude coordinates for geo-specific/landmark/navigation features.
3.6.3.7Photos, graphics and charts used to create cultural features and models.
3.6.3.8Describe and list light maps, water masks, and coastline data used for the development of the database.
3.6.3.9Scene content management and level of detail information for terrain, features and models.

References

Copies of documents are available online at http://sourceforge.net/projects/cigi/files/

Copies of this document are available online at http://www.dtic.mil/docs/citations/ADA570726

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