Attachment B Solution Requirements.xlsx
XLSX spreadsheet 54 KB Posted
- Attached to
- Virtual Machine Infrastructure
- Solicitation number
- InfoSys-2025-001
- Issued by
- Gilpin County, Colorado
About this file
Attachment B Solution Requirements.xlsx is a technical specification document for Grand County Government of Colorado's Virtual Machine Infrastructure (VMI) procurement. The county is seeking proposals for a new VMI platform to replace its current on-premise environment located in Hot Sulphur Springs and Granby, with proposals due by July 1, 2025, and a planned contract award on January 1, 2026. The project timeline includes vendor information collection through June 1, 2025, proposal review by September 1, 2025, and phased deployments in Hot Sulphur Springs (by July 1, 2026) and Granby (Q4 2026), with full project closure anticipated in Q4 2026.
The technical requirements specify a comprehensive VMI solution demanding specific hardware and software capabilities, including support for multiple hypervisors, high-availability architecture, and robust infrastructure specifications. The primary site requirements include 176GHz vCPU, 1.5TB RAM, 50TB storage, support for 60+ VMs, and energy-efficient hardware. Key additional requirements include direct vendor support, all-inclusive licensing, Active Directory integration, backup compatibility with Veeam and Exagrid, centralized management, performance analytics, and a migration pathway that accommodates potential growth over a 5-year period. The county's current infrastructure uses VMware vSAN, Dell PowerEdge, Exagrid, and Veeam solutions, and seeks a modern, scalable, resilient, and operationally uncomplicated replacement.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| Grand County 2025 VMI RFP Final.pdf | ||
| Attachment A Sample County Services Contract.pdf |
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
Requirements Exhibit A
| Attachment B: 2025 Virtual Machine Infrastructure Solution Requirements | |||
| Rating Value | Description | ||
| SUP | Supported as delivered "out-of-the-box" | ||
| MOD | Supported via modifications (screen configurations, reports, GUI tailoring, etc.) | ||
| 3RD | Supported via a third party solution | ||
| FUT | Will be supported in a future release | ||
| NS | Not supported | ||
| # | Requirement | Rating | Additional Comments |
| 1.00 | Industry Common Hypervisor | ||
| 1.01 | VMware ESXi, Microsoft Hyper-V, KVM, Xen, AHV, etc. | Which one(s)? | |
| 2.00 | Resilience (Dual Site) | ||
| 2.01 | Highly Available/Clustered architecture | ||
| 2.02 | Hardware Redundancy. PSU, NIC, RAID, etc. | ||
| 2.03 | Ability to failover with remote site over VPN or direct fiber. | ||
| 3.00 | Hardware Minimum Specifications (Primary Site) | ||
| 3.01 | vCPU ≥ 176GHz | ||
| 3.02 | RAM ≥ 1.5TB | ||
| 3.03 | DISK ≥ 50TB (IOPS up to 3,412) | ||
| 3.04 | iSCSI Capable (Jumbo Frames) | ||
| 3.05 | Copper Ethernet up to 10Gbps | ||
| 3.06 | 12U or less of rack consumption. | ||
| 3.07 | Energy efficient hardware. | ||
| 3.08 | Support for 60+ VMs. (Windows, Ubuntu, and OVF) | ||
| 3.09 | Ability to manage and allocate GPU resources to virtual machines | ||
| 4.00 | Hardware Minimum Specifications (DR Site) | ||
| 4.01 | Sized to accommodate 1/2 of the primary site workload. | ||
| 4.02 | Rapid scalability. One week target node delivery. | ||
| 5.00 | Software: Licensing and Support | ||
| 5.01 | Direct to platform vendor support. | ||
| 5.02 | All inclusive licensing with clear itemization for addon components. | ||
| 5.03 | Documented inventory of licensed components and keys. | ||
| 5.04 | Documented support and account manager contacts. | ||
| 6.00 | Hardware: Licensing and Support | ||
| 6.01 | Direct to platform vendor support. | ||
| 6.02 | Documented inventory of support contacts and warranties. | ||
| 7.00 | Additional Components | ||
| 7.01 | 10Gbps switching to support core networking. | ||
| 7.02 | Capability of adding encryption at rest functionality to the datastores. | ||
| 7.03 | Integrates with Active Directory | ||
| 7.04 | Compatibility with Microsoft SQL Server and Failover Clustering at the VM level | ||
| 8.00 | Deployment Services | ||
| 8.01 | Bid to include on-site installation, validation, and ad-hoc training. | ||
| 9.00 | Manageability | ||
| 9.01 | Proposed solution should allow for management flexibility such as hardware/firmware updating across nodes without interruption of production services. | ||
| 9.02 | Scheduling and QoS for workloads and maintenance windows. | ||
| 9.03 | Centralized management and monitoring of distributed resources and workloads. | ||
| 9.04 | Analytics for resource usage and performance over time. | ||
| 9.05 | Automated Alerting and Reporting. Proactive phone home support allowed. | ||
| 9.06 | vMotion or comparable functionality. | ||
| 10.00 | Backup Integration | ||
| 10.01 | Integrates with Veeam Enterprise BDR and Exagrid | ||
| 10.02 | Hypervisor level integration for backups | ||
| 11.00 | Expansion and Lifecycle | ||
| 11.01 | Proposal should provide a pathway for cost effective scaling and expansion of resources. | ||
| 11.02 | Proposal should provide a pathway for seamless replacement of aged hardware. | ||
| 11.03 | Proposal should be sized to accommodate light growth over a period of 5 years. | ||
| 12.00 | Migration Capable | ||
| 12.01 | Uses common methods and protocols to allow for migration and upgrade of hardware components. | ||
| 13.00 | Remote Site Recoverability | ||
| 13.01 | Ability to schedule snapshot or workload transfer to remote DR site. | ||
| 13.02 | Bandwidth recommendations based on provided storage specs. | ||
| 14.00 | Training and Knowledge Transfer | ||
| 14.01 | Comprehensive knowledge transfer and shadowing during primary site deployment. | ||
| 14.02 | Provide guidance that will help us deploy the remote DR site VMI with minimal assistance. | ||
| 14.03 | Demonstration of Knowledge Base and support system. | ||
| 14.04 | Training course cost breakdown and schedules. |
File details come from the government source that posted it. Updated .