Tripwires for PEO C4I Systems
Navy SBIR 2013.2 - Topic N132-139
SPAWAR - Ms. Elizabeth Altmann - [email protected]
Opens: May 24, 2013 - Closes: June 26, 2013

N132-139 TITLE: Tripwires for PEO C4I Systems

TECHNOLOGY AREAS: Information Systems, Sensors, Battlespace

ACQUISITION PROGRAM: Distributed Common Ground System-Navy (DCGS-N) ACAT IAM

OBJECTIVE: Develop a software solution for monitoring and determining the operational condition and effectiveness of PMW 120 fielded systems afloat.

DESCRIPTION: PMW 120 desires the capability to monitor and determine the operational condition and effectiveness of PMW 120 fielded systems afloat. Some of the knowledge desired includes whether PMW-120 systems that are installed on Navy ships are operating correctly as designed and tested, have network connectivity and sufficient bandwidth, system hardware is functioning properly, operators are suitably trained and data is being delivered and utilized effectively and correctly. The developed software solution should be capable of being monitored from a shore location and able to determine the above knowledge without additional instrumentation being installed, and would function as a tripwire to alert the program office before the system degrades to the point of a Casualty Report (CASREP) or significant warfighter dissatisfaction. The solution should also encompass a maintenance analytics solution that will provide real time visibility into system and network component status, predicted downtime/failure rates, as well as recommended actions. Appropriate metrics for system effectiveness, training, network connectivity and other areas will have to be established and methods for remotely determining their values will have to be developed.

The solution will provide PMW 120 with a state of the art measurable and predictive risk based asset management solution that will enable the program office to drive down lifecycle and maintenance costs and improve system operational availability and effectiveness. Ideally, the solution will leverage predictive maintenance tools already being developed by the Navy. In addition, the solution will provide the capability to model system/equipment/LRU failure modes, which would allow continuous estimation of current and predicted equipment/electronics reliability. Based on projected reliability impacts to mission readiness, it would ensure achieving maximum mission reliability with minimum down time. Analysis and work-flow automation would reduce the manning required at the In-Service Engineering Activity shore node. The solution should provide the capability to store maintenance and parts failure history, which allows periodic computation of MTBF, MTTR, at the LRU failure mode level. This includes external factors, such as operator error or ambient conditions. A "one size fits all" solution is not required, but the level of tailoring for any system should be kept to a minimum.

PHASE I: Phase I will result in a design concept for providing a tripwire to predict DCGS-N and JTT system failures and performance issues without instrumenting the systems currently deployed.

Required Phase I deliverables will include:
- Design concept
- Block diagram of proposed solution
- Proposed metrics and measurement methodologies identified
- Proposed schedule for Phase II
- Cost estimate for Phase II
- Phase I Final Report

PHASE II: Based on Phase I efforts and any redirection from the program office, Phase II will develop, demonstrate and validate the solution. A working solution linked to a limited number of fielded systems will be delivered.

Required Phase II deliverables will include:
- Design architecture, algorithms and data analytics
- Test plan
- Software executables and source code
- Demonstration of solution effectiveness and relevance
- Phase II Final report

Phase II will probably require access to classified data for modeling and testing of developed algorithms.

PHASE III: Phase III will consist of transitioning the solution to one of the three programs of record by expanding the type of systems monitored as well as the number of systems concurrently scrutinized. Source code, will be provided in a format compatible with current Navy repositories such as forge.mil.

PRIVATE SECTOR COMMERCIAL POTENTIAL/DUAL-USE APPLICATIONS: The solution developed under this topic has potential application to commercial entities seeking to reduce their equipment downtime without instrumentation costs.

REFERENCES:
1. OPNAV INSTRUCTION 3000.12A OPERATIONAL AVAILABILITY OF EQUIPMENTS AND WEAPONS SYSTEMS
http://doni.daps.dla.mil/directives/03000%20naval%20operations%20and%20readiness/03-00%20general%20operations%20and%20readiness%20support/3000.12a.pdf

2. Reliability Information Analysis Center: http://theriac.org/

3. MACSEA Improving Navy Ship Reliability
http://www.automation.com/resources-tools/application-stories/machine-monitoring-control/macsea-improving-navy-ship-reliability

KEYWORDS: Availability; reliability; afloat systems; tripwires; analysis; DCGS-N; SSEE Inc F; NITES Next

** TOPIC AUTHOR (TPOC) **
DoD Notice:  
Between April 24 through May 24, 2013, you may talk directly with the Topic Authors (TPOC) 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 24, 2013, 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 (13.2 Q&A) during the solicitation period for questions and answers, and other significant information, relevant to the SBIR 13.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.