The solution will use tools and processes to facilitate rapid content development and support reusable model content. Additionally, the solution will ensure that the development of combat system domain data models is extensible, maintainable, and flexible for use across multiple warfighting domains. Competing vendors will exercise their ability to create tools that utilize FACE data modeling constructs to detect and marry up the semantic constructs that are documented in the current data model views (physical, logical, cognitive), then creating the needed implementation transformations required to effectively provide congruence at all three levels of information transfer.
New software tools and techniques must be developed to build and maintain data models that capture an interface’s syntax and structure, semantics and contextual meaning, and deployment and communication patterns. The innovative and automated use of the models should decrease the integration effort and required certification at a minimum 80% or more where possible.
Processes should support integration scalability without requiring commonality of interfaces, provide mechanisms to test and limit scope of impact of software updates, and enable the automated generation of optimized integration layer software. The tools and proposed architecture should support a system architect, a system designer, and a system implementer in discovery, analysis, and implementation of complex distributed combat system software. These tools and model processes are applicable to the emerging Internet of Things (IoT) where each device and interface can be unique and commonality-based integration approaches do not work. The research proposed will fill the gap between current data model practices and semantically verifiable matchups for information (not just data) needs. As new or enhanced systems appear, new information constructs are added to the data model, which is a normal evolution for improving applications and weapons technologies. Once properly documented, the 20% of effort creates full automation of semantic information transforms, and becomes a natural part of the growing combat system.
The Phase II effort will likely require secure access, and NAVSEA will process the DD254 to support the contractor for personnel and facility certification for secure access. The Phase I effort will not require access to classified information. If need be, data of the same level of complexity as secured data will be provided to support Phase I work.
Work produced in Phase II may become classified. Note: The prospective contractor(s) must be U.S. Owned and Operated with no Foreign Influence as defined by DOD 5220.22-M, National Industrial Security Program Operating Manual, unless acceptable mitigating procedures can and have been implemented and approved by the Defense Security Service (DSS). The selected contractor and/or subcontractor must be able to acquire and maintain a secret level facility and Personnel Security Clearances, in order to perform on advanced phases of this contract as set forth by DSS and NAVSEA in order to gain access to classified information pertaining to the national defense of the United States and its allies; this will be an inherent requirement. The selected company will be required to safeguard classified material IAW DoD 5220.22-M during the advance phases of this contract.
PHASE I: Develop a concept for an architecture, tools, and processes that streamline the integration of software and show they can feasibly meet rapid integration and certification scaling challenges currently present in today’s combat systems software, as described in the description. Feasibility will be established by modeling and analysis. The Phase I Option, if awarded, will include the initial design specifications and capabilities description to build a prototype in Phase II. Develop a Phase II plan.
PHASE II: Based on the Phase I results and the Phase II Statement of Work (SOW), develop and deliver prototype architecture, tools, and processes that streamline the integration of software and certification of distributed combat system software. The prototype software tools will demonstrate that they meet the objectives outlined in the description. The demonstration will take place at a Government- or company-provided facility. Tests cases include the ability to integrate, and certify software updates and methods for generating conformant data models from existing message sets. Deliver a prototype that is ready to integrate into the IWS 1.0 software acquisition and development processes. Prepare a Phase III development plan to transition the technology for Navy production and potential commercial use.
It is probable that the work under this effort will be classified under Phase II (see Description section for details).
PHASE III DUAL USE APPLICATIONS: Assist the Government in transitioning architecture, tools, and processes that streamline the integration of software to allow for further experimentation and refinement. The implementation will be tools and process for building and leveraging models that facilitate large-scale system integration. The Navy will use the final technology in the IWS 1.0 AEGIS combat system.
Rapid and agile software development processes and architectures have broad application in the IoT market where integration through commonality simply will not work.
Companies in the industrial and manufacturing sectors such as electric power generation, chemical manufacturing, oil refineries, and water and waste water treatment facilities as well as traditional defense contractors (Siemens Industry, General Electric, Schneider Electric, Lockheed Martin, Northrop Grumman), that use control systems as the backbone of their business processes will benefit from the technology as those systems are comprised of many diverse systems communicating to perform a common mission. The tools developed under this effort have potential benefit to these commercial needs.
REFERENCES:
1. “FACE Technical Standard 3.0.” The Open Group. http://www.opengroup.org/face
2. Kendall, Frank. "Implementation Directive for Better Buying Power 3.0 - Achieving Dominant Capabilities through Technical Excellence and Innovation." April 9 2015. http://www.acq.osd.mil/fo/docs/betterBuyingPower3.0 (9Apr15).pdf
3. Kuhn, Kacker, Lei; “Introduction to Combinatorial Testing.” Chapman and Hall/CRC, June 20, 2013, ISBN 9781466552296.
4. Hohpe, Woolf. “Enterprise Integration Patterns: Designing, Building, and Deploying Messaging Solutions.” Addison-Wesley, 2004.
KEYWORDS: Combat Systems Software; System Integration; Data Model; Future Airborne Capability Environment (FACE); Software Certification; Integration Scalability
N181-054
|
TITLE: High Performance Compact Medium-Power Long-Wave Infrared (LWIR) Laser System for Shipboard Deployment
|
TECHNOLOGY AREA(S): Battlespace, Electronics, Sensors
ACQUISITION PROGRAM: Combined EO/IR Surveillance and Response System (CESARS) Future Naval Capabilities (FNC) 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 compact long-wave infrared (LWIR) laser system for the Navy.
DESCRIPTION: Airborne threats to surface ships, whether anti-ship cruise missiles, drones, or aircraft, benefit from passive sensing technology spanning the infrared (IR) spectrum. Passive sensors are widely available, compact, require little power, and generate little waste heat. Furthermore, because passive sensors are not dependent on discrete energy transitions, they are sensitive across contiguous wavelength bands. That is, passive sensors – either discrete photodiodes or focal plane arrays – “see” across a band of the spectrum.
Sensor availability in the long-wave infrared (LWIR) wavelength band offers advantages in certain environments. At times, signature contrast and atmospheric affects favor LWIR propagation in many regions of the globe and certain combinations of humidity and turbulence favor higher contrast imaging in the LWIR. Where space and power allow, prudence dictates that sensing in multiple IR bands (for example, mid-wave IR – from 3 to 5 micro meters - combined with LWIR) be employed together for maximum effect. This presents a significant challenge to ship self-defense systems that must likewise counter threats across multiple bands. Active IR sensors and IR countermeasures require lasers as sources. Optimally, laser sources should cover the broadest range possible within their band to ensure availability. For example, broad coverage in the LWIR band minimizes the vulnerability to counter-countermeasures and allows for optimal transmission at wavelengths favorable for atmospheric propagation. The requirement for broad spectral coverage is achievable, however, it complicates the desire for compactness. Furthermore, the ship’s response system, whether attempting to simply illuminate and detect the threat or apply countermeasures, must transmit sufficient power to achieve the maximum range and the high power-density required presents thermal management challenges. These issues are highly relevant because system performance is enhanced when the laser aperture is mounted high on the ship’s superstructure, making optimization of size, and by inference efficiency, significant considerations and challenges.
The Navy seeks development of a compact LWIR laser system as described above. It should be noted that a “laser system” is considered, in this case, to include technologies where beam combining from multiple individual lasers (or some alternate technology) is used to achieve the requirements (as distinct from a single LWIR laser solution). The laser system is also understood to incorporate any power conversion, packaging, and control required for the system to function as an integrated source of single-beam LWIR laser output. The laser system should cover the entire LWIR band and allow for maximum atmospheric transmission while incorporating means to optimize beam quality for maximum atmospheric propagation. The power output should be 100W or greater in continuous wave (CW) operation. However, technologies that offer scalability of output power are most attractive. In addition to CW operation, the laser system shall also be capable of providing pulsed output.
Physical constraints imposed by the application make minimization of the laser system volume the primary consideration. As a requirement, the laser system shall occupy a combined volume of no more than 8ft3 with a goal of less than 4ft3. Due to the compact packaging this imposes, it is desirable to maximize the efficiency – not so much to conserve ship’s power as to reduce the cooling requirements for the laser system. The proposed solution should indicate the expected power conversion efficiency and show that this efficiency serves the objectives of the proposed solution. The efficiency is here defined as the transmitted average laser beam power divided by the average input electrical power drawn by the laser system. The requirement for this topic is strictly the laser system; aiming and positioning systems such as gimbals are not part of the desired technology.
PHASE I: Define and develop a concept for a LWIR laser system meeting the objectives provided in the description above. Demonstrate the feasibility of its concept in meeting Navy needs and establish that the laser system can be feasibly produced. Feasibility will be established by a combination of initial concept design, analysis, and modeling. The Phase I Option, if awarded, will include the initial design specifications and capabilities description to build a prototype in Phase II. Develop a Phase II plan.
PHASE II: Based on the Phase I results and the Phase II Statement of Work (SOW), design, develop, test, and deliver a prototype LWIR laser system for evaluation and demonstration that it meets the parameters in the description. The demonstration will take place at a Government- or company-provided facility. Provide an affordability analysis that proposes best-practice manufacturing methods to prepare the laser technology for Phase III transition. Prepare a Phase III development plan to transition the technology for Navy production and other potential military uses.
PHASE III DUAL USE APPLICATIONS: Support the Navy in transitioning the technology to the Combined electro-optic and infrared (EO/IR) Surveillance and Response System (CESARS) architecture for further experimentation and refinement. The LWIR laser system implementation will be a fully functional system that can be added to the CESARS architecture. Produce/license the final product and provide for insertion into CESARS and acquisition programs resulting from CESARS in partnership with the acquisition program prime contractor.
LWIR laser technology, as sought for this effort, is primarily applicable to military applications. However, the range of potential military applications is wide. The commercial applications of this technology are primarily in scientific and instrumentation areas such as materials research and spectroscopy.
REFERENCES:
1. Sanchez-Rubio, Antonio. “Wavelength Beam-Combined Laser Diode Arrays.” MIT Lincoln Laboratory Tech Notes, 2012. https://www.ll.mit.edu/publications/technotes/TechNote_beamcombining.pdf
2. Mecherle, G. Stephen. “Laser diode combining for free space optical communication.” Proc. SPIE 0616, Optical Technologies for Communication Satellite Applications, 281 (May 15, 1986); doi:10.1117/12.961064. http://proceedings.spiedigitallibrary.org/proceeding.aspx?articleid=1241781
3. Fan, T. Y. “Laser beam combining for high-power, high-radiance sources.” IEEE Journal of Selective Topics in Quantum Electronics, 11, 2005, 567-577. http://ieeexplore.ieee.org/document/1516122/
4. Leger, J. R., et al. (editors). “Special Issue on Laser Beam Combining and Fiber Laser Systems.” IEEE Journal of Selected Topics in Quantum Electronics, Vol. 15, No. 2, March/April 2009. http://ieeexplore.ieee.org/stamp/stamp.jsp?arnumber=4799145
KEYWORDS: LWIR Laser; IR Sensors; LWIR Propagation; IR Countermeasure; Beam Combining; Laser Source
N181-055
|
TITLE: Scheduling Algorithm for Efficient and Effective Predicted Intercept Points (PIPs) for Multiple Targets
|
TECHNOLOGY AREA(S): Battlespace, Electronics, Sensors
ACQUISITION PROGRAM: Program Executive Office Integrated Warfare System (PEO IWS) 1.0 – AEGIS Combat Systems
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 scheduling software algorithm that instantaneously and accurately predicts intercept points (PIPs) between an interceptor and a target for multiple simultaneous and/or staggered threats.
DESCRIPTION: The AEGIS Combat System (ACS) utilizes the PIP of the interceptor to the target to determine weapons engagement sequencing and scheduling of ACS functions. A PIP is the intersection of two moving or one stationary object by an interceptor(s). Evolving threats, and the prolific manner in which they are used, necessitate the calculation of multiple PIPs to: (1) maintain the highest probability of elimination of a single threat and (2) successfully eliminate multiple threats. Hundreds of data sets comprise a single PIP and the calculation of a PIP requires the use of hundreds of thousands of algorithmic calculations.
A scheduling software algorithm is needed that can instantaneously predict numerous simultaneous intercept points to improve scheduling performance of AEGIS Weapons Systems (AWS). Inputs to the scheduling software include data from track managers, weapons, and missile systems. The scheduling algorithm must reliably provide ACS resourcing recommendations utilizing PIPs that account for variations in the type of threats, the number of threats, operational and test environments, and environmental and engagement debris. A solution must not increase any combat system processing time to achieve its primary objective. It will integrate with all elements of the ACS in order to collect the maximum amount of data sets to include in PIP determination, including track managers, weapons, and missile systems. It will also be able to integrate with the Combat System Test Bed (CSTB) using Real-time JAVA programming language to facilitate system evaluation against more advanced and prolific threats. This will enable shortening of testing and certification timelines for new AEGIS baselines as compared to current timelines. This will also help in maintaining or improving product quality through the early detection of deficiencies in the product. The speed and accuracy of the solution must exceed existing ACS performance attributes resonant in the CSTB.
The scheduling software algorithm developed under this effort will provide an enhanced capability to address targets in raiding or swarming configurations and provide optimal engagement options to the Sailor. This will increase mission capability and effectiveness against the latest threats. Because of the planned implementation in both operational and testing environments, the software will permit realistic testing of interceptor versus evolving threat types and configurations in a dynamic test environment. The modeling and simulation will provide initial physics-based weapon system testing in an environment that does not require the expenditure of ordnance; thereby reducing test complexities and costs associated with fielding new ACS baselines.
The Phase II effort will likely require secure access, and NAVSEA will process the DD254 to support the contractor for personnel and facility certification for secure access. The Phase I effort will not require access to classified information. If need be, data of the same level of complexity as secured data will be provided to support Phase I work.
Work produced in Phase II may become classified. Note: The prospective contractor(s) must be U.S. Owned and Operated with no Foreign Influence as defined by DOD 5220.22-M, National Industrial Security Program Operating Manual, unless acceptable mitigating procedures can and have been implemented and approved by the Defense Security Service (DSS). The selected contractor and/or subcontractor must be able to acquire and maintain a secret level facility and Personnel Security Clearances, in order to perform on advanced phases of this contract as set forth by DSS and NAVSEA in order to gain access to classified information pertaining to the national defense of the United States and its allies; this will be an inherent requirement. The selected company will be required to safeguard classified material IAW DoD 5220.22-M during the advance phases of this contract.
PHASE I: Develop a concept for a scheduling algorithm for PIPs that must show it will feasibly support the operational and test environments identified in the description. Feasibility will be established through comparative evaluation and integration capability into the CSTB environment. The Phase I Option, if awarded, will include the initial design specifications and capabilities description to build a prototype in Phase II. Develop a Phase II plan.
PHASE II: Based upon the results of Phase I and the Phase II Statement of Work (SOW), develop, deliver, and implement a prototype scheduling algorithm for PIPs into an existing Government-approved modeling and simulation environment such as the AEGIS test bed to validate performance. The prototype must be capable of demonstrating the implementation and integration of the engagement model as described in the description. Prepare a Phase III development plan to transition the technology for Navy use and Program of Record
It is probable that the work under this effort will be classified under Phase II (see Description section for details).
PHASE III DUAL USE APPLICATIONS: Support PEO IWS 1.0 in transitioning the prototype PIP algorithm to AEGIS use in the baseline testing modernization process. The effort will consist of integrating into a baseline definition, incorporation of the baselines existing and new threat capabilities, validation testing, and combat system certification.
REFERENCES:
1. Younas, I. and Aqeel, A. “A Genetic Algorithm for Mid-Air Target Interception.” International Journal of Computer Applications (0975 – 8887) Volume 14– No.1, January 2011. http://www.avcs-au.com/library/files/algorythms/pxc3872309.pdf
2. Bentley, J. L. and Ottmann, T. A. "Algorithms for reporting and counting geometric intersections." IEEE Transactions on Computers, 1979. http://ieeexplore.ieee.org/document/1675432/?reload=true
3. Chazelle, Bernard and Edelsbrunner, Herbert. "An optimal algorithm for intersecting line segments in the plane." Journal of the ACM, 39 (1): 1–54. http://dl.acm.org/citation.cfm?doid=147508.147511
KEYWORDS: Scheduling Software Algorithm; Weapons Engagement Sequencing; Predictive Intercept Points; Predict Numerous Simultaneous Intercept Points; Swarm and Raid Tactics; Scheduling Performance of AEGIS Combat Systems (ACS)
N181-056
|
TITLE: Adaptable Boat Launch and Recovery System
|
TECHNOLOGY AREA(S): Ground/Sea Vehicles
ACQUISITION PROGRAM: PMS 500, DDG 1000 Class Destroyer 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 technology required to handle an array of different hull forms and vessel types in boat bay launch and recovery system.
DESCRIPTION: There is a Navy-wide need for a common vehicle launch and recovery mechanism among ships without a well deck. Currently, surface ships without a well deck each have a different method of launch and recovery, and are driven toward a specific craft. A common launch and recovery system that can launch and recover a variety of craft instituted on all surface ship platforms will be a great benefit in both cost and mission capability.
Share with your friends: |