DOCUMENT
D -- RFI - Enterprise Mobile Device Services (MDS) - Attachment
- Notice Date
- 8/21/2018
- Notice Type
- Attachment
- NAICS
- 541512
— Computer Systems Design Services
- Contracting Office
- Department of Veterans Affairs;Technology Acquisition Center;23 Christopher Way;Eatontown NJ 07724
- ZIP Code
- 07724
- Solicitation Number
- 36C10B18Q3113
- Response Due
- 8/24/2018
- Archive Date
- 9/23/2018
- Point of Contact
- George Govich, george.govich@va.gov
- E-Mail Address
-
george.govich@va.gov
(george.govich@va.gov)
- Small Business Set-Aside
- N/A
- Description
- This modification is to post the Q&A. Question/Comment Government Response 1. We have reviewed the requirements and would like to suggest adding a provision in your final solicitation (i.e., PWS, Section H) that speaks to ongoing security compliance, such as, An offeror shall identify in its proposal, quote, bid or any resulting contract, their strategy for ensuring policy compliance with the May 11, 2017 Executive Order 13800, Strengthening the Cybersecurity of Federal Networks and Critical Infrastructure. The compliance strategy shall conform to cybersecurity risk management best practices set forth in the National Institute of Standards and Technology (NIST) Framework for Improving Critical Infrastructure Cybersecurity and National Checklist Program (NCP), defined by the NIST SP 800-70. All products shall adhere to the organization s system configuration standards for all types of system components and verify the system configuration standards are consistent with industry accepted hardening standards, including, SysAdmin Audit Network Security (SANS), NIST, and the Center for Internet Security (CIS). Our experience is that much of the overarching policy leaves a gap in the requirements for compliance at the solution level and stating this as an overt compliance may preclude the potential for change (FAR 43) and Requests for Equitable Adjustments (REAs) as security requirements continue to evolve in light of the current environment. We do not see this as a major cost driver, but it is a strong mitigation measure over the life cycle of the solution. Thank you for your consideration. Government will take recommendation into consideration. 2. I am hoping to find out if the subject effort is a new requirement or a follow-on to an existing contract? If the latter, can I please find out the incumbent contractor's name and contract number? I appreciate your time and help. This is a new effort for total lifecycle management. There is no current vendor doing this effort. 3. The RFI states this is a DAAS contract but does not specify if the Offeror is responsible for procuring and providing the devices. Please confirm if procurement of equipment is included in the scope. Yes the device procurement is a component of the total solution. The offeror will take over management of the existing devices as well as procure the new devices 4. Please confirm if devices are to be provisioned at the contractor s facility and shipped to each VA office, performed at a central VA location, or are if the VA expects to have contractor personnel on-site at various locations to perform provisioning. The VA is looking for the contractor to be able to have devices available in a short timeframe at any of the facilities. The VA is open to multiple approaches that meet the customer support timelines as well as total cost savings to the VA. The VA is not set into a single solution model for provisioning, but the contractor will be doing the provisioning for the VA. 5. If available, please provide insight on what the current provisioning process is, how long it takes to provision a device with the current device configuration and if there are any specific security settings or app configurations that would need to be included in the provisioning setup. Currently we provision devices into an EMM using either token-based enrollment or DEP enrollment. The configuration must meet the DISA STIG. 6. Are your current devices Government furnished, BYOD, or mixed? Will this device ownership change as your mobile fleet expands? Current devices are Government furnished. This will not change. 7. Aside from policies managed through the EMM, does the deployment currently consist of any additional endpoint security? Currently the mobility deployment also has a third party MTP / MTD solution to layer in additional visibility and security compliance policies for mobile devices. 8. What types of devices compose the 100 unique function devices and what are their uses? As part of the requirements, the Offeror would be managing VHA telehealth devices running android would be part of requirement. 9. What mission-critical applications would the devices need to be provisioned with? All applications should be managed by the EMM, and the VA would work with the vendor to upload and manage these applications with the selected EMM product.
- Web Link
-
FBO.gov Permalink
(https://www.fbo.gov/notices/b5950a0981fcf13dadcb5458df87e688)
- Document(s)
- Attachment
- File Name: 36C10B18Q3113 36C10B18Q3113_1.docx (https://www.vendorportal.ecms.va.gov/FBODocumentServer/DocumentServer.aspx?DocumentId=4552883&FileName=36C10B18Q3113-001.docx)
- Link: https://www.vendorportal.ecms.va.gov/FBODocumentServer/DocumentServer.aspx?DocumentId=4552883&FileName=36C10B18Q3113-001.docx
- Note: If links are broken, refer to Point of Contact above or contact the FBO Help Desk at 877-472-3779.
- Record
- SN05048674-W 20180823/180821231538-b5950a0981fcf13dadcb5458df87e688 (fbodaily.com)
- Source
-
FedBizOpps Link to This Notice
(may not be valid after Archive Date)
| FSG Index | This Issue's Index | Today's FBO Daily Index Page |