Appendix 12 - PWS Technical Requirements (1).xlsx

0001 Storage 0001A - Enterprise Block Storage 0001B - Enterprise Virtual Environment Storage 0001C - Storage Area Network (SAN) 0001D - Bulk, Block-Based Storage 0001E - Network Attached Storage (NAS) 0001F - Object Storage 0001G - Backup Appliance 0001H - Mainframe Virtual Tape System (VTS) 0001I - Storage Resource Management (SRM) 0001J - Software Defined Storage (SDS) 0001K - High Performance Computing (HPC) Storage 0001Z - Emerging Tech - Storage

•Must support heterogeneous data migration which is non-disruptive to ongoing operations •Must support asynchronous replication of data to a minimum of 3 remote target devices •Must support minimum of 32Gb Fibre Channel (FC) front-end ports with an OEM roadmap to 64Gb •Must support synchronous data replication for full volume copy internal to the array and snapshot copies and synchronous/asynchronous replication external to the array •Must support automatic space recovery reclamation •Must support multitenancy and single tenancy •Must support thin provisioning virtualization of storage resources to attached servers •Must automatically identify and optimize disk usage •Must support data protection for drive failure to include Global Hot Spares or functional equivalent •Must support dynamic tiering and multi-tiered lifecycle management •Must support array-based volume snapshots •Must support Non-Volatile Memory Express (NVMe) and Non-Volatile Memory Express over Fabrics (NVMe-oF) •Must support storage efficiency technologies (e.g. deduplication, compression, etc.)

•Mainframe •Must support minimum of 16Gb Fiber Connection (FICON) ports with an OEM roadmap to 32Gb •Must support Mainframe operating systems to include all licensing for Mainframe use

•Must support minimum of virtual machine software (e.g. VMware, VM Essentials, etc.) hypervisor integration •Must support disaster recovery of virtual machines (VMs) and VM snapshots •Must support VM hypervisor Application Program Interface (API) for Array Integration or equivalent •Must support VM hypervisor API for Storage Awareness (latest version) or equivalent •Must support VM hypervisor Pluggable Storage Architecture for SAN multipathing or equivalent •Must support minimum of 32Gb FC front-end ports with an OEM roadmap to 64Gb •Must support synchronous data replication for full volume copy internal to the array and snapshot copies and synchronous/asynchronous replication external to the array •Must support automatic space recovery reclamation •Must support multitenancy and single tenancy •Must support thin provisioning virtualization of storage resources to attached servers •Must automatically identify and optimize disk usage •Must support data protection for drive failure to include Global Hot Spares or functional equivalent •Must support dynamic tiering and multi-tiered lifecycle management •Must support NVMe and NVMe-oF •Must support storage efficiency technologies (e.g. deduplication, compression, etc.)

•Large •Must support a minimum of 100GBps total throughput •Medium •Must support a minimum of 50GBps total throughput •Small •Must support a minimum of 20GBps total throughput

•Must support non-disruptive Adding/Removing components, including SFPs •Must support non-disruptive updates of software/firmware •Must support scale up/down and allow for reconfiguration in a manner that is non-disruptive •Must be 100% compatible with the Government's current SAN hardware •FICON Switching •Must support short wave ports (Multi-mode) •Must support long wave ports (Single-mode) •Must support 16Gb Small Form-factor Pluggable (SFP) with an OEM roadmap to 32Gb •Must support FICON CUP •Fibre Channel Switching •Must support short wave blades (Multi-mode) •Must support 64Gb SFPs with an OEM roadmap to 128Gb •Must support Enterprise class backbones with multiple blades •Must support NVMe-oF •SAN Extension Switching •Must support minimum of 24 short wave FC ports •Must support 10 Gigabit Ethernet (GbE) ports •Must support Fibre Channel over IP

•Must support basic Redundant Array of Independent Disks (RAID) protection/erasure coding •Must support multitenancy •Must support FC connectivity •Must support thin provisioning virtualization of storage resources to attached servers

•Must support multitenancy and multiple virtual local area networks with IP space separation (IPv4 & IPv6) •Must allow each tenant to join a separate Windows Active-Directory Domain •Must support 10 GbE and 32Gb FC interfaces with an OEM roadmap for 64Gb for customer and backup data paths •Must support separate network ports for device management •Must support 802.1Q trunking •Must support RAID capabilities or equivalent •Must support asynchronous data replication •Must support point-in-time and snapshot copies internal to the array •Must support thin provisioning virtualization of storage resources to attached servers •Must support cloud connectivity •Large •Must support a minimum of 200GBps total throughput •Medium •Must support a minimum of 75GBps total throughput •Small •Must support a minimum of 5GBps total throughput

•Must support written data protection by encoding and distribution to multiple sites to ensure data availability in the case of a site loss •Must support space recovery reclamation •Must support logical storage separation •Must support Lightweight Directory Access Protocol/Single Sign On/external authentication solution to manage users and groups •Must support multi-tenancy allowing for self-management •Must support data protection for component failure •Must support automated data tiering capabilities •Must automatically identify and optimize disk usage •File sync and share •Must support enterprise-level Secure Cloud Storage with user-level file-sharing and file-syncing services and capabilities that is capable of integrating with multiple external authentication sources for user access (e.g. Active Directory domains) •Must support a Global File System •Must support local caching for on-prem data access •Must support edge acceleration •Must include High Availability •Must support multi-site deployment

•Must support data protection for component failures •Must support minimum of 16Gb FC connections with an OEM roadmap to 32Gb and 64Gb •Must support 10GbE connections •Must be an appliance-based solution that significantly reduces external master/media backup servers •Must support appliance-based deduplication and compression •Must support multi-site replication (1-1 and 1-many) •Must be 100% compatible with the Government's Veritas NetBackup Enterprise Server environment •Master •Central control point to manage backup policies and configurations •Contains backup catalog and internal databases •Media •Stores backup data on attached storage •Manages data movement between backup clients and backup storage devices

•Must be reconfigurable without service disruption •Must not include any physical tape •Must support deduplication and replication capabilities to support Continuity of Operations (COOP) •Must support Automated Tape Library command processing from Mainframe hosts and command processing from the Mainframe host to support COOP simulation testing •Must support read of replicated tape data and write of new tape data during testing with no adverse impact to the ongoing COOP replication of production processing •Must support a High Availability configuration to eliminate tape processing outages during component failures and/or code updates •Must include all integration support between the Mainframe and all components of the VTS solution •Must provide local and replication performance of live production data

•Must provide business process, metered/usage (used capacity) billing to support charge-back capabilities, and multi-tiered lifecycle management utilizing built-in AI •Must provide server storage and array capacity utilization information for physical servers, virtual servers, and Kubernetes containers to be utilized for Government financial billing purposes •Must provide the ability to export data and/or the ability to link through a web services interface •Must have detailed reporting and provide data filtering and granularity to the storage volume level •Must fully sustain all storage solutions provided under this contract •Must maximize integration with the Government’s current installed storage inventory •Must be capable of integrating with the Government's ServiceNow environment

•Must run on a vendor agnostic infrastructure •Must provide flexibility to scale to a multi-petabyte capacity •Must provide flexibility to scale performance and capacity independently •Must provide automation and orchestration capabilities for managing storage resources •Physical Appliance •Includes hardware, software and licensing to manage appliance •Virtual Appliance •Includes software and licensing to manage appliance

•Must support high-speed, low-latency front-end port connectivity, to include InfiniBand •Must support parallel file systems •Must provide flexibility to scale performance and capacity independently •Must support dynamic tiering and multi-tiered lifecycle management •Must support heterogeneous data migration which is non-disruptive to ongoing operations •Must provide a comprehensive API for programmatic access to storage resources to enable automation and integration with orchestration platforms (e.g. Kubernetes, OpenShift) •Must support Infrastructure as Code (IaC) tools for automated storage provisioning/configuration (e.g. Terraform, Ansible, etc.)

•Must support seamless integration with cloud storage services for data transfer and hybrid cloud workflows •Must support asynchronous replication of data to a minimum of 3 remote target devices •Must support synchronous data replication for full volume copy internal to the array and snapshot copies and synchronous/asynchronous replication external to the array •Must support automatic space recovery reclamation •Must support thin provisioning virtualization of storage resources to attached servers •Must automatically identify and optimize disk usage •Must support data protection for node and drive failure to include Global Hot Spares or functional equivalent •Must support array-based volume snapshots •Must support Non-Volatile Memory Express (NVMe) and Non-Volatile Memory Express over Fabrics (NVMe-oF) •Must support storage efficiency technologies (e.g. deduplication, compression, etc.)