Loren Data's SAM Daily™

FBO DAILY - FEDBIZOPPS ISSUE OF OCTOBER 06, 2013 FBO #4334
DOCUMENT

R -- TAC-14-10846 Enterprise Software Asset Management (ESAM) - Attachment

Notice Date

10/4/2013
 

Notice Type

Attachment
 

NAICS

541519 — Other Computer Related Services
 

Contracting Office

Department of Veterans Affairs;Technology Acquisition Center;260 Industrial Way West;Eatontown NJ 07724
 

ZIP Code

07724
 

Solicitation Number

VA11813I0643
 

Archive Date

12/3/2013
 

Point of Contact

Kimberly Flynn
 

E-Mail Address

8-5442<br
 

Small Business Set-Aside

N/A
 

Description

Questions & Answers on VA118-13-I-0643 1.Regarding VA current SCCM 2007 enterprise implementation, does VA currently use SCCM for the following functionality? SCCM functionality currently in useWindows Workstations (Y/N)Windows servers (Y/N)Apple Workstations (Y/N)Unix/Linux Servers (Y/N) SCCM Discovery of installed softwareYYNN SCCM Software CatalogYYNN SCCM Software DistributionYNN SCCM Software Metering *YNN *We are currently monitoring 36 applications and are adding more based on requirements. We estimate the ceiling to be approximately 200 products. 2.If VA has not yet implemented any of the above SCCM features, can we assume that VA has plans to deploy these capabilities in the future or would VA like to have vendor proposed solution for any gap identified above? There is no current funded project for SCCM 2012 in which non windows capabilities could be deployed. VA does not have preference regarding how requirements are met at this time. VA is conducting market research to assess the commercial space as it relates to current VA requirements and enterprise state. 3.Is VA looking for an asset inventory and distribution tool? There are several requirements that call out the need for this (example see #'s 5 (software distribution), 14 (software deployment), 17 (software media library), 24 (discovery will identify virtual or physical), 25, 30 (metering is typically a function of discovery solutions), 31 (discovery technology removes the software), 32, 35 (removal of temporary software)). We understand that SCCM, Tivoli Endpoint Manager, and BDNA may be in place and could be used to fulfill these requirements. VA is looking for an Enterprise Software Asset Management solution as described in the requirements, including inventory and distribution for software to the extent described in the requirements. Hardware assets are not targeted under this effort. Existing tools deployed in the VA enterprise may be leveraged to the extent as delineated in the RFI. BDNA discovery is not deployed throughout the VA enterprise. 4.It is unclear whether VA currently owns a Discovery tool that they are looking to augment or whether the bidders will need to supply a Discovery tool as part of the final solution. Please clarify. VA does not have preference regarding how requirements are met. VA is conducting market research to assess the commercial space as it relates to current VA requirements. Requirements include discovery. 5.Is VA looking for a Catalog tool? There are several requirements that call out the need for a request portal (example see #'s 13, 36, 37, 38, 39). Yes, as part of the solution - to the extent such is described in the requirements. 6.Are there any request and approval portals in place or would you be looking for a solution here? No request and approval portals are currently in place for software across the enterprise. 7.Does VA have an ownership repository that tracks the purchases of hardware? This repository would track the procurement and lifecycle status of hardware assets which would be needed to accurately assess compliance. If yes, can you describe how this is accomplished? ESAM is a software asset management project, not hardware. 8.Design Constraints Specifications: The solution software and hardware shall comply with the One VA Technical Reference Model (TRM) and the Enterprise Technical Architecture Compliance Criteria. Please explain the "One VA Technical Reference Model (TRM) and the Enterprise Technical Architecture Compliance Criteria." Links to the TRM and ETACC: One VA Technical Reference Model (TRM) Enterprise Technical Architecture Compliance Criteria 9.Bring Your Own Endpoint (BYOD): The solution shall support meet the requirement defined herein for BYOD regardless of how the license is structured, i.e. (a) concurrent, (b) endpoint based, (c) named user, etc. Please respond below for each separately. Please explain "requirement defined herein for BYOD" BYOD devices have license requirements depending on how they connect to the network and who connects. Therefore the need to manage these licenses as well. Are these endpoints all mobile devices or are users bringing their own workstations? A BYOD can be a wireless device laptop, desktop or any approved device that connects to the VA network and provided by the employee. A home personnel computer used to connect to the VA network via the Citrix access gateway is an example of a non-wireless BYOD. These devices have license requirements as well depending on how they connect. Does the VA already possess any technology for Mobile Device Management? Yes, VA uses Airwatch for Mobile device management 10.Software Titles: The solution shall meet the requirements herein for software applications from all major software vendors. The following vendors shall be supported in the initial phase of the project: (a) Microsoft, (b) Oracle, (c) VMware, (d) Red Hat, (e) Citrix, and (f) Adobe. (Please respond below to each separately). Please explain "requirements herein for software applications from all major software vendors" Clearly other vendors will be required in future phases. VA anticipates a phased approach to implementing the solution, applying the Software Asset Management solution to these vendors first and then expanding to all vendors and software titles.
 

Web Link

FBO.gov Permalink
(https://www.fbo.gov/notices/900dfffb278262bdf2d13520c8906452)
 

Document(s)

Attachment
 

File Name: VA118-13-I-0643 VA118-13-I-0643_1.docx (https://www.vendorportal.ecms.va.gov/FBODocumentServer/DocumentServer.aspx?DocumentId=1037761&FileName=VA118-13-I-0643-002.docx)

Link: https://www.vendorportal.ecms.va.gov/FBODocumentServer/DocumentServer.aspx?DocumentId=1037761&FileName=VA118-13-I-0643-002.docx

 

Note: If links are broken, refer to Point of Contact above or contact the FBO Help Desk at 877-472-3779.
 

Record

SN03211853-W 20131006/131004233947-900dfffb278262bdf2d13520c8906452 (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 |