The file's text, extracted by GovTribe without its formatting.
EUHW LATE RFP QUESTIONS RECEIVED ON 12/21/2018 and 1/8/2019
RESPONSES POSTED TO INDUSTRY ON 1/9/2019
| Question # |
| Government File Name/ Section Number |
| Questions |
| RESPONSE |
| 1 |
| EUHW Attch 1 EUHW PWS_v5 14Dec2018 Final; EUHW Attch 10 EUHW Device Specifications v6; |
PWS Section: 3.2.3.1.7; Attch 10, Technical Threshold Tab, Rows 3, 9, 10, 13 Current commercially available PCoIP Zero Clients are based on Teradici Tera Chipsets, do not have general purpose CPUs with multiple cores, have minimal RAM (512MB) since they do not run an operating system and do not support USB 3.0. The Government’s current firmware-based PCoIP Zero Client requirements for a dual core processor, 1 USB 3.0 port and 2 GB of memory are not commercially available and preclude all vendors from offering a commercially available solution. Request the Government consider listing corresponding TERA 2321 PCOIP Zero Client processor, 512 MB of memory, and USB 2.0 only, removing the requirement for USB 3.0 in an amended Attch 10 document, to allow compliant solutions to be bid, as listed in table below. Table items highlighted below are suggested changes.
| CONFIGURATION |
| Zero Client (PCoIP) - Firmware Based |
| Processor |
| Tera 2321 Processor |
Cores/Threads
Base/Boost Clock Speed GHz
TDP (maximum accepted) vPro
Cache
| Universal Serial Bus (USB) Ports (all types) |
| 4 |
| High-end USB Ports (3.0 or C) |
| 0 |
An amendment to the RFP will update the Zero Client requirement from “Zero Client” to “Zero/Thin Client.” Attachment 1 (PWS) and Attachment 10 (Device Specifications) will update Zero/Thin Client requirements. The suggested changes to the Processor and USB recommendations were not taken, as market research has found several Zero/Thin Client devices from several manufacturers that meet or exceed the thresholds.
| 2 |
| EUHW Attch 1 EUHW PWS_v5 14Dec2018 Final; EUHW Attch 10 EUHW Device Specifications v6; |
PWS Section: 3.2.3.1.7; Attch 10, Technical Threshold Tab, Rows 2, 9, 11
There is no Zero Client (ICA) firmware-based device on the market. PWS 3.2.3.1.7 defines Zero Client as “a lightweight computing device (firmware based) developed for remote connection”. Based on current commercially available information, Citrix Receiver (ICA), as specified in Attch 10 is not supported in firmware and requires either a Linux or Windows Operating System. There is no Teradici ICA Receiver on the market, meaning that ICA is not a Zero Client device and should be referred to as a thin client.
We request the Government remove the “firmware-based” requirement from Zero Client (ICA) category in an amended PWS document, to allow vendors to propose a valid solution and rename the Zero Client (ICA) category to Thin Client (ICA), since there are no Zero Client (ICA) products on the market. In addition, request the Government specify the storage required for the Zero Client (ICA) based upon the required operating system, which has not yet been specified for this category, whether it be Linux or Windows. Only a single operating system can be loaded on the Thin Client (ICA) from the vendor, therefore, vendors require the Government’s guidance on the required operating system, to avoid assumptions. If the Government’s intent is to have a Windows and a Linux option, please consider adding an additional Thin Client (ICA) category, with specifications listed accordingly for each required operating system, Linux and Windows. Please reference table below for potential changes highlighted in yellow.
| CONFIGURATION |
| Thin Client (ICA) - Not Firmware Based |
| Processor |
| Dual Core processor 1.2 GHz |
supporting ICA; Linux or Windows
Cores/Threads
Base/Boost Clock Speed GHz
TDP (maximum accepted) vPro
Cache
| Memory |
| TBD, based on Linux or Windows specs |
| Can support up to |
| TBD, based on Linux or Windows specs |
| Storage |
| TBD, based on Linux or Windows specs |
| Universal Serial Bus (USB) Ports (all types) |
| 4 |
| High-end USB Ports (3.0 or C) |
| 1 |
An amendment to the RFP will update the Zero Client requirement from “Zero Client” to “Zero/Thin Client.” Attachment 1 (PWS) and Attachment 10 (Device Specifications) will update Zero/Thin Client requirements. The Government’s market research has identified multiple Zero/Thin Client devices from several manufacturers that meet or exceed the thresholds.
| 3 |
| EUHW Attch 1 EUHW PWS_v5.0 14Dec2018 Final; |
PWS section 3.2.2.3
| Please clarify whether the Peripheral Full Bundle specified in EUHW Attch 1 PWS_v5 FINAL Section 3.2.2.3 Peripherals, Table 3.2.2 needs to ship with Zero Client devices. The Peripheral Full Bundle in Table 3.2.2 includes a monitor w/power cord, keyboard, mouse, and network cable. The Government’s response to Question 62 in the Q&A from 11/2/18 states that “the Zero/Thin Client includes two (2) display monitors as stipulated within the specifications.” Consequently, if a Peripheral Full Bundle ships with a Zero Client, the Government would receive three (3) displays; the two (2) that ship with the Zero Client and the one (1) that ships in the peripheral bundle. Does the Government require a keyboard, mouse and network cable for Zero Clients? If so, it is requested the Government specify which peripherals need to be included for Zero Clients or specify a new Zero Client Peripheral Full Bundle. |
| The device specifications found in Attachment 10, were updated for the Zero/Thin Client. In accordance with Attachment 10, Device Specifications, the Zero/Thin Client must support dual monitors. The orderable Zero/Thin Client SLINs (x001AF, x0001AG, x002AF, and x002AG) do not include the two monitors. |
The full peripheral bundle is ordered separately from the EUHW device.
| 4 |
| EUHW Attch L-1, Price Workbook_v4; Attch 10 EUHW Device Specifications v6; |
Row 41, Row 11
| The technical specifications listed in EUHW Attch 10 EUHW Device Specifications REV6 specify a range of hard drives from 256GB through 2TB SSD, which have significant cost differences. There is only a single input area for the deployable seat uplift in EUHW Attch L-1, EUHW Price Workbook-v4. Please provide guidance on whether vendors should provide a minimum, average or maximum price for CLIN 0003AA based on specified quantities. |
| An amendment to the RFP will update the Deployables CLIN x003 structure, Attachment L-1, Pricing Workbook, and Attachment 1, PWS section 3 to address this issue. |
| 5 |
| EUHW Attch L-1, Price Workbook_v4; |
Row 66
| EUHW Attch L-1, EUHW Price Workbook _v4, CLIN 0007AC – Removal of Wireless (Wi-Fi): Please define, with CLINs, which Hardware Categories require Removal of Wireless LAN. In the EUHW Attch L-1, EUHW Price Workbook_V2 dated 11/5/18, CLIN 0007AC specified Removal of Desktop Wireless (Wi-Fi), which implied removal of Wi-Fi from desktops only. Should vendors assume that Wi-Fi now needs to be removed from all devices? |
| An amendment to the RFP will update Attachment 10, Device Specifications, Common HW REQs tab. CLIN x007AC is applicable to all computers excluding Zero/Thin Client devices. |
| 6 |
| Attch 10 EUHW Device Specifications v6; |
Rows 4-6 Based on commercially available information, by requiring a 7th Generation processor in combination with other technical specifications for the Rugged Laptop, it is our understanding the Government has eliminated all viable solutions. Those that have transitioned to the 8th Generation no longer offer compliant 7th Generation processors. It is therefore requested that the Government allow flexibility to offer either 7th or 8th generation processors by specifying corresponding Cores/Threads, Base/Boost Clock Speed GHz, TDP, vPro, and Cache for both processor generations on the Rugged Laptop category.
An amendment to the RFP updated Attachment 10 (Device Specifications) for the Rugged Laptop and Rugged Tablet. Specifications for the Base/Boost Clock Speed GHz for the Rugged Laptop have been updated to 1.7/2.9 and Base/Boost Clock Speed GHz for the Rugged Tablet have been updated to 1.7/3.5.
| 7 |
| Attch 10 EUHW Device Specifications v6; |
Rows 4-6 Based on commercially available information, 2-in-1 Detachable devices are long life cycle products and various vendors offer either 7th or 8th Generation processors. Those that have transitioned to the 8th Generation no longer offer compliant 7th Generation processors. As such, it is requested the Government allow flexibility to offer either 7th or 8th Generation processors and insert the table below in Attch 10, 2-in-1 Detachable Category:
Base/Boost/Clock Speed GHz
| TDP (maximum accepted) |
| 45W |
| 45W |
Furthermore, there appears to be only one compliant device on the market in the 2-in-1 Detachable category. It is requested the Government also consider allowing a 360° convertible hinge device to allow the Government more options. A 360° hinge allows the device to flip and fold into notebook, stand, tent, and tablet modes and still falls below the Government's specified maximum weight requirement.
The Base/Boost Clock Speed GHz specifications found in Attachment 10 for the 2-in-1 Detachable will remain unchanged at 1.7/3.6.
The government will not consider allowing a 360° convertible hinge device for the 2-in-1 Detachable category.
| 8 |
| Attch 10 EUHW Device Specifications v6; |
Technical Thresholds tab, Rows 12 and 13
| New requirements were added in Rows 12 and 13 of Attch 10 for “Universal Serial Bus (USB) Ports (all types)” and “High-end USB Ports (3.0 or C)”, with corresponding numbers of ports for each requirement. Is the Government’s intent to require vendors to offer an either/or USB port solution or are both specifications required? If both are required, several categories will become non-compliant, because the total USB port requirement exceeds what can be provided in the industry on various Attch 10 Technical Threshold categories. Request the Government specify the USB Port requirements as either/or specifications. |
| There were no new requirements added to the USB Ports. The additional row was intended to provide clarification. |
The following is an explanation on the appropriate way to interpret the USB requirements:
Attachment 10, General Purpose Desktop, Column B,
| Universal Serial Bus (USB) Ports (all types) |
| 6 |
| High-end USB Ports (3.0 or C) |
| 3 |
A total of six (6) USB ports is the minimum threshold required. Out of the 6 USB ports total, a minimum of three (3) must be “High-end” USB ports (3.0 or C).
| 9 |
| EUHW N00039-18-R 0004 Amd 0006 MOD dtd 14DEC2018 PG 4; |
SUBCLIN 1007AF
SUBCLIN 1007AF specifies that the Contractor shall provide and install a Federal Information Processing Standard (FIPS) compliant internal ST-Type Connector 100/1000 MB Peripheral Component Interconnect Express (PCI-e) Fiber Network Interface Card (NIC) into the EUHW. A 100/1000 MB Fiber NIC does not exist in the industry. Fiber NICs do not auto-negotiate between 100 and 1000 Mbps speeds and are instead fixed speeds of either 100 Mbps or 1000 Mbps. It is recommended that the Government specify four different CLINs for Fiber NICs if the Government requires both 100 Mbps and 1000 Mbps Fiber NICs. The four CLINs would be identified as listed in the following table:
An amendment to the RFP will update the Fiber NIC requirement.
PWS section 3.2.6 a. i. EUHWaaS Deployable Computing
PWS section 3.2.6 a. i. EUHWaaS Deployable Computing states "Five percent (5%) whole unit (i.e., additional EUHWaaS devices) and five percent (5%) replacement device storage (i.e., replacement internal storage) of total deployed hardware devices (fractional percentages will be rounded up to the next whole number) with a minimum of one (1) each." Will the Government define what EUHWaaS device categories are included in Deployable Kits? Will the Government provide additional CLINs to allow the Contractor to provide a price per category of device?
An amendment to the RFP will update the Deployable Seat Uplift requirement, including the PWS, Attachment 1, section 3.2.6, EUHWaaS Deployable Computing. PWS section 3.2.6.a.i will be removed.
| PWS section 3.2.6 c. states "Deliver imaged replacement devices and repair parts to the requesting location." Will the Government define what type of repair parts are needed and the quantity percentage? Is this separate from the PUK or can a new CLIN be identified for each category where it is required? |
| An amendment to the RFP will update the Deployable Seat Uplift requirement, including the PWS, Attachment 1, section 3.2.6, EUHWaaS Deployable Computing. |
| 12 |
| N00039-18-R-0004 FINAL 17SEP2018 (1) |
| The N00039-18-R-0004 FINAL 17SEP2018 (1).docx specifies in CLIN 0007AE that “The Contractor shall provide and install a Federal Information Processing Standard (FIPS) compliant internal Fiber Network Interface Card (NIC) into the EUHW.” Will the Government define which desktop categories require CLIN 0007AF and 0007AG in EUHW Attachment L-1, EUHW Price Workbook FINAL (1) (QTY).xlsx document.? Will the Government exclude the Ultra-Small Desktop from this requirement due to the limited size of the form factor? |
| In accordance with Attachment 10, Device Specifications, the Fiber NIC requirement does not apply to the Ultra-Small Desktop. However, offerors are not precluded from offering an Ultra-Small Desktop that includes a Fiber NIC. |
| 13 |
| Attachment 6, EUHW Navy Site Listing; |
ONE-Net Sites (OCONUS)
| Since Diego Garcia does not accept commercial traffic, will the Government modify the ONE-NET Sites (OCONUS) delivery service level and the delivery location for military transport to Diego Garcia within Attachment 6, EUHW Navy Site Listing? |
| There is no change to the requirement at this time. The Government will determine and/or develop a mechanism to ensure the EUHW contractor is capable of delivering the hardware to Diego Garcia. |
| 14 |
| Attachment 1: Performance Work Statement (PWS) |
| To achieve the most cost-effective tagging solution, will the Government please identify the CLIN (if different) and specific material requirements for Asset tags for Navy and Marine Corps? |
| The Government does not intend to have a separate CLIN for tagging. The requirements for the asset tags are found in the PWS section 3.4.4 and Appendix A (MIL-STD-130N), and Attachment 16, USMC Logistics Asset Data Attributes. |