SANnav_PD_RFI.pdf

PDF 780 KB Posted

Attached to
SANnav Management Portal Software License
Solicitation number
36C10B24Q0419
Issued by

About this file

This document is a Product Description (PD) for the SANnav Management Portal Software required by the Department of Veterans Affairs (VA) Electronic Health Record Modernization Integration Office (EHRM-IO). The key requirements include a unified monitoring and performance solution for the Brocade/Broadcom Fiber Channel network, with capabilities such as configuration, real-time monitoring, historical analysis, alerting, and reporting. The software must be compatible with and supported by Brocade/Broadcom, and run on specific versions of Linux. The period of performance is from September 1, 2024 to August 31, 2029, with a base year and four option years. The acquisition is a firm-fixed price Brand Name or equal procurement on the NASA Solutions for Enterprise-Wide Procurement (SEWP) V contract. The PD also includes federal accessibility (Section 508) requirements, general IT requirements, and software and licensing requirements. This PD is associated with a pre-solicitation for the SANnav Management Portal Software License, which is set aside for Service-Disabled Veteran-Owned Small Businesses (SDVOSBs) and Veteran-Owned Small Businesses (VOSBs). Responses to the RFI are due by July 25, 2024.

View the file

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

PRODUCT DESCRIPTION (PD)

DEPARTMENT OF VETERANS AFFAIRS

Electronic Health Record Modernization Integration Office (EHRM-IO)

SANnav Management Portal Software

Date : July 8, 2024

VA-24-00078397

PD Version Number: 1.0

DRAFT

SANnav Management Portal Software (24REQ0004c) TAC Number: VA-24-00078397

CONTENTS

1.0 PRODUCT REQUIREMENTS

1.1 SALIENT Characteristics

2.0 NOTICE OF THE FEDERAL ACCESSIBILITY LAW AFFECTING ALL

INFORMATION AND COMMUNICATION TECHNOLOGY (ICT)

PROCUREMENTS (SECTION 508)

2.1 SECTION 508 – INFORMATION AND COMMUNICATION TECHNOLOGY (ICT)

STANDARDS

2.2 COMPATABILITY WITH ASSISTIVE TECHNOLOGY

2.3 ACCEPTANCE AND ACCEPTANCE TESTING

3.0 SHIPMENT OF SOFTWARE AND SOFTWARE LICENSES

4.0 GENERAL REQUIREMENTS

4.1 VA TECHNICAL REFERENCE MODEL

4.2 SOCIAL SECURITY NUMBER (SSN) REDUCTION

4.3 INTERNET PROTOCOL VERSION 6 (IPV6)

5.0 SOFTWARE AND LICENSING REQUIREMENTS

1.0 PRODUCT REQUIREMENTS

The Department of Veterans Affairs (VA) Electronic Health Record Modernization Integration Office (EHRM-IO) has a requirement to renew brand name or equal Broadcom (Hewlett Packard Enterprise (HPE)) SANnav Management Portal software.

The EHRM-IO Data Migration/Syndication Fiber Channel network is a Brocade/Broadcom network that includes more than 1228 ports connected to more than 25 Storage Area Network (SAN) arrays. Fiber Channel is used as the primary data interface between SAN storage and servers. The data is constantly moving from server to server. Renewal of the SANnav Management Portal license is required so that system administrators (SAs) can continue to visualize the health and performance of the entire Brocade/Broadcom Fiber Channel network in real time. Migration of Veteran patient data to Oracle Health and syndication of data back to the VA environment requires high performance and high system availability. SANnav Management Portal provides a single monitor to oversee all the activity on the Data Migration/Syndication Fiber Channel network, which allows SAs to quickly identify problem areas and take corrective action expediently. This capability enables SAs to maximize performance, avoid congestion, and optimize resources on the Data Migration/Syndication Fiber Channel network, thereby facilitating successful movement of all relevant VA/VistA data into the Oracle Health environment and syndication of Oracle Health data back into VA for analytics and reporting purposes.

This acquisition is a firm-fixed price Brand Name or equal procurement on National Aeronautics and Space Administration (NASA) Solutions for Enterprise-Wide Procurement (SEWP) V Governmentwide Acquisition Contract (GWAC). The period of performance shall be September 1, 2024 – August 31, 2025, for the base year, plus four

(4) option years starting September 1, 2025, and ending on August 31, 2029.

BASE PERIOD: 9/1/2024 to 8/31/2025

ITEM # PART NUMBER DESCRIPTION QTY

0001 R3P46AAE HPE SANnav Management Portal Enterprise

1yr E-LTU - Storage Networking

To include support for switches with the following serial numbers:

DZH3011N031

CZC1362PTC

DZH3011N032

CZC214235H

OPTION YEAR 1: 9/1/2025 to 8/31/2026

ITEM # PART NUMBER DESCRIPTION QTY

1001 R3P46AAE HPE SANnav Management Portal Enterprise

1yr E-LTU - Storage Networking

To include support for switches with the following serial numbers:

DZH3011N031

CZC1362PTC

OPTION YEAR 2: 9/1/2026 to 8/31/2027

2001 R3P46AAE HPE SANnav Management Portal Enterprise

1yr E-LTU - Storage Networking

To include support for switches with the following serial numbers:

DZH3011N031

CZC1362PTC

OPTION YEAR 3: 9/1/2027 to 8/31/2028

3001 R3P46AAE HPE SANnav Management Portal Enterprise

1yr E-LTU - Storage Networking

To include support for switches with the following serial numbers:

DZH3011N031

CZC1362PTC

OPTION YEAR 4: 9/1/2028 to 8/31/2029

4001 R3P46AAE HPE SANnav Management Portal Enterprise

1yr E-LTU - Storage Networking

To include support for switches with the following serial numbers:

DZH3011N031

CZC1362PTC

1.1 SALIENT CHARACTERISTICS

The Government requires that the SANnav Management Portal software procured with this action provide ALL the following salient characteristics:

1. Must support a unified monitoring and performance solution for a Brocade/Broadcom Fiber Channel network.

• Must provide a single browser-based graphical user interface (GUI) that allows users to configure and monitor the Brocade/Broadcom Fiber Channel network and to view performance statistics.

• Configuration capabilities must include the ability to configure multiple SAN switches and provision multiple devices to SAN fabrics at the same time by applying configurations with policy-based configuration management.

• General monitoring capabilities must include the ability to drill down to view historical or real-time input/output (I/O) traffic on any point of interest (SAN switch, port, extension tunnel, extension circuit, or flow).

• Performance monitoring capabilities must include:

i. A heath summary dashboard that allows users to view summary health scores for fabrics, switches, hosts, and targets that may be contributing to performance issues within the network.

ii. A network port traffic dashboard that allows users to identify congested or oversubscribed fabric ports (up to the minute) and lists the topmost congested or oversubscribed ports over a period of time (up to the last 2 hours) for further investigation.

iii. Context-based topology views that allow visualize relevant contextual information such as directly connected entities in the data path and all end-point physical devices connected to a specific device (such as a particular switch).

2. Must be compatible with and supported by Brocade/Broadcom.

3. Must support minimum versions of Linux software:

• Must run on Red Hat Enterprise Linux, version 7.5 or higher.

• Must run CentOS Linux, version 7.5 or higher.

4. Must provide visibility across all fabrics simultaneously with a single monitor (also known as a single pane of glass) to all the physical, and virtual layers of the Fiber Channel network.

5. Must streamline common workflows:

• Configuration: configure SAN switches and provision devices to fabrics.

• Zoning: partition the Fiber Channel fabric into smaller subsets to restrict interference, add security, and simplify management.

6. Must provide a view of fabric topology based on context (host, target, fabric, zone, etc.) and support the capability to search by various contexts, such as switches, switch ports, hosts, host ports, virtual machines (VMs), storage, and storage ports.

7. Must provide log analyses of historical and real-time data.

8. Must send automated performance reports via email. The software must have the capability to gather performance reports and email them to specified system administrators at specified time intervals (what reports to email and how often to email them must be configurable).

9. Must send alerts via email real-time as hardware issues occur. In other words, when a hardware issue occurs, the software must immediately detect it and send an alert via email.

10. All performance and error reports must be analyzable by Brocade/Broadcom. In other words, performance and error reports must include language that allows Brocade/Broadcom to interpret performance metrics and error messages to assist with troubleshooting.

2.0 NOTICE OF THE FEDERAL ACCESSIBILITY LAW AFFECTING ALL

INFORMATION AND COMMUNICATION TECHNOLOGY (ICT)

PROCUREMENTS (SECTION 508)

On January 18, 2017, the Architectural and Transportation Barriers Compliance Board (Access Board) revised and updated, in a single rulemaking, standards for electronic and information technology developed, procured, maintained, or used by Federal agencies covered by Section 508 of the Rehabilitation Act of 1973, as well as our guidelines for telecommunications equipment and customer premises equipment covered by Section 255 of the Communications Act of 1934. The revisions and updates to the Section 508-based standards and Section 255-based guidelines are intended to ensure that information and communication technology (ICT) covered by the respective statutes is accessible to and usable by individuals with disabilities.

2.1 SECTION 508 – INFORMATION AND COMMUNICATION TECHNOLOGY

(ICT) STANDARDS

The Section 508 standards established by the Access Board are incorporated into, and made part of all VA orders, solicitations and purchase orders developed to procure ICT.

These standards are found in their entirety at: https://www.access-board.gov/guidelines-and-standards/communications-and-it/about-the-ict-refresh/final-rule/text-of-the-standards-and-guidelines. A printed copy of the standards will be supplied upon request.

Federal agencies must comply with the updated Section 508 Standards beginning on January 18, 2018. The Final Rule as published in the Federal Register is available from the Access Board: https://www.access-board.gov/guidelines-and-standards/communications-and-it/about-the-ict-refresh/final-rule.

The Contractor shall comply with “508 Chapter 2: Scoping Requirements” for all electronic ICT and content delivered under this contract. Specifically, as appropriate for the technology and its functionality, the Contractor shall comply with the technical standards marked here:

E205 Electronic Content – (Accessibility Standard -WCAG 2.0 Level A and AA Guidelines)

E204 Functional Performance Criteria E206 Hardware Requirements E207 Software Requirements E208 Support Documentation and Services Requirements

2.2 COMPATABILITY WITH ASSISTIVE TECHNOLOGY

The standards do not require installation of specific accessibility-related software or attachment of an assistive technology device. Section 508 requires that ICT be compatible with such software and devices so that ICT can be accessible to and usable by individuals using assistive technology, including but not limited to screen readers, screen magnifiers, and speech recognition software.

2.3 ACCEPTANCE AND ACCEPTANCE TESTING

Deliverables resulting from this solicitation will be accepted based in part on satisfaction of the Section 508 Chapter 2: Scoping Requirements standards identified above.

The Government reserves the right to test for Section 508 Compliance before delivery.

The Contractor shall be able to demonstrate Section 508 Compliance upon delivery.

https://www.access-board.gov/guidelines-and-standards/communications-and-it/about-the-ict-refresh/final-rule/text-of-the-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 https://www.access-board.gov/guidelines-and-standards/communications-and-it/about-the-ict-refresh/final-rule/text-of-the-standards-and-guidelines https://www.access-board.gov/guidelines-and-standards/communications-and-it/about-the-ict-refresh/final-rule https://www.access-board.gov/guidelines-and-standards/communications-and-it/about-the-ict-refresh/final-rule

3.0 SHIPMENT OF SOFTWARE AND SOFTWARE LICENSES

Inspection: Destination Acceptance: Destination Free on Board (FOB): Destination

Ship To and Mark For: ALL DELIVERY SHALL BE ELECTRONIC DELIVERY OF

SOFTWARE AND SOFTWARE LICENSES TO:

Primary Alternate Name: Augie Turano Name: Joe Kopra Address: Address:

Voice: 412-241-0217 Voice: (623) 330-0692 Email: Augie.turano@va.gov Email: Joseph.Kopra@va.gov

4.0 GENERAL REQUIREMENTS

4.1 VA TECHNICAL REFERENCE MODEL

The Contractor shall support the VA enterprise management framework. In association with the framework, the Contractor shall comply with OIT Technical Reference Model (VA TRM). The VA TRM is one component within the overall Enterprise Architecture (EA) that establishes a common vocabulary and structure for describing the information technology used to develop, operate, and maintain enterprise applications. Moreover, the VA TRM, which includes the Standards Profile and Product List, serves as a technology roadmap and tool for supporting OIT. Architecture & Engineering Services (AES) has overall responsibility for the VA TRM.

4.2 SOCIAL SECURITY NUMBER (SSN) REDUCTION

The Contractor solution shall support the Social Security Number (SSN) Fraud Prevention Act (FPA) of 2017 which prohibits the inclusion of SSNs on any document sent by mail. The Contractor support shall also be performed in accordance with Section 240 of the Consolidated Appropriations Act (CAA) 2018, enacted March 23, 2018, which mandates VA to discontinue using SSNs to identify individuals in all VA information systems as the Primary Identifier. The Contractor shall ensure that any new IT solution discontinues the use of SSN as the Primary Identifier to replace the SSN with the Integrated Control Number (ICN) in all VA information systems for all individuals. The Contractor shall ensure that all Contractor delivered applications and systems integrate with the VA Master Person Index (MPI) for identity traits to include the use of the ICN as the Primary Identifier. The Contractor solution may only use a Social Security Number to identify an individual in an information system if and only if the use of such number is required to obtain information VA requires from an information system that is not under the jurisdiction of VA.

4.3 INTERNET PROTOCOL VERSION 6 (IPV6)

The Contractor solution shall support Internet Protocol Version 6 (IPv6) based upon the memo issued by the Office of Management and Budget (OMB) on November 19, 2020 (https://www.whitehouse.gov/wp-content/uploads/2020/11/M-21-07.pdf). IPv6 technology, in accordance with the USGv6 Program (https://www.nist.gov/programs-projects/usgv6-program/usgv6-revision-1), NIST Special Publication (SP) 500-267B Revision 1 “USGv6 Profile” (https://doi.org/10.6028/NIST.SP.500-267Br1), and NIST SP 800-119 “Guidelines for the Secure Deployment of IPv6” (https://doi.org/10.6028/NIST.SP.800-119), compliance shall be included in all IT infrastructures, application designs, application development, operational systems and sub-systems, and their integration. In addition to the above requirements, all devices shall support native IPv6 and dual stack (IPv6 / IPv4) connectivity without additional memory or other resources being provided by the Government, so that they can function in a mixed environment. All public/external facing servers and services (e.g. web, email, DNS, ISP services, etc.) shall support native IPv6 and dual stack (IPv6 / IPv4) users and all internal infrastructure and applications shall communicate using native IPv6 and dual stack (IPv6 / IPv4) operations.

5.0 SOFTWARE AND LICENSING REQUIREMENTS

The Contractor shall be responsible for the provision of all software licenses and any associated licensing maintenance required for any development, delivery, integration, operation, and/or maintenance associated with its proposed application(s), software products, software solution, and/or system including, but not limited to, any and all application(s), software and/or software products that comprise, are a part of, or integrate with the Contractor’s proposed application(s), software products, software solution, and/or system for the life of any resulting contract.

https://www.whitehouse.gov/wp-content/uploads/2020/11/M-21-07.pdf file://R04.med.va.gov/V03/EAS/Users/vhaeasWymbsk/TEMPLATES--NEW%20TAC%20PROCESS/PWS%20TEMPLATE%20(DO%20NOT%20TOUCH)%20-%20In%20Process%20Revisions/DO%20NOT%20TOUCH%20(next%20version/IPv6/(https:/www.nist.gov/programs-projects/usgv6-program/usgv6-revision-1 file://R04.med.va.gov/V03/EAS/Users/vhaeasWymbsk/TEMPLATES--NEW%20TAC%20PROCESS/PWS%20TEMPLATE%20(DO%20NOT%20TOUCH)%20-%20In%20Process%20Revisions/DO%20NOT%20TOUCH%20(next%20version/IPv6/(https:/www.nist.gov/programs-projects/usgv6-program/usgv6-revision-1 https://doi.org/10.6028/NIST.SP.500-267Br1 https://doi.org/10.6028/NIST.SP.800-119

POINTS OF CONTACT

VA Program Manager:

Name: Augie Turano Address:

Voice: 412-241-0217 Email: Augie.Turano@va.gov

Contracting Officer’s Representative:

Name: Starlyn Reed Address:

Voice: 202-910-7491 Email: Starlyn.Reed@va.gov

Contracting Officer:

Name: Wendella Baptiste Address:

Voice: 848-377-5155 Email: Wendella.baptiste@va.gov

Contract Specialist:

Name: Kimberly Stansbury Address:

Voice: 848-377-5204 Email: Kimberly.stansbury@va.gov mailto:Augie.Turano@va.gov mailto:Starlyn.Reed@va.gov mailto:Wendella.baptiste@va.gov mailto:Kimberly.stansbury@va.gov

1.0 PRODUCT REQUIREMENTS
1.1 SALIENT Characteristics
2.0 NOTICE OF THE FEDERAL ACCESSIBILITY LAW AFFECTING ALL INFORMATION AND COMMUNICATION TECHNOLOGY (ICT) PROCUREMENTS (SECTION 508)
2.1 SECTION 508 – INFORMATION AND COMMUNICATION TECHNOLOGY (ICT) STANDARDS
2.2 COMPATABILITY WITH ASSISTIVE TECHNOLOGY
2.3 ACCEPTANCE AND ACCEPTANCE TESTING
3.0 SHIPMENT OF SOFTWARE AND SOFTWARE LICENSES
4.0 GENERAL REQUIREMENTS
4.1 VA TECHNICAL REFERENCE MODEL
4.2 SOCIAL SECURITY NUMBER (SSN) REDUCTION
4.3 INTERNET PROTOCOL VERSION 6 (IPV6)

5.0 SOFTWARE AND LICENSING REQUIREMENTS

File details come from the government source that posted it. Updated .