SOW WoundVision Subscription Audie Murphy 2026.docx

Statement of Work (SOW)

General: The contractor shall provide full-service support for both hardware and software for the Scout Woundvision systems located at the Audie Murphy VA Medical Center, San Antonio, Texas. The system is designed to document and record wounds to through a combination of digital and long-wave infrared cameras. The system avoids documentation errors, minimizes subjectivity an variation, and advances health equity for veteran patients.

Description of Work: The contractor shall provide all required service and subscription to cloud based software including emergency service, repairs, preventative and corrective maintenance, labor, travel, unlimited parts, technical support, application support, and factory authorized updates/modifications/upgrades for the Scout Woundvision systems. All services performed shall be in accordance with the original equipment manufacturer (OEM) specifications. Field service engineers must be licensed or contracted with the original manufacturer in order to work on the equipment. All parts and software must be certified new from the original manufacturer. Reference below for equipment type and the required service:

Summary of Service & Equipment Description: Service Coverage for Scout Woundvision and software are for but not limited to the below model names and serial numbers and coverage verbiage: Models may change by the time contract is awarded, latest model to be provided by vendor.

· VHA Scount Essentials – Software Support (Base Year)

· Monday – Friday 06:00-18:00 MST telephone Support

· Corrective Maintenance and Repair Service Calls to include parts, travel, and labor to return equipment to standard operating condition

· Software Updates and Upgrades

· Software Diagnostic and Repair

· Option to extend for an additional year for up to four additional option years

· Provide service reports

· Scout (SCA200) Protection Plan – Equipment Support – (Base Year)

· Monday – Friday 06:00-18:00 MST telephone Support

· Annual Preventative Maintenance including parts

· Corrective Maintenance and Repair Service Calls to include parts, travel, and labor to return equipment to standard operating condition

· Technician Supplied Accessories

· OEM repair and maintenance parts

· Loaner equipment availability and option to include shipping fees

· Option to extend for an additional year for up to four additional option years

· Provide service reports

Hours of Performance: Normal hours of coverage are Monday through Friday 6:00 AM to 6:00 PM CST excluding federal holidays.

A. All service/repairs will be performed during normal hours of coverage unless requested or approved by the Contracting Officer’s Representative (COR).

B. Preventative periodic maintenance will be performed Monday through Friday 6:00 AM to 6:00 PM MST or as agreed to by the user and the COR in accordance with manufacturer’s recommendations.

C. There will be 24/7 telephone support.

D. Federal Holidays observed by the VAMC are:

i. New Year’s Day

ii. Martin Luther King Day

iii. Presidents’ Day

iv. Memorial Day

v. Juneteenth Day

vi. Independence Day

vii. Labor Day

viii. Columbus/Indigenous People’s Day

ix. Veterans’ Day

x. Thanksgiving Day

xi. Christmas Day

NOTE: Hardware/software update/upgrade installations will be scheduled and performed at a mutually agreed upon time at no additional charge to the Government (unless it would be detrimental to equipment up-time; to be determined by the COR or designated representatives. Government provides software/hardware upgrade/update. There shall be no additional charge for time spent at the site during or after the normal hours of coverage awaiting the arrival of additional FSE and/or delivery of parts.

Conformance Standards: Contractor shall provide service and ensure that the equipment functions in accordance with the equipment manufacturer’s technical performance specifications.

Contractor shall conform to all regulations to include but not be limited to federal, state, and local governing any chemicals, equipment or work which may be used or performed in the work under this contract.

Operational Uptime – Requirements: The medical equipment/system shall be operable and available for use 98% of the normal operating hours of the equipment. Downtime will be computed from notification of problem during normal work hours.

Guaranteed Response Time: The OEM certified Field Service Engineer (FSE) will use commercially reasonable efforts to respond to Customer’s requests within 24 hours of notification to the vendor’s service support team.

Live Phone Support: Service shall include phone support with vendor technical support engineers 24 hours, 7 days a week.

After Hours Phone Support: Service for after hour phone support shall include 24 hours, 7 days a week, and 365 days a year for technical assistance when required.

Software Enhancements: Periodic software enhancements shall be provided as part of the firm fixed price contract and shall be considered within scope.

Preventative Maintenance: Perform system scheduled maintenance inspections as outlined in the user’s manual developed by the manufacturer.

Parts Exchange: All parts required for the repair of the system (excludes instruments and accessories) are covered.

Part Protection: Preferred pricing on repairs or replacement due to accidental damage.

Labor & Travel Expenses: All labor and travel conducted during normal business hours: Monday through Friday, 6:00 AM to 6:00PM MST (excludes vendor company holidays) are covered.

Certified Trained Technicians and Key Personnel: The scheduled maintenance and service calls shall be performed by OEM trained personnel in accordance with the agreement. Technicians shall include fully qualified Facility Service Engineers (FSE) and a fully qualified FSE who will serve as the backup and show proof of competency, as shown by training conducted on said system. "Fully Qualified" is based upon training and on experience in the field. For training, the FSE(s) has successfully completed a formalized training program, for the equipment identified in this statement of work. For field experience, the FSE(s) has a minimum of two years of experience (except for equipment newly on the market) with respect to scheduled and unscheduled preventive and remedial maintenance. Proof of training shall be provided upon demand and be immediately sent via fax, upon demand to the COR. All FSE’s and technicians shall be authorized by the Contractor to perform the maintenance services. All work shall be performed by "Fully Qualified" competent FSE's. The COR and/or designated representative specifically reserve the right to reject any of the Contractor's personnel and refuse them permission to work on the VAMC equipment. It is anticipated that any hospital regulatory inspections (TJC, etc.) will have the vendor providing proof that they meet industry standards of quality, and traceable standards, as used to calibrate this device- system, at the time of the maintenance event.

Period of Performance:

Base year: TBD Option year 1: TBD Option year 2: TBD Option year 3: TBD Option year 4: TBD Dates as specified unless contract award passes these dates. Then the first date of performance will start the day of award.

Unscheduled Maintenance (Emergency Repair Service):

A. Contractor shall maintain the equipment in accordance with the manufacturer’s specifications. The Contractor shall provide repair service which may consist of calibration, cleaning, oiling, adjusting, replacing parts, and maintaining the equipment, including all intervening calls necessary between regular services and calibrations. All required parts shall be furnished.

B. The COR or government designated representatives are authorized to request and approve service calls from the Contractor.

C. Response Time: Contractor's FSE must respond with a phone call to the COR or designated representative within 1 hour after receipt of telephoned notification during normal hours of coverage.

Scheduled Maintenance: All labor and travel conducted during normal business hours: Monday through Friday, 8:00 AM to 6:00PM EST (excludes vendor company holidays) are covered.

Check in Requirements: The Field Service Engineer must report to the Biomedical Engineering Department to obtain a badge and sign in with the Biomedical Engineering Service before work begins. Submit any mobile media devices that would be used on the system to a virus scan. Upon completion of work, the Field Service Engineer must report to the Biomedical Engineering Service to sign out and brief Biomedical Staff or Supervisor if Biomedical Staff is unavailable concerning completion of service. At the end of briefing Field Service Engineer will return the badge and sign out in the Biomedical Engineering Department.

Documentation: Contractor shall furnish a detailed field service report upon completion of work to Biomedical Staff in the Biomed Department. Payment will not be processed until a properly completed service report is received. The service report shall contain, at a minimum, the following information:

· Identification of equipment to be serviced:

· VA EE Number

· Vendor Inventory ID number

· Manufacturer Name

· Device Name

· Model Number

· Serial Number

· System ID

· Name of contractor and contract number

· Name of FSE who performed services

· Contractor service ESR number/log number

· Date, time (starting and ending), equipment downtime and hours on-site for service call

· VA purchase order number(s) covering the call if outside normal working hours

· Total time spent performing maintenance.

· Detailed narrative and itemized description of the services required and performed including:

· Labor and travel

· Parts (with part numbers)

· Materials

· Location

· Corrective Action

· Copies of all test reports

· Complete list of parts replaced (when applicable)

· Date and time the repair/support was completed

· Total Cost to be billed (if applicable – i.e., part(s) not covered, or service rendered after normal hours of coverage).

· Signatures:

· FSE performing services described

· Authorized VA employee who witnessed service described

· NOTE: - Any additional charges claimed must be approved by the COR or designated representative before service is completed!

The service report shall itemize every item in the specification. Each item shall state the "as found" condition or values, the "calibrated to" or "adjusted to" values, the factory design tolerances, and a complete description of all work performed concerning the items. Included will be a list of new parts used and recommended future repairs.

Reporting Requirements: The Contractor shall be required to report to the Clinical Engineering Department to log in. This check- in is mandatory. When the service is completed, the FSE shall document services rendered on a legible ESR(s). The FSE shall be required to log out with Biomedical Engineering and submit the ESR(s) to the COR or designated representative. ALL ESRs shall be submitted to the equipment user for an "acceptance signature" and to the COR or designated representative for an "authorization signature". If COR or designated representative is unavailable, a signed, authorized copy of the ESR will be left with the user.

Place of Performance:

Department of Veterans Affairs Audie L. Murphy VA Medical Center 7400 Merton Minter San Antonio, Texas 78229

Contracting Officer Representatives: Prior to contract award, the Contracting Officer shall designate a VA Medical Center employee as the COR. All work coordination shall be made through the COR. The Contractor shall be provided a copy of the letter of delegation authorizing the COR at the commencement of the term of the contract. No other person shall be authorized to act in such capacity unless appointed in writing by the Contracting Officer.

Information Technology Security Requirements: The contractor, their personnel, and their subcontractors shall be subject to the Federal laws, regulations, standards, and VA Directives and Handbooks regarding information and information system security as delineated in this contract. The contractor shall comply with all Federal laws and regulations the VA has developed when VA sensitive information is accessed, used, stored, generated, transmitted, or exchanged by and between VA and a contractor. The information made available to the contractor by VA for the performance of this contract will be used only for the purposes of performance under this contract. The certification and accreditation requirements do not apply to this requirement and a security accreditation package is not required.

Security Statement: Sensitive VA information is contained within the systems covered by this contract.

Biomedical Engineering shall perform virus scans on all removable media prior to use on VA medical equipment. This includes all types of removable media, including media (e.g., USB devices, CDs, dongles, etc.) that has been issued by VA, media not issued by VA, and media brought in by vendors or independent service organizations. Within accordance of VA Directive 6500, Information Security Program, September 2007 The Vendor will not transfer any VA information to a location outside the VA and only to VA locations determined by the VA System Administrator. The information in these systems may be covered by the Privacy Act 1974 which contains criminal penalties of abuse of information.

During onsite service, the Vendor shall be chaperoned by VA Personnel. However, the vendor shall not be issued a User ID/Password.

Non-volatile memory devices, working or non-working, shall NOT be removed from the Audie L. Murphy VA Medical Center until the ISO has certified that the data has been destroyed. For magnetic devices and media, the data destruction will be by degaussing. Other forms of cleansing will be used for non-magnetic media.

The vendor will not have remote access to complete the repair(s) and preventive maintenance.

Safety Requirements: In the performance of this contract, the Contractor shall take such safety precautions as the Contracting Officer may determine to be reasonably necessary to protect the lives and health of occupants of the building. The Contracting Officer shall notify the Contractor of any safety issues and the action necessary to correct these issues. Such notice, when served to the Contractor or his representative at the work site shall be deemed sufficient for the corrective actions to be taken. If the Contractor fails or refuses to comply promptly, the Contracting Officer may issue an order stopping all or part of the work and hold the Contractor in default.

Invoicing: Payment to be made monthly in arrears by certified invoices and must contain the contract number in addition to the requirements detailed in 52.212-4 (G) to be considered valid. All invoices shall be submitted to the VA Financial Service Center and emailed to the COTR. All invoices will reference the purchase order number assigned to the contract.

Additional Charges: There shall be no additional charge for time spent at the site (during, or after the normal hours of coverage) awaiting the arrival of additional FSE and/or delivery of parts.

Reporting Required Services Beyond the Contract Scope: The Contractor shall immediately, but no later than 24 (twenty-four) consecutive hours after discovery, notify the COR and/or designated representative (in writing) of the existence or the development of any defects in, or repairs required, to the scheduled equipment which the Contractor considers he/she is not responsible for under the terms of the contract. The Contractor shall furnish to the COR or designated representative a written estimate of the cost to make necessary repairs.

Condition of Equipment: The Contractor shall accept responsibility for the equipment.

Failure to inspect the equipment prior to contract award will not relieve the Contractor from performance of the requirements of this contract.

Test Equipment: Prior to commencement of work on this contract, the Contractor shall provide the VAMC with a copy of the current calibration certification of all test equipment which is to be used by the Contractor on VAMC's equipment. This certification shall also be provided on a periodic basis when requested by the VAMC. Test equipment calibration shall be traceable to the Original Equipment Manufacture’s standard.

Identification, Parking, Smoking, and VA Regulations: The Contractor's FSE's shall always wear visible identification while on the premises of the VAMC. The Contractor shall park in the appropriate designated parking areas. Information on parking is available from the VA Police Section. The VAMC will not invalidate or make reimbursement for parking violations of the Contractor under any conditions. Smoking is prohibited inside any buildings at the VAMC. Possession of weapons is prohibited. Enclosed containers, including tool kits, shall be subject to search. Violations of VA regulations may result in citation answerable in the United States (Federal) District Court, not a local district, state, or municipal court.

Training: The Contractor shall provide first call Clinical Engineering training for current qualified technicians at the VAMC, CT during regular service hours of Monday through Friday from 8:00am – 6:00 PM EST. This is not an ongoing training and will only be provided on an annual basis as required. All training for upgrades to equipment shall be considered within scope throughout the life of the contract. All service and repairs are performed by OEM factory certified technicians.

Miscellaneous: Additional equipment may be added and/or removed throughout the life of this contract and shall be considered within scope.

Contractor Personnel Security Requirements: Security Requirements: All contractor personnel shall obtain a short-term identification badge issued by the COR or government designated representative. Such badge shall be worn by the individual and prominently always displayed while on VA Property. No employee of the contractor shall enter the project site without a valid identification badge issued by the VA. To obtain a short-term identification badge, contractor personnel shall present to the COR a valid (non-expired) photo identification issued by a US federal, state, or local government agency. Escort will be provided as required in sensitive work areas. The C&A requirements do not apply, and the security accreditation package is not required. The identified Sole Source Vendor shall be subject to the Federal laws, regulations, standards, and VA Directives and Handbooks regarding information and information system security as delineated in standard acquisition guidelines. Per the VA handbook 6500.6, no VA sensitive information will be transferred, shared, or stored with vendor. As such, no additional mechanisms will be needed to ensure the protection of information.

Records Management Statement:

1. Contractor shall comply with all applicable records management laws and regulations, as well as National Archives and Records Administration (NARA) records policies, including but not limited to the Federal Records Act (44 U.S.C. chs. 21, 29, 31, 33), NARA regulations at 36 CFR Chapter XII Subchapter B, and those policies associated with the safeguarding of records covered by the Privacy Act of 1974 (5 U.S.C. 552a). These policies include the preservation of all records, regardless of form or characteristics, mode of transmission, or state of completion.

2. In accordance with 36 CFR 1222.32, all data created for Government use and delivered to, or falling under the legal control of, the Government are Federal records subject to the provisions of 44 U.S.C. chapters 21, 29, 31, and 33, the Freedom of Information Act (FOIA) (5 U.S.C. 552), as amended, and the Privacy Act of 1974 (5 U.S.C. 552a), as amended and must be managed and scheduled for disposition only as permitted by statute or regulation.

3. In accordance with 36 CFR 1222.32, Contractor shall maintain all records created for Government use or created in the course of performing the contract and/or delivered to, or under the legal control of the Government and must be managed in accordance with Federal law. Electronic records and associated metadata must be accompanied by sufficient technical documentation to permit understanding and use of the records and data.

4. Audie L. Murphy VA Medical Center and its contractors are responsible for preventing the alienation or unauthorized destruction of records, including all forms of mutilation. Records may not be removed from the legal custody of the Audie L. Murphy VA Medical Center or destroyed except for in accordance with the provisions of the agency records schedules and with the written concurrence of the Head of the Contracting Activity. Willful and unlawful destruction, damage or alienation of Federal records is subject to the fines and penalties imposed by 18 U.S.C. 2701. In the event of any unlawful or accidental removal, defacing, alteration, or destruction of records, Contractor must report to Audie L. Murphy VA Medical Center. The agency must report promptly to NARA in accordance with 36 CFR 1230.

5. The Contractor shall immediately notify the appropriate Contracting Officer upon discovery of any inadvertent or unauthorized disclosures of information, data, documentary materials, records or equipment. Disclosure of non-public information is limited to authorized personnel with a need-to-know as described in the [contract vehicle]. The Contractor shall ensure that the appropriate personnel, administrative, technical, and physical safeguards are established to ensure the security and confidentiality of this information, data, documentary material, records and/or equipment is properly protected. The Contractor shall not remove material from Government facilities or systems, or facilities or systems operated or maintained on the Government’s behalf, without the express written permission of the Head of the Contracting Activity. When information, data, documentary material, records and/or equipment is no longer required, it shall be returned to Audie L. Murphy VA Medical Center control or the Contractor must hold it until otherwise directed. Items returned to the Government shall be hand carried, mailed, emailed, or securely electronically transmitted to the Contracting Officer or address prescribed in the [contract vehicle]. Destruction of records is EXPRESSLY PROHIBITED unless in accordance with Paragraph (4).

6. The Contractor is required to obtain the Contracting Officer's approval prior to engaging in any contractual relationship (sub-contractor) in support of this contract requiring the disclosure of information, documentary material and/or records generated under, or relating to, contracts. The Contractor (and any sub-contractor) is required to abide by Government and Audie L. Murphy VA Medical Center guidance for protecting sensitive, proprietary information, classified, and controlled unclassified information.

7. The Contractor shall only use Government IT equipment for purposes specifically tied to or authorized by the contract and in accordance with Audie L. Murphy VA Medical Center policy.

8. The Contractor shall not create or maintain any records containing any non-public Audie L. Murphy VA Medical Center information that are not specifically tied to or authorized by the contract.

9. The Contractor shall not retain, use, sell, or disseminate copies of any deliverable that contains information covered by the Privacy Act of 1974 or that which is generally protected from public disclosure by an exemption to the Freedom of Information Act.

10. The Audie L. Murphy VA Medical Center owns the rights to all data and records produced as part of this contract. All deliverables under the contract are the property of the U.S. Government for which Audie L. Murphy VA Medical Center shall have unlimited rights to use, dispose of, or disclose such data contained therein as it determines to be in the public interest. Any Contractor rights in the data or deliverables must be identified as required by FAR 52.227-11 through FAR 52.227-20.

APPENDIX C — VA INFORMATION AND INFORMATION SYSTEM SECURITY AND PRIVACY LANGUAGE FOR INCLUSION IN CONTRACTS, AS APPROPRIATE

1. GENERAL. This entire section applies to all acquisitions requiring any Information Security and Privacy language. Contractors, contractor personnel, subcontractors and subcontractor personnel 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 INFORMATION CUSTODIAL LANGUAGE. This entire section applies to all acquisitions requiring any Information Security and Privacy language.

a. The Government shall receive 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 FAR 52.227-14 Rights in Data – General. The primary clause used to define computer software license (not data/intellectual property first produced under this contractor or order) is FAR 52.227-19, Commercial Computer Software License.

b. 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 service agreement, SOW, PWS, PD, and/or contract. The contractor shall not use VA information in any other manner without prior written approval from a VA Contracting Officer (CO). The primary clause used to define Government and Contractor data rights is FAR 52.227-14 Rights in Data – General.

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

d. 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. 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 contractor and subcontractor staff associated with the contract) to VA, VA's Office Inspector General (OIG), and/or Government Accountability Office (GAO) staff during periodic control assessments, audits, or investigations.

e. The contractor may only use VA information within the terms of the contract and applicable Federal law, regulations, and VA policies. If new Federal information security 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.

f. The contractor shall not make copies of VA information except as specifically authorized and necessary to perform the terms 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 Information Security Knowledge Service.

g. If a Veterans Health Administration (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 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 contactor.

h. The contractor shall store and transmit VA sensitive information in an encrypted form, using VA-approved encryption tools which are, at a minimum, Federal Information Processing Standards (FIPS) 140-2, Security Requirements for Cryptographic Modules (or its successor) validated and in conformance with VA Information Security Knowledge Service requirements. The contractor shall transmit VA sensitive information using VA approved Transport Layer Security (TLS) configured with FIPS based cipher suites in conformance with National Institute of Standards and Technology (NIST) 800-52, Guidelines for the Selection, Configuration and Use of Transport Layer Security (TLS) Implementations.

i. The contractor’s firewall and web services security controls, as applicable, shall meet or exceed VA’s minimum requirements.

j. Except for uses and disclosures of VA information authorized by this contract for performance of the 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, demands for production of or inquiries about, VA information and information systems to the VA CO for response.

k. Notwithstanding the provision above, the contractor shall not release VA records protected by Title 38 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 requests for the above- mentioned information, the contractor shall immediately refer such court order or other requests to the VA CO for response.

l. 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 and Identity and Access Management (IAM) Security processes specified in the VA Information Security Knowledge Service.

m. Any data destruction done on behalf of VA by a contractor shall be done 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.

n. The contractor shall provide its plan for destruction of all VA data in its possession according to VA Directive 6500 and NIST 800-88, Guidelines for Media Sanitization prior to termination or completion of this contract. If directed by the COR/CO, the contractor shall return all Federal Records to VA for disposition.

o. Any media, such as paper, magnetic tape, magnetic disks, solid state devices or optical discs that is used to store, process, or access VA information that cannot be destroyed shall be returned to VA. The contractor shall hold the appropriate material until otherwise directed by the Contracting Officer’s Representative (COR) or CO. Items shall be returned securely via VA-approved methods. VA sensitive information must be transmitted utilizing VA-approved encryption tools which are validated under FIPS 140-2 (or its successor) and NIST 800-52. If mailed, the contractor shall send via a trackable method (USPS, UPS, FedEx, etc.) and immediately provide the COR/CO with the tracking information. Self-certification by the contractor that the data destruction requirements above have been met shall be sent to the COR/CO within 30 business days of termination of the contract.

p. All electronic storage media (hard drives, optical disks, CDs, back-up tapes, etc.) used to store, process or access VA information will not be returned to the contractor at the end of lease, loan, or trade-in. Exceptions to this paragraph will only be granted with the written approval of the VA CO.

3. ACCESS TO VA INFORMATION AND VA INFORMATION SYSTEMS.

This section applies when any person requires access to 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.

a. A contractor/subcontractor shall request logical (technical) or physical access to VA information and VA information systems for their employees and subcontractors only to the extent necessary to perform the services specified in the solicitation or contract. This includes indirect entities, both affiliate of contractor/subcontractor and agent of contractor/subcontractor.

b. Contractors and subcontractors shall sign the VA Information Security Rule of Behavior (ROB) before access is provided to VA information and information systems (see Section 4, Training, below). The ROB contains the minimum user compliance requirements and does not supersede any policies of VA facilities or other agency components which provide higher levels of protection to VA’s information or information systems. Users who require privileged access shall complete the VA elevated privilege access request processes before privileged access is granted.

c. All contractors and subcontractors working with VA information are subject to the same security investigative and clearance requirements as those of VA appointees or employees who have access to the same types of information. The level and process of background security investigations for contractors shall be in accordance with VA Directive and Handbook 0710, Personnel Suitability and Security Program. The Office of Human Resources and Administration/Operations, Security and Preparedness (HRA/OSP) is responsible for these policies and procedures. Contract personnel who require access to classified information or information systems shall have an appropriate security clearance. Verification of a Security Clearance shall be processed through the Special Security Officer located in HRA/OSP. Contractors shall conform to all requirements stated in the National Industrial Security Program Operating Manual (NISPOM).

d. All contractors and subcontractors shall comply with conditions specified in VAAR 852.204-71(d); Contractor operations required to be in United States. All contractors and subcontractors working with VA information must be permanently located within a jurisdiction subject to the law of the United States or its Territories to the maximum extent feasible. If services are proposed to be performed abroad the contractor must state where all non-U.S. services are provided. The contractor shall deliver to VA a detailed plan specifically addressing communications, personnel control, data protection and potential legal issues. The plan shall be approved by the COR/CO in writing prior to access being granted.

e. The contractor shall notify the COR/CO in writing immediately (no later than 24 hours) after personnel separation or occurrence of other causes. Causes may include the following:

(1) Contractor/subcontractor personnel no longer has a need for access to VA information or VA information systems.

(2) Contractor/subcontractor personnel are terminated, suspended, or otherwise has their work on a VA project discontinued for any reason.

(3) Contractor believes their own personnel or subcontractor personnel may pose a threat to their company’s working environment or to any company- owned property. This includes contractor-owned assets, buildings, confidential data, customers, employees, networks, systems, trade secrets and/or VA data.

(4) Any previously undisclosed changes to contractor/subcontractor background history are brought to light, including but not limited to changes to background investigation or employee record.

(5) Contractor/subcontractor personnel have their authorization to work in the United States revoked.

(6) Agreement by which contractor provides products and services to VA has either been fulfilled or terminated, such that VA can cut off electronic and/or physical access for contractor personnel.

f. 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 contractor/subcontractor personnel. These measures include (but are not limited to): removing and then securing Personal Identity 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 appropriate VA COR/CO immediately to initiate access removal.

g. Contractors/subcontractors who no longer require VA accesses will return VA- issued property to VA. This property includes (but is not limited to): 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 appropriate VA COR/CO.

4. TRAINING. This entire section applies to all acquisitions which include section 3.

a. All contractors and subcontractors requiring access to VA information and VA information systems shall successfully complete the following before being granted access to VA information and its systems:

(1) VA Privacy and Information Security Awareness and Rules of Behavior course (Talent Management System (TMS) #10176) initially and annually thereafter.

(2) Sign and acknowledge (electronically through TMS #10176) understanding of and responsibilities for compliance with the Organizational Rules of Behavior, relating to access to VA information and information systems initially and annually thereafter; and

(3) Successfully complete any additional cyber security or privacy training, as required for VA personnel with equivalent information system or information access [to be defined by the VA program official and provided to the VA CO for inclusion in the solicitation document – i.e., any role- based information security training].

b. The contractor shall provide to the COR/CO a copy of the training certificates and certification of signing the Organizational Rules of Behavior for each applicable employee within five days of the initiation of the contract and annually thereafter, as required.

c. Failure to complete the mandatory annual training is grounds for suspension or termination of all physical or electronic access privileges and removal from work on the contract until such time as the required training is complete.

5. SECURITY INCIDENT INVESTIGATION. This entire section applies to all acquisitions requiring any Information Security and Privacy language.

a. The contractor, subcontractor, their employees, or business associates shall immediately (within one hour) report suspected security / privacy incidents to the VA OIT’s Enterprise Service Desk (ESD) by calling (855) 673-4357 (TTY: 711). The ESD is OIT’s 24/7/365 single point of contact for IT-related issues. After reporting to the ESD, the contractor, subcontractor, their employees, or business associates shall, within one hour, provide the COR/CO the incident number received from the ESD.

b. To the extent known by the contractor/subcontractor, the contractor/ subcontractor's notice to VA shall identify the information involved and the circumstances surrounding the incident, including the following:

(1) The date and time (or approximation of) the Security Incident occurred.

(2) The names of individuals involved (when applicable).

(3) The physical and logical (if applicable) location of the incident.

(4) Why the Security Incident took place (i.e., catalyst for the failure).

(5) The amount of data belonging to VA believed to have been compromised.

(6) The remediation measures the contractor is taking to ensure no future incidents of a similar nature.

c. After the contractor has provided the initial detailed incident summary to VA, they will continue to provide written updates on any new and relevant circumstances or facts they discover. The contractor, subcontractor, and their employes shall fully cooperate with VA or third-party entity performing an independent risk analysis on behalf of VA. Failure to cooperate may be deemed a material breach and grounds for contract termination.

d. VA IT contractors shall follow VA Handbook 6500, Risk Management Framework for VA Information Systems VA Information Security Program, and VA Information Security Knowledge Service guidance for implementing an Incident Response Plan or integrating with an existing VA implementation.

e. In instances of theft or break-in or other criminal activity, the contractor/subcontractor must concurrently report the incident to the appropriate law enforcement entity (or entities) of jurisdiction, including the VA OIG, and the VA Office of Security and Law Enforcement. The contractor, its employees, and its subcontractors and their employees 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/subcontractor 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.

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

g. 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 part of VHA contract, notification to the covered entity (VHA) shall be made in accordance with the executed BAA.

h. If the contractor or any of its agents fails to protect VA sensitive personal information or otherwise engages in conduct which results in a data breach involving any VA sensitive personal information the contractor/subcontractor processes or maintains under the contract; the contractor shall pay liquidated damages to the VA as set forth in clause 852.211-76, Liquidated Damages— Reimbursement for Data Breach Costs.

6. INFORMATION SYSTEM DESIGN AND DEVELOPMENT. This entire section applies to information systems, systems, major applications, minor applications, enclaves, and platform information technologies (to include the subcomponents of each) designed or developed for or on behalf of VA by any non-VA entity.

a. Information systems designed or developed on behalf of VA at non-VA facilities shall comply with all applicable Federal law, regulations, and VA policies. This includes standards for the protection of electronic Protected Health Information (PHI), outlined in 45 C.F.R. 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. Baseline security controls shall be implemented commensurate with the FIPS 199 system security categorization (reference VA Handbook 6500 and VA Trusted Internet Connections (TIC) Architecture).

b. Contracted new developments require creation, testing, evaluation, and authorization in compliance with VA Assessment and Authorization (A&A) processes in VA Handbook 6500 and VA Information Security Knowledge Service to obtain an Authority to Operate (ATO). VA Directive 6517, Risk Management Framework for Cloud Computing Services, provides the security and privacy requirements for cloud environments.

c. VA IT contractors, subcontractors and third-party service providers shall address and/or integrate applicable VA Handbook 6500, VA Handbook 6517, Risk Management Framework for Cloud Computing Services and Information Security Knowledge Service specifications in delivered IT systems/solutions, products and/or services. If systems/solutions, products and/or services do not directly match VA security requirements, the contractor shall work though the COR/CO to identify the VA organization responsible for governance or resolution. Contractors shall comply with FAR 39.1, specifically the prohibitions referenced.

d. The contractor (including producers and resellers) shall comply with Office of Management and Budget (OMB) M-22-18 and M-23-16 when using third-party software on VA information systems or otherwise affecting the VA information. This includes new software purchases and software renewals for software developed or modified by major version change after the issuance date of M- 22-18 (September 14, 2022). The term “software” includes firmware, operating systems, applications and application services (e.g., cloud-based software), as well as products containing software. The contractor shall provide a self- attestation that secure software development practices are utilized as outlined by Executive Order (EO)14028 and NIST Guidance. A third-party assessment provided by either a certified Federal Risk and Authorization Management Program (FedRAMP) Third Party Assessor Organization (3PAO) or one approved by the agency will be acceptable in lieu of a software producer's self- attestation.

e. The contractor shall ensure all delivered applications, systems and information systems are compliant with Homeland Security Presidential Directive (HSPD) 12 and VA Identity and Access management (IAM) enterprise identity management requirements as set forth in OMB M-19-17, M-05-24, FIPS 201-3, Personal Identity Verification (PIV) of Federal Employees and Contractors (or its successor), M-21-31 and supporting NIST guidance. This applies to Commercial Off-The-Shelf (COTS) product(s) that the contractor did not develop, all software configurations and all customizations.

f. The contractor shall ensure all contractor delivered applications and systems provide user authentication services compliant with VA Handbook 6500, VA Information Security Knowledge Service, IAM enterprise requirements and NIST 800-63, Digital Identity Guidelines, for direct, assertion-based authentication and/or trust-based authentication, as determined by the design and integration patterns. Direct authentication at a minimum must include Public Key Infrastructure (PKI) based authentication supportive of PIV and/or Common Access Card (CAC), as determined by the business need and compliance with VA Information Security Knowledge Service specifications.

g. The contractor shall use VA authorized technical security baseline configurations and certify to the COR that applications are fully functional and operate correctly as intended on systems in compliance with VA baselines prior to acceptance or connection into an authorized VA computing environment. If the Defense Information Systems Agency (DISA) has created a Security Technical Implementation Guide (STIG) for the technology, the contractor may configure to comply with that STIG. If VA determines a new or updated VA configuration baseline needs to be created, the contractor shall provide required technical support to develop the configuration settings. FAR 39.1 requires the population of operating systems and applications includes all listed on the NIST National Checklist Program Checklist Repository.

h. The standard installation, operation, maintenance, updating and patching of software shall not alter the configuration settings from VA approved baseline configuration. Software developed for VA must be compatible with VA enterprise installer services and install to the default “program files” directory with silently install and uninstall. The contractor shall perform testing of all updates and patching prior to implementation on VA systems.

i. Applications designed for normal end users will run in the standard user context without elevated system administration privileges.

j. The contractor-delivered solutions shall reside on VA approved operating systems. Exceptions to this will only be granted with the written approval of the COR/CO.

k. The contractor shall design, develop, and implement security and privacy controls in accordance with the provisions of VA security system development life cycle outlined in NIST 800-37, Risk Management Framework for Information Systems and Organizations: A System Life Cycle Approach for Security and Privacy, VA Directive and Handbook 6500, and VA Handbook 6517.

l. The Contractor shall comply with the Privacy Act of1974 (the Act), FAR 52.224- 2 Privacy Act, and VA rules and regulations issued under the Act in the design, development, or operation of any system of records on individuals to accomplish a VA function.

m. The contractor shall ensure the security of all procured or developed information systems, systems, major applications, minor applications, enclaves and platform information technologies, including their subcomponents (hereinafter referred to as “Information Systems”) throughout the life of this contract and any extension, warranty, or maintenance periods.