N08-103 TITLE: Autonomic Logistics Tactical Logistics Data Communcation Network

TECHNOLOGY AREAS: Information Systems, Ground/Sea Vehicles, Electronics

ACQUISITION PROGRAM: Embedded Platform Logistics System (EPLS) - ACAT III

OBJECTIVE: This topic is seeks to support two key DoD technology areas, primarily in the Information Systems Technology area supporting development of communications and networking technologies in a mobile tactical environment. In addition the topic supports Ground Vehicles by supporting the development of a real-time situational awareness capability. Specifically, the topic seeks technology to develop and test mobile data communication networks and data management software that will communicate the status of tactical assets in the area of operations and provide in-transit visibility of supporting logistics operations. When tactical assets, such as ground vehicles, are equipped with an embedded sensing and reporting capability they will need to be linked into a communications network that moves timely status information off the platform and to a command platform that can transmit the consolidated data throughout, up and out of theater. The objective is to solve the data reporting problem that exists because of lean communications in the tactical area of operations.

DESCRIPTION: The Autonomic Logistics (AL) Program has the requirement to report logistic information in near real time from each platform/asset within its local unit, up through the area of operations, to the theater and strategic levels beyond. When achieved, this will greatly increase the visibility of actual operational demands and logistic requirements of platforms during operations. With such situational awareness available, the tactical commander now knows how much "fight" is left within his weapons platforms; just as importantly, Logistics planners now readily and accurately know the "sustainment requirements" of in theater units. AL is currently deploying an embedded platform logistic system (EPLS) that will monitor and process individual platform logistic status. This status consists of data elements including: platform health, ammunition and fuel levels, and mobile load information. However, A robust, dynamic, secure communication infrastructure will be required to collect and move this data from the individual platforms. The data will then need to be compiled and rolled up to the command platform to be monitored and transmitted to the theater and strategic levels.

A dynamic, robust, and secure mobile communication network infrastructure will allow the collection and reporting of logistic information between platforms assigned to specific missions. For example the vehicles in a convoy need to be able to transmit individual platform health and status data to a master or command vehicle while on the move with out interfering with tactical operational communications. Another application would support a Light Armored Vehicle (LAV) platoon on a mission where the vehicles are scattered around a specific battle space. Each vehicle should be able to report status and health data back to the command vehicle as they move around the battle space beyond line-of -sight of the command vehicle. A current mesh network design does allow extend range by transmitting through other nodes which demonstrates the advantage of mesh networking. However, we need to develop an affordable data communications system or architecture to support operations in the dynamic or sometimes chaotic tactical environment. The communication network system must be rapidly reconfigurable and allow the acceptance / departure of additional authenticated nodes on the fly. It needs to be able to reliably maintain connection while on the move in all types of terrain including rural and urban areas of operation. Through this innovative research effort we expect to be able to develop a communication architecture that will transmit the data off the platform to establish real-time situational awareness for operational and logistics commanders. The challenge is to reliably collect and consolidate platform health and status data from a number of highly mobile platforms/nodes in a tactical environment. An affordable logistics data network architecture that can support the tactical security, bandwidth, and connectivity requirements without interfering with tactical operational communications has not been developed. In this tactical environment we expect to have platforms/nodes on the move that will drop in and out of connectivity, interference from terrain, man-made obstacles, other communications. The platform data will have to be synced when connectivity is restored without loss of data. The master or command node/platform will need to be able to consolidate the data, populate an onboard Common Operating Picture (COP), and then redirect/transmit the data to a higher level COP via radios or satellite communications. This product will increase the visibility of the tactical level logistic requirements like identifying the support request for repair parts/consumables and tracking of mobile load distribution events from individual systems. The mobile network architecture will support software that includes business rules allowing the network to recognize new nodes on the fly and provide a status of nodes connectivity. This dynamic capability could also be expanded to support Identification Friend or Foe (IFF) between nodes/platforms.

PHASE I: During Phase I we will determine, the scientific and technical approaches for completing the following tasks:
1) Development of a cost effective robust tactical data Communication network capability for transmitting Vehicle health and status in support of Operational and logistics commanders situational awareness.
Network robustness refers to the overall capability and reliability of the network to perform in the anticipated con-ops. Specific concerns include:
1) Dynamically changing topologies resulting from mobile nodes.
2) Scalability with respect to the number of nodes/vehicles in the network and increasing traffic/ network overhead data.
3) Wireless node range and interference with other wireless devices in the ISM bands
4) Meeting Navy/Marine Corps wireless security protocols and requirements
5) Network needs to be "Self Organizing". All nodes shall have routing capability for network traffic. This routing is constantly updated as nodes move about and as nodes join and leave the network. This shall be done automatically as part of the infrastructure and requires no external control.
6) The network must be capable of supporting at a minimum the bandwidth requirements of the EPLS data package. Ideally the bandwidth should be sufficient to support voice and video transmissions.
7) The network architecture must be capable of syncing data from platforms/nodes that was collected when connectivity was lost without loss of data.

PHASE II: Develop proof-of-concept demonstrators of systems to conduct each task separately or simultaneously.

PHASE III: Integrate proof-of-concept demonstrators with existing AL/EPLS systems and demonstrate.

PRIVATE SECTOR COMMERCIAL POTENTIAL/DUAL-USE APPLICATIONS: Commercial applications would include industrial and municipal potential. Affordable robust Communication networks could extend wireless connectivity to areas currently not practical to provide coverage. The Transportation Industry could provide improved monitoring of Fleet vehicles. The Railroad industry could monitor the cars on trains as they drop and add rail cars. Municipalities could network fleet vehicles for more reliable and redundant monitoring and communications in remote locations. Further development of this capability would improve costs and reliability of these systems allowing for consumer use and benefits.

REFERENCES:
1. Initial Capabilities Document for AL

2. AL Critical Design Document (Draft)

3. EPLS Specification

KEYWORDS: Autonomic Logistics, Embedded Platform Logistics System, Net-centric Communications, Situational Awareness. Logistics Data Communication Architecture.

** TOPIC AUTHOR (TPOC) **

DoD Notice:   Between April 21 and May 18, 2008, you may talk directly with the Topic Author(s) to ask technical questions about the topics. Their contact information is listed above. For reasons of competitive fairness, direct communication between proposers and topic authors is not allowed starting May 19, 2008, when DoD begins accepting proposals for this solicitation.

However, proposers may still submit written questions about solicitation topics through the DoD's SBIR/STTR Interactive Topic Information System (SITIS), in which the questioner and respondent remain anonymous and all questions and answers are posted electronically for general viewing until the solicitation closes. All proposers are advised to monitor SITIS (08.2 Q&A) during the solicitation period for questions and answers, and other significant information, relevant to the SBIR 08.1 topic under which they are proposing.

If you have general questions about DoD SBIR program, please contact the DoD SBIR Help Desk at (866) 724-7457 or email weblink.