J065--36C255-26-AP-0804, OmniCell Maintenance Service for Columbia VAMC

Description

{"description":"PERFORMANCE WORK STATEMENT\nOmnicell Maintenance Services -Columbia\nGeneral Requirements:\n\nThe Contractor shall provide services and support at the locations identified in this Performance Work Statement. The Government reserves the right to add, remove, or modify locations and facilities as mission requirements evolve across the current and future operational footprint. The Contractor shall accommodate these changes within the scope of the contract without disruption to services. Any adjustments to pricing, schedule, or resources resulting from such changes shall be addressed through the appropriate contractual modification process in accordance with the applicable Changes clause.\n\nPlace of Performance:\n\nHarry S. Truman Memorial Veterans Hospital (HSTMVH)\n800 Hospital Drive\nColumbia, MO 65201-5275\n\nPeriod of Performance:\nIt is the Governments intent to award a fixed price contract. Contract period of performance will commence on April 1, 2026, and extend through March 31, 2027.\nBackground: \nThe Pharmacy currently is requesting routine maintenance for their Omnicell systems and associated equipment. This equipment is used to dispense and package medications for patients. The Columbia VA Medical Center is requesting routine maintenance as required by the Truman VA Medical Center Healthcare Technology Management Medical Equipment Management Program and the OEM specifications for Omnicell medication dispensing systems. Timely repair of this equipment is essential to the safety of the patient population and the efficient operation of the Pharmacy.\nRequired Services:\nThe contractor must be an authorized service provider for the Original Equipment Manufacturer (OEM) and provide OEM letter.\nThe contractor shall provide maintenance and repair on site (when determined by contract COR), to include all replacement parts, labor, travel expenses, telephone technical support, remote on-line support (maintain a current MOU/ISA allowing VPN access), software, tools, test equipment and other incidentals necessary to maintain and/or restore the listed equipment (see below), to operating specifications according to the manufacturer's specifications. This includes maintenance and repair both hardware and software (this includes primary operating systems and proprietary software) of the Production Server, Test Server, Carousels and all peripheral PC s/devices(Scanners & Printers). All maintenance and repairs shall be provided during the contract business hours of 8:00AM 5:00 PM, Monday through Friday, excluding federal holidays unless otherwise approved by Contract COR. Upon placement of a service request, the contractor must respond to the contract COR within one (1) hour by telephone for diagnostic response, and must provide priority on-site service response within four (4) business hours after contacting the VA, unless otherwise determined by contract COR. \nAll scheduled preventive maintenance for equipment listed will be performed by Contractor. Contractor will provide (at no additional cost) any part(s) found out of manufacture specification during the preventive maintenance inspection activities. Contractor shall assist with Planned Maintenance, Quality Assurance and Safety Checks. Scheduling of preventive maintenance will be coordinated between the contractor and the contract COR. \nAll services for this contract must meet manufacturer performance and technical specifications, Federal Regulations, and other specifications that may apply such as National Electric Code (NEC), Life Safety Code (LSC), Joint Commission (JC), and VA Regulations. The contractor shall ONLY respond to service calls placed by Biomedical Engineering to include: The Contracting Officer s Representative (COR) Adam Richardson (573) 814-6000 ext. 52408, or designee. \nThe contractor accessing the listed equipment must have an approved VA VPN network account established (existing MOU/ISA). All VPN accounts will be coordinated through the facilities ISO (Information Security Officer) and will comply with all VA regulations and standards to include OA&MM Information Letter (IL 90-01-6) dated July 16, 2001. Additionally, the contractor will be responsible for adhering to the following security requirements/clauses:\nALL SERVICE ENGINEERS MUST REPORT to the FM Office (Building 22) to sign in before work\nis begun on the premises of the HSTMVH and must also to sign out after work has been completed. The contractor must furnish a detailed field service report, or equivalent, showing work completed, listing all repairs and/or repair parts used to maintain operating efficiency of the equipment. When possible, this report may be delivered to Biomedical Engineering before contractor leaves the station or via email please see section B.4 for contact information. If it is necessary for the contractor to work after 4:30pm, permission must be granted from the Contract POC. If the service was completed after regular duty hours, the FSE will sign out and leave the report in the Engineering Control Center, room DO 19 of the hospital.\nFailure to provide the service report may lead to a delay in payment as verification is required to ensure service was provided. The service report from the contractor must contain, at a minimum, the following information:\na. Date and time of the contractor's arrival on station,\nb. Type, model, and serial number(s) of all equipment on which maintenance was performed,\nc. Total time spent performing maintenance, excluding travel time,\nd. Detailed narrative description of the malfunction or PM action required,\ne. Complete list of parts replaced,\nf. Comments as to the cause of the malfunction when applicable,\ng. Date and time the work is completed.\n\nEquipment\n\nThe following is the list of equipment covered under this Statement of Work:\n\nEE/MXASC \n\nSN\nDescription ASC / DESC\nOSASC/DESC\n230784\nF0JR243\nOMNICELL PRODUCTION \n\nWindows Server 2016\nSERVER\n230786\nHL3FR33\nOMNICELL TEST SERVER\nWindows Server 2016\n230150\nMXL00520Q2\nCAROUSEL WORKSTATION 3\nWindows 10 L TSB\n\n230151\n\nMXL00520W9\nCAROUSEL WORKSTATION 4\nWindows 10 L TSB\n\n230152\nMXL00520Q1\nCAROUSEL WORKSTATION 5\nWindows 10 L TSB\n\n217629\nMXL00520W2\nCAROUSEL WORKSTATION 6\nWindows 10 L TSB\n\n\n102001644\nCAROUSEL\nSV-CAROUSL MEG\nRS350.1.2450.4.419.10,CRX\n\n102001645\nCAROUSEL\nSY-CAROUSEL MEG RS350.1.3050.4.419.12,CR\n\n102001646\nCAROUSEL\nSY-CAROUSEL MEG\nRS350.1.3050.4.419.12,CR\n\n102006459\nCAROUSEL\nSV-CAROUSL MEG\nRS350.1.3050.4.419.10 CR\n\nFederal Holidays Observed by the VA Medical Center\n\nNew Year's Day\nMartin Luther King, Jr. Day\nPresident's Day\nMemorial Day\nJuneteenth\nIndependence Day\nLabor Day\nColumbus Day\nVeterans Day\nThanksgiving Day\nChristmas Day; \nand any other day specifically designated by the President of the United States.\n\nFederal law and regulations\n\nFederal law and regulations, including the Federal Acquisition Regulations (FAR), shall govern this Purchase Order (PO). A Contractor's terms and conditions may be made a part of this PO but only if both parties expressly make it an addendum hereto. Federal law and regulation including, without limitation, the Contract Disputes Act (41 U.S.C. § 7101 et seq.), the Anti-Deficiency Act (31 U.S.C. §1341 et seq.), the Competition in Contracting Act (41 U.S.C. § 3301 et seq.), the Prompt Payment Act (31 U.S.C. § 3901 et seq.), and FAR 52.212-4 shall supersede, control, and render ineffective any inconsistent, conflicting, or duplicative provision in any Contractor Terms and Conditions. Any additional changes to this PO must be made by modification (Standard Form 30) and shall only be made by a warranted Contracting Officer. Nothing in this PO, or any addendum, shall be construed as a waiver of sovereign immunity.\n\nVA INFORMATION AND INFORMATION SYSTEM SECURTIY/PRIVACY LANGUAGE FOR INCLUSION INTO CONTRACTS\n\nGENERAL\n \nContractors, contractor personnel, subcontractors, and subcontractor personnel shall be subject to the same Federal laws, regulations, standards, and VA Directives and Handbooks as VA and VA personnel regarding information and information system security.\n \n1. ACCESS to VA INFORMATION AND VA INFORMATION SYSTEMS\n \nA contractor/subcontractor shall request logical (technical) or physical access to VA information and VA information systems for their employees, subcontractors, and affiliates only to the extent necessary to perform the services specified in the contract, agreement, or task order.\n\nThe contractor or subcontractor must notify the Contracting Officer immediately when an employee working on a VA system or with access to VA information is reassigned or leaves the contractor or subcontractor s employ. The Contracting Officer must also be notified immediately by the contractor or subcontractor prior to an unfriendly termination.\n\n2. VA INFORMATION CUSTODIAL Language\n \nInformation made available to the contractor or subcontractor by VA for the performance or administration of this contract or information developed by the contractor/subcontractor in performance or administration of the contract shall be used only for those purposes and shall not be used in any other way without the prior written agreement of the VA. This clause expressly limits the contractor/subcontractor's rights to use data as described in Rights in Data - General, FAR 52.227-14(d) (1).\n \nIf VA determines that the contractor has violated any of the information confidentiality, privacy, security, and other provisions of the contract, it shall be sufficient grounds for VA to withhold payment to the contractor or third party or terminate the contract for default or terminate for cause under Federal Acquisition Regulation (FAR) part 12.\n\n3. SECURITY INCIDENT INVESTIGATION\n \nThe term security incident means an event that has, or could have, resulted in unauthorized access to, loss or damage to VA assets, or sensitive information, or an action that breaches VA security procedures. The contractor/subcontractor shall immediately notify the COTR and simultaneously, the designated ISO and Privacy Officer for the contract of any known or suspected security/privacy incidents, or any unauthorized disclosure of sensitive information, including that contained in system(s) to which the contractor/subcontractor has access.\n\nTo the extent known by the contractor/subcontractor, the contractor/subcontractor s notice to VA shall identify the information involved, the circumstances surrounding the incident (including to whom, how, when, and where the VA information or assets were placed at risk or compromised), and any other information that the contractor/subcontractor considers relevant.\n \nWith respect to unsecured protected health information, the business associate is deemed to have discovered a data breach when the business associate knew or should have known of a breach of such information. Upon discovery, the business associate must notify the covered entity of the breach. Notifications need to be made in accordance with the executed business associate agreement.\n \nIn 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 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.\n \n4. LIQUIDATED DAMAGES FOR DATA BREACH\n \nConsistent with the requirements of 38 U.S.C. §5725, a contract may require access to sensitive personal information. If so, the contractor is liable to VA for liquidated damages in the event of a data breach or privacy incident involving any SPI the contractor/subcontractor processes or maintains under this contract. \n \nThe contractor/subcontractor shall provide notice to VA of a security incident as set forth in the Security Incident Investigation section above. Upon such notification, VA must secure from a non-Department entity or the VA Office of Inspector General an independent risk analysis of the data breach to determine the level of risk associated with the data breach for the potential misuse of any sensitive personal information involved in the data breach. The term 'data breach' means the loss, theft, or other unauthorized access, or any access other than that incidental to the scope of employment, to data containing sensitive personal information, in electronic or printed form, that results in the potential compromise of the confidentiality or integrity of the data. Contractor shall fully cooperate with the entity performing the risk analysis. Failure to cooperate may be deemed a material breach and grounds for contract termination.\n \nEach risk analysis shall address all relevant information concerning the data breach, including the following:\n \n(1) Nature of the event (loss, theft, unauthorized access);\n \n(2) Description of the event, including:\n \n(a) date of occurrence;\n \n(b) data elements involved, including any PII, such as full name, social security number, date of birth, home address, account number, disability code;\n \n(3) Number of individuals affected or potentially affected;\n \n(4) Names of individuals or groups affected or potentially affected;\n \n(5) Ease of logical data access to the lost, stolen or improperly accessed data in light of the degree of protection for the data, e.g., unencrypted, plain text;\n \n(6) Amount of time the data has been out of VA control;\n\n(7) The likelihood that the sensitive personal information will or has been compromised (made accessible to and usable by unauthorized persons);\n \n(8) Known misuses of data containing sensitive personal information, if any;\n \n(9) Assessment of the potential harm to the affected individuals;\n \n(10) Data breach analysis as outlined in 6500.2 Handbook, Management of Security and Privacy Incidents, as appropriate; and\n \n(11) Whether credit protection services may assist record subjects in avoiding or mitigating the results of identity theft based on the sensitive personal information that may have been compromised.\n \nBased on the determinations of the independent risk analysis, the contractor shall be responsible for paying to the VA liquidated damages in the amount of $37.50 per affected individual to cover the cost of providing credit protection services to affected individuals consisting of the following:\n \n (1) Notification;\n \n(2) One year of credit monitoring services consisting of automatic daily monitoring of at least 3 relevant credit bureau reports;\n \n (3) Data breach analysis;\n \n(4) Fraud resolution services, including writing dispute letters, initiating fraud alerts and credit freezes, to assist affected individuals to bring matters to resolution; \n \n (5) One year of identity theft insurance with $20,000.00 coverage at $0 deductible; and\n \n(6) Necessary legal expenses the subjects may incur to repair falsified or damaged credit records, histories, or financial affairs.\n \n\n5. TRAINING\n \nAll contractor employees and subcontractor employees requiring access to VA information and VA information systems shall complete the following before being granted access to VA information and its systems:\n \n(1) Successfully complete the appropriate VA privacy training and annually complete required privacy training (See below training); and\n(2) Successfully complete any additional cyber security or privacy training, as required for VA personnel with equivalent information system access\n \nThe contractor shall provide to the contracting officer and/or the COTR a copy of the training certificates for each applicable employee within 1 week of the initiation of the contract and annually thereafter, as required. \n \nFailure to complete the mandatory annual training, within the timeframe required, 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 training and documents are complete.\n \n7. ADDITIONAL Requirements\n \nThe COR is responsible for coordinating with the Police prior to contractor arrival to identify the names of contractor personnel so that Police can ensure sufficient number of contractor badges are available for issuance prior to beginning work. COR is also responsible for signing out and signing in temporary contractor badges. \n \nThe COR is also responsible for maintaining copies of signed Privacy training for all contractors according to RCS 10-1.\n \nAny work performed outside of official VA business hours after hours will require escorts.\n \nEscort duties for un-cleared contractors are strictly limited to government officials, specifically VA employees. At no time are contractors allowed to escort other contractors.\n\n\nACCESS TO VA INFORMATION AND VA INFORMATION SYSTEMS\n\nA contractor/subcontractor shall request logical (technical) or physical access to VA\ninformation and VA information systems for their employees, subcontractors, and affiliates only to the extent necessary to perform the services specified in the contract, agreement, or task order.\n\nContract personnel who require access to national security programs must have a valid\nsecurity clearance. National Industrial Security Program (NISP) was established by Executive Order 12829 to ensure that cleared U.S. defense industry contract personnel safeguard the classified information in their possession while performing work on contracts, programs, bids, or research and development efforts. The Department of Veterans Affairs does not have a Memorandum of Agreement with Defense Security Service (DSS). Verification of a Security Clearance must be processed through the Special Security Officer located in the Planning and National Security Service within the Office of Operations, Security, and Preparedness.\n\nCustom software development and outsourced operations must be located in the United States, to the maximum extent practical. If such services are proposed to be performed abroad and are not disallowed by other VA policy or mandates, the ontractor/subcontractor must state where all non-U.S. services are provided and detail a security plan, deemed to be acceptable by VA, specifically to address mitigation of the resulting problems of communication, control, data protection, and so forth. Location within the U.S. may be an evaluation factor.\n\nd. The contractor or subcontractor must notify the Contracting Officer immediately when\nan employee working on a VA system or with access to VA information is reassigned or leaves the contractor or subcontractor's employment. The Contracting Officer must also be notified immediately by the contractor or subcontractor prior to an unfriendly termination.\n\nVA INFORMATION CUSTODIAL LANGUAGE\n\nInformation made available to the contractor or subcontractor by VA for the performance or administration of this contract or information developed by the contractor/subcontractor in performance or administration of the contract shall be used only for those purposes and shall not be used in any other way without the prior written agreement of the VA. This clause expressly limits the contractor/subcontractor's rights to use data as described in Rights in Data- General, FAR 52.227-14(d) (1).\n\nVA information should not be co-mingled, if possible, with any other data on the\ncontractors/subcontractor's information systems or media storage systems in order to ensure VA requirements related to data protection and media sanitization can be met. If co-mingling must be allowed to meet the requirements of the business need, the contractor must ensure that VA's information is returned to the VA or destroyed in accordance with VA's sanitization requirements. VA reserves the right to conduct on-site inspections of contractor and subcontractor IT resources to ensure data security controls, separation of data and job duties, and destruction/media sanitization procedures are in compliance with VA directive requirements.\n\nPrior to termination or completion of this contract, contractor/subcontractor must not\ndestroy information received from VA, or gathered/created by the contractor in the course of performing this contract without prior written approval by the VA. Any data destruction done on behalf of VA by a contractor/subcontractor must be done in accordance with National Archives and Records Administration (NARA) requirements as outlined in VA Directive 6300, Records and Information Management and its Handbook 6300.1 Records Management Procedures, applicable VA Records Control Schedules, and VA Handbook 6500.1, Electronic Media Sanitization. Self-certification by the contractor that the data destruction requirements above have been met must be sent to the VA Contracting Officer within 30 days of termination of the contract.\n\nd. The contractor/subcontractor must receive, gather, store, back up, maintain, use,\ndisclose and dispose of VA information only in compliance with the terms of the contract and applicable Federal and VA information confidentiality and security laws, regulations and policies. If Federal or VA information confidentiality and security laws, regulations and policies become applicable to the VA information or information systems after execution of the contract, or if NIST issues or updates applicable FIPS or Special Publications (SP) after execution of this contract, the parties agree to negotiate in good faith to implement the information confidentiality and security laws, regulations and policies in this contract.\n\nThe contractor/subcontractor shall not make copies of VA information except as\nauthorized and necessary to perform the terms of the agreement or to preserve electronic information stored on contractor/subcontractor electronic storage media for restoration in case any electronic equipment or data used by the contractor/subcontractor needs to be restored to an operating state. If copies are made for restoration purposes, after the restoration is complete, the copies must be appropriately destroyed.\n\nIf VA determines that the contractor has violated any of the information confidentiality,\nprivacy, and security provisions of the contract, it shall be sufficient grounds for VA to withhold payment to the contractor or third party or terminate the contract for default or terminate for cause under Federal Acquisition Regulation (FAR) part 12.\n\nIf a VHA contract is terminated for cause, the associated BAA must also be terminated\nand appropriate actions taken in accordance with VHA Handbook 1600.01, Business\nAssociate Agreements. Absent an agreement to use or disclose protected health information, there is no business associate relationship.\n\nThe contractor/subcontractor must store, transport, or transmit VA sensitive information in an encrypted form, using VA-approved encryption tools that are, at a minimum, FIPS 140-2 validated.\n\nThe contractor/subcontractor's firewall and Web services security controls, if applicable,\nshall meet or exceed VA's minimum requirements. VA Configuration Guidelines are available upon request.\n\nExcept for uses and disclosures of VA information authorized by this contract for\nperformance of the contract, the contractor/subcontractor may use and disclose VA information only in two other situations: (i) in response to a qualifying order of a court of competent jurisdiction, or (ii) with VA's prior written approval. The contractor/subcontractor must refer all requests for, demands for production of, or inquiries about, VA information and information systems to the VA contracting officer for response.\n\nNotwithstanding the provision above, the contractor/subcontractor shall not release VA\nrecords 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 health records pertaining to drug addiction, sickle cell anemia, alcoholism or alcohol abuse, or infection with human immunodeficiency virus. If the contractor/subcontractor is in receipt of a court order or other requests for the above mentioned information, that contractor/subcontractor shall immediately refer such court orders or other requests to the VA contracting officer for response.\n\nINFORMATION SYSTEM DESIGN AND DEVELOPMENT\n\nThe standard installation, operation, maintenance, updating, and patching of software\nshall not alter the configuration settings from the VA approved and FDCC configuration.\nInformation technology staff must also use the Windows Installer Service for installation to the default \"program files\" directory and silently install and uninstall.\n\nThe vendor shall ensure the security of all procured or developed systems and\ntechnologies, including their subcomponents (hereinafter referred to as \"Systems\"), throughout the life of this contract and any extension, warranty, or maintenance periods. This includes, but is not limited to workarounds, patches, hotfixes, upgrades, and any physical components (hereafter referred to as Security Fixes) which may be necessary to fix all security vulnerabilities published or known to the vendor anywhere in the Systems, including Operating Systems and firmware. The vendor shall ensure that Security Fixes shall not negatively impact the Systems.\n\nThe vendor shall notify VA within 24 hours of the discovery or disclosure of successful\nexploits of the vulnerability which can compromise the security of the Systems (including the confidentiality or integrity of its data and operations, or the availability of the system). Such issues shall be remediated as quickly as is practical, but in no event longer than 3 days.\n\nWhen the Security Fixes involve installing third party patches (such as Microsoft OS\npatches or Adobe Acrobat), the vendor will provide written notice to the VA that the patch has been validated as not affecting the Systems within 10 working days. When the vendor is responsible for operations or maintenance of the Systems, they shall apply the Security Fixes within 10 days.\n\n All other vulnerabilities shall be remediated as specified in this paragraph in a timely\nmanner based on risk, but within 60 days of discovery or disclosure. Exceptions to this\nparagraph (e.g. for the convenience of VA) shall only be granted with approval of the\ncontracting officer and the VA Assistant Secretary for Office of Information and Technology.\n\nINFORMATION SYSTEM HOSTING, OPERATION, MAINTENANCE, OR USE\n\nBio-Medical devices and other equipment or systems containing media (hard drives,\noptical disks, etc.) with VA sensitive information must not be returned to the vendor at the end of lease, for trade-in, or other purposes. The options are:\n\nVendor must accept the system without the drive;\n\nVA's initial medical device purchase includes a spare drive which must be installed in\nplace of the original drive at time of turn-in; or\n\nVA must reimburse the company for media at a reasonable open market replacement\ncost at time of purchase.\n\nBio-Medical devices and other equipment or systems containing media (hard drives,\noptical disks, etc.) with VA sensitive information must not be returned to the vendor at the end of lease, for trade-in, or other purposes. The options are:\n\nVendor must accept the system without the drive;\n\nVA's initial medical device purchase includes a spare drive which must be installed in\nplace of the original drive at time of turn-in; or\n\nVA must reimburse the company for media at a reasonable open market replacement\ncost at time of purchase.\n\nDue to the highly specialized and sometimes proprietary hardware and software\nassociated with medical equipment/systems, if it is not possible for the VA to retain the hard drive, then;\n\nThe equipment vendor must have an existing BAA if the device being traded in has\nsensitive information stored on it and hard drive(s) from the system are being returned\nphysically intact; and\n\nAny fixed hard drive on the device must be non-destructively sanitized to the greatest\nextent possible without negatively impacting system operation. Selective clearing down to patient data folder level is recommended using VA approved and validated overwriting technologies/methods/tools. Applicable media sanitization specifications need to be preapproved and described in the purchase order or contract.\n\nA statement needs to be signed by the Director (System Owner) that states that the\ndrive could not be removed and that (a) and (b) controls above are in place and completed.\nThe ISO needs to maintain the documentation.\n\nSECURITY INCIDENT INVESTIGATION\n\nThe term \"security incident\" means an event that has, or could have, resulted in\nunauthorized access to, loss or damage to VA assets, or sensitive information, or an action that breaches VA security procedures. The contractor/subcontractor shall immediately notify the COTR and simultaneously, the designated ISO and Privacy Officer for the contract of any known or suspected security/privacy incidents, or any unauthorized disclosure of sensitive information, including that contained in system(s) to which the contractor/subcontractor has access.\n\nTo the extent known by the contractor/subcontractor, the contractor/subcontractor's\nnotice to VA shall identify the information involved, the circumstances surrounding the incident (including to whom, how, when, and where the VA information or assets were placed at risk or compromised), and any other information that the ontractor/subcontractor considers relevant.\n\nWith respect to unsecured protected health information, the business associate is\ndeemed to have discovered a data breach when the business associate knew or should have known of a breach of such information. Upon discovery, the business associate must notify the covered entity of the breach. Notifications need to be made in accordance with the executed business associate agreement.\n\nIn instances of theft or break-in or other criminal activity, the contractor/subcontractor\nmust concurrently report the incident to the appropriate law enforcement entity (or entities) of jurisdiction, including the VA OIG and 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.\n\n\nCONTRACTOR RULES OF BEHAVIOR\n\nThis User Agreement contains rights and authorizations regarding my access to and use\nof any information assets or resources associated with my performance of services under\nthe contract terms with the Department of Veterans Affairs (VA). This User Agreement\ncovers my access to all VA data whether electronic or hard copy (\"Data\"), VA information\nsystems and resources (\"Systems\"), and VA sites (\"Sites\"). This User Agreement\nincorporates Rules of Behavior for using VA, and other information systems and\nresources under the contract.\n\nGENERAL TERMS AND CONDITIONS FOR ALL ACTIONS AND ACTIVITIES UNDER\nTHE CONTRACT:\n\nunderstand and agree that I have no reasonable expectation of privacy in\naccessing or using any VA, or other Federal Government information systems.\n\nI consent to reviews and actions by the Office of Information & Technology (Ol&T)\nstaff designated and authorized by the VA Chief Information Officer (CIO) and to the VA\nOIG regarding my access to and use of any information assets or resources associated\nwith my performance of services under the contract terms with the VA. These actions\nmay include monitoring, recording, copying, inspecting, restricting access, blocking,\ntracking, and disclosing to all authorized Ol&T, VA, and law enforcement personnel as\ndirected by the VACIO without my prior consent or notification.\n\nI consent to reviews and actions by authorized VA systems administrators and\nInformation Security Officers solely for protection of the VA infrastructure, including, but not limited to monitoring, recording, auditing, inspecting, investigating, restricting access, blocking, tracking, disclosing to authorized personnel, or any other authorized actions by all authorized Ol&T, VA, and law enforcement personnel.\n\nI understand and accept that unauthorized attempts or acts to access, upload,\nchange, or delete information on Federal Government systems; modify Federal\ngovernment systems; deny access to Federal government systems; accrue resources for\nunauthorized use on Federal government systems; or otherwise misuse Federal\ngovernment systems or resources are prohibited.\n\nI understand that such unauthorized attempts or acts are subject to action that may\nresult in criminal, civil, or administrative penalties. This includes penalties for violations\nof Federal laws including, but not limited to, 18 U.S.C. §1030 (fraud and related activity in connection with computers) and 18 U.S.C. §2701 (unlawful access to stored\ncommunications).\n\nRECORDS MANAGEMENT OBLIGATIONS\n\nApplicability\n\nThis clause applies to all Contractors whose employees create, work with, or otherwise handle\nFederal records, as defined in Section B, regardless of the medium in which the record exists.\n\nDefinitions\n\n\"Federal record\" as defined in 44 U.S.C. § 3301, includes all recorded information, regardless\nof form or characteristics, made or received by a Federal agency under Federal law or in\nconnection with the transaction of public business and preserved or appropriate for\npreservation by that agency or its legitimate successor as evidence of the organization,\nfunctions, policies, decisions, procedures, operations, or other activities of the United States\nGovernment or because of the informational value of data in them.\n\nThe term Federal record:\n\nincludes VASTLHCS records.\n\ndoes not include personal materials.\n\napplies to records created, received, or maintained by Contractors pursuant to their [Agency] contract.\n\nmay include deliverables and documentation associated with deliverables.\n\nRequirements\n\nContractor 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 XI I 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.\n\nIn 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.\n\nIn accordance with 36 CFR 1222.32, Contractor shall maintain all records created for\nGovernment 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.\n\nVHA 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 [Agency] 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\nremoval, defacing, alteration, or destruction of records, Contractor must report to VHA. The agency must report promptly to NARA in accordance with 36 CFR 1230.\ns. 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]. \n\nThe 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 VHA 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).\n\nThe Contractor is required to obtain the Contracting Officer's approval prior to\nengaging in any contractual relationship (sub-contractor) in support of this contract\nrequiring 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 VHA guidance for protecting sensitive, proprietary information, classified, and controlled unclassified information.\n\nThe Contractor shall only use Government IT equipment for purposes specifically tied to or authorized by the contract and in accordance with VHA policy.\n\nThe Contractor shall not create or maintain any records containing any non-public\nVHA information that are not specifically tied to or authorized by the contract.\n\nThe Contractor shall not retain, use, sell, or disseminate copies of any deliverable\nthat contains information covered by the Privacy Act of 197 4 or that which is generally protected from public disclosure by an exemption to the Freedom of Information Act.\n\nThe VHA owns the rights to all data and records produced as part of this contract. All\ndeliverables under the contract are the property of the U.S. Government for which VHA 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.\n\nTraining. All Contractor employees assigned to this contract who create, work with, or otherwise handle records are required to take VHA -provided records management training. The Contractor is responsible for confirming training has been completed according to agency policies, including initial training and any annual or refresher training. [Note: To the extent an agency requires contractors to complete records management training, the agency must provide the training to the contractor.]\n\nd. Flowdown of requirements to subcontractors\n\nThe Contractor shall incorporate the substance of this clause, its terms and requirements including this paragraph, in all subcontracts under this [contract vehicle], and require written subcontractor acknowledgment of same.\n\nViolation by a subcontractor of any provision set forth in this clause will be\nattributed to the Contractor.\n\n"} Solicitation Number: 36C25526Q0214 Type: Sources Sought Base Type: Sources Sought NAICS: 811210 Classification Code: J065 Response Deadline: 2026-02-23T08:00:00-06:00 Office Address: LEAVENWORTH, KS Place of Performance: Columbia, MO, 65201-5275 POC: Erika Kobulnicky, Erika.Kobulnicky@va.gov, 913-946-1991 {"description":"PERFORMANCE WORK STATEMENT\nOmnicell Maintenance Services -Columbia\nGeneral Requirements:\n\nThe Contractor shall provide services and support at the locations identified in this Performance Work Statement. The Government reserves the right to add, remove, or modify locations and facilities as mission requirements evolve across the current and future operational footprint. The Contractor shall accommodate these changes within the scope of the contract without disruption to services. Any adjustments to pricing, schedule, or resources resulting from such changes shall be addressed through the appropriate contractual modification process in accordance with the applicable Changes clause.\n\nPlace of Performance:\n\nHarry S. Truman Memorial Veterans Hospital (HSTMVH)\n800 Hospital Drive\nColumbia, MO 65201-5275\n\nPeriod of Performance:\nIt is the Governments intent to award a fixed price contract. Contract period of performance will commence on April 1, 2026, and extend through March 31, 2027.\nBackground: \nThe Pharmacy currently is requesting routine maintenance for their Omnicell systems and associated equipment. This equipment is used to dispense and package medications for patients. The Columbia VA Medical Center is requesting routine maintenance as required by the Truman VA Medical Center Healthcare Technology Management Medical Equipment Management Program and the OEM specifications for Omnicell medication dispensing systems. Timely repair of this equipment is essential to the safety of the patient population and the efficient operation of the Pharmacy.\nRequired Services:\nThe contractor must be an authorized service provider for the Original Equipment Manufacturer (OEM) and provide OEM letter.\nThe contractor shall provide maintenance and repair on site (when determined by contract COR), to include all replacement parts, labor, travel expenses, telephone technical support, remote on-line support (maintain a current MOU/ISA allowing VPN access), software, tools, test equipment and other incidentals necessary to maintain and/or restore the listed equipment (see below), to operating specifications according to the manufacturer's specifications. This includes maintenance and repair both hardware and software (this includes primary operating systems and proprietary software) of the Production Server, Test Server, Carousels and all peripheral PC s/devices(Scanners & Printers). All maintenance and repairs shall be provided during the contract business hours of 8:00AM 5:00 PM, Monday through Friday, excluding federal holidays unless otherwise approved by Contract COR. Upon placement of a service request, the contractor must respond to the contract COR within one (1) hour by telephone for diagnostic response, and must provide priority on-site service response within four (4) business hours after contacting the VA, unless otherwise determined by contract COR. \nAll scheduled preventive maintenance for equipment listed will be performed by Contractor. Contractor will provide (at no additional cost) any part(s) found out of manufacture specification during the preventive maintenance inspection activities. Contractor shall assist with Planned Maintenance, Quality Assurance and Safety Checks. Scheduling of preventive maintenance will be coordinated between the contractor and the contract COR. \nAll services for this contract must meet manufacturer performance and technical specifications, Federal Regulations, and other specifications that may apply such as National Electric Code (NEC), Life Safety Code (LSC), Joint Commission (JC), and VA Regulations. The contractor shall ONLY respond to service calls placed by Biomedical Engineering to include: The Contracting Officer s Representative (COR) Adam Richardson (573) 814-6000 ext. 52408, or designee. \nThe contractor accessing the listed equipment must have an approved VA VPN network account established (existing MOU/ISA). All VPN accounts will be coordinated through the facilities ISO (Information Security Officer) and will comply with all VA regulations and standards to include OA&MM Information Letter (IL 90-01-6) dated July 16, 2001. Additionally, the contractor will be responsible for adhering to the following security requirements/clauses:\nALL SERVICE ENGINEERS MUST REPORT to the FM Office (Building 22) to sign in before work\nis begun on the premises of the HSTMVH and must also to sign out after work has been completed. The contractor must furnish a detailed field service report, or equivalent, showing work completed, listing all repairs and/or repair parts used to maintain operating efficiency of the equipment. When possible, this report may be delivered to Biomedical Engineering before contractor leaves the station or via email please see section B.4 for contact information. If it is necessary for the contractor to work after 4:30pm, permission must be granted from the Contract POC. If the service was completed after regular duty hours, the FSE will sign out and leave the report in the Engineering Control Center, room DO 19 of the hospital.\nFailure to provide the service report may lead to a delay in payment as verification is required to ensure service was provided. The service report from the contractor must contain, at a minimum, the following information:\na. Date and time of the contractor's arrival on station,\nb. Type, model, and serial number(s) of all equipment on which maintenance was performed,\nc. Total time spent performing maintenance, excluding travel time,\nd. Detailed narrative description of the malfunction or PM action required,\ne. Complete list of parts replaced,\nf. Comments as to the cause of the malfunction when applicable,\ng. Date and time the work is completed.\n\nEquipment\n\nThe following is the list of equipment covered under this Statement of Work:\n\nEE/MXASC \n\nSN\nDescription ASC / DESC\nOSASC/DESC\n230784\nF0JR243\nOMNICELL PRODUCTION \n\nWindows Server 2016\nSERVER\n230786\nHL3FR33\nOMNICELL TEST SERVER\nWindows Server 2016\n230150\nMXL00520Q2\nCAROUSEL WORKSTATION 3\nWindows 10 L TSB\n\n230151\n\nMXL00520W9\nCAROUSEL WORKSTATION 4\nWindows 10 L TSB\n\n230152\nMXL00520Q1\nCAROUSEL WORKSTATION 5\nWindows 10 L TSB\n\n217629\nMXL00520W2\nCAROUSEL WORKSTATION 6\nWindows 10 L TSB\n\n\n102001644\nCAROUSEL\nSV-CAROUSL MEG\nRS350.1.2450.4.419.10,CRX\n\n102001645\nCAROUSEL\nSY-CAROUSEL MEG RS350.1.3050.4.419.12,CR\n\n102001646\nCAROUSEL\nSY-CAROUSEL MEG\nRS350.1.3050.4.419.12,CR\n\n102006459\nCAROUSEL\nSV-CAROUSL MEG\nRS350.1.3050.4.419.10 CR\n\nFederal Holidays Observed by the VA Medical Center\n\nNew Year's Day\nMartin Luther King, Jr. Day\nPresident's Day\nMemorial Day\nJuneteenth\nIndependence Day\nLabor Day\nColumbus Day\nVeterans Day\nThanksgiving Day\nChristmas Day; \nand any other day specifically designated by the President of the United States.\n\nFederal law and regulations\n\nFederal law and regulations, including the Federal Acquisition Regulations (FAR), shall govern this Purchase Order (PO). A Contractor's terms and conditions may be made a part of this PO but only if both parties expressly make it an addendum hereto. Federal law and regulation including, without limitation, the Contract Disputes Act (41 U.S.C. § 7101 et seq.), the Anti-Deficiency Act (31 U.S.C. §1341 et seq.), the Competition in Contracting Act (41 U.S.C. § 3301 et seq.), the Prompt Payment Act (31 U.S.C. § 3901 et seq.), and FAR 52.212-4 shall supersede, control, and render ineffective any inconsistent, conflicting, or duplicative provision in any Contractor Terms and Conditions. Any additional changes to this PO must be made by modification (Standard Form 30) and shall only be made by a warranted Contracting Officer. Nothing in this PO, or any addendum, shall be construed as a waiver of sovereign immunity.\n\nVA INFORMATION AND INFORMATION SYSTEM SECURTIY/PRIVACY LANGUAGE FOR INCLUSION INTO CONTRACTS\n\nGENERAL\n \nContractors, contractor personnel, subcontractors, and subcontractor personnel shall be subject to the same Federal laws, regulations, standards, and VA Directives and Handbooks as VA and VA personnel regarding information and information system security.\n \n1. ACCESS to VA INFORMATION AND VA INFORMATION SYSTEMS\n \nA contractor/subcontractor shall request logical (technical) or physical access to VA information and VA information systems for their employees, subcontractors, and affiliates only to the extent necessary to perform the services specified in the contract, agreement, or task order.\n\nThe contractor or subcontractor must notify the Contracting Officer immediately when an employee working on a VA system or with access to VA information is reassigned or leaves the contractor or subcontractor s employ. The Contracting Officer must also be notified immediately by the contractor or subcontractor prior to an unfriendly termination.\n\n2. VA INFORMATION CUSTODIAL Language\n \nInformation made available to the contractor or subcontractor by VA for the performance or administration of this contract or information developed by the contractor/subcontractor in performance or administration of the contract shall be used only for those purposes and shall not be used in any other way without the prior written agreement of the VA. This clause expressly limits the contractor/subcontractor's rights to use data as described in Rights in Data - General, FAR 52.227-14(d) (1).\n \nIf VA determines that the contractor has violated any of the information confidentiality, privacy, security, and other provisions of the contract, it shall be sufficient grounds for VA to withhold payment to the contractor or third party or terminate the contract for default or terminate for cause under Federal Acquisition Regulation (FAR) part 12.\n\n3. SECURITY INCIDENT INVESTIGATION\n \nThe term security incident means an event that has, or could have, resulted in unauthorized access to, loss or damage to VA assets, or sensitive information, or an action that breaches VA security procedures. The contractor/subcontractor shall immediately notify the COTR and simultaneously, the designated ISO and Privacy Officer for the contract of any known or suspected security/privacy incidents, or any unauthorized disclosure of sensitive information, including that contained in system(s) to which the contractor/subcontractor has access.\n\nTo the extent known by the contractor/subcontractor, the contractor/subcontractor s notice to VA shall identify the information involved, the circumstances surrounding the incident (including to whom, how, when, and where the VA information or assets were placed at risk or compromised), and any other information that the contractor/subcontractor considers relevant.\n \nWith respect to unsecured protected health information, the business associate is deemed to have discovered a data breach when the business associate knew or should have known of a breach of such information. Upon discovery, the business associate must notify the covered entity of the breach. Notifications need to be made in accordance with the executed business associate agreement.\n \nIn 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 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.\n \n4. LIQUIDATED DAMAGES FOR DATA BREACH\n \nConsistent with the requirements of 38 U.S.C. §5725, a contract may require access to sensitive personal information. If so, the contractor is liable to VA for liquidated damages in the event of a data breach or privacy incident involving any SPI the contractor/subcontractor processes or maintains under this contract. \n \nThe contractor/subcontractor shall provide notice to VA of a security incident as set forth in the Security Incident Investigation section above. Upon such notification, VA must secure from a non-Department entity or the VA Office of Inspector General an independent risk analysis of the data breach to determine the level of risk associated with the data breach for the potential misuse of any sensitive personal information involved in the data breach. The term 'data breach' means the loss, theft, or other unauthorized access, or any access other than that incidental to the scope of employment, to data containing sensitive personal information, in electronic or printed form, that results in the potential compromise of the confidentiality or integrity of the data. Contractor shall fully cooperate with the entity performing the risk analysis. Failure to cooperate may be deemed a material breach and grounds for contract termination.\n \nEach risk analysis shall address all relevant information concerning the data breach, including the following:\n \n(1) Nature of the event (loss, theft, unauthorized access);\n \n(2) Description of the event, including:\n \n(a) date of occurrence;\n \n(b) data elements involved, including any PII, such as full name, social security number, date of birth, home address, account number, disability code;\n \n(3) Number of individuals affected or potentially affected;\n \n(4) Names of individuals or groups affected or potentially affected;\n \n(5) Ease of logical data access to the lost, stolen or improperly accessed data in light of the degree of protection for the data, e.g., unencrypted, plain text;\n \n(6) Amount of time the data has been out of VA control;\n\n(7) The likelihood that the sensitive personal information will or has been compromised (made accessible to and usable by unauthorized persons);\n \n(8) Known misuses of data containing sensitive personal information, if any;\n \n(9) Assessment of the potential harm to the affected individuals;\n \n(10) Data breach analysis as outlined in 6500.2 Handbook, Management of Security and Privacy Incidents, as appropriate; and\n \n(11) Whether credit protection services may assist record subjects in avoiding or mitigating the results of identity theft based on the sensitive personal information that may have been compromised.\n \nBased on the determinations of the independent risk analysis, the contractor shall be responsible for paying to the VA liquidated damages in the amount of $37.50 per affected individual to cover the cost of providing credit protection services to affected individuals consisting of the following:\n \n (1) Notification;\n \n(2) One year of credit monitoring services consisting of automatic daily monitoring of at least 3 relevant credit bureau reports;\n \n (3) Data breach analysis;\n \n(4) Fraud resolution services, including writing dispute letters, initiating fraud alerts and credit freezes, to assist affected individuals to bring matters to resolution; \n \n (5) One year of identity theft insurance with $20,000.00 coverage at $0 deductible; and\n \n(6) Necessary legal expenses the subjects may incur to repair falsified or damaged credit records, histories, or financial affairs.\n \n\n5. TRAINING\n \nAll contractor employees and subcontractor employees requiring access to VA information and VA information systems shall complete the following before being granted access to VA information and its systems:\n \n(1) Successfully complete the appropriate VA privacy training and annually complete required privacy training (See below training); and\n(2) Successfully complete any additional cyber security or privacy training, as required for VA personnel with equivalent information system access\n \nThe contractor shall provide to the contracting officer and/or the COTR a copy of the training certificates for each applicable employee within 1 week of the initiation of the contract and annually thereafter, as required. \n \nFailure to complete the mandatory annual training, within the timeframe required, 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 training and documents are complete.\n \n7. ADDITIONAL Requirements\n \nThe COR is responsible for coordinating with the Police prior to contractor arrival to identify the names of contractor personnel so that Police can ensure sufficient number of contractor badges are available for issuance prior to beginning work. COR is also responsible for signing out and signing in temporary contractor badges. \n \nThe COR is also responsible for maintaining copies of signed Privacy training for all contractors according to RCS 10-1.\n \nAny work performed outside of official VA business hours after hours will require escorts.\n \nEscort duties for un-cleared contractors are strictly limited to government officials, specifically VA employees. At no time are contractors allowed to escort other contractors.\n\n\nACCESS TO VA INFORMATION AND VA INFORMATION SYSTEMS\n\nA contractor/subcontractor shall request logical (technical) or physical access to VA\ninformation and VA information systems for their employees, subcontractors, and affiliates only to the extent necessary to perform the services specified in the contract, agreement, or task order.\n\nContract personnel who require access to national security programs must have a valid\nsecurity clearance. National Industrial Security Program (NISP) was established by Executive Order 12829 to ensure that cleared U.S. defense industry contract personnel safeguard the classified information in their possession while performing work on contracts, programs, bids, or research and development efforts. The Department of Veterans Affairs does not have a Memorandum of Agreement with Defense Security Service (DSS). Verification of a Security Clearance must be processed through the Special Security Officer located in the Planning and National Security Service within the Office of Operations, Security, and Preparedness.\n\nCustom software development and outsourced operations must be located in the United States, to the maximum extent practical. If such services are proposed to be performed abroad and are not disallowed by other VA policy or mandates, the ontractor/subcontractor must state where all non-U.S. services are provided and detail a security plan, deemed to be acceptable by VA, specifically to address mitigation of the resulting problems of communication, control, data protection, and so forth. Location within the U.S. may be an evaluation factor.\n\nd. The contractor or subcontractor must notify the Contracting Officer immediately when\nan employee working on a VA system or with access to VA information is reassigned or leaves the contractor or subcontractor's employment. The Contracting Officer must also be notified immediately by the contractor or subcontractor prior to an unfriendly termination.\n\nVA INFORMATION CUSTODIAL LANGUAGE\n\nInformation made available to the contractor or subcontractor by VA for the performance or administration of this contract or information developed by the contractor/subcontractor in performance or administration of the contract shall be used only for those purposes and shall not be used in any other way without the prior written agreement of the VA. This clause expressly limits the contractor/subcontractor's rights to use data as described in Rights in Data- General, FAR 52.227-14(d) (1).\n\nVA information should not be co-mingled, if possible, with any other data on the\ncontractors/subcontractor's information systems or media storage systems in order to ensure VA requirements related to data protection and media sanitization can be met. If co-mingling must be allowed to meet the requirements of the business need, the contractor must ensure that VA's information is returned to the VA or destroyed in accordance with VA's sanitization requirements. VA reserves the right to conduct on-site inspections of contractor and subcontractor IT resources to ensure data security controls, separation of data and job duties, and destruction/media sanitization procedures are in compliance with VA directive requirements.\n\nPrior to termination or completion of this contract, contractor/subcontractor must not\ndestroy information received from VA, or gathered/created by the contractor in the course of performing this contract without prior written approval by the VA. Any data destruction done on behalf of VA by a contractor/subcontractor must be done in accordance with National Archives and Records Administration (NARA) requirements as outlined in VA Directive 6300, Records and Information Management and its Handbook 6300.1 Records Management Procedures, applicable VA Records Control Schedules, and VA Handbook 6500.1, Electronic Media Sanitization. Self-certification by the contractor that the data destruction requirements above have been met must be sent to the VA Contracting Officer within 30 days of termination of the contract.\n\nd. The contractor/subcontractor must receive, gather, store, back up, maintain, use,\ndisclose and dispose of VA information only in compliance with the terms of the contract and applicable Federal and VA information confidentiality and security laws, regulations and policies. If Federal or VA information confidentiality and security laws, regulations and policies become applicable to the VA information or information systems after execution of the contract, or if NIST issues or updates applicable FIPS or Special Publications (SP) after execution of this contract, the parties agree to negotiate in good faith to implement the information confidentiality and security laws, regulations and policies in this contract.\n\nThe contractor/subcontractor shall not make copies of VA information except as\nauthorized and necessary to perform the terms of the agreement or to preserve electronic information stored on contractor/subcontractor electronic storage media for restoration in case any electronic equipment or data used by the contractor/subcontractor needs to be restored to an operating state. If copies are made for restoration purposes, after the restoration is complete, the copies must be appropriately destroyed.\n\nIf VA determines that the contractor has violated any of the information confidentiality,\nprivacy, and security provisions of the contract, it shall be sufficient grounds for VA to withhold payment to the contractor or third party or terminate the contract for default or terminate for cause under Federal Acquisition Regulation (FAR) part 12.\n\nIf a VHA contract is terminated for cause, the associated BAA must also be terminated\nand appropriate actions taken in accordance with VHA Handbook 1600.01, Business\nAssociate Agreements. Absent an agreement to use or disclose protected health information, there is no business associate relationship.\n\nThe contractor/subcontractor must store, transport, or transmit VA sensitive information in an encrypted form, using VA-approved encryption tools that are, at a minimum, FIPS 140-2 validated.\n\nThe contractor/subcontractor's firewall and Web services security controls, if applicable,\nshall meet or exceed VA's minimum requirements. VA Configuration Guidelines are available upon request.\n\nExcept for uses and disclosures of VA information authorized by this contract for\nperformance of the contract, the contractor/subcontractor may use and disclose VA information only in two other situations: (i) in response to a qualifying order of a court of competent jurisdiction, or (ii) with VA's prior written approval. The contractor/subcontractor must refer all requests for, demands for production of, or inquiries about, VA information and information systems to the VA contracting officer for response.\n\nNotwithstanding the provision above, the contractor/subcontractor shall not release VA\nrecords 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 health records pertaining to drug addiction, sickle cell anemia, alcoholism or alcohol abuse, or infection with human immunodeficiency virus. If the contractor/subcontractor is in receipt of a court order or other requests for the above mentioned information, that contractor/subcontractor shall immediately refer such court orders or other requests to the VA contracting officer for response.\n\nINFORMATION SYSTEM DESIGN AND DEVELOPMENT\n\nThe standard installation, operation, maintenance, updating, and patching of software\nshall not alter the configuration settings from the VA approved and FDCC configuration.\nInformation technology staff must also use the Windows Installer Service for installation to the default \"program files\" directory and silently install and uninstall.\n\nThe vendor shall ensure the security of all procured or developed systems and\ntechnologies, including their subcomponents (hereinafter referred to as \"Systems\"), throughout the life of this contract and any extension, warranty, or maintenance periods. This includes, but is not limited to workarounds, patches, hotfixes, upgrades, and any physical components (hereafter referred to as Security Fixes) which may be necessary to fix all security vulnerabilities published or known to the vendor anywhere in the Systems, including Operating Systems and firmware. The vendor shall ensure that Security Fixes shall not negatively impact the Systems.\n\nThe vendor shall notify VA within 24 hours of the discovery or disclosure of successful\nexploits of the vulnerability which can compromise the security of the Systems (including the confidentiality or integrity of its data and operations, or the availability of the system). Such issues shall be remediated as quickly as is practical, but in no event longer than 3 days.\n\nWhen the Security Fixes involve installing third party patches (such as Microsoft OS\npatches or Adobe Acrobat), the vendor will provide written notice to the VA that the patch has been validated as not affecting the Systems within 10 working days. When the vendor is responsible for operations or maintenance of the Systems, they shall apply the Security Fixes within 10 days.\n\n All other vulnerabilities shall be remediated as specified in this paragraph in a timely\nmanner based on risk, but within 60 days of discovery or disclosure. Exceptions to this\nparagraph (e.g. for the convenience of VA) shall only be granted with approval of the\ncontracting officer and the VA Assistant Secretary for Office of Information and Technology.\n\nINFORMATION SYSTEM HOSTING, OPERATION, MAINTENANCE, OR USE\n\nBio-Medical devices and other equipment or systems containing media (hard drives,\noptical disks, etc.) with VA sensitive information must not be returned to the vendor at the end of lease, for trade-in, or other purposes. The options are:\n\nVendor must accept the system without the drive;\n\nVA's initial medical device purchase includes a spare drive which must be installed in\nplace of the original drive at time of turn-in; or\n\nVA must reimburse the company for media at a reasonable open market replacement\ncost at time of purchase.\n\nBio-Medical devices and other equipment or systems containing media (hard drives,\noptical disks, etc.) with VA sensitive information must not be returned to the vendor at the end of lease, for trade-in, or other purposes. The options are:\n\nVendor must accept the system without the drive;\n\nVA's initial medical device purchase includes a spare drive which must be installed in\nplace of the original drive at time of turn-in; or\n\nVA must reimburse the company for media at a reasonable open market replacement\ncost at time of purchase.\n\nDue to the highly specialized and sometimes proprietary hardware and software\nassociated with medical equipment/systems, if it is not possible for the VA to retain the hard drive, then;\n\nThe equipment vendor must have an existing BAA if the device being traded in has\nsensitive information stored on it and hard drive(s) from the system are being returned\nphysically intact; and\n\nAny fixed hard drive on the device must be non-destructively sanitized to the greatest\nextent possible without negatively impacting system operation. Selective clearing down to patient data folder level is recommended using VA approved and validated overwriting technologies/methods/tools. Applicable media sanitization specifications need to be preapproved and described in the purchase order or contract.\n\nA statement needs to be signed by the Director (System Owner) that states that the\ndrive could not be removed and that (a) and (b) controls above are in place and completed.\nThe ISO needs to maintain the documentation.\n\nSECURITY INCIDENT INVESTIGATION\n\nThe term \"security incident\" means an event that has, or could have, resulted in\nunauthorized access to, loss or damage to VA assets, or sensitive information, or an action that breaches VA security procedures. The contractor/subcontractor shall immediately notify the COTR and simultaneously, the designated ISO and Privacy Officer for the contract of any known or suspected security/privacy incidents, or any unauthorized disclosure of sensitive information, including that contained in system(s) to which the contractor/subcontractor has access.\n\nTo the extent known by the contractor/subcontractor, the contractor/subcontractor's\nnotice to VA shall identify the information involved, the circumstances surrounding the incident (including to whom, how, when, and where the VA information or assets were placed at risk or compromised), and any other information that the ontractor/subcontractor considers relevant.\n\nWith respect to unsecured protected health information, the business associate is\ndeemed to have discovered a data breach when the business associate knew or should have known of a breach of such information. Upon discovery, the business associate must notify the covered entity of the breach. Notifications need to be made in accordance with the executed business associate agreement.\n\nIn instances of theft or break-in or other criminal activity, the contractor/subcontractor\nmust concurrently report the incident to the appropriate law enforcement entity (or entities) of jurisdiction, including the VA OIG and 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.\n\n\nCONTRACTOR RULES OF BEHAVIOR\n\nThis User Agreement contains rights and authorizations regarding my access to and use\nof any information assets or resources associated with my performance of services under\nthe contract terms with the Department of Veterans Affairs (VA). This User Agreement\ncovers my access to all VA data whether electronic or hard copy (\"Data\"), VA information\nsystems and resources (\"Systems\"), and VA sites (\"Sites\"). This User Agreement\nincorporates Rules of Behavior for using VA, and other information systems and\nresources under the contract.\n\nGENERAL TERMS AND CONDITIONS FOR ALL ACTIONS AND ACTIVITIES UNDER\nTHE CONTRACT:\n\nunderstand and agree that I have no reasonable expectation of privacy in\naccessing or using any VA, or other Federal Government information systems.\n\nI consent to reviews and actions by the Office of Information & Technology (Ol&T)\nstaff designated and authorized by the VA Chief Information Officer (CIO) and to the VA\nOIG regarding my access to and use of any information assets or resources associated\nwith my performance of services under the contract terms with the VA. These actions\nmay include monitoring, recording, copying, inspecting, restricting access, blocking,\ntracking, and disclosing to all authorized Ol&T, VA, and law enforcement personnel as\ndirected by the VACIO without my prior consent or notification.\n\nI consent to reviews and actions by authorized VA systems administrators and\nInformation Security Officers solely for protection of the VA infrastructure, including, but not limited to monitoring, recording, auditing, inspecting, investigating, restricting access, blocking, tracking, disclosing to authorized personnel, or any other authorized actions by all authorized Ol&T, VA, and law enforcement personnel.\n\nI understand and accept that unauthorized attempts or acts to access, upload,\nchange, or delete information on Federal Government systems; modify Federal\ngovernment systems; deny access to Federal government systems; accrue resources for\nunauthorized use on Federal government systems; or otherwise misuse Federal\ngovernment systems or resources are prohibited.\n\nI understand that such unauthorized attempts or acts are subject to action that may\nresult in criminal, civil, or administrative penalties. This includes penalties for violations\nof Federal laws including, but not limited to, 18 U.S.C. §1030 (fraud and related activity in connection with computers) and 18 U.S.C. §2701 (unlawful access to stored\ncommunications).\n\nRECORDS MANAGEMENT OBLIGATIONS\n\nApplicability\n\nThis clause applies to all Contractors whose employees create, work with, or otherwise handle\nFederal records, as defined in Section B, regardless of the medium in which the record exists.\n\nDefinitions\n\n\"Federal record\" as defined in 44 U.S.C. § 3301, includes all recorded information, regardless\nof form or characteristics, made or received by a Federal agency under Federal law or in\nconnection with the transaction of public business and preserved or appropriate for\npreservation by that agency or its legitimate successor as evidence of the organization,\nfunctions, policies, decisions, procedures, operations, or other activities of the United States\nGovernment or because of the informational value of data in them.\n\nThe term Federal record:\n\nincludes VASTLHCS records.\n\ndoes not include personal materials.\n\napplies to records created, received, or maintained by Contractors pursuant to their [Agency] contract.\n\nmay include deliverables and documentation associated with deliverables.\n\nRequirements\n\nContractor 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 XI I 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.\n\nIn 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.\n\nIn accordance with 36 CFR 1222.32, Contractor shall maintain all records created for\nGovernment 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.\n\nVHA 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 [Agency] 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\nremoval, defacing, alteration, or destruction of records, Contractor must report to VHA. The agency must report promptly to NARA in accordance with 36 CFR 1230.\ns. 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]. \n\nThe 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 VHA 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).\n\nThe Contractor is required to obtain the Contracting Officer's approval prior to\nengaging in any contractual relationship (sub-contractor) in support of this contract\nrequiring 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 VHA guidance for protecting sensitive, proprietary information, classified, and controlled unclassified information.\n\nThe Contractor shall only use Government IT equipment for purposes specifically tied to or authorized by the contract and in accordance with VHA policy.\n\nThe Contractor shall not create or maintain any records containing any non-public\nVHA information that are not specifically tied to or authorized by the contract.\n\nThe Contractor shall not retain, use, sell, or disseminate copies of any deliverable\nthat contains information covered by the Privacy Act of 197 4 or that which is generally protected from public disclosure by an exemption to the Freedom of Information Act.\n\nThe VHA owns the rights to all data and records produced as part of this contract. All\ndeliverables under the contract are the property of the U.S. Government for which VHA 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.\n\nTraining. All Contractor employees assigned to this contract who create, work with, or otherwise handle records are required to take VHA -provided records management training. The Contractor is responsible for confirming training has been completed according to agency policies, including initial training and any annual or refresher training. [Note: To the extent an agency requires contractors to complete records management training, the agency must provide the training to the contractor.]\n\nd. Flowdown of requirements to subcontractors\n\nThe Contractor shall incorporate the substance of this clause, its terms and requirements including this paragraph, in all subcontracts under this [contract vehicle], and require written subcontractor acknowledgment of same.\n\nViolation by a subcontractor of any provision set forth in this clause will be\nattributed to the Contractor.\n\n"}