Forward Area Air Defense Control System

Description: The United States (U.S.) Government is conducting market research to identify currently available software solutions which provide Counter-Rocket, Artillery, Mortar (C-RAM), Counter-Unmanned Aerial Systems (UAS), and Short-Range Air Defense (SHORAD) Command and Control (C2) solutions. Any solutions offered must be capable of maintaining Forward Area Air Defense (FAAD) Command and Control (C2) software capabilities and interfaces while incrementally incorporating the Army's Integrated Air and Missile Defense Battle Command System's (IBCS) software architecture and data interfaces. The U.S. Government seeks to maintain the current system capability set as well as provide enhancements to meet emerging requirements. Respondents must: Given a full TDP and source code of existing FAAD C2, must be able to sustain, maintain, and develop future capabilities to satisfy the Government's requirements. This will require extensive experience in the ADA programming language. Perform required functions for the SHORAD, Maneuver-SHORAD (M-SHORAD), C-RAM, Counter-Unmanned Aircraft Systems (C-UAS) battle space, United States Marine Corps Ground Based Air Defense (USMC GBAD) capabilities, and Air Force Research Laboratory directed energy technologies. Interface with systems in the C-RAM and SHORAD mission space to include Avenger, Compact Laser Weapon System, Reconfigurable Integrated Weapons Platform, Coyote, Tactical High-Power Microwave, Land-Based Phalanx Weapon System, M-SHORAD, IBCS, Improved Sentinel, Fire-Finder (Q-36 and Q-37), Lightweight Counter Mortar Radar, Q-53 Counterfire Target Acquisition Radar, Multi-Functional Radio Frequency System, RPS-42 Multi-Mission Hemispherical Radar, NightHawk Electro-Optical/Infrared surveillance system, Duke Electronic Warfare Suite, and CORIAN C-UAS technology providing overarching FAAD C2 for those systems. This interface must be accomplished with no requirements change to the system. Interface and exchange tactical data messages with Air and Missile Defense Workstations (AMDWS). Provide software modernization plan to support ongoing (regression testing/backwards compatibility) and future requirements. Run in the real-time safety critical embedded computing environment and support real-time track acquisition, track identification, track correlation, track alerting, track management, track cueing, track dissemination functions, battle management and status, weapon coordination and management, and saturation alleviation. Support Sense, Warn, Intercept, and Respond to missions of the FAAD C2 System. Must run on existing, government furnished equipment; Miltope SRNC-17, Dell Latitude 7212, and Crystal Rugged Embedded Computer RE1218M. Must be completely interoperable with legacy fielded FAAD C2 Systems to include real-time exchange of air and space tracks, RAM tracks, engagement orders with history, Change Data Orders (CDO), unit operational status, track management and battle management data. Must provide a training, safety, and logistics package capable of achieving Government validation to support urgent and full material releases. The training will include FAAD C2 computer based training (CBT), CONUS on-site training, and AMDWS training. The logistics package will include Field Service Representatives (FSRs), technical manuals, and delivery of software upgrades and patches. Provide test support in the field and lab. Simultaneously support a dual C2 mission role which includes real-time air defense and RAM Engagement Operations. Must operate at the Secret and unclassified levels. Must comply with the Department of Defense Risk Management Framework. Provide joint service history. Interested firms who believe they are capable of providing the aforementioned services are invited to indicate their interest by providing the following information: Company name, company address, overnight delivery address (if different from mailing address, Cage Code, point of contact, e-mail address, telephone number, fax number. Business size (i.e. large, small disadvantaged, veteran owned, woman owned, etc.) Unclassified white paper on 8.5 x 11 inch paper with fonts no smaller than 10 point, one inch margins, in a Microsoft Word or Adobe file format. Each page of the submission shall contain a document identifier in the document header. Respondents should ensure to label any information contained in the white paper considered to be proprietary. At a minimum, the white paper shall provide a description of the technical approach and a statement on how the technical capabilities meet the following key attributes: Technical Overview: Including how the system accomplishes C-RAM C2 capabilities as defined above. Operational Effectiveness: Including a description of how the C2 system enables weapons and sensors to accomplish required missions. Integration: Ability of the system to integrate with AMDWS, existing/off the shelf sensors and effectors, and Joint/NATO data links such as Link16, Link 11B, Joint Range Extension Application Protocol (JREAP) and Low Level Air Picture Interface (LLAPI). Sustainability: Consider sustainability with theater assets (training and maintenance) Affordability: Estimated system costs for budgeting purposes. System costs must be both reasonable and achievable. The baseline for requested solutions is the ability to meet the minimum requirements of the current system. Responses should clearly identify and summarize all previous testing of either individual components of their proposed system of systems, or of the integrated system of systems, by either U.S. Government agencies or other test agencies. Conformance: Conformance with the U.S. Government open systems architecture initiatives. Responses should discuss types, extent, depth and breadth of analysis and data to substantiate performance and containment claims. Responses should also describe the firm's capability and experience in providing tactical systems in this mission area. The white paper will contain no more than 20 total pages including tables, charts, and figures. The white paper should include a technical POC, phone number and email. This RFI is for planning purposes only and shall not be considered as an IFB, RFQ, or RFP. Additionally, there is no obligation on the part of the Government to acquire any products described in this RFI. Your response to this RFI is voluntary and will be treated only as information for the Government to consider. You will not be entitled to payment for direct or indirect costs that you incur in responding to this RFI. This request does not constitute a solicitation for proposals or the authority to enter into negotiations to award a contract. No funds have been authorized, appropriated, or received for this effort. The Army may use the information provided to develop its acquisition strategy. Interested parties are responsible for adequately marking proprietary, restricted, or competition sensitive information contained in their response. The Government will not pay for the information submitted in response to this RFI. If a solicitation is released for the supplies or services described herein, then it will be synopsized through the government point of entry (GPE) web site. It is the responsibility of the potential offerors to monitor this site for additional information pertaining to this potential requirement.