36C26322Q0104.docx

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.

DUNS:

DUNS+4:

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. SIGNATURE 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. 2/2012)

PREVIOUS EDITION IS NOT USABLE

Prescribed by GSA - FAR (48 CFR) 53.212

7. FOR SOLICITATION

INFORMATION CALL:

STANDARD FORM 1449

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

SOLICITATION/CONTRACT/ORDER FOR COMMERCIAL ITEMS

36C26322Q0104 12-08-2021 Jeffrey Brown Jeffrey.Brown8@va.gov 651 293 3009 12-20-2021

5:00 PM

CST

36C263 Department of Veterans Affairs

NETWORK 23 CONTRACTING OFFICE

316 Robert Street N. STE. 506 St. Paul MN 55101 X 621910 $16.5 Million N/A X Department of Veterans Affairs Minneapolis VA Medical Center One Veterans Drive, Building 70 Minneapolis MN 55417 Department of Veterans Affairs

NETWORK 23 CONTRACTING OFFICE

316 Robert Street N. STE. 506 St. Paul MN 55101

Y Department of Veterans Affairs Financial Services Center PO Box 149971 Austin TX 78714-9971 See CONTINUATION Page Provide Ground Ambulance Services for the Twin Ports/Duluth Area, see Statement of Work and Schedule Below.

Important notice to Offerors:

Review and follow INSTRUCTIONS TO OFFERORS in Clause 52.212-1 Addendum.

See CONTINUATION Page X X X Donald Gilbert 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 36C263 Department of Veterans Affairs

NETWORK 23 CONTRACTING OFFICE

316 Robert Street N. STE. 506 St. Paul MN 55101

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.

Department of Veterans Affairs Financial Services Center PO Box 149971

Austin TX 78714-9971 ACKNOWLEDGMENT OF AMENDMENTS: The offeror acknowledges receipt of amendments to the Solicitation numbered and dated as follows:

(End of Clause)

B.2 PRICE/COST SCHEDULE

ITEM INFORMATION

Ground ambulance services, in accordance with the statement of work, see rate table below for individual item pricing.

Contract Period: Base POP Begin: 01-01-2022 POP End: 12-31-2022

Ground ambulance services, in accordance with the statement of work, see rate table below for individual item pricing.

Contract Period: Option 1 POP Begin: 01-01-2023 POP End: 12-31-2023

Ground ambulance services, in accordance with the statement of work, see rate table below for individual item pricing.

Contract Period: Option 2 POP Begin: 01-01-2024 POP End: 12-31-2024

Ground ambulance services, in accordance with the statement of work, see rate table below for individual item pricing.

Contract Period: Option 3 POP Begin: 01-01-2025 POP End: 12-31-2025

Ground ambulance services, in accordance with the statement of work, see rate table below for individual item pricing.

Contract Period: Option 4 POP Begin: 01-01-2026 POP End: 12-31-2026

B.3 RATE TABLE

Base Year

SUBTOTAL (Products)

Option Year One

SUBTOTAL (Products)

Option Year Two

SUBTOTAL (Products)

Option Year Three

SUBTOTAL (Products)

Option Year Four

SUBTOTAL (Products)

B.4 STATEMENT OF WORK

1. Requirement In accordance with standard industry practice furnish Basic Life Support (BLS) and Advanced Life Support (ALS) Ground Ambulance Services to authorized beneficiaries of the Department of Veterans Affairs, Twin Ports Outpatient Clinic (TPOC), Superior, WI 54880 in accordance with the specifications, terms and conditions of this Request for Quotation.

The quantity of trips and mileages indicated in the Schedule of Items are estimated only and were based upon historical and projections were made for an annual requirement. The Government makes no guarantee that these estimates will become actual quantities of trips or mileages.

When scheduling the mode of transportation, i.e., BLS, or ALS, will be discussed with the Contractor and determined by TPOC clinical personnel; however, Contractor will transport per its policies and standard industry practice. If mode of transport differs from what was agreed upon, vendor must submit documentation to TPOC explaining reasons for change.

2. STATUTES/RULES/DEFINITIONS:

a. Transportation services herein are subject to standard industry practice and provider must be compliant with 2006 Minnesota Statutes and Rules Relating to the Regulation of Ambulance Services, or latest edition, as stipulated by applicable sections of the Minnesota Emergency Medical Services Regulatory Board (EMSRB), Chapter 144E. The provider must be currently licensed by the EMSRB.

b. The Contractor will have a medical director qualified for ambulance services, be Minnesota Emergency Medical Services Regulatory Board (EMSRB) certified, and multi-state certified; will be a physician who accepts responsibility for the quality of care provided during transport by drivers and attendants; provides standards for training and orientation of personnel; provides standards on upgrading and purchasing equipment; prescribes any standing orders for the provision of life support care; provides triage, treatment, and transporting protocols to ensure that patients requiring care are transported appropriately; assists with the development and operation of an internal quality assurance mechanism that includes a review of services provided; provides written procedures for the storage and administration of drugs; and provides written standards for medical equipment and supplies used to provide ambulance services. The medical director is considered a key personnel and is essential to the work performance, VAAR clause 852.237-75 applies.

Contractor must provide service Monday through Friday (excluding holidays) for TPOC for the term of this contract. The majority of the requests for service for TPOC will be between the hours of 6:00 a.m. and 6:00 p.m., Monday through Friday. The Contractor must provide TPOC with a method of contacting him/her, 24-hours per day.

9. REQUEST FOR SERVICES:

a. Request for services will be made in writing (facsmile, e-mail, mail) or by telephone by an authorized representative of the VA. When ordering services the VA shall provide the Contractor with the following type of information:

· Mode of transportation required;

· Required date and time of arrival;

· Name of Beneficiary

· Pick-up and delivery point;

· Type and number of additional medical care specialists required;

· Any other special instructions;

d. In the case of inclement weather, the decision as to whether or not a VA beneficiary will be transported will be discussed with the Contractor; however, the final decision as the whether a patient transport will be ordered or cancelled remains with the VA.

e. The contractor shall, at all times during the contract period, have on his/her premises a functioning fax machine to communicate requirements with the VA (i.e., requests for service, patient incidents, special correspondence, etc.). Each contractor shall indicate if there is e-mail availability for their company to complete communications with the VA (use of this communication system will be mutually agreed upon after award of contract before any communications are completed in this manner). If the contractor’s place of business is located beyond the local telephone call zone of the VA (area code 612), the contractor shall install and provide to the VA, a toll free number for accepting the VA calls. It is estimated that 90% of daily contacts regarding questions and/or problems are initially addressed by telephone.

b. Ground Ambulance Response to Air Ambulance Ground Pick Up Transport Services: VA will provide ground ambulance contractor with an estimated time of arrival in accordance with paragraphs 9b (1) & (2) when services are required for pick-up of patients transported to the Minneapolis VAMC through air ambulance. While in flight, the VA air ambulance contractor will notify the ground ambulance contractor with an updated estimated time of flight arrival, normally one (1) hour prior to flights actual arrival (dependant upon departure location). In the event that contractor fails to pick up air ambulance patient within fifteen (15) minutes of scheduled landing, the VAMC reserves the right to bill ground ambulance contractor established air crew layover fee in fifteen minute increments.

c. Response Time Compliance Rate: The contractor shall maintain at a minimum an 80% compliance rate on responses to pick-up or deliver during the contract year. Failure of the contractor to perform in accordance with the compliance rating may constitute sufficient cause for termination of the contract for cause (see FAR clause 52.212-4(m))

11. INSPECTION:

a. An inspection plan covering all services required by this contract. The inspection plan must specify the areas to be inspected on either a scheduled or unscheduled basis, how often inspections will be accomplished and documented, and the title of the individual(s) who will perform the inspections.

b. On-site records of all inspections conducted by the Contractor noting necessary corrective action taken. The Government reserves the right to request copies of any and/or each inspection.

c. Incorporation of either active or established internal policy and procedures for updating service protocols that may affect performance of contract.

d. The methods for identifying and preventing deficiencies in the quality of service performed, before the level of performance becomes unacceptable, and organizational functions noting intermediate supervisory responsibilities and overall management responsibilities for ensuring total acceptable performance.

e. On-site records of all vehicle maintenance and repairs performed on vehicles used in the performance of this contract. The methods of identifying and preventing vehicle breakdowns, and detailed procedure for alternative transportation of patients in the event of mechanical breakdown of vehicle.

f. On-site records identifying the character (background checks) and certifications of ongoing training of each employee performing services under this contract.

g. The methods of identifying and preventing radio communication breakdowns. A detailed procedure for alternative communications in the event of electronic and mechanical breakdown of vehicle two-way radios.

h. A log to account for all requests for service. The log shall indicate the date and time of service call, name of patient requiring services, designated pick-up and delivery points, actual time of arrival at pick-up and delivery points and actual waiting time at pick-up and delivery points, if waiting charges are claimed.

On-site records of any complaints or problems, with procedures taken to allow for corrections and/or elimination before effects caused interruption of performance of contract.

13. Miscellaneous:

a. Contractor employees shall conduct themselves in a businesslike manner at all times while on VA premises.

b. When transporting patients to or from Medical facilities, the driver, acting for the Contractor, will ensure that patient’s luggage, medical records, medications, and prosthetic devices are properly accounted for and delivered with the patient as required.

END STATEMENT OF WORK

B.5 IT CONTRACT SECURITY

VA INFORMATION AND INFORMATION SYSTEM SECURITY/PRIVACY

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

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

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

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

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

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

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

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

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

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

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

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

l. 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 COR.

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 COR, and approved by the VA Privacy Service in accordance with Directive 6507, VA Privacy Impact Assessment.

b. The contractor/subcontractor shall certify to the COR 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 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.

g. The contractor/subcontractor agrees to:

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

(a) The Systems of Records (SOR); and

(b) The design, development, or operation work that the contractor/ subcontractor is to perform;

(1) 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

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

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

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

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

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

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

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

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.

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 vulnerablity 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 COR 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.