P01 FY25 PD IBM-MVS zSAM draft.pdf

PRODUCT DESCRIPTION (PD)

DEPARTMENT OF VETERANS AFFAIRS

Office of Information Technology (OIT) Infrastructure Operations (IO)

Software Licenses and Maintenance

For IBM-MVS Z Software Asset Management (ZSAM)

Date: March 27, 2025

VA-25-00036936

PD Version Number: DRAFT

Software Licenses and Maintenance for IBM Z Software Asset Management

(ZSAM)

TAC Number: VA-25-00036936

1.0 PRODUCT REQUIREMENTS

The Department of Veterans Affairs (VA), Office of Information Technology (OIT), Infrastructure Operations (IO) requires purchase of requires perpetual software licenses and maintenance for the following IBM Z Software Asset Management (ZSAM). The IBM ZSAM software will create, automate and maintain zEnterprise server software inventory. Enhances security posture by identifying obsolete and unsupported software.

IBM ZSAM is built on the concept of remote and central mainframe components which work together to produce reports on z/OS® mainframe products and their usage. This section provides you with a high-level overview of the IBM ZSAM core architecture.

IBM ZSAM runs on z/Architecture® mainframes that use the z/OS operating system. Its purpose is to:

• Discover and identify products for the z/OS platform.

• Monitor software usage and trends.

• Report on the MSU capacity of each system under which the product runs.

• Provide reporting functions for assets and usage.

The benefits of using this software are:

• Used and unused software are identified.

• Users of software are identified.

• Obsolete versions of software are identified and the usage of these versions determined.

• Usage trends of software and libraries are identified.

In a z/OS environment, software is contained in load libraries or as z/OS UNIX™ executable files. IBM ZSAM scans contents of these libraries and executable files to determine which software products are installed. IBM ZSAM also monitors the loaded programs and executable files to measure software usage.

The discovered load libraries and executable files are then checked against a global database of product information. IBM ZSAM uses this information to determine which products are installed and used on each system.

The IBM ZSAM Maintenance will consist of software upgrades and updates to include point releases, service releases and security release of applicable software on a quarterly basis and/or within 48 hours in cases in which a high-risk vulnerability fix becomes available. These software upgrades and updates are necessary for IO to ensure complete and accurate accounting of mainframe software assets which support existing IO systems and applications.

The Contractor shall provide one (1) telephone number and a Point of Contact for VA to utilize open maintenance support calls. The required full level of service includes 24 hours per day, 7 days per week telephone and online coverage with a two (2) hour response time. All VA support calls will be initiated by the VA designated Point of

Contact. The Contractor shall provide secure connection capabilities for the downloading of software updates and uploading of diagnostic information.

The IBM-MVS ZSAM Maintenance will consist of software upgrades and updates to include point releases, service releases and security release of applicable software on a quarterly basis and within 48 hours in cases in which a high-risk vulnerability fix becomes available. These software upgrades and updates are necessary for IO to ensure complete and accurate accounting of mainframe software assets which support existing IO systems and applications.

The Contractor shall provide one (1) telephone number and/or a point of contact for VA to contact and opening maintenance service calls. The Contractor shall provide secure connection capabilities for the downloading of software updates and the uploading of diagnostic information. The preferred protocol for transfer is Secure File Transfer Protocol (SFTP).

The Period of Performance (PoP) is May 1, 2025 through April 30, 2026, with 2 (two) 12-month option periods..

This requirement is for Software Licenses and Maintenance for IBM-MVS Z Software Asset Management (ZSAM) as identified in the table below. The Contractor will provide the following:

Base Period

Item No Product Description QTY Unit

Control No: SW5193.SW Description: IBM z Software Asset Managent (zSAM)-License

License Metric: Per VU (Value Unit) License Duration: Perpetual

OEM: IBM

Mfg Part No: 5698-AA4 Quantity: 106 (VUs)

Customer No: 9294155 Mfg Model No: 3931-409; 3932-B03 HW Serial No: AEAB8; AEAC8 SW Serial No: TBD MCC: A00 AppCode: CPS Location: AITC

1 Lot

Control No: SW5193.SWM Description: IBM z Software Asset Managent (zSAM)-Maintenance

License Metric: Per VU (Value Unit) License Duration: Perpetual

OEM: IBM

Mfg Part No: 5698-R28 Quantity: 106 (VUs)

Customer No: 9294155 Mfg Model No: 3931-409; 3932-B03 HW Serial No: AEAB8; AEAC8 SW Serial No: TBD MCC: A00 AppCode: CPS Location: AITC

1 Lot

Deliverable: Deliverable Support Information in accordance with (IAW) Section 1.1 of the

PD

NSP NSP

Option Period One

The Period of Performance is May 1, 2026 through April 30, 2027 unless otherwise noted in the Description block in the table below.

Control No: SW5193.SWM Description: IBM z Software Asset Managent (zSAM)-Maintenance

License Metric: Per VU (Value Unit) License Duration: Perpetual

OEM: IBM

Mfg Part No: 5698-R28 Quantity: 106 (VUs)

Customer No: 9294155 Mfg Model No: 3931-409; 3932-B03 HW Serial No: AEAB8; AEAC8 SW Serial No: TBD MCC: A00 AppCode: CPS Location: AITC

1 Lot

Deliverable Deliverable Support Information IAW Section 1.1 of the PD.

Option Period Two The Period of Performance is May 1, 2028 through April 30, 2028 unless otherwise noted in the Description block in the table below.

2001 Control No: SW5193.SWM Description: IBM z Software Asset Managent (zSAM)-Maintenance

License Metric: Per VU (Value Unit) License Duration: Perpetual

OEM: IBM

Mfg Part No: 5698-R28 Quantity: 106 (VUs)

Customer No: 9294155 Mfg Model No: 3931-409; 3932-B03 HW Serial No: AEAB8; AEAC8 SW Serial No: TBD MCC: A00 AppCode: CPS Location: AITC

1 Lot

2002 Deliverable: Deliverable Support Information in accordance with (IAW) Section 1.1 of the

PD

1.1 DELIVERABLE SUPPORT INFORMATION

The Contractor shall complete the Deliverable Support Information form (DSI) for maintenance support. The Contractor shall fill in blocks 15-32. Note for Multiple CLINs:

For asset specific information that applies to multiple CLINs, provide an attachment correlating any asset specific information to specific CLINS. (For example: Serial Numbers or License Keys). The Contractor shall provide Original Equipment Manufacturer (OEM) confirmation that all software support or licenses have been purchased. The Contractor shall provide service call instructions to include all information required to obtain maintenance, support or licenses. The form shall be submitted electronically to: VA PM, COR, CO and AACLicense@va.gov.

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 https://vaww.aams.ecms.va.gov/AAMS_Production/DAV/fhhyyyymyytqs6-y/AACLicense@va.gov 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 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.

3.0 INFORMATION TECHNOLOGY USING ENERGY-EFFICIENT PRODUCTS

Not Applicable

3.1 EPEAT

EPEAT product compliance is not required in this acquisition.

3.2 ENERGY STAR

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

Energy Star compliance is not required in this acquisition.

3.3 FEMP

FEMP or FEMP low standby power product compliance is not required in this acquisition.

4.0 SYSTEM ACCEPTANCE (PRE-PRODUCTION) TESTING

5.0 SHIPMENT OF SOFTWARE

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

Ship To and Mark For: Delivery of software licenses and/or maintenance shall be submitted electronically.

Name:

Email:

Name:

Address:

Email:

5.1 SPECIAL SHIPPING INSTRUCTIONS

5.2 NATIONAL ACQUISITIONS

Not Applicable

6.0 GENERAL REQUIREMENTS

6.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.

6.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.

6.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.

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

6.4 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.

6.5 POSITION/TASK RISK DESIGNATION LEVEL(S)

INFORMATION SECURITY CONSIDERATIONS:

The Assessment and Authorization (A&A) requirements do not apply and a Security Accreditation Package is not required

All VA sensitive information shall be protected at all times in accordance with local security field office System Security Plans (SSP’s) and Authority to Operate (ATO)’s for all systems/LAN’s accessed while performing the tasks detailed in this Product Description.

A prohibition on unauthorized disclosure: “Information made available to the Contractor or Subcontractor by VA for the performance or administration of this contract or information developed by the Contractor/Subcontractor in performance or administration of the contract shall be used only for those purposes and shall not be used in any other way without the prior written agreement of the VA.” This clause expressly limits the Contractor/Subcontractor’s rights to use data as described in Rights in Data – General, FAR 52.227-14(d).(1).

A requirement for data breach notification: Upon discovery of any known or suspected security/privacy incidents, or any unauthorized disclosure of sensitive information, including that contained in system(s) to which the Contractor/Subcontractor has access, the Contractor/Subcontractor shall immediately notify the COR and simultaneously, the designated ISO, and Privacy Officer for the contract. The term “security incident” means an event that has, or could have, resulted in unauthorized access to, loss or damage to VA assets, or sensitive information, or an action that breaches VA security procedures. See VA Handbook 6500.6, Appendix C, paragraph 6.a.

A requirement to pay liquidated damages in the event of a data breach: “In the event of a data breach or privacy incident involving SPI the contractor processes or maintains under this contract, the contractor shall be liable to VA for liquidated damages for a specified amount per affected individual to cover the cost of providing credit protection services to those individuals.” However, it is the policy of VA to forgo collection of liquidated damages in the event the Contractor provides payment of actual damages in an amount determined to be adequate by the agency.

Based on the determinations of the independent risk analysis, the Contractor shall be responsible for paying to VA liquidated damages in the amount of $37.50 per affected individual to cover the cost of providing credit protection services to affected individuals consisting of the following:

1) Notification;

2) One year of credit monitoring services consisting of automatic daily monitoring of at least 3 relevant credit bureau reports;

3) Data breach analysis;

4) Fraud resolution services, including writing dispute letters, initiating fraud alerts and credit freezes, to assist affected individuals to bring matters to resolution;

5) One year of identity theft insurance with $20,000.00 coverage at $0 deductible; and

6) Necessary legal expenses the subjects may incur to repair falsified or damaged credit records, histories, or financial affairs

A requirement for annual security/privacy awareness training: “Before being granted access to VA information or information systems, all Contractor employees and Subcontractor employees requiring such access shall complete on an annual basis either: (i) the VA security/privacy awareness training (contains VA security/privacy requirements) within 1 week of the initiation of the contract, or (ii) security awareness training provided or arranged by the contractor that conforms to VA’s security/privacy requirements as delineated in the hard copy of the VA security awareness training provided to the Contractor. If the Contractor provides their own training that conforms to VA’s requirements, they will provide the COR or CO, a yearly report (due annually on the date of the contract initiation) stating that all applicable employees involved in VA’s contract have received their annual security/privacy training that meets VA’s requirements and the total number of employees trained. See VA Handbook 6500.6, Appendix C, paragraph 9.

A requirement to sign VA’s Rules of Behavior: “Before being granted access to VA information or information systems, all Contractor employees and Subcontractor employees requiring such access shall sign on annual basis an acknowledgement that they have read, understand, and agree to abide by VA’s Contractor Rules of Behavior which is attached to this contract.” See VA Handbook 6500.6, Appendix C, paragraph 9, and Appendix D. Note: If a medical device vendor anticipates that the services under the contract will be performed by 10 or more individuals, the Contractor Rules of Behavior may be signed by the vendor’s designated representative. The contract must reflect by signing the Rules of Behavior on behalf of the vendor that the designated representative agrees to ensure that all such individuals review and understand the Contractor Rules of Behavior when accessing VA’s information and information systems.