About this file

This is a Product Description document for a Department of Veterans Affairs (VA) federal contract opportunity for the initial outfitting, transition, and activation of a PAR Excellence Weight Based Inventory Management System at the East Indianapolis VA Clinic.

The contract requires delivery of brand-name PAR Excellence hardware and components, including 7 PX9186 PAR Bins Replenish Licenses, 871 individual scales, 102 small/medium platform scales, 102 large platform scales, 8 controllers, 1 set of PAR hardware accessories, 1 set of plastic storage bins, 23 bridge allocations, and 38 QS-LR36 qwikSIGHT mobile louvered panel units. Services required include third-party services and 100 hours of onsite implementation and setup. Delivery must occur between March 1, 2027 and March 30, 2027 to the East Indianapolis VA Clinic at 9402 East 21st Street, Indianapolis, Indiana 46229, with installation completed the same day as delivery during normal loading dock business hours (8:00 AM to 3:30 PM Eastern Time, Monday through Friday, excluding federal holidays). The contractor is responsible for all assembly, installation, calibration, staging requirements, cleanup, and disposal of materials, with vendor accountability for any damage to building finishes. Products must be unused, not refurbished, manufactured within 24 months of purchase order issuance, and have batteries manufactured within 12 months. The contractor must submit quarterly Price and Utilization Reports using the OMB M-26-10 Template and comply with comprehensive Section 508 accessibility standards, VA cybersecurity and privacy requirements, Zero Trust critical security controls, IPv6 support, software licensing provisions, Trusted Internet Connection standards, and personnel security vetting procedures including background investigations for all contractor staff with facility access.

View the file

Other files

File Type Posted
36C10B27Q0140.docx DOCX document

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

DEPARTMENT OF VETERANS AFFAIRS (VA)

Veterans Health Administration Veteran Health Indiana, East Indianapolis VA Clinic for

PAR Excellence Weight Based Inventory Management System Initial Outfitting, Transition, and Activation

Date: October 7, 2026 PD Version: 1.0

Contents

1.0 PRODUCT REQUIREMENTS

1.1 <ITEM 1 SALIENT CHARACTERISTIC(S)> (Add additional items as needed) Error! Bookmark not defined.

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 INFORMATION TECHNOLOGY USING SUSTAINABLE PRODUCTS

4.0 SHIPMENT OF HARDWARE OR EQUIPMENT

4.1 SPECIAL SHIPPING INSTRUCTIONS

4.2 NATIONAL ACQUISITIONS

5.0 GENERAL REQUIREMENTS

5.1 VA TECHNICAL REFERENCE MODEL

5.2 ZERO TRUST – VA CRITICAL SECURITY CONTROLS

5.3 SOCIAL SECURITY NUMBER (SSN) REDUCTION

5.4 INTERNET PROTOCOL VERSION 6 (IPV6)

5.5 SOFTWARE AND LICENSING REQUIREMENTS

5.6 TRUSTED INTERNET CONNECTION (TIC)

5.7 GENERATIVE ARTIFICIAL INTELLIGENCE REQUIREMENTS

5.7.1 AI SYSTEM/LLM DEVELOPMENT AND OPERATION

DOCUMENTATION REQUIREMENTS .................... Error! Bookmark not defined.

5.7.2 MONITORING, REPORTING, AND CORRECTIVE ACTION ............ Error!

Bookmark not defined.

5.7.3 AI MODEL UPDATES AND CHANGE DISCLOSURES .. Error! Bookmark not defined.

5.8 SOURCE CODE HARMONIZATION AND REUSE IN INFORMATION

TECHNOLOGY (SHARE IT Act)

6.0 SECURITY AND PRIVACY REQUIREMENTS

6.1 POSITION/TASK RISK DESIGNATION LEVEL(S)

6.2 CONTRACTOR PERSONNEL SECURITY REQUIREMENTS

ADDENDUM B – VA INFORMATION AND INFORMATION SYSTEM SECURITY/

PRIVACY LANGUAGE .................................................... Error! Bookmark not defined.

1.0 PRODUCT REQUIREMENTS

The Veterans Health Administration (VHA) Veteran Health Indiana East Indianapolis VA Clinic (Indy East) has a requirement for Brand Name PAR Excellence Weight Based Inventory Management Systems (WBIM) and associated components as described herein. This requirement supports the initial outfitting, transition, and activation (IOT&A) efforts of the Indy East clinic.

1.1 PRODUCTS

The table below summarizes the required products:

Description Quantity PX9186 PAR Bins Replenish License 7 Scale - Avg Cost for PAR Individual Scales 871 Scale - Avg Cost for PAR Individual Scales (15k) 17 Small & Medium Platform Scales 102 Large Platform Scales 102 Controller, Replenish, Ethernet 8 PAR Hardware Accessories 1 Plastic Storage Bins 1 Bridge Allocation (unit plus sides/front) 23 QS-LR36 qwikSIGHT Mobile Louvered Panel Units, 36"

1.2 SERVICES

The table in Section 1.2 (Services) below summarizes the required services:

Description Unit of Issue

Quantity

Third party services Ea 1 Onsite Implementation and set up Hours 100

1.3 DELIVERY/INSTALLATION/TRAINING SCHEDULE

Delivery Site:

East Indianapolis VA Clinic (East Indy) 9402 East 21st Street Indianapolis, IN 46229

The Contractor shall deliver all products and items necessary for the contractor to complete installation of the East Indy PAR Excellence Weight Based Inventory Management System. Delivery shall be to the delivery site identified above.

The Government’s delivery/installation schedule is based on the current construction timeline and considering the nature of activation efforts. It may change as dates fluctuate, so delivery/installation dates must remain flexible. The contractor shall deliver/install all products no earlier than the estimated delivery/installation start date of March 1, 2027, and no later than the estimated delivery/installation end date of March 30, 2027.

The delivery of all products depends on the completion of construction in relevant areas within the building. If any delay occurs with the construction or building acceptance, the vendor may need to adjust the delivery date at no cost to the Government. VA does not anticipate a need for the delivery/installation date to be delayed, but any delay will not be longer than 30 days. The Contractor will coordinate with the on-site points of contact prior to delivery.

The VA activations team will confirm the specific delivery/installation date (within the above range) with the awardee upon award.

Post-award, the vendor will coordinate delivery/installation identified in this document with the VA before beginning any work (See Section 2.3). Once the dates have been confirmed, modifications to the schedule are subject to written approval by the Contracting Officer (CO), Contracting Officer Representative (COR), and the vendor.

The delivery/installation of items identified in this document shall occur during normal loading dock business hours, which are defined as 8:00 AM to 3:30 PM Eastern Standard Time, Monday through Friday, excluding Federal Holidays.

Delivery trucks are not permitted to remain at the receiving area. Trucks shall be unloaded, moved from the receiving area, and then brought back to the receiving area if necessary to haul out any waste, tools, or excess materials.

Installation shall be completed the same day equipment is delivered.

1.4 STAGING REQUIREMENTS

The vendor must outline the need for a staging area to facilitate item assembly and installation, if necessary. After the award, this information will be verified with the vendor.

The vendor is responsible for any damage to the building and finishes incurred by their team or associated subcontractors. The vendor must protect doors, walls, corners, and flooring prior to starting installation and provide proper protection for the building during installation.

The vendor will be accountable for covering the costs and repairing any damage or deficiencies noted in finished spaces and surfaces resulting from the vendor’s installation or associated subcontractors.

1.5 ASSEMBLY, INSTALLATION, AND CALIBRATION

The vendor must manage and coordinate the installation with the VA Activations and IOT&A contractor teams.

On-site assembly and installation of items, and performance of services identified in this document shall take place during normal business hours which are defined as: 8:00 AM to 3:30 PM Eastern Standard Time, Monday through Friday, and excluding Federal Holidays.

The vendor is required to provide tools, labor, and materials to complete assembly and installation of the items detailed in this document.

Throughout the assembly and installation process, the vendor will have a qualified representative on-site as the vendor’s contact, serving as the liaison between the vendor and the East Indy clinic. This on-site representative may also be the installer.

Whenever a vendor representative is present at the East Indy clinic, the instructions from the COR to the representing party will be binding as if given to the vendor’s primary contact. While the COR may provide specific instructions, only the Contracting Officer has the authority to modify the terms or conditions of the contract.

During installation, if there are any potential problems (e.g., Furniture, Fixtures & Equipment (FF&E) blocking or interfering with outlets, thermostats, sprinkler heads, etc.), the vendor and/or installer must report the issue to the onsite project manager as soon as it is discovered.

The Vendor is to ensure that all products and components are in working order and run a complete operational cycle through as needed. After installation, the vendor must inspect all products for proper operation and defects and perform a final cleaning.

After the assembly and installation, the vendor must complete the calibration procedures outlined by the Original Equipment Manufacturer (OEM).

The vendor shall submit all documentation related to function and electrical testing, calibration, and overall product acceptance of OEM standards to the on-site Project Manager and VA Activation teams.

1.6 CLEAN-UP AND DISPOSAL

The vendor shall unpack furnishings and dispose of packaging materials offsite unless otherwise directed by the COR. All packaging materials must be recycled if possible.

The vendor shall clean up and dispose of all waste generated each day they are on-site.

If the vendor is unable to do so that day, they must inform the on-site Project Manager to establish the expected date for the remaining waste removal and disposal.

The East Indy clinic does not have on-site dumpsters available for vendor use; all waste generated must be taken to an off-site location.

Waste and excess material removal shall occur through the loading dock area.

1.7 ADDITIONAL REQUIREMENTS

The product manufacturer’s date cannot exceed 24 months (2 years) before the purchase order date. The equipment must be unused and not refurbished, and it should have the latest software and hardware updates installed by the manufacturer.

Batteries included with the unit must have been manufactured within 12 months (1 year) of the purchase order issuance date.

Service Manuals, including the theory of operation, maintenance requirements, repair information, schematics, part lists, and troubleshooting details, shall be provided to the VA HTM Department in electronic format.

Warranty information regarding parts and labor shall be provided for all procured products in electronic format. Documentation must be sent to both the IOT&A contractor and the VA HTM Department within three (3) days of delivery.

1.8 REPORTING REQUIREMENTS

The Contractor shall provide a Price and Utilization Report using the M-26-10 Template, completing the appropriate tabs, which collects information related to Software, Artificial Intelligence, Cloud, and Hardware acquisitions in accordance with OMB M-26-10. This information shall be submitted on a quarterly basis throughout the period of performance, including any exercised options or contract extensions. OMB M-26-10 is a requirement of this contract and requires IT vendors to disclose utilization and pricing information to the Government, without limiting the extent to which that information may be shared across agencies. The Contractor shall access the M-26-10 Template, located at, https://www.voa.va.gov/DocumentView.aspx?DocumentID=5122, prior to reporting each quarter to ensure latest template is used.

Deliverable:

Price and Utilization Report

2.0 NOTICE OF THE FEDERAL ACCESSIBILITY LAW AFFECTING ALL

INFORMATION AND COMMUNICATION TECHNOLOGY (ICT)

PROCUREMENTS (SECTION 508)

On January 18, 2017, the Access Board issued a final rule that updated accessibility requirements covered by Section 508 and refreshed guidelines for telecommunications equipment subject to Section 255 of the Communications Act. The final rule went into effect on January 18, 2018. 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: Revised 508 Standards and 255 Guidelines (access-board.gov). A single PDF file version of the Revised Section 508 Standards and 255 Guidelines will be supplied upon request, or can be obtained from the Access Board website. Federal agencies must comply with the Rehabilitation Act of 1973, as amended.

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 SUSTAINABLE PRODUCTS

Not Applicable

4.0 SHIPMENT OF HARDWARE OR EQUIPMENT

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

Ship To and Mark For:

Primary Secondary Name: To Be Provided (TBP) Name: TBP Address: Address:

Voice: Voice:

Email: Email:

4.1 SPECIAL SHIPPING INSTRUCTIONS

Prior to shipping, Contractor shall notify Site POCs, by phone followed by email, of all incoming deliveries including line-by-line details for review of requirements. The Contractor shall not make any changes to the delivery schedule at the request of Site

POC.

Contractors shall coordinate deliveries with Site POCs before shipment of hardware to ensure sites have adequate storage space.

All shipments, either single or multiple container deliveries, shall bear the VA IFCAP Purchase Order number (if applicable) on external shipping labels and associated manifests or packing lists. In the case of multiple container deliveries, a statement readable near the VA Integrated Funds Distribution, Control Point Activity, Accounting and Procurement (IFCAP) Purchase Order (PO) or Contract number shall indicate total number of containers for the complete shipment (e.g. “Package 1 of 2”), clearly readable on manifests and external shipping labels.

Packing Slips/Labels and Lists shall also include the following:

Attn: East Indianapolis VA Activations Address IFCAP PO # (e.g., 166-E11234 (the IFCAP PO number is located in block #20 of the Standard Form, SF 1449)) Total number of Containers: Package ___ of ___. (e.g., Package 1 of 3)

Attn: East Indianapolis VA Activations (VA PO# ********) East Indianapolis VA Clinic 9402 East 21st St Indianapolis, IN 46229 Package _1__ of _3__.

4.2 NATIONAL ACQUISITIONS

Not Applicable

4.3 SHIPMENT/DELIVERY KICK-OFF MEETING

The Contractor shall conduct a Shipment/Delivery Kick-off Meeting with the VA Program Manager (PM), COR, Delivery Date Coordinator, Implementation Manager, and Facility CIOs (or designee) to discuss delivery schedule requirements and facilitate delivery of equipment. This meeting may be held in conjunction with the post award conference or identified technical kickoff meeting, if applicable. The Contractor shall also present the Shipment/Delivery Weekly Progress Report format for review and approval by the Government. This meeting, if held independently, shall be conducted telephonically within ten days after award and shall incorporate any delivery schedule changes to the draft Delivery Schedule identified by the Government.

5.0 PD ATTACHMENTS

Scaled Room Drawing With Mechanical, Electrical, and Plumbing (MEP) PAR Excellence Warranties

6.0 GENERAL REQUIREMENTS

6.1 VA TECHNICAL REFERENCE MODEL

The Contractor shall comply with the VA OIT Technical Reference Model (VA TRM).

Compliance with the VA TRM is achieved by using only technologies and standards that are listed as approved for use in the VA TRM. The Contractor shall provide all necessary information requested by VA to ensure TRM approval is obtained prior to use on VA’s network.

6.2 ZERO TRUST – VA CRITICAL SECURITY CONTROLS

VA has established minimum mandatory security requirements and requires that any network connected software system or service must meet the VA Critical Security Controls as outlined in the VA Memorandum, “VA Security Controls”, https://www.voa.va.gov/DocumentView.aspx?DocumentID=5010. VA Critical Security Controls identify the minimum mandatory requirements that must be implemented across all VA enterprise infrastructure, cloud computing environments, information systems, networks, and specialized devices (medical devices/systems, special-purpose systems, and research scientific computing devices) that process, store, and/or transmit VA data. Effective July 1, 2025, the Contractor shall implement these VA Critical Security Controls, within any network connected software system or service prior to being authorized for use in the VA. This functional requirement is not negotiable, and Plan of Action & Milestones (POAM) will not be accepted in the event these controls cannot be implemented for new systems. Critical Security Controls are intended to increase VA’s security posture and provide security and privacy risk visibility into the VA network and is not a new requirement. The Contractor’s failure to maintain these VA Critical Controls after implementation will result in VA discontinuing the use of the system.

6.3 ENTERPRISE SOCIAL SECURITY NUMBER (ESSN) REDUCTION

The Contractor solution shall comply with the Social Security Number (SSN) Fraud Prevention Act (FPA) of 2017 (P.L. 115-59 (Sept. 15, 2017)) which prohibits the inclusion of Social Security Numbers (SSNs) on any document sent by mail, except for limited exemptions codified in 38 C.F.R. § 1.575 (2022). The Contractor solution shall only include a SSN on a mailed document with an approved Exemption from VA Enterprise Social Security Number Reduction (ESSNR) Leadership. The Contractor solution shall also comply with the Continuing Appropriations, Agriculture, Legislative Branch, Military Construction and Veterans Affairs, and Extensions Act (CAA), 2026 (P.L. 119-37, Div. D, Title II, Sect. 237 (Nov. 12, 2025)) that prohibits VA from using SSN for VA system authentication and restricts VA’s use of a SSN to identify an individual in a VA information system. The Contractor solution shall only use a SSN to identify an individual in a VA information system if its use complies with CAA’s Acceptable Use and the information system has received approval from ESSNR Leadership.

6.4 INTERNET PROTOCOL VERSION 6 (IPV6)

The Contractor solution shall support IPv6-Only 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). Which defines IPv6-only as the state of an operational system or service when IPv4 protocol functions (addressing, packet forwarding) are not in use. The NIST USGv6 profile defines technical requirements for a product to be capable of operating in IPv6-Only environments. IPv6-Only 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, applications, and systems shall support all applicable functionality on native IPv6-Only as well as 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-Only and dual stack (IPv6 / IPv4) users and all internal infrastructure and applications shall support using native IPv6-Only and dual stack (IPv6 / IPv4) for all functionality and operations.

6.5 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.6 TRUSTED INTERNET CONNECTION (TIC)

The Contractor solution shall meet the requirements outlined in Office of Management and Budget Memorandum M-19-26, “Update to the Trusted Internet Connections (TIC) Initiative“ (https://www.whitehouse.gov/wp-content/uploads/2019/09/M-19-26.pdf), VA Directive 6513 “Secure External Connections”, and shall comply with the TIC 3.0 Core Guidance Documents, including all Volumes and TIC Use Cases, found at the Cybersecurity & Infrastructure Security Agency (CISA) (https://www.cisa.gov/publication/tic-30-core-guidance-documents.)

6.7 GENERATIVE ARTIFICIAL INTELLIGENCE REQUIREMENTS

Not applicable.

6.8 SOURCE CODE HARMONIZATION AND REUSE IN INFORMATION

TECHNOLOGY (SHARE IT ACT)

Not applicable

7.0 SECURITY AND PRIVACY REQUIREMENTS

7.1 POSITION/TASK RISK DESIGNATION LEVEL(S)

7.2 CONTRACTOR PERSONNEL SECURITY REQUIREMENTS

Contractor Responsibilities:

a. The Contractor shall prescreen all personnel requiring access to the computer systems to ensure they maintain the appropriate Background Investigation, and are able to read, write, speak, and understand the English language.

b. Within 3 business days after award, the Contractor shall provide a roster of Contractor and Subcontractor employees to the COR to begin their background investigations in accordance with the PAL template artifact. The Contractor Staff Roster shall contain the Contractor’s Full Name, Date of Birth, Place of Birth, individual background investigation level requirement (based upon Section 6.2.1 Tasks), as well as the following information IAW VAAR 852.204-72 Personnel Vetting and Credentialing:

i. Name of VA facility where Contractor/subcontractor employee works, if applicable.

ii. Date background check submitted for Contractor/subcontractor employee.

iii. Date PIV/identification card issued to Contractor/subcontractor employee.

iv. Contractor/subcontractor employee’s PIV/identification card number, as applicable.

v. Date Contractor/subcontractor employee no longer has need for PIV/identification card.

vi. Date Contractor notified VA that PIV/identification card is no longer required.

vii. Date Contractor returned PIV/identification card to VA.

c. The Contractor shall submit associated full Social Security Numbers either within the Contractor Staff Roster or under separate cover to the COR. The Contractor Staff Roster shall be updated and provided to VA within 5 working days after the end of each calendar quarter, and within 1 day of any changes in employee status, training certification completion status, Background Investigation level status, additions/removal of employees, etc. throughout the Period of Performance. The Contractor Staff Roster shall remain a historical document indicating all past information and the Contractor shall indicate in the Comment field, employees no longer supporting this contract. The preferred method to send the Contractor Staff Roster or Social Security Number is by encrypted e-mail. If unable to send encrypted e-mail, other methods which comply with FIPS 140-2 (or its successor) are to encrypt the file, use a secure fax, or use a traceable mail service. (Note that by September 22, 2026, all FIPS 140-2 certificate validations will be placed on the Historical List. See FIPS Transition Effort Timeline for more details: https://csrc.nist.gov/projects/fips-140-3-transition-effort#schedule)

d. The Contractor should coordinate with the location of the nearest VA fingerprinting office through the COR. Only electronic fingerprints are authorized.

The Contractor shall bring their completed Personnel Security Adjudication Center (PSAC) Fingerprint request form with them (see paragraph e.4. below) when getting fingerprints taken.

e. The Contractor shall ensure the following required forms are submitted to the COR within 5 days after contract award:

1) Optional Form 306

2) Self-Certification of Continuous Service

3) VA Form 0710

4) Completed PSAC Fingerprint Request Form

f. The Contractor personnel shall submit all required information related to their background investigations (completion of the investigation documents (SF85, SF85P, or SF 86) utilizing the Defense Counterintelligence and Security Agency

(DCSA) National Background Investigation Services (NBIS) Electronic Application (eAPP) (formerly e-QIP) after receiving an email notification from the

PSAC.

g. The Contractor employee shall certify and release the eAPP document, print, and sign the signature pages, and send them encrypted to the COR for electronic submission to the PSAC. These documents shall be submitted to the COR within 3 business days of receipt of the eAPP) notification email. (Note: DCSA is moving towards a “click to sign” process. If click to sign is used, the Contractor employee should notify the COR within 3 business days that documents were signed via eAPP).

h. The Contractor shall be responsible for the actions of all personnel provided to work for VA under this contract. In the event that damages arise from work performed by Contractor provided personnel, under the auspices of this contract, the Contractor shall be responsible for all resources necessary to remedy the incident.

i. A Contractor may be granted unescorted access to VA facilities and/or access to VA Information Technology resources (network and/or protected data) with a favorably adjudicated Special Agreement Check (SAC), completed training delineated in VA Handbook 6500.6 (Section 8.c.(5)), signed “Contractor Rules of Behavior”, and with a valid, operational Personal Identity Verification (PIV) credential for PIV-only logical access to VA’s network. A PIV card credential can be issued once your SAC has been favorably adjudicated and your background investigation has been scheduled by DCSA. However, the Contractor will be responsible for the actions of the Contractor personnel they provide to perform work for VA. The investigative history for Contractor personnel working under this contract must be maintained in the database of DCSA.

j. The Contractor, when notified of an unfavorably adjudicated background investigation on a Contractor employee as determined by the Government, shall withdraw the employee from consideration in working under the contract.

k. Failure to comply with the Contractor personnel security investigative requirements may result in loss of physical and/or logical access to VA facilities and systems by Contractor and Subcontractor employees and/or termination of the contract for default.

l. PIV Credential Holders must follow all HSPD-12 policies and procedures as well as use and protect their assigned identity credentials in accordance with VA policies and procedures, displaying their badges at all times, and returning the identity credentials upon termination of their relationship with VA.

Deliverable:

Contractor Staff Roster

ADDENDUM B – VA CYBERSECURITY AND PRIVACY LANGUAGE FOR

INCLUSION IN ACQUISITIONS

NOTE: In the event of a conflict, VA Acquisition Regulation (VAAR) Security Clauses take precedence over the language in this Addendum B.

FROM: VA HANDBOOK 6500.6, ACQUISITION CYBERSECURITY, SECTION 8, VA

CYBERSECURITY AND PRIVACY LANGUAGE, FOR INCLUSION IN CONTRACTS

a. GENERAL

1) Contractors, Contractor personnel, Sub-Contractor and Sub-Contractor personnel (hereinafter referred to as “Contractor”) will be subject to the same Federal laws, regulations, standards, VA directives and handbooks as VA personnel regarding information and information system security and privacy.

2) VA Cybersecurity and Privacy language included in the solicitation or contract applies to the Contractor and all Contractor affiliates and agents.

3) All information systems, applications, and services operating on behalf of or within VA must meet or exceed all applicable federal cybersecurity and risk management minimum standards. At a minimum, systems shall implement and maintain compliance with the National Institute of Standards and Technology (NIST) Special Publication (SP) 800-37, Risk Management Framework for Information Systems and Organization: A System Life Cycle Approach for Security and Privacy, Federal Information Security Modernization Act of 2014 (FISMA) requirements, and all applicable federal laws, and Office of Management and Budget (OMB) mandates.

Contractual terms, implementation approaches, or operational constraints shall not supersede or circumvent these federal minimum security and compliance requirements. Authority established under this handbook is limited to technical, and enterprise architecture matters; interpretation or adjudication of non-technical policy or programmatic content remains the responsibility of the appropriate business or governing policy offices.

b. VA INFORMATION CUSTODIAL

1) The Contractor must provide unlimited rights to data / intellectual property first produced and delivered in the performance of this contract or order (hereinafter “contract”) unless expressly stated otherwise in this contract. This includes all rights to source code and all documentation created in support thereof. The primary clause used to define Government and Contractor data rights is Federal Acquisition Regulation (FAR) 52.227-14, Rights in Data – General.

a) The Contractor must provide all custom-developed code and technical components developed in the performance of this contract (e.g., documentation; data models; schemas; metadata; architecture designs;

configuration scripts; and artifacts required to develop, build, test, and deploy the code for or on behalf of VA) for storage in a VA-designated repository for custom-developed code in a format that allows VA to access, use, modify, distribute, and reuse it in accordance with the Source Code Harmonization and Reuse in Information Technology Act of 2024 (SHARE IT Act).

b) The Contractor must provide any support and assistance deemed necessary for VA to comply with the SHARE IT Act (e.g., furnishing data for reporting and following federal and VA standards for custom code development).

2) Information made available to the Contractor by VA for the performance or administration of this contract will be used only for the purposes specified in the contract, service agreement, SOW, PWS, and / or PD. The Contractor shall not use VA information in any other manner without prior written approval from a VA CO. The Contractor shall disclose to the CO all Data to be collected, stored, and accessed and will only collect, store, and access the minimum Data necessary to perform its services. The Contractor may only use VA information within the terms of the contract and applicable Federal law, regulations, and VA policies. If new Federal laws, regulations, or VA policies become applicable after execution of the contract, the parties agree to negotiate contract modification and adjustment necessary to implement the new laws, regulations, and / or policies.

The primary clause used to define Government and Contractor data rights is FAR 52.227-14.

3) The Contractor shall not make copies of VA information unless necessary to perform the requirements of the contract. If copies are made for restoration purposes, after the restoration is complete, the copies shall be destroyed in accordance with VA Directive 6500, VA Cybersecurity Program, and VA Office of Information Security (OIS) Knowledge Service.

4) VA information will not be co-mingled with any other data on the Contractor’s information systems or media storage systems. The Contractor shall ensure compliance with Federal and VA requirements related to data protection, data encryption, physical data segregation, logical data segregation, classification requirements and media sanitization. Exceptions to this paragraph will be granted only with the approval of the VA Program Office communicated to the Contractor by the VA CO.

5) Except for uses and disclosures of VA information specifically authorized by this contract, the Contractor may use and disclose VA information only in two situations: (i) in response to a qualifying order of a court of competent jurisdiction after notification to VA CO (ii) with written approval from the VA CO. The Contractor shall refer all requests for, or inquiries about, VA information and information systems to the VA CO.

6) Notwithstanding the provision above, the Contractor shall not release VA records protected by Title 38 United States Code (U.S.C.) § 5705, Confidentiality of medical quality- assurance records, and / or Title 38 U.S.C. § 7332, Confidentiality of certain medical records pertaining to drug addiction, sickle cell anemia, alcoholism or alcohol abuse or infection with Human Immunodeficiency Virus (HIV). If the Contractor is in receipt of a court order or other form of request for the above-mentioned information, the Contractor shall immediately refer that court order or request to the VA CO.

7) If a VHA contract is terminated for default or cause with a business associate, the related local Business Associate Agreement (BAA) shall also be terminated and actions taken in accordance with Veterans Health Administration (VHA) Directive 1605.05, Business Associate Agreements. If there is an executed national BAA associated with the contract, VA will determine what actions are appropriate and notify the contractor.

8) Information made available to the Contractor by VA for the performance or administration of this contract, or information developed by the Contractor in performance or administration of the contract, will be protected and secured in accordance with VA Directive 6500, VA Directive 6510, VA Identity, Credential, and Access Management, and VA Handbook 6510, VA Identity, Credential and Access Management.

9) The Contractor shall store VA sensitive information in an encrypted form, using

VA-approved encryption tools which are Federal Information Processing Standards (FIPS)-validated in accordance with requirements on the OIS Knowledge Service. The Contractor shall verify the integrity of transmitted security and privacy attributes. The Contractor shall provide the capability to check the integrity of VA information while it resides in the external system.

10) The Contractor shall transmit VA sensitive information using VA approved

Transport Layer Security (TLS) configured with FIPS based cipher suites in conformance with NIST SP 800-52, Guidelines for the Selection, Configuration and Use of Transport Layer Security (TLS) Implementations. The cryptographic module used must be FIPS-validated in accordance with requirements on the OIS Knowledge Service.

11) The Contractor’s firewall security shall meet or exceed VA’s minimum requirements.

12) The Contractor shall retain all data storage media which have been used to create, collect, process, store, or disseminate any VA data, information, or agency record in accordance with National Archives and Records Administration (NARA) requirements as outlined in VA Directive 6300, Records and Information Management, VA Handbook 6300.1, Records Management Procedures, and applicable VA Records Control Schedules.

13) The Contractor shall not store or maintain VA sensitive information, including on any form of removable or transportable media, without CO’s prior written approval.

14) The Contractor, in accordance with Federal and VA policy, shall maintain backup of Data containing VA sensitive information, image repositories, and provisioned environments. The backup storage infrastructure shall be located in physically protected, limited-access facilities within the United States and governed by the cybersecurity Controls set forth herein.

15) The Contractor shall provide its plan for the disposition of all VA data in its possession, including destruction and return, in accordance with VA Directive 6500 and requirements specified on the VA OIS Knowledge Service, prior to termination or completion of this contract.

16) The Contractor shall return to VA all data storage media which have been used to create, collect, process, store, or disseminate any VA data, information, or agency record which cannot be sanitized or destroyed as required by Section b(15) of this contract. Such media include, but are not limited to, printed or handwritten hardcopies (containing text or images), magnetic tapes, magnetic discs, optical discs, solid state devices, or any other removable digital or analog data storage media.

17) Media shall be returned using VA-approved methods for secure data transfer. If the media contain VA sensitive information, that information must be encrypted by a VA-approved FIPS-validated encryption tool in accordance with requirements on the OIS Knowledge Service. If the Contractor chooses to ship the media, and the media contain no VA sensitive information, such shipment shall be performed in accordance with VA Directive 6340, Enterprise Mail Management. If any of the media to be shipped contain VA Sensitive Information, the shipment shall be performed in accordance with VA Directive 6609, Mailing of Sensitive Personal Information.

18) The Contractor shall self-certify that the data disposition requirements in Section b (12)-(15) of this contract have been satisfied, and shall send this self-certification to the VA Program Office and the VA CO within 30 business days of the completion or termination of this contract.

19) At the end of any contracted lease, loan, or trade-in of equipment, VA shall not return any electronic storage media included in or with equipment if that media has been used to create, collect, process, store, or disseminate VA data, information, or agency record. Any exception to this stipulation will be granted only with the written approval of the VA CO.

20) VA reserves the right to conduct scheduled or unscheduled audits, assessments, or investigations of Contractor Information Technology (IT) resources to ensure information security is compliant with Federal and VA requirements in accordance with Title 38 U.S.C. § 5722(b)(1). This includes, but is not limited to, periodic assessments of the risk and magnitude of harm that could result from the unauthorized access, use, disclosure, disruption, modification, or destruction of information and information systems that support the operations and assets of VA. The Contractor shall provide all necessary access to records (including electronic and documentary materials related to the contracts and subcontracts) and support (including access to Contractors associated with the contract) to VA, VA's Office Inspector General (OIG), and / or the Government Accountability Office (GAO) staff during periodic control assessments, audits, or investigations.

c. ACCESS TO VA INFORMATION AND VA INFORMATION SYSTEMS

1) All Contractors shall comply with conditions specified in the Veterans Affairs Acquisition Regulation (VAAR) 852.204-71(d), and Contractor operations are required to be in U.S. All Contractors working with VA information must be permanently located within a jurisdiction subject to the law of the U.S. to the maximum extent practicable. The Contractor shall also ensure to restrict the geographic location of information processing and data storage to facilities located within the legal jurisdictional boundary of the U.S. If services are proposed to be performed abroad, the Contractor must state where all non-U.S.

services are provided and obtain the CO’s prior written approval where required by law.

2) The Contractor shall deliver to VA a detailed risk mitigation plan specifically addressing communications, personnel control, data protection and potential legal issues. The plan shall be approved by the Contracting Officer (CO) in writing prior to access being granted.

3) The Contractor shall ensure that all Contractors assigned to work on the contract undergo the same security investigations and obtain the same levels of clearance as VA employees who have been granted access to VA information at the same level of sensitivity. The level and process of background security investigations for Contractors shall be in accordance with VA Directive 0710, Personnel Vetting Program, and VA Handbook 0710, Personnel Vetting Program.

4) The Contractor shall request logical (electronic) or physical access to VA information and VA information systems only to the extent that the requested information is needed to perform the services specified in the solicitation or contract. Contractors who require privileged access to any VA Information System (or component) shall complete the VA elevated privilege access request processes before privileged access is granted.

5) Before being granted access to VA information or VA information systems, Contractors shall:

a) Successfully complete VA Privacy and Information Security Awareness and Rules of Behavior (RoB) course [Talent Management System (TMS) #10176] upon contract initiation and annually thereafter;

b) Sign and acknowledge (electronically through TMS #10176) understanding of and responsibilities for compliance with the VA RoB for Organizational Users;

and

c) Successfully complete all additional cybersecurity or privacy training required for personnel granted equivalent information system or information access.

6) The Contractor shall provide to the VA Program Office a copy of each applicable employee’s training certificates and certificate of signature of the VA RoB for Organizational Users within five (5) business days of contract initiation and annually thereafter. Failure by the Contractor to complete the mandatory annual training is grounds for suspension or termination of all privileges to access VA information physically or electronically and removal from work on the contract until such time as the required training has been successfully completed.

a) The Contractor shall notify the VA Program Office and the VA CO in writing immediately (within 24 hours) after any of the following events:

i. The Contractor no longer needs access to VA information or VA information systems.

ii. The Contractor is terminated, suspended, or otherwise has their work on a

VA project discontinued for any reason.

iii. The Contractor believes that a member of their own personnel may pose a threat to the Contractor’s working environment or to any Contractor-owned assets (e.g., property, buildings, confidential data, COs, employees, networks, systems, trade secrets and / or VA data entrusted to the Contractor).

iv. Discovery or revelation of previously undisclosed changes to a

Contractor’s background history, background investigation, or employee record.

v. The Contractor has their authorization to work in the U.S. revoked.

vi. The contract by which Contractors provides products and services to VA has either been fulfilled or terminated, such that VA can cut off electronic and / or physical access for the Contractor.

7) The Contractor is not permitted to access the VA network or internal resources from any foreign country. When travel outside the United States is required for official VA business or an international work location is explicitly specified in the contract, the Contractor must submit a request for accessing the VA internal network and resources internationally subject to the written approval by the Contracting Officer’s Representative (COR) and all required VA approvers. If approved, the Contractor must adhere to all approval conditions for accessing VA networks or internal resources via VA-issued Government Furnished Equipment (GFE), contractor supplied devices, personal devices with appropriate remote desktop features, or personal devices enrolled in VA’s Bring Your Own Device (BYOD) program.

8) The Contractor is not permitted to travel outside the U.S. with any VA-issued GFE. If international travel is required for official VA business or an international work location is explicitly specified in the contract, an exception may be requested and is subject to written approval by the COR and all required VA approvers.

9) In such cases of contract fulfillment, termination, or other causes, the Contractor shall take the necessary measures to immediately revoke access to VA network, property, information, and information systems (logical and physical) by the Contractor. These measures include (but are not limited to): removing and then securing Personal Identification Verification (PIV) badges and PIV–Interoperable (PIV-I) access badges, VA-issued photo badges, credentials for VA facilities and devices, VA-issued laptops, and authentication tokens. Contractors shall notify the VA Program Office immediately to initiate access removal.

10) Contractors who no longer require VA access will return VA-issued assets to VA

(e.g., documents, electronic equipment, keys, and parking passes). PIV and PIV- I access badges shall be returned to the nearest VA PIV Badge Issuance Office.

Once they have had access to VA information, information systems, networks and VA property in their possessions removed, Contractors shall notify the VA Program Office.

d. SECURITY INCIDENT INVESTIGATION

1) The Contractor shall immediately (within one hour) report suspected security / privacy incidents (including intrusions) to the CO and VA Office of Information and Technology’s (OIT) Enterprise Service Desk (ESD) by calling (855) 673- 4357 [Text Telephones (TTY)-based Telecommunications Relay Service: 711].

2) The Contractor's immediate notice to VA about the incident shall include the following information about the incident, to the extent that this information is known:

a) Date and time (known or approximated) the security incident occurred.

b) Names of individuals involved (when applicable).

c) Location (physical and / or logical, as applicable) of the incident.

d) Event logs related to the incident in a format agreed upon by the Contractor and VA.

e) Actual or potential security issues associated with any Contractor-designed

Product Known Exploited Vulnerabilities (KEVs). i The Contractor shall create, implement, and maintain a process to record, track, and report all KEVs.

f) Amount (in number of files or records) of data belonging to VA believed to have been compromised; and

g) Immediate remediation and mitigation measures the Contractor is taking to minimize exposure to the vulnerability and impact of future incidents of a similar nature including timeframes.

3) After providing the initial incident summary to VA, the Contractor shall continue to provide written updates on any new relevant information about the incident and provide updates at the request of VA officials. The Contractor shall fully cooperate with VA or third-party entity performing an independent risk analysis.

Failure to cooperate may be deemed a material breach and grounds for contract termination.

4) If the incident involves theft or break-in or other criminal activity, the Contractor must concurrently report the incident to the appropriate law enforcement entity (or entities) of jurisdiction, including to the VA OIG and to the VA Office of Security and Law Enforcement. The Contractor shall cooperate with VA and any law enforcement authority responsible for the investigation and prosecution of any possible criminal law violation(s) associated with any incident. The Contractor shall cooperate with VA in any civil litigation to recover VA information, obtain monetary or other compensation from a third party for damages arising from any incident, or obtain injunctive relief against any third party arising from, or related to, the incident.

5) The Contractor shall comply with VA Handbook 6500.2, Management of

Breaches Involving Sensitive Personal Information, which establishes the breach management policies and assigns responsibilities for the oversight, management and reporting procedures associated with managing of breaches.

6) The Contractor shall follow VA Directive 6500 and VA OIS Knowledge Service guidance for implementing an Incident Response Plan or integrating with an existing VA implementation.

7) With respect to unsecured Protected Health Information (PHI), the Contractor is deemed to have discovered a data breach when the Contractor knew or should have known of breach of such information. When a business associate is subject to the requirements of a VHA-issued contract, notification to the covered entity (VHA) shall be made in accordance with the executed BAA.

8) If the Contractor or any of its agents fails to protect VA Sensitive Personal Information (SPI) or otherwise engages in conduct which results in a data breach involving any VA SPI, the Contractor processes or maintains under the contract;

the Contractor shall pay liquidated damages to VA as set forth in VAAR clause 852.211-76, Liquidated Damages—Reimbursement for Data Breach Costs.

e. INFORMATION SYSTEM DESIGN AND DEVELOPMENT

1) The Contractor shall design and develop information systems in compliance with all VA Directives and Handbooks. This includes standards for the protection of electronic PHI, outlined in 45 Code of Federal Regulations (CFR)Part 164, Subpart C and information and system security categorization level designations in accordance with FIPS 199, Standards for Security Categorization of Federal Information and Information Systems and FIPS 200, Minimum Security Requirements for Federal Information Systems.

This is the start of the file's text. The full file is on GovTribe.

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