jtls-2012-11412 expand link-16 messages - … expand link-16 messages ... (2.8.2) and provid es the...

Design Plan JTLS-2012-XXXXX ROLANDS & ASSOCIATES Corporation

JTLS 4.1.0.0 575 25 February 2013

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 Link-16 Surface-to-Air Missile Command and Control System (SAMC2) Interoperability Demonstratorknown as Link 16 Intelligent Decision Tool (LSID), JTLS must produce several new Link-16messages. LSID is part of the new version of ICC (2.8.2) and provides the capability to display themissile defense situational awareness picture using Link 16 Data. The following messages mustbe 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 *** remove???

• J 10.2 Engagement Status

2.0 Design Summary

In current JTLS, several Link-16 messages are being generated and provided to the C4I systemfrom the JTLS Operational Interface (JOI) Program. The JOI can provide the following Link-16messages:

• Air Precision Participant Location and Identification (PPLI), J2.2 - This message is sent outfor 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 thefollowing data are included in the message; speed, course, location, platform, mode2,etc.

ROLANDS & ASSOCIATES Corporation Design Plan JTLS-2012-XXXXX

25 February 2013 576 JTLS 4.1.0.0

• Land Point PPLI, J2.5 - This message is sent out for Link-16 capable ground based unitsand 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 ellipsedata.

• Emergency Point, J3.1 - This message is sent out to report an emergency situation, suchas DOWN AIRCRAFT.

• Air Track, J3.2 - This message is sent out for air tracks that are detected by Link-16capable 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 aBallistic 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 ofan 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-2012-11377 Link 16 Surface Tracks. With this ECP, the JOI will provide five additional new messagetypes:

• 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 andtracks

• 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 participatingtracks

The J13.3 and J13.5 messages will work in similar manner as the J13.2 messages which provideadditional status/weapon information for the air PPLI/tracks that are currently being reported tothe C4I system.


JTLS 4.1.0.0 577 25 February 2013

3.0 Detailed Design

The key to this ECP is understanding the message requirements and how to provide the datafrom 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 requiredto be able to generate the Link-16 acceptable data values if the information is currently notavailable in JTLS.

Following subsections will each describe new message type that will be generated in JTLS. One ormore tables under each section will list data elements that JOI will provide for the specified Link-16 message type. Instead of trying to supply most of the fields on each message type, we willconcentrate 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, adefault 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) 16Message 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 generatingthe J2.3 andJ2.5 messages. Currently, when JU numbers were assigned to the ground-based orsurface-based units, JOI was producing the PPLI messages to report the position of units. We willadd 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 currentlocation. These are:

• Air Defense Targets - Their characteristics are defined by the Air Defense Class entity, Thisentity will have a new database parameter called AD.LINK16.CAPABLE.

• Sensor Targets - Their characteristics are defined by the Sensor Type entity. This entity willhave a new database parameter called ST.LINK16.CAPABLE.

• Surface-to-Surface Missile Targets - Their characteristics are defined by the Surface-to-Surface or SSM entity. This entity will have a new database parameter calledSSM.LINK16.CAPABLE.

• Facility Targets - Their characteristics are defined by the Facility entity. This entity will havea new database parameter called FAT.LINK16.CAPABLE.


25 February 2013 578 JTLS 4.1.0.0

• Communication Targets - Their characteristics are defined by the Communication Centerentity. 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 TrackNumber (STN) in each message header. The current mechanism of assigning JU numbers will beexpanded so that we can assign the JU numbers for the targets to participate the Link-16network.

The most difficult design decision concerns how are Link-16 entities going to be assigned theirju_number and if needed their track blocks that should be used. The problem is confused by thefact that the database team may decide not to build the individual targets, but instead use thePrototype Owned Target (POT) capability. POT targets do not exist in the database, they arecreated when the unit is initialized in the model. This means that the database cannot alwaysspecify the ju_number information leaving the assignment of this data until the last minute whethe game is initialized. One of the purposes of this design is to alleviate that burden from gamecontrollers.

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 notchange. 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 blockof track numbers. When an aircraft takes off, it takes a JU Number from the list and itsassociated 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 hasan air search sensor and a surface search sensor has two different track blocks. This iscontrary to the manner in which the real-world operates. The ship owns the track blockand will assign track numbers from its block irregardless of whether the track is an airtrack 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 BLOCKEND 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


JTLS 4.1.0.0 579 25 February 2013

in the target’s assigned TG JU NUMBER. Those targets will then be sending out Link-16PPLIs. If the target detects something, it will look to its parent and pickup a JU TrackNumber from the unit’s block.

Of these three types of targets, only Air Defense targets can be placed on the game board in anindependent 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 PLATFORMand LAND ACTIVITY data elements for the J2.5 messages. The table displays the key dataelements in the message.

Table 1. Land Point PPLI (J2.5)

The following table provides the mapping guideline for the Land Platform data element for bothJ2.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 groundbased units. We will expand the mapping so that we can also assign the platform field for targetsof interest. The Link-16 documentation provides the complete list of acceptable values withdescription.

Table 2. Land Platform Mapping Guide

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

ELEVATION, 25 FT (I) Elevation in feet above mean sea level 0

LATITUDE (E0) Position of the track UT.LOCATION/TG.LOCATION

LONGITUDE(E0) Position of the track UT.LOCATION/TG.LOCATION

LAND PLATFORM (C1) Link-16 acceptable platform see Table 2. Land Platform Mapping Guide

LAND ACTIVITY (C1) Link-16 acceptable activity see Table 3 Land Activity Mapping Guide

LINK-16 LAND PLATFORM BIT CODELSID

INTERPRETATIONJTLS UNITS/TARGET

NO STATEMENT 0 Interceptor (default)

TROOP CONCENTRATION/UNIT 1 MIsc All units except bases and ships


25 February 2013 580 JTLS 4.1.0.0

HEADQUARTER COMPLEX 2 Misc

COMMAND/CONTROL/COMMAND AND CONTROL CENTER

3 C2

ASSEMBLY AREA 4 Misc

INSTALLATION/FACILITY, MILITARY 5 Misc facility target

INSTALLATION/FACILITY, CIVILIAN 6 Misc

AIRFIELD/AIRBASE 7 Misc All airbases

PORT/HARBOR FACILITY 8 Misc

STORAGE SITE 9 Misc

TACTICAL POSITION 10 Misc

FORTIFICATION 11 Misc

INTERSECTION 12 Misc

CONVOY 13 Misc

COMBAT VEHICLE 14 Misc

COMBAT SUPPORT VEHICLE 15 Misc

VEHICLE, OTHER 16 Misc

TANK 17 Misc

TRAIN 18 Misc

REMOTELY PILOTED VEHICLE 19 Misc

MORTAR 20 Misc

FIELD ARTILLERY 21 Misc

AIR DEFENSE ARTILLERY 22 Misc

ROCKET LAUNCHER 23 Misc

MISSILE LAUNCHER 24 Interceptor All SSM targets

SPECIAL WEAPON 25 Misc

BRIDGE 26 Misc

BUILDING/STRUCTURE 27 Misc

POWER FACILITY 28 Misc




JTLS 4.1.0.0 581 25 February 2013

For the LAND ACTIVITY, the following table provides the list of Link-16 activities that we arecurrently providing based on the unit’s posture including High Resolution Units. For ground basedtargets, we will use the status of target to determine the activity. The complete list of the LandActivity is provided in the Link-16 documentation.

RAIL FACILITY 29 Misc

TERRAIN 30 Misc

NAVAID SITE 31 Misc

COMMUNICATION SITE 32 Misc communication sites

RADAR SITE 33 Sensor All Sensor targets

SURFACE-TO-AIR MISSILE (SAM) SITE 40 Interceptor All SAM targets

MARITIME HEADQUARTERS 41 Misc

AIR SUPPORT RADAR TEAM (ASRT) 42 Misc

DIRECT AIR SUPPORT CENTER (DASC) 43 Misc

FORWARD AIR CONTROL PARTY (FACP) 44 Misc

BATTALION OPERATIONS CENTER (BOC) 45 C2

TACTICAL DATA SYSTEM (TDS) 46 Misc

DECOY 47 Misc

TRACKED VEHICLE 48 Misc

THEATER HIGH ALTITUDE AREA DEFENSE (THAAD)

49 Misc

JOINT TACTICAL GROUND STATION (JTAGS)

50 Misc

ARMOR 51 Misc

CAVALRY 52 Misc

ENGINEER 53 Misc

AIRBORNE/SPECIAL OPERATIONS 54 Misc

AVIATION 55 Misc

AIR DEFENSE SITE 56 Misc

BALLISTIC MISSILE DEFENSE SITE 57 Misc




25 February 2013 582 JTLS 4.1.0.0

Table 3. Land Activity Mapping Guide

LINK-16 LAND ACTIVITY BIT CODEJTLS UNIT POSTURE OR TARGET

STATUS

NO STATEMENT 0 Default if none of the other situations do not apply.

HOLDING 1 DEFEND

DELAYING 2 DELAY

MOVING 3 MOVING

DETECTING 4 TURNED_ON Sensor targets

ACQUIRING 5 SAM Targets that have enemy aircraft within detection range.

ENGAGING 6 SAM Targets that have fired on an enemy aircraft. It will stay in this activity until the Target is free to fire again.

ADVANCING 7

ANTIAIR ATTACK 8

AMPHIBIOUS ASSAULT 9 AMPHIBIOUS

FIRING/LAUNCHING 10 SSM Target that has a status of SETUP.

CONVENTIONAL ATTACK/ASSAULT 11 ATTACK

SPECIAL WEAPONS ATTACK 12

DEMOLITION 13 An HRU on a raid against a neutral target.

OVER THE HORIZON TARGETING 14

TRANSITING 15 An HRU moving to a task area.

RETURN TO BASE 16 HRUs REJOIN PARENT

DEPLOYING 17 An SSM with a status of SETTING UP

EMISSION CONTROL (EMCON) 18

RIVER CROSSING 19

LOADING 20

TOWING 21


JTLS 4.1.0.0 583 25 February 2013

BUILDING FORTIFICATION BARRIER 22

CLEARING BARRIER 23

RECOVERING EQUIPMENT 24

MINE SWEEPING 25

MINE LAYING 26

JAMMING 27

RECONNAISSANCE/PATROLLING

28 PATROL

SEARCH AND RESCUE (SAR) 29

TRAINING 30 TRAINING

MEDICAL EVACUATION (MEDEVAC) 31 A Downed Pilot when it is recovered by an Air Mission.

ESCORTING 32

TRANSPORTING 33

SCREENING 34

SUPPORTING 35

REPAIRING 36 A target that is currently being repaired.

REFUELING 37

NEUTRALIZING 38

TARGETING 39

BYPASSING 40

CLOSING 41

CONCENTRATING 42

DEFENDING 43 DEFEND

DISENGAGING 44

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


STATUS


25 February 2013 584 JTLS 4.1.0.0

For Link-16 participating surface based targets, we will provide the location and the surfaceplatform 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 capableresources. The JOI will provide the Initialization word (I), Extension word 0 (E0), and Continuationword 1 (C1). The following table lists the required data elements for the LSID.

Table 4. Land Point Track (J3.5)

INTERDICTING 46

LANDING 47

OCCUPYING 48

DISPERSING 49

SUPPLY/RESUPPLY 50

RETROGRADE/WITHDRAWING 51 WITHDRAW

TRANSMITTING 52

ELECTRONIC WARFARE SUPPORT (ES) 53 A unit that has a Radar Jammer that is turned on.

ELECTRONIC ATTACK (EA) 54 A unit that has a Radar Jammer that is turned on.

MOVING EQUIPMENT 55

POWER UP AND MANNED, NOT EMITTING

56

PREPARATION FOR LAUNCH 57 PREPARINGSSM targets

SITE SHUT DOWN TO UNPOWERED STATUS

58


REFERENCE TRACK NUMBER (I)

The reference JU number (JU) of land point/track assigned JU number from the JU block of reporting source

ELEVATION (I) elevation in feet elevation if known, NS otherwise


STATUS


JTLS 4.1.0.0 585 25 February 2013

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 asset’s JUnumber is used as the source and the reference track number will be assigned from reporter’sblock 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 isnot "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 asset’sblock (part of J3.3 or J3.5 Initial message).

• source_ju_number - This attribute holds the JU number of the reporting asset (sourcetrack 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 currentJTLS, 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 isnot "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 asset’sblock (part of J3.3 or J3.5 Initial message).

• source_ju_number - This attribute holds the JU number of the reporting asset (sourcetrack number as part of J3.3 or 3.5 header).

POINT/TRACK INDICATOR (I)

POINT or TRACK (POINT for stationary objectTRACK for mobile ground object)

POINT

LATITUDE (E0) position of the point/track known location of the object

LONGITUDE (E0) position of the point/track known location of the object

LAND PLATFORM (C1) Link-16acceptable land platform Table 2. Land Platform Mapping Guide

LAND ACTIVITY (C1) Link-16 acceptable Land activity Table 3 Land Activity Mapping Guide

LAND SPECIFIC TYPE (C1)

specific type of point/track Not implemented for this ECP



25 February 2013 586 JTLS 4.1.0.0

For the last 3 data elements in the Table, you can either provide the LAND SPECIFIC Type or LANDPLATFORM with LAND ACTIVITY data. We have selected the second option; provide platform andactivity data. The same data elements also exist in the J2.5 messages and we will use the samemapping guideline as explained in Table 2. Land Platform Mapping Guide and Table 3 LandActivity Mapping Guide.

If the LSID is expecting the LAND SPECIFIC TYPE data element, we will need an additionalmapping mechanism to accomplish the task. For the LAND SPECIFIC TYPE data element, morethan 400 entries are listed in the Link-16 documentation (DFI 810/DUI 001). We may need tocreate a subset of types to be used in JTLS and make it available for database and vocabularyfile.

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 theoperational status and on board systems' status. These additional information will be providedfor the existing Surface PPLIs and Surface Tracks of own side. For any Link-16 participatingsurface-based owning side entities, the on-board missile information is collected and passed tothe C4I system.

The following table list the required fields for the LSID, and the JOI will provide the InitializationWord (I), Continuation Word 1 (C1), and Continuation Word 2 (C2) to meet the requirements. Allthe requested information is available in JODA objects, either in NAVAL or target objects.]

The continuation word 1 message contains the on-board missile information for ships. There are3 sets of data elements to provide, up to 3 different missile types on board. For the data element

Table 5. Surface Platform and System Status (J13.3)



The reference number (JU) of surface PPLI/Track JU number of participating surface object (J2.3 or J3.3)

MISSILE TYPE, 1-3 (C1) The type of missile being reported ship’s own SAMs and SSM target type

OPERATIONAL MISSILE INVENTORY, 1-3 (C1)

An estimated amount of operational missiles. use JODA TG.NUMBER attribute?

NUMBER OF FIRE CONTROL SYSTEMSAVAILABLE, 1-3 (C1)

The number of available fire control systems NS?

3RD AIR SEARCH RADAR Status of 3-dimensional air search radar and their components. (NO STATEMENT, DEGRADED, NON OPERATIONAL, OPERATIONAL)

use JODA attribute TG.PERCENT_CAPABLE?


JTLS 4.1.0.0 587 25 February 2013

MISSILE_TYPE, the Link-16 documents provides a list of 27 acceptable types. We will adddatabase variable to hold the Link-16 missile type information. This variable will be an attributeto 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 BIT CODE EXPLANATION

NO STATEMENT 0

SHORT RANGE SAM 1 RANGE LESS THAN 10 NM

MEDIUM RANGE SAM 2 RANGE 10-50 NM

LONG RANGE SAM 3 RANGE GREATER THAN 50 NM

SHORT RANGE SSM 4 RANGE LESS THAN 15 NM

MEDIUM RANGE SSM 5 RANGE 15-75 NM

LONG RANGE SSM 7 RANGE GREATER THAN 75 NM

SM2(ER) 8 A LONG RANGE SAM

SM2(MR) 9 A MEDIUM RANGE SAM

SM1(ER) 10 A MEDIUM RANGE SAM

SM1(MR) 11 A MEDIUM RANGE SAM

EXTENDED RANGE SAM (SHORT)

12 RANGE 51 THROUGH 99 NM

EXTENDED RANGE SAM (MEDIUM)


EXTENDED RANGE SAM (LONG)

14 RANGE GREATER THAN 150 NM

EXTENDED RANGE SSM (SHORT)


EXTENDED RANGE SSM (MEDIUM)


EXTENDED RANGE SSM (LONG)

17 RANGE GREATER THAN 300 NM

SM2 BLOCK II 18 AN EXTENDED RANGE SAM (SHORT)

SM2 BLOCK III 19 AN EXTENDED RANGE SAM (SHORT)

SM2 BLOCK IIIA 20 AN EXTENDED RANGE SAM (SHORT)

SM2 BLOCK IIIB 21 AN EXTENDED RANGE SAM (SHORT)


25 February 2013 588 JTLS 4.1.0.0

For the three sets of on-board missile data. JOI will provide inventory of up to 3 different missiletypes owned by the surface PPLIs. To access this data, JOI will extract the data from the SAM andSSM targets from JODA that are owned by naval objects. For the 3RD AIR SEARCH RADAR dataelement, we will determine the status based on the air search sensor target’s 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 landplatform. For this ECP, we will provide this message for all Link-16 participating owning side SSMand SAM sites. The following tables lists the required data elements by the LSID. We will providethe Initial Word (I) and Continuation Word 1 (C1) to meet the requirements.

SM2 BLOCK IV 22 AN EXTENDED RANGE SAM (MEDIUM)

SM2 BLOCK IVA 23 AN ANTI-THEATER BALLISTIC MISSILE(TBM) CAPABLE EXTENDED RANGE SAM(LONG)

TOMAHAWK (TASM) 24 A LONG RANGE SSM TACTICAL ANTISHIP MISSILE

TOMAHAWK (TLAM C) 25 A LONG RANGE SSM TACTICAL LANDATTACK MISSILE CONVENTIONAL

HARPOON 26 A MEDIUM RANGE SSM

SM3 (LEAP) 27 LIGHT EXOATMOSPHERIC PROJECTILE - ANANTI-TBM MISSILE (EXTENDED RANGE (LONG)).

UNDEFINED

LINK-16 BIT CODE EXPLANATION


JTLS 4.1.0.0 589 25 February 2013

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

For the SITE TYPE field, the documentation provides a list of 42 acceptable items DFI 1555/DUI001). We will add three new database variables in JTLS to hold this information. This databaseattribute 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). The list ofacceptable site types is provided in the following table. The explanation for different site typesare provided in the Link-16 documentation. The database developer can assign each of thesesite types to the Target Subcategories listed above.

Table 8. Site Type Mapping

LINK-16 DATA ELEMENT DESCRIPTION INFORMATION PROVIDED FROM JTLS

OPERATIONAL CAPABILITY

No Statement, Fully Operational, Partially Operational, or Non operational

derive from the target strength


The reference number (JU) of land PPLI/Track JU number of participating object (J2.5 or J3.5)

SITE TYPE(I) The type of site being reported (from the Link-16 acceptable site type)

select an entry for SAM/SSM targetsNS for all other types

HOT INVENTORY (I) Number of Remaining Hot Missiles on a weapon system

COLD INVENTORY (C1) Amount of cold missiles remaining

PRIMARY SURVEILLANCE RADAR STATUS

Operating status of a primary surveillance radar system (NO STATEMENT, OPERATIONAL, NON-OPERATIONAL, OFF)

TG attribute?

SITE TYPE BIT CODE EXPLANATION LSID INTERPRETS

NO STATEMENT 0 LSID_OTHER

ADOC 1 AIR DEFENSE TACTICAL OPERATIONS CENTER LSID_OTHER

SOC 2 SECTOR OPERATION CENTER LSID_OTHER

SOC/CRS 3 SECTOR OPERATION CENTER /CONTROL REPORTING SITE

LSID_OTHER

CRC 4 CONTROL AND REPORTING CENTER LSID_OTHER

CRP 5 CONTROL AND REPORTING POST LSID_OTHER

AEGIS 6 AIRBORNE EARLY WARNING GROUNDINTERFACE SEGMENT

LSID_OTHER


25 February 2013 590 JTLS 4.1.0.0

TACC (USAF) 7 TACTICAL AIR CONTROL CENTER LSID_OTHER

CRC/MCE 8 CRC/MODULAR CONTROL EQUIPMENT LSID_OTHER

SSSB 9 SHIP SHORE SHIP BUFFER LSID_OTHER

HIMAD BDE 10 HIGH TO MEDIUM ALTITUDE AIR DEFENSE BRIGADE

LSID_OTHER

HIMAD BN 11 HIMAD BATTALION LSID_OTHER

PATRIOT BN ICC 12 PATRIOT BN INFORMATION COORDINATION CENTER

LSID_ABT_SAM

PATRIOT/ECS 13 PATRIOT ENGAGEMENT CONTROL STATION LSID_ABT_SAM

HAWK/AFP 14 HAWK ASSAULT FIRE PLATOON LSID_ABT_SAM

SHORAD BDE 15 SHORT RANGE AIR DEFENSE BRIGADE LSID_OTHER

SHORAD BN 16 SHORT RANGE AIR DEFENSE BATTALION LSID_OTHER

SWC 17 COMPASS EARS LSID_OTHER

TACC (USMC) 18 TACTICAL AIR COMMAND CENTER LSID_OTHER

TADC 19 TACTICAL AIR DIRECTION CENTER LSID_OTHER

TAOC 20 TACTICAL AIR OPERATIONS CENTER LSID_OTHER

ROCC 21 REGIONAL OPERATIONS CONTROL CENTER LSID_OTHER

RADIL 22 ROCC AWACS DIGITAL INTERFACE LINK LSID_OTHER

ASIT 23 ADAPTABLE SURFACE INTERFACE TERMINAL LSID_OTHER

GCI 24 GROUND CONTROL INTERCEPT LSID_OTHER

MPC 25 MESSAGE PROCESSING CENTER LSID_OTHER

TOC 26 TACTICAL OPERATIONS CENTER LSID_OTHER

DIVARTY 27 DIVISION ARTILLERY LSID_OTHER

NIKE 28 NIKE SITE LSID_OTHER

GACC 29 GROUND ATTACK CONTROL CENTER LSID_OTHER

PLSS 30 PRECISION LOCATED STRIKE SYSTEM LSID_OTHER

ENSCE 31 ENEMY SITUATION CORRELATION ELEMENT LSID_OTHER

TGIF 32 TRANSPORTABLE GROUND INTERCEPTFACILITY

LSID_OTHER

FACP 33 FORWARD AIR CONTROL POST LSID_OTHER



JTLS 4.1.0.0 591 25 February 2013

3.1.5 Engagement Status (J10.2)

This message provides the status of a weapon engagement between two JUs, the ReferenceTrack and the Target Track. Since the engagement status changes so rapidly, the CEP cannot useJODA 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) andContinuation Word 2 (C2).

Table 9. Engagement Status (J10.2)

TOC (THAAD) 34 TACTICAL OPERATIONS CENTER (THEATERHIGH ALTITUDE AREA DEFENSE)

LSID_UPPER_LAYER_SAM

LCS (THAAD) 35 LAUNCHER COMMUNICATIONS STATION (THEATER HIGH ALTITUDE AREA DEFENSE)

LSID_UPPER_LAYER_SAM

SSI (THAAD) 36 SENSOR SYSTEM INTERFACE (THEATERHIGH ALTITUDE AREA DEFENSE)

LSID_OTHER

JTAGS 37 JOINT TACTICAL GROUND STATION LSID_OTHER

ADTOC/BN 38 AIR DEFENSE TACTICAL OPERATIONSCENTER, BATTALION

LSID_OTHER

ADTOC/BDE 39 AIR DEFENSE TACTICAL OPERATIONSCENTER, BRIGADE

LSID_OTHER

ADCP 41 AIR DEFENSE COMMUNICATIONS PLATFORM LSID_OTHER

BM DEFENSE SITE 41 BALLISTIC MISSILE DEFENSE SITE LSID_OTHER

ME SSAMP/T 42 SAMP/T FIRE UNIT LSID_OTHER



The reference JU number of the friendly track assigned JU number from reporting source

TARGET TRACK NUMBER (I)

The reference JU number of the target track assigned JU number from reporting source

WEAPON SYSTEM (I) weapon type from the list

WEAPON ENGAGEMENT STATUS (I)

engagement status of a weapon against an object (select status from the list)

TIME FUNCTION (C2) TIME OF PREDICTED INTERCEPT (=1) orTIME OF ACTUAL INTERCEPT (=2)

1 or 2



25 February 2013 592 JTLS 4.1.0.0

To provide the weapon system and weapon engagement status information, separate tables areprovided below. To provide data for the WEAPON SYSTEM data element, we will define a list ofsystems JTLS can produce from the complete list defined in the documentation. The followingtable 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

MINUTES (C2) minute of the hour

TENTH SECONDS (C2) one tenth of second

WEAPON SYSTEM BIT CODE JTLS?

NO STATEMENT 0 YES - When none of the other situations apply, this will be output.

SURFACE-TO-AIR MISSILE (SAM) 1 YES - If the reporting unit owns any Air Defense Sites with precision guided weapons.

SURFACE-TO-SURFACE MISSILE (SSM) 2 YES - If the reporting unit owns any SSM site targets.

AIRCRAFT 3 YES - if the reporting unit is a squadron with fixed wing aircraft.

CONVENTIONAL (SHORT RANGE MISSILE OR GUNS)

4 YES - If the reporting unit has any Air Defense Sites with non-precision guided weapons.

ANTISUBMARINE WARFARE HELICOPTER 5 Yes - If the reporting unit has any helicopters that are mission capable for Patrol.

ANTISUBMARINE WARFARE MISSILE 6 YES - If the reporting unit has any Torpedo Weapons that are listed as precision guided and have a PK against at least one submarine,

DEPTH CHARGE/DEPTH BOMB 7 YES - If the reporting unit has any Torpedo Weapons that are listed as non-precision guided..

TORPEDO 8 Yes - If the reporting unit has any Torpedo Weapons that are listed as precision guided and have a PK against only surface ships.



JTLS 4.1.0.0 593 25 February 2013

For the WEAPON ENGAGEMENT STATUS data element, the following table provides thedocumented engagement statuses. The JTLS provided statuses are color-coded in green.

Table 11. Link-16 Weapon Engagement Status List

FIXED WING ANTISUBMARINE WARFARE AIRCRAFT

9 Yes - If the reporting unit has any helicopters that are mission capable for Patrol.

LASER 10

BEAM WEAPON 11 Yes - if the reporting unit has any Aircraft-based Beam Weapons.

INFRARED DECOY 12

CHAFF 13

SPOT JAMMER 14 Yes - if the reporting unit owns a jammer that is jamming a specific unit.

BARRAGE JAMMER 15 Yes - if the reporting unit owns a jammer that is jamming a specific side.

DECEPTION JAMMER 16

INTERCEPTOR 17

AIR-TO-SURFACE MISSILE (ASM) 18 Yes - if the reporting unit has any precision-guided weapons that can hit surface targets.

WEAPON ENGAGEMENT STATUS (WES) BIT CODE JTLS PROVIDE?

NO STATEMENT 0 YES

RECOMMEND REATTACK 1 YES - if the assigned weapon has a BDA capability and the target was not fully destroyed.

WEAPON ASSIGNED 2 YES

TRACKING/LOCKED ON/READY TO FIRE/BIRD AFFIRM

3 YES

FIRING/MISSILE IN FLIGHT/ENGAGING TO DESTROY

4 YES

EFFECTIVE/TARGET DESTROYED/GRAND SLAM 5 YES

PARTIALLY EFFECTIVE 6

WEAPON SYSTEM BIT CODE JTLS?


25 February 2013 594 JTLS 4.1.0.0

The special message will be produced by CEP to indicate the engagement between two Link-16tracks. 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-16engagement 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)

• 2 - index to the weapon system (=SSM)

• 2 - index to the engagement status (=WEAPON ASSIGNED)

• 1 - time function (=TIME OF PREDICTED INTERCEPT)

NOT EFFECTIVE 7

ENGAGEMENT BROKEN 8

HEADS UP 9

ENGAGEMENT INTERRUPTED 10

INVESTIGATING/INTERROGATING 11

SHADOWING 12

INTERVENING 13

COVERING 14

BATTLE DAMAGE ASSESSMENT UNKNOWN 15

WEAPON ENGAGEMENT STATUS (WES) BIT CODE JTLS PROVIDE?


JTLS 4.1.0.0 595 25 February 2013

• 25 - 25 minutes

• 24.5 - seconds

3.2 CEP Changes

With additional required information to provide in the messages, the following modifications willbe made in CEP:

• WIth added JU number attributes, CEP will assign the correct JODA JU attributes. Theju_number attribute is used for self reporting Link-16 participating asset, assigned withinthe database or the order. The track_ju_number is assigned from the JU block ofreporting asset when detection occurs and the source_ju_number is the reporter’s JUNumber.

• Generate special message to provide engagement status for JOI to generate J10.2message. The format of the message is provided in 3.1.5 Engagement Status (J10.2). Theweapon system and engagement status information will be added to the model so thatappropriate data can be sent to JOI via the special message.

3.3 SVP Errors/Warnings

These SVP Errors and Warnings will be implemented to support this ECP:

• Error 436: Unit UNIT.NAME's LINK16.TYPE Link16 value 12345 overlaps UNIT.NAME'sLINK16.TYPE Link16 value.

This unit’s JU number, JU number within the Target Block, or JU number within the TrackBlock is being used by another unit. This condition must be corrected to avoid a majorproblem with the C4I systems.

• Error 442: Unit UNIT.NAME has an illegal Track Block POSITION value of 12345.

The Track Block Start or End value is incorrectly formatted. The DDS ensures that aproperly formatted JU number was entered. A nonconforming value was entered into thedatabase in a manner other than the DDS. The Track JU numbers must contain fivecharacters; the first two characters must be alphanumeric (A-Z, excluding I and O, or 0-7)and the last three characters must be numeric (0-7). TADIL-J documentation should bereferenced to ensure complete compliance with TADIL-J regulations, since certain legalvalues are reserved for use by specific Government agencies. JTLS does not check for theentry of a restricted JU Number and only ensures that the JU Number is properlyformatted.

• Error 443: Unit UNIT.NAME has a Track Block Start value 12345 larger than its TrackBlock End value 12345.


25 February 2013 596 JTLS 4.1.0.0

The End Track Block value must be greater than the Start Track Block value so that a JUnumber within the block is assigned to a Link-16 track when detection occurs.

• Error 444: Unit UNIT.NAME has an illegal Target Block POSITION value of 12345.

The Target Block Start or End value is incorrectly formatted. The DDS ensures that aproperly formatted JU number was entered. A nonconforming value was entered into thedatabase in a manner other than the DDS. The Track JU numbers must contain fivecharacters; the first two characters must be alphanumeric (A-Z, excluding I and O, or 0-7)and the last three characters must be numeric (0-7). TADIL-J documentation should bereferenced to ensure complete compliance with TADIL-J regulations, since certain legalvalues are reserved for use by specific Government agencies. JTLS does not check for theentry of a restricted JU Number and only ensures that the JU Number is properlyformatted.

• Error 445: Unit UNIT.NAME has a Target Block Start value 12345 larger than its TargetBlock End value 12345.

The End Target Block value must be greater than the Start Target Block so that a JUnumber within the block can be assigned to the Unit’s owning/associated Link-16capable Targets.

• Warning 401: Unit UNIT.NAME has a Link16 Track Block START and END, but it belongs toa faction that is not Link16 Capable.

The Unit must belong to a Link-16 capable Faction to report Link-16 tracks. The Faction towhich the unit belongs does not have an ACP AIR INFORMATION PROTOCOL of LINK16.Remove the Track Block from the Unit or set the Faction’s ACP AIR INFORMATIONPROTOCOL to LINK16. Correcting this problem is not required, but assigning the Unit aTrack Block of JU Numbers is inconsistent if the Unit is incapable of using them.

• Warning 407: Unit UNIT.NAME has a Link16 Target Block START and END, but it belongs toa faction that is not Link16 Capable.

The Unit must belong to a Link-16 capable Faction to be able to assign JU Numbers toowned or associated Link-16 capable Targets. The Faction to which the unit belongs doesnot have an ACP AIR INFORMATION PROTOCOL of LINK16. Remove the Target Block fromthe Unit or set the Faction’s ACP AIR INFORMATION PROTOCOL to LINK16. Correcting thisproblem is not required, but assigning the Unit a Target Block of JU Numbers isinconsistent if the Unit is incapable of using them.

• Warning 434: Unit UNIT.NAME has a Link16 Track Block, but has no Link16 CapableSensors.


JTLS 4.1.0.0 597 25 February 2013

One or more Link-16 capable Sensor targets are needed to report Link-16 tracks. The Unitdoes not have any owned or associated Sensor targets that are Link-16 capable. Removethe Track Block from the Unit or set the Link-16 Capable flag to "True" for the Sensor Typecategory of the owned or associated Sensor targets. Correcting this problem is notrequired, but assigning the Unit a Track Block of JU Numbers is inconsistent if the Unit isincapable of using them.

• Warning 435: Unit UNIT.NAME has a Link16 Target Block, but has no Link16 CapableTargets.

The JU Numbers within the Target Block are being used by the Unit to assign the JUNumber for the Unit’s owned or associated Link-16 capable targets. The Unit does nothave any owned or associated Targets that are Link-16 capable. Remove the Target Blockfrom the Unit or set the Link-16 Capable flag to "True" for the Target Category of theowned or associated SAM, Sensor, SSM, Facility, and Communication Center targets.Correcting this problem is not required, but assigning the Unit a Target Block of JUNumbers is inconsistent if the Unit is incapable of using them.

• Warning 438: Unit UNIT.NAME has a Link16 Target Block, but has 123 Link16 CapableTargets, but only 123 Target JU Numbers.

The possbile JU Numbers that can be allocated from the Target Block is less than theUnit’s owned or associated Link-16 capable Target counts. Adjust the Target Block Startand End values to hold sufficient JU Numbers.

3.4 JOI Changes

With the current Link-16 capabilities in JOI, no additional setup is required for this ECP. All theexisting network parameters will be used and all the generated Link-16 messages will be sent atevery time interval that was set during the setup process. Currently, no filtering is provided for theLink-16 messages, except when the operator turns the Link-16 feed Off to resolve anynetwork-related issues.

The capability to generate the newly added Link-16 messages will be added to the JOI with addeddata 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 participatingsurface based targets will generate J2.3 and the ground based targets will generate J2.5messages.

4.0 Data Changes

Remove the Sensor Targets, TG LINK16 BLOCK START and TG LINK16 BLOCK END.


25 February 2013 598 JTLS 4.1.0.0

UT LINK16 TRACK BLOCK START

• Dimension: Unit Entity Attribute

• Mode: Text

• Unit of Measure: Five character formatted text, representing an octal number.

• Range: Characters 1,2: A - Z and/or 0 - 7; Characters 3,4,5: only 0 - 7

• Default Value: NULL

• Definition: This is the starting octal number for the tracks that this unit’ssensors detected

• Relationships: This database parameter is related to all of the other Link-16data that exists in the database. There can be no overlapbetween any assigned Link-16 octal number.

On conversion, if the unit owns a sensor target and it has a start block value, it should gointo this new database parameter.

UT LINK16 TRACK BLOCK END


• Mode: Text


• Range: Characters 1,2: A - Z and/or 0 - 7; Characters 3,4,5: only 0 - 7


• Definition: This is the ending octal number for the tracks that this unit’ssensors detected.


On conversion, if the unit owns a sensor target and it has an end block value, it should gointo this new database parameter.

UT LINK16 TARGET BLOCK START


• Mode: Text


• Range: 00000 through 77777


JTLS 4.1.0.0 599 25 February 2013


• Definition: This is the starting octal number for assigning the ju_number forthis unit’s owning or associated Link-16 capable targets.


At the beginning of the game, the model will assigned a JUNUMBER to all of this units, SAM sites, Sensor Sites, SSM Sites,Communication Centers, and Facilities if their target typeinformation indicates that they are Link-16 capable. See thedatabase 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


• Mode: Text


• Range: 00000 through 77777


• Definition: This is the ending octal number for assigning the ju_number forthis unit’s owning or associated Link-16 capable targets.


At the beginning of the game, the model will assigned a JUNUMBER to all of this units, SAM sites, Sensor Sites, SSM Sites,Communication Centers, and Facilities if their target typeinformation indicates that they are Link-16 capable. See thedatabase 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: Sensor Type Entity Attribute

• Mode: Boolean


25 February 2013 600 JTLS 4.1.0.0

• Unit of Measure: A zero mean NO, a 1 means YES

• Range: 0 (NO), 1 (YES)

• Default Value: NO

• Definition: This parameter indicates whether Sensor Targets of this type arecapable of communicating with the Link-16 network.

• Relationships: This database parameter is related to all of the other Link-16data that exists in the database. Targets that are Link-16 Capablewill be assigned a JU NUMBER when their owning unit arrives inthe theater, if the unit has been given a Target Assignment blockas specified by the database parameters UT LINK16 TARGETBLOCK 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 existin the database have a TG TRACK BLOCK START set. If not, then the conversion willinitialize the database parameter to NO.

AD LINK16 CAPABLE

• Dimension: Air Defense Class Entity Attribute

• Mode: Boolean




• Definition: This parameter indicates whether Air Defense Targets of this typeare capable of communicating with the Link-16 network.


On conversion this will always be set to NO.

CC LINK16 CAPABLE

• Dimension: Communication Center Entity Attribute

• Mode: Boolean



JTLS 4.1.0.0 601 25 February 2013



• Definition: This parameter indicates whether Communication Center Targetsof this type are capable of communicating with the Link-16network.



FAT LINK16 CAPABLE

• Dimension: Facility Type Entity Attribute

• Mode: Boolean




• Definition: This parameter indicates whether Facility Type Targets of thistype are capable of communicating with the Link-16 network.



SSM LINK16 CAPABLE

• Dimension: Surface Surface Missile Entity Attribute

• Mode: Boolean





25 February 2013 602 JTLS 4.1.0.0

• Definition: This parameter indicates whether Surface-to-Surface Missile(SSM) Targets of this type are capable of communicating with theLink-16 network.



AD LINK16 MISSILE TYPE

• Dimension: Variable - Entity Attribute

• Mode: Text

• Unit of Measure: N/A

• Range: The name of Link-16 defined missile type

• Default Value: NONE

• Definition: A valid missile type as defined in Link-16 documentation.

• Relationships: This information is used to provide J13.3 (Surface Platform andSystem Status) message to report on-board missile data for Link-16 participating surface platform.

AD LINK16 SITE TYPE


• Mode: Text


• Range: The name of a Link-16 site type


• Definition: A valid site type as defined in the Link-16 documentation.

• Relationships: This information is used to provide J13.5 (Land Platform andSystem Status) message to report system status.

CC LINK16 SITE TYPE


• Mode: Text


JTLS 4.1.0.0 603 25 February 2013


• Range: The name of Link-16 site type


• Definition: A site type as defined in the Link-16 documentation.


FAT LINK16 SITE TYPE


• Mode: Text






ST LINK16 SITE TYPE


• Mode: Text






SSM LINK16 MISSILE TYPE


• Mode: Text


• Range: The name of Link-16 missile type



25 February 2013 604 JTLS 4.1.0.0

• Definition: A missile type as defined in Link-16 documentation.

• Relationships: This information is used to provide J13.3 (Surface Platform andSystem Status) message to report on-board missile data forLink16-participating surface platform.

SSM LINK16 SITE TYPE


• Mode: Text


• Range: The name of a Link-16 site type




Two new lookup tables are created in DDS to hold the list of acceptable Link-16 missile types andsite 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 andtarget 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, andLink-16 Missile Type selection fields.

• SET.COMMUNICATION.CENTER order to include the Link-16 Capable Flag and Link-16 SiteType selection fields

• SET.FACILITY.PARAMETER order to include the Link-16 Capable Flag and Link-16 Site Typeselection fields.

• SET.SENSOR.PARAMETER order to include the Link-16 Capable Flag and Link-16 Site Typeselection fields.

• SET.SSM.PARAMETER orders to include the Link-16 Capable Flag, Link-16 Site Type, andLink-16 Missile Type selection fields.


JTLS 4.1.0.0 605 25 February 2013

6.0 JODA Changes

Each of the six basic Unit object (ground, support, airbase, squadron, naval, and FARP) will havethree 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 bothattributes are set, the JOI will send out track information

• track_ju_number - if set, then the source_ju_number must also be set. When bothattributes 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 bothattributes 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 bothattributes 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 whethera 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 publishedas a separate document.]

7.1 Test 1 Title

Purpose: [Describe the specific feature, function, or behavior to be tested or measured.]


25 February 2013 606 JTLS 4.1.0.0

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

jtls-2012-11412 expand link-16 messages - … expand link-16 messages ... (2.8.2) and provid es the...

Documents