Hardware Open Systems Technologies (HOST) Conformant Secure Network Server
Navy SBIR 2015.1 - Topic N151-019
NAVAIR - Ms. Donna Moore - [email protected]
Opens: January 15, 2015 - Closes: February 25, 2015 6:00am ET

N151-019 TITLE: Hardware Open Systems Technologies (HOST) Conformant Secure Network Server



The technology within this topic is restricted under the International Traffic in Arms Regulation (ITAR), 22 CFR Parts 120-130, which controls the export and import of defense-related material and services, including export of sensitive technical data, or the Export Administration Regulation (EAR), 15 CFR Parts 730-774, which controls dual use items. Offerors must disclose any proposed use of foreign nationals (FNs), their country(ies) of origin, the type of visa or work permit possessed, and the statement of work (SOW) tasks intended for accomplishment by the FN(s) in accordance with section 5.4.c.(8) of the solicitation. Offerors are advised foreign nationals proposed to perform on this topic may be restricted due to the technical data under US Export Control Laws.

OBJECTIVE: Develop, demonstrate, and validate a secure network server, based on the Hardware Open Systems Technologies (HOST) Standard, that can operate in a real time (or near real time) system while minimizing space, weight, power and cooling (SWaP-C).

DESCRIPTION: Today's military aviation community has many standards to choose from when developing hardware for government use. Two well recognized examples of these standards are VME and OpenVPX. While these standards provide a general basis from which to develop hardware, they contain enough flexibility that two vendors can build to this standard and produce a product whose components are not portable - meaning that a module from one vendor's product cannot be placed in another vendor's product with the expectation of full function. The Navy is currently maturing a standard, called HOST, whose purpose is to reduce the variability in existing standards (such as VME and OpenVPX) such that the portability of components within the computing architecture is enabled.

One common design challenge in open architecture systems is achieving the optimal trade between SWaP-C and latency. The purpose of an open architecture is to generalize hardware module interfaces to ensure that the interface can support hardware components from multiple independent vendors. This generalization may, in some cases, lead to an implementation that is not optimized with respect to latency. In avionics systems that are required to function in real time or near real time, any potential latency generated via an open architecture is a problem. A common way to fix the latency problem is to add additional processing capabilities. However, due to the additional weight and power requirements this solution requires, it is not a viable option for an aircraft implementation.

The Navy requires the development of a secure network server that can implement open architecture (i.e. built to the HOST standard). This device must be able to operate in real time (or near real time) without any latency generated from the open architecture design, and without any increase in SWaP-C requirements. This server must be capable of hosting traditionally developed software as well as software developed in accordance with the Future Airborne Capability Environment (FACE) Technical Standard. The server will be used as a surrogate to demonstrate component portability with an existing government HOST conformant computer, as well as to validate the design meets real time (or near real time) latency standards.

PHASE I: Design and develop a concept for a HOST conformant open architecture secure network server, that can demonstrate module portability with an existing government HOST conformant computer, as well as operate in a real time (or near real time) system while minimizing SWaP-C. Analyze the SWaP-C and latency expectations for this concept and compare with existing network server implementations (to be agreed upon at project start) to verify the HOST conformant design concept exceeds current non-HOST performance specifications.

PHASE II: Based upon the findings from Phase I, build the prototype secure network server and test the device by interfacing and demonstrating modular portability with a Government HOST conformant computer. In addition to demonstrating hardware portability, continue to optimize the critical trade space between SWaP-C and latency for avionics implementation.

PHASE III: Transition the prototype secure network server to a production representative network server that meets commercial and Navy avionics flight worthy requirements.

PRIVATE SECTOR COMMERCIAL POTENTIAL/DUAL-USE APPLICATIONS: This innovation will significantly enhance the capability and flexibility of military and civilian aircraft while enabling additional safety and mission critical systems to be developed, integrated and fielded at a lower cost and reduced developmental cycles. As a system of systems, or distributed application, the HOST Standard will enable the combination of a variety of different system hardware architecture representations.

1. NAVAIR. (2014). Technical Standard for Future Airborne Capability Environment (FACE), Edition 2.1. Retrieved from https://www2.opengroup.org/ogsys/catalog/c145

2. RAND® Corporation. (2011). Finding Services for an Open Architecture. Retrieved from http://www.rand.org/pubs/monographs/MG1071.html

3. NAVAIR PMA-209. Hardware Open Systems Technology (HOST) Tier 1 standard. (Please visit SITIS to download)

4. NAVAIR PMA-209. Hardware Open Systems Technology (HOST) Tier 2 standard. (Please visit SITIS to download)

KEYWORDS: Interoperability; Avionics; Architecture; Mission Systems; FACE; HOST

DoD Notice:  
Between December 12, 2014 and January 14, 2015 you may talk directly with the Topic Authors (TPOC) to ask technical questions about the topics. For reasons of competitive fairness, direct communication between proposers and topic authors is
not allowed starting January 15, 2015 , 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 (15.1 Q&A) during the solicitation period for questions and answers, and other significant information, relevant to the SBIR 15.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 webmail link.


Offical DoD SBIR FY-2015.1 Solicitation Site: