Inactive

The Request For Information (RFI) response due date has been extended to October 3, 2024 4:30pm EST. The questions submitted for this RFI have been attached with the Government responses. 1.0 DESCRIPT... The Request For Information (RFI) response due date has been extended to October 3, 2024 4:30pm EST. The questions submitted for this RFI have been attached with the Government responses. 1.0 DESCRIPTION. Product Lead Strategic Spectrum Warfare (PL SSW) is seeking information from interested vendors who can offer a solution to integrate disaggregated and distributed electronic warfare (EW) capability into/onto either a small-scale transit case or a large-scale Command and Control (C2) platform and/or shelter. PL SSW is interested in understanding how a vendor will approach designing an EW hardware architecture, integrate systems and subsystems to include sensor(s) and/or effector(s) hardware and software, test and validate the same, establish training and maintenance procedures and adapt and evolve the EW system. This RFI, and the capabilities sought herein, are extensible across the PM EW&C portfolio, including but not limited to Terrestrial Layer System (TLS) Echelons Above Brigade (EAB), TLS Brigade Combat Team (BCT), and other current and future EW programs. For further information please visit: https://peoiews.army.mil/pm-ewc/. 1.1 This is a Request For Information (RFI) only. This RFI is issued for information and planning purposes. It does not represent a Request for Proposal (RFP) or a guarantee of future RFP issuance. This RFI does not commit the Government to contract for any supply or service whatsoever. It is important to note that the Government is currently not seeking proposals and will not accept unsolicited proposals. Any costs incurred while responding to this RFI will be the sole responsibility of the responding party, as the Government will not reimburse for any expenses. Not responding to this RFI will not affect eligibility for future RFPs, should they be issued. 1.2 Potential follow-on activities. The Government may use this RFI as a means of competition to grant one or more Title 10 USC 4023 experimentation agreements. These agreements will provide an opportunity for Vendors to demonstrate their software and potentially sell items for testing and evaluation purposes. Following these demonstrations, the Government intends to award one or more prototyping other transaction agreements (OTAs) and/or follow-on production contracts depending on the results of the testing and evaluation. Consortium for Command, Control and Communications in Cyberspace (C5) membership is required to be considered for any follow-on actions. For information on joining the C5 Consortium, please visit https://cmgcorp.org/c5/. 2.0 BACKGROUND. In the past, EW solutions were primarily centralized, with EW capabilities and C2 functions located on a single platform. This conventional setup often led to restrictions on C2 platform mobility and potential limitations in analyzing and targeting radio frequency (RF) emissions associated with targets of interest. To address these challenges, PL SSW aims to address the following. 2.1 Sensor and C2 Platform Integration: Integration of complex RF systems as standalone sensor/effectors, portable form factors (individual or team), and within vehicular platforms/shelters where sensors may be remotely accessed via a C2 link or directly accessed via a combination of on and off platform implementations. 2.2 Software Architecture: 2.2.1 Software architecture: Include details on the software design, programming languages used, software libraries/frameworks, and modularity of the software components. Discuss how the software architecture supports the required functionality to integrate disaggregated and distributed EW capability into/onto a small-scale transit case or a large-scale C2 platform and/or shelter. 2.2.2 Open standards: Identify any open standards, protocols, or interfaces used in the design of the software and hardware architecture. This would include communication protocols, data formats, application programming interfaces (APIs), and any other open standards that are essential to ensuring compatibility and interoperability with other systems or platforms. 2.3 Hardware Architecture: 2.3.1 Describe the criteria for selecting hardware components, microprocessors/system-on-chips (SoCs), communication interfaces, and external hardware modules used in the design. 2.4 Identification of changes in Tactics, Techniques, and Procedures (TTPs): Explore various TTPs to enhance C2 and patching/updating processes, such as time-sharing, queuing, or scheduling techniques. Describe potential collateral effects and countermeasures for TTPs. 2.5 Advanced Analytics: Identification of system capabilities and limitations as a function of implementation and technique(s) such as (performance, scalability, reliability, capability, etc.) 2.6 Systems and Software Engineering Structure: Leverage industry standard Systems and Software Engineering approaches to achieve a more complete set of requirements. 2.6.1 Identify system and software engineering tools, strategies and techniques used in overall system engineering process. 2.6.2 Identify a process(es) of integrating subsystems and components into a functioning system. 2.6.3 Identify system verification and validation process that involves confirming that the designed sub-assemblies and system meets there intended requirements and specifications. 2.6.4 Identify system maintenance approaches (to include ongoing support and improvement of the system) after it has been delivered and deployed. 3.0 REQUESTED INFORMATION: 3.1 Question 1. Please provide details on the vendor's experience in integrating complex RF systems as standalone sensors, portable solutions for individuals or teams, and within vehicular platforms/shelters. 3.1.1 Years of experience: Provide years of experience integrating complex RF systems into/onto a small-scale transit case or a large-scale C2 platform and/or shelter. 3.1.2 Types of projects: Describe the vendor's previous project types and essential details related to those projects. 3.1.3 Technical expertise: Provide experience in RF engineering, signal processing, antenna design, and other relevant fields that is deemed applicable. 3.1.4 Thermal analysis expertise: Provide analysis techniques and tools used to determine and to analyze the thermal behavior of materials, components, and or integrated assemblies. 3.1.5 Facilities: Identify available laboratory spaces (classified and/or unclassified) that could be utilized for open software architecture development and integration including security accreditation, current usage, co-use with partners, power space and cooling. 3.1.6 Certifications and accreditations: Provide any relevant certifications or accreditations in RF engineering, such as IEEE membership, Society of Broadcast Engineers (SBE) certification, or ISO/IEC 17025 accreditation. 3.1.7 References and case studies: Provide references and case studies that demonstrate experience in integrating complex RF systems. 3.1.8 Collaboration with other vendors: List experience working with other companies and vendor(s). 3.1.9 Quality assurance: List quality assurance processes experience. 3.1.10 Regulatory compliance: Outline the vendor's understanding of technical guidelines and RF system integration regulatory requirements, including relevant military, FCC, FAA, IEEE, and other applicable standards. 3.2 Question 2. What experience does the vendor have in the planning and execution of EW missions, (e.g. EW operator workflows and EW operations within the variety of tactical and strategic areas of operations)? 3.2.1 Years of experience: Provide years of experience in the EW industry understanding the operational environment, relevant technologies, and EW operator workflows. 3.2.2 Types of projects: Provide previous projects worked that shows experience with EW operations. 3.2.3 Technical expertise: Provide technical expertise in EW operations as it pertains to areas such as signal processing, communication systems, radar systems, cybersecurity, and other relevant fields. 3.2.4 Certifications and accreditations: Provide any relevant certifications or accreditations in EW, such as IEEE membership, Society of Broadcast Engineers (SBE) certification, or ISO/IEC 17025 accreditation. 3.2.5 Operational experience: Provide experience working in the operational environment, including experience with EW operator workflows and operations within a variety of tactical and strategic areas. 3.3 Question 3. What experience does the vendor have in specifying complex software architectures and in implementing open source and DoD standards (such as Open API, MORA, MOSA, VICTORY, CMOSS, etc.) into those architectures? 3.3.1 Years of experience: Provide years of experience with complex software architectures. 3.3.2 Technical expertise: Provide experience in areas such as software design, software development, software integration, and software testing methodologies. 3.4 Question 4. How does the vendor evaluate performance of the architecture within the design phase of a program? 3.4.1 Use of modeling and simulation: Provide experience with modeling and simulation techniques to evaluate the performance of the architecture before it is implemented. 3.4.2 Use of performance metrics: Provide a set of established performance metrics and best practices used to evaluate the architecture's performance. These metrics can include measures such as response time, throughput, resource utilization, and reliability. 3.4.3 Use of testing tools: Provide testing tools used to evaluate the performance of the architecture. 3.5 Question 5. How does the vendor estimate resource utilization (Field- Programmable Gate Array (FPGA), Digital Signal Processing (DSP), General Purpose Processor (GPP), Graphics Processing Unit (GPU), memory, disk, etc.) during the design phase? Please provide information on your approach(es). 3.5.1 Design Tools: Provide design tools used to estimate space utilization. (e.g. FPGA design tools such as Xilinx, Vivado or Intel Quartus Prime to estimate the size of the FPGA and DSP blocks required for a given design). 3.5.2 Provide software profiling tools used (e.g. Valgrind or Cachegrind) to estimate system memory and disk space requirements. 3.5.3 Modeling and Simulation: Provide the use of any modeling and simulation tools used to estimate space utilization. 3.6 Question 6. What experience does the vendor have as a Systems Integrator managing vendor(s) and subcontract(s)? 3.6.1 Previous experience: Provide previous experience as a system integrator managing other vendors and subcontractors. 3.6.2 Project management methodology: Provide project management methodology used to meet project goals and objectives such as Agile, Waterfall, or Scrum, etc. 3.6.3 Risk management: Provide experience managing risks associated with integrating systems from multiple vendors and subcontractors, including technical, schedule, and budget risks. 3.6.4 Quality assurance: Provide experience implementing quality assurance processes and procedures to ensure that products and services meet the required standards and specifications. 3.6.5 Program outcomes: Provide key examples of program outcomes and lessons learned where applicable. 3.7 Question 7. What capabilities exist at Technology Readiness Level (TRL) 6 or above to perform signal analysis on previously characterized and uncharacterized signals? 3.8 Question 8. How is this capability adaptable to future military and commercial threats (e.g. artificial Intelligence (AI), machine learning (ML), or other).? 3.9 Question 9. What capabilities does the vendor have in Operator assist AI/ML? For AI/ML based or assisted training? 3.10 Question 10. What industry accepted standards/ratings does the vendor have for structured system and software development/implementation (e.g. ISO 9001, ISO 12207, Agile methodologies, Capability Maturity Model Integration (CMMI), etc.) or equivalent? 4.0 RESPONSES: Interested parties are requested to respond to this RFI. Responses are encouraged even if they address only one of questions contained within the RFI. Responses shall provide the following minimum administrative information: Name, mailing address, phone number, fax number, and e-mail of designated point of contact. 4.1 Responses are due no later than 10 September 2024. Vendors shall limit responses to 20 pages. Proprietary information, if any MUST BE CLEARLY MARKED. To aid the Government, please segregate proprietary information (included in the page limit). Please be advised that all submissions become Government property and will not be returned. Vendors shall submit responses via mail to: • U.S. Army, PM EW&C, ATTN: SFAE-IEW-EW, Security Office, 6631 Cyber Street, Bldg. 5100, Aberdeen Proving Ground, MD 21005 4.2 Respondents may provide supplemental information such as product brochures, specification sheets, photographs, illustration, and technical descriptions that describe your company’s current products that most closely match these capabilities described above. Vendors are encouraged not to include marketing informational materials that do not relate to the products recommended for consideration, as they will be discarded. However, responses may include universal resource locater (URL) links to technical documentation materials (i.e., technical data sheet). 4.3 Classified responses. Vendors may submit CLASSIFIED (up to and including SECRET) responses to this RFI. These submissions shall only include the CLASSIFIED portions of the Vendor’s response. Vendors shall submit any CLASSIFIED portions directly to the Government via hardcopy or electronic submission. When mailing CLASSIFIED documents, Vendors must ensure that they are securely packaged and properly labeled in accordance with the appropriate security guidelines. 4.3.1 CLASSIFIED hardcopy submission shall be addressed to U.S. Army, PM EW&C, ATTN: SFAE-IEW-EW, Security Office, 6631 Cyber Street, Bldg 5100, Aberdeen Proving Ground, MD 21005. 4.3.2 The inner wrapper of the submittal shall be addressed to U.S. Army, PM EW&C, ATTN: SFAE-IEW-ES, Attn: Alison Powell, 6631 Cyber Street, Bldg 5100, Aberdeen Proving Ground, MD 21005. 4.3.3 CLASSIFIED (up to and including SECRET) electronic submission shall be via SIPR email to: usarmy.apg.peo-iews.mbx.pmew-pmo@mail.smil.mil or via JWICS email to: ewc.pmewc.pmo.mbx@army.ic.gov. 5.0 QUESTIONS. Vendors shall submit questions regarding this announcement in writing via e-mail. Verbal questions will NOT be accepted. Accordingly, questions shall NOT contain proprietary or classified information. The Government does not guarantee answers to questions received. The deadline for questions is noon on 26 August 2024. The Government will release questions and answers to all vendors by 30 August 2024. Vendors shall submit questions via e-mail to: • Oral Grant, Contracting Officer, oral.g.grant.civ@army.mil • Amber Lowe, Contract Specialist, amber.m.lowe3.civ@army.mil 5.1 Secure Handling Questions. Vendors shall submit questions regarding handling of CLASSIFIED information in writing via e-mail to the PM EW&C Security Officer, Alison Powell, alison.t.powell.civ@army.mil. 6.0 SUMMARY: THIS IS AN RFI ONLY to identify sources that can provide a capability to C2 disaggregated and distributed electronic warfare (EW) sensors/devices on the battlefield. The information provided in the RFI is subject to change and is not binding on the Government. The Army has not made a commitment to procure any of the items discussed, and release of this RFI should not be construed as such a commitment or as authorization to incur cost for which reimbursement would be required or sought. All submissions become Government property and will not be returned.