P09 Lebanon_VAMC_Security_Maintenance_SOW_updated.docx

DOCX document 43 KB Posted

Attached to
J063--Security Access Control and Video Surveillance Systems Maintenance.
Solicitation number
36C24427Q0047
Issued by

About this file

This is a Statement of Work (SOW) for comprehensive preventive maintenance, software and firmware support, technical support, cybersecurity compliance, corrective maintenance, and hardware repair services for security, access control, video surveillance, intrusion detection, and associated management systems at Lebanon VA Medical Center and its satellite facilities (CBOCs in Berks, York, Cumberland, and Lancaster counties, TR House, and Fort Indiantown Gap Cemetery). The contractor shall perform quarterly preventive maintenance or at manufacturer-recommended intervals, including system performance testing, camera cleaning and alignment, card reader and lock verification, storage system testing, and environmental checks of racks and UPS units. Corrective maintenance requires response within defined timeframes with diagnosis, replacement of defective components using OEM-authorized parts, onsite repairs, and loaner equipment for critical components when necessary.

The contractor is responsible for applying vendor-approved security patches and firmware updates with VA approval, backing up and verifying databases and configurations, hardening configurations per VA cybersecurity requirements, and providing 24/7 remote diagnostics and troubleshooting. Contractor personnel must comply with VA background checks, credentialing, cybersecurity and privacy training, and facility access protocols. The equipment scope includes 1 main access control server (Genetec), 1 main VMS server, 13 VMS servers with archivers, badging and video management workstations, 313 door controller/reader modules, 402 card readers, access control hardware (electric strikes, mag locks, mortice locksets, Salto systems), 484 IP cameras (267 indoor non-moving, 178 outdoor non-moving, 39 outdoor PTZ), 12 NVR archivers, 58 network switches with POE capability, 81 fiber conversion modules, and associated infrastructure including UPS units and wireless antennas.

View the file

Other files

File Type Posted
36C24427Q0047.docx DOCX document

On GovTribe

Work with this file

  • Download the original file
  • Contacts named in this file
  • Similar government files
  • Ask GovTribe AI about this file

Text version

Statement of Work (SOW) Security, Access Control, and Video Surveillance Systems Maintenance Services Lebanon VA Medical Center, CBOCs (Berks, York, Cumberland, Lancaster), Lebanon TR House & Fort Indiantown Gap Cemetery

1.0 Purpose

The Contractor shall provide comprehensive preventive maintenance, software and firmware support, technical support, cybersecurity compliance, corrective maintenance, and hardware repair services for security, access control, video surveillance, intrusion detection, and associated management systems installed across the Lebanon VA Medical Center, the listed outpatient clinics as well as the TR House and Fort Indiantown Gap Cemetery. The contractor shall ensure system reliability, operational integrity, cybersecurity, and functional performance through scheduled maintenance, ongoing software support, remote assistance, and replacement of failed hardware components as required.

2.0 Scope of Work

The Contractor shall service, maintain, repair, replace (if unrepairable), back-up, and update all security system components listed in Section 6.0 across all designated VA facilities, including associated software, servers, databases, storage, network switches, controllers, cameras, peripheral devices, and access control devices.

3.0 Contractor Responsibilities

3.1 Preventive Maintenance (PM)

Quarterly PM or manufacturer-recommended intervals.

System performance testing and functional verification across devices.

Cleaning and alignment of cameras and inspection of housings.

Verification of card readers, door strikes, magnetic locks, mortice locksets, and REX devices.

Testing of storage systems, retention configurations, and system integrity.

Environmental checks of racks, UPS units, and network cabinets.

Documentation of all PM work and identified deficiencies.

3.2 Restorative Maintenance

Respond to service calls within the response times defined in Section 6.0.

Diagnose equipment and system failures and replace defective components using OEM-authorized parts.

Provide loaner equipment for critical components when necessary.

Perform onsite repairs, validate post-repair functionality, and document all corrective actions.

3.3 Software & Firmware Support

Apply vendor-approved security patches, hotfixes, and firmware updates with VA approval.

Back up and verify VMS and Access Control databases and configurations.

Configuration hardening per VA cybersecurity requirements.

Maintain update logs and version control for all changes.

3.4 Technical Support & Remote Assistance

Provide 24/7 remote diagnostics and troubleshooting.

Conduct remote health checks on servers, NVRs, and access control panels.

Support user queries and configuration adjustments with Government approval.

Assist VA Police and Security personnel with system operations as needed.

3.5 Lifecycle & Improvement Recommendations

Annual system lifecycle analysis and end-of-life risk reports.

Upgrade and modernization recommendations.

Network load and storage retention assessments and capacity planning.

4.0 Personnel Requirements

Contractor personnel shall comply with VA background checks and credentialing.

Personnel must carry VA badges and comply with facility access protocols.

All employees must complete VA cybersecurity and privacy training.

5.0 Equipment List

Servers, Workstations, and Core Systems Main Server – Access Control (Genetec): 1 Main Server – VMS (Video Management System): 1 Main Server – VMS including Archivers: 13 Workstation – Badging: 2 Workstation – VMA (Video Management Archiver): 7 Main Workstation – Access Control – Genetec: 1 Salto Server: 2 Sipass Workstations (Standalone): 2 Access Control Hardware Door Controller/Reader Interface Modules: 313 Card Readers (Non-Biometric): 402 Electric Strikes: 194 Mag Locks: 60 Mortice Locksets: 93 Salto Control Units – Online: 9 Salto Wireless Escutcheons: 147 Salto Wireless Locker Locks: 32 Salto Readers: 9 Salto Portable Programmer: 2 Salto Mifare Card Encoder: 2 Door Prop Alarms: 7 Video Surveillance Hardware IP Cameras (Non-Moving) Indoor: 267 IP Cameras (Non-Moving) Outdoor: 178 IP Cameras (PTZ) Outdoor: 39 Photo ID Video Camera: 1 Color Monitors: 23 Video Recording & Network Infrastructure Network Video Recorder (NVR) Archivers: 12 Network Switches – POE (incl. core switch): 58 Network Switches – Non-POE: 6 POE Injectors: 59 Fiber Conversion Modules: 81 Fiber Termination Boxes: 45 Wireless Network Antennas: 8 UPS – Large >1000VA: 6 UPS – Small <1000VA: 21 Intrusion Detection Intrusion Control Panels: 19 Intrusion Keypads: 39 Motion Detectors: 60

PIR-REX: 354

Personnel Door Contacts: 460 Overhead Door Contacts – Armored: 12 Intercom & Communication Intercom IP Masters: 2 Intercom Non-IP Masters: 5 IP Door Stations: 4 Control Boards & Interface Units Input Boards: 7 Output Boards: 6 Synergis Control Links: 10 Special Systems — Siemens Sipass (Pharmacy & Day Care) Sipass Control Panel: 2 Sipass Eight-Reader Interface: 2 Sipass Two-Reader Interface: 2 Sipass System (General): 1 Miscellaneous Button, Hold-Up: 44 Exit Buttons: 50 Card Printer: 1 Power Supply – Access Control: 49 Power Supply – Video: 6 Network Maintenance (annual task): 1 Quality Assurance Meetings (annual): 1 Customer-Directed Support (as needed): 1 Firmware Update Tasking: 1

6.0 Service Levels & Response Times

Corrective Maintenance Response Times:

Emergency (system down/security risk): Onsite within 4 hours.

High Priority (major subsystem impairment/non security risk): Onsite within 24 hours.

Routine (non-critical issue): Onsite within 72 hours.

Remote assistance: Response within 1 hour of notification.

7.1 Hours of Operation & Scheduling

7.1.1 Standard Service Window. The Contractor shall perform routine preventive and corrective maintenance during the Government’s standard business hours **7:00 a.m.–3:30 p.m., Monday–Friday**, unless otherwise authorized by the TPOC.

7.1.2 After‑Hours / On‑Call Support. Outside the standard window, the Contractor shall provide after‑hours support for Emergency and High Priority incidents in accordance with Section 7.0 SLAs and the on‑call/dispatch procedures approved by the TPOC.

7.1.3 Federal Holidays. No routine maintenance shall be scheduled on Federal holidays unless specifically approved by the TPOC. The VA observes: New Year’s Day; Birthday of Martin Luther King, Jr.; President’s Day; Memorial Day; Juneteenth; Independence Day; Labor Day; Columbus Day; Veterans Day; Thanksgiving Day; Christmas Day; and any day declared a national holiday.

7.1.4 Site‑Access Windows. The Contractor shall coordinate site access windows per facility security/escort requirements and provide 48 hours’ notice for planned work that may impact operations (e.g., controller reboots, firmware updates).

7.1.5 Scheduling Changes. The TPOC may modify service windows or authorize weekend/evening work as mission needs dictate. The Contractor shall accommodate such changes and propose staffing to meet Section 7.0 SLAs.

7.1.6 Remote Diagnostics. Remote monitoring/diagnostics may be performed 24/7 as permitted by Section 3.4 (Technical Support & Remote Assistance) and VA cybersecurity rules.

7.2 Locations of Performance

Lebanon VA Medical Center 1700 S. Lincoln Ace Lebanon, PA. 17042

Berks County VA Clinic 2762 Century Boulevard Wyomissing, PA 19601

Lancaster County VA Clinic 212 Willow Valley Lakes Drive Suite 208 Willow Street, PA 17584

York County VA Clinic 2251 Eastern Blvd York, PA 17402

Cumberland County VA Clinic 5070 Ritter Road Mechanicsburg, PA 17055

Lebanon TR House 199 Walnut Street Lebanon, PA 17042

Fort Indiantown Gap Cemetery 60 Indiantown Gap Rd Annville, PA 17003

7.3 Deliverables

Preventive Maintenance Reports (per visit).

Corrective Maintenance Reports (per incident).

Firmware and Software Update Logs.

Cybersecurity Patch/Compliance Statements.

Annual System Health Assessment Report.

Lifecycle and Upgrade Recommendation Report.

Inventory Reconciliation (if requested).

Monthly/Quarterly Trouble Ticket Summaries.

8.0 Security & Compliance Requirements

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 TPOC/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 Technical Point of Contact (TPOC) 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 TPOC/CO with the tracking information. Self-certification by the contractor that the data destruction requirements above have been met shall be sent to the TPOC/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 TPOC/CO in writing prior to access being granted.

e. The contractor shall notify the TPOC/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 TPOC/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 TPOC/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 TPOC/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 TPOC/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.

Records Management Language When Federal agencies acquire goods or services, they need to determine what Federal records management requirements should be included in the contract. Federal contractors often create, send, or receive Federal records. Federal contracts should provide clear legal obligations describing how the contract employees must handle Federal records.

Agency records officers, procurement counsel, and acquisitions officers must discuss how to integrate records management obligations into their existing procurement processes. NARA has developed the following language to be included as an agency-specific term and condition in Federal contracts for a variety of services and products. The majority of contracts should include language on records management obligations, but each contract should be evaluated individually. For example, the data-rights paragraph (Paragraph 10 below) may not be appropriate for all contracts. Instead, agencies may be better served by one of the established data-rights clauses in the Federal Acquisition Regulations.

This language should not replace specific records management requirements included within Federal information system contracts.

RECORDS MANAGEMENT OBLIGATIONS

A. Applicability This clause applies to all Contractors whose employees create, work with, or otherwise handle Federal records, as defined in Section B, regardless of the medium in which the record exists.

B. Definitions “Federal record” as defined in 44 U.S.C. § 3301, includes all recorded information, regardless of form or characteristics, made or received by a Federal agency under Federal law or in connection with the transaction of public business and preserved or appropriate for preservation by that agency or its legitimate successor as evidence of the organization, functions, policies, decisions, procedures, operations, or other activities of the United States Government or because of the informational value of data in them.

The term Federal record:

1. includes [Agency] records.

2. does not include personal materials.

3. applies to records created, received, or maintained by Contractors pursuant to their [Agency] contract.

4. may include deliverables and documentation associated with deliverables.

C. Requirements

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. [Agency] 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 removal, defacing, alteration, or destruction of records, Contractor must report to [Agency]. 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 [Agency] 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 [Agency] 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 [Agency] policy.

8. The Contractor shall not create or maintain any records containing any non-public [Agency] 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 [Agency] 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 [Agency] 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.

11. Training. All Contractor employees assigned to this contract who create, work with, or otherwise handle records are required to take [Agency]-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.

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