Questions and Answers N0018926QL146.pdf
PDF 146 KB Posted
- Solicitation number
- N0018926QL146
About this file
This is a Questions and Answers document for federal contract N0018926QL146 issued by NAVOCEANO (Naval Oceanographic Office).
The document clarifies four key requirements from the solicitation. Regarding laptop Bluetooth restrictions referenced in Section 1.10 of the SOW, hardware-level BIOS disablement of the Bluetooth chip is acceptable as long as the capability cannot be re-enabled; physical removal is not required. For software licensing in Section 2.0.10, contractors must factor a multi-year subscription tier directly into their base quote rather than proposing traditional perpetual licenses with annual maintenance options. Documentation for "or equal" software components need only comply with standard developer API and SDK reference manuals per Section 2.0.7; no specific preferred layout is required for communications protocol documentation. The document resolves a timeline conflict by confirming the required delivery date is sixty (60) days after contract award, superseding the nine-month timeline referenced elsewhere in the PWS.
View the file
Other files
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
N0018926QL146
Questions and Answers
Question 1: Laptop Bluetooth Restrictions (Section 1.10): The SOW notes that "NO TWO-WAY
BLUETOOTH IS PERMITTED" on the dedicated laptops. To ensure absolute compliance, is a hardware-level BIOS disablement of the Bluetooth chip acceptable, or does the command require the physical removal of the internal wireless card?
Answer 1: As long as Bluetooth can't be reenabled, disablement of the chip is acceptable.
Question 2: Software Licensing (Section 2.0.10): The requirement mentions providing a price list for software license maintenance. Is NAVOCEANO anticipating a traditional perpetual license model with annual maintenance options, or should we factor a multi-year subscription tier directly into our base quote?
Answer 2: Please factor a multi-year subscription tier into the quote.
Question 3: Documentation Format (Section 2.0.7): For any "or equal" software components, is there a specific preferred layout for the communications protocol documentation, or will standard developer API/SDK reference manuals suffice?
Answer 3: Standard developer reference manuals will suffice.
Question 4: Please confirm the required delivery timeline for the subject requirement at your earliest convenience. It was noticed that there are 2 different timelines listed in the PWS, sixty (60) days is listed in 1.2 while nine (9) months is listed in 3.1. Thank you.
Answer 4: The required delivery date is sixty (60) days after award.
File details come from the government source that posted it. Updated .