New clarification added: Question 8:We would like to raise a concern regarding certain hardware requirements in the TOR, specifically under Section 7.3.1 HCI Cluster Nodes (VM Hosts). We are currently facing challenges sourcing the following components due to a global parts shortage:- Table 8, Ref: #14 Internal Storage Controllers: HBA355i,- Table 8, Ref: #16 Boot Devices: BOSS controller card.As these parts are currently unavailable for the Dell R770 vSAN Ready Node, we would like to propose an alternative solution. Could we utilize the Dell R760 with Dell VxRail instead? This configuration would include the required BOSS cards and HBAs necessary for the vSAN setup.Please let us know if this alternative is acceptable.Response 8:The minimum requirements for the HCI nodes as outlined in the TOR, such as the need for vSAN Ready Nodes, remain unchanged. As indicated in the TOR, and reiterated in the prebid meeting, offers are required to meet at least the specified minimum requirements. 

New clarification added: Question 7:In 7.3.1, Line 15 - Storage devices 15. Storage Devices –a) vSAN Caching Tier: Nodes must have at least Two (2) Enterprise NVMe drives, Mixed-Use, 1.6TB,b) vSAN Capacity Tier: Nodes must have at least Twelve (12) Solid State Drive (SSD) drives, 1.92TB, SAS, Read Intensive, 24Gbps, 2.5-inch, Hot-Plug drives.7.1. Based on Dell, 1.6TB NVMe drives and 1.92TB NVMe drives are not anymore available to be ordered. Can we propose 6 x 3.84TB Enterprise NVMe drives same aggregate capacity as required? 12 x 1.92TB = 23.04TB6 x 3.84TB = 23.04TB7.2. Can we do away with the Caching and Capacity Tier since we are following Single Storage Tier for vSAN Express Architecture that requires Full NVMe drives? Response 7:7.1. You may propose 8 x 3.84TB Enterprise NVMe Mixed Use drives instead, to fulfill the requirements.7.2. This is acceptable as long as it fulfills vSAN Ready Nodes recommendations/specifications. 

New clarification added: Question 6:Clarification on Requirement 7.3.1 – Internal Storage Controllers and Storage Devices. Under line 15:a) vSAN Caching Tier: Nodes must have at least Two (2) Enterprise NVMe drives, Mixed-Use, 1.6TB,b) vSAN Capacity Tier: Nodes must have at least Twelve (12) Solid State Drive (SSD) drives, 1.92TB, SAS, Read Intensive, 24Gbps, 2.5-inch, Hot-Plug drives.Clarification: 6.1. Upon checking,in the vSAN ESA (Express Storage Architecture), there is no need for a separate cache tier and a capacity tier. There should only be a Single Storage Tier (All NVMe), what can specific NVMe drive should we consider? (3.2TB Enterprise NVMe Mixed Use, 3.84TB Enterprise NVMe Read Intensive, 6.4TB Enterprise NVMe Mixed Use, 7.68TB Enterprise NVMe Read Intensive or 15.36TB Enterprise NVMe Read Intensive).6.2. How many drives? Response 6 (6.1 & 6.2): You may propose 8 x 3.84TB Enterprise NVMe Mixed Use drives instead, to fulfill the requirements.

New clarification added: Question 5:Clarification on Requirement 7.3.1 – Internal Storage Controllers and Storage Devices. Under line 14. Internal Storage Controllers – Nodes must have suitable storage controllers to enable and support the required drive and vSAN setup (HBA355i Front or similar).Our proposed R770 vSAN ESA solution uses NVMe direct-attached drives (E3.S) which do not require a traditional internal storage controller (HBA/RAID).Kindly confirm if this controller-less architecture is acceptable for compliance with item 7.3.1, as it aligns with VMware vSAN ESA best practices.Response 5:This is acceptable as long as it fulfills vSAN Ready Nodes recommendations/specifications.

New amendment added #2: Dear Bidders,Be informed of the following amendments to the deadlines:​Tender closing date: Thursday 7 May 2026 at 11:59 PM (Philippine local time)Deadline for clarifications: Tuesday 5 May 2026 at 11:59 PM (Philippine local time)Expected Contract award date: 8 June 2026.This shall form an integral part of the tender; be guided accordingly.UNOPS

New clarification added: Question 1:1.1) 3-Node vs 4-Node HCI Design - Cost and Architecture: The revised Terms of Reference specifies the deployment of a three (3) node all-flash HCI cluster utilizing VMware vSAN technology, with virtualization licensing based on 144 cores total (3 nodes × 2 CPUs × 24 cores). While the node count has been reduced from the original four-node configuration, the functional scope, system workload, and nationwide operational requirements remain unchanged, including: support for 235 municipalities  regional and central users  application, database, monitoring, and secure access services. 1.2) Network Topology Design, Segmentation, and Implementation Scope: The provided system architecture diagram outlines the required network zones and logical segmentation (e.g., DMZ, Management, Production, and Replication). However, detailed implementation parameters such as VLAN ID assignment, IP addressing scheme, QoS policies, NIC bonding configuration, routing design, and firewall rule definitions are not explicitly specified. May we confirm whether these detailed network design components are to be provided by the end-user, or are expected to be designed and implemented by the supplier as part of the project scope?Response 1 (1.1 & 1.2):The minimum requirements for the HCI nodes, as outlined in the TOR, remain unchanged. As indicated in the TOR, and reiterated in the prebid meeting, offers are required to meet at least the specified minimum requirements.Refer to the TOR Section 7.5.2, Ref. 48ff which, inter alia, defines the responsibilities of the Supplier in terms of system architecture design. The Purchaser and/or the DOH will provide the necessary input to enable the development of a comprehensive design.Question 2: Backup and Disaster Recovery (DR) Scope. May we kindly clarify whether the project scope requires only the built-in redundancy and high availability features of the HCI platform, or if a dedicated backup and disaster recovery (DR) solution is expected to be included as part of the deliverables?Response 2:The requirements set out in the TOR regarding data backup and disaster recovery remain unchanged.Question 3:Security requirements: May we kindly confirm if there are specific security standards or compliance frameworks (e.g., ISO, NIST, or DOH-specific guidelines) that the system is required to adhere to?Response 3:For requirements in terms of security, refer to the TOR Section 3.3 Par. 34 (a) v., Section 7.5.2 Ref. 51 and Ref. 55, and Section 78 b) ii), etc. Further, Suppliers may recommend specific and additional security measures to be implemented in the System Architecture Design & Implementation Report (see TOR 7.5.2, Ref. 48ff).The requirements set out in the TOR regarding data monitoring, logging and alerting remain unchanged.Question 4:We kindly request that a three (3) day extension be considered to allow sufficient time for us to review, align, and appropriately reflect your guidance in our final submission.Response 4:Note that your request was accepted favorably and the deadlines have been extended as follow:Tender closing date: 4 May 2026 at 11:59 PM (Philippine local time)Deadline for clarifications: 29 April 2026 at 11:59 PM (Philippine local time).

New amendment added #1: Dear Bidders,Be informed of the following amendments:The Minutes and Presentation of the pre-bid meeting held on 23 April 2026 have been uploaded under the documents section,The deadlines have been extended as follow:Tender closing date: 4 May 2026 at 11:59 PM (Philippine local time)Deadline for clarifications: 29 April 2026 at 11:59 PM (Philippine local time)Expected Contract award date: 1 June 2026.This shall form an integral part of the tender; be guided accordingly.UNOPS