TECHNOLOGY AREA(S): Air Platform
OBJECTIVE: This effort intends to enhance the ability for small units to recover, charge, and relaunch SUAS with minimal significant user input. Improving these aspects of SUAS operations will minimize time and effort spent preparing and recovering the SUAS, and allow the soldier to maximize focus on the surrounding area
DESCRIPTION: With the introduction of SUAS operational concepts, Soldiers are now able to remotely maintain eyes on target and remain out of harm’s way. Due to a finite power supply, however, SUAS are limited to short flight times before they must be returned to the user, recovered by the user, recharged at a charging station, and relaunched. Additionally, current SUAS that are used by soldiers are not paired with launchers, and require the soldier to manually launch the SUAS when flown. These tasks prevent continuous monitoring of the target, and require additional effort that are a significant distraction from the mission. As a way to provide continuous target coverage, it is possible to use multiple SUAS with overlapped flight times that will allow time for each UAS to charge and return to the target. While this solution addresses the issue of constant coverage, it increases the burden on the user to recover and prepare each SUAS to relaunch.
In addition, there is increased interest in SUAS “swarming” capabilities, which allow several SUAS to work together simultaneously to complete tasks that are beyond the capabilities of each individual system. As this capability develops, the management of large numbers of SUAS “swarms” will likely not be feasible with current equipment.
With increased fielding of SUAS, and increased number of scenarios that require the use of multiple systems, there is an increased need for a technology that is capable of reducing the physical and cognitive burden of recovery, recharge, and relaunch activities from the Soldier. Therefore, the primary focus of this effort should be on the design and development of a system to reduce the burden of these actions while adhering to the power, size, and weight requirements as specified below.
Concept of Operations Description: The CONOPS intended for this system surround a small unit of dismounted soldiers that are tasked with maintaining eyes on target with at least two SUAS units, designated SUAS-A and SUAS-B. The system is intended to launch SUAS-A, while maintaining charge on SUAS-B. As SUAS-A reaches low power state, the system should launch SUAS-B as SUAS-A automatically returns to base and lands on or near the recovery system. The system should then be able to recover, charge and relaunch SUAS-A by the time SUAS-B reaches its low power state. Charging duration of SUAS must be less than the flight time of the SUAS, which differs between each fielded SUAS. CONOP can be scaled to the number of SUAS units carried by the dismounted unit, and developed system must be able to function similarly with a minimum of four (4) SUAS in any given mission.
The technology should have the following performance requirements:
o System Weight: 10lbs (Threshold). 5lbs (Objective). System weight includes power source and all ancillary equipment. System weight does not include weight of SUAS
o System Volume: 3ft3 (Threshold); 1ft3 (Objective). System volume includes power source and all ancillary equipment. System volume does not include volume of SUAS
o Power Requirements
Interface: System must accept power from standard military batteries.
Duration: Operational Runtime must be at least 4 hours (Threshold) and up to 8 hours (Objective).
o Interface Compatibility: System must be compatible with military fielded SUAS. This could include direct compatibility with SUAS and its charging interfaces, or just compatibility with the charging units included with each fielded SUAS.
o Recovery Range: System must be capable of recovering SUAS within a range of 20 feet of launch point. SUAS recovery is defined as collecting the SUAS from its landing location and connecting it to the charging dock for charging.
PHASE I: Research, develop and propose a design concept with the potential of realizing the goals in the description above. Describe and quantify how the proposed solution offers enhancement(s) over current technology approaches and/or how it augments other strategies/technologies. Conduct necessary investigation and breadboarding on the design and performance of the components to demonstrate the feasibility and practicality of the proposed system design, minimizing user input. Deliver monthly progress reports and a final report documenting the research and development efforts, identifying any technical challenges that may cause a performance parameter(s) not to be met, results of any modeling, safety issues, and estimated production costs. All drawing and code developed during this effort are to be included in the final report.
PHASE II: Develop the technology identified in Phase I. Fabricate, demonstrate and deliver one prototype (including SUAS recovery and relaunch device and any ancillary devices, with the exception of standard military batteries). The prototype must be capable of demonstrating the performance goals stated in the description above in the relevant environments, in addition to weather hardening and increased portability of system. For the proposal, bidders can prepare their estimates based on the Army providing two of the selected systems for test and demonstration purposes. Selection process for Army fielded SUAS is scheduled for early FY18. Additionally, the unit cost after development must not exceed $15,000. Deliver monthly progress reports and a final report documenting the design specifications, performance characterization and any recommendations for future development.
PHASE III DUAL USE APPLICATIONS: A device meeting the performance requirements outlined in this effort would be applicable to military, industrial, and recreational user groups. Those who operate multiple SUAS simultaneously would realize significant reduction of effort and increased time on task benefits. Detection and Response Personnel would be able to increase coverage of a protected area while maintaining focus on operation of SUAS.
REFERENCES:
1. AV Snipe Description http://www.avinc.com/uas/view/snipe
2. Department of Defense; Release No. NR-008-17; Department of Defense Announces Successful Micro-Drone Demonstrations; 9 Jan 2017. Swarming Demonstration https://www.defense.gov/News/News-Releases/News-Release-View/Article/1044811/department-of-defense-announces-successful-micro-drone-demonstration/
3. Army Short-Range SUAS Salient System Requirements http://www3.natick.army.mil/docs/SUAS/Attachment6_Short_Salient.pdf
A18-077
|
TITLE: Innovative Marking Technology for Hand Grenades
|
TECHNOLOGY AREA(S): Weapons
OBJECTIVE: Develop an innovative technology and/or process that will provide legible and robust marking on various hand grenade bodies (shapes and materials), with initial focus on XM111
DESCRIPTION: The body of the XM111 Offensive Hand Grenade has a unique shape and designated material (Noryl N190X), which makes the body challenging to mark with legible and robust marking. Currently, the XM111 is in development and the current developmental marking method is through manual pad printing application which is a slow, inconsistent method requiring post process steps to clean overspray and smudges. Pad printing also does not result in a durable and robust solution for lifecycle use. Market research on currently available methods has not identified any existing method that would meet all requirements of the XM111. Therefore, a new and innovative process/product is needed that will meet legibility and durability requirements of the XM111; and reduce or eliminate the preparation required prior to marking the bodies (e.g. necessary pretreatment and cleaning), post processing, and inconsistent legibility of text. Additionally, the new technology/process shall not require complex automation or equipment so as to keep capital investment and follow-on production costs low, and shall be compatible with marking explosively loaded items (i.e. shall not require high heat). Markings are expected to remain legible for at least 20 years while experiencing a storage temperature range of -65 deg F to 165 deg F. Assuming success, the technology/process may also be applied to other grenade munitions to include the M82 and L96/97.
PHASE I: Study various printing/marking technologies and processes that will meet product requirements, resulting in a recommendation of final technology/process(es). Representative samples of the grenade body (inert) will be subject to the new technology/process and tested per standard evaluation techniques, to include acetone and spackle knife tests. A final report will document results of the testing as well as process parameters such as pre and post processing requirements, equipment and supplies/materials required, expected throughput, and overall cost. Phase I option will include delivery of the initial System Requirement Specification (SRS) which will annotate technical requirements and verification methods. The SRS shall be approved by the government.
PHASE II: Mature the technology and/or process to scale-up to meet the up to 50,000 units per month throughput rate. Demonstrate a pilot production line that meets required production rates (using inert samples). Test samples from the production line to ensure products meet performance requirements. Submit a final report documenting the production process and parameters, including equipment/supplies required, test results, and recommendations for further process refinement. The final Phase II pilot production line shall be delivered to the Government to a site TBD.
PHASE III DUAL USE APPLICATIONS: The objective goal of this SBIR project is to integrate the resulting technology/process in a government load-assembly-pack (LAP) facility, therefore it is important that the capital costs associated with implementing the results be kept at a minimum. This technology has widespread commercial applicability with any product with complex shapes requiring robust yet affordable marking techniques.
REFERENCES:
1. A Basic Overview of the Pad Printing Process, Peter Kiddell http://www.epsvt.com/wp-content/uploads/2017/04/1.Articles_A%20basic%20overview%20of%20the%20pad%20printing%20process.pdf
2. NORYL N190X material property datasheet, Matweb, http://www.matweb.com/ and enter "SABIC NORYL N190X" in the search box
3. PEO Ammunition Systems Portfolio Book, 2012-2013, pages 97-109, http://www.dtic.mil/get-tr-doc/pdf?AD=ADA567897
4. MIL-STD-810G; https://www.atec.army.mil/publications/Mil-Std-810G/Mil-Std-810G.pdf
A18-078
|
TITLE: Advanced Artillery & Mortar personnel Blast Gauge System
|
TECHNOLOGY AREA(S): Weapons
OBJECTIVE: Develop an advanced gauge that will measure blast overpressure at the mortar or artillery weapon and provide that data to the fire control computer or other computerized systems for analysis and use in decision making.
DESCRIPTION: Assessing the soldier's blast exposure is important to prevent traumatic brain injuries and hearing loss, and assisting the trauma team in guiding triage with blast exposure data. Currently Blast Over Pressure (BOP) for artillery and mortars is tracked using the weapon’s digital fire control system (DFCS). If the DFCS malfunctions, the crew reverts to a manual BOP exposure tracking method. This conservative technique assumes the worst case exposure which limits the amount of rounds to be fired. The advanced blast gauge system would accurately measure the actual individual exposure to safely optimize the allowable number of rounds to be fired. This system would allow for accurate tracking of exposure in unusual scenarios not captured in training and/or the operational manual (e.g. unusual terrains and firing proximity). Ideally, the blast gauge would be integrated with the weapon’s digital fire control and automatically provide data to the crew chief and platoon/battery leadership to support informed decisions during live fire training and combat missions.
PHASE I: Study various options for measuring BOP and include modeling and simulations and laboratory testing to validate that the proposed solutions would meet system requirements. At the conclusion of Phase I efforts, submit a report on the engineering analysis of the proposed options and results of modeling, simulations and/or testing. Propose the solution(s) that should be continued in Phase II with adequate justification. Phase I option will include delivery of the initial System Requirement Specification (SRS) which will annotate technical requirements and verification methods. The SRS shall be approved by the government.
PHASE II: Build prototype systems and demonstrate that prototypes can perform in operational environments while providing the required information to the fire control computer. Demonstration at a government facility may be required to demonstrate the operational environment. A surrogate fire control computer (i.e. ruggedized laptop with simulated fire control software) can be used to support the demonstration in lieu of integrating with the actual fire control system. Produce final prototypes that meet system requirements per the SRS. Submit a final report that describes the testing performed on the items, and contains technical data on the gauge, simulated fire control software, and any other product deliverable.
PHASE III DUAL USE APPLICATIONS: Phase II will consist of integrating the new BOP gauges into the fire control systems of mortar and artillery systems and deploying as appropriate. This technology has commercial application for any occupation subject to loud noises caused by sonic events (such as well drilling, rock blasting, building demolition, etc.), as well as certain sporting events such as football.
REFERENCES:
1. Brain Vulnerability to Repeated Blast Overpressure and Polytrauma; Long, Joseph B; May 2012
2. Standardization of Muzzle Blast Overpressure Measurements; Patterson, James; Coulter, George A.; Kalb, Joel ; Garinther, George; Mozo, Benjamin; APR 1980
3. An Introduction to Detonation and Blast for the Non-Specialist; Wilkinson, C. R. & Anderson, J. G.; NOV 2003
4. Use of Blast Test Device (BTD) During Auditory Blast Overpressure Measurement. Test Operations Procedure (TOP) 4-2-831; DIRECTORATE FOR TEST MANAGEMENT ABERDEEN PROVING GROUND MD TEST BUSINESS MANAGEMENT DIV; 12 AUG 2008
KEYWORDS: Blast Over Pressure, Traumatic Brain Injury, Hearing Loss, pressure gauge, blast attenuation, artillery, mortar
A18-079
|
TITLE: Novel Reserve Power System with High-Power On-Demand Capability
|
TECHNOLOGY AREA(S): Weapons
OBJECTIVE: investigate and develop innovative reserve battery technologies that provide the required pulse power, exceed the 20 year shelf life, survive severe gun launch shock and heat environments, and are affordable and readily available within the commercial marketplace.
DESCRIPTION: Current reserve batteries used in munitions meet operational requirements, however suffer performance loss at extreme temperatures and are only able to be used once (not conducive for emplaced munitions). Additionally, there is no significant commercial market for the reserve batteries used in munitions, so the cost is higher than it should be and availability is lower. The proposed project aims at developing new reserve power systems with energy management architectures and initiation methods that make the power system programmable to fit various application missions. Prior to activation, the energy storage system remains in a quiescent state with negligible self-discharge, power drain or leakage. Activation may occur via remote control or various triggering mechanisms and once activated the power system must be capable of providing a relatively low amount of electrical power over periods that may be as long as one month while being capable of providing short duration high power pulses on demand. Shelf life of the proposed power system concept is expected to exceed 20 years and the temperature performance of the energy storage system must meet full military required operational and storage temperature range of -65 deg. F to 165 deg. F. Additionally, the power system must be capable of being deployed by low and high spins rounds and withstand high launch accelerations and flight vibration. The power systems being sought by this topic must be scalable, miniaturizable and must be safe to operate across the harsh environments produced by military applications. The power system must be capable of providing a relatively low amount of electrical power over periods that may be as long as one month while being capable of providing short duration high power pulses on demand. As an example, the power system must provide 180 mW of power at 9 Volts over 30 days, while being capable of providing at least five pulses of 2-4 seconds duration of power at 5 and 9 Volts with 0.5 and 1 A current, respectively. It is highly desirable that the power system provide relatively fast initiation (200 mS), but power for the indicated pulses be available in 20-30 msec upon demand. The new power systems are desired to occupy relatively small volumes, 16 cubic cm threshold and less than 1 cubic cm objective.
PHASE I: Study various novel reserve battery chemistries and designs that can provide the required nominal low and high pulse power over a 30 days period following activation. The feasibility study is expected to include and modeling and simulations and laboratory testing of the critical components of the candidate power system concepts, and development of a strategy for achieving the best possible power system architecture for minimal volume, initiation mechanisms, and all other system components, to meet power and application objective of topic. At the conclusion of Phase I efforts, a selected design meeting the power requirements of a host application would have to be proven feasible, in order to be ready to advance to the project Phase II. Phase I option will include delivery of the initial System Requirement Specification (SRS) which will annotate technical requirements and verification methods. The SRS shall be approved by the government.
PHASE II: Build full-scale reserve power system prototypes and test in relevant environments, including simulated launch events. Demonstrate that prototypes can survive in operational environments while providing voltages and power requirements under simulated load conditions. Produce final prototypes of each design that meets power requirements mentioned in the description, conduct survivability and performance tests. Develop a manufacturing plan for transitioning from prototypes to low rate initial production.
PHASE III DUAL USE APPLICATIONS: The objective goals of this SBIR project is the insertion of this novel reserve power system into a number of military applications with small and medium power requirements over long periods of times, which might be days, weeks or over a month, which may include short periods of high power requirements (pulses). Such power systems may be used to power devices in gun-fired munitions or mortars or devices that are deployed by air or hand placed.
Possibility for application not limited to the area of munitions and could include power sources for remote sensor network devices, emergency memory back up for computer systems, and power sources for anti-tampering electronics.
REFERENCES:
1. Handbook of Batteries - Linden, McGraw-Hill, “Technology Roadmap for Power Sources: Requirements Assessment for Primary, Secondary and Reserve Batteries”, dated 1 December 2007, DoD Power Sources Working Group.
2. Macmahan, W., “RDECOM Power & Energy IPT Thermal Battery Workshop – Overview, Findings, and Recommendations,” Redstone Arsenal, U.S. Army, Huntsville, AL, April 30 (2004).
3. Linden, D., “Handbook of Batteries,” 2nd Ed., McGraw-Hill, New York, NY (1998).
4. R. A. Guidotti, F. W. Reinhardt, J. D., and D. E. Reisner, “Preparation and Characterization of Nanostructured FeS2 and CoS2 for High-Temperature Batteries,” to be published in proceedings of MRS meeting, San Francisco, CA, April 1-4, 2002.
5. Delnick, F.M., Butler, P.C., “Thermal Battery Architecture,” Joint DOD/DOE Munitions Technology Program, Project Plan, Sandia Internal Document, April 30, 2004.
A18-080
|
TITLE: Common Engine Software Interface (FADEC) Component
|
TECHNOLOGY AREA(S): Air Platform
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 5.4.c.(8) of the Announcement.
OBJECTIVE: Develop data models, architectural concepts, and components for use in developing a common avionics to engine interface, including data modeling for general Full Authority Digital Engine Controller (FADEC) interfaces to the avionics suite. The intent is to have common reusable software for engine controllers that are Future Airborne Capabilities Environment (FACE™) Units of Portability (UoPs) and that also meet airworthiness or security requirements unique to the US Army. This would ensure that as engines are updated that integration with respect to the avionics suites in use by the Army is simplified and streamlined and also that the data model for common engine information is complete.
DESCRIPTION: The US Army is developing an Improved Turbine Engine that will upgrade the current engines on Black Hawk and Apache platforms and pave the way for Future Vertical Lift (FVL) engine programs. Modern engines utilize FADEC technology, which is complex and highly specialized, thus it is highly unlikely that in competitive engine procurement a common FADEC will be procured for future engines. It is likely that FADEC technology will be used and upgraded as an ongoing improvement for the Army both in modernization and in new program development. While it may not be possible to fully isolate change for integrating future FADEC technology (e.g. reuse a common FADEC on any engine), the information from the engine is brought forward into the avionics suite for use by various software applications and for display to the crew. This data represents a subset of the total complex data that a FADEC or other engine controller requires for that unique function. The common data required by the typical avionics suite to interface with FADEC may benefit from a common data model and one or more software components that abstract the complexities of a specific engine and specific FADEC. Ideally, a common abstraction layer for engine interface could be built including common FACE Conformant Units of Portability (UoP)s that will ease the integration burden on platforms with disparate avionics suites receiving upgraded engines.
Appropriate data rights to the key interfaces, including the data models and architectural artifacts for integration, will be desired and discussed post award to ensure reuse of the key interface definitions is enabled for non-proprietary information and data. It is not the intent of the Government to possess rights to prior innovations that may be leveraged or any proprietary products or developments.
Share with your friends: |