Attachment 1. SOW - PHX_Area_IT Storage-Compute_v2.pdf

PHOENIX AREA INDIAN HEALTH SERVICE

Storage and Compute Solution

Statement of Work

Prepared by:

Phoenix Area Office

40 N Central, Suite 605

Phoenix, Arizona 85004

April 25, 2025

Vision Statement

Optimize, modernize, and standardize hardware for Indian Health Service Phoenix Area Hospitals and Clinics.

1 Background IHS Phoenix Area is comprised of eleven regional areas referred to as service units. Service units are located across central Arizona, northern Nevada and Northwestern Utah. The facilities range from small ambulatory care clinics to full-service hospitals.

The Indian Health Service (IHS) uses secure information technology (IT) to improve health care quality, enhance access to specialty care, reduce medical errors, and modernize administrative functions consistent with the Department of Health and Human Services (HHS) enterprise initiatives. The Indian Health Service (IHS) Department of Information Resource Management (DIRM), Phoenix Area Office, is responsible for maintaining the IHS Enterprise Architecture (EA), established to improve the effectiveness of the business processes, data, resources, services, systems and technology that support IHS mission and goals.

1.2 Objective

Currently we are looking to modernize and standardize on a hardware solution for storage and compute for the hospitals in the Phoenix region, along with 3 other IHS facility regional offices that may participate. We want to engage in a Blanket Purchase Agreement (BPA), to standardize on specific hardware standards, to allow our hospitals to order from that agreement, to stay in line with enterprise architecture initiatives.

1.3 Scope

This project aims to implement a standard storage solution along with standard server hardware deployments at each of our large hospitals as well as our area office. The contractor shall provide, configure, and install hardware based on 3 configuration options for our service units to choose from. Details of each configuration requirement will be provided in section 3 Performance requirement. The contractor will be required to provide a standard server solution for computing requirements, storage requirements, and networking hardware to integrate solution in to each local area network. Contractor shall provide professional services to accomplish tasks outlined in this SOW.

2 General Requirements General requirement for contracting with the government.

2.1 Non-Personal Services

The Government shall neither supervise contractor employees nor control the method by which the contractor performs the required tasks. Under no circumstances shall the Government assign tasks to, or prepare work schedules for, individual contractor employees. It shall be the responsibility of the contractor to manage its employees and to guard against any actions that are of the nature of personal services, or give the perception of personal services. If the contractor believes that any actions constitute, or are perceived to constitute personal services, it shall be the contractor's responsibility to notify the Contracting Officer Representative (COR) immediately.

2.2 Business Relations

The contractor shall successfully integrate and coordinate all activity needed to execute the requirement. The contractor shall manage the timeliness, completeness, and quality of problem identification. The contractor shall provide corrective action plans, proposal submittals, timely identification of issues, and effective management of subcontractors. The contractor shall seek to ensure customer satisfaction and professional and ethical behavior of all contractor personnel.

2.4 Subcontract Management

The contractor shall be responsible for any subcontract management necessary to integrate work performed on this requirement and shall be responsible and accountable for subcontractor performance on this requirement. The prime contractor will manage work distribution to ensure there are no Organizational Conflict of Interest (OCI) considerations. Contractors may add subcontractors to their team after notification to the Contracting Officer Representative (COR).

Cross teaming may be permitted.

2.5 Contractor Personnel, Disciplines, and Specialties

The contractor shall accomplish the assigned work by employing and utilizing qualified personnel with appropriate combinations of education, training, and experience. The contractor shall match personnel skills to the work or task with a minimum of under/over employment of resources.

The Contractor shall provide the necessary resources and infrastructure to manage, perform, and administer the contract.

2.6 Location and Hours of Work

Accomplishment of the results contained in this SOW requires work at Phoenix Area Indian Health Service, 40 North Central Ave #605, Phoenix AZ 85004 and at various contractor, subcontractor, and Government facilities (mainly in the continental United States). Normal workdays are Monday through Friday except US Federal Holidays. Workers typically work eight

(8) hours per day, 40 hours per week. Flextime workers start not earlier than 0600 and not later than 0900. Core hours of work are from 0900 to 1500 daily. All employees are expected to be available during core hours.

3 Performance Requirements Contractor shall meet all performance standards with their proposal.

3.1 Provide and install Storage Solution within Indian Health Center's datacenters.

Storage Performance Standards

Storage capacity and performance Requirements

● A minimum of 1.2 PB of effective NVMe-oF storage capacity

● A minimum of 16 100GbE QSFP28 or HDR100 QSFP56 ports for Client access

● Installation, configuration, and dedicated support team

● All data must exist in a single flash tier. Hybrid storage solutions or tiering to other storage platforms will induce latency and fast storage misses if data has been aged out to slower storage.

Data Reduction Requirements

● The system shall reduce data across the entire namespace. Data reduction on a per-volume, per-RAID set, per-node or other subdivision is not acceptable. Full system data reduction.

● Data reduction shall be performed by the storage system inline before data is written to flash to minimize flash wear.

● Data reduction shall not require administrators to manage any jobs

● System must support data deduplication and compression.

● System must support byte-range global compression, Multi-protocol Support Requirements

● The system shall support object access via the Amazon S3 API and file access via NFS

& SMB 3.x across a single system wide namespace.

● Files created via NFS or SMB shall be accessible as S3 objects

● Objects created via S3 shall be accessible as NFS and/or SMB files

● The system shall support directory quotas that apply to both NFS and SMB

● The system must provide comparable performance for all supported protocols

NFS Support Requirements

● The system shall support byte-range advisory locking via the NLM protocol

● The system shall support a minimum of 1000 byte-range locks on a single file

● The system shall support POSIX and NFS v4.1 ACLs

● The system shall support NFS over RDMA

● The system shall support NFS v3 and V4.1

● The system shall support Kerberos for authentication

SMB Support Requirements

● The system shall support SMB/NTFS style ACLs including Deny

● The system shall support SMB 3 or greater

● Mandatory file and byte range locking

● Server failover using SMB 3 resilient handles

● System must support SMB3 Multi channel

● Access Based Enumeration (ABE) must be supported

● The system shall provide Active Directory Multi-Forest and Multi-Domain support

● The system must support SMB server-side copy

● The system must support Volume Shadow Copy (VSS)

S3 Features Requirements

● Support for all major official S3 SDK’s, such as aws-sdk-cpp, aws-sdk-java, boto3

● Multipart uploads

● 5TB or larger maximum object size

● Support for >(X) buckets/namespace

System Architecture Requirements

● The system shall not include, or rely upon, batteries or uninterruptible power supplies to insure data persistence

● The system shall not use DRAM or other volatile memory as a write cache regardless of how such DRAM is protected including NVDIMMs

● All data shall be stored in non-volatile solid-state memory devices not magnetic media

● The system shall be based on a scale-out architecture

● The system shall allow for independent scaling of capacity and performance (compute power for storage services)

● The system shall support no less than 3 generations of hardware in a single pool of storage

● Any client software make consume no more than 5% of host CPU resources

● The System must deliver promised performance without the use of kernel patches or host clients

● The system shall allow segregation of users/applications to specified compute/controller nodes

● The system shall provide transparent failover in the event of a node or network failure

● All storage system must support NFSoRDMA for CPU offload of I/O

● Namespace must be scalable to support over 100PB of capacity

● The system must store a minimum of 250TB of effective capacity per rack unit

● The system shall consume less than 7w/TB while operating

● The system must be capable of native InfiniBand and Ethernet connectivity.

● The system must support Hyper-V for VHDX volumes

● The system must support VMWare VAAI

● The system must provide a CSI driver for Kubernetes Persistent Volumes

Resilience Requirements

● The system must not have any single points of failure

● The system shall survive a minimum of four SSD failures within a failure domain without data loss

● Data protection overhead shall not exceed 10%

● The system shall use checksums, hashes or CRCs stored independent from the data

● Data and parity shall be distributed across the system without dedicated spare or parity devices

● Data rebuilds should be fail-in-place and shall begin automatically without device replacement or operator action

● Data rebuilds will be performed many to many

● Device rebuilds must take less than 1 day under load

● All updates must be non-disruptive to all users including SMB connected users

● System must minimize the impact of rebuilds to under 1%

● The system must support N:1 & 1:N replication

● The system must support asynchronous replication with a minimum frequency below 1 minute Management Requirements

● System must be manageable via CLI, GUI (HTTPS) or RESTful API

● Service shall securely collect log and analytics data

● Services shall allow issues to be proactively discovered and reported

● The system must provide a centralized console for deployed clusters

● The vendor must provide a Python SDK for system management

● The system must provide built-in performance analytics with the ability to identify top actors for all protocols down to the user level

Security Requirements

● The system shall encrypt all data before storing it to persistent media

● Encryption shall use AES-256

● The system must support both fail over and fail back of a replication pair

● The system shall provide immutable snapshots for RansomWare protection

● System must support for FIPS 140-2 today and FIPS 140-3 by the end of 2024

● The system must have the ability to support multiple tenants on the same filesystem

● The system must support Attribute Based Access control (ABAC) in conjunction with

Role Based Access control (RBAC)

● The system must provide built in audit logging for console access, admin, and protocol access (s3, NFS, SMB)

● The system must provide the ability to query audit logs directly from the User interface or

APIs

● The system must support event forwarding to Syslog, Splunk, Elastic, etc

Performance Requirements

● System must be able to deliver advertised performance without client-side caching

● System must be able to deliver advertised performance with Data Reduction and

Encryption at Rest enabled.

● System must support over 100K random read operations per client

● Clients must be capable of listing 20,000 (or more) FS objects/second

● Storage performance must be scalable to 1TB/s+ (read)

● The system must provide over 8GB/s read throughput to a single client accessing a single NFS mount

● The System must support a file size up to 128TB per file.

● S3 Single bucket: greater than 10K write IOPS @100ms latency, 20K IOPS @1ms

● The system must provide built in QOS

Catalog Functionality

● The system must have a built-in catalog with a built-in query interface to search the filesystem for specific users, create time, file size, extension, etc.

● The system must support data pushdowns from complex query engines such as Trino, Spark, and Vertica

● The built-in catalog shall support the following:

○ Up to 100 billion rows per table

○ Functions - Insert, update, delete, filtered queries, and aggregates

○ Sparse Indexes

Global Namespace Capabilities

● The system shall provide a single namespace that can span multiple locations including remote offices, centralized data stores, and cloud instances.

● The global namespace must support NFS, SMB, and S3

● The global namespace must provide a decentralized locking mechanism (IE not over the

WAN) for remote site data access and consistency Software Licensing and Support Requirements

● Vendor must guarantee software licenses and support, including replacement of all parts regardless of flash wear, will be offered on the system for a minimum of 10 years.

● Vendor must guarantee that support and software license costs shall not increase for a minimum of 10 years

● Software licenses shall be transferable to replacement hardware including hardware of later generations

● The Vendor must be the single point of support for all components of the data platform including software, server, storage, cabling, and network switching components related to the data platform

● Must offer the license of software at 100TB-600TB increments based on usage and consumption.

Requirement for Fabric Switches

● The solution must be SuperPod validated by Nvidia (validation report to be attached)

● The specified solution must meet the Superpod BEST guidance

● The specified solution must support Nvidia GPU Direct Storage over multiple paths to multiple nodes.

Space Requirements o 100 TB Usable storage for smaller clinics solution o 200 TB usable storage for medium hospitals solution o 300 TB usable storage for larger hospitals solution

Deliverables A001 Minimum of 8 Storage solutions that can be sized to the service units’ needs and can meet the defined storage requirements.

3.1.1 Provide and install Compute Solution within Indian Health Service datacenters.

Performance Standards o Small Compute Servers: minimum 3 servers per storage solution o Minimum of 256 GB Random-Access Memory o Dual 100 GB NIC for redundancy o Processor that has no more than 16 cores, Intel Xeon—G 6326 or Better o Dual Nvm-e PCIe3 storage devices for hyper visor install o Large/Medium Compute Servers: minimum 4 servers per storage solution o Minimum of 512 GB Random-Access Memory for each server o Dual 100 GB NIC for redundancy for each server o Processor that has no more than 16 cores, Intel Xeon—G 6326 or Better o Dual Nvm-e PCIe3 storage devices for hyper visor install

A002 Minimum 8 server compute solutions.

3.1.2 Provide, Rack, and Configure Top of Rack Switches for Storage and Server integration.

Performance Standards

Contractor shall provide and configure 2 top of rack solutions to integrate into storage and computer servers into LAN, for each proposal.

Standard: Cisco Nexus 9300 Series 9336C-FX2-E

• AQL: Minimum 100GE speed, 36 port per switch

• AQL: Redundant Power Supplies, 1100 Watts

• AQL: 100GBASE SR4 QSFP Transceiver, MPO, 100m over OM4 MMF for each connection to solution

• AQL: 100GBASE QSFP Active Optical Cable, 1m and 3m options for each connection to overall solution

Standard: Installation services

• AQL: Rack and install switches in existing racks or proposed rack solution.

• AQL: Replace patch cables as needed.

Standard: Support

• AQL: Smart net 5-year support contract

A003 2 top of rack switches per solution

3.1.3 Provide, install, and configure additional racks and power equipment if needed.

Performance Standards

Contractor shall provide and install a Rack and Power solution, only if required by the service unit to meet the needs of the storage solution.

Standard: Server Rack

AQL: 45 U, White sized to meet solution

Standard: Dual Power Distribution Units for power redundancy

AQL: PDU’s must meet solutions power requirements

Standard: Dual Uninterruptable Power Supplies

AQL: UPS must meet power requirements of solution to allow 30 minute uptimes in power loss scenario.

Deliverables (optional)

A004 Rack and Power options 11

4.1 Security and Safety

Contractor will adhere to all federal and tribal laws while working on location. While on location, contractor will respect any safety precautions put forth to prevent and reduce spreading the Covid-19 virus.

4.1.1 Security

Contractor working within IHS Federal Government network will be required to complete Information System Security Awareness training.

https://www.ihs.gov/issa/

Contractor shall provide a background check before accessing Indian Health Service’s information systems.

4.1.2 Safety

Contractor Compliance: The contractor and its subcontractors shall comply with Public Law 91- 596 (Occupational Safety and Health Act (OSHA)) and the Environmental, Safety, and Occupational Health (ESOH) (DODD 4715.1E). These requirements shall be incorporated into the contractor's safety and health program. The Department of Defense (DoD) participates in the OSHA Voluntary Protection Program (VPP). Contractor personnel performing services on a DoD installation shall participate in the local VPP. Information on the VPP is available at http://www.osha.gov/dcsp/vpp/index.html.

Mishap Notification and Investigation: The contractor and its subcontractors (if applicable) shall promptly report pertinent facts regarding mishaps involving Government property damage or injury to Government personnel and to cooperate in any resulting safety investigation. The contractor shall notify (via telephone) the cognizant contracting officer, the contracting officer's representative, and/or other applicable members within four (4) hours of all mishaps or incidents. The Government person notified by the contractor will in-turn notify the Safety office. Contractor notifications made after duty hours shall be reported to the appropriate installation Command Post. If requested by the cognizant contracting officer, the contracting officer's representative, and/or the cognizant program manager, the contractor shall immediately secure the mishap scene/damaged property and impound pertinent maintenance and training records until released by the investigating safety office. If the Government investigates the mishap, the contractor and the subcontractors shall cooperate fully and assist the Government personnel until the investigation is completed.

http://www.osha.gov/dcsp/vpp/index.html

4.1.3 Section 508 and Accessibility

This product must conform to the Revised Section 508 (https://www.access-board.gov/guidelines-and-standards/communications-and-it/about-the-ict-refresh/final-rule/text-of-the-standards-and-guidelines) and WCAG 2.0 Level AA standards as outlined below.

Solicitations for supplies and services shall require the submission of a Section 508 Product Assessment Template. The template can be found at https://www.itic.org/policy/accessibility/vpat.

352.239-73 Electronic Information and Technology Accessibility Notice.

(a) As prescribed in HHSAR 339.203-70(a), the Contracting Officer shall insert the following provision:

Electronic and Information Technology Accessibility Notice (December 18, 2015)

(a) Section 508 of the Rehabilitation Act of 1973 (29 U.S.C. 794d), as amended by the Workforce Investment Act of 1998 and the Architectural and Transportation Barriers Compliance Board Electronic and Information (EIT) Accessibility Standards (36 CFR part 1194), require that when Federal agencies develop, procure, maintain, or use electronic and information technology, Federal employees with disabilities have access to and use of information and data that is comparable to the access and use by Federal employees who are not individuals with disabilities, unless an undue burden would be imposed on the agency. Section 508 also requires that individuals with disabilities, who are members of the public seeking information or services from a Federal agency, have access to and use of information and data that is comparable to that provided to the public who are not individuals with disabilities, unless an undue burden would be imposed on the agency.

(b) Accordingly, any offeror responding to this solicitation must comply with established HHS EIT accessibility standards. Information about Section 508 is available at http://www.hhs.gov/web/508. The complete text of the Section 508 Final Provisions can be accessed at http://www.access-board.gov/guidelines-and-standards/communications-and-it/about-the-section-508-standards.

(c) The Section 508 accessibility standards applicable to this solicitation are stated in the clause at 352.239-74, Electronic and Information Technology Accessibility.

In order to facilitate the Government’s determination whether proposed EIT supplies meet applicable Section 508 accessibility standards, offerors must submit an HHS Section 508 Product Assessment Template, in accordance with its completion instructions. The purpose of the template is to assist HHS acquisition and program officials in determining whether proposed EIT supplies conform to applicable Section 508 accessibility standards. The template allows offerors or developers to self-evaluate their supplies and document—in detail—whether they conform to a specific Section 508 accessibility standard, and any underway remediation efforts addressing conformance issues. Instructions for preparing the HHS Section 508 Evaluation Template are available under Section 508 policy on the HHS website http://www.hhs.gov/web/508.

In order to facilitate the Government’s determination whether proposed EIT services meet applicable Section 508 accessibility standards, offerors must provide enough information to assist the Government in determining that the EIT services conform to Section 508 accessibility standards, including any underway remediation efforts addressing conformance issues.

(d) Respondents to this solicitation must identify any exception to Section 508 requirements. If a offeror claims its supplies or services meet applicable Section 508 accessibility standards, and it is later determined by the https://urldefense.us/v3/__https:/www.access-board.gov/guidelines-and-standards/communications-and-it/about-the-ict-refresh/final-rule/text-of-the-standards-and-guidelines__;!!Og_tST9LxTiQE1I!s1ZvIkBnOdFwuJAw6TNjwxSVmTqtYVLsro-fo4TSGsFlmvuAOy55AsmvJAVAcDuga94lmt5GMwUvhSf6-FkBtsuElfpoC26ukg$ https://urldefense.us/v3/__https:/www.access-board.gov/guidelines-and-standards/communications-and-it/about-the-ict-refresh/final-rule/text-of-the-standards-and-guidelines__;!!Og_tST9LxTiQE1I!s1ZvIkBnOdFwuJAw6TNjwxSVmTqtYVLsro-fo4TSGsFlmvuAOy55AsmvJAVAcDuga94lmt5GMwUvhSf6-FkBtsuElfpoC26ukg$ https://urldefense.us/v3/__https:/www.access-board.gov/guidelines-and-standards/communications-and-it/about-the-ict-refresh/final-rule/text-of-the-standards-and-guidelines__;!!Og_tST9LxTiQE1I!s1ZvIkBnOdFwuJAw6TNjwxSVmTqtYVLsro-fo4TSGsFlmvuAOy55AsmvJAVAcDuga94lmt5GMwUvhSf6-FkBtsuElfpoC26ukg$ https://urldefense.us/v3/__https:/www.itic.org/policy/accessibility/vpat__;!!Og_tST9LxTiQE1I!s1ZvIkBnOdFwuJAw6TNjwxSVmTqtYVLsro-fo4TSGsFlmvuAOy55AsmvJAVAcDuga94lmt5GMwUvhSf6-FkBtsuElfoHSBdjrg$ https://urldefense.us/v3/__http:/www.hhs.gov/web/508__;!!Og_tST9LxTiQE1I!s1ZvIkBnOdFwuJAw6TNjwxSVmTqtYVLsro-fo4TSGsFlmvuAOy55AsmvJAVAcDuga94lmt5GMwUvhSf6-FkBtsuElfr1DyJQ_A$ https://urldefense.us/v3/__http:/www.access-board.gov/guidelines-and-standards/communications-and-it/about-the-section-508-standards__;!!Og_tST9LxTiQE1I!s1ZvIkBnOdFwuJAw6TNjwxSVmTqtYVLsro-fo4TSGsFlmvuAOy55AsmvJAVAcDuga94lmt5GMwUvhSf6-FkBtsuElfoVX55uTQ$ https://urldefense.us/v3/__http:/www.access-board.gov/guidelines-and-standards/communications-and-it/about-the-section-508-standards__;!!Og_tST9LxTiQE1I!s1ZvIkBnOdFwuJAw6TNjwxSVmTqtYVLsro-fo4TSGsFlmvuAOy55AsmvJAVAcDuga94lmt5GMwUvhSf6-FkBtsuElfoVX55uTQ$ https://urldefense.us/v3/__http:/www.hhs.gov/web/508__;!!Og_tST9LxTiQE1I!s1ZvIkBnOdFwuJAw6TNjwxSVmTqtYVLsro-fo4TSGsFlmvuAOy55AsmvJAVAcDuga94lmt5GMwUvhSf6-FkBtsuElfr1DyJQ_A$

Government, i.e., after award of a contract or order, that supplies or services delivered do not conform to the described accessibility standards, remediation of the supplies or services to the level of conformance specified in the contract will be the responsibility of the Contractor at its expense.

Standards

The included standards that must be met for this contract are taken from the following two resources. Compliance with these standards is mandatory for Federal agencies subject to Section 508 of the Rehabilitation Act of 1973, as amended (29 U.S.C. 794d).

• Section 508 Standards and Guidelines: https://www.access-board.gov/guidelines-and-standards/communications-and-it/about-the-ict-refresh/final-rule/text-of-the-standards-and-guidelines

• Web Content Accessibility Guidelines (WCAG) 2.0: https://www.w3.org/TR/WCAG20/

Software Accessibility - Non-Web Based

• All WCAG A & AA Success Criteria apply – EXCEPT the following:

o 2.4.1 Bypass Blocks o 2.4.5 Multiple Ways o 3.2.3.Consistent Navigation o 3.2.4 Consistent Identification

• 502 Interoperability with Assistive Technology

• 503 Application

• 602 Support Documentation

• 603 Support Services

• 302 All Functional Performance Criteria - Note: Applies when Chapter 5 does not address one or more functions of ICT (E204), or when an agency invokes "equivalent facilitation" (E101.2)

Hardware Accessibility

• 404 Preservation of Information Provided for Accessibility

• 405 Privacy

• 406 Standard Connections

• 407 Operable Parts

• 409 Status Indicators

• 410 Color Coding

• 411 Audible Signals

• 602 Support Documentation

• 603 Support Services

• 302 All Functional Performance Criteria - Note: Applies only when Chapter 4 does not address one or more functions of ICT (E204), or when an agency invokes "equivalent facilitation" (E101.2))

Support Documentation Accessibility

• E602.1 General - Documentation that supports the use of ICT shall conform to 602.

• E602.2 Accessibility and Compatibility Features - Documentation shall list and explain how to use the accessibility and compatibility features required by Chapters 4 and 5. Documentation shall include accessibility features that are built-in and accessibility features that provide compatibility with assistive technology.

https://urldefense.us/v3/__https:/www.access-board.gov/guidelines-and-standards/communications-and-it/about-the-ict-refresh/final-rule/text-of-the-standards-and-guidelines__;!!Og_tST9LxTiQE1I!s1ZvIkBnOdFwuJAw6TNjwxSVmTqtYVLsro-fo4TSGsFlmvuAOy55AsmvJAVAcDuga94lmt5GMwUvhSf6-FkBtsuElfpoC26ukg$ https://urldefense.us/v3/__https:/www.access-board.gov/guidelines-and-standards/communications-and-it/about-the-ict-refresh/final-rule/text-of-the-standards-and-guidelines__;!!Og_tST9LxTiQE1I!s1ZvIkBnOdFwuJAw6TNjwxSVmTqtYVLsro-fo4TSGsFlmvuAOy55AsmvJAVAcDuga94lmt5GMwUvhSf6-FkBtsuElfpoC26ukg$ https://urldefense.us/v3/__https:/www.access-board.gov/guidelines-and-standards/communications-and-it/about-the-ict-refresh/final-rule/text-of-the-standards-and-guidelines__;!!Og_tST9LxTiQE1I!s1ZvIkBnOdFwuJAw6TNjwxSVmTqtYVLsro-fo4TSGsFlmvuAOy55AsmvJAVAcDuga94lmt5GMwUvhSf6-FkBtsuElfpoC26ukg$ https://urldefense.us/v3/__https:/www.w3.org/TR/WCAG20/__;!!Og_tST9LxTiQE1I!s1ZvIkBnOdFwuJAw6TNjwxSVmTqtYVLsro-fo4TSGsFlmvuAOy55AsmvJAVAcDuga94lmt5GMwUvhSf6-FkBtsuElfptx0PL1g$

• E602.3 Electronic Support Documentation - Documentation in electronic format, including Web-based self-service support, shall conform to Level A and Level AA Success Criteria and Conformance Requirements in WCAG 2.0 (incorporated by reference, see 702.10.1).

• E602.4 Alternate Formats for Non-Electronic Support Documentation - Where support documentation is only provided in non-electronic formats, alternate formats usable by individuals with disabilities shall be provided upon request.

• E602.3 Electronic Support Documentation - Documentation in electronic format, including Web-based self-service support, shall conform to Level A and Level AA Success Criteria and Conformance Requirements in WCAG 2.0 (incorporated by reference, see 702.10.1).

• E602.4 Alternate Formats for Non-Electronic Support Documentation - Where support documentation is only provided in non-electronic formats, alternate formats usable by individuals with disabilities shall be provided upon request.

• E603.1 General - ICT support services including, but not limited to, help desks, call centers, training services, and automated self-service technical support, shall conform to 603.

• E603.2 Information on Accessibility and Compatibility Features - ICT support services shall include information on the accessibility and compatibility features required by 602.2.

• E603.3 Accommodation of Communication Needs - Support services shall be provided directly to the user or through a referral to a point of contact. Such ICT support services shall accommodate the communication needs of individuals with disabilities.

• WCAG – All WCAG 2.0 A & AA Success Criteria

EXCEPTION:

o Non-Web documents shall not be required to conform to the following four WCAG 2.0 Success Criteria: 2.4.1 Bypass Blocks, 2.4.5 Multiple Ways, 3.2.3 Consistent Navigation, and 3.2.4 Consistent Identification.

o E205.4.1 Word Substitution when Applying WCAG to Non-Web Documents. For non- Web documents, wherever the term "Web page" or "page" appears in WCAG 2.0 Level A and AA Success Criteria and Conformance Requirements, the term "document" shall be substituted for the terms "Web page" and "page". In addition, in Success Criterion in 1.4.2, the phrase "in a document" shall be substituted for the phrase "on a Web page".

• Appendix A – Section 508 of the Rehabilitation Act: Application and Scoping Requirements o E208 Support Documentation and Services

• Appendix C – Functional Performance Criteria and Technical Requirements o 302 - Functional Performance Criteria o 602 – Support Documentation o 603 – Support Services

Functional Performance Criteria

• 301.1 Scope - The requirements of Chapter 3 shall apply to ICT where required by 508 Chapter 2 (Scoping Requirements), 255 Chapter 2 (Scoping Requirements), and where otherwise referenced in any other chapter of the Revised 508 Standards or Revised 255 Guidelines.

• 302.1 Without Vision - Where a visual mode of operation is provided, ICT shall provide at least one mode of operation that does not require user vision.

• 302.2 With Limited Vision - Where a visual mode of operation is provided, ICT shall provide at least one mode of operation that enables users to make use of limited vision.

• 302.3 Without Perception of Color - Where a visual mode of operation is provided, ICT shall provide at least one visual mode of operation that does not require user perception of color.

• 302.4 Without Hearing - Where an audible mode of operation is provided, ICT shall provide at least one mode of operation that does not require user hearing.

• 302.5 With Limited Hearing - Where an audible mode of operation is provided, ICT shall provide at least one mode of operation that enables users to make use of limited hearing.

• 302.6 Without Speech - Where speech is used for input, control, or operation, ICT shall provide at least one mode of operation that does not require user speech.

• 302.7 With Limited Manipulation - Where a manual mode of operation is provided, ICT shall provide at least one mode of operation that does not require fine motor control or simultaneous manual operations.

• 302.8 With Limited Reach and Strength - Where a manual mode of operation is provided, ICT shall provide at least one mode of operation that is operable with limited reach and limited strength.

• 302.9 With Limited Language, Cognitive, and Learning Abilities - ICT shall provide features making its use by individuals with limited cognitive, language, and learning abilities simpler and easier.

5 Deliverables The contractor shall provide deliverables as described in subsequent task orders. Deliverables shall be specified by the government. Format and delivery schedule for deliverables shall be outlined in CDRLs and/or other means TBD.

Number Name Frequency Quantity

A001 Storage Systems 11

A002 Server Compute Systems 33

A003 Top of Rack Switches 22

A004 Rack and Power options 11

Sample Configuration (Small)

Acme Storage Solution 100 TB

Acme Server x 3

Acme Switches x 2

Acme Power (optional)

Acme Professional Services