N121-105 TITLE: Lines of Operations Automated Decision Support System

TECHNOLOGY AREAS: Information Systems

ACQUISITION PROGRAM: PEO C4I/PMW150

RESTRICTION ON PERFORMANCE BY FOREIGN CITIZENS (i.e., those holding non-U.S. Passports): This topic is "ITAR Restricted". The information and materials provided pursuant to or resulting from this topic are restricted under the International Traffic in Arms Regulations (ITAR), 22 CFR Parts 120 - 130, which control the export of defense-related material and services, including the export of sensitive technical data. Foreign Citizens may perform work under an award resulting from this topic only if they hold the "Permanent Resident Card", or are designated as "Protected Individuals" as defined by 8 U.S.C. 1324b(a)(3). If a proposal for this topic contains participation by a foreign citizen who is not in one of the above two categories, the proposal will be rejected.

OBJECTIVE: Develop a Lines of Operations Automated Decision Support System to evaluate Lines of Operations identifying deviations from planned Lines of Operations (to cue re-planning), formulate branch plan and sequel recommendations, and feedback plan changes to the master operational plan repository.

DESCRIPTION: The Operational Planning Processes of NWP 5-01 (Navy Planning) results in a selected Course of Action composed of a set of logical Lines of Operations. As defined by Joint Publication 3-0 (Joint Operations), Lines of Operations are logical lines that connect actions on nodes and/or decisive points related in time and purpose with objectives. Lines of Operations developed in the planning phase are based on a set of assumptions about the expected execution phase operational situation. The dynamic nature of warfare nearly guarantees that the actual operational situation will deviate from the assumed operational situation utilized in planning. Resulting deviations necessitate branch plans and sequel actions to accommodate emergent operational events. Human C2 operators regularly spend more time heads-down in their C2 systems assessing incoming situational awareness data, leaving them little time to engage in the important task of evaluating the operational situation with respect to the selected Course of Action and stated operational goals/objectives. Evaluation is critical, as identification of Lines of Operations deviations precedes vital branch planning and sequel action activities. What is needed is an automated system that evaluates incoming situational awareness data and has the capability to alert human C2 operators when deviations from planned Lines of Operations are detected. Furthermore, the automated system should provide initial branching plan and sequel action recommendations. This enables the human C2 operator to shift focus from building the C2 picture to making C2 decisions!

PHASE I: Assess the feasibility of developing a Lines of Operations Automated Decision Support System. Determine if a Lines of Operations evaluation data model can be developed such that incoming C2 data can be aggregated and analyzed in a manner that enables system understanding of Line of Operations progress and deviation. Determine what kinds of operational re-planning could be conducted by such a system when deviations from current Lines of Operations are detected. Define a high-level architecture for the system and provide a roadmap for development of Phase II prototype of the system.

PHASE II: Develop a prototype Lines of Operations Automated Decision Support System. Demonstrate that the prototype is able to aggregate and analyze incoming C2 data and provide C2 operator with Lines of Operations progress updates and deviation alerts. Demonstrate how the system would assist in operational re-planning when deviations from planned Lines of Operations are identified. Determine what additional capabilities are required to provide a fully developed Lines of Operations Automated Decision Support System for the fleet.

PHASE III: Work with the Navy C2 Program of Record sponsor � PMW-150 GCCS-M Program Office - to expand prototype and prepare for transition of the Lines of Operations Automated Decision Support System into the Navy C2 architecture for eventual fielding at ashore and afloat locations. Analyze and address Information Assurance Certification & Accreditation requirements. Demonstrate the Line of Operations Automated Decision Support System in a Sea Trial experiment and evaluate for military utility. The experiment shall be deployed on a US Navy Secret network, with at least one ashore instance, one command ship, and two or more subordinate afloat units.

PRIVATE SECTOR COMMERCIAL POTENTIAL/DUAL-USE APPLICATIONS: A successful implementation of a Lines of Operations Automated Decision Support System should yield a technology foundation that can be similarly applied to other distributed enterprises. Navy processes are unique only in their application domain. The technology should be adaptable to corporate environments, other Government agencies, or any other organization that implements operational plans. The technology and know-how developed by the provider will support a private sector business model if desired.

REFERENCES:
1. Willard, Robert F. Rediscover the Art of Command and Control, Proceedings of the U.S. Naval Institute, October 2002

2. Naval Warfare Publication NWP 5-01 Navy Planning, Office of the Chief of Naval Operations, January 2007

3. Joint Publication 3-0 Joint Operations, Joint Chiefs of Staff, 17 September 2006 Change 2 (22 March 2010)

4. On Lines of Operations : A Framework for Campaign Design Coxwell, Charles W. 01 November 1995

KEYWORDS: Lines of Operation; OLW; Command and Control; C2; Planning; Decision

** TOPIC AUTHOR (TPOC) **

DoD Notice:   Between November 9 and December 11, 2011, you may talk directly with the Topic Authors 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 December 12, 2011, 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 (12.1 Q&A) during the solicitation period for questions and answers, and other significant information, relevant to the SBIR 12.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.