8124 record(s) found.
Improvement List
| Info | Area | Subarea | Description | |||
|---|---|---|---|---|---|---|
| C4I | OTHGold - Add Missile Type Filters The OTH-Gold Message Service needs a filter for type of missile. It currently has a filter for type of convoy. It needs the same type of filter for type of missile. In JTLS-GO 6.3 this will be CRUISE, BALLISTIC, and HYPERSONIC. | ||||
| Database | Document Creating DDS Glassfish Proxy Server In JTLS-GO 6.2, WHIP encrypted passwords were implemented. The desire is to implement encrypted passwords for DDS users too. Instead of implementing the encrypted passwords, the development team is suggesting to place Glassfish behind Apache and use Apache as a proxy server and thus use its password capabilities. | ||||
| Model | Formation Minefield Damage Too Signfiicant When a Formation and its ships travel through a minefield, all of the Naval Units sustain damage. A better model is required. Once the first ship is hit, all other ships in the formation would alter their procedures to reduce the risk of similar damage. | ||||
| WHIP | Different Colors For Different Barrier Types Add the ability to change the colors of barriers by barrier type. They also want this in the DDS. | ||||
| Model | Limit Missile Turn Points Some missiles have a limited number of turn points that the missile is allowed to make. This limitation is needs to be represented in the model. | ||||
| Model | Represent Air Defense Trucks Some ADA sites are a truck and the sensor and the launchers are integrated – you kill one – you kill the other. A model improvement is needed to better representation the difference between a truck ADA Site and an ADA Site as a whole. | ||||
| Model | Improve ADA Percent Capable A UAV dropped a weapon on a SAM site and reported no damage. The controller damage report also says No Damage, but the IMT shows the SAM site as Destroyed. What is going on? The situation is that the SAM site has a jammable Fire Control Sensor and so it automatically goes into Suppression mode. When it is in suppression mode, we mark the Fire Control Sensor as dead which because the AD UNGUIDED PK MODIFIER is 0.0, results in the model computing a Percent Capable of 0.0. After the AD SUPPRESSION TIME Random Draw, the END SUPPRESSION event executes and the sensor is marked Alive again and the percent capable is back to 100% and the SAM site shows alive. Now this entire process is reasonable when looking at the situation from the attacking side. They no longer see the emissions from the Air Defense Site so they assume it is dead. The MISREP could better say – emissions stopped – damage cannot be confirmed. The Controller Damage report could say undamaged but suppressed and give when the suppression will be over. Taiwan personnel asked why we selected the Exponential Distribution for Suppression time. I couldn’t provide a logical explanation. We do need to review this portion of the design and come up with a good solution to the current state of this code. | ||||
| Model | Minimum Ship Required Crew JTLS-GO does not model the minimum crew or personnel required to operate a ship. In fact, it is possible to have no personnel alive and the ship will still operate. This needs to be modeled better. | ||||
| C4I | Only Some Users Shold See AAR WHIP Login Options Our operating method requires that only a select number of user should be able to see the three AAR links on the JTLS-GO WEb Page. Two possible solution are: ->Password protect the three AAR entries on the Login Page →Create two Login Web Pages - one for players and one for Controllers. This is Taiwan’s preferred approach. The reasoning is if users don’t know about the capability they won’t ask for the password. | ||||
| Model | Automatically Store Supplies In Supply Storage Areas Taiwan wants to always store weapons in bunkers - even after being offloaded from aircraft. The desire is to always disperse the supplies but doing so manally through player orders leads to several problems. The model should automatically put supplies in bunkers just like the model automatically fills Equipment shelters. | ||||
| Model | Jamming Electro-Optical Satellite Sensors There is a desire to be able to incapacitate EO sensors on satellites with equipment such as laser dazzlers. | ||||
| Model | Expanded Reactivate Unit Order It is felt that there are too many steps involved in the reactivation of a unit. You need to reactivate the unit, then change its strength, then magic move it where you want it, then change its HQ. Some of the orders are done by the Controller and other, change HQ, by the player. An expanded Reactive Unit order which allowed the Controller to specify all these items at once would simplify the process. | ||||
| Model | Area Report Order Generate an IPIR Both the Controller Target Report and Unit Report orders cause the generation of an intel IPIR message. The Area Report order does not. There are numerous cases where an IPIR from an Area Report would be useful. | ||||
| WHIP | Automatic Shutdown of Idle WHIPS There is a desire for WHIPS that have been idle a certain amount of time, preferably a Tech Control specified time, to automatically disconnect from the services and shutdown. | ||||
| WHIP | Links to Documentation from Order Panels A new user (Canada) requested that there be links between the help on order panels and the documentation. For example, it would be nice to a link from the HRU TASK order to the HRU section of the Analyst Guide. | ||||
| Database | Allow Chinese Characters Throughout Model Allow use of Chinese (Non-ASCII) characters in the WHIP including names of orders and Order Group names. Allowing in the database is another issue too, | ||||
| C4I | Dashboard - Notification Function It would be nice if users could submit notifications that appear on the Dashboard, similar to the WHIP Notification Tool. Notifications could be permanent or transient. Permanent notifications could be presented on a banner at the top of the screen. Transient notifications could be displayed in a 'toast' (https://www.w3schools.com/howto/howto_js_snackbar.asp) or another widget that pops up on the screen and disappears after a timeout. | ||||
| C4I | Dashboard - Monitor ELS The Dashboard service currently monitors the CEP speed and connection. It is desired that the Dashboard support an optional connection to the ELS/EODA for monitoring as well. | ||||
| Tools | Synapse - Create Separate Authentication Service The Synapse currently manages all WHIP files, as well as WHIP login authentication. During high traffic exercises, the Synapse can see performance reduction due to the number of WHIP files it manages. This, as well as slow network performance, can cause noticeable slowdowns when logging users in. The WHIP authentication responsibility of the Synapse should be moved to a separate service. This will reduce strain on the Synapse and lead to better login performance. | ||||
| C4I | OTHGMS - Automend Tracknames A database naming convention is used by many database builders. This convention is to add '_<SIDE>' to each unit. For example, TOP-UNIT_US is a common unit name. A function of the OTHGold Message Service (OTHGMS) is to remove the underscore '_' character and anything after it in the track name. This makes the track names friendly for receiving C4I systems. However, this can lead to side effects where multiple objects derive the same track name. For example, squadron detachments often will have the same track name because of how the model names detachments. For example, squadron 1FS_US will create detachments 1FS_US.1 and 1FS_US.2. These squadrons will all have the same track name of 1FS. To prevent this situation, the OTHGMS should deconflict and mend track names in a smart way so users do not have to complete that process manually. This would only apply when the 'Delete After Underscore in Track Name' option is enabled. | ||||
| WHIP | Allow Sending An AAR Orders With Geographic Regions The WHIP allows many orders to be sent that refer to geographic regions. These regions may be Operation Areas, Air Control Means, Directed Search Areas, Battle Damage Assessment Areas, or Political Countries. These areas are not available for AAR reports because the AAR does not know about the areas. It is desirable to be able to use these same areas for AAR reports by either having the AAR hold the data or by having the WHIP include coordinates of the area when the order is sent. | ||||
| WHIP | Allow Copying of All Information From WHIP SitRep Window The WHIP SitRep window provides a lot of useful information for a Response Cell to feed new detections to the Training Audience, but there is no easy way to copy the data to other formats. I way to copy the entire contents of the WHIP SitRep window is desired. | ||||
| Tools | JSyms Improvements The JSyms tool should have some improvements to ease finding symbols and also to ease the setting of 2525B ID Codes. The 1st and 3rd symbols of the ID Code should be limited to those we actually use for warfighting, Signals Intelligence, and Operations Other than War. The 11th position should allow the setting of the letter H for fixed installations. Users should have a search tool that will look for matches based on name, symbol ID code, 2525B numeric and named hierarchies. Thus, if they know they need an armour combat unit they could enter symbol numeric hierarchy '1.X.3.1.1.2', part of the named hierarchy 'CBT.ARM', part of the ID code 'UCA', or part of the symbol name 'ARMOUR' and a list of all matches and partial matches would be made available, preferably with a small symbol icon next to them. | ||||
| Model | Allow Limit On Munition Usage of Fire Support Units In order to avoid a unit in Direct Support using all its ammunition, when the user might require some for a follow on operation, it is desirable to set a limit on the amount of ammo a unit will use when it is placed in Direct Support. | ||||
| Tools | Web Services Manager Auto-Reload Whenever the Web Services Manager (WSM) determines there is a change to the ICP database it pops up a dialog informing the user. This dialog has only a single button to reload the ICP data and the user can not do anything on the WSM until they have selected it. Since the action is required no matter what, it would be better if the WSM informed the user what was happening and automatically reloaded the ICP database instead of forcing a dialog to be answered. | ||||
| WHIP | Allow Context Sensitive Actions For Multiple Objects A requirement existed to view range rings for multiple ADA targets owned by a variety of units. This required the user to select the IMT screen for each unit, get the owned target IMT screen, then for each ADA target turn on the range ring. Since we were talking about 20+ targets this was a time consuming action. If the user had been able to select the units on the command hierarchy, right click and get an IMT screen with all the selected units, retrieved the owned targets for all those units, then select and right click the owned ADA targets turning on the range rings in one group this would have taken seconds. What is missing is the ability of having multiple objects selected, either on the command hierarchy or the IMT screens, and right click to a context sensitive menu to perform the same action for all the objects. | ||||
| Tools | Redefining Zulu Time And Defining Time Zones Multiple Days In The Future At both the Keen Edge 24 and the previous Citadel Bonus 23 an attempt was made to adjust a timezone Unit of Measure to add time to the simulation. At Citadel Bonus the attempt was made to redefine Zulu as the baseline time plus 12 hours, whereas at Keen Edge 24 the attempt was to add a new timezone, Juliet, that was 1440 (24 days) in the future. While these changes worked for messages viewed inside the Message Browser and for messages delivered by the MDP, the other locations on the WHIP where times are displayed showed erroneous results. This includes the current game time in the WHIP window bar, any times in a Sitrep window, and any times on the IMT panels. A consistent and reliable Unit of Measure adjustment for both redefining Zulu or adding multiple days to a time is desired. | ||||
| C4I | Additional Data For TACELINT Messages When an object of interest exists for a TACELINT message we can provide the object name and the country code in the MAROP, GNDOP, and AIROP records. What we don't currently provide is the Subject Type and Subject ID fields since we don't hold data for those fields within the JTLS database. However, we do have the 2525B Symbol ID Code available for most objects, and since a specific ID Code should always map to a specific Subject Type and a specific Subject ID we could use the Symbol ID Code to fill these fields. This would require a lookup table be constructed for the various symbols and for an XSL extension function to be written in both Java and C to take a Symbol ID Code and return the various values that we could associate with it. This is not limited to just TACELINT messages, but could also be used to better fill out NATO OWNSITREP and NATO ENSITREP messages. | ||||
| WHIP | Color Coded WHIP Login Screen The ICP allows the Tech Controller to set the background color of the WHIP menu bar. This same color is also used on most scenario tools, such as the WHIP Notification Tool, Interface Configuration Program, and Web Services Manager to denote the scenario for which the tool is being used. The color does not, but should, also be visible on the WHIP Login window to help identify the specific scenario that is being logged into. | ||||
| Model | Air Mission TST Detections A method to get detections of high value enemy objects for Time Sensitive Targeting is desired. HRUS already have an EEI list for which they will break radio silence to report any detected object on that list. The same mechanism of quick and timely reporting of detections by air missions is needed. | ||||
| Model | Supply Run Control The Controller should have a method to move, damage, and destroy convoys. | ||||
| Model | Disseminating Missed Detections A unit was told to attack an enemy unit based on old intelligence. Even when right on top of the location of the old intelligence the operator did not understand why the enemy unit was not being decremented. Some way to note, disseminate, and filter detections based on age and known bad locations is required. | ||||
| Model | Change HRU Strength A method to quickly and magically change the strength of an HRU, similiar to the Unit Change Strength order, is desired. | ||||
| Model | Magic Move a Unit Anywhere Magic Move does not permit a unit to be placed too close to an enemy unit. This seems like an obsolete requirement, and being able to magic a unit anywhere they are needed on the game board is a requirement. | ||||
| C4I | OTH-Gold UDP Conectivity NIRIS can accept an OTH-Gold feed via UDP, but there is no way to setup an OTH-JOI to use UDP. | ||||
| Model | Unit Resting Control A method to determine and modify the status of a restring unit is required. | ||||
| Model | AAR Base Expenditures Report Required A new After Action Review (AAR) report that shows weapon and fuel expenditures at individual bases is required for logistics tracking in exercises. This report would be placed under the Logistics AAR submenu and allow an airbase/FARP/carrier to be specified (with start & end times) to display the beginning available, ending available, expenditures (usage), and any controller adds/removals for each weapon type and fuel type. Note that weapons & fuel loaded on aircraft are considered available until actually expended. | ||||
| Model | Improve Manage Load Assignment Add an option to the MANAGE LOAD ASSIGNMENT order panel to set a load assignment for both day and night at the same time. Currently it requires 2 separate orders. Submitted from the GRAM@# exercise log. | ||||
| Tools | Tool For Editing Orders in a Checkpoint In the event of a model crash, it is sometimes useful for Tech Control to remove or change orders in a checkpoint (ci1 file) and then restart/push from a previous checkpoint. It would be nice to view and edit the ci1 file using a tool which looks more like a spreadsheet - where the order type is a name instead of an integer. The orders can already be viewed in the TechTool. This proposal suggests an editing capability be added to the TechTool to allow for more efficient identification and removal of bad orders. | ||||
| Model | Represent Anti-Tank Barrier Targets A new type of target is required in JTLS-GO that when fully capable impedes traffic and when destroyed makes traffic flow better. A good example of such a target is an emplaced anti-tank barrier. The barrier needs to stop traffic on roads and maybe as well as off-road movement. | ||||
| Model | Better Model Volcano Minelaying System Taiwan has just purchased the VOLCANO Truck used to Lay and Clear minefields. I spent over two hours explaining how minefield laying and minefield clearing worked. We went through the repository and it has the VOLCANO exactly as I would set it up: -->Its own Combat System -->Its own Targetable Weapon -->Its own Supply Category -->Its own HUP to send out this specific truck to either lay or clear mines. The only missing piece of the puzzle is that this super-duper mining machine does not change the lay and clear time that a normal engineering unit uses. | ||||
| C4I | LC2IS Negative Filter Capability It could be helpful, if we can setup 'negative' filters, to exclude part of ORBAT from the report. Typically, under main Headquarters, (HQ) we have a few Brigades or Divisions, and then a number of other units, which are coalition partner Divisions or Theatre Troops, directly under the main HQ. For these extra units, there is no need to report then under the main HQ. This request is to be able to exclude a complete 'leg' of the Order of Battle (ORBAT) in which a unit with all of its subordinates are not reported as part of the hierarchy structure to LC2IS. | ||||
| WHIP | RIC Code Visibility Message Browser Update (Reports) - If RIC codes exist, they should be added to all LOG reports. Ensure that messages look good if the RIC codes do not exist since they are strictly a NATO concept. In addition, RIC codes should be displayed also for all aircrafts and targets. | ||||
| C4I | Easy Visualization Of Unit ROE Desire to have symbols/colors on unit icons to indicate ROE status for the specific unit. Developer Note: The unit symbol is already overloaded. R&A’s suggestion is that this information be placed on the Unit Info IMT Screen. Basically, place an indicator whether the unit has any current ROEs against any side for Air-to-Air, Surface-to-Air, and Surface, which included Air-to-Surface, ROEs. | ||||
| Model | Provide IMT Information On Being Jammed A user has little to no visibility of the fact that they are being jammed. It would help to have this information displayed on the WHIP IMT screen. Want to know if a unit is being: --> Radar Jammers --> Communications Jammed --> Subjected to PSYOP broadcasts | ||||
| Tools | Mean Game Speed on Dashboard Client wishes to see the average game speed over a specified period of time. Allow tech control to specify start and end times for the calculation. The average speed will show on the dashboard page. | ||||
| Model | Improve No Suitable Weapon Message An OAS mission was told to attack an enemy unit. The mission flew to the attack location, sent a 'No Suitable Weapon' found message, and turned around to go home. The message contains no information of use to 'debug' and figure out why no suitable weapons could be found. The message should list exactly why each weapon was rejected. Was it range, PH/PK, Weapon Guidance restrictions, ROE, etc. | ||||
| Database | Create Network Unique Node Names A large node network was created, verified, and corrected within a user's scenario. The desire was to migrate this same road network to numerous other scenarios. The migration tool did not work to accomplish this fact, because the node names created by the DDS are generic in nature. The road network to be migrated had nodes names such as Node1, Node2, etc. Those generic node names also existed in destination scenario but within different networks. When migrated, the nodes and their location were not moved over because the node already existed in the destination. The end result was that one road network was intertwined with a different and independent network in the destination. Road network nodes and arc should not be named generically but should be given names by the DDS to reflect the network to which they belong. | ||||
| Model | Allow User To Select Truck Type For Supply Run Need an option on the Directed Resupply Order to use a specific type of truck. For example, we cannot currently send an ambulance to pick up WIA or KIA because any pickup truck can move those supply categories, but it is more appropriate to use an ambulance unless nothing is available. | ||||
| Model | Add Unit Prepare To Move Time A Tactical Unit Prototype should be given a new database parameter called PREPARE TO MOVE TIME. Once the unit is given a move order, it must wait this amount of time before it can start to move. Obviously, it should start this preparation at the correct time if the user gives a start time in the future. In other words, if you are supposed to move a 1200 and it takes 30 minutes to prepare to move - you should start the preparation at 1130. |