Federal Procurement Notice•Posted: 2025-01-23

AFRL-RVKY-2025-SHREC

Entity
DEPT OF DEFENSE
Posted
2025-01-23
DepartmentDEPT OF DEFENSE
Notice Typer
NAICS541715
Notice IDbf4a45d077d54162a93769c3025cefd2

Source Record

REQUEST FOR INFORMATION (RFI) AIR FORCE RESEARCH LABORATORY (AFRL) SPACE VEHICLES (RV) DIRECTORATE SPACECRAFT COMPONENT TECHNOLOGIES (RVSV) RFI ID: AFRL-RVKY-2025-SHREC 23 January 2025 OVERVIEW CONTRACTING OFFICE ADDRESS AND POINTS OF CONTACTS Department of the Air Force Material Command (AFMC), Air Force Research Laboratory, Space Vehicles Directorate, 3550 Aberdeen Ave, SE, Kirtland AFB, 87117-5776 CONTRACTING POINTS OF CONTACT (POC) Mr. Francis Eggert (Primary) Ms. Paige L. Thompson (Alternate) Contracting Officer Contracting Officer AFRL/RVKY AFRL/RVKY Phone Number: 505-846-5935 Phone Number: 505-846-2070 Email: francis.eggert@us.af.mil Email: paige.thompson@spaceforce.mil TECHNICAL POINTS OF CONTACT (POC) Dr. Andrew C. Pineda Ms. Amanda P. Fetzer AFRL/RVSV AFRL/RVSV Phone Number: 505-853-2509 Email: amanda.fetzer.2@spaceforce.mil Email: andrew.pineda.6@spaceforce.mil PROGRAM MANAGER (POC) Mr. Manuel V. Gonzales AFRL/RVFC f/RVSV Email: manuel.gonzales.9@spaceforce.mil 1. Part: U.S. Government Procurements Request for Information (RFI) 2. Subpart: R&D Memberships 3. Procurement Classification Code: A � Research and Development (R&D); Code # 18 � Space Vehicles Directorate 4. Agency: Department of the Air Force 5. Responsible Office and Address: Air Force Research Laboratory (AFRL), Space Vehicles Directorate (AFRL/RV); Mail to: AFRL/RVKY (WEST AREA GENERAL MAIL ROOM); Attn: Mr. Francis M. Eggert 3550 Aberdeen Ave. S.E.; Building 425, Room 100, 1st floor; Kirtland AFB, N.M. 87117-5773. 6. North American Industry Classification Systems (NAICS) Code: 541715 � R&D in the Physical, Engineering & Life Sciences (except Biotechnology) 7. RFI ID: AFRL-RVKY-2025-SHREC 8. Notice Type: Sources Sought to Space Computing community for memberships 9. Subject: Develop leaders in technology, development, and science and technology working groups. Space, High-Performance, and Resilient Computing (SHREC) FY25 and beyond. Fault-Tolerant Techniques for Heterogenous Computing Architectures, and Reliable Non-Volatile Memory (NVM). Provide reliability testing for selected FPGAs, reliability testing of deep learning hardware in a radiation environment, reliability testing of high-performance memory, and general radiation testing of heterogenous computing devices. The Government shall determine the number of memberships and Option year(s) based upon offeror(s) recommendations and the funds available for the FFP. The Government can decide to award to one, more than one, or no memberships to one, more than one, or no offerors. 10. Background. Center for Space, High-Performance & Resilient Computing, an NSF IUCRC, was founded in Sep. 2017, replacing the highly successful NSF CHREC Center. Under auspices of IUCRC Program at NSF, the program fosters university, agency, and industry R&D collaborations in space and high-performance computing. SHREC is both National Research Center and consortium, university groups serve as research base (faculty, students, staff), industry & government organizations are research partners, sponsors, collaborators, advisory board, & technology-transfer recipients. 11. Mission: MISSION CRITICAL COMPUTING, Basic and applied R&D to advance Science & Technology (S&T) on advanced computing that captures 20+ program needs for government and commercial space applications. Many common challenges, technologies, & benefits, in terms of performance, power, adaptivity, productivity, cost, size, etc. from architectures to applications to design concepts and tools spanning applications from spacecraft to supercomputers! 12. The Air Force Research Laboratory is issuing this "Request for Information" to Industry and Academic sources to gather current data on the existing market sector, identify potential market characteristics, best practices, emerging technologies, sources of supply, vendor capabilities, and to assist the government with leveraging opportunities so that an informed acquisition strategy can be accomplished. The Air Force Research Laboratory is interested in determining existing capabilities and future capacities to provide research and development in the areas of Space, High-Performance, & Resilient Computing (SHREC). The applicable North American Industry Classification Systems (NAICS) code assigned to these activities is 541715 Research and Development in the Physical, Engineering, and Life Sciences (except Biotechnology). This U.S. Industry comprises establishments primarily engaged in conducting research and experimental development (except biotechnology research and experimental development) in the fields of engineering, electronics, computers, chemistry, physics, and other allied subjects. 13. THIS IS NOT A SOLICITATION. This request is for capability information and does not constitute a request for proposal; submission of any information in response to this request for Information/market survey is purely voluntary; the government assumes no financial responsibility for any costs incurred. 14. This notice is for planning purposes only and does not commit the Government to any contractual agreement. Telephone inquiries will not be accepted or acknowledged, and no feedback or evaluations will be provided to companies regarding their submissions. 15. SAMPLE RESPONSE OUTLINE There is a suggested total page count limit of 10 pages for each topic area response. The following is a suggested outline for a response to this RFI. The page limitation and outline to this RFI is intended to minimize the effort of the respondent. Nevertheless, respondents are free to develop their responses as they see fit. 16. SECTION 1: CORPORATE EXPERTISE Briefly describe your company, your products and services, history, ownership, financial information and other relevant information. As part of your corporate expertise, please highlight critical elements in the envisioned solution to meet one the topic area outlined above. Also, discuss your ability to perform work in a classified environment. Identify any foreign ownership or investment. It is expected that Section 1 from this sample response outline is less than 10% of the response. 17. SECTION 2: TECHNICAL SOLUTIONS Describe your company�s concept for the proposed solution addressing one of the topic areas outlined above. The proposed concept should address the various capabilities and capacity. Describe any technologies in your current product line, as well as products currently under development that meet the capabilities identified in Section 10. Provide performance and physical specifications for each product, as well as anticipated performance for products under development. The technical solution should also include test plan outlining a series of tests/experiments to increase Technology Readiness Level (TRL) of proposed architecture. 18. SECTION 3: COST AND SCHEDULE ESTIMATES Provide a Rough Order of Magnitude (ROM) cost and schedule estimates for design/build to properly scope a United Acquisition Strategy. 19. SECTION 4: ADDITIONAL DETAILS Please provide any other materials, suggestions and discussions you deem appropriate. Include any recommended structure of the requirements in the event the Government decides to issue a Request for Proposal. 20. SUBMISSIONS OF RESPONSES There is a recommended total page count limit of 6 pages for topic response. This page count does not include the coversheet. The page limitation to the RFI is intended to minimize the effort of the respondent. Responses to the RFI should be submitted in MS Word format in 12-point font, double-spaced with one-inch margins and use the standard letter size (8.5�x11�) paper. Responses are due no later than 25 FEB 25. Responses to all or part of this RFI will be accepted. Responses to this RFI must be submitted to AFRL. Responders shall provide one electronic copy (MS Word or editable PDF) of their unclassified response via DoD SAFE (https://safe.apps.mil/). NOTE: See Paragraph 6 for the instructions DoD SAFE submittal(s). DO NOT send via