36C26124Q0346.docx

36C26124Q0346

PAGE 1 OF

1. REQUISITION NO.

2. CONTRACT NO.

3. AWARD/EFFECTIVE DATE

4. ORDER NO.

5. SOLICITATION NUMBER

6. SOLICITATION ISSUE DATE

a. NAME

b. TELEPHONE NO. (No Collect Calls)

8. OFFER DUE

DATE/LOCAL

TIME

9. ISSUED BY

CODE

10. THIS ACQUISITION IS

UNRESTRICTED OR

SET ASIDE:

% FOR:

SMALL BUSINESS

HUBZONE SMALL

BUSINESS

SERVICE-DISABLED

VETERAN-OWNED

SMALL BUSINESS

WOMEN-OWNED SMALL BUSINESS

(WOSB) ELIGIBLE UNDER THE WOMEN-OWNED

SMALL BUSINESS PROGRAM

EDWOSB

8(A)

NAICS:

SIZE STANDARD:

11. DELIVERY FOR FOB DESTINA-

TION UNLESS BLOCK IS

MARKED

SEE SCHEDULE

12. DISCOUNT TERMS

13a. THIS CONTRACT IS A

RATED ORDER UNDER

DPAS (15 CFR 700)

13b. RATING

14. METHOD OF SOLICITATION

RFQ

IFB

RFP

15. DELIVER TO

CODE

16. ADMINISTERED BY

CODE

17a. CONTRACTOR/OFFEROR

CODE

FACILITY CODE

18a.

PAYMENT WILL BE MADE BY

CODE

TELEPHONE NO.

UEI:

EFT:

PHONE:

FAX:

17b. CHECK IF REMITTANCE IS DIFFERENT AND PUT SUCH ADDRESS IN OFFER 18b. SUBMIT INVOICES TO ADDRESS SHOWN IN BLOCK 18a UNLESS BLOCK BELOW IS CHECKED

SEE

ADDENDUM

19.

20.

21.

22.

23.

24.

ITEM NO.

SCHEDULE OF SUPPLIES/SERVICES

QUANTITY

UNIT

UNIT PRICE

AMOUNT

(Use Reverse and/or Attach Additional Sheets as Necessary)

25. ACCOUNTING AND APPROPRIATION DATA

26.

TOTAL AWARD AMOUNT (For Govt. Use Only) 27a. SOLICITATION INCORPORATES BY REFERENCE FAR 52.212-1, 52.212-4. FAR 52.212-3 AND 52.212-5 ARE ATTACHED. ADDENDA

ARE

ARE NOT ATTACHED.

27b. CONTRACT/PURCHASE ORDER INCORPORATES BY REFERENCE FAR 52.212

-4. FAR 52.212-5 IS ATTACHED. ADDENDA

ARE

ARE NOT ATTACHED

28. CONTRACTOR IS REQUIRED TO SIGN THIS DOCUMENT AND RETURN _______________

29. AWARD OF CONTRACT: REF. ___________________________________ OFFER

COPIES TO ISSUING OFFICE. CONTRACTOR AGREES TO FURNISH AND

DATED ________________________________. YOUR OFFER ON SOLICITATION

DELIVER ALL ITEMS SET FORTH OR OTHERWISE IDENTIFIED ABOVE AND ON ANY

(BLOCK 5), INCLUDING ANY ADDITIONS OR CHANGES WHICH ARE

ADDITIONAL SHEETS SUBJECT TO THE TERMS AND CONDITIONS SPECIFIED

SET FORTH HEREIN IS ACCEPTED AS TO ITEMS:

30a. SIGNAT

URE OF OFFEROR/CONTRACTOR

31a. UNITED STATES OF AMERICA (SIGNATURE OF CONTRACTING OFFICER) 30b. NAME AND TITLE OF SIGNER (TYPE OR PRINT) 30c. DATE SIGNED 31b. NAME OF CONTRACTING OFFICER (TYPE OR PRINT) 31c. DATE SIGNED

AUTHORIZED FOR LOCAL REPRODUCTION

(REV. NOV 2021)

PREVIOUS EDITION IS NOT USABLE

Prescribed by GSA - FAR (48 CFR) 53.212

7. FOR SOLICITATION

INFORMATION CALL:

STANDARD FORM 1449

SOLICITATION/CONTRACT/ORDER FOR COMMERCIAL

PRODUCTS AND COMMERCIAL SERVICES

OFFEROR TO COMPLETE BLOCKS 12, 17, 23, 24, & 30

36C261-24-AP-1215

612-24-1-145-0034 36C26124Q0346 02-05-2024 Dennis Salmonsen 916-923-4508 02-08-2024 17:00

PST

612MCP

Department of Veterans Affairs VA Sierra Pacific Network (VISN 21) Network Contracting Office (NCO) 21 3237 Peacekeeper Way, Bldg 200 Suite 204 McClellan Park CA 95652 X X 513210 $47 Million N/A X

** SEE DELIVERY LOCATION **

612MCP

Department of Veterans Affairs VA Sierra Pacific Network (VISN 21) Network Contracting Office (NCO) 21 3237 Peacekeeper Way, Bldg 200 Suite 204 McClellan CA 95652

Department of Veterans Affairs FMS VA-9(101) Financial Services Center PO Box 149971 Austin TX 78714-9971 See CONTINUATION Page BioDose/NMIS software, Technical Support, and Software Updates.

Quotes shall be submitted to Dennis Salmonsen at dennis.salmonsen@va.gov by: See Block 8

NOTE

1: Offers shall follow the submission instructions specified in FAR Provisions 52.212-1 and 52.212-2, and their addendums included in this solicitation. Failure to follow the instructs will result in an unfavorable evaluation.

Note 2:

Offer must complete page 1 of the SF-1449 by completing sections 30a, 30b and 30c below.

See CONTINUATION Page X Dennis Salmonsen Contracting Officer Table of Contents

SECTION B - CONTINUATION OF SF 1449 BLOCKS

B.1 CONTRACT ADMINISTRATION DATA

1. Contract Administration: All contract administration matters will be handled by the following individuals:

a. CONTRACTOR:

b. GOVERNMENT: Contracting Officer 36C261 Dennis Salmonsen Department of Veterans Affairs VA Sierra Pacific Network (VISN 21) Network Contracting Office (NCO) 21 3237 Peacekeeper Way, Bldg 200 Suite 204 McClellan Park CA 95652

2. CONTRACTOR REMITTANCE ADDRESS: All payments by the Government to the contractor will be made in accordance with:

3. INVOICES: Invoices shall be submitted in arrears:

4. GOVERNMENT INVOICE ADDRESS: All Invoices from the contractor shall be submitted electronically in accordance with VAAR Clause 852.232-72 Electronic Submission of Payment Requests.

ACKNOWLEDGMENT OF AMENDMENTS: The offeror acknowledges receipt of amendments to the Solicitation numbered and dated as follows:

GOVERNMENT INVOICE ADDRESS: All Invoices from the contractor shall be submitted electronically in accordance with VAAR Clause 852.232-72 Electronic Submission of Payment Requests.

All invoices from the contractor shall be submitted electronically in accordance with VAAR Clause 852.232-72 Electronic Submission of Payment Requests. VA’s Electronic Invoice Presentment and Payment System – The FSC uses a third-party contractor, Tungsten, to transition vendors from paper to electronic invoice submission. Please go to this website:

http://www.tungsten-network.com/US/en/veterans-affairs/ to register and begin submitting electronic invoices, free of charge. The Department of Veterans Affairs Tungsten Number is: AAA544240062 (this allows you to file invoices online for free.)

More information on the VA Financial Services Center is available at: http://www.fsc.va.gov/einvoice.asp.

Vendor e-Invoice Set-Up Information:

If you have questions about the e-invoicing program or Tungsten, please contact the FSC at the phone number or email address listed below:

• Tungsten e-Invoice Setup Information: 1-877-489-6135

• Tungsten e-Invoice email: VA.Registration@Tungsten-Network.com

• FSC e-Invoice Contact Information: 1-877-353-9791

• FSC e-invoice email: vafsccshd@va.gov

B.2 - Statement of Work

A. SCOPE:

The VA Northern California Health Care System (VANCHCS), Mather Hospital, requests a Brand Name Only software BioDose/NMIS developed by EC2 Software Solutions LLC. The software is designed for Nuclear Medicine radiopharmaceutical dose tracking. The authorized vendor must be able to furnish nuclear medicine dose tracking software that allows the nuclear medicine department to keep track of radioactive inventory, radiopharmaceutical doses, patient dose records information, and radiopharmaceutical billing.

B. SALIENT CHARACTERISTICS

Brand Name Item: BioDose/NMIS Software by EC2 Software Solutions

1) Essential/significant physical, functional, or performance characteristics.

Allows nuclear medicine departments to keep track of radioactive inventory, radiopharmaceutical doses, patient dose records information and radiopharmaceutical billing.

2) Complete generic identification – Nuclear Medicine radiopharmaceutical dose tracking software

3) Capabilities The fully integrated Nuclear Medicine dose tracking software shall include:

A. Streamlined Record Keeping

· Patient dose amounts, procedures, referring physicians and radioactive waste disposal.

· Automated daily reporting

· Automated monthly record keeping

B. Simplified Workflow

· Access everything from one main screen

· Have convenient shortcuts for day-to-day tasks

· Ability to quickly view all patient information

· View satellite department data

C. Effortless Compliance

· Produce daily and monthly inspection reports

· Health physics services

· Export reports to Excel

D. Patient Exam Info

· View a patient's scheduled exams and exam history

· View a patient’s dose record from previous exams

E. Inventory Management

· Track shipping containers

· Track records of sealed sources and radioactive waste disposal

· Sort inventory

· Barcoded inventory

6) Software Requirements - Fully integrated Nuclear Medicine dose computer software module that supports all aspects of a nuclear medicine department including but not limited to:

· Patient dose record keeping.

· Radiopharmaceutical inventory.

· Billing

· Quality Assurance (QA) & Quality Management (QM) for all nuclear medicine hot lab equipment.

· Hot waste disposal.

· Daily and weekly survey, and wipes record keeping.

· Technical Reference Model (TRM) approved.

Additional Required Software Features/Capabilities

· Shall provide software maintenance as needed. Software maintenance includes, but is not limited to, periodic updates, enhancements and corrections, and reasonable technical support.

Maintenance also includes support customarily provided by the vendor to any of its customers that makes it such that the software performs according to all specifications, documentation, regulations, and demonstrated claims.

· Shall comply with VA network security regulations according to VA Directives 6500.

· Shall meet dictates of the following standards organizations as relevant:

· HIPPA (Health Insurance Portability Act)

· JCT (The Joint Commission)

· DOT (Department of Transportation)

· NRC (Nuclear Regulatory Commission)

· NHPP (National Health Physics Program)

· Shall have extensive experience in the installation and use of technologies for management and tracking of radiopharmaceuticals.

· Shall provide all licenses necessary to use all software installed on the technologies acquired and required.

· Shall be able to provide evidence of financial solvency.

· Shall be able to provide evidence to support any claims regarding capabilities, reliability, experience, technology, past and existing installations, past and present performance, and knowledge and abilities of personnel.

· Shall provide commitment that their software is willing to continue to be VA Technical Reference Model (TRM) compliant through 2027; specifically, the vendor will provide and patches and updates etc. needed and generated to keep product TRM compliant.

· Shall ensure, when appropriate, that data are encrypted.

C. INSTALLATION

Installation is required by the Contractor. Contractor must contact the Point-of-Contact listed in Section E of the Statement of Work within 10 business days.

· Shall include assistance for installation and configuration of the software.

· Shall include configuration of all necessary aspects of all client users.

D. PERORMANCE – QUALITY

· The vendor shall be available for system assistance during normal working hours, excluding Federal holidays and weekends.

· The vendor shall respond to system assistance calls within two hours from the time the call is placed.

· The system shall be able to be set automatically backup on a nightly basis.

· The vendor shall notify the users of any system upgrades and allow, at minimum, 30 calendar days from the date of the initial notification for scheduling of the software upgrade.

· The vendor shall ensure that before any system maintenance that all data is backed up, and after any maintenance all data is restored properly.

D. PERIOD OF PERFORMANCE:

TBD

E. TYPE OF CONTRACT

This is a Firm-Fixed-Priced, one-time supply contract with four (1) one-year Options. Please see 52.217-9 – Option to Extend the Term of the Contract below.

F. POINT-OF-CONTACT (POC)

This contract is assigned a POC and will provide general instructions for administrating the contract. The POC is not authorized to grant permission(s) to change the scope of the project. The POC that is assigned for this contract will ensure that the supplies/services provided by this company are received based on the contractual terms and conditions.

Phone:

e-mail:

G. DELIVERABLES OR DELIVERY SCHEDULE

The vendor shall deliver the equipment via standard delivery with F.O.B. Destination as scheduled. See Section C for delivery schedule period-of-performance.

The equipment shall be delivered to the following address:

H. VENDORS RESPONSIBILITIES

· Shall provide software maintenance as needed. Software maintenance includes, but is not limited to, periodic updates, enhancements and corrections, and reasonable technical support.

Maintenance also includes support customarily provided by the vendor to any of its customers that makes it such that the software performs according to all specifications, documentation, regulations, and demonstrated claims.

· Shall comply with VA network security regulations according to VA Directives 6500.

· Shall meet dictates of the following standards organizations as relevant:

· HIPPA (Health Insurance Portability Act)

· JCT (The Joint Commission)

· DOT (Department of Transportation)

· NRC (Nuclear Regulatory Commission)

· NHPP (National Health Physics Program)

· Shall have extensive experience in the installation and use of technologies for management and tracking of radiopharmaceuticals.

· Shall provide all licenses necessary to use all software installed on the technologies acquired and required.

· Shall be able to provide evidence of financial solvency.

· Shall be able to provide evidence to support any claims regarding capabilities, reliability, experience, technology, past and existing installations, past and present performance, and knowledge and abilities of personnel.

· Shall provide commitment that their software is willing to continue to be VA Technical Reference Model (TRM) compliant through 2027; specifically, the vendor will provide and patches and updates etc. needed and generated to keep product TRM compliant.

· Shall ensure, when appropriate, that data are encrypted.

I. CHANGES TO CONTRACT

Before performing any action in a non-contractual nature or is considered out-of-scope, the Contractor shall contact the Point of Contact (POC) and the Contract Officer identifying the reason(s) for change. All changes shall have prior authorization from a VA Contract Officer in the form of a written modification.

J. POST-AWARD PERFORMANCE CONVERENCE

The POC, Contract Specialist, or Contract Officer may schedule a post-award performance conference with Contractor, if deemed necessary, for contract orientation purposes.

K. VA INFORMATION AND INFORMATION SYSTEM SECURITY/PRIVACY LANGUAGE

The C&A requirements do not apply and a Security Accreditation Package is not required.

1. GENERAL

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.

2. ACCESS TO VA INFORMATION AND VA INFORMATION SYSTEMS

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

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

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

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

3. VA INFORMATION CUSTODIAL LANGUAGE

a. 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).

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

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

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

4. INFORMATION SYSTEM DESIGN AND DEVELOPMENT

a. Information systems that are designed or developed for or on behalf of VA at non-VA 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.

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

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

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

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

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

g. 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 15 days.

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

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

5. INFORMATION SYSTEM HOSTING, OPERATION, MAINTENANCE, OR USE.

a. 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 ensuring 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.

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

c. 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. Government-owned (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.

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

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

f. VA prohibits the installation and use of personally owned or contractor/subcontractor-owned equipment or software on VA’s network. If non-VA 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.

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

6. SECURITY INCIDENT INVESTIGATION

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

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

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

d. 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 injunctive relief against any third party arising from, or related to, the incident.

7. LIQUIDATED DAMAGES FOR DATA BREACH

a. Consistent 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 SP/ the contractor/subcontractor processes or maintains under this contract. However, it is the policy of VA to forgo collection of liquidated damages in the event the contractor provides payment of actual damages in an amount determined to be adequate by the agency.

b. The 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.

c. Each risk analysis shall address all relevant information concerning the data breach, including the following:

(1) Nature of the event (loss, theft, unauthorized access);

(2) Description of the event, including:

(a) date of occurrence;

(b) data elements involved, including any PII, such as full name, social security number, date of birth, home address, account number, disability code;

(3) Number of individuals affected or potentially affected;

(4) Names of individuals or groups affected or potentially affected;

(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;

(6) Amount of time the data has been out of VA control;

(7) The likelihood that the sensitive personal information will or has been compromised (made accessible to and usable by unauthorized persons); (8) Known misuses of data containing sensitive personal information, if any;

(9) Assessment of the potential harm to the affected individuals;

(10) Data breach analysis as outlined in 6500.2 Handbook, Management of Security and Privacy Incidents, as appropriate; and

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

d. Based 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:

(1) Notification;

(2) One year of credit monitoring services consisting of automatic daily monitoring of at least 3 relevant credit bureau reports;

(3) Data breach analysis;

(4) Fraud resolution services, including writing dispute letters, initiating fraud alerts and credit freezes, to assist affected individuals to bring matters to resolution;

(5) One year of identity theft insurance with $20,000.00 coverage at $0 deductible; and

(6) Necessary legal expenses the subjects may incur to repair falsified or damaged credit records, histories, or financial affairs.

8. TRAINING

a. All 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:

(1) Sign and acknowledge (either manually or electronically) understanding of and responsibilities for compliance with the Contractor Rules of Behavior, Appendix E relating to access to VA information and information systems;

(2) Successfully complete the VA Cyber Security Awareness and Rules of Behavior training and annually complete required security training;

(3) Successfully complete the appropriate VA privacy training and annually complete required privacy training; and

(4) Successfully complete any additional cyber security or privacy training, as required for VA personnel with equivalent information system access [to be defined by the VA program official and provided to the contracting officer for inclusion in the solicitation document – e.g., any role-based information security training required in accordance with NIST Special Publication 800-16, Information Technology Security Training Requirements.]

b. The contractor shall provide to the contracting officer and/or the COTR a copy of the training certificates and certification of signing the Contractor Rules of Behavior for each applicable employee within 1 week of the initiation of the contract and annually thereafter, as required.

c. Failure to complete the mandatory annual training and sign the Rules of Behavior annually, 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.

End of Statement of Work

B.3 PRICE/COST SCHEDULE

ITEM INFORMATION

Nuclear Medicine Information System NMIS Software (3 Node Network Software) USB Barcode Reader & Software.

Ship (1) to Mather Hospital (1) to Martinez Clinic.

Contract Period: Base POP Begin:

POP End:

PRINCIPAL NAICS CODE: 513210 - Software Publishers PRODUCT/SERVICE CODE: 6530 - Hospital Furniture, Equipment, Utensils, and Supplies

MANUFACTURER PART NUMBER (MPN): NMIS

LOCAL STOCK NUMBER: NMIS

RS-232 Cable - (1) Mather Hospital (1) Martinez Clinic.

Contract Period: Base POP Begin:

POP End:

PRINCIPAL NAICS CODE: 513210 - Software Publishers PRODUCT/SERVICE CODE: 6530 - Hospital Furniture, Equipment, Utensils, and Supplies

HL7 Interface software - (1) Mather Hospital (1) Martinez Clinic.

POP Begin:

POP End:

PRINCIPAL NAICS CODE: 513210 - Software Publishers

WEB TRAINING - (1) Mather Hospital (1) Martinez Clinic.

POP Begin:

POP End:

PRINCIPAL NAICS CODE: 513210 - Software Publishers PRODUCT/SERVICE CODE: 6530 - Hospital Furniture, Equipment, Utensils, and Supplies

MANUFACTURER PART NUMBER (MPN): TRNG

LOCAL STOCK NUMBER: TRNG

Installation - (1) Mather Hospital (1) Martinez Clinic.

POP Begin:

POP End:

PRINCIPAL NAICS CODE: 513210 - Software Publishers

MANUFACTURER PART NUMBER (MPN): Instal

Packaging and Handling - (1) Mather Hospital (1) Martinez Clinic.

POP Begin:

POP End:

PRINCIPAL NAICS CODE: 513210 - Software Publishers

MANUFACTURER PART NUMBER (MPN): Packaging and Handling

Technical Support & Updates (Software Agreement after 1 year) - (1) Mather Hospital (1) Martinez Clinic.

Contract Period: Option 1 POP Begin:

POP End:

PRINCIPAL NAICS CODE: 513210 - Software Publishers

MANUFACTURER PART NUMBER (MPN): Support and Updates

Technical Support & Updates (Software Agreement after 1 year) - (1) Mather Hospital (1) Martinez Clinic.

Contract Period: Option 2 POP Begin:

POP End:

PRINCIPAL NAICS CODE: 513210 - Software Publishers

Technical Support & Updates (Software Agreement after 1 year) - (1) Mather Hospital (1) Martinez Clinic.

Contract Period: Option 3 POP Begin:

POP End:

PRINCIPAL NAICS CODE: 513210 - Software Publishers

Technical Support & Updates (Software Agreement after 1 year) - (1) Mather Hospital (1) Martinez Clinic.

Contract Period: Option 4 POP Begin:

POP End:

PRINCIPAL NAICS CODE: 513210 - Software Publishers

B.4 DELIVERY SCHEDULE

Page 1 of Page 1 of

SECTION C - CONTRACT CLAUSES

C.1 52.204-18 COMMERCIAL AND GOVERNMENT ENTITY CODE MAINTENANCE (AUG 2020)

(a) Definition. As used in this clause— Commercial and Government Entity (CAGE) code means—

(1) An identifier assigned to entities located in the United States or its outlying areas by the Defense Logistics Agency (DLA) Commercial and Government Entity (CAGE) Branch to identify a commercial or government entity by unique location; or

(2) An identifier assigned by a member of the North Atlantic Treaty Organization (NATO) or by the NATO Support and Procurement Agency (NSPA) to entities located outside the United States and its outlying areas that the DLA Commercial and Government Entity (CAGE) Branch records and maintains in the CAGE master file. This type of code is known as a NATO CAGE (NCAGE) code.

(b) Contractors shall ensure that the CAGE code is maintained throughout the life of the contract for each location of contract, including subcontract, performance. For contractors registered in the System for Award Management (SAM), the DLA Commercial and Government Entity (CAGE) Branch shall only modify data received from SAM in the CAGE master file if the contractor initiates those changes via update of its SAM registration. Contractors undergoing a novation or change-of-name agreement shall notify the contracting officer in accordance with subpart 42.12. The contractor shall communicate any change to the CAGE code to the contracting officer within 30 days after the change, so that a modification can be issued to update the CAGE code on the contract.

(c) Contractors located in the United States or its outlying areas that are not registered in SAM shall submit written change requests to the DLA Commercial and Government Entity (CAGE) Branch. Requests for changes shall be provided at https://cage.dla.mil. Change requests to the CAGE master file are accepted from the entity identified by the code.

(d) Contractors located outside the United States and its outlying areas that are not registered in SAM shall contact the appropriate National Codification Bureau (points of contact available at http://www.nato.int/structur/AC/135/main/links/contacts.htm) or NSPA at https://eportal.nspa.nato.int/AC135Public/scage/CageList.aspx to request CAGE changes.

(e) Additional guidance for maintaining CAGE codes is available at https://cage.dla.mil.

(f) If the contract includes Federal Acquisition Regulation clause 52.204-2, Security Requirements, the contractor shall ensure that subcontractors maintain their CAGE code(s) throughout the life of the contract.

(End of Clause) C.2 52.212-4 CONTRACT TERMS AND CONDITIONS—COMMERCIAL PRODUCTS AND COMMERCIAL SERVICES (NOV 2023)

(a) Inspection/Acceptance. The Contractor shall only tender for acceptance those items that conform to the requirements of this contract. The Government reserves the right to inspect or test any supplies or services that have been tendered for acceptance. The Government may require repair or replacement of nonconforming supplies or reperformance of nonconforming services at no increase in contract price. If repair/replacement or reperformance will not correct the defects or is not possible, the Government may seek an equitable price reduction or adequate consideration for acceptance of nonconforming supplies or services. The Government must exercise its post-acceptance rights—

(1) Within a reasonable time after the defect was discovered or should have been discovered; and

(2) Before any substantial change occurs in the condition of the item, unless the change is due to the defect in the item.

(b) Assignment. The Contractor or its assignee may assign its rights to receive payment due as a result of performance of this contract to a bank, trust company, or other financing institution, including any Federal lending agency in accordance with the Assignment of Claims Act (31 U.S.C. 3727). However, when a third party makes payment (e.g., use of the Governmentwide commercial purchase card), the Contractor may not assign its rights to receive payment under this contract.

(c) Changes. Changes in the terms and conditions of this contract may be made only by written agreement of the parties.

(d) Disputes. This contract is subject to 41 U.S.C. chapter 71, Contract Disputes. Failure of the parties to this contract to reach agreement on any request for equitable adjustment, claim, appeal or action arising under or relating to this contract shall be a dispute to be resolved in accordance with the clause at Federal Acquisition Regulation (FAR) 52.233-1, Disputes, which is incorporated herein by reference. The Contractor shall proceed diligently with performance of this contract, pending final resolution of any dispute arising under the contract.

(e) Definitions. The clause at FAR 52.202-1, Definitions, is incorporated herein by reference.

(f) Excusable delays. The Contractor shall be liable for default unless nonperformance is caused by an occurrence beyond the reasonable control of the Contractor and without its fault or negligence such as, acts of God or the public enemy, acts of the Government in either its sovereign or contractual capacity, fires, floods, epidemics, quarantine restrictions, strikes, unusually severe weather, and delays of common carriers. The Contractor shall notify the Contracting Officer in writing as soon as it is reasonably possible after the commencement of any excusable delay, setting forth the full particulars in connection therewith, shall remedy such occurrence with all reasonable dispatch, and shall promptly give written notice to the Contracting Officer of the cessation of such occurrence.

(g) Invoice.

(1) The Contractor shall submit an original invoice and three copies (or electronic invoice, if authorized) to the address designated in the contract to receive invoices. An invoice must include—

(i) Name and address of the Contractor;

(ii) Invoice date and number;

(iii) Contract number, line item number and, if applicable, the order number;

(iv) Description, quantity, unit of measure, unit price and extended price of the items delivered;

(v) Shipping number and date of shipment, including the bill of lading number and weight of shipment if shipped on Government bill of lading;

(vi) Terms of any discount for prompt payment offered;

(vii) Name and address of official to whom payment is to be sent;

(viii) Name, title, and phone number of person to notify in event of defective invoice; and

(ix) Taxpayer Identification Number (TIN). The Contractor shall include its TIN on the invoice only if required elsewhere in this contract.

(x) Electronic funds transfer (EFT) banking information.

(A) The Contractor shall include EFT banking information on the invoice only if required elsewhere in this contract.

(B) If EFT banking information is not required to be on the invoice, in order for the invoice to be a proper invoice, the Contractor shall have submitted correct EFT banking information in accordance with the applicable solicitation provision, contract clause (e.g., 52.232-33, Payment by Electronic Funds Transfer—System for Award Management, or 52.232-34, Payment by Electronic Funds Transfer—Other Than System for Award Management), or applicable agency procedures.

(C) EFT banking information is not required if the Government waived the requirement to pay by EFT.

(2) Invoices will be handled in accordance with the Prompt Payment Act (31 U.S.C. 3903) and Office of Management and Budget (OMB) prompt payment regulations at 5 CFR part 1315.

(h) Patent indemnity. The Contractor shall indemnify the Government and its officers, employees and agents against liability, including costs, for actual or alleged direct or contributory infringement of, or inducement to infringe, any United States or foreign patent, trademark or copyright, arising out of the performance of this contract, provided the Contractor is reasonably notified of such claims and proceedings.

(i) Payment.—

(1) Items accepted. Payment shall be made for items accepted by the Government that have been delivered to the delivery destinations set forth in this contract.

(2) Prompt payment. The Government will make payment in accordance with the Prompt Payment Act (31 U.S.C. 3903) and prompt payment regulations at 5 CFR part 1315.

(3) Electronic Funds Transfer (EFT). If the Government makes payment by EFT, see 52.212-5(b) for the appropriate EFT clause.

(4) Discount. In connection with any discount offered for early payment, time shall be computed from the date of the invoice. For the purpose of computing the discount earned, payment shall be considered to have been made on the date which appears on the payment check or the specified payment date if an electronic funds transfer payment is made.

(5) Overpayments. If the Contractor becomes aware of a duplicate contract financing…