Department of the navy (don) 18. 1 Small Business Innovation Research (sbir) Proposal Submission Instructions introduction

A CubeSat would likely be used for initial low-cost demonstration of the technology. In general, proposed payloads should:
• Meet the CubeSat Design Specifications [Reference 2];
• Stow within a volume approximately 10x10x30 centimeters or ideally smaller;
• Have 5 kilograms or less mass;
• Survive the Low Earth Orbit (LEO) space environment for at least two years;
• Operate at less than 25 Watts while transmitting, less than 5 Watts in receive mode (if any) and less than 2 Watts in standby mode.

PHASE I: Develop a concept and determine feasibility for the development of a tactical communications payload for small commercial satellites. Create an initial conceptual design for development of a prototype system in Phase II. Predict payload performance using modeling and simulation or other tools. Consider spacecraft integration issues. Estimate the mass, volume, and power requirements.

PHASE II: Build a prototype tactical communications payload and test it in the space environment. Improve the payload design based on feedback from Phase I and from Phase II testing. Demonstrate communications operation of the prototype with an existing tactical radio terminal. Demonstrate operation of the prototype in a simulated space environment to include thermal vacuum and vibration testing (see Reference 2 for testing requirements). Evaluate measured performance characteristics versus payload performance predictions from Phase I and make design adjustments as necessary.

PHASE III DUAL USE APPLICATIONS: Integrate the tactical communications payload with a CubeSat bus and launch into LEO for testing. Demonstrate interoperability with existing tactical communications systems.

The technologies developed under this topic can be applied to a variety of commercial SmallSat missions that are currently in design and development. A number of commercial space firms have stated plans or already begun to develop large communications satellite missions in LEO. This technology could become part of those systems.

REFERENCES:

1. “Naval Open Architecture.” Defense Acquisition University – Acquisition Community Connection. https://acc.dau.mil/oa

2. CubeSat, Developer Resourceshttp://www.cubesat.org/s/cds_rev13_final2.pdf

3. “The Navy's Needs in Space for Providing Future Capabilities.” National Research Council; Division on Engineering and Physical Sciences; Naval Studies Board; Committee on the Navy's Needs in Space for Providing Future Capabilities, 2005, National Academies Press. http://www.nap.edu/catalog.php?record_id=11299

4. United States Navy, Program Executive Office Space Systems (PEO Space Systems) – Programs Overview. http://www.public.navy.mil/spawar/PEOSpaceSystems/Pages/Programs.aspx

KEYWORDS: MUOS; CubeSat; Nanosat; SmallSat; WCDMA; Satellite; Communications; Cellular; 3G

N181-091

TITLE: Long-Duration Proportional Thruster for Navy Hot-Gas Control System

TECHNOLOGY AREA(S): Materials/Processes, Weapons

ACQUISITION PROGRAM: TRIDENT II (D5) ACAT I

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 Announcement. 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 and evaluate advanced, innovative concepts for proportional thrusters for application to the Navy Trident II (D5) strategic missile post-boost control system (PBCS). The proportional thruster design and material selection must advance the state-of-the-art to meet Navy goals for burn-time duration (up to 1,000 seconds) while being compatible with flame temperatures and the chemical environment of D5 PBCS operation. Strategic Systems Programs (SSP) will make available the baseline PBCS System Design Requirements Document and applicable baseline Weapon Specifications upon request. Requests will be in accordance with process defined in SSPINST 5540.2D.

DESCRIPTION: In the 21st century, advances have been made in the area of proportional thrusters for solid propellant, hot-gas controls systems by Navy, Air Force, Missile Defense Agency (MDA), and National Space and Aeronautics Administration (NASA) development programs.

Hot-gas controls systems must be constructed using materials that are thermally, structurally, and chemically compatible with the propellant gases. Higher propellant gas temperatures are a common feature of higher energy control systems. In general, these conditions prevent the use of traditional refractory metals because their strengths diminish significantly with increasing temperature. Phase stability diagrams shed light on microstructural effects, and are calculated from thermodynamic predictions of what phases will exist at a specific temperature and levels of oxygen and carbon in the gas. Using gas thermochemistry calculations, phase stability diagrams predict what phases will be stable given the gas composition. The ratio of carbon monoxide to carbon dioxide is applied to determine the partial pressure of oxygen in the system. At a given temperature, a gas mixture with a lower ratio of carbon monoxide to carbon dioxide (CO:CO2) has a more severe oxidizing environment; this enables one to create oxidizing environments in the laboratory that approximate the oxidizing environments of a range of gas generator propellants, including Navy 1.1 propellant. This is used to conduct 3,000° Fahrenheit testing of thruster material compatibility in an oxidizing environment representative of propellant combustion products. Material science principles must be applied in the development of a hot-gas component. Understanding the environment, time at temperature and pressure, adjacent materials, gas chemistry interactions, thermodynamics, and kinetics is paramount to selecting a material that will survive and provide mission success.

The Navy SSP development of additional PBCS valves is expected to begin in the early-to-mid-2020’s; this SBIR topic will reduce the technical risk of proportional thrusters before the Navy SSP development program begins and positions the program to make an informed decision on whether to re-create the D5 PBCS valves or replace them with proportional thrusters. The proportional thruster design and material selection must advance the state of the art to meet Navy goals for burn-time duration (up to 1,000 seconds) while being compatible with flame temperatures (3,000° Fahrenheit) and the chemical environment of Navy Class 1.1 gas generator combustion products. The combination of extended burn time and compatibility with high flame temperature and oxidizing combustion products presents an extreme technical challenge for which development of innovative technologies is required. The proportional thruster design and material selection must advance the state-of-the-art to meet Navy goals for burn-time duration (up to 1,000 seconds) while being compatible with flame temperatures (3,000° Fahrenheit) and the chemical environment of Navy Class 1.1 gas generator combustion products. The combination of extended burn time and compatibility with high flame temperature and oxidizing combustion products presents an extreme technical challenge for which development of innovative technologies is required. Strategic Systems Programs will make available the technical data regarding the PBCS gas generator's combustion products upon request. Request will be in accordance with process defined in SSPINST 5540.2D.

PHASE I: Develop technical concepts for proportional thrusters for solid-propellant, hot-gas control systems. Conduct top-level trade studies, design concepts, model performance, and perform key tests to transition from Phase I to a Phase II.

Work with Navy SSP to establish key technical requirements for burn-time duration, thrust versus time, flame temperature compatibility, and compatibility with the combustion products of Navy PBCS gas generator propellants.

Use model-based engineering (MBE) techniques to develop technical concepts of designs for proportional thrusters. Develop and apply technologies to meet the thermal-management challenge of a long-duration burn time (1,000 seconds) with flame temperatures approximately 3,000° Fahrenheit. Conduct top-level thermal and structural analyses of the MBE-generated design.

Develop a proportional-thruster performance model for attaining the thrust versus time profile required for Navy PBCS application.

Identity risks to the technical approach and develop plans to mitigate those risks for Phase II. Elucidate the technical approach to the thermal management challenge and risk of a long-duration burn time (1,000 seconds) with flame temperatures of 3,000° Fahrenheit.

PHASE II: Design and fabricate a breadboard, flight-design proportional thruster that will include attach points for integration with the gas generator. Conduct a Systems Requirements Review (SRR) and Preliminary Design Review (PDR) with Navy SSP.

Conduct laboratory experiments and/or modeling as needed to verify the proposed breadboard concept for proportional thrusters. Conduct material compatibility and hot-gas testing of key components for the breadboard concept for the proportional thruster. Note: The small business may subcontract this work to a laboratory capable of conducting hot-gas tests at 3,000° Fahrenheit in an oxidizing environment that emulates that of D5 gas generator combustion products.

Conduct a static-fire test of the flight-design, breadboard proportional thruster at the small business facility. The test will be designed to run the full-duration of 1,000 seconds using a standard, work-horse gas generator and a thrust-time duty cycle that is representative of the D5 PBCS. Conduct a post-test evaluation of the breadboard proportional thruster, write a Test Report, and conduct a post-test review with Navy SSP.

PHASE III DUAL USE APPLICATIONS: Develop a prototype flight design concept for a proportional thruster using model-based engineering techniques. The prototype flight design will meet technical goals for burn-time duration and compatibility with D5 flame temperatures and combustion products.

Refine the breadboard design based on results and lessons learned from Phase II static-fire tests. Fabricate a prototype flight design proportional thruster. The prototype design will include attach points for integration with the gas generator. Conduct a Critical Design Review (CDR) with Navy SSP.

Provide a prototype proportional thruster for testing with a Navy SSP-provided gas generator and associated test components at a Government facility (e.g., the Naval Air Weapons Center (NAWC) at China Lake, CA). Perform post-test analysis of the fired proportional thruster to assess erosion of thruster materials and compatibility with the flame temperature and combustion products of the test. Post-test analysis should include: Pre- and post-test component weights, macro photos, and dimensional analysis. Following these non-destructive measurements, metallographic sections will be prepared and analyzed at low and high magnification. Scanning Electron Microscopy (SEM) will also be used to understand oxidation and microstructural changes of thruster materials the occurred during the static-fire test.

There is the potential that proportional valve technology developed on this SBIR project could be adapted for use on proportional thrusters for NASA and/or commercial spacecraft.

REFERENCES:

1. Sutton, George P., and Oscar Biblarz. “Rocket Propulsion Elements.” Hoboken: John Wiley & Sons Inc., 2010. 8th Edition, p. 236-9. ISBN 978-0-470-08024-5. https://www.amazon.com/Rocket-Propulsion-Elements-George-Sutton/dp/0470080248

2. Lee, J. et al. “Study on the Performance Characteristics of Blunt Body Pintle Nozzle.” 49th AIAA/ASME/SAE/ASEE Joint Propulsion Conference, June 2013. https://arc.aiaa.org/doi/abs/10.2514/6.2013-4080

3. Ponzo, J. et al. “Long Duration Hot Gas Valve Demonstration.” 45th AIAA/ASME/SAE/ASEE Joint Propulsion Conference; August 2009. http://enu.kz/repository/2009/AIAA-2009-5483.pdf

4. “Systems and Software Engineering – Systems Life Cycle Processes.” IEEE 15288 (2015). https://www.iso.org/standard/63711.html

5. “IEEE Standard for Application of Systems Engineering on Defense Programs.” IEEE 15288.1 (2014). https://standards.ieee.org/findstds/standard/15288.1-2014.html

6. “Standard for Technical Reviews and Audits on Defense Programs.” IEEE 15288.2 (2014). https://standards.ieee.org/findstds/standard/15288.2-2014.html

7. “Department of Standard Practices: Technical Data Packages.” MIL-STD-31000 Rev. A.” http://23.96.237.142/wp-content/uploads/2015/10/MIL-STD-31000A-released-on-ASSIST-3-13-2013.pdf

8. “Department of Defense Standard Practice: Documentation of Verification, Validation, and Accreditation (VV&A) for Models and Simulations.” MIL-STD-3022 Chg. 1. https://www.scribd.com/document/136735764/MIL-STD-3022-Documentation-of-Verification-and-Validation

9. “Policy and Procedures for Security Review Requests for the Public Release of Unclassified Information Generated Under the Director Strategic Systems Programs, SSPINST 5540.2 Revision D. http://149.32.95.180/ESSPINST/

KEYWORDS: Proportional Thruster; Pintle Valve; Refractory Metals; Hot-Gas Control System; Navy Strategic Missiles

N181-092

TITLE: Shipboard Cross Domain Secure Solutions

TECHNOLOGY AREA(S): Electronics, Ground/Sea Vehicles, Nuclear Technology

ACQUISITION PROGRAM: Columbia Class - ACAT ID program

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 Announcement. 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 a cross-domain solution for secure networks specialized operating applications and interfaces between systems of differing security classifications.

DESCRIPTION: The security of discrete activities operating within the same network environment under strict requirements for zero data mixing or “spills” is a challenge. Cross- domain data flows impeded by time-consuming release procedures prevent fluid and effective operations. The situation also encourages the entire activity to be carried out at the highest security level to avoid sharing the data between security domains.

Such applications would serve to coordinate activities and maintain data consistency between domains. Such split applications would also reduce the need for ad hoc forms of communication between the domains, whose security is difficult to ensure. Critically, such applications must not enable unintended flows of information between domains. Thus, this SBIR topic focuses on the design of the protocol that ties the two parts of the application together as the key challenge.

While the information being processed by the cross-domain solution will be classified, the system without data will be unclassified.

This SBIR topic seeks two kinds of developments: 1) Protocols or classes of protocols of practical interest to the Navy Strategic Systems Program (SSP) that can be securely operated between security domains, and/or 2) Practical means for determining that instances and implementations of such cross-domain protocols are secure and correct.

The two main parts of the application should run without special privileges in their domains. However, the module that interprets the protocol within the guard is highly privileged, and therefore the highest degree of trust in its correctness and security is of key importance. This component of the system must either be very simple so that manual inspection is feasible, or there must be some other means or strategy for ensuring correctness. Assume that the straightforward operation of the distributed application for its intended purpose is well within the security policy that will be defined as part of this development. This topic focuses on ensuring that the protocol cannot also serve as a conduit for covert communications, or that the bandwidth of such covert channels is limited. Respondents should describe what kind of protocol their system will support, what sorts of cross-domain applications that protocol will enable, and what the overall usefulness of such applications would be in a cross-domain setting. Additionally, the protocols should configure/control the identified hardware to obey the controls and should be identified as part of a software/hardware solution. Respondents should also indicate why it is at least plausible that their selected class of protocols will be secure. Of particular interest will be theoretical advances that enable larger classes of protocols to be handled securely or that enable automated analysis of protocols to ensure that they are secure with mathematical accuracy.

PHASE I: Define a class of protocols operating across domain boundary with a strategy for protecting protocol as it passes through a guard. Provide a security argument/analysis that details a bandwidth limit on the covert channel(s) that could be supported by this protocol. Phase I will also include plans to develop a prototype application under Phase II.

PHASE II: Based on the work completed during Phase I and the proposed Phase II plan, implement tools to support the class of protocols selected including the guard component, and any automated protocol analysis that is necessary to ensure security. Construct a sample cross-domain application using a protocol from that class that meets security requirements and augments the selected hardware for those protocols. Illustrate the security argument in concrete form for this application. The prototypes should be delivered with basic functionality testing by the end of Phase II. During Phase II, it would be advantageous to utilize the FCS development platform located in Pittsfield, MA to coordinate and execute MISM prototype verification and validation testing in the SSBN-R Advanced Development Lab (ADL) and Engineering Test System (ETS).

PHASE III DUAL USE APPLICATIONS: Solve the multi-domain coordination problem for the Navy customer. This design can be applicable for future applications that require handling data in-between multiple security domains. Work with automated guard vendor to install and test protocol checking module. Apply technique to protect communications between multi-network systems. Integrate guard component within existing hardware/software systems. A tested prototype should be delivered by the end of Phase III.

REFERENCES:

1. U.S. Defense Information Systems Agency (DISA) Cross Domain Solutions (CDS) 101. http://www.disa.mil/network-services/enterprise-connections/mission-partner-training-program/cds-101

2. Department of Defense Instruction (DODI) 8510.01: “Risk Management Framework (RMF) for DoD Information Technology.” https://www.hsdl.org/?view&did=793050

KEYWORDS: Cross Domain; Network Security; Protocol; Data Security; Classification Interface; Cross Domain Guard

N181-093

TITLE: Wireless Sensor Technology for Use in Missile System Applications

TECHNOLOGY AREA(S): Sensors, Weapons

ACQUISITION PROGRAM: Strategic Systems Programs; ACAT IC

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 Announcement. 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 and demonstrate a wireless instrumentation system that may be used as the baseline instrumentation system, or to augment a hard-wired instrumentation system for use in Submarine Launched Ballistic Missile (SLBM) systems and/or private sector space launch platforms such as the SpaceX Falcon 9 rocket.

DESCRIPTION: Instrumentation is a critical part of missile system development, testing, and validation. Instrumentation sensors provide data to inform a variety of missile performance parameters, to include temperature, pressure, vibration, acoustic, strain, and video monitoring. While instrumentation sensors have historically been “hard-wired” to a sensor data acquisition package, it is desirable to have wireless capability for some, if not all, sensors in the instrumentation suite. The cabling associated with wired systems yields a lack of system flexibility, as the cabling infrastructure would need to be changed to accommodate the addition or change to sensors and sensor locations. Eliminating or reducing the need for onboard cabling would promote greater flexibility of the sensor suite, and offer the opportunity to tailor the instrumentation according to the needs of a development and flight test program. Additionally, the reduction or elimination of an onboard cable infrastructure would reduce the weight of the missile system. A wireless system, or a hybrid wired/wireless system, can be advantageous to a variety of missile systems and commercial launch vehicles.

The following capabilities should be addressed by the proposed solution:
• Ability to add sensors to a baseline instrumentation system without the addition of wires
• Ability to operate without external power for 60 days standby and 60 minutes operating time
• Ability to survive typical missile launch environments (shock, vibration, vacuum)
• Ability to remain fully operational through short duration (<60 minutes) space radiation environments
• Ability to support multiple sensors (50+ temperature, vibration, pressure) at a variety of data rates (10Hz to 10kHz).
• Ability to support high data rate sensors such as video (e.g., 30fps 1080p video—compressed)
• Ability to transmit over a distance of 50 feet through various structure elements and through staging events (rocket motor case, rocket motor plume, propellant)
• Assessment of wireless signal interface caused by transmission through various structure elements and staging events