JTLS 2012 11412

Design Plan JTLS-2012-11412
ROLANDS & ASSOCIATES Corporation
JTLS-2012-11412 Expand Link-16 Messages

Reenah Kang
1.0 Summary of Model Change Request

In order to provide the required feed for the Ballistic Missile Defense (BMD) tool called the Link16 Surface-to-Air Missile Command and Control System (SAMC2) Interoperability Demonstrator known as Link 16 Intelligent Decision Tool (LSID), JTLS must produce several new Link-16 messages. LSID is part of the new version of ICC (2.8.2) and provides the capability to display the missile defense situational awareness picture using Link 16 Data. The following messages must be produced by JTLS: J 3.6 Space track Message J 3.0 Reference Point J 7.0 Track Management (Drop Track)
J 13.3 Surface (Maritime) Platform and System Status J 13.5 Surface (Land) Platform and System Status (only for SSM & SAM Sites) J 3.5 Land Point or Track J 2.6 Land Track PPLI J 10.2 Engagement Status *** remove???
2.0 Design Summary

In current JTLS, several Link-16 messages are being generated and provided to the C4I system from the JTLS Operational Interface (JOI) Program. The JOI can provide the following Link-16 messages: Air Precision Participant Location and Identification (PPLI), J2.2 - This message is sent out for self-reporting Link-16 capable Air Missions and includes data such as; altitude, speed, course, location, activity, mode1, mode 2 mode 3, call sign, etc. Surface (PPLI), J2.3 - This message is sent out for Link-16 capable naval units and the following data are included in the message; speed, course, location, platform, mode2, etc. JTLS 4.1.0.0 557 22 January 2013
Land Point PPLI, J2.5 - This message is sent out for Link-16 capable ground based units and provides the location, activity, and platform. Reference Point, J3.0 - This message is generated upon the detection of a Ballistic Missile (TBM) launch and provides the launch point, impact point, and expected impact ellipse data. Emergency Point, J3.1 - This message is sent out to report an emergency situation, such as DOWN AIRCRAFT. Air Track, J3.2 - This message is sent out for air tracks that are detected by Link-16 capable assets and provides the following data; relationship, altitude, strength, speed, course, location, mode 1, mode 2, mode 3, mode 4 indicator, etc. Space Track, J3.6 - This message is sent to report continuous location updates for a Ballistic Missile object. Drop Track, J7.0 - This message is sent when an air PPLI or track is dropped. Air Platform and Surface, J13.2 - This message is sent out to provide the current status of an air PPLI or track. The message includes the following data; fuel, operational capability, weapon loads, etc. An additional Link-16 message J3.3 (Surface Track) was added to JTLS 4.1 as part of JTLS-201211377 Link 16 Surface Tracks. With this ECP, the JOI will provide five additional new message types: J 2.6 Land Track PPLI - provide PPLI data for mobile ground objects --- remove??? J 3.5 Land Point or Track - provide tactical surveillance information on land points and tracks J 13.3 - provide the current status information for a surface platform J 13.5 - provide the weapon and equipment status information of a land platform J 10.2 Engagement Status - provides status of an engagement between the participating tracks The J13.3 and J13.5 messages will work in similar manner as the J13.2 messages which provide additional status/weapon information for the air PPLI/tracks that are currently being reported to the C4I system.
22 January 2013
558
JTLS 4.1.0.0
3.0 Detailed Design

The key to this ECP is understanding the message requirements and how to provide the data from JTLS via JOI. If the required information is currently not available in JODA for JOI to retrieve, we will need to make necessary CEP/JODA changes. Few database changes will also be required to be able to generate the Link-16 acceptable data values if the information is currently not available in JTLS. Following subsections will each describe new message type that will be generated in JTLS. One or more tables under each section will list data elements that JOI will provide for the specified Link16 message type. Instead of trying to supply most of the fields on each message type, we will concentrate on providing data elements that are being utilized by the LSID component of the ICC. The requirement information was based on the ICC documentation, LSID Software User Manual. Also note that the LSID does not use all parts of the messages. If the information is not applicable in JTLS, No Statement (NS) is sent. If NS is not allowed, a default value from the list of acceptable values is sent. For detailed message definitions, descriptions, and acceptable values, please refer to the DOD Tactical Data Link (TDL) 16 Message Standard documentation (MIL-STD-6016C_Change_1_complete_document.pdf). 3.1 Message Description 3.1.1 Expand Surface PPLI (J2.3) and Land Point PPLI (J2.5) To provide the weapon system information data to LSID, we will expand the criteria for generating the J2.3 andJ2.5 messages. Currently, when JU numbers were assigned to the ground-based or surface-based units, JOI was producing the PPLI messages to report the position of units. We will add the capability to generate the PPLI messages from unit-owned or unit-associated targets. There are only three types of targets that can send out information concerning their current location. These are: Air Defense Targets - Their characteristics are defined by the Air Defense Class entity, This entity will have a new database parameter called AD.LINK16.CAPABLE. Sensor Targets - Their characteristics are defined by the Sensor Type entity. This entity will have a new database parameter called ST.LINK16.CAPABLE. Surface-to-Surface Missile Targets - Their characteristics are defined by the Surface-toSurface or SSM entity. This entity will have a new database parameter called SSM.LINK16.CAPABLE. Facility Targets - Their characteristics are defined by the Facility entity. This entity will have a new database parameter called FAT.LINK16.CAPABLE. JTLS 4.1.0.0 559 22 January 2013
Communication Targets - Their characteristics are defined by the Communication Center entity. This entity will have a new database parameter called CC.LINK16.CAPABLE. Currently, all unit objects have the JU number database field which is used as the Source Track Number (STN) in each message header. The current mechanism of assigning JU numbers will be expanded so that we can assign the JU numbers for the targets to participate the Link-16 network. The most difficult design decision concerns how are Link-16 entities going to be assigned their ju_number and if needed their track blocks that should be used. The problem is confused by the fact that the database team may decide not to build the individual targets, but instead use the Prototype Owned Target (POT) capability. POT targets do not exist in the database, they are created when the unit is initialized in the model. This means that the database cannot always specify the ju_number information leaving the assignment of this data until the last minute whe the game is initialized. One of the purposes of this design is to alleviate that burden from game controllers. Currently the JTLS 4.0 database has the following Link-16 related data: Every unit has an attribute called UT.JU.NUMBER. This database parameter will not change. If set, the unit will send out Link-16 PPLI data. Every Squadron also has a list of JU Numbers that its aircraft can use along with a block of track numbers. When an aircraft takes off, it takes a JU Number from the list and its associated track block. The mission uses this information as it detects foreign objects. Every Sensor Target has a block of track numbers assigned. Thus a single ship that has an air search sensor and a surface search sensor has two different track blocks. This is contrary to the manner in which the real-world operates. The ship owns the track block and will assign track numbers from its block irregardless of whether the track is an air track or a surface track. So what database will need to be made. We are proposing the following: From the sensor target table, remove the TG TRACK BLOCK START and TG TRACK BLOCK END attributes. To all unit types, add a UT TRACK BLOCK START and a UT TRACK BLOCK END. To all unit types, add an owned and associated target block of available JU Numbers. When the unit arrives in the theater, it will look at all of its owned and associated targets, this does include its POT targets. If the target is listed as Link-16 capable, the unit will fill
22 January 2013
560
JTLS 4.1.0.0
in the targets assigned TG JU NUMBER. Those targets will then be sending out Link-16 PPLIs. If the target detects something, it will look to its parent and pickup a JU Track Number from the units block. Of these three types of targets, only Air Defense targets can be placed on the game board in an independent location. They may be either owned by a unit or associated with a unit. With the target addition to the PPLI messages, we will review and expand the LAND PLATFORM and LAND ACTIVITY data elements for the J2.5 messages. The table displays the key data elements in the message. Table 1. Land Point PPLI (J2.5)
LINK-16
DATA ELEMENT
DESCRIPTION
INFORMATION PROVIDED IN JTLS
STRENGTH (I)
Number of entities represented by a single track
number of firing elements for SAM target, number of launchers for SSM site, 1 for all other object types 0 UT.LOCATION/TG.LOCATION UT.LOCATION/TG.LOCATION see Table 2. Land Platform Mapping Guide see Table 3 Land Activity Mapping Guide
ELEVATION, 25 FT (I) LATITUDE (E0) LONGITUDE(E0) LAND PLATFORM (C1) LAND ACTIVITY (C1)
Elevation in feet above mean sea level Position of the track Position of the track Link-16 acceptable platform Link-16 acceptable activity
The following table provides the mapping guideline for the Land Platform data element for both J2.5 and J3.5 messages. For the LAND PLATFORM data element, we were providing 7 (=AIRFIELD/AIRBASE) for the airbase and 1 (=TROOP CONCENTRATION/UNIT) for all other ground based units. We will expand the mapping so that we can also assign the platform field for targets of interest. The Link-16 documentation provides the complete list of acceptable values with description. Table 2. Land Platform Mapping Guide
LINK-16 LAND PLATFORM NO STATEMENT TROOP CONCENTRATION/UNIT BIT CODE 0 1 LSID
INTERPRETATION
JTLS UNITS/TARGET
Interceptor (default) MIsc All units except bases and ships
JTLS 4.1.0.0
561
22 January 2013
LINK-16 LAND PLATFORM HEADQUARTER COMPLEX COMMAND/CONTROL/COMMAND AND CONTROL CENTER ASSEMBLY AREA INSTALLATION/FACILITY, MILITARY INSTALLATION/FACILITY, CIVILIAN AIRFIELD/AIRBASE PORT/HARBOR FACILITY STORAGE SITE TACTICAL POSITION FORTIFICATION INTERSECTION CONVOY COMBAT VEHICLE COMBAT SUPPORT VEHICLE VEHICLE, OTHER TANK TRAIN REMOTELY PILOTED VEHICLE MORTAR FIELD ARTILLERY AIR DEFENSE ARTILLERY ROCKET LAUNCHER MISSILE LAUNCHER SPECIAL WEAPON BRIDGE BUILDING/STRUCTURE POWER FACILITY
BIT CODE 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28
LSID
INTERPRETATION
JTLS UNITS/TARGET
Misc C2 Misc Misc Misc Misc Misc Misc Misc Misc Misc Misc Misc Misc Misc Misc Misc Misc Misc Misc Misc Misc Interceptor Misc Misc Misc Misc All SSM targets All airbases facility target
22 January 2013
562
JTLS 4.1.0.0
LINK-16 LAND PLATFORM RAIL FACILITY TERRAIN NAVAID SITE COMMUNICATION SITE RADAR SITE SURFACE-TO-AIR MISSILE (SAM) SITE MARITIME HEADQUARTERS AIR SUPPORT RADAR TEAM (ASRT) DIRECT AIR SUPPORT CENTER (DASC) FORWARD AIR CONTROL PARTY (FACP) BATTALION OPERATIONS CENTER (BOC) TACTICAL DATA SYSTEM (TDS) DECOY TRACKED VEHICLE THEATER HIGH ALTITUDE AREA DEFENSE (THAAD) JOINT TACTICAL GROUND STATION (JTAGS) ARMOR CAVALRY ENGINEER AIRBORNE/SPECIAL OPERATIONS AVIATION AIR DEFENSE SITE BALLISTIC MISSILE DEFENSE SITE
BIT CODE 29 30 31 32 33 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57
LSID
INTERPRETATION
JTLS UNITS/TARGET
Misc Misc Misc Misc Sensor Interceptor Misc Misc Misc Misc C2 Misc Misc Misc Misc Misc Misc Misc Misc Misc Misc Misc Misc communication sites All Sensor targets All SAM targets
For the LAND ACTIVITY, the following table provides the list of Link-16 activities that we are currently providing based on the units posture including High Resolution Units. For ground based targets, we will use the status of target to determine the activity. The complete list of the Land Activity is provided in the Link-16 documentation.
JTLS 4.1.0.0
563
22 January 2013
Table 3. Land Activity Mapping Guide

LINK-16 LAND ACTIVITY NO STATEMENT HOLDING DELAYING MOVING DETECTING ACQUIRING ENGAGING 0 1 2 3 4 5 6
BIT CODE
JTLS UNIT POSTURE OR TARGET STATUS Default if none of the other situations do not apply. DEFEND DELAY MOVING TURNED_ON Sensor targets SAM Targets that have enemy aircraft within detection range. SAM Targets that have fired on an enemy aircraft. It will stay in this activity until the Target is free to fire again.
ADVANCING ANTIAIR ATTACK AMPHIBIOUS ASSAULT FIRING/LAUNCHING CONVENTIONAL ATTACK/ASSAULT SPECIAL WEAPONS ATTACK DEMOLITION OVER THE HORIZON TARGETING TRANSITING RETURN TO BASE DEPLOYING EMISSION CONTROL (EMCON) RIVER CROSSING LOADING TOWING
7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 An HRU moving to a task area. HRUs REJOIN PARENT An SSM with a status of SETTING UP An HRU on a raid against a neutral target. AMPHIBIOUS SSM Target that has a status of SETUP. ATTACK
22 January 2013
564
JTLS 4.1.0.0
LINK-16 LAND ACTIVITY BUILDING FORTIFICATION BARRIER CLEARING BARRIER RECOVERING EQUIPMENT MINE SWEEPING MINE LAYING JAMMING RECONNAISSANCE/ PATROLLING SEARCH AND RESCUE (SAR) TRAINING MEDICAL EVACUATION (MEDEVAC) ESCORTING TRANSPORTING SCREENING SUPPORTING REPAIRING REFUELING NEUTRALIZING TARGETING BYPASSING CLOSING CONCENTRATING DEFENDING DISENGAGING INFILTRATING
BIT CODE
JTLS UNIT POSTURE OR TARGET STATUS
22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 An HRU that is on a Combat Raid mission against a unit. When it is on the area of the unit, this Land Activity will be set. DEFEND A target that is currently being repaired. TRAINING A Downed Pilot when it is recovered by an Air Mission. PATROL
JTLS 4.1.0.0
565
22 January 2013
LINK-16 LAND ACTIVITY INTERDICTING LANDING OCCUPYING DISPERSING SUPPLY/RESUPPLY RETROGRADE/WITHDRAWING TRANSMITTING ELECTRONIC WARFARE SUPPORT (ES) ELECTRONIC ATTACK (EA) MOVING EQUIPMENT POWER UP AND MANNED, NOT EMITTING PREPARATION FOR LAUNCH SITE SHUT DOWN TO UNPOWERED STATUS
BIT CODE
JTLS UNIT POSTURE OR TARGET STATUS
46 47 48 49 50 51 52 53 54 55 56 57 58 PREPARINGSSM targets A unit that has a Radar Jammer that is turned on. A unit that has a Radar Jammer that is turned on. WITHDRAW
For Link-16 participating surface based targets, we will provide the location and the surface platform data of the owning ship. 3.1.2 Land Point/Track (J3.5) The J3.5 messages will be generated when an ground object is detected by any Link-16 capable resources. The JOI will provide the Initialization word (I), Extension word 0 (E0), and Continuation word 1 (C1). The following table lists the required data elements for the LSID. Table 4. Land Point Track (J3.5)
LINK-16
DATA ELEMENT
DESCRIPTION
REFERENCE TRACK NUMBER (I) ELEVATION (I)
The reference JU number (JU) of land point/track elevation in feet
assigned JU number from the JU block of reporting source elevation if known, NS otherwise
22 January 2013
566
JTLS 4.1.0.0
LINK-16
DATA ELEMENT
DESCRIPTION
POINT/TRACK INDICATOR (I) LATITUDE (E0) LONGITUDE (E0) LAND PLATFORM (C1) LAND ACTIVITY (C1) LAND SPECIFIC TYPE (C1)
POINT or TRACK (POINT for stationary object TRACK for mobile ground object) position of the point/track position of the point/track Link-16acceptable land platform Link-16 acceptable Land activity specific type of point/track
POINT known location of the object known location of the object Table 2. Land Platform Mapping Guide Table 3 Land Activity Mapping Guide Not implemented for this ECP
In current JTLS, air search sensor targets were assigned JU block of starting and ending JU numbers. A JU number within the block was used when a detection occurs by the sensor to report Air Tracks (J3.2). With this ECP, any types of sensors will have JU blocks so that it is used when a detection occurs to report any surface (J3.3) and ground tracks (J3.5). When any ground/surface based targets are detected by Link-16 assets, the reporting assets JU number is used as the source and the reference track number will be assigned from reporters block list. For detected SAM and SSM targets, three new JODA target attributes will be added. ju_number - The attribute holds the database variable TG.JU_NUMBER. If this text value is not "NONE", JOI will generated either J2.3 or J2.5 PPLI message. track_ju_number - This attribute holds the JU number assigned from the reporting assets block (part of J3.3 or J3.5 Initial message). source_ju_number - This attribute holds the JU number of the reporting asset (source track number as part of J3.3 or 3.5 header). For detected ground/surface based units, one new JODA unit attribute will be added. In current JTLS, the ju_number and source_ju_number exist as unit attributes. ju_number - The attribute holds the database variable UT.JU_NUMBER. If this text value is not "NONE", JOI will generated either J2.3 or J2.5 PPLI message. track_ju_number - This attribute holds the JU number assigned from the reporting assets block (part of J3.3 or J3.5 Initial message). source_ju_number - This attribute holds the JU number of the reporting asset (source track number as part of J3.3 or 3.5 header). JTLS 4.1.0.0 567 22 January 2013
For the last 3 data elements in the Table, you can either provide the LAND SPECIFIC Type or LAND PLATFORM with LAND ACTIVITY data. We have selected the second option; provide platform and activity data. The same data elements also exist in the J2.5 messages and we will use the same mapping guideline as explained in Table 2. Land Platform Mapping Guide and Table 3 Land Activity Mapping Guide. If the LSID is expecting the LAND SPECIFIC TYPE data element, we will need an additional mapping mechanism to accomplish the task. For the LAND SPECIFIC TYPE data element, more than 400 entries are listed in the Link-16 documentation (DFI 810/DUI 001). We may need to create a subset of types to be used in JTLS and make it available for database and vocabulary file. 3.1.3 Surface Platform and System Status (J13.3) With this message, JOI will provide the current status of a surface platform which includes the operational status and on board systems' status. These additional information will be provided for the existing Surface PPLIs and Surface Tracks of own side. For any Link-16 participating surface-based owning side entities, the on-board missile information is collected and passed to the C4I system. The following table list the required fields for the LSID, and the JOI will provide the Initialization Word (I), Continuation Word 1 (C1), and Continuation Word 2 (C2) to meet the requirements. All the requested information is available in JODA objects, either in NAVAL or target objects.] Table 5. Surface Platform and System Status (J13.3)
LINK-16
DATA ELEMENT
DESCRIPTION
REFERENCE TRACK NUMBER (I) MISSILE TYPE, 1-3 (C1) OPERATIONAL MISSILE INVENTORY, 1-3 (C1) NUMBER OF FIRE CONTROL SYSTEMS AVAILABLE, 1-3 (C1) 3RD AIR SEARCH RADAR
The reference number (JU) of surface PPLI/Track The type of missile being reported An estimated amount of operational missiles. The number of available fire control systems
JU number of participating surface object (J2.3 or J3.3) ships own SAMs and SSM target type use JODA TG.NUMBER attribute? NS?
Status of 3-dimensional air search radar and their components. (NO STATEMENT, DEGRADED, NON OPERATIONAL, OPERATIONAL)
use JODA attribute TG.PERCENT_CAPABLE?
The continuation word 1 message contains the on-board missile information for ships. There are 3 sets of data elements to provide, up to 3 different missile types on board. For the data element 22 January 2013 568 JTLS 4.1.0.0
MISSILE_TYPE, the Link-16 documents provides a list of 27 acceptable types. We will add database variable to hold the Link-16 missile type information. This variable will be an attribute to the Air Defense Class (AD.LINK16.MISSILE.TYPE) and SSM Type (SSM.LINK16.MISSILE.TYPE) entities. The following table provides the list of acceptable Missile Types (DFI 399/DUI 004). Table 6. Missile Type Mapping Guideline
LINK-16 NO STATEMENT SHORT RANGE SAM MEDIUM RANGE SAM LONG RANGE SAM SHORT RANGE SSM MEDIUM RANGE SSM LONG RANGE SSM SM2(ER) SM2(MR) SM1(ER) SM1(MR) EXTENDED RANGE SAM (SHORT) EXTENDED RANGE SAM (MEDIUM) EXTENDED RANGE SAM (LONG) EXTENDED RANGE SSM (SHORT) EXTENDED RANGE SSM (MEDIUM) EXTENDED RANGE SSM (LONG) SM2 BLOCK II SM2 BLOCK III SM2 BLOCK IIIA SM2 BLOCK IIIB BIT CODE 0 1 2 3 4 5 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 RANGE LESS THAN 10 NM RANGE 10-50 NM RANGE GREATER THAN 50 NM RANGE LESS THAN 15 NM RANGE 15-75 NM RANGE GREATER THAN 75 NM A LONG RANGE SAM A MEDIUM RANGE SAM A MEDIUM RANGE SAM A MEDIUM RANGE SAM RANGE 51 THROUGH 99 NM RANGE 100 THROUGH 150 NM RANGE GREATER THAN 150 NM RANGE 76 THROUGH 199 NM RANGE 200 THROUGH 300 NM RANGE GREATER THAN 300 NM AN EXTENDED RANGE SAM (SHORT) AN EXTENDED RANGE SAM (SHORT) AN EXTENDED RANGE SAM (SHORT) AN EXTENDED RANGE SAM (SHORT) EXPLANATION
JTLS 4.1.0.0
569
22 January 2013
LINK-16 SM2 BLOCK IV SM2 BLOCK IVA
BIT CODE 22 23
EXPLANATION AN EXTENDED RANGE SAM (MEDIUM) AN ANTI-THEATER BALLISTIC MISSILE (TBM) CAPABLE EXTENDED RANGE SAM (LONG) A LONG RANGE SSM TACTICAL ANTISHIP MISSILE A LONG RANGE SSM TACTICAL LAND ATTACK MISSILE CONVENTIONAL A MEDIUM RANGE SSM LIGHT EXOATMOSPHERIC PROJECTILE ANANTI-TBM MISSILE (EXTENDED RANGE (LONG)).
TOMAHAWK (TASM) TOMAHAWK (TLAM C) HARPOON SM3 (LEAP)
24 25 26 27
UNDEFINED
For the three sets of on-board missile data. JOI will provide inventory of up to 3 different missile types owned by the surface PPLIs. To access this data, JOI will extract the data from the SAM and SSM targets from JODA that are owned by naval objects. For the 3RD AIR SEARCH RADAR data element, we will determine the status based on the air search sensor targets percent capable. For other targets, we will provide NO STATEMENT. NO STATEMENT DEGRADED NOT OPERATIONAL OPERATIONAL 3.1.4 Land Platform and System Status (J13.5) The J13.5 message is used to provide the current weapons and equipment information of a land platform. For this ECP, we will provide this message for all Link-16 participating owning side SSM and SAM sites. The following tables lists the required data elements by the LSID. We will provide the Initial Word (I) and Continuation Word 1 (C1) to meet the requirements.
22 January 2013
570
JTLS 4.1.0.0
Table 7. Land Platform and System Status (J13.5)

LINK-16
DATA ELEMENT
DESCRIPTION
INFORMATION PROVIDED FROM JTLS
OPERATIONAL CAPABILITY REFERENCE TRACK NUMBER (I) SITE TYPE(I)
No Statement, Fully Operational, Partially Operational, or Non operational The reference number (JU) of land PPLI/Track The type of site being reported (from the Link-16 acceptable site type) Number of Remaining Hot Missiles on a weapon system Amount of cold missiles remaining Operating status of a primary surveillance radar system (NO STATEMENT, OPERATIONAL, NONOPERATIONAL, OFF)
derive from the target strength JU number of participating object (J2.5 or J3.5) select an entry for SAM/SSM targets NS for all other types
HOT INVENTORY (I) COLD INVENTORY (C1) PRIMARY SURVEILLANCE RADAR STATUS
TG attribute?
For the SITE TYPE field, the documentation provides a list of 42 acceptable items DFI 1555/DUI 001). We will add three new database variables in JTLS to hold this information. This database attribute will be added to the Target Category level for the AIr Defense Class (AD.LINK16.SITE.TYPE), Sensor Site (ST.LINK16.SITE.TYPE), SSM (SSM.LINK16.SITE.TYPE), Facility (FAT.LINK16.SITE.TYPE), and Communication Center (CC.LINK16.SITE.TYPE). A SVP warning will be generated if the Link16 capable flag is set to true but the site type is not defined. The list of acceptable site types is provided in the following table. The explanation for different site types are provided in the Link-16 documentation. The database developer can assign each of these site types to the Target Subcategories listed above. Table 8. Site Type Mapping
SITE TYPE
BIT CODE 0 1 2 3 4 5
EXPLANATION
LSID INTERPRETS LSID_OTHER
NO STATEMENT ADOC SOC SOC/CRS CRC CRP
AIR DEFENSE TACTICAL OPERATIONS CENTER SECTOR OPERATION CENTER SECTOR OPERATION CENTER /CONTROL REPORTING SITE CONTROL AND REPORTING CENTER CONTROL AND REPORTING POST
LSID_OTHER LSID_OTHER LSID_OTHER LSID_OTHER LSID_OTHER
JTLS 4.1.0.0
571
22 January 2013
SITE TYPE
BIT CODE 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31
EXPLANATION
LSID INTERPRETS LSID_OTHER LSID_OTHER LSID_OTHER LSID_OTHER LSID_OTHER LSID_OTHER LSID_ABT_SAM LSID_ABT_SAM LSID_ABT_SAM LSID_OTHER LSID_OTHER LSID_OTHER LSID_OTHER LSID_OTHER LSID_OTHER LSID_OTHER LSID_OTHER LSID_OTHER LSID_OTHER LSID_OTHER LSID_OTHER LSID_OTHER LSID_OTHER LSID_OTHER LSID_OTHER LSID_OTHER
AEGIS TACC (USAF) CRC/MCE SSSB HIMAD BDE HIMAD BN PATRIOT BN ICC PATRIOT/ECS HAWK/AFP SHORAD BDE SHORAD BN SWC TACC (USMC) TADC TAOC ROCC RADIL ASIT GCI MPC TOC DIVARTY NIKE GACC PLSS ENSCE
AIRBORNE EARLY WARNING GROUND INTERFACE SEGMENT TACTICAL AIR CONTROL CENTER CRC/MODULAR CONTROL EQUIPMENT SHIP SHORE SHIP BUFFER HIGH TO MEDIUM ALTITUDE AIR DEFENSE BRIGADE HIMAD BATTALION PATRIOT BN INFORMATION COORDINATION CENTER PATRIOT ENGAGEMENT CONTROL STATION HAWK ASSAULT FIRE PLATOON SHORT RANGE AIR DEFENSE BRIGADE SHORT RANGE AIR DEFENSE BATTALION COMPASS EARS TACTICAL AIR COMMAND CENTER TACTICAL AIR DIRECTION CENTER TACTICAL AIR OPERATIONS CENTER REGIONAL OPERATIONS CONTROL CENTER ROCC AWACS DIGITAL INTERFACE LINK ADAPTABLE SURFACE INTERFACE TERMINAL GROUND CONTROL INTERCEPT MESSAGE PROCESSING CENTER TACTICAL OPERATIONS CENTER DIVISION ARTILLERY NIKE SITE GROUND ATTACK CONTROL CENTER PRECISION LOCATED STRIKE SYSTEM ENEMY SITUATION CORRELATION ELEMENT
22 January 2013
572
JTLS 4.1.0.0
SITE TYPE
BIT CODE 32 33 34 35 36 37 38 39 41 41 42
EXPLANATION
LSID INTERPRETS LSID_OTHER LSID_OTHER LSID_UPPER_LAYER_SAM LSID_UPPER_LAYER_SAM LSID_OTHER LSID_OTHER LSID_OTHER LSID_OTHER LSID_OTHER LSID_OTHER LSID_OTHER
TGIF FACP TOC (THAAD) LCS (THAAD) SSI (THAAD) JTAGS ADTOC/BN ADTOC/BDE ADCP BM DEFENSE SITE ME SSAMP/T
TRANSPORTABLE GROUND INTERCEPT FACILITY FORWARD AIR CONTROL POST TACTICAL OPERATIONS CENTER (THEATER HIGH ALTITUDE AREA DEFENSE) LAUNCHER COMMUNICATIONS STATION (THEATER HIGH ALTITUDE AREA DEFENSE) SENSOR SYSTEM INTERFACE (THEATER HIGH ALTITUDE AREA DEFENSE) JOINT TACTICAL GROUND STATION AIR DEFENSE TACTICAL OPERATIONS CENTER, BATTALION AIR DEFENSE TACTICAL OPERATIONS CENTER, BRIGADE AIR DEFENSE COMMUNICATIONS PLATFORM BALLISTIC MISSILE DEFENSE SITE SAMP/T FIRE UNIT
3.1.5 Engagement Status (J10.2) This message provides the status of a weapon engagement between two JUs, the Reference Track and the Target Track. Since the engagement status changes so rapidly, the CEP cannot use JODA attributes to provide the information to JOI. It will require a different way to provide the data, a special message will be sent out for JOI to generate the J10.2 message. To provide the required data elements to ICC, JOI will generate the Initial Word (I) and Continuation Word 2 (C2). Table 9. Engagement Status (J10.2)
LINK-16
DATA ELEMENT
DESCRIPTION
REFERENCE TRACK NUMBER (I) TARGET TRACK NUMBER (I) WEAPON SYSTEM (I)
The reference JU number of the friendly track The reference JU number of the target track weapon type from the list
assigned JU number from reporting source assigned JU number from reporting source
JTLS 4.1.0.0
573
22 January 2013
LINK-16
DATA ELEMENT
DESCRIPTION
WEAPON ENGAGEMENT STATUS (I) TIME FUNCTION (C2) MINUTES (C2) TENTH SECONDS (C2)
engagement status of a weapon against an object (select status from the list) TIME OF PREDICTED INTERCEPT (=1) or TIME OF ACTUAL INTERCEPT (=2) minute of the hour one tenth of second 1 or 2
To provide the weapon system and weapon engagement status information, separate tables are provided below. To provide data for the WEAPON SYSTEM data element, we will define a list of systems JTLS can produce from the complete list defined in the documentation. The following table provides the complete list of WEAPON SYSTEMs as defined in the documentation (DFI 700/ DUI 002). Those ed in Green can be supported by JTLS. Table 10. Link-16 Weapon System List
WEAPON SYSTEM NO STATEMENT SURFACE-TO-AIR MISSILE (SAM) 0 1 BIT CODE
JTLS?
YES - When none of the other situations apply, this will be output. YES - If the reporting unit owns any Air Defense Sites with precision guided weapons. YES - If the reporting unit owns any SSM site targets. YES - if the reporting unit is a squadron with fixed wing aircraft. YES - If the reporting unit has any Air Defense Sites with non-precision guided weapons. Yes - If the reporting unit has any helicopters that are mission capable for Patrol. YES - If the reporting unit has any Torpedo Weapons that are listed as precision guided and have a PK against at least one submarine, YES - If the reporting unit has any Torpedo Weapons that are listed as non-precision guided..
SURFACE-TO-SURFACE MISSILE (SSM) AIRCRAFT CONVENTIONAL (SHORT RANGE MISSILE OR GUNS) ANTISUBMARINE WARFARE HELICOPTER
2 3 4
ANTISUBMARINE WARFARE MISSILE
DEPTH CHARGE/DEPTH BOMB
22 January 2013
574
JTLS 4.1.0.0
WEAPON SYSTEM TORPEDO 8
BIT CODE
JTLS?
Yes - If the reporting unit has any Torpedo Weapons that are listed as precision guided and have a PK against only surface ships. Yes - If the reporting unit has any helicopters that are mission capable for Patrol.
FIXED WING ANTISUBMARINE WARFARE AIRCRAFT LASER BEAM WEAPON INFRARED DECOY CHAFF SPOT JAMMER BARRAGE JAMMER DECEPTION JAMMER INTERCEPTOR AIR-TO-SURFACE MISSILE (ASM)
10 11 12 13 14 15 16 17 18 Yes - if the reporting unit has any precision-guided weapons that can hit surface targets. Yes - if the reporting unit owns a jammer that is jamming a specific unit. Yes - if the reporting unit owns a jammer that is jamming a specific side. Yes - if the reporting unit has any Aircraft-based Beam Weapons.
For the WEAPON ENGAGEMENT STATUS data element, the following table provides the documented engagement statuses. The JTLS provided statuses are color-coded in green. Table 11. Link-16 Weapon Engagement Status List
WEAPON ENGAGEMENT STATUS (WES) NO STATEMENT RECOMMEND REATTACK 0 1 BIT CODE YES YES - if the assigned weapon has a BDA capability and the target was not fully destroyed. YES YES
JTLS PROVIDE?
WEAPON ASSIGNED TRACKING/LOCKED ON/READY TO FIRE/BIRD AFFIRM
2 3
JTLS 4.1.0.0
575
22 January 2013
WEAPON ENGAGEMENT STATUS (WES) FIRING/MISSILE IN FLIGHT/ENGAGING TO DESTROY EFFECTIVE/TARGET DESTROYED/GRAND SLAM PARTIALLY EFFECTIVE NOT EFFECTIVE ENGAGEMENT BROKEN HEADS UP ENGAGEMENT INTERRUPTED INVESTIGATING/INTERROGATING SHADOWING INTERVENING COVERING BATTLE DAMAGE ASSESSMENT UNKNOWN 4 5 6 7 8 9 10 11 12 13 14 15
BIT CODE YES YES
JTLS PROVIDE?
The special message will be produced by CEP to indicate the engagement between two Link-16 tracks. The order of typical J10.2 message is described as follows; Weapon assigned 1st intercept Firing/Missile in flight/engage Effective/Target destroyed or not effective The special message will contain all the necessary data for JOI to generate the Link-16 engagement message. An example message string is shown below: 9997 1 10001 20014 AZ001 2 2 1 25 24.5 9997 - special message indicator 1 - indicates this is an engagement message 10001 - JU number of reporting asset (source JU number) 20014 - JU number of friendly object AZ001 - JU number of the target object (TBM track JU number as shown on J3.6) 22 January 2013 576 JTLS 4.1.0.0
2 - index to the weapon system (=SSM) 2 - index to the engagement status (=WEAPON ASSIGNED) 1 - time function (=TIME OF PREDICTED INTERCEPT) 25 - 25 minutes 24.5 - seconds 3.2 CEP Changes With additional required information to provide in the messages, the following modifications will be made in CEP: WIth added JU number attributes, CEP will assign the correct JODA JU attributes. The ju_number attribute is used for self reporting Link-16 participating asset, assigned within the database or the order. The track_ju_number is assigned from the ju block of reporting asset when detection occurs and the source_ju_number is the reporters ju number. Generate special message to provide engagement status for JOI to generate J10.2 message. The format of the message is provided in 3.1.5 Engagement Status (J10.2). The weapon system and engagement status information will be added to the model so that appropriate data can be sent to JOI via the special message. 3.3 JOI Changes With the current Link-16 capabilities in JOI, no additional setup is required for this ECP. All the existing network parameters will be used and all the generated Link-16 messages will be sent at every time interval that was set during the setup process. Currently, no filtering is provided for the Link-16 messages except when the operator turns the Link-16 feed Off to resolve any network related issues. The capability to generate the newly added Link-16 messages will be added to the JOI with added data provided by CEP & JODA. JOI will subscribe additional objects which include targets of SAM, Sensor, and SSM categories. Based on where the target is located, the Link-16 participating surface based targets will generate J2.3 and the ground based targets will generate J2.5 messages.
4.0 Data Changes

Remove the Sensor Targets, TG LINK16 BLOCK START and TG LINK16 BLOCK END.
JTLS 4.1.0.0
577
22 January 2013
UT LINK16 TRACK BLOCK START Dimension: Mode: Range: Default Value: Definition: Relationships: Unit Entity Attribute Text Characters 1,2: A - Z and/or 0 - 7; Characters 3,4,5: only 0 - 7 NULL This is the starting octal number for the tracks that this units sensors detected This database parameter is related to all of the other Link-16 data that exists in the database. There can be no overlap between any assigned Link-16 octal number.
Unit of Measure: Five character formatted text, representing an octal number.
On conversion, if the unit owns a sensor target and it has a start block value, it should go into this new database parameter. UT LINK16 TRACK BLOCK END Dimension: Mode: Range: Default Value: Definition: Relationships: Unit Entity Attribute Text Characters 1,2: A - Z and/or 0 - 7; Characters 3,4,5: only 0 - 7 NULL This is the ending octal number for the tracks that this units sensors detected. This database parameter is related to all of the other Link-16 data that exists in the database. There can be no overlap between any assigned Link-16 octal number.
On conversion, if the unit owns a sensor target and it has an end block value, it should go into this new database parameter. UT LINK16 TARGET BLOCK START Dimension: Mode: Range: Unit Entity Attribute Text 00000 through 77777
22 January 2013
578
JTLS 4.1.0.0
Default Value: Definition: Relationships:
NULL This is the starting octal number for assigning the ju_number for this units owning or associated Link-16 capable targets. This database parameter is related to all of the other Link-16 data that exists in the database. There can be no overlap between any assigned Link-16 octal number. At the beginning of the game, the model will assigned a JU NUMBER to all of this units, SAM sites, Sensor Sites, SSM Sites, Communication Centers, and Facilities if their target type information indicates that they are Link-16 capable. See the database parameters AD LINK16 CAPABLE, ST LINK16 CAPABLE, and SSM LINK16 CAPABLE.
This parameter should be NULL as a result of the database conversion. UT LINK16 TARGET BLOCK END Dimension: Mode: Range: Default Value: Definition: Relationships: Unit Entity Attribute Text 00000 through 77777 NULL This is the ending octal number for assigning the ju_number for this units owning or associated Link-16 capable targets. This database parameter is related to all of the other Link-16 data that exists in the database. There can be no overlap between any assigned Link-16 octal number. At the beginning of the game, the model will assigned a JU NUMBER to all of this units, SAM sites, Sensor Sites, SSM Sites, Communication Centers, and Facilities if their target type information indicates that they are Link-16 capable. See the database parameters AD LINK16 CAPABLE, ST LINK16 CAPABLE, and SSM LINK16 CAPABLE. This parameter should be NULL as a result of the database conversion. ST LINK16 CAPABLE Dimension: Mode: JTLS 4.1.0.0 Sensor Type Entity Attribute Boolean 579 22 January 2013
Unit of Measure: A zero mean NO, a 1 means YES Range: Default Value: Definition: Relationships: 0 (NO), 1 (YES) NO This parameter indicates whether Sensor Targets of this type are capable of communicating with the Link-16 network. This database parameter is related to all of the other Link-16 data that exists in the database. Targets that are Link-16 Capable will be assigned a JU NUMBER when their owning unit arrives in the theater, if the unit has been given a Target Assignment block as specified by the database parameters UT LINK16 TARGET BLOCK START and UT LINK16 TARGET BLOCK END.
On conversion, this parameter will be set to YES, if any of the targets of this type that exist in the database have a TG TRACK BLOCK START set. If not, then the conversion will initialize the database parameter to NO. AD LINK16 CAPABLE Dimension: Mode: Range: Default Value: Definition: Relationships: Air Defense Class Entity Attribute Boolean 0 (NO), 1 (YES) NO This parameter indicates whether Air Defense Targets of this type are capable of communicating with the Link-16 network. This database parameter is related to all of the other Link-16 data that exists in the database. Targets that are Link-16 Capable will be assigned a JU NUMBER when their owning unit arrives in the theater, if the unit has been given a Target Assignment block as specified by the database parameters UT LINK16 TARGET BLOCK START and UT LINK16 TARGET BLOCK END.
Unit of Measure: A zero mean NO, a 1 means YES
On conversion this will always be set to NO. CC LINK16 CAPABLE Dimension: Mode: Communication Center Entity Attribute Boolean
22 January 2013
580
JTLS 4.1.0.0
Range: Default Value: Definition:
0 (NO), 1 (YES) NO This parameter indicates whether Communication Center Targets of this type are capable of communicating with the Link-16 network. This database parameter is related to all of the other Link-16 data that exists in the database. Targets that are Link-16 Capable will be assigned a JU NUMBER when their owning unit arrives in the theater, if the unit has been given a Target Assignment block as specified by the database parameters UT LINK16 TARGET BLOCK START and UT LINK16 TARGET BLOCK END.
Relationships:
On conversion this will always be set to NO. FAT LINK16 CAPABLE Dimension: Mode: Range: Default Value: Definition: Relationships: Facility Type Entity Attribute Boolean 0 (NO), 1 (YES) NO This parameter indicates whether Facility Type Targets of this type are capable of communicating with the Link-16 network. This database parameter is related to all of the other Link-16 data that exists in the database. Targets that are Link-16 Capable will be assigned a JU NUMBER when their owning unit arrives in the theater, if the unit has been given a Target Assignment block as specified by the database parameters UT LINK16 TARGET BLOCK START and UT LINK16 TARGET BLOCK END.
On conversion this will always be set to NO. SSM LINK16 CAPABLE Dimension: Mode: Range: Default Value: JTLS 4.1.0.0 Surface Surface Missile Entity Attribute Boolean 0 (NO), 1 (YES) NO 581 22 January 2013
Definition:
This parameter indicates whether Surface-to-Surface Missile (SSM) Targets of this type are capable of communicating with the Link-16 network. This database parameter is related to all of the other Link-16 data that exists in the database. Targets that are Link-16 Capable will be assigned a JU NUMBER when their owning unit arrives in the theater, if the unit has been given a Target Assignment block as specified by the database parameters UT LINK16 TARGET BLOCK START and UT LINK16 TARGET BLOCK END.
Relationships:
On conversion this will always be set to NO. AD LINK16 MISSILE TYPE Dimension: Mode: Range: Default Value: Definition: Relationships: Variable - Entity Attribute Text The name of Link-16 defined missile type NONE A valid missile type as defined in Link-16 documentation. This information is used to provide J13.3 (Surface Platform and System Status) message to report on-board missile data for Link16 participating surface platform.
Unit of Measure: N/A
AD LINK16 SITE TYPE Dimension: Mode: Range: Default Value: Definition: Relationships: CC LINK16 SITE TYPE Dimension: Mode: 22 January 2013 Variable - Entity Attribute Text 582 JTLS 4.1.0.0 Variable - Entity Attribute Text The name of a Link-16 site type NONE A valid site type as defined in the Link-16 documentation. This information is used to provide J13.5 (Land Platform and System Status) message to report system status.
Unit of Measure: N/A Range: Default Value: Definition: Relationships: FAT LINK16 SITE TYPE Dimension: Mode: Range: Default Value: Definition: Relationships: ST LINK16 SITE TYPE Dimension: Mode: Range: Default Value: Definition: Relationships: SSM LINK16 MISSILE TYPE Dimension: Mode: Range: Default Value: Variable - Entity Attribute Text The name of Link-16 missile type NONE Variable - Entity Attribute Text The name of Link-16 site type NONE A site type as defined in the Link-16 documentation. This information is used to provide J13.5 (Land Platform and System Status) message to report system status. Variable - Entity Attribute Text The name of Link-16 site type NONE A site type as defined in the Link-16 documentation. This information is used to provide J13.5 (Land Platform and System Status) message to report system status. The name of Link-16 site type NONE A site type as defined in the Link-16 documentation. This information is used to provide J13.5 (Land Platform and System Status) message to report system status.
JTLS 4.1.0.0
583
22 January 2013
Definition: Relationships:
A missile type as defined in Link-16 documentation. This information is used to provide J13.3 (Surface Platform and System Status) message to report on-board missile data for Link16-participating surface platform.
SSM LINK16 SITE TYPE Dimension: Mode: Range: Default Value: Definition: Relationships: Variable - Entity Attribute Text The name of a Link-16 site type NONE A site type as defined in the Link-16 documentation. This information is used to provide J13.5 (Land Platform and System Status) message to report system status.
Two new lookup tables are created in DDS to hold the list of acceptable Link-16 missile types and site types as defined in the Link-16 documentation.
5.0 Order Changes

These orders must be modified to implement this ECP: MANAGE.LINK16.BLOCKS order will be modified to include assigning JU track blocks and target blocks for units. Also, setting the JU number for Link-16 capable SAM, SSM, Communication Center, Facility, and Sensor targets. SET.ADA.PARAMETER order to include the Link-16 Capable Flag, Link-16 Site Type, and Link-16 Missile Type selection fields. SET.COMMUNICATION.CENTER order to include the Link-16 Capable Flag and Link-16 Site Type selection fields SET.FACILITY.PARAMETER order to include the Link-16 Capable Flag and Link-16 Site Type selection fields. SET.SENSOR.PARAMETER order to include the Link-16 Capable Flag and Link-16 Site Type selection fields. SET.SSM.PARAMETER orders to include the Link-16 Capable Flag, Link-16 Site Type, and Link-16 Missile Type selection fields. 22 January 2013 584 JTLS 4.1.0.0
6.0 JODA Changes

Each of the six basic Unit object (ground, support, airbase, squadron, naval, and FARP) will have three Link-16 related attributes ju_number - if set, then the JOI will output PPLI data for the unit. source_ju_number - if set, then the track_ju_number must also be set. When both attributes are set, the JOI will send out track information track_ju_number - if set, then the source_ju_number must also be set. When both attributes are set, the JOI will send out track information. An air mission object will have the same three Link-16 related attributes ju_number - if set, then the JOI will output Air PPLI data for the mission. source_ju_number - if set, then the track_ju_number must also be set. When both attributes are set, the JOI will send out Air track information track_ju_number - if set, then the source_ju_number must also be set. When both attributes are set, the JOI will send out Air track information. The target object will have two Link-16 related attribute ju_number - if set, the JOI must look at the owning/associatged unit to determine whether a Land PPI or a Surface PPLI is sent out. link16_site_type The target category subtype will have additional attributes Add link16_missile_type attribute to the ADA_TARGET_SUBTYPE object Add link16_missile_type attributes to the SSM_TARGET_SUBTYPE object
7.0 Test Plan

Text [Describe the basic test objectives and procedures. This Test Plan section may be published as a separate document.] 7.1 Test 1 Title Purpose: [Describe the specific feature, function, or behavior to be tested or measured.] JTLS 4.1.0.0 585 22 January 2013
Step 1: Text Step 2: Text Expected Results: [Describe the specific model behavior to be observed.] 7.2 Test 2 Title Purpose: Text Step 1: Text Step 2: Text Step 3: Text Expected Results: Text
22 January 2013
586
JTLS 4.1.0.0

JTLS 2012 11412

Transféré par

Informations du document

Description originale:

Titre original

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

JTLS 2012 11412

Transféré par

Droits d'auteur :

Formats disponibles

Design Plan JTLS-2012-11412

ROLANDS & ASSOCIATES Corporation

JTLS-2012-11412 Expand Link-16 Messages

1.0 Summary of Model Change Request

2.0 Design Summary

ROLANDS & ASSOCIATES Corporation

Design Plan JTLS-2012-11412

Design Plan JTLS-2012-11412

ROLANDS & ASSOCIATES Corporation

3.0 Detailed Design

ROLANDS & ASSOCIATES Corporation

Design Plan JTLS-2012-11412

Design Plan JTLS-2012-11412

ROLANDS & ASSOCIATES Corporation

INFORMATION PROVIDED IN JTLS

Number of entities represented by a single track

Interceptor (default) MIsc All units except bases and ships

ROLANDS & ASSOCIATES Corporation

Design Plan JTLS-2012-11412

Design Plan JTLS-2012-11412

ROLANDS & ASSOCIATES Corporation

ROLANDS & ASSOCIATES Corporation

Design Plan JTLS-2012-11412

Table 3. Land Activity Mapping Guide

Design Plan JTLS-2012-11412

ROLANDS & ASSOCIATES Corporation

JTLS UNIT POSTURE OR TARGET STATUS

ROLANDS & ASSOCIATES Corporation

Design Plan JTLS-2012-11412

JTLS UNIT POSTURE OR TARGET STATUS

INFORMATION PROVIDED IN JTLS

REFERENCE TRACK NUMBER (I) ELEVATION (I)

The reference JU number (JU) of land point/track elevation in feet

Design Plan JTLS-2012-11412

ROLANDS & ASSOCIATES Corporation

INFORMATION PROVIDED IN JTLS

ROLANDS & ASSOCIATES Corporation

Design Plan JTLS-2012-11412

INFORMATION PROVIDED IN JTLS

use JODA attribute TG.PERCENT_CAPABLE?

Design Plan JTLS-2012-11412

ROLANDS & ASSOCIATES Corporation

ROLANDS & ASSOCIATES Corporation

Design Plan JTLS-2012-11412

LINK-16 SM2 BLOCK IV SM2 BLOCK IVA

TOMAHAWK (TASM) TOMAHAWK (TLAM C) HARPOON SM3 (LEAP)

Design Plan JTLS-2012-11412

ROLANDS & ASSOCIATES Corporation

Table 7. Land Platform and System Status (J13.5)

INFORMATION PROVIDED FROM JTLS

OPERATIONAL CAPABILITY REFERENCE TRACK NUMBER (I) SITE TYPE(I)

LSID INTERPRETS LSID_OTHER

NO STATEMENT ADOC SOC SOC/CRS CRC CRP

LSID_OTHER LSID_OTHER LSID_OTHER LSID_OTHER LSID_OTHER

ROLANDS & ASSOCIATES Corporation

Design Plan JTLS-2012-11412

Design Plan JTLS-2012-11412

ROLANDS & ASSOCIATES Corporation

INFORMATION PROVIDED IN JTLS

ROLANDS & ASSOCIATES Corporation

Design Plan JTLS-2012-11412

INFORMATION PROVIDED IN JTLS