|
Real-Time, Bandwidth Optimized Collaboration Mission Planning Infrastructure
Navy SBIR 2009.1 - Topic N091-037 NAVAIR - Mrs. Janet McGovern - [email protected] Opens: December 8, 2008 - Closes: January 14, 2009 N091-037 TITLE: Real-Time, Bandwidth Optimized Collaboration Mission Planning Infrastructure TECHNOLOGY AREAS: Information Systems, Battlespace ACQUISITION PROGRAM: PMA 281, Joint Mission Planning Systems-Maritime (ACAT IV-T) The technology within this topic is restricted under the International Traffic in Arms Regulation (ITAR), which controls the export and import of defense-related material and services. Offerors must disclose any proposed use of foreign nationals, their country of origin, and what tasks each would accomplish in the statement of work in accordance with section 3.5.b.(7) of the solicitation. OBJECTIVE: Develop innovative technologies to allow for real-time, network bandwidth optimized mission planning collaboration between multiple users using the Joint Mission Planning System (JMPS) and JMPS-Expeditionary. DESCRIPTION: Pilots use the JMPS to develop route plans and weapons data load inputs prior to flying each mission. These files can be extensive and many require change prior to each flight. In addition, Force-level JMPS users attempt to optimize the individual aircraft plans into larger groups of assets. The pilots and other users require real-time file transfer with simultaneous joint file manipulation between geographically separated operational units, in order to support increasingly complex and time-critical mission planning processes. JMPS provides support for geographically separated pilots (mission planning users) operating at the individual Combat Unit level, with each user planning a single mission for a specific aircraft. These users are often under the command of different forces and Combatant or Expeditionary Commanders. The capacity to support collaborative mission planning between individual unit users in Joint Force operations, in a real-time, network bandwidth optimized manner is required. Current efforts to perform collaborative planning depend on e-mail, on-line chat, and telephone (voice). These methods are non-real time, limited in the scope of information that can be communicated, and have significant potential for errors due to manual communication methods. In addition to providing real-time file transfer and simultaneous manipulation of the files for nominal mission planning data, there is a need to support the advanced communication required for coordinated operations between operational units (e.g., rendezvous locations, times, etc.). To realize significant reductions in the time required to complete coordinated mission/flight/weapons plans, and to eliminate the potential for errors in manual communication methods, this must be performed machine-to-machine rather than by the off-line, manual methods now used. To provide maximum planning effectiveness, with no data communication errors, in the shortest possible amount of time, interoperable and collaborative mission planning systems are required. Operational benefits of this technology will include decreased time-to-plan, increased sortie rate, more optimal air group performance, and greater warfighter safety. PHASE I: Determine the feasibility of implementing a concept for collaboration among individual users/pilots/mission planners. Specifically address implementing a collaboration technology that is compatible with the data architecture and Service Oriented Architecture in JMPS 1.4. Assess these technologies with respect to human factors and operability in a wartime scenario. PHASE II: Design, develop and demonstrate a prototype collaboration system for JMPS. Develop performance metrics to quantify the improvements observed in group mission planning. Develop several mission planning test scenarios representative of multi-unit, wartime planning and communications, amongst geographically segregated planners. Perform mock mission planning exercises using both manual methods in use today, and the prototype collaborative architecture/software. Evaluate prototype system performance through laboratory analysis of data obtained from experiments or testing. Perform and document a quantitative analysis of the performance improvements in group mission planning using the prototype. PHASE III: Transition and integrate mature technology into a Joint Mission Planning System collaborative mission planning production baseline. PRIVATE SECTOR COMMERCIAL POTENTIAL/DUAL-USE APPLICATIONS: This technology has direct application to Department of Homeland Security and local authorities asset dispatching and control systems where many remotely commanded assets will operate in coordinated teams. REFERENCES: 2. Draft Collaboration Common Capability Requirements Document dated January 16, 2003. 3. Capability Requirements Specification for the Joint Mission Planning System (JMPS) Collaborative Planning (CP) Common Capability (CC) dated 1 June 2004. USAF Materiel Command, Electronic Systems Center (ESC), Mission Planning Program Office (ESC/ACU). 5. C4ISR Interoperability Working Group, DoD � Levels of Information Systems Interoperability � latest edition. http://www.sei.cmu.edu/isis/guide/introduction/lisi.htm KEYWORDS: Communications; Collaboration; Mission Planning; Joint Operations; Interoperability; Information Technology
|