SPECIAL NOTICE
99 -- Request For Information for HyperVisor
- Notice Date
- 4/20/2020 11:30:05 AM
- Notice Type
- Special Notice
- NAICS
- 541715
— Research and Development in the Physical, Engineering, and Life Sciences (except Nanotechnology and Biotechnology)
- Contracting Office
- ACC WRN
- ZIP Code
- 00000
- Response Due
- 6/5/2020 1:00:00 PM
- Archive Date
- 06/20/2020
- Point of Contact
- Doris Lemcool
- E-Mail Address
-
doris.p.lemcool.civ@mail.mil
(doris.p.lemcool.civ@mail.mil)
- Description
- Part I. Description of Intent: The Army Contracting Command-Detroit Arsenal, in conjunction with US Army�s Combat Capabilities Development Command (CCDC), Ground Vehicle System Center (GVSC), Ground System Cyber Engineering (GSCE) is issuing a Request for Information (RFI) for the procurement of a Hypervisor. The objective of the RFI is to better understand the availability and capabilities of products and the potential of the manufacturers. The information gathered by the Army through this RFI, along with other market investigation data, is solely intended for use by the U.S. Army and will not be shared with any company. Participation in this RFI provides an important opportunity to influence the Army�s approach to procuring the Hypervisor. � The U.S. Government is in no way liable to pay for or reimburse any companies or entities that respond to this announcement. Any costs incurred by interested companies in response to this announcement will NOT be reimbursed. This is a RFI ONLY and is not a solicitation for proposals; therefore, no questions will be taken at this time. A prototype project will not be awarded in response to this announcement. RESPONSE TIME: We thank you in advance, for your time and participation in this RFI.� The U.S. Government requires all responses be returned by 4:00 pm, 05 June 2020 to Doris Lemcool at doris.p.lemcool.civ@mail.mil. � � PART 1.� BUSINESS INFORMATION: Please provide the following Administrative information as the first section of your submission. Manufacturer Company Name (and any former names): Traditional or Non-Traditional Contractor:����������� *Non-Traditional Contractor: An entity that is not currently performing and has not performed, for at least the one-year period preceding the solicitation of sources by DoD for the procurement or transaction, any contract or subcontract for the DoD that is subject to full coverage under the cost accounting standards prescribed pursuant to section 1502 of title 41 and the regulations implementing such section (see 10 U.S.C. 2302(9)).���������� �������������3. �Mailing Address:� ����� ���� 2. Personnel Responding to this Survey ��������a. Name: ����� � b.Title: ��������c.Company Responsibility/Position: ������� d. Telephone/Fax Numbers: ������� e. E-mail address: PART 2. TECHNICAL QUESTIONNAIRE: Introduction/Background: Current US Army Ground Combat vehicles make use of over 70 microelectronic components, which have their own operating systems/runtimes and physical space requirements. While some components perform similar functions, each component is essential for the full mission capability of the vehicle. Thus, it is critical that if any of these components fail for reasons external or internal to the vehicle and its systems that the faulty component(s) can be replaced in the least amount of time possible. The Cybersecurity Technology Development team has determined that one such way to do this is to examine the feasibility of using virtualization technology suitable for ground combat vehicular components. GSCE is seeking DATCE members� solutions that will allow the DoD to: 1) combine onboard or similar services, 2) offer near real-time instantiation of a backup operating system, and 3) provide improved partitioning of safety critical signaling and standard control signaling. Have you developed a hypervisor with the intended purpose to be used on any commercial or US Army Ground Combat vehicle? What is the anticipated method for updating the hypervisor after it has been integrated into fielded systems? What is the current Technology Readiness Level (TRL) of the hypervisor technology? What encryption methods and technologies are supported by the hypervisor? Have you integrated the hypervisor onto any commercial or US Army Ground Combat vehicle? If so, what were the impacts to the systems? Does the hypervisor support the simultaneous execution of multiple Operating System (OS) varieties and architectures? How many distinct instances can it support at the same time? What type of virtualization technology does it use?
- Web Link
-
SAM.gov Permalink
(https://beta.sam.gov/opp/bac0790dfe944aa49d7314eb686c0e69/view)
- Place of Performance
- Address: USA
- Country: USA
- Country: USA
- Record
- SN05626072-F 20200422/200420230141 (samdaily.us)
- Source
-
SAM.gov Link to This Notice
(may not be valid after Archive Date)
| FSG Index | This Issue's Index | Today's SAM Daily Index Page |