Transportation Asset Forecasting Using Joint Databases

RFI: Transportation Asset Forecasting Using Joint Databases

PROBLEM STATEMENT:

The Army lacks a coordinated approach to control the movement of transportation assets between multiple DoD organizations. This comes from the inability to access and connect with other database systems across the DOD.

INTRODUCTION:

The Army Contracting Command Research Triangle Park Contracting Office is issuing a sources-sought synopsis as a means of conducting market research to identify parties having an interest in and the resources to support the requirement for research in Transportation Asset Forecasting Using Joint Databases.

Defense Transportation Regulation, Appendix I, dated 3 March 2023, states, "The use of automated systems to support mobility operations for force projection is essential to maintaining data management and inputs into and interfaces between automated systems." Additionally, Chapter 14 of the NATO Logistics Handbook, dated October 1997, states, "Movement and transportation planning to support military operations should be carried out and coordinated on a combined service and joint military/civil basis encompassing all modes of transport. Separate planning for maritime, land, and air components of force packages should be avoided. NATO civil transportation experts are a valuable asset and should be included in the development of NATO contingency plans."

Across the DOD, there are a myriad of tools employed for cargo movement, but the lack of integration poses a significant challenge. Most transportation movement planning is conducted on unclassified/Controlled Unclassified Information (CUI) systems. Depending on the contingency operation, portions must be planned and executed at the secret level. Depending on the theater, you may also have to use paper-based products. Each service has individualized tools to prepare for personnel and cargo movements. The Army must access an Air Force Reserve system for air movements worldwide. The Air Mobility Command assets are visible through the Single Mobility System (SMS). This web-based computer system provides visibility of air, sea, and land transportation assets and aggregated reporting of cargo and passenger movements. However, SMS does not provide visibility of Marine, Navy, or AFSOC air assets.

For strategic sealift, the Army's Surface Deployment and Distribution Command (SDDC) maintains separate software for scheduling commercial sealift/Industrial Base Information System (IBIS) through the Export Traffic Release Request (ETRR) process. Military Sealift Command owns the process of scheduling voyages and time charters. The Army tracks cargo movement using Radio Frequency Identification (RFID) tags, which are monitored on the Radio Frequency In-Transit Visibility RADIO (RF-ITV) network. Because RFIDs emit a signal, they are easily tracked using Electronic Warfare equipment and are readily visible across the commercial market space. Units also must utilize GCSS to track cargo.

Typically, these tools do not communicate with each other, forcing units to attend various working groups to advocate for their requirements. This highlights the need for a more streamlined process and the urgency of a more integrated system.

RESPONSE INSTRUCTIONS:

1. Your response should have a cover page with your company information, including: Company Name, Address, Primary Point of Contact with a phone number and email address.
2. Please limit your response to 750 words per question.
3. Please provide the response to these questions in a single PDF file.
4. You may answer all or only a portion of the questions offered for consideration.
5. Please email responses to TMBF@aal.army no later than 11:59PM ET, August 15th, 2024.

QUESTIONS FOR CONSIDERATION:

1. What are some existing software solutions that can connect separate transportation databases?
2. What are some approaches to create visual dashboards and a user interface that can track and schedule movement of transportation assets?
3. How would you format a digital dashboard and user interface to support scheduling and tracking of transportation assets?
4. What DOD databases have you worked with in the past?
5. Do you have experience linking DOD transportation databases?

WORKS CITED:

Defense Transportation Regulation Part III Mobility Appendix 1 [https://www.ustranscom.mil/dtr/part-iii/dtr_part_iii_app_i.pdf]

NATO Logistics Handbook October 1997 Chapter 14: Movement and transportation Movement and Transportation Policies [https://www.nato.int/docu/logi-en/1997/lo-1404.htm]

USTRANSCOM Reference Data Management Glossary [https://www.ustranscom.mil/cmd/associated/dteb/files/refdata/V_AIS.htm]

APPENDIX D EXPORT TRAFFIC RELEASE REQUEST (ETRR) PROCEDURES [https://www.ustranscom.mil/dtr/part-ii/dtr_part_ii_app_d.pdf]