8147 record(s) found.
Improvement List
| Info | Area | Subarea | Description | |||
|---|---|---|---|---|---|---|
| Tools | Allow Variable Number of Ad-Hoc Web Login Columns Three columns have been added to the Web Login Page of the Apache server to allow scenario specific requirements. These cells are used by creating server side HTML files named | ||||
| Tools | Copying DDS Reports and Maintaining Formatting Recently there was a requirement to get a DDS report to a Response Cell (RC). At the time the mail system was not functioning properly. Other ways existed to make a file available if the data within the report could be captured. A copy and paste of the data from the TRIPP Report Browser did not copy the HTML formatting. A copy and paste into a spreadsheet placed everything into the first column losing the row and column concept. A need exists to be able to capture the contents of the Report Browser and copy it into other tools while retaining the formatting. This could be as simple as a "show source" button that exists on many web browsers allowing the HTML markup to be captured with a copy and paste. | ||||
| WHIP | Site Specific CADRG Files A set of CADRG maps is delivered with a JTLS release in the ~/CADRG directory. This is the standard directory on a Linux system that the WHIP/DDS/JOBE look for CADRG maps. When updating a system it is important to verify that the CADRG directory does not contain site-specific maps before replacing the directory. In order to avoid this issue the WHIP/DDS/JOBE should support a ~/game/data_site/CADRG directory that may contain additional CADRG maps, allowing the end user to place their site-specific data outside the standard release directory structure. | ||||
| C4I | Enhanced Reformat Spreadsheet Program This is probably not the first time I've submitted something like this, but I have some new ideas here. The Reformat Spreadsheet Program (RSP) requires a Comma Separated Value (CVS) file for input that contains a single type of order. The user is then required to map each column of the file to a field from the order using the order keywords. This is done as a command line interface. The task of using the RSP could be simplified with a Graphical User Interface (GUI) driven program. The program should be capable of reading an Excel spreadsheet directly, displaying multiple sheets of data in different tabs, allow the assignment of an order or utility to each tab, allow the assignment of a field to each column within the tab, and output either a Read Order File (ROF), a group of orders for a specific WHIP, or a JTLS Order Spreadsheet for a WHIP. | ||||
| Tools | Hiding Password Fields The user account tab for the DDS Configuration Program (DCP) contains user names and passwords. The passwords are printed with stars, i.e. ****, by default but an icon exists next to each one that the Tech Controller can press to see the actual password. This capability should be extended to other Tech Control tools where a password exists such as the ICP, the Javamenu for DDS and AAR access, etc. | ||||
| C4I | Make JTOI A Service In JTLS 4.1, all of the programs that link to various C4I systems were supposed to become services. The first attempt at making the JTLS Transaction Operational Interface (JTOI) to real-world air planning systems did not meet end user requirements; therefore, the service version of the JTOI project was canceled. The desire of this ECP is to provide a more robust design for moving the JTOI to the service environment. | ||||
| JMRM | Improve NWARS Available Data It was veryu difficult for NWARS to interpret the JTLS provided data concerning active emitters. There simply was not enough time to alter the data structures. A better data model based on NWARS needs to help the ease with which NWARS can link to JTLS. | ||||
| Tools | Allow Translation Of Army Missile Orders In ATO JTLS does not have the concept of processing ARMY land based SSM missile shots scheduled in the ATO | ||||
| C4I | Pass Squadrons To MUSE During Game Execution We need to think of a way to pass new units to MUSE. | ||||
| C4I | Log JOI Filter Changes Provide log entries for individual unit filter changes. Ideally all configuration changes would be placed in this file as well. This would have proven useful during the recent exercise. | ||||
| C4I | WHIP and JOI Interface Name Improvement Consider sending Track IDs to the service when modifying filters, instead of using the JTLS Short name. This results is less traffic and no possibilities of the IDs containing spaces or unexpected characters. This also matches up with the JOI console command implementation. | ||||
| WHIP | Full Screen Message Browser And IMT Need the ability to full screen the message browser and IMT would be nice. You currently can with the ATOV and it is helpful when dealing with lots of info. | ||||
| Model | Air | Easy Flush Airbase The exercise audience gave an order to flush all aircraft from an airbase. There was no easy way to do this in JTLS. We should implement an order to easily accomplish this task. | |||
| JMRM | NWARS Reporting Damage Instead Of Maintenance In JTLS three situations can place combat systems into maintenance: 1. Normal breakdown because of use 2. Specific disease or failure breakdowns 3. Combat There is no easy way for the ELS and thus NWARS to know the difference. The result is that NWARS always reported the systems as damaged even though there was no combat prior to the generated NWARS report. The link between JTLS and NWARS needs to be improved to solve this problem. | ||||
| C4I | Allow TACELINT Message Filtering Currently the Tactical Electronic Intelligence (TACELINT) messages are generated by the TACELINT Message Server (tems) for every emitter that is currently turned on for which there exists Electronic Notation (ELNOT data. User would like to filter messages based on data such as country code of the emitter or relationship of the emitter to the C4I side. | ||||
| WHIP | Setting WHIP Heap Size For large databases it is necessary to increase the Heap size available to the WHIPs. This needs Technical Control to hand-edit a file. The process of increasing a WHIP's Heap size needs to be much easier to do and it needs to be assignable by WHIP. A WHIP that is executing on a small or old machine may not be able to handle a large Heap size. Setting Heap Side should be a part of the Interface Control Program. | ||||
| Tools | RSP Create WHIP Spreadsheets The Reformat Spreadsheet Program (RSP) takes a spreadsheet of information and creates legal orders that can be submitted to JTLS. It would be nice if this program also had the capability to create a spreadsheet set of orders that coujld be viewed and managed from within the WHIP | ||||
| C4I | Properly Represent Japanese Link-16 Capabiltiy Japan does not have the ability to report self-reporting aircraft using Link-16 2.3 messages. They need to report using 3.3 messages. The full Japanese Link-16 reporting capability should be properly represented within JTLS. | ||||
| Model | Air | Allow Aircraft To Turn Off Mode 2 and Mode 3 Enemy aircraft during combat operations would not use their Mode 2 or Mode 3 transponders. The user should be able to turn these on and off in the same manner that sensors can be turned on or off. | |||
| WHIP | Submarine Battery Warning Message Is it possible and worth wile to add a ALERT message to the WHIP notifing a WHIP operator when a submarine battery has reached a minimal operating level or capability such as 10% remaining battery life. | ||||
| Database | Integrate Error and Warning Text into SVPR Enter a description of the proposal or issue here.Similar to accessing the DRM pages from the OPMs, I would like to be able to access the DDS User Guide Error and Warning text directly from the SVPR. Not all errors and warnings make sense at face value, this requires the users to open the DDS User Guide and find the text for the error. This is cumbersome especially on small monitors and laptops. Some user are also less likely to care and update data incorrectly just to clear a particular problem. If the text were readily available there would be a better chance of problems being corrected properly. Display of the text could be one of several ways. 1. Include a auto fix option to display the DDS User Guide Page 2. Have the text display using a process similar to context sensitive menus 3. Have the text automatically appear in the bottom of the right hand window when a error or warning is selected. This feature could be turned on or off similar to the wrap function toggles currently in the SVPR. | ||||
| Database | Add SVPR NULL Record Notification The SVPR function contains auto correction options which include the option to display a record from one of the many tables. If the record does not exist the appropriate table is displayed with no records. For a user with little experience this could lead to the user believing there was an error in the retrieval. I recommend adding a pop up warning window to notify the user when no records were selected. This user should be able to turn the pop up window off once they are familiar with the problem similar to the SVPR line wrap fundctions. | ||||
| WHIP | Allow external applications to draw on WHIP. Provide a method for external applications like the TechTool to be able to draw on the WHIP. | ||||
| Tools | Perform Verification on Order Times The OMA does not reject ATO Mission Package orders with a time in the past. These are rejected by the model, but if the operator misses the message the next step in submitting an ATO is to send the package missions. These would then be rejected since the package does not exist. If the OMA performed verification on times the error would be caught earlier in the sequence of events. | ||||
| WHIP | Provide CAS Support Information There is no way for the WHIP operators to provide information on which air missions respond to a CAS Request. This is a major part of the Response Cell play in both the friendly and sitfor cells. | ||||
| WHIP | Order Groups Within Groups The ATOT produces up to 10 order groups for every ATO that is translated. After 15 days of an exercise this will result in 150 groups within the Order Group Editor. Allowing the capability to put groups within groups would enable to air operator to better manage this large number of orders. | ||||
| WHIP | WHIP Find On Map for Multiple Objects The DDS tables allow an operator to select multiple rows and perform a Find on Map for object or locations. This marks every matching object on the map, moving the map frame reference as needed to display each object. This capability is desired but does not exist within the WHIP. | ||||
| Model | Air | Multiple Squadron Airlift/Airdrop The model permits the user to use multiple squadrons in an airlift or airdrop by submitting separate airlift/drop orders. For each airlift/drop order either the order can be sent, or a time estimate for the lift can be requested. The time estimate option will only provide the estimate for the specified order and its assets. It is desirable to be able to obtain an airlift/drop time estimate for a multiple squadron airlift/drop. | |||
| Tools | OVT Order Files Currently the OVT will verify and submit orders directly to the CEP. This provides no method for the operators to view what was submitted or to recall orders. If the OVT had the ability to create actual orders for the player, then the WHIP could perform the verification and submission of orders, and additionally recall orders at a later time. This behavior would mimic the submission of orders from the ATOT. | ||||
| Tools | TechTool Moving Views Currently the TechTool has the ability to move slides and order groups between scenarios, even scenarios on different file systems. A third WHIP created item which would be useful to move is views. | ||||
| Tools | TUP/HUP/SUP Combat System DDS Report. As the size of data repositories grows, the number of TUPs, SUPs, and HUPs will grow making if hard for database builders to find existing prototypes that meet their needs. This report will allow prototypes to be filtered by the number of Combat Systems and/or Supplies they have. | ||||
| C4I | Output TACELINT Using TAB37 Format The desire is to output TACELINT messages using the alternate TAB37 format. | ||||
| Model | Ground | BDA Report Needs Separate HRU Section HRU kills and damage are reported in BDA reports but are listed under the Ground Combat section. It is desired that a separate section that lists the kills by HRU be added to the report. | |||
| Model | Navy | Represent Port Capacity Represent the number of ships that can be in port at any one time. The model does present the number of MHE facilties owned by the port, and only so many ships can be off-loaded at once, but nothing makes these ships line up outside of port waiting for a berthing position. This function is desired. | |||
| Model | Navy | Change Smoke Time Improvement In a recent test, several ships were hit and they started to smoke. The Controller them went in and changed the time that smoke should persist from the 13 hours in standard database to 5 minutes. This change was desired to insure that MUSE and NWARS stopped seeing the smoke. The database parameter was changed, but it had no effect on the ongoing smoking ships. The desire is to have the change in the database parameter also alter any ongoing smoking ships. | |||
| Model | Navy | Formation Enter Port Capability Only indivudual units can be told to enter port. The desire is to create an order when the user can order a formation to enter port. | |||
| C4I | TACELINT Message Sevice Operate As Server Currently the TACELINT Message Service (tems) only operates as a client. It should also have the ability to operate as a server when required, | ||||
| Model | Ground | Contamination Area Weapon Information The desire is to allow the user to filter contamination areas based on the weapon that created the contamination area. Also it would be helpful to know the type of contamination agent, such as nerve, blister, etc. | |||
| Model | Log | Add Targets to Logistic Report If it is possible we would like to see targets in the logistic report. These targets should appear in the Combat System section of the report. It should also appear in the Logistic Roll-up Report. | |||
| WHIP | Order Group Editor Reload Of Orders Currently after using the Tech Tool's Order Group Copy, the Synapse and WHIP need to be brought down and brought back up in order to see the newly copied order groups and their orders in the affected WHIPs. This process will be simplified for the user if there was a manner to invoke a reload of any newly copied orders from in the WHIP, such as a reload button on the Order Group Editor, to avoid the need to restart the Synapse and any WHIPs. | ||||
| Model | Air | Want Summary Mission Report for a Specific Time Period During a major exercise, the senior officer serving as Air Controller requested that the model generated an on-demand summary report for all missions in a specific time period (such as the ATO period, or for a certain range of hours). | |||
| Model | Air | Automatic Mission Report After Important Events At a recent major exercise, the senior officer in charge of the air cell requested that the model provide an automatically generated report every time an air mission experiences an important event (such as dropped weapons, lost an aircraft, reached the rendezvous point). These messages will alert the coordinator to know that certain events occurred as planned. | |||
| Model | Air | Handling Overlapping Sensors On Air Mission When multiple sensors are collecting intelligence information, the model does not want to keep multiple versions of an information update on a given object. When a sensor detects and object, the model determines whether the sensor that detected the object is “better’ than the previous sensor that detected the object. The concept of “better’ is not easy to quantify because there are several characteristics to consider such as: -->The time to report the information -->The classification level of the detection -->The type of report that the sensor will generate. The concept of overlapping sensor detection from the same air mission needs to be looked at in detail and a workable solution to the dilemma needs to be established and implemented. | |||
| Model | Air | Aircraft Orbit Fuel Consumption Savings When an aircraft is orbiting, it does not use fuel at the same rate it uses when flying. This is definitely true for the P3 aircraft in which two of the 4 engines are turned off while the aircraft is on station thus saving fuel and extending the time it can stay on station. This needs too be modeled. | |||
| Model | Air | Aircraft Load Flexibility Cannot change weapon load while a mission is on alert posture. Must cancel the mission and re-submit with the desired weapon load. This creates unnecessary work in an ops-tempo environment. | |||
| Model | Air | Interceptor Speed When In Position An air mission was intercepting at 525 knots (weapons hold). The intercepted mission was flying at 248 knots. When the missions coincided, the intercepting air mission maintained 525 knots. The interceptor should have slowed down to match the intercepted mission’s speed to conserve fuel. | |||
| WHIP | Remove Inactive Formations From WHIP Formation icon should be destroyed after the last ship leaves the formation or is destroyed. | ||||
| WHIP | Method To Know If Message Has Been Read Player requested an option/button to mark all messages as read in the message browser. | ||||
| C4I | DSA For Roads It would be useful to create Directed Search Areas (DSAs) which follow a road, but they should also report with accurate locations of the objects. The proposed road-following DSA would be used for collecting on main supply routes (MSR). | ||||
| Model | Intel | Better Location Information In IIR Messages Location information of detected objects in the generated IIR messages needs to be more accurate and detailed. As a side note, the JTLS-GO design team is hoping that the NWARS project will provide examples of more appropriate IIR messages from which a better inherent IIR generation capability can be built within JTLS-GO. |