7791 record(s) found.
Improvement List
| Info | Area | Subarea | Description | |||
|---|---|---|---|---|---|---|
| Database | DDS Selection by RIC Allow user to select a CS by RIC as well. If we want to insert a new TUP (SUP-HUP) by knowing the RIC, we have to filter CS table by RIC and then copy the name of the CS and insert it in the TUP CS table. By allowing a user to insert a CS by typing the RIC it will make the process easier, without opening multiple tables. Same concept might be applied to POT but this is probably more demanding (pre filter by Target type). | ||||
| Database | DDS Prototype Selection The DDS user wants to change the prototype of multiple units to a given prototype. To do this they use the multiple record “Set Value” capability. They: • Highlight the records that should be changed, • Go to the column header for the data parameter that should be changed, in this case the Prototype column • Right Click and select the “Set Value” option. • This presents a drop-down list of all Tactical Unit Prototypes. There is no way to type in the prototype name to “cull” or “whittle” down the list. You must scroll through the extremely long list looking for the one prototype you need. This is difficult and time consuming. This Multi-Record Set Value Drop-Down list should work exactly like the list works when you go to the unit’s individual prototype cell. You start typing in the name of the desired prototype and the drop-down list opens, and the list is whittled down shows only the TUPs that start with the letters being typed. This will make it easy for them to find and select the prototype they you want. This should be a “general” capability – and not limited to just the Unit Prototype Multi-Record Set Value function. All Multi-Record Set Value Drop Down lists should work this way. | ||||
| Database | CAP Codes in Database Prototypes express a specific capability. In NATO we have CAP codes list. Such a list is updated yearly. Every prototype can be assigned multiple cap codes (like CS). In JWC repository capabilities are nowadays recorded as a Comment field. This is making the update mechanism extremely complex. | ||||
| Database | APP6 Symbols in JDSP Alter the JSYMS program to have two Graphics Symbol identifiers, one for 2525 and one for APP6. The two symbol identifiers will be placed in the JSYMS save files and will be read in by the model. Every unit will have two JODA attributes for their symbol identifier, one indicating the unit’s 2525 Symbol identifier and one for the unit’s APP4 identifier. These same two attributes will be represented in the SDR database. The model takes the baseline identifiers created within JSYMS and adds information such as echelon and country code. Currently the Country Code format that should be used is hard-coded within the CEP. This will change and become two database parameters, “2525 Country Code Type” and “APP6 Country Code Type”. The published unit identifiers will use the Country Code specified in the database. Currently JTLS-GO does not use the Graphics Symbol identifiers. They are provided to support the interface between JTLS-GO and various C4I systems. The only C4I Interface Program that uses the identifier is Land Command and Control Information Service (LC2IS), which we have been told will no longer be supported. Updating LC2IS Message Service is not expected to be a significant change and will be accomplished under this FMR if there is a need to do so. he proposal or issue here. | ||||
| Tools | Allow Political Country Region Filtering Both the WHIP IMTs and the DDSC Tables have the ability to filter by geographic regions that are definable by the users. The JTLS-GO database has the geographic Regions defined by the represented Pollical Countries. The desire is to allow the user to filter on the Political Country regions. | ||||
| Database | DDS Combat System Access For Units User should be able to access a specific unit's prototype (and possibly the prototype CS) from the unit table. Similar functionality as user has today for unit owned targets. | ||||
| WHIP | Command Hierarchy Name Alias Support User should be able to visualize (and search) for units in the ORBAT window using both short name and C4i name or both (visualize both values). Developer note: Should it be limtied to those two names or all anes that a unit can have, Short name, long name, UIC, C4I Name. | ||||
| Tools | Make Classification Available In JDSP Although Classification was recently added to the JDSP Simulation State Object, it is currently not fully implemented across all JTLS-GO Tools and Programs. This ECP is designed to fully implement the change so the controller can simply change game classification and all program that need game classification will obtain that information from the JODA data structure or the SDC as appropriate. | ||||
| Model | Intel | Handle Large DSAs In our work to improve our use of satellite functionalities, we have identified an issue with the current collection method using DSA. We need to be able to utilize collections in bigger areas than 10000 sqkm. Our proposal is to introduce a new order for collection interests specifically tied to satellite collection. | |||
| Model | Represent AirFish Drne The AirFish Drone is a Wing-In-Ground (WIG) Aircraft that creates an air cushion allowing the aircraft to fly low over water. Its characteristics need to be better integrated with a wide variety of other aircraft capabilities that JTLS-GO currently cannot represent. ->Float Planes, like the AirFish, which must take off and land in water ->Fixed Wing Aircraft that do not need a runway. They are launched from a catapult type system and parachute back to the ground. ->Look at the "Loyal Wingman" drone concept. The entire concept of equating: ->Fixed Wing with runway takeoff and landing requirement and fast ->Rotary with no runway requirement and slow is no longer working for everything. | ||||
| Model | Automatically Load Breakpoint File Some users do not allow changes to be made to code during an exercise. Instead, model experts must develop ways to catch cashes before they happen and develop work arounds. This normally means setting a breakpoint in the code prior to bad code being executed. Some exercises can have 10 or 20 breakpoints. If the model is restarted and the breakpoint file is not submitted to the model, it is bound to crash again when already deleted errors occur again. The desire is for tje breakpoint file to be loaded automatically. Technically I don't have a clue of how to implement this. | ||||
| Tools | Refresh Of CEP Start Panel User would like a Refresh button on the CEP start Panel. This user leaves the CEP Start Panel open at all times and it doesn't know about new checkpoints as they are created. Instead of closing the panel and reopening the panel, they user wants a refresh button | ||||
| Tools | Create Automated Synchronization Tool User wants a tool to automatically synchronize game time to real time is we are coming up from a crash or fall behind for any other reason. | ||||
| WHIP | Desire To Have Multiple WHIP Layouts Currently you can have only one WHIP layout. The user wants named layouts similar to the Filter and views. | ||||
| Model | Air | Need Current Manual Pair Flag On IMT The current manual pair flag should be on the IMT. | |||
| WHIP | Allow User Selection Of E-mail Output Format Code exists to format e-mail output of IMT screens as either plain text with columns separated by a bar ("|"), plain text with data quoted and columns separated by a comma, plain text with columns separated by tabs, or data embedded in an HTML table. Despite the various output formats available, the code is hard- coded to a single format. It would be desirable for the end user to specify which output format they desire. | ||||
| Model | Log | Provide Capability To Select Exact Types Of Truck In A Convoy The desire is to expland the Directed Resupply Order to allow the user to indicate exactly what trucks by type and number that should be assigned to the convoy. | |||
| Model | Intel | AAR Collect All DSA Data Currently the AAR does not get the detection data for Combat Systems and wreckage seen in DSAs. A detection event is sent to the AAR via 2 JDSP objects: an AAR_DETECTION_EVENT identifies the object doing the detection, the sensor, the DSA searched if a DSA is involved, etc; a series of AAR_DETECTION_ITEMS identify each item detected, their location, and their percent capable. This provides only the most basic detection information and does not provide the detailed information expected in a DSA report including numbers and types of combat systems, wreckage, etc. | |||
| Model | Represent Impact of Jammer Altitude On Jamming Power Currently the altitude of a jammer on an aircraft or satellite is not considered as part of the jammer power degradation. The end user believes it should. | ||||
| Model | Player Orde rTo Transfer SAM/AAA TArget Supplies The players want to take supplies from a SAM/AAA target and give those suppli9es to someone else. The controller can do this from the SET TARGET PARAMETER order followed by a LOGIN BUILD order to another unit. Taiwan believes this capability should be available to the player. They don’t want the magic movement of the supplies, just the ability to take supplies away from one owned target with the Directed Resupply order and take those supplies to a different unit. | ||||
| WHIP | Order Map Selection For Barriers. Users have requested that a map select capability be added to Barrie fields within order panels. | ||||
| Model | Represent Artillery Firing Limitations Tech Control is discussing what can be done to stop the users from putting in so many explicit fire missions. The players are not comfortable with Lanchester. One idea is to add a max number of rounds that can be fired in an hour from a gun before is gets “too” hot to be used properly. | ||||
| Tools | New Air Defense AAR Report Taiwan would like a new AAR Air Defense report that lists Air Defense kills broken out by type of Air Defense Site firing and type of Aircraft kill. | ||||
| Model | Loitering Munition Landing Capability Representation The player put up a loitering munition UAV for a length of time that was beyond its flight time capability. The UAV indicated that it was not air-to-air refuelable and when fuel was needed, it found an airbase from which to get fuel. Although some loitering munition UAVs, such as the Harpy, can land, not all of these UAVs can land once they have taken off. This distinction needs to be made. | ||||
| Model | Different Aircraft Class SCores The Taiwan staff was looking over the Combat System Score data. They believe that JTLS-GO needs a score by Aircraft Class and not the generic score for Combat System Aircraft. For example, CS AIRCRAFT has a score of 40 but an Armor unit with a small UAV should not consider the UAV that important. | ||||
| Tools | Select OPM Available Pages By Side Taiwan does not want their players to see Probability of Hit (pH) and Probablity of Kill (pK) data. Each time the OPMs are generated, they manually go in and delete the pH and pK OPM pages. We informed them that this procedure works fine for JTLS-GO 6.2 but because of changes to JTLS-GO 6.3, the same procedure will not work. Fixing this problem so it meets both the needs and desired of Taiwan and the needs and desired of other units, has been placed on the JTLS-GO ECP list. | ||||
| WHIP | Generate Alert When HRU Raids ARU Land cell players would like to see an alert triangle when an HRU raids an ARU and vice-versa. Currently, only the message browser indicates the attack is occurring. | ||||
| Tools | Create An OBS File From A JTLS-GO Scenario The desire is to take an existing JTLS-GO scenario and develop a tool to create a legal JTDS OBS file that can be uploaded and shared with other JLVC Federates. | ||||
| Tools | Create A JTLS-GO Scenario From JTDS OBS File The Joint Training Data Services (JTDS) has an Order of Battle Service (OBS) that creates a unified Order of Battle for all of the federates that belong to the Joint Live Virtual Constructive Federation (JLVC). JTLS-GO needs to be able to read this OBS file and create its scenario databases. Note this ECP does not address which JLVC federales with which JTLS-GO is envisioned to federate. The ECP purely request building such a scenario from the information available in and OBS file. | ||||
| WHIP | Browser Based WHIP - Or WHIP 2.0 Develop a new WHIP that has a 3D Map and Complete Redesign and works inside the browser vice stand-alone Java app | ||||
| Model | Represent Jammers On Satellites Satellites should be allowed to conduct all types of jamming operations: Weapon, Sensor, and PSYOP. | ||||
| C4I | Containerize JTLS-GO Numerous customers what a containerized version of JTLS-GO. Build it! | ||||
| Database | Support New US Air Planning Tool, KRADOS The US is developing a new Air Planning Tool that will be used to plan and publish daily Air Tasking Orders. This new system is called Kessel Run All Domain Operations Suite (KRADOS). JTLS-GO needs to be able to link and accept ATOs from this new system. | ||||
| Database | DDSC Layout Save And Restore The DDSC has no layout save and restore feature like the WHIP has. It should have the same capability. | ||||
| WHIP | Allow Users To Change Their Own Password Currently if a user wants to change his or her password, they must call Tech control to reset the password to the Default password and then relog in to give themselves a new password. Take Technical Control out of this process. | ||||
| Model | Navy | Add Spoofing of Ship Positions to Mimic AIS It would be nice to use the model to spoof the positions of ships. This capability would mimic the ability to hide ships using AIS. | |||
| Model | Log | Controller Damage Supplies Order Improvements This ECP provides for expanding the options available to a Controller on the DAMAGE SUPPLIES order. Currently, the order only includes the option to enter a single supply category, how much to damage, and a text reason. The result is that the single supply is damaged for one unit. The following change is requested: the Controller can submit a list of Supplies that should be destroyed. | |||
| Tools | Request for Unit Tables in OPM By Unit Type A player in the Naval Cell requested the ability to view a list of ALL Naval Units in the game. This table should be searchable and filtered to find units by their attributes (such as ship class or by prototype). This proposal should be generalized to allow the user to select subsets of all units by filtereing by unit type (such as GROUND, SQUADRON, NAVAL, etc.). | ||||
| Model | Navy | Better Representation Of Sonobuoy Fields Currently in JTLS-GO to represent a sonobuoy field, the database builder needs to create a mission load that has the sonobuoy supplies. They must be available for the mission launch. In addition, the mission should be given a sonobuoy sensor. When the mission leaves the Patrol area, the sonobuoys are considered ineffective and are not really represented. It would be more realistically modeled where they remain active for their lifespan and can communicate what they hear back to the mission that emplaced the buoy, a follow-on mission or even a nearby ship. | |||
| Database | Give Factions Colors Different From Force Color Want to have factions with their own color. | ||||
| Tools | COA - Course of Action in ATO Would love a feature to let air tasks have some sort of comment referencing the specific COA to which it applies. For example, an offensive air support mission with 3 different targets, the tasking of which depends on other happenings. If we could have some sort of comment behind the tasks, we could simply put everything in one order and then decide which ones that won't be used once we know the COA. As this was explained, Coarse Of Actions (COA) for air missions are the two or more intentions the missions may need to fly depending on events that unfold later in the game. The ATO would have the flexibility to double and triple task squadron missions. In other words, use missions to fly two or more different tasks and, at the proper time for a decision, only employ one of those tasks. I suspect JWC has considered this same option, and some procedure used to solve it. Maybe the ATO could mark a mission as a primary COA, secondary COA, etc. In this way the Translator could add the orders to separate order groups. | ||||
| WHIP | UIC in Sitrep window Selected unit in WHIP, should also display UIC in the Sitrep window. UIC is often a key-field in connected system, and now an operator needs to open the Info window and turn on the UIC column to get the UIC for a unit. | ||||
| Model | ELINT Sensors on Satellites To Report Only On DSAs Client would like to be able to use ELINT satellites to report on DSAs and only DSAs, and not on everything within detection radius of ELINT sensor. | ||||
| C4I | Exercise Log Generalization JWC wants to use the Exercise Log as a general issue log that can be used across exercises. This is a current capability of the Exercise Log, but to work as they envision, they would like to add another field called the Event. Thus each Log The Issue would be created at a specific Event so they can filter on it. This ECP also implies that if we update or change the database format we must provide an update capability. | ||||
| Model | Not All Signature Targets Have Side Signature targets such as Aircraft and Vehicle targets do not have an owning or associated unit and therefore they have no side. In a recent exercise there was a need to represent these types of targets and have a side. | ||||
| C4I | Easy Way To Create JTLS-GO Targets For ATO A given Air Tasking Order (ATO) may specify that a target be hit and the target does not exist in the scenario. An easy way to create the target is needed instead of requiring Senior Control to create the target manually. This may be a part of the MIDB Tool or even the ATO Translator. | ||||
| Model | Allow Multi-Target Attack Against Coordinates This has been brought up numerous times, but I could not find an existing ECP or Issue Log Entry. The user wants to be able to drop weapons on a specific coordinate with the Multi-Target Attack order. | ||||
| WHIP | ACMs Selectable On Map Like ICC A user requested that an ACM be selectable from the map, as ICC allows an ACM to be selected. I looked at ICC, and the outlines of each ACM is visible. If the user clicks on the outline of the ACM, then it is the selected object. Once the ACM is a selectable object, then the ACM should have a context-sensitive menu. | ||||
| Tools | Create JTOI JTLS Posture To ICC Posture Conversion Table Currently, the JTOI takes an Air Mission's posture and converts it to a posture recognizable to ICC. In a recent exercise, it was discovered that the code linked a posture of 'WAITING' to ICC 'FLYING' A mission in a WAITING Posture is on the ground and should have a closer ICC posture. The exercise audience suggested 'On Alert', but that seems misleading. Thus, the reason for an external data file that the JTOI can read and that can be changed to meet the whims of the AOC. | ||||
| WHIP | Add Time To Alert Messages Displayed On WHIP Currently, an Alert packet from the model is displayed on the WHIP. If a user is busy and does not review these alerts promptly, there is no way to determine if the alert is current or old information. A time should be placed in the alert message to help users determine if the alert information is old or new. This is related to ECP 2015-12491 requesting that the alert messages be stacked chronologically. |
© 2025 Valkyrie Enterprises LLC
