SITIS Archives - Topic Details
Program:  SBIR
Topic Num:  A11-129 (Army)
Title:  Methodologies and Algorithms for Ground Soldier Load and Route Selection Decision Applications
Research & Technical Areas:  Information Systems, Ground/Sea Vehicles, Human Systems

Acquisition Program:  
  Objective:  To research, develop, and demonstrate tools that could support tactical small unit load planning and route selection.
  Description:  The Army’s dismounted tactical small units (Infantry Company and below) could benefit from decision support applications that can support mission planning and execution of their operational tasks. The selection of equipment to take on a mission and the selection of routes can be quite complex and based upon numerous factors, to include the METT-TC elements (mission, enemy, terrain and weather, troops and support available, time available and civil considerations), work-rest cycles, resupply, contingency planning and terrain analysis. The term OACOK is often used to support terrain analysis, with the major elements including: Observation and Fields of Fire, Avenues of Approach, Cover and Concealment, Obstacles, and Key or Decisive Terrain. Algorithms can be developed to support execution of these interdependent tasks. It would also be desirable that the route and load planning tools be compatible with and support the military planning process, e.g. generation of Operation Order. This effort would research, develop, and demonstrate methodologies and algorithms that enhance load planning, route selection and in making changes during mission execution. Potential approaches should address the data, methodologies, algorithms, and validation audit trail. Proposals should identify how the proposed research will advance the current state of the art. The products should support development or improving battlefield and training decision support applications focused on Soldier load issues. The Tactical Small Unit (TSU) leader is responsible for making the final decision and we are trying to provide actionable information (e.g. timely, accurate or more complete) in which to do so. Elements that could be important to execution of this work include: identifying the TSU leader decisions that are to be supported, understanding user needs; identifying the factors that are important; identifying and developing methods of obtaining the data needed; developing user interfaces that meet user needs; developing methodologies and computer algorithms; providing the desired output in a useful form; and addressing software and platform integration issues. Since validation is a critical issue, the algorithms and decision aid application must accurately represent the intended real world phenomena from the perspective of its intended use. At this point, we are assuming that the TSU will have: intermittent network connectivity, some resident computational capabilities, terrain databases, and some form of display available to them. At this time, it is not clear if the products of this effort would be integrated with other existing battle command systems, become a module in an integrated application or be utilized as a stand-alone application.

  PHASE I: Phase I will provide a proposed concept for the generation of methodologies and algorithms that would be needed and could be incorporated into an application to support load planning and route selection at the TSU level. The focus should be on the METT-TC and/or OACOK elements. This will include identifying a number of specific operationally relevant decisions and actions that could be at least partially supported by a decision support application. The proposal should also show how the proposed methodologies and algorithms would provide the TSU leaders with useful information to support his decision making. As a result, it is important that verification and validation planning be initiated at this stage. It is desirable that algorithms be computationally efficient within a potential battlefield and training decision support aid. Any data needs and assumptions required by the concept to be compatible with a TSU decision aid should be clearly outlined and explained. Phase I should also include identification and discussion of additional operationally relevant algorithms that could support equipment and route selection at the TSU level. Phase I will perform a proof of concept that describes how one proposed concept may be utilized within a ground Soldier battlefield decision support aid. Metrics in phase I will include: • The usefulness of the methodology or algorithm to support load planning or route selection across a range of situations, • the applicability and utility of an initial methodology and algorithm to be implemented within a decision application, • the degree that it represents the important elements of the real world (valid), • documentation and ability to demonstrate the methodology or algorithm, • modularity and ability to be incorporated into a route selection cost function that incorporates other factors, • and applicability of the selected approach to the development of additional algorithms.
  PHASE II: Phase II will include research, design and implementation of multiple methodologies and algorithms necessary in accordance with the topic objective. Knowledge elicitation may need to be conducted with tactical small unit SME’s to ensure that critical real world factors (i.e. METT-TC or OACOK) are identified and included in such a way as to support the development of each methodology, to include the necessary data elements and data structures. In Phase II, validation and verification will have to be addressed. The plan may also include how specific applications could be developed. A set of use cases that describe relevant military operations or missions will be provided to guide research, methodology development and support testing and experimentation. The work effort will lead to demonstration of the products developed in phase II within an appropriate environment. Other tasks include documenting and delivering a report including all user needs assessments, methodologies, algorithms, and any data structures or software products necessary to support transition of the work to DoD material developers. The phase II report should also demonstrate and document how algorithms may be transitioned to support implementation into battlefield and training decision support applications. Metrics for this effort will include the number of methodologies and algorithms developed, the degree to which they represent the important elements of the real world, their potential utility within the decision application, documentation and their ability to be demonstrated. Other considerations include the degree to which the algorithms are computationally efficient, can be modified if additional factors need to be included, and can be implemented within appropriate decision applications of the governments’ choosing. Because we do not yet know if the products of this effort will lead to a stand-alone system or be integrated within another system, compatibility is an important issue. As a result, the architecture, modularity and interfaces are all important.

  PHASE III: The developed methodologies and associated implementation have commercial applications of these simulation products to proposed DoD solutions whose goal is to provide Soldier’s applications that will support enhanced Soldier situational awareness and improved decision-making. Also, there is potential application to future automated or semi-automated ground Soldier battlefield systems, such as an Unmanned Ground Vehicles. Non military applications could relate to route selection where there are common elements with tactical small unit operations.

  References:  . FM 3-21.8, The Infantry Rifle Platoon and Squad, 28 March 2007 2. Department of Defense Instruction number 5000.61, Subject: DoD Modeling and Simulation (M&S) Verification, Validation, and Accreditation (VV&A), 9 December 2009 3. Department of the Army Pamphlet 5-11, Verification, Validation, and Accreditation of Army Models and Simulations, 30 September 1999 4. FM 3-21.10, The Infantry Rifle Company, 27 July 2006 5. FM 21-18 Foot Marches, dated 1 June 1990

Keywords:  Decision Support Application, Small Combat Unit, Ground Soldier, Soldier Load, Path Planning, Route Selection, Training

Questions and Answers:
Q: Is there any specific terrain database that this project should use or should the proposal suggest one?
A: There is no specific terrain database. The information needs to be georectifed and accepts elevation data. The type of elevation data is also irrelevant. The proposal can assume that this information is available from sources at higher levels of command. (e.g. dted from battalion s-2, imagery from batallion s-2, etc.)
Q: The topic lists six shortcomings that need to be addressed. Must the proposal address all of them?
A: This does not necessarily have to address all six shortcomings. Novel ways of improving the shortcomings incrementaly could possibly be considered.
Q: Is it desired that the proposal focus mainly on algorithmic use of exiting terrain products (e.g, DTED and imagery) rather than study what might be done with new terrain data types not yet common in the field?
A: Given our focus on decision aid development and resulting transition, it would desirable to develop algorithms to the greatest extent using existing terrain sources. However, it is not a requirement to limit your work to terrain products that are common in the field. It is perfectly acceptable during this process to highlight limitations in the algorithms or methods that resulted from the terrain limitations and to highlight the enhancements that would need to be to the terrain representation to more fully address the problem.

I hope this covers it.

Record: of