Amendment 0001 12/16 - extend propoal due date to 12/23. Please be sure to acknowledge this amendment with your proposal. Remove and Replace Roofing Systems for Building 1A & 12 at the VA Sierra Nevad... Amendment 0001 12/16 - extend propoal due date to 12/23. Please be sure to acknowledge this amendment with your proposal. Remove and Replace Roofing Systems for Building 1A & 12 at the VA Sierra Nevada Health Care System, 975 Kirman Ave, Reno, NV 89502. The NCO 21 MACC will be utilized to execute this construction project. See attachments for solicitation package.
Data sourced from SAM.gov.
View Official Posting »
NCO 21 MACC GROUP 2 TASK ORDER PROPOSAL REQUEST Remove and Replace Roofing Buildings 1A & 12 PLACE OF PERFORMANCE VA Sierra Nevada Health Care System 975 Kirman Ave Reno, NV 89502 NOTICE TO VETERANS I... NCO 21 MACC GROUP 2 TASK ORDER PROPOSAL REQUEST Remove and Replace Roofing Buildings 1A & 12 PLACE OF PERFORMANCE VA Sierra Nevada Health Care System 975 Kirman Ave Reno, NV 89502 NOTICE TO VETERANS INTGRATED SERVICE NETWORK 21 (VISN 21) MULTIPLE AWARD CONSTRUCTION CONTRACT (MACC) HOLDERS Description: THE RESULTING SOLCITATION IS TASK ORDER PROPOSAL REQUEST. Proposals will only be requested and accepted from contractors who were awarded a Veterans Integrated Service Network 21 (VISN 21) Multiple-Award Construction Contract (MACC) from Network Contracting Office 21 (NCO 21). Point of Contact: Samantha Henderson, Contract Specialist, samantha.henderson@va.gov Project Title: Remove and Replace Roofing Buildings 1A & 12. Project specifications and all associated project documents shall be incorporated into the Task Order Bid Request which shall be posted electronically through https://sam.gov Magnitude of Construction: Between $1,000,000.00 and $2,000,000.00 Questions regarding this notice shall be submitted via e-mail to: samantha.henderson@va.gov. Please respond if you re interested in this project no later than September 23, 2022 at 2:00 PM (PST) The following firms are eligible for award of the resulting task order: MACC GROUP 2 Acierto, LLC Hawk Contracting Group 2053 North 2000 West P.O. Box 490 Farr West, UT 84404 Montrose, CO 81402 Bexar Advanced Solutions Group Patriot Construction 47 E. Crestwood Road 4646 Qantas Lane Kaysville, UT 84037 Stockton, CA 95206 Dsquare Construction Saw-Greenland JV 107 W. Sahuaro Street 2625 Production Road Tucson, AZ 85705 Virginia Beach, VA 23454 ESA South, Inc. Sergent Mechanical 1681 Success Drive 1617 Pacific Avenue Cantonment, FL 32533 Oxnard, CA 93033 Ground Level Overaa Joint Venture West Point Contractors 5013 Forni Drive 2915 E. Weiding Road Concord, CA 94520 Tucson, AZ 85706 **Any offers received from contractors not mentioned above will not be accepted. Statement of Work Date: May 20, 2022 Project Number: 654-21-104 Project Name: Remove and Replace Roofing Buildings 1A & 12 GENERAL The project scope comprises of removal and replacement of existing roofing systems for buildings 1A and 12. The Contractor shall furnish all services, materials, testing, equipment, and supervisions as required in connection with this State of Work, Drawings and Specifications. All work will conform to the facility requirements as outlined in the 010000 General Requirements Specification and all federal, state, and local requirements. The work shall include all equipment, labor, materials, testing/certification, demolition, disposal, and new construction as demonstrated in the specifications and drawings. All work is located at the VA Sierra Nevada Health Care System facility located at 975 Kirman Ave., Reno, Nevada 89502. SCOPE Contractor to remove and replace the existing roofs per the provided details and specifications. Contractor shall visit the site prior to the start of construction to verify existing site conditions and identify potential conflicts. Construction should be timed to be performed in late spring and summer. Project shall be constructed in phases. Contractor shall coordinate with VA staff to minimize disruptions to normal operations and prevent interruption of the VAMC s delivery of care to patients at the facility at any time. Contractor to perform lead and asbestos sampling on roofing materials to be demolished to confirm that there is no hazardous materials present. Contractor shall coordinate staging, access, and crane location for both buildings with COR. Existing lighting protection conductors located on the building roof and parapet shall be removed. Contractor to provide filter covers at intakes during demolition of roof system to prevent collection of debris. Remove existing walkway pads. Existing roof drain assembly to remain. Contractor to clean free of debris as necessary and check all drain transitions for all roofs for any signs of leaks and repair if necessary. Replace roof drain assembly cover. Building 1A remove existing sprayed applied polyurethane foam roofing system & associated flashing. Remove existing seismic expansion joint cover. Remove existing equipment not in use. Install new TPO roofing assembly w/ insulation (r-30) per manufacturer installation requirements. Install new roof expansion joint assembly. Install new supports for existing elevated ductwork. Building 12 Remove existing PVC roofing system, associated rigid insulation, and associated flashings down to the primary structural roof deck. Remove existing sheet metal parapet coping Remove pipe and conduit supports as necessary for installation of new roofing system. Remove existing roofing membrane, termination bar, and sealant at precast GFRC coping and at stucco assembly. Remove and dispose of existing CMU blocks. Install new TPO roofing assembly w/ insulation (R-30) per manufacturer installation requirements. Install new supports for existing pipes and conduits. Install new non-slip walkway pads per manufacturer s recommendations. Equipment moving to accommodate tear off and re-setting on new roof. Install high visibility safety demarcation line (nighttime reflective) to establish a 3-foot safety inset line. Install new lightning protection devices and associated cabling at perimeter and reconnect to existing mechanical units. Work is to be performed during normal work hours Monday Friday between the hours of 7:30am and 4pm, excluding Federal holidays. After hours work may be required during work phases that generate high levels of noise/vibrations or produce noxious fumes that cannot be contained to the work area. The proposed work shall be performed to cause minimal disruption to office staff. The contractor, their personnel, and their subcontractors shall be subject to the Federal laws, regulations, standards, and VA Directives and Handbooks regarding information and information system security as delineated in this contract. Work area shall be cleaned prior to leaving the site. Any hazards shall be identified, and risk properly mitigated. ATTACHMENTS Construction Drawings Project Specifications Photos ADMINISTRATIVE Schedule. It is the intent of the Reno VA that the work is to be completed within 120 days from the issuance of the Notice to Proceed. Work will be conducted during normal business hours with the exception of work that will cause disruption to hospital operations. Proposal. The Contractor shall thoroughly review the scope, all attachments, and specifications prior to submitting their proposal. The proposal shall be prepared to reflect all work required to provide a complete system. The contractor s proposal will list the breakdown of all materials and labor and time required to complete the above-mentioned work. Onsite job walk prior to bid is highly recommended. ATTACHMENT 1 Information Security (VA Handbook 6500.6) 1.1. GENERAL 1.1.1. Contractors, 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. 1.2. ACCESS TO VA INFORMATION AND VA INFORMATION SYSTEMS 1.2.1. A 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. 1.2.2. All contractors, subcontractors, and third-party servicers and associates working with VA information are subject to the same investigative 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 must be in accordance with VA Directive and Handbook 0710, Personnel Suitability and Security Program. The Office for Operations, Security, and Preparedness is responsible for these policies and procedures. 1.2.3. Contract personnel who require access to national security programs must have a valid security 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. 1.2.4. Custom software development and outsourced operations must be located in the U.S. 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 contractor/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. 1.2.5. The 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. 1.3. VA INFORMATION CUSTODIAL LANGUAGE 1.3.1. Information made available to the contractor or subcontractor by VA for the performance or administration of this contract or information developed by the contractor/subcontractor in performance or administration of the contract shall be used only for those purposes and shall not be used in any other way without the prior written agreement of the VA. This clause expressly limits the contractor/subcontractor's rights to use data as described in Rights in Data - General, FAR 52.227-14(d) (1). 1.3.2. VA information should not be co-mingled, if possible, with any other data on the contractors/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. 1.3.3. Prior to termination or completion of this contract, contractor/subcontractor must not destroy 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. 1.3.4. The contractor/subcontractor must receive, gather, store, back up, maintain, use, disclose 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. 1.3.5. The contractor/subcontractor shall not make copies of VA information except as authorized 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. 1.3.6. If VA determines that the contractor has violated any of the information confidentiality, privacy, 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. 1.3.7. If a VHA contract is terminated for cause, the associated BAA must also be terminated and appropriate actions taken in accordance with VHA Handbook 1600.01, Business Associate Agreements. Absent an agreement to use or disclose protected health information, there is no business associate relationship. 1.3.8. The 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. 1.3.9. The contractor/subcontractor s firewall and Web services security controls, if applicable, shall meet or exceed VA s minimum requirements. VA Configuration Guidelines are available upon request. 1.3.10. Except for uses and disclosures of VA information authorized by this contract for performance 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. 1.3.11. Notwithstanding the provision above, the contractor/subcontractor 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 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. 1.3.12. For service that involves the storage, generating, transmitting, or exchanging of VA sensitive information but does not require C&A or an MOU-ISA for system interconnection, the contractor/subcontractor must complete a Contractor Security Control Assessment (CSCA) on a yearly basis and provide it to the COTR. 1.4. INFORMATION SYSTEM DESIGN AND DEVELOPMENT 1.4.1. Information systems that are designed or developed for or on behalf of VA at nonVA facilities shall comply with all VA directives developed in accordance with FISMA, HIPAA, NIST, and related VA security and privacy control requirements for Federal information systems. This includes standards for the protection of electronic PHI, outlined in 45 C.F.R. Part 164, Subpart C, information and system security categorization level designations in accordance with FIPS 199 and FIPS 200 with implementation of all baseline security controls commensurate with the FIPS 199 system security categorization (reference Appendix D of VA Handbook 6500, VA Information Security Program). During the development cycle a Privacy Impact Assessment (PIA) must be completed, provided to the COTR, and approved by the VA Privacy Service in accordance with Directive 6507, VA Privacy Impact Assessment. 1.4.2. The contractor/subcontractor shall certify to the COTR that applications are fully functional and operate correctly as intended on systems using the VA Federal Desktop Core configuration (FDCC), and the common security configuration guidelines provided by NIST or the VA. This includes Internet Explorer 7 configured to operate on Windows XP and Vista (in Protected Mode on Vista) and future versions, as required. 1.4.3. The standard installation, operation, maintenance, updating, and patching of software shall not alter the configuration settings from the VA approved and FDCC configuration. Information technology staff must also use the Windows Installer Service for installation to the default program files directory and silently install and uninstall. 1.4.4. Applications designed for normal end users shall run in the standard user context without elevated system administration privileges. 1.4.5. The security controls must be designed, developed, approved by VA, and implemented in accordance with the provisions of VA security system development life cycle as outlined in NIST Special Publication 800-37, Guide for Applying the Risk Management Framework to Federal Information Systems, VA Handbook 6500, Information Security Program and VA Handbook 6500.5, Incorporating Security and Privacy in System Development Lifecycle. 1.4.6. The contractor/subcontractor is required to design, develop, or operate a System of Records Notice (SOR) on individuals to accomplish an agency function subject to the Privacy Act of 1974, (as amended), Public Law 93-579, December 31, 1974 (5 U.S.C. 552a) and applicable agency regulations. Violation of the Privacy Act may involve the imposition of criminal and civil penalties. 1.4.7. The contractor/subcontractor agrees to: 1.4.7.1.Comply with the Privacy Act of 1974 (the Act) and the agency rules and regulations issued under the Act in the design, development, or operation of any system of records on individuals to accomplish an agency function when the contract specifically identifies: 1.4.7.1.1. The Systems of Records (SOR); and 1.4.7.1.2. The design, development, or operation work that the contractor/subcontractor is to perform; 1.4.7.2.Include the Privacy Act notification contained in this contract in every solicitation and resulting subcontract and in every subcontract awarded without a solicitation, when the work statement in the proposed subcontract requires the redesign, development, or operation of a SOR on individuals that is subject to the Privacy Act; and 1.4.7.3.Include this Privacy Act clause, including this subparagraph (3), in all subcontracts awarded under this contract which requires the design, development, or operation of such a SOR. 1.4.8. In the event of violations of the Act, a civil action may be brought against the agency involved when the violation concerns the design, development, or operation of a SOR on individuals to accomplish an agency function, and criminal penalties may be imposed upon the officers or employees of the agency when the violation concerns the operation of a SOR on individuals to accomplish an agency function. For purposes of the Act, when the contract is for the operation of a SOR on individuals to accomplish an agency function, the contractor/subcontractor is considered to be an employee of the agency. 1.4.8.1. Operation of a System of Records means performance of any of the activities associated with maintaining the SOR, including the collection, use, maintenance, and dissemination of records. 1.4.8.2. Record means any item, collection, or grouping of information about an individual that is maintained by an agency, including, but not limited to, education, financial transactions, medical history, and criminal or employment history and contains the person s name, or identifying number, symbol, or any other identifying particular assigned to the individual, such as a fingerprint or voiceprint, or a photograph. 1.4.8.3. System of Records means a group of any records under the control of any agency from which information is retrieved by the name of the individual or by some identifying number, symbol, or other identifying particular assigned to the individual. 1.4.9. The vendor shall ensure the security of all procured or developed systems and technologies, 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. 1.4.10. The vendor shall notify VA within 24 hours of the discovery or disclosure of successful exploits 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 10 days. 1.4.11. When the Security Fixes involve installing third party patches (such as Microsoft OS patches or Adobe Acrobat), the vendor will provide written notice to the VA that the patch as 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. l. All other vulnerabilities shall be remediated as specified in this paragraph in a timely manner based on risk, but within 60 days of discovery or disclosure. Exceptions to this paragraph (e.g. for the convenience of VA) shall only be granted with approval of the contracting officer and the VA Assistant Secretary for Office of Information and Technology. 1.5. INFORMATION SYSTEM HOSTING, OPERATION, MAINTENANCE, OR USE 1.5.1. For information systems that are hosted, operated, maintained, or used on behalf of VA at non-VA facilities, contractors/subcontractors are fully responsible and accountable for insuring compliance with all HIPAA, Privacy Act, FISMA, NIST, FIPS, and VA security and privacy directives and handbooks. This includes conducting compliant risk assessments, routine vulnerability scanning, system patching and change management procedures, and the completion of an acceptable contingency plan for each system. The contractor s security control procedures must be equivalent, to those procedures used to secure VA systems. A Privacy Impact Assessment (PIA) must also be provided to the COTR and approved by VA Privacy Service prior to operational approval. All external Internet connections to VA s network involving VA information must be reviewed and approved by VA prior to implementation. 1.5.2. Adequate security controls for collecting, processing, transmitting, and storing of Personally Identifiable Information (PII), as determined by the VA Privacy Service, must be in place, tested, and approved by VA prior to hosting, operation, maintenance, or use of the information system, or systems by or on behalf of VA. These security controls are to be assessed and stated within the PIA and if these controls are determined not to be in place, or inadequate, a Plan of Action and Milestones (POA&M) must be submitted and approved prior to the collection of PII. 1.5.3. Outsourcing (contractor facility, contractor equipment or contractor staff) of systems or network operations, telecommunications services, or other managed services requires certification and accreditation (authorization) (C&A) of the contractor s systems in accordance with VA Handbook 6500.3, Certification and Accreditation and/or the VA OCS Certification Program Office. Governmentowned (government facility or government equipment) contractor-operated systems, third party or business partner networks require memorandums of understanding and interconnection agreements (MOU-ISA) which detail what data types are shared, who has access, and the appropriate level of security controls for all systems connected to VA networks. 1.5.4. The contractor/subcontractor s system must adhere to all FISMA, FIPS, and NIST standards related to the annual FISMA security controls assessment and review and update the PIA. Any deficiencies noted during this assessment must be provided to the VA contracting officer and the ISO for entry into VA s POA&M management process. The contractor/subcontractor must use VA s POA&M process to document planned remedial actions to address any deficiencies in information security policies, procedures, and practices, and the completion of those activities. Security deficiencies must be corrected within the timeframes approved by the government. Contractor/subcontractor procedures are subject to periodic, unannounced assessments by VA officials, including the VA Office of Inspector General. The physical security aspects associated with contractor/subcontractor activities must also be subject to such assessments. If major changes to the system occur that may affect the privacy or security of the data or the system, the C&A of the system may need to be reviewed, retested and re-authorized per VA Handbook 6500.3. This may require reviewing and updating all of the documentation (PIA, System Security Plan, Contingency Plan). The Certification Program Office can provide guidance on whether a new C&A would be necessary. 1.5.5. The contractor/subcontractor must conduct an annual self-assessment on all systems and outsourced services as required. Both hard copy and electronic copies of the assessment must be provided to the COTR. The government reserves the right to conduct such an assessment using government personnel or another contractor/subcontractor. The contractor/subcontractor must take appropriate and timely action (this can be specified in the contract) to correct or mitigate any weaknesses discovered during such testing, generally at no additional cost. 1.5.6. VA prohibits the installation and use of personally-owned or contractor/subcontract or owned equipment or software on VA s network. If nonVA owned equipment must be used to fulfill the requirements of a contract, it must be stated in the service agreement, SOW or contract. All of the security controls required for government furnished equipment (GFE) must be utilized in approved other equipment (OE) and must be funded by the owner of the equipment. All remote systems must be equipped with, and use, a VA-approved antivirus (AV) software and a personal (host-based or enclave based) firewall that is configured with a VA approved configuration. Software must be kept current, including all critical updates and patches. Owners of approved OE are responsible for providing and maintaining the anti-viral software and the firewall on the non-VA owned OE. 1.5.7. All electronic storage media used on non-VA leased or non-VA owned IT equipment that is used to store, process, or access VA information must be handled in adherence with VA Handbook 6500.1, Electronic Media Sanitization upon: (i) completion or termination of the contract or (ii) disposal or return of the IT equipment by the contractor/subcontractor or any person acting on behalf of the contractor/subcontractor, whichever is earlier. Media (hard drives, optical disks, CDs, back-up tapes, etc.) used by the contractors/subcontractors that contain VA information must be returned to the VA for sanitization or destruction or the contractor/subcontractor must self-certify that the media has been disposed of per 6500.1 requirements. This must be completed within 30 days of termination of the contract. 1.5.8. Bio-Medical devices and other equipment or systems containing media (hard drives, optical 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: 1.5.8.1.Vendor must accept the system without the drive; 1.5.8.2.VA s initial medical device purchase includes a spare drive which must be installed in place of the original drive at time of turn-in; or 1.5.8.3.VA must reimburse the company for media at a reasonable open market replacement cost at time of purchase. 1.5.8.4.Due to the highly specialized and sometimes proprietary hardware and software associated with medical equipment/systems, if it is not possible for the VA to retain the hard drive, then; 1.5.8.4.1. The equipment vendor must have an existing BAA if the device being traded in has sensitive information stored on it and hard drive(s) from the system are being returned physically intact; and 1.5.8.4.2. Any fixed hard drive on the device must be non-destructively sanitized to the greatest extent 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. 1.5.8.4.3. A statement needs to be signed by the Director (System Owner) that states that the drive could not be removed and that (a) and (b) controls above are in place and completed. The ISO needs to maintain the documentation. 1.6. SECURITY INCIDENT INVESTIGATION 1.6.1. The term security incident means an event that has, or could have, resulted in unauthorized access to, loss or damage to VA assets, or sensitive information, or an action that breaches VA security procedures. 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. 1.6.2. To 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. 1.6.3. With 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. 1.6.4. 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 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 inj...
Data sourced from SAM.gov.
View Official Posting »