Attachment 5 WDZ Tool Software Vol IV.pdf

PDF 957 KB Posted

Attached to
Range Managers Tool Kit Federal contract opportunity
Solicitation number
M67854-22-R-7905
Issued by
United States Marine Corps

View the file

Other files for this federal contract opportunity

Other files attached to Range Managers Tool Kit, newest first.
File Type Posted
Attachment 8_TEP Total Evaluated Price.xlsx XLSX spreadsheet
Amendment 1_M67854-22-R-7905 RMTK.docx DOCX document
Attachment 9 Staffing Planv2.xlsx XLSX spreadsheet
RFP M67854-22-R-7905-Questions.xlsx XLSX spreadsheet
Solicitation.docx DOCX document
Attachment 2 NAVSEA_OP-5_Rev7_OP_5.pdf PDF
Attachment 8 Total Evaluated Price.xlsx XLSX spreadsheet
Attachment 7 DD254 _RTAM_Solicatation 21 June 2022.pdf PDF
Attachment 1 MCO 3550.9A.pdf PDF
Attachment 3 TC 25-8.pdf PDF
Attachment 4 ARSP-2 VOLI EDB V1 E (2470).pdf PDF
Attachment 4 continued ARSP-2 Vol II Edition A Version 1 Draft 4.pdf PDF
Attachment 6 RMTK Mobile Assessment_9-29-17_Final.docx DOCX document
Show all 13

On GovTribe

Work with this file on GovTribe

  • Download the original file
  • Contacts named in this file
  • Similar government files
  • Ask GovTribe AI about this file

Text version

For Official Use Only

Weapon Danger Zone Tool Software Specification Document

Volume VI – Graphical User Interface Versions 10.6.1.0.6/10.8.1.0.2

Last Updated: March 2022

This document has been approved for documentary release to the government(s) of _______________________ (or members of The Technical Cooperation Program (TTCP) (which include the United Kingdom, Canada, Australia and New Zealand).

It is not the intention of the US Marine Corps or the US Government to provide information, technology, training or education without concurrence or approval from appropriate organizations, departments or agencies, per the governing US Laws, National Disclosure Policy, and Department of Defense policy and directives.

This information is furnished upon the condition that it or knowledge of its possession will not be released to another nation without specific authority from the U.S. Marine Corps; that it will not be used for other than military purposes; that individual or corporate rights originating in the information, whether patented or not, will be respected and; that the information will be provided the same degree of security afforded it by the Department of Defense of the United States. Regardless of any other markings on this document, it may not be declassified or downgraded without the written approval of the originating U.S. agency.

(WARNING - This document contains technical data whose export is restricted by the Arms Export Control Act (Title 22, U.S.C., Sec 2751, et seq.) or the Export Administration Act of 1979 (Title 50, U.S.C., App. 2401 et seq.), as amended. Violations of these export laws are subject to severe criminal penalties. Disseminate in accordance with provisions of DoD Directive 5230.25.

Record of Changes *A - Added M - Modified D – Deleted

Version Number Date

Number of Figure, Table, or Paragraph

A* M D

Title Or Brief Description Change Request Number

1.0 02/20/2017 Baseline

2.0 11/04/2020 ALL M Complete Rewrite

3.0 10/14/2021 ALL M Update to Version 10.6.1.0.5

Section 2.4.1 M Added Individual Risk M Added firing area buffer Section 2.4.2 M Added target line buffer

4.0 03/10/2022 ALL M Update to Version 10.6.1.0.6/10.8.1.0.2

Weapon Danger Zone Tool

These documents define the Weapon Danger Zone Tool versions 10.6.1.0.6 configuration and test plan to reflect Weapon Danger Zone Tool software as delivered to United States Marine Corps

Range and Training Area Management.

Document Created 20 February 2017

Prepared For:

United States Marine Corps Training and Education Command

Range and Training Area Management

Contract Numbers: M67854-20-F-3003

PROPRIETARY INFORMATION

Distribution authorized to U.S. Government agencies and their contractors for administrative or operational use. Other requests for this document must be referred to Commanding General, U.S. Marine Corps Training and Education Command, ATTN: Range and Training Programs Division, RTAM Branch, Quantico, VA 22134.

Revision History

Originated By: WDZ Configuration Manager

Approved By: WDZ Project Leader

Accepted By:

Document Status: Delivered Documentation

This Page is Intentionally Left Blank

Table of Contents

2. Application Requirements and Setup

2.1 Application Setup

2.2 User-Input Data

2.3 Tool Output Data

2.4 Geographic Features

2.4.1 WDZ Geometry

2.4.2 Target Geometry

2.4.3 Area of Critical Control (ACC) Geometry

3. Risk

3.1 Risk Analysis

3.2 Point Risk

3.3 Off-Range Risk

4. Batch Tool

5. Move/Rotate Tool

6. Adjustments Tool

7. Update Magnetic Declination Tool

8. Terrain Mitigation Tool

9. Layout WDZ

10. Other Non-model related functions

Appendix A: Glossary ............................................................................................................................. A-1

Appendix B: Acronyms .......................................................................................................................... B-1

Appendix C: Data Dictionary.......................................................................... Error! Bookmark not defined.

Input Database: ......................................................................................... Error! Bookmark not defined.

Output Database (and Standard Export Database): ................................. Error! Bookmark not defined.

Army SDSFIE Output Database: .............................................................. Error! Bookmark not defined.

USMC SDSFIE Output Database: ............................................................ Error! Bookmark not defined.

RFMSSOutput Database: ......................................................................... Error! Bookmark not defined.

1. Introduction

1.1 Purpose

The Weapon Danger Zone (WDZ) Tool is a software application that currently runs as an ArcMap extension. The WDZ Tool allows the user to create and modify custom Weapon Danger Zones (WDZs). The WDZ engine is defined in Volumes I, II, III, IV & V. The User Interface is defined in Volume VI.

A Weapon Danger Zone (WDZ) is defined as a three-dimensional region that encompasses the ground and airspace required for horizontal and vertical containment of impact and post- impact effects (i.e. projectiles, fragments, debris, and components) resulting from the firing, launching, release and /or detonation of aviation-delivered ordnance. This three-dimensional zone accounts for weapon accuracy, failures, ricochets, and broaches/porpoising of a specific weapon/munition type delivered by a specific aircraft type. WDZs represent the minimum safety requirements designed for aviation weapons training on DoD ranges.

1.2 AIM

Weapon Danger Zones are classified by weapon type and aircraft type; the general principles described here apply to air-to-ground weapon systems. The aim of this document is to describe the general principles as applied with each weapon system in the development of the appropriate

WDZ.

1.3 Scope

This document along with the associated documents as defined in paragraph 1.4 applies to the development of the WDZ Tool.

1.4 Related Documents

This is one of a series of documents that are concerned with the development of WDZs for a variety of weapon systems for use on training ranges. The following is a list of the current Software Development Documents for WDZ:

WDZ Tool Software Development Specification Volume I – Source Code & Project Overview WDZ Tool Software Development Specification Volume II – Data Cube WDZ Tool Software Development Specification Volume III – WDZ Specifications WDZ Tool Software Development Specification Volume IV – Requirements WDZ Tool Software Development Specification Volume V – Test Plan WDZ Tool Software Development Specification Volume VI – User Interface

1.5 Glossary and Acronyms

A glossary and list of acronyms used in this document are provided in Appendices A and B, respectively.

2. Application Requirements and Setup The WDZ Graphical User Interface extension is programmed using industry standard .NET COM object classes. Microsoft .Net Framework 4.5 is required.

The WDZ Setup Tool defines the geographic projection for the WDZs, sets default selections and identifies where the output data is to be saved.

2.1 Application Setup

The projection must be set on the map’s data frame before the application setup tool can be completed. Each setup configuration can have its own output database. Multiple configurations can be setup on a single map. Multiple configurations can use a shared output database.

The instructions and requirements to complete the WDZ Setup configuration can be found in the WDZ User’s Manual on the “Setting up WDZ” page.

All setup information is saved to C:\Users\Public\RMTK\WDZ\wdzConfig.XML. This XML file is used by both the WDZ Tool and ArcMap applications.

Upon completion of the WDZ Setup function the tool will validate that the user’s database has been updated to the current version installed. This is performed by verifying the current version in the code with the data contained in the db_version field of the Version table in the selected output database. The user will be prompted to update if these versions do not match.

2.2 User-Input Data

The user-selected aircraft and weapon determine the workflow to generate the WDZ. The Graphical User Interface is driven by flags set in the input database based on the aircraft and/or weapon selected.

Most dialog changes or messages are controlled by the CustomCreateDialogModifier field value for the selected aircraft and weapon in the lnk_Aircraft_Weapon table. The CustomCreateDialogModifier value is defined in the ddl_CustomDialog table.

There are various other database flags that display messages or alter workflow based on specific aircrafts and/or weapons. If a flag is weapon-specific, such as “IsHellfire”, it can be found in the lst_Weapon table. If a flag is aircraft-specific, such as “IsRolltipoff”, it can be found in the lnk_Service_Aircraft table. Flags that can vary by aircraft/weapon platform, such as “IsSidefire”, can be found in the lnk_Aircraft_Weapon table. A complete list of flags can be found in the Data Dictionary.

The Event list is displayed based on the EventType field value in the lnk_Aircraft_Weapon table for the selected aircraft and weapon. The Event list is populated from the lnk_EventType_Event table for the EventType selected.

If the selected weapon has both a live (“LiveRad”) and inert (“EffectiveRad”) radius in the lst_Weapon table then both the Live and Inert options will be available. If LiveRad is null then the weapon can be Inert only. If EffectiveRad is null then the weapon can be Live only.

The “Weapon Info” button returns the file name from the InfoFileName in the ddl_CustomDialog table using the CustomCreateDialogModifier value for the selected aircraft and weapon. It then opens the corresponding .rtf file located in the installation folder at “\RMTK\RMTK Weapon Danger Zone Tool\Bin\Templates”. The “Weapon Info” button is only visible when a file is available for the selected weapon.

The “IsLinearReleaseEnabled” flag is set in the lnk_Aircraft_Weapon table for aircraft/weapon combinations that have linear firing area capability.

IsLinearReleaseEnabled

Value Options

1 Strafe and Linear Door Gunnery 2 Strafe is NOT available

3 AGR-19

Release Angle is not available for Linear Door Gunnery or AGR-19.

Some weapons require a Launch mode selection. These options are currently hard-coded in the source code.

The weapon description that displays below the weapon selected is populated from the “Model Display Name” field of the lst_Weapon table for the selected weapon.

Maximum Weapon Altitude for AGR-19 and AGR-20s is calculated using the MaxAltitude field value in the lst_Weapon table; all others are calculated by the WDZ engine.

The hover fire option is displayed if the HoverFire flag in the lnk_Aircraft_Weapon table is selected for the selected aircraft and weapon.

The input data is assembled in a data structure that is passed as an argument in a wdzEngine.dll function. The wdzEngine core simulation is a registered COM dynamic link library.

2.3 Tool Output Data

The output for a WDZ consists of geographic features and attribute data. The geographic features are two-dimensional points, lines and polygons.

WDZ polygon features are saved to the mil_surface_danger_zone_area feature class. Most WDZs will contain a corresponding firing area in the firing_area feature class. WDZs on line and area targets will only contain a firing point in the firing_point feature class. Legacy and String of bombs will have no firing area indicator included. Hellfire weapons with a single run-in heading will have designator lines, which are saved in the mil_surface_danger_zone_line feature class.

Targets can be created as a point, line or polygon feature. The geographic features for targets are saved to the military_target_point, military_target_line or military_target_area feature classes.

Areas of Critical Concern (ACCs) can be created as a point, line or polygon feature. Point and Line ACCs are created by buffering a selected point or line, making all ACCs area features. The geographic features for ACCs are saved to both the acc_area feature class with a point placed at the centroid in the acc_point feature class.

Attribute data consist of user-selected data and tool generated data to create and identify the features.

2.4 Geographic Features

2.4.1 WDZ Geometry

2.4.1.1 WDZs

WDZ Geometry Features are created by the WDZ engine. WDZ creation is based on the user-selected parameters and the weapon data. Creation of WDZs is defined in Volumes II and III.

Different weapons have different parameters. All tool generated data and user-selected data is saved to the wdz_parameters_input table. The WDZ graphic is saved to the mil_surface_danger_zone_area feature class where the sfdzone_id equals the wdz_id from the wdz_parameters_input table.

Individual Risk WDZs can be created for specific aircraft and weapons. Individual Risk WDZs require a risk type, number of rounds and number of participants be identified.

Individual Risk data is saved to the wdz_parameters_input table. The selected Risk Type is converted to a number and saved to ir_risk_type. Rounds per Event is saved to ir_rounds_per.

Number of Participants at Risk is saved to ir_participant_count.

Risk Type Numeric value Deaths per Event 1 Deaths per Year 2 Deaths per Person-Year 3

2.4.1.2 Firing Areas

Creation of firing area features depends on the type of WDZ or the weapon selected. If the “CustomLaunchRegion” in the lnk_Aircraft_Weapon table value is greater than zero then the firing area is generated by the WDZ engine.

If CustomLaunchRegion equals zero and the WDZ is placed on a point target the firing area is created as follows:

a. Create a circular arc using the target point as the center and the minimum release range as the radius.

b. Create a second circular arc using the target point as the center and the maximum release range as the radius.

c. Create a line along the left run-in heading that begins at the target point and has a length greater than the maximum release range.

d. Create a line along the right run-in heading that begins at the target point and has a length greater than the maximum release range.

e. Trim the lines and circular arcs at the 4 points of intersection to create a polygon. This polygon is the firing box.

i. In cases where the left and right run-in headings are the same, a width of one mil is used so that an area can be created.

ii. In cases where the minimum and maximum release ranges are the same, a depth of 10 feet is used so that an area can be created.

Firing areas are saved to the firing_area feature class where sfdzone_id equals the wdz_id from the wdz_parameters_input table.

Firing points are saved to the firing_point feature class where the sfdzone_id equals the wdz_id from the wdz_parameters_input table.

2.4.1.2.1 Offset Firing Area

An offset firing box is defined as a firing box where the standard inputs are extended to the left and/or right by the specified offset. Some weapons require an offset distance while some require an offset angle.

2.4.1.2.1.1 Distance Offset

The firing box is constructed the same as the firing area with these exceptions:

a. The lines created along the run-in headings are offset to the left and/or right by the specified offset distances (the left heading line is offset by the left offset distance and the right heading line is offset by the right offset distance). These lines are parallel to the run-in heading lines and are created after the run-in heading lines have been trimmed at the intersections with the circular arcs.

b. The parallel lines are connected to the firing box by creating perpendicular lines at the endpoints. This expands the firing box to the left and/or right with the parallel lines becoming the left/right edges of the box.

2.4.1.2.1.2 Angular Offset

The offset is added to the left and/or right run-in headings and the firing box is created in the same way as the standard firing box.

2.4.1.2.1.3 Single Offset

The user has the option to specify a single offset (left or right). In this case, the firing box is created in the same way as the standard firing box and then shifted to the left or right by the offset distance. In cases where the offset is given as an angular value, the firing box is rotated around the target point by the offset value.

When a single offset is selected the offset values are saved in the database as the selected offset value and the negative of that value for the offset not selected.

2.4.1.2.2 Sidefire/Door Gunnery Firing Areas

2.4.1.2.2.1 Circling

The firing area for circling sidefire is constructed the same as the standard firing area except that it uses the firing direction in lieu of the run-in heading.

2.4.1.2.2.2 Linear

a. Linear Door Gunnery requires the user select a start and cease fire point on the map. These points are used to define the firing line.

b. The firing line is buffered by 10 meters on all sides creating a polygon feature.

c. The buffered firing line is then buffered by the user-specified buffer distance to create a firing area.

d. This firing area is modified by the WDZ engine to include only the portion of the original area that is possible given the specified input parameters.

e. The feat_desc field in the firing_point feature class is set to “Start Fire Point” for the first point selected and “Cease Fire Point” for the last point selected.

2.4.1.2.3 Firing Areas for Line and Area Target

The current implementation does not create firing areas for WDZs created using line or area targets. A firing point indicator is placed at the centroid of the standard firing area.

2.4.1.2.4 Hover fire

Hover fire requires the user select a single firing point on the map. Hover fire is only available for aircraft/weapon combinations where the HoverFire bit is selected in the lnk_Aircraft_Weapon table. These aircraft/weapons must have an allowable minimum airspeed of zero.

2.4.1.2.4.1 Circling

A firing point is used to represent the hover fire point selected. The feat_desc field in the firing_point feature class is set to “Launch Point”.

2.4.1.2.4.2 Linear

The firing point selected is buffered by the buffer value entered and saved as firing area and a firing point. The feat_desc field in the firing_point feature class is set to “Start Fire Point”.

2.4.2 Target Geometry

Target geometry can be a point, line or polygon. User-selected target parameters are saved in the target_attributes table. A target is defined for a WDZ when the target_id in the wdz_parameters_input table equals the target_id in the target_attributes table.

Point target geometry is saved in the military_target_point feature class where target_id equals target_id from the target_attributes table.

Line target geometry is saved in the military_target_line feature class where target_id equals target_id from the target_attributes table. Line target geometry is buffered by 10 meters on all sides creating a polygon feature class.

Area target geometry is saved in the military_target_area feature class where target_id equals target_id from the target_attributes table.

If an elevation layer is defined in the WDZ Setup tool the map elevation will be automatically populated for a target using the target point location, the centroid of the area target or the midpoint of the line target.

2.4.3 Area of Critical Control (ACC) Geometry

ACC geometry can be a point, line or polygon. User-selected ACC parameters are saved in the acc_attributes table.

All ACC geometries are saved as both a point and area features.

The ACC Point feature saves the selected point to the acc_point feature class. This point is buffered by the user-provided value and saved to the acc_area feature class.

The ACC Line feature saves the mid-point of the line to the acc_point feature class. The line is buffered by the user-provided value and saved to the acc_area feature class.

The ACC Area feature saves the centroid of the area to the acc_point feature class. The area is buffered by the user-provided value and saved to the acc_area feature class.

3. Risk Risk is defined as the probability of an impact at a specified location. The types of risk analysis in the WDZ application are Risk Analysis, Off Range Risk, and Point Risk.

3.1 Risk Analysis

Risk Analysis is performed using previously generated ACCs and WDZs.

All visible ACCs will be displayed in the Risk Analysis dialog. If no ACCs are visible then all existing ACCs will be displayed. The ACC location and area will be retrieved for each user-selected ACC.

All visible WDZs will be displayed in the Risk Analysis dialog. If no WDZs are visible then all existing WDZs will be displayed.

When processing risk the user can select the specific ACCs and WDZ combinations to run. Each WDZ and ACC is passed to the WDZ engine where the ACC area is buffered by the live or inert radius for the selected WDZ. The total ACC area is then used by the WDZ engine for the risk calculation. The risk value is passed back to the tool as a floating-point value no greater than 1.

3.2 Point Risk

Point Risk Analysis is performed using previously generated WDZs with a user-specified point location on the map.

The user must enter a square foot area for the selected point, then click the desired location on the map.

When processing point risk each visible WDZ under the selected location will be processed. For each WDZ the point risk location and area are passed to the WDZ engine where the area is buffered by the live or inert radius for the selected WDZ. The total point risk location area is then used by the WDZ engine for the risk calculation. The risk value is passed back to the tool as a floating-point value no greater than 1.

3.3 Off-Range Risk

Off-Range Risk Analysis is performed using previously generated WDZs with a defined range boundary feature.

A range boundary layer must be selected in the WDZ Setup Tool and be a layer on the map. To calculate the off-range risk the user will be required to select a WDZ on the map.

When processing off-range risk each WDZ under the selected location will be processed. For each WDZ the range boundary feature is passed to the WDZ engine. The range boundary is then used by the WDZ engine for the risk calculation. The WDZ engine then returns the remainder of the risk not included in the range boundary as a floating-point value no greater than

1. The range boundary feature is not buffered by the live or inert radius for the selected WDZ to calculate the off-range risk.

4. Batch Tool The Batch Tool allows the user to load multiple WDZ parameters into a data grid to be processed in a single step. Linear Door Gunnery and AGR-19 cannot be generated using the batch tool without modification to the import template.

Changing units on this dialog will clear the data for the selected units for all records.

The Batch Tool data grid can be loaded:

1. by entering data manually one entry at a time.

2. from a previously saved Batch Tool CSV file using the “Import” function.

3. by selecting a previously saved Batch Tool Template using the “Available Templates” drop-down list.

4. using the “Copy Parameters” function to copy an existing record in the Batch Tool data grid to create a new record.

The “Select WDZ” function is required to populate the record for WDZs that do not have ballistic data available, AKA “Legacy WDZs”. To use this function the Service, Aircraft and Weapon must be selected in the record. The user will be required to select a record from the dialog displayed.

Most existing parameters cannot be changed for these WDZs.

The “Delete” function will delete the selected record.

“Validate Selected Row” will verify that the selected record has all data required to generate a WDZ. “Validate All Rows” will process through the complete data grid and verify each record has the data required. Different weapons have different requirements. The batch tool validates weapons using the same restrictions as the create wizard. Checkboxes cannot be validated.

Checking a checkbox that is not required for the selected weapon will simply ignore the checkbox when generating the WDZ. Not checking a checkbox that is required will generate the WDZ as defined.

“Create Selected WDZ” will process the selected record and “Create All WDZs” will step through processing each record in the list from the bottom to the top. Before the “Create” functions execute they will each run the appropriate “Validate” function. The “Create” function will process all possible records before updating the map view.

The “Export” function will copy the data grid contents to a CSV file to be saved for later use. This function does not perform any validation prior to exporting the file.

5. Move/Rotate Tool The Move/Rotate Tool allows the user to interactively move or rotate a single WDZ. The user must select a WDZ visible on the map to move or rotate. Only WDZs created on point targets can be moved or rotated. WDZs contained in a composite, Linear Door Gunnery, AGR-19 and Hover Fire cannot be moved or rotated.

When the WDZ is selected the magnetic declination for the selected WDZ is verified against the magnetic declination in the WDZ Setup Tool. If these values differ the selected WDZ is updated to the current magnetic declination, regenerated appropriately and saved; this function cannot be reversed or canceled by the user.

The user can choose to update the selected WDZ or create a copy. When the copy option is selected no modification, other than magnetic declination update, will be performed on the originally selected WDZ.

The user can move the WDZ by dragging the graphic to a new location. Upon “Perform Selected Action” the user will be prompted to generate a new target. The new target is created and the target properties are saved to the target_attributes table and the military_target_point feature class. The selected WDZ parameters and new target properties are then passed to the WDZ engine where the WDZ is regenerated using the new target properties and the WDZ geometry is passed back to be displayed on the map. If the user opts to not save the WDZ change the newly created target is then deleted.

The user can move the WDZ to an existing target by using the “Select Target” function. Upon “Perform Selected Action” the target properties for the selected WDZ will be updated to the selected target. The selected WDZ parameters and selected target properties are then passed to the WDZ engine where the WDZ is regenerated using the selected target properties and the WDZ geometry is passed back to be displayed on the map.

The user can rotate the WDZ using the mouse to rotate the graphic on the map, incrementally rotate using the “Rotate by” value and the “Rotate” button or by changing the “New From” and “New To” headings on the dialog. The “New From” and “New To” heading values are updated with each rotate option. “Perform Selected Action” will update the WDZ to the heading values in the “New From” and “New To” textboxes in all cases. For Gunnery the “launch_pt_to_target_dir_from” is updated to the “New From” and “launch_pt_to_target_dir_to” is updated to “New To” headings; the “run_in_heading_from” and “run_in_heading_to” are modified by the angle of rotation. All other weapons update the “run_in_heading_from” to the “New From” and “run_in_heading_to” to the “New To”. The selected WDZ parameters with the updated headings are then passed to the WDZ engine where the WDZ is regenerated with the updated headings and the WDZ geometry is passed back to be displayed on the map.

The “Perform Selected Action” function will update the appropriate feature classes and the wdz_parameters_input table for the selected WDZ; however, if the user opts to not save the changes the feature classes and WDZ parameters are returned to their original state with the exception of any magnetic update modifications.

6. Adjustments Tool The Adjustments Tool is an extension on the Move/Rotate Tool. The user must select a single WDZ visible on the map to modify. Only WDZs created on point targets can be modified. WDZs contained in a composite, Legacy WDZs, Linear Door Gunnery, AGR-19, Hover Fire and WDZs that allow off-axis delivery cannot be modified using this tool.

The user can use the sliders or update the textboxes to modify WDZ parameters. Parameters that can be changed using the Adjustments Tool are airspeeds, altitudes, release angles, release ranges and run-in headings. Each slider will automatically update the textbox. Each parameter textbox change results in a call the to WDZ engine to return a regenerated WDZ with the new parameters. The new temporary WDZ graphic is then updated on the map.

The “Perform Selected Action” function will update the appropriate feature classes and the wdz_parameters_input table for the selected WDZ; however, if the user opts to not save the changes the feature classes and WDZ parameters are returned to their original state with the exception of any magnetic update modifications.

7. Update Magnetic Declination Tool The Update Magnetic Declination Tool will regenerate all WDZs not contained in a composite using the current magnetic declination entered in the WDZ Setup Tool.

Update Magnetic Declination will remove terrain mitigation from all WDZs not contained in a composite but will not reapply the terrain mitigation.

The tool replaces the existing magnetic declination with the magnetic declination in the WDZ Setup Tool for each applicable WDZ and passes it to the WDZ engine. The WDZ engine regenerates the WDZ and passes back the updated geometry.

The “Update Magnetic Declination” function will break large files up into groups of two thousand records each. After each group is processed the database will be updated and the WDZ feature classes will be updated and visible on the map and in the manager.

8. Terrain Mitigation Tool Existing WDZs may be modify by the underlying terrain layer. The Terrain Mitigation Tool requires an elevation layer and the appropriate elevation units be selected in the WDZ Setup Tool. The WDZ being terrain modified must be wholly contained within the terrain layer. Only Gunnery weapons can be terrain modified.

The tool crops out a terrain patch approximately 1½ times the size of the WDZ to be modified and passes it to the WDZ engine along with the WDZ parameters. The WDZ engine modifies the WDZ by the underlying terrain and passes back the updated geometry. The updated geometry is saved to the mil_surface_danger_zone_area feature class and the “is_terrain_mitigated” field in the wdz_parameters_input table is set.

WDZs that have been terrain mitigated cannot be modified using any tool other than the “Edit WDZ” function. Editing a WDZ that has been terrain mitigated will remove the terrain mitigation by setting the “is_terrain_mitigated” field back to zero and regenerating the WDZ.

9. Layout WDZ The layout template used is based on the weapon selected. Smart bombs use the “PavewayIVLayout.mxd” template. Dumb bombs use the “TargetCentricLayout.mxd” template.

Gunnery weapons use the “SidefireLayout.mxd” template. Weapons with offset angles like Griffin and Hellfire use the “LaunchCentricLayout.mxd” template. Most layout data is retrieved from the wdzoutput database, but some fields are dynamically populated, turned on/off at the time the layout is generated.

10. Other Non-model related functions WDZ contains several tools that do not have a direct impact on the WDZ generation. These tools do not affect the models or the underlying WDZ geometries.

Some of these functionalities are:

Changing WDZ Color Restacking WDZ Calculating WDZ area Setting Bookmarks Exporting WDZ to various DoD standards Administrative functions

{INTENTIONALLY LEFT BLANK}

A-1

Appendix A: Glossary

ArcMap Geographical Commercial off-the-shelf Software published by ESRI

WDZ A 3-dimensional area associated with firing an air-to-ground weapon where the risk of damage, injury or death does not exceed an acceptable level. A WDZ encompasses the ground and airspace for lateral and vertical containment of projectiles, fragments, debris and components resulting from the firing, launching and/or detonation of aviation delivered ordnance. This 3-dimensional zone accounts for weapon accuracy, failures, ricochets, and broaches/porpoising of a specific weapon/munition type delivered by a specific aircraft type. WDZs represent the minimum safety requirements designed for aviation weapons training on “DoD” ranges.

B-1

Appendix B: Acronyms

ACC Area of Critical Concern

AKA Also Known As

COM Component Object Model

CSV Comma-separated values

DLL Dynamic Link Library

DoD Department of Defense

WDZ Weapon Danger Zone

XML Extensible Markup Language

B-2

File details come from the government source that posted it. Updated .