Loren Data's SAM Daily™

FBO DAILY - FEDBIZOPPS ISSUE OF DECEMBER 23, 2016 FBO #5509
DOCUMENT

R -- Cloud Infrastructure and Management - Attachment

Notice Date

12/21/2016
 

Notice Type

Attachment
 

NAICS

541519 — Other Computer Related Services
 

Contracting Office

Department of Veterans Affairs;Technology Acquisition Center;23 Christopher Way;Eatontown NJ 07724
 

ZIP Code

07724
 

Solicitation Number

VA11817R1821
 

Response Due

1/6/2017
 

Archive Date

3/7/2017
 

Point of Contact

Joseph Pignataro
 

E-Mail Address

5-1115<br
 

Small Business Set-Aside

N/A
 

Description

Department of Veterans Affairs (VA) Cloud Infrastructure and Management Request for Information (RFI) 1.0 RFI Details This is a Request for Information (RFI) only. Do not submit a proposal. This RFI is for planning purposes only and shall not be considered an Invitation for Bid, Request for Task Execution Plan, Request for Quotation or a Request for Proposal. Additionally, there is no obligation on the part of the Government to acquire any products or services described in this RFI. Your response to this RFI will be treated only as information for the Government to consider. It is requested that all companies interested in participating in this effort please note their interest and submit a capability statement demonstrating their ability to meet this requirement. The page limit for RFI responses is 15 pages. Also, as part of your RFI response, please include a Rough Order of Magnitude (ROM) Price for Government estimating purposes. Please note the business size for North American Industry Classification System (NAICS) Code and indicate if you are a Service-Disabled Veteran-Owned Small Business (SDVOSB) or a Veteran-Owned Small Business (VOSB). You will not be entitled to payment for direct or indirect costs that you incur in responding to this RFI. This request does not constitute a solicitation for proposals or the authority to enter into negotiations to award a contract. No funds have been authorized, appropriated or received for this effort. The information provided may be used by the VA in developing its acquisition strategy. Interested parties are responsible for adequately marking proprietary, restricted or competition sensitive information contained in their response. The Government does not intend to pay for the information submitted in response to this RFI. For SDVOSB/VOSB firms, indicate whether at least 50% of the cost of performance incurred is planned to be expended for employees of your concern or employees of other eligible SDVOSB/VOSB firms.   Indicate whether at least 50% of the cost of performance incurred is planned to be expended for employees of your concern or employees of all other small business firms. Main POCs: Joe Pignataro, Contract Specialist Joseph.Pignataro@va.gov, 732-795-1115, Kevin Monahan, Contracting Officer- Kevin.Monahan@va.gov, 732-440-9695. Please submit your responses through email to the Contract Specialist and Contracting Officer at Joseph.Pignataro@va.gov and Kevin.Monahan@va.gov. Responses must be received by 12:00PM, NOON, EST on January 6, 2017. 2.0 Background: The Department of Veterans Affairs (VA) Office of Information and Technology (OI&T) Information Technology Operations and Services (ITOPS), Infrastructure Operations (IO) operates and maintains a complex and fast paced Information Technology (IT) environment in a number of Government and commercial data centers. IO requires the ability to rapidly respond to the dynamically changing IT requirements of its customers which include OI&T, Veterans Health Administration (VHA), Veterans Benefits Administration (VBA), and National Cemetery Administration (NCA), and Other Government Agencies (OGA). In FY12, IO delivered a private cloud deployment as part of its fee-for-service franchise fund service catalog. Based on commodity hardware and VMware software to create virtual server environments, the offering aligns with the National Institute of Standards and Technology (NIST) Infrastructure-as-a-Service (IaaS) service model. This IO private cloud IaaS currently supports 2,000 Virtual Machines (VM) on 1PB of storage, 195kGHz CPU, and 48TB Random Access Memory (RAM) using VMWare and Microsoft hypervisor technology. IO hosts this IaaS at VA s Austin Information Technology Center (AITC) and Philadelphia Information Technology Center (PITC). Table 1: Parameter Value Current Number of Cloud Virtual Machines 2000 Current Cloud CPU Capacity 195000 GHz Current Cloud RAM Capacity 48 TB Current Cloud Storage Capacity 1 PB Operating Systems Windows 2008-2012 R2, Red Hat Linux Hypervisors VMware vSphere Enterprise Plus, Microsoft Hyper-V IT Service Management (ITSM) Configuration Management Database (CMDB Software CA Service Manager ITSM Help Desk Software CA Service Manager Networking Cisco N1000V, Cisco ACI, F5, Riverbed Database Software Microsoft SQL, Oracle, MongoDB Deployment Data Centers Locations Austin ITC (TX), Philadelphia ITC (PA), Hines ITC (IL) In order to meet the growing needs of its customers and efficiently and effectively utilize its IT resources (network infrastructure, servers, etc.), IO intends to implement an enterprise-class, geographically diverse, Hybrid Cloud solution that offers essential cloud characteristics such as on-demand self-service, resource pooling, rapid elasticity, and measured service. Some of the Hybrid Cloud service models to be integrated include Infrastructure as-a Service (IaaS), Platform-as-a-Service (PaaS), Database-as-a-Service (DBaaS), and Software-as-a-Service (SaaS) service models. This Hybrid Cloud infrastructure will permit VA customers to self-provision resources, etc. VA IT administrators will be able to monitor customer utilization, analyze trends, and effectively plan IT resource expansion. The Hybrid Cloud may be deployed to more than one geographically dispersed VA Information Technology Center. The Hybrid Cloud will also have the ability to connect VA s current IO Cloud and to multiple VA-approved Cloud Service Providers (CSPs) including other government agencies and commercial entities such as Microsoft Azure, Amazon Web Services (AWS), or other FISMA high or moderate environments. To achieve this objective, VA may require the following onsite capabilities: Cloud Management Platform (CMP) Converged/Hyper-converged Cloud Infrastructure Managed Services for a Cloud Infrastructure VA is considering a variety of implementation options to include but not limited to the following possible approaches to acquiring and managing these new functionalities. VA will also consider alternate implementation approaches. CMP On-Premise Software Only Vendor shall provide, install, and test the CMP and provide all licenses and documentation. Cloud infrastructure hardware and hardware installation will be provided VA. VA service lines will manage the system. Converged/Hyper-converged Infrastructure Only Vendor shall provide, install, and test the Converged/Hyper-converged Infrastructure and provide all licenses and documentation. VA will supply the CMP solution. VA service lines will manage the system. Converged/Hyper-converged Infrastructure and CMP: Vendor shall provide, install, and test the CMP and Converged/Hyper-converged Infrastructure and provide all licenses and documentation. The vendor shall also provide integration with existing infrastructure. VA service lines will manage the system. Converged/Hyper-converged Infrastructure, CMP, and Managed Services for a Cloud Infrastructure: Vendor shall provide, install, and test the CMP and Converged/Hyper-converged Infrastructure and provide all licenses and documentation. The vendor shall also provide integration with existing infrastructure. The vendor shall provide managed services to include operations, maintenance, support services, and full lifecycle management of the solution. 3.0 Technical Requirements: The detailed technical requirements for the CMP, Converged/Hyper-converged Infrastructure, and associated Managed Services capabilities are listed below. VA expects the vendors to provide configuration/implementation services, training, and help desk services to support each of these three capabilities. 3.1 CMP: The CMP solution shall provide the capability to dynamically monitor system usage and incorporate processes that allow for the full resiliency of a cloud solution. The solution shall be scalable on an enterprise level to multiple geographically diverse data centers, and may consist of one or more tools/components. Gartner defines Cloud Management Platforms as integrated products that provide for the management of public, private and hybrid cloud environments. The minimum requirements to be included in this category are products that incorporate self-service interfaces, provision system images, enable metering and billing, and provide for some degree of workload optimization through established policies. More-advanced offerings may also integrate with external enterprise management systems, include service catalogs, support the configuration of storage and network resources, allow for enhanced resource management via service governors and provide advanced monitoring for improved guest performance and availability. Specifically, VA anticipates that the CMP solution will include many or all of the following key capabilities: On-demand self-service. Broad network access. Resources pooled to serve multiple consumers using a multi-tenant model. Rapid elasticity. Measured service. Automatic provisioning of computing capabilities. Consumable by heterogeneous thin or thick client platforms (e.g., mobile phones, tablets, desktops). Support current versions of Microsoft Windows Server, Red Hat Linux operating systems, VMware Cloud infrastructure, and other VA Technical Reference Model (TRM) components. Location independence of provided resources. Resource capacity appears to be unlimited (elasticity, scalability). Automatically control and optimize resource use. Resource usage monitored, controlled, and reported (including chargeback). Cost stability and containment. Support integration of alternative cloud service providers (commercial and Government) as part of the IO cloud computing environment. Employ a continuous improvement, flexible architecture that can rapidly integrate new requirements and functionality. Architecture sufficiently abstract to enable VA to effectively utilize current cloud solutions and transition or replace core components as needed with minimal interruption. Self-Provisioning: Web-based User Interface (UI) Ability to perform all self-provisioning functions from a web-based UI. At a minimum, the web-based UI shall be fully compatible with specific operating system and web browsers utilized within VA. Provisioning request customization The CMP shall provide VA administrators with the ability to customize the provisioning request. Request management system Ability to manage provisioning request and review all requests and generate reports showing the status of all requests. Preapproved provisioning. Automated request fulfillment Automatic without requiring intervention of VA administrators. Provisioning status and change request status. Life cycle management for provisioned objects. Performance monitoring for provisioned objects. Usage limits enforcement. Service Catalog Web-based administrative interface. Cloud resource pool definition. Cloud resource pool elasticity. Cloud tenant network object definition. Virtual service object definition. Object cost, pricing model and currency definition. Support for delta disks. Object customization permissions. Service-level definition. Software library. Access permissions definition. Charge Back Web-based administrative interface. Cost reporting. Allocation-based charging model. Multi-tenant charging. Capacity Management Web-based administrative Interface. Object provisioning quota. Tenant-level resource allocation. Tenant-level resource limits. VM-level resource allocation. Performance Management Web-based administrative interface. Infrastructure-level performance monitoring. Agentless data collection. Self-monitoring. Configuration and Change Management Web-based administrative interface. Topology and configuration discovery. Compliance rule definition and assignment. Predefined compliance rule base. Configuration compliance verification. Change auditing. Maintenance window management. Change request management. Asset, change, compliance and software distribution reporting. Software configuration management. Configuration versioning. Lifecycle Management Web-based administrative interface. Object import. Object management. Object reconfiguration. Object decommission. Lease time management. Lifecycle analytics and reporting. External Cloud Connector Web-based administrative interface. External cloud access management. Secure network tunneling. Network transparency. External cloud service discovery. Object transfer optimization. Automated object transfer. Transfer monitoring and debugging. Object constraint propagation. Guest Operating System (OS) sanitization. Virtual machine format conversion. Support for proxy connectivity. Support for multiple cloud service providers. Orchestration Web-based administrative interface. Workflow definition. Combined workflows. Automation policy definition. Support for a minimum of 100 concurrent workflows. Workflow library. Workflow monitoring and debugging. Predefined automation workflows. Workflow versioning. Support for a minimum of 500 concurrent workflows. Predefined automation policies. Platform Highly available design. Scalable deployment. Support for mainstream operating systems. Support for mainstream databases. Configuration management database. Support for infrastructure maintenance. Support for a minimum of 10,000 managed objects. Support for a minimum of 25 concurrent administrators. Security Automated IT Security controls that deliver Federal Information Security Management Act (FISMA) High NIST 800-53 rev4 and all enhancements. Integration with directory services. Role-based access control. Secure Socket Layer (SSL) connection. Security logging and auditing of administrative actions. Support for multiple Virtual Local Area Networks (VLAN). Access auditing reporting. Multifactor authentication. Identification of object location. Software library protection. Internal denial-of-service prevention. Integration with 3rd Party Tools Application programming interfaces. Integration with resource managers. Integration with configuration management databases. Integration with help desk and ticketing systems. Integration with enterprise security solutions. Integration with third-party external cloud connectors. Licensing License normalization. License modularity. Per-number-of-provisioned-catalog-objects licensing. License bursting. Product/Vendor Support Two-year minimum of extended support for end-of-life products. Published support life cycle dates at product launch. Support for multiple hypervisors VMware Hyper-V The solution shall comply with the NIST Cloud Computing Standards Roadmap (Special Publication 500-291), which describes standards for interoperability, portability, and security). The solution shall also comply with Guidelines on Security and Privacy in Public Cloud Computing (Special Publication 800-144) and VA Handbook 6500 VA Handbook 6500 - US Department of Veterans Affairs. For a list of all required documents, see Appendix C. The solution shall have the ability to connect to multiple VA approved public cloud entities. Tools to facilitate migration of applications and data between CSPs and also from traditional/virtual environments operated by the VA to a CSP Ability to integrate with Cloud Access Security Broker or provide facilitate migration of applications and data between CSPs and also from traditional/virtual environments operated by the VA to a CSP 3.2 Converged/Hyper-converged Infrastructure The Converged/Hyper-converged Infrastructure solution shall be capable of integrating with current IO infrastructure (see table 1) and scale to meet future VA Enterprise needs. The solution shall work with the CMP identified above. The solution shall comply with the NIST Cloud Computing Standards Roadmap (Special Publication 500-291), which describes standards for interoperability, portability, and security). The solution shall also comply with Guidelines on Security and Privacy in Public Cloud Computing (Special Publication 800-144) and VA Handbook 6500 VA Handbook 6500 - US Department of Veterans Affairs. The solution shall be scalable on an enterprise level to multiple geographically diverse data centers. Scalability: Automated and rapid scaling of cloud computing resources to synchronize application capabilities with changing mission and load requirements. The vendor shall provide documented limitations to scalability and maximum capacity of the solution. Elasticity: Makes it easy to scale out/in resources as required by business demands. Virtual Machine (VM) Centricity: A focus on the VM or workload as the cornerstone of enterprise IT, with all supporting constructs revolving around individual VMs. Data Protection: Ensures that data can be restored in the event of loss or corruption is a key IT requirement, made far easier by VA Cloud infrastructure. VM Mobility: Enables greater application/workload mobility. High availability: Enables higher levels of availability than possible in legacy systems. 3.3 Managed Services The VA may be interested in obtaining managed services for the above items to augment available resources. The vendor may have sole or shared responsibility for this service, including implementation, operations, maintenance, and administrative activities. The vendor may provide full lifecycle management to one or more of the following areas: Architecture guidance System administration and operations (OPs) System monitoring, alerting, and reporting Performance testing and tuning Proactive communications and 24×7 support A single point of contact for support Domain Name System (DNS) management Security and compliance management Backup and disaster recovery Database administration Developer support and training Network administration Storage administration Virtualization management Capacity management Application deployment, scaling and lifecycle management CMP administration and integration Process integration Cloud migration architectural, configuration, and logistics support for applications and data   4.0 References: The following references are relevant to this RFI: The NIST Definition of Cloud Computing Special Publication 800-145 Guidelines on Security and Privacy in Public Cloud Computing Special Publication 800-144 NIST Cloud Computing Standards Roadmap Special Publication 500-291 VA Handbook 6500 - US Department of Veterans Affairs VA Handbook 6500 - US Department of Veterans Affairs Hyper-convergence Online Reference Defining Hyper-convergence, Hyper-converged Infrastructure Basics, © 2016 5.0 Questions for Industry: Overall RFI Questions Please indicate which of the four possible approaches identified in Section 2.0 above that you would be interested and capable of providing. Please identify any alternative approaches to obtain, implement, support, and operate a complete CMP and Converged/Hyper-converged Infrastructure solution with life-cycle managed services. CMP Would you be interested and capable of providing a CMP solution to support this effort? What are alternative approaches that VA should consider to obtain, implement, support, and operate the described CMP capabilities? What type of pricing structures (FFP vs. T&M, unit vs. range pricing, etc.) are typically used by industry to deliver VA s CMP requirements described in this RFI? What types of software licensing arrangements are typically used by industry to deliver the VA CMP requirements described in this RFI? What, if any, technical requirements (capabilities, functionalities, etc.) do you believe VA has omitted that will be required in order for VA to meet its intended CMP objective? What specific commercial-off-the-shelf (COTS) hardware and software components are capable of meeting VA s requirements for the CMP? Are there any limitations to scalability and maximum capacity of the solution? Provide a pricing Rough Order of Magnitude (ROM) to deliver, implement, support, and operate a CMP solution to meet the requirements of this effort. VA is considering conducting product demonstrations to test and evaluate proposed CMP solutions in a VA sandbox environment under strict source selection procedures for this effort. Please provide any input (i.e., technical, logistical or otherwise) for VA to consider if requiring product demonstrations during a formal source selection evaluation phase for this effort. Do you currently have a CMP solution of similar size and scope to that envisioned in Section 3 of this RFI that is in full production within the Federal Government or elsewhere? If so, please detail the existing solution. Converged/Hyper-converged Infrastructure Would you be interested and capable of providing a Converged/Hyper-converged Infrastructure solution to support this effort? What are alternative approaches that VA should consider to obtain, implement, support, and operate the described Converged/Hyper-converged Infrastructure capabilities? What type of pricing structures (FFP vs. T&M, unit vs. range pricing, etc.) are typically used by industry to deliver VA s Converged/Hyper-converged Infrastructure requirements described in this RFI? What types of software licensing arrangements are typically used by industry to deliver the VA Converged/Hyper-converged Infrastructure requirements described in this RFI? What, if any, technical requirements (capabilities, functionalities, etc.) do you believe VA has omitted that will be required in order for VA to meet its intended Converged/Hyper-converged Infrastructure objective? What specific commercial-off-the-shelf (COTS) hardware and software components are capable of meeting VA s requirements for the Converged/Hyper-converged Infrastructure? Are there any limitations to scalability and maximum capacity of the solution? Provide a pricing Rough Order of Magnitude (ROM) to deliver, implement, support, and operate a Converged/Hyper-converged Infrastructure solution to meet the requirements of this effort. VA is considering conducting product demonstrations to test and evaluate proposed Converged/Hyper-converged Infrastructure solutions under strict source selection procedures for this effort. Please provide any input (i.e., technical, logistical or otherwise) for VA to consider if requiring product demonstrations during a formal source selection evaluation phase for this effort. Do you currently have a Converged/Hyper-converged Infrastructure solution of similar size and scope to that envisioned in Section 3 of this RFI that is in full production within the Federal Government or elsewhere? If so, please detail the existing solution. Managed Services Would you be interested and capable of providing Managed Services for a CMP and/or Converged/Hyper-converged Infrastructure solution? What are alternative approaches that VA should consider to maintain and support a CMP and/or Converged/Hyper-converged Infrastructure solution? What type of pricing structures (FFP vs. T&M, etc.) are typically used by industry to deliver VA s Managed Services requirements described in this RFI? What, if any, technical requirements do you believe VA has omitted that will be required in order for VA to meet its intended Managed Services objective? Provide a pricing Rough Order of Magnitude (ROM) for all identified alternatives for providing the VA-required Managed Services capabilities.
 

Web Link

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

Document(s)

Attachment
 

File Name: VA118-17-R-1821 VA118-17-N-1821.docx (https://www.vendorportal.ecms.va.gov/FBODocumentServer/DocumentServer.aspx?DocumentId=3173196&FileName=VA118-17-R-1821-000.docx)

Link: https://www.vendorportal.ecms.va.gov/FBODocumentServer/DocumentServer.aspx?DocumentId=3173196&FileName=VA118-17-R-1821-000.docx

 

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

Record

SN04358130-W 20161223/161221235331-df25badb5dbbd68c5bdcd9d965fe52e9 (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 |