Notice ID: 1ae5f94204e14e96b29cead80eb966a8Award NoticeAwarded
J065--Scriptpro Oracle Migration Support in support of the VISN 23 VACHS
Awarded on August 25, 2026. Award Notice posted by VETERANS AFFAIRS, DEPARTMENT OF on August 25, 2026. Solicitation 36C26326Q1000.
NAICS 541512 (Computer Systems Design Services). The description is published on SAM.gov: Full description on SAM.gov.
Awarded tounder 36C26326C0056 (source: SAM.gov award notice)• $64.8K
Description
No description in the SAM.gov data feed for this notice.
Overview
Agency:
Department of Veterans Affairs
Office:NETWORK CONTRACT OFFICE 23 (36C263)
Posted:August 25, 2026
NAICS:541512: Computer Systems Design Services
Last Updated:Oct 6, 2026
PSC:J065: MAINT/REPAIR/REBUILD OF EQUIPMENT- MEDICAL, DENTAL, AND VETERINARY EQUIPMENT AND SUPPLIES
Response Deadline:
Not specified
Set-Aside:Not specified
Type:Award Notice
Place of Performance:Not specified
Award Date:Aug 25, 2026
Award Amount (SAM.gov award notice):$64.8K
Award Overview
Award Number
36C26326C0056
Award Amount (SAM.gov award notice)
$64.8K
Award Date
Aug 25, 2026
Awardee
Awardee UEI
RTB3DEMJ91U4
Awardee CAGE Code
1FYZ2
Original Solicitation
Notice ID: 1ae5f94204e14e96b29cead80eb966a8
Posted Date: Aug 25, 2026
Original Response Deadline: Not specified
Contacts
Contracting Officer
Primary Contact
Documents
Select documents to download
Showing 4 of 4 items
Document | Source | Agency | Posted Date | File Size | Actions | |
|---|---|---|---|---|---|---|
| Award Notice | VETERANS AFFAIRS, DEPARTMENT OF | Aug 25, 2026 | 3.25 MB | |||
| Award Notice | VETERANS AFFAIRS, DEPARTMENT OF | Aug 25, 2026 | 13.42 KB | |||
| Award Notice | VETERANS AFFAIRS, DEPARTMENT OF | Aug 25, 2026 | 13.42 KB | |||
| Award Notice | VETERANS AFFAIRS, DEPARTMENT OF | Aug 25, 2026 | 3.25 MB |
Lifecycle
Solicitation:
36C26326Q1000- Awarded
This opportunity has been awarded.
- 2×AwardedCurrentAug 25, 2026
J065--Scriptpro Oracle Migration Support in support of the VISN 23 VACHS
Similar Opportunities
Title | Phase | Agency | NAICS | Set Aside | Posted | Deadline | Location |
|---|---|---|---|---|---|---|---|
| Awarded | 541512 | No Set-Aside | 08/25/2026 | Open | - | ||
| Awarded | 541512 | Service-Disabled Veteran-Owned Small Business Set-Aside | 08/25/2026 | Open | - | ||
This award notice/synopsis is being issued to fulfil the requirements of FAR 6.302-1(d)(2) and FAR 5.201. The procurement is a sole source action for Data Analytics Service Line Support Services. The contractor is ReefPoint Group, LLC. The statutory authority permitting other than full and open competition for this acquisition is 41 U.S.C. 3304(a)(5), Authorized or Required by Statute, as implemented by FAR 6.103-5. For this action, 38 U.S.C. 8127(c), known as the Veterans First Contracting Program, provides the authority to directly contract with a Service-Disabled Veteran-Owned Small Business (SDVOSB) or a Veteran0Owned Small Business (VOSB). | Awarded | 541512 | Service-Disabled Veteran-Owned Small Business Set-Aside | 10/08/2026 | Open | - | |
Request for Information Synopsis Enterprise Service Desk: Integrated Service Delivery Model with Independent Billing and Outcome Oversight 1.0 RFI Synopsis Narrative Background and Purpose The Department of Veterans Affairs (VA), Office of Information & Technology (OIT), Enterprise Command Operations (ECO) is issuing a Request for Information (RFI) to conduct market research supporting a planned future acquisition strategy for Enterprise Service Desk (ESD) support and its associated Contact Center Infrastructure (CCI). VA currently operates ESD Tier 0/1 support and CCI as two separate prime contracts under a Multi-Vendor Service Provider (MVSP) model, where the CCI vendor produces independent Service Level Agreement (SLA) compliance reporting and conducts formal quality assurance oversight of the Tier 1 vendor's performance. VA is exploring whether and how Tier 1 agent services and CCI platform management could be brought together under an integrated service delivery model, while determining what functions, if any, should remain organizationally independent from the delivery contractor to preserve objective performance, quality, and billing oversight. VA has not determined the appropriate scope or structure of any such independent function and is seeking industry input on whether independence is necessary, which functions require it, and the most effective means of providing it. The primary purpose of this RFI is to hear from industry on how an integrated delivery model would work in practice, i.e., how it would be structured, transitioned, and operated and to use that input, together with the Rough Order of Magnitude (ROM) estimates requested below, to inform the resulting Performance Work Statement (PWS) and VA's decisions on scope, sequencing, and commercial structure. VA recognizes that consolidation may not be the right answer in every respect, and industry input that identifies where a combined model would be impractical, along with the reasoning behind that view, is just as valuable to VA as input on how to make consolidation work. This RFI is not a solicitation and does not commit VA to a particular acquisition approach. One specific issue on which VA would welcome industry input, particularly in the context of a combined model, is how outcomes should be classified if VA adopts outcome-based, automation-linked, or gainshare pricing. Under those pricing structures, the classification of individual contacts (e.g., AI-resolved vs. human-handled, genuinely deflected vs. merely relabeled, successfully automated vs. escalated) becomes the basis for what VA pays. If agent services and CCI are combined, VA wants to understand how a vendor would ensure that the entity performing the work and the entity classifying/reporting the outcome of that work don't create a structural incentive to classify ambiguous or borderline contacts in whichever direction favors billing. VA recognizes that transparent data feeds alone may not fully resolve this on their own, since the vendor typically controls the metadata structure, the correlation logic between systems, and the judgment calls in ambiguous cases. This lines up with feedback VA has already received from industry: multiple respondents to prior VA market research independently flagged the "AI-attempted-then-escalated" correlation and the "resolving tier" determination as fields that are self-reported, consequential to billing, and not easily produced by either vendor alone under the current structure. Given that feedback, VA wants industry's perspective on whether some form of independent validation of billing-relevant outcomes would be useful under a combined model, and if so, how narrowly or broadly it should be scoped. For example, whether it should focus solely on billing/outcome validation, or whether it makes more sense operationally to fold in general quality assurance scoring and day-to-day SLA compliance reporting as well. VA has not settled this question and is not assuming an independent function is necessary at all; VA's own data feeds, combined with automated QA tooling already in production, may prove sufficient on their own. This RFI invites industry input to help VA define the scope of the issue without presupposing a particular outcome. Strategic Direction VA's objective is not simply to combine two existing statements of work. It is to move the ESD operating model from a labor- and channel-centric structure to one organized around demand elimination, unified customer experience, and outcome-based accountability. Specifically, VA is seeking industry's perspective on an operating model that: Eliminates demand rather than optimizing contact handling. The strategic objective is not reducing cost per contact but reducing the volume of contacts that require human involvement in the first place, through AI-assisted self-service, proactive communication, automated fulfillment, and FboNotice-cause elimination. Presents a unified, channel-agnostic experience to the End User. The distinction between phone, chat, portal, and other channels should be invisible to the employee; the service environment, not the caller, determines whether AI, automation, knowledge, or a human agent is the appropriate resolution path. Treats AI and automation as the operating model, not an add-on. The relevant question is which categories of work should never require a human, and how the contractor is held contractually accountable for progressively moving categories of work off human agents. Realigns commercial incentives from resources consumed to outcomes achieved, while recognizing that outcome-based and gainshare pricing models raise the stakes on how outcomes are classified and who classifies them. Current Environment VA's current environment processes approximately 125,000 150,000 contacts per month across voice, chat, SMS, and self-service channels, supports roughly 600,000 End Users and 900 applications, and already has voice biometric verification, IVR-based automation (NICE Autopilot), and Medallia-based automated quality analytics in development or early production. VA's current CCI platform is NICE CXOne. VA is not presupposing that either of these existing tooling investments, the CCI platform or the automated QA platform, necessarily carries forward unchanged into a consolidated structure, and is asking industry to address both explicitly in the questions below. For purposes of responding to this RFI, the current functional baseline includes Tier 0/self-service and Tier 1 multi-channel end-user support, incident and service request intake, triage, resolution, and routing; knowledge management, process integration and new-service intake; workforce management, ACD/IVR and contact routing, contact recording and quality management, contact center platform administration; analytics and reporting; integration with VA's enterprise ITSM environment, customer experience capabilities, identity verification, existing voice AI/IVR automation and evolving enterprise self-service and AI capabilities; transition services; and continual service improvement. VA is interested in industry's perspective on evolving these capabilities toward an omnichannel service model and expanded AI-enabled automation. This description is intended to provide industry with sufficient context regarding the current functional baseline and potential scope under consideration. VA has not determined that all functions identified above will be included within a single future acquisition, nor has VA determined the final allocation of responsibilities among the delivery contractor, VA, other enterprise service providers, or any independent oversight function. Industry is specifically encouraged to identify functions that would benefit from common contractual accountability, as well as functions that should remain separate and the rationale for doing so. What VA Is Asking Industry to Address This RFI asks industry to respond to the questions below based on operational and commercial experience delivering comparable integrated service desk models particularly within federal, security-sensitive, or highly regulated environments, and where outcome-based or automation-linked billing has been implemented. VA's central interest is in how industry would combine Tier 1 and CCI delivery successfully, where industry believes a combined model would not work well, and to understand why to assist in determining the acquisition approach. VA is also interested in candid input on how billing-relevant classifications can be gamed, intentionally or not, and what structural safeguards actually prevent it as opposed to merely documenting it after the fact. This RFI is issued for information and planning purposes only and does not constitute an Invitation for Bid, Request for Task Execution Plan, Request for Quotation or Request for Proposal nor does it restrict the Government as to the ultimate acquisition approach. In accordance with (IAW) Federal Acquisition Regulation (FAR) 15.201(e) and 15.101-1, responses to this notice are not offers and cannot be accepted by the Government to form a binding contract. Responses to this RFI will directly inform requirements development, as well as VA's continued re nement of contract scope, sequencing, and commercial structure. You will not be entitled to payment for direct or indirect costs that you incur in responding to this RFI. This request does not constitute a solicitation for proposals or the authority to enter into negotiations to award a contract. No funds have been authorized, appropriated or received for this effort. Interested parties are responsible for adequately marking proprietary, restricted or competition sensitive information contained in their response. The Government does not intend to pay for the information submitted in response to this RFI. Not responding to this RFI does not preclude participation in any future Invitation for Bid, Request for Task Execution Plan, Request for Quotation or Request for Proposal, if any is issued. Any information submitted by respondents to this RFI is strictly voluntary. All submissions become Government property and will not be returned. Proposed RFI Questions 1. Integrated Operating Model and Transition How would your organization recommend VA structure and operate an integrated service delivery model for ESD Tier 1 agent services and CCI, including Automatic Call Distributor, Interactive Voice Response, telephony, and platform management? Please address whether these capabilities should be delivered under a single contract or separate contracts, including the benefits, risks, dependencies, and conditions necessary for your recommended model to succeed. Additionally, describe how VA should transition from its current two-prime MVSP environment to the recommended model while maintaining service continuity for approximately 600,000 End Users. Address platform continuity, data and knowledge transfer, workforce transition, and whether Tier 1 and CCI should transition simultaneously or be sequenced, including the rationale for your recommended approach. Â 2. Platform and Tooling: Retain or Replace VA's current CCI platform is NICE CXOne, and its current automated quality assurance capability runs on the Medallia Speech, Sentiment, and Analytics platform. Prior market research conducted on the CCI requirement alone returned a strong industry preference for retaining NICE CXOne. VA also uses Genesys as its enterprise Contact Center as a Service platform. Compare retaining NICE CXOne for this requirement with transitioning to Genesys, including the relative cost, transition timeline, operational risk, functionality, and long-term efficiencies of each approach. Separately, address whether VA should retain Medallia for automated QA or consider an alternative, and why. 3. Enterprise ITSM Integration and ServiceNow Dependency VA's current enterprise ITSM environment is ServiceNow, however the future enterprise ITSM solution has not yet been determined. How critical is identification of the future ITSM solution to your ability to propose, price, transition, and perform the ESD Tier 1/CCI requirement? What ITSM information or interface requirements would VA need to define in the solicitation if the specific future-state tool is not yet known? 4. Performance, Billing, & Independent Oversight Under an outcome-based, automation-linked, or gainshare pricing model, how would your organization ensure the accuracy and integrity of classifications used to determine VA payments? Please address: how successful automated or self-service resolution should be defined, including escalations, repeat contacts, incomplete resolutions, and abandoned interactions; safeguards against contractor-favorable classification or reporting; whether independent validation is warranted and, if so, whether it should cover billing/outcomes only or also QA and SLA compliance; and governance and dispute-resolution mechanisms. Identify the key definitions and potential classification disputes VA should resolve in the PWS upfront. If independent oversight is unnecessary, explain what controls and data transparency would give VA sufficient confidence in contractor-reported results. 5. Demand Elimination and Automation Roadmap What approaches, technologies, and operating practices would you employ to reduce the need for human-assisted contacts over the life of the contract? Identify the types of service desk requests you would prioritize for automation first, the key dependencies VA would need to address, and how you would phase implementation. Address how generative AI, conversational AI, agentic automation, and predictive capabilities would support that roadmap and how VA should measure progress. 6. Commercial and Pricing Models and Rough Order of Magnitude (ROM) What pricing model would best incentivize automation, demand reduction, and service quality while remaining viable as human-assisted volume declines? Provide a five-year ROM for your recommended ESD Tier 1/CCI delivery model, including major staffing, platform/licensing, transition, automation, and independent oversight assumptions. Provide separate platform cost assumptions for retaining NICE CXOne and transitioning to Genesys, to the extent practicable, and identify material cost differences between integrated and separate ESD Tier 1/CCI delivery. 7. Security, Privacy, and High-Risk Interaction Governance What unique considerations should VA address regarding cybersecurity, data ownership, records management, biometric data handling, system authorization (ATO/FedRAMP), and AI governance in a model where a consolidated vendor holds both agent-facing and infrastructure-level access? Separately, VA is considering, but has not formally adopted, a risk-tiered verification framework (e.g., voice biometric, mobile OTP, supervisor authorization) for high-risk transactions such as credential resets and account access changes. For planning purposes, assuming such a framework were adopted, how would a consolidated delivery vendor operationalize and enforce it across both the platform and agent layers? 8. Acquisition Structure, Organizational Conflict of Interest, and Relevant Experience What contract and organizational structure would you recommend for ESD Tier 1 and CCI, including any functions that should remain independent to address OCI concerns? Briefly describe comparable experience delivering the recommended model at similar scale, including outcome-based pricing or independent performance oversight where applicable. 9. Section 508 / Accessibility Compliance How would your company ensure that all customer-facing and agent-facing components of a consolidated ESD/CCI solution- including IVR, chat, self-service portals, knowledge base interfaces, and any AI-driven or conversational automation, meet Section 508 accessibility requirements (including WCAG conformance for digital interfaces and accessible design for voice/IVR interactions)? Describe your approach to accessibility testing, remediation, and ongoing conformance monitoring across the life of the contract, including how new AI/automation features would be evaluated for accessibility before deployment rather than after the fact. 10. What VA May Be Missing: Based on the information provided in this RFI, what important requirements, risks, dependencies, or considerations has VA not addressed that should inform development of the future PWS and acquisition strategy? As part of your response, identify any functions that should remain separate rather than be consolidated and explain why. 2. Submittal Information: All responsible sources may submit a response in accordance with the information below. There is a page limitation for this RFI of 25 pages. The Government will not review any other information or attachments included, that are in excess of the 25-page limit. NO MARKETING MATERIALS ARE ALLOWED AS PART OF THIS RFI. Generic capability statements will not be accepted or reviewed. Responses are due no later than 10:00AM ET, Wednesday, October 21, 2026 via email to Andrea Caltabilota, Contract Specialist at Andrea.Caltabilota@va.gov. Please note Enterprise Service Desk RFI in the subject line of your response. Mark your response as Proprietary Information if the information is considered business sensitive. The email file size shall not exceed 5 MB. | Market Research | 541512 | No Set-Aside | 10/07/2026 | 10/21/2026 | - | |
Page 1 of 1 36C25027Q0023 SPECIAL NOTICE NOTICE OF INTENT TO SOLE SOURCE Abbott RALS POC Middleware - Columbus, OH The Department of Veterans Affairs, The Chalmers P. Wylie VA Ambulatory Care Center, Columbus OH, 420 N. James Road, Columbus, Ohio 43219 intends to solicit and negotiate with only one source under the authority of FAR 6.302-1(a), Only one responsible source and no other supplies or services will satisfy agency requirements. The VA intends to solicit and negotiate with Abbott Rapid Diagnostics Informatics, Inc., RALS, 915 East High Street, Suite 500, Charlottesville, VA 22902. This purchase is with Abbott Rapid Diagnostics Informatics, Inc., RALS; Abbott does not use third parties to distribute their products to the government. Abbott has a program for connecting Abbott i-STAT, Abbott ID NOW and Accu-Chek point of care instruments to RALS Software so that Veteran test results automatically upload to the Electronic Health Medical Records. RALS is already in use at Columbus VA ACC and outlying CBOCs. RALS is the only Middleware capable of restricting user access for manual POC test entry into the EHRM and compatible with Cerner. The Government believes that only Abbott Rapid Diagnostics Informatics, Inc., RALS can satisfy the agency requirement. We intend to negotiate with only one source under the authority of FAR 6.302-1(a)(2), Only one responsible source and no other supplies or services will satisfy agency requirements. Other people may identify their interest and capability to respond to this requirement by October 13, 2026, by 5PM EST. Such capabilities information will be used solely for the purpose of determining whether or not to conduct this procurement on a competitive basis. All information shall be furnished at no cost or obligation to the Government. A determination by the Government not to open the requirement to competition based upon responses to this notice is solely within the discretion of the Government. No solicitation is available at this time.  All inquiries must be submitted by email to Gina P. Crank at gina.crank@va.gov Enter RFQ 36C25027Q0023 Abbott RALS POC Middleware - Columbus, OH in the email subject line. DEPARTMENT OF VETERANS AFFAIRS Justification for Single Source Awards IAW FAR 13.106-1 For Over Micro-Purchase Threshold but Not Exceeding the SAT Acquisition Plan Action ID: 36C250-27-AP-0832 Contracting Activity: Department of Veterans Affairs, Network/Program Contracting Office 10, in support of VISN 3 VA Health Care System located at 420 N James Rd, Columbus, Ohio 43219 using 2237# 757-27-1-775-0010 Brief Description of Supplies/ Services required and the intended use/Estimated Amount: Abbott Rapid Diagnostics Informatics RALS Middleware to support ID Now point of care patient testing instrumentation. This middleware allows the transmission of point of care instrumentation data to the facilities Laboratory Information System (LIS) which is subsequently viewable to the clinicians via Cerner Electronic Health Record Modernization (EHRM). The interface connections will transmit results from the provided POC testing for COVID 19, Influenza A/B, RSV, Strep A, Creatinine and Glucose at the main facility and all Community Based Outpatient Clinic (CBOC) locations. Unique characteristics that limit availability to only one source, with the reason no other supplies or services can be used: This middleware is proprietary for the use of these point of care testing devices and the subsequent transmission of data into the facilities LIS system. Description of market research conducted and results or statement why it was not conducted: Per the End user, not applicable, as this is proprietary middleware for use with this specific point of care testing devices. The CO conducted market research to locate adequate small business concerns on ADDS-UP, GSA Advantage/eBuy, eLibrary, FPDS, SAM, SBL, and the Internet. The SBA nor the VA s Rule of Two can be met. An Intent to Sole Source will be posted on Contract Opportunities. Contracting Officer's Certification: Purchase is approved in accordance with FAR13.106-1(b). I certify that the foregoing justification is accurate and complete to the best of my knowledge and belief. ______________ Gina P. Crank 10/06/2026 Contracting Officer STATEMENT OF WORK (SOW) PROGRAM REQUESTOR/MANAGER. Name: Marie Brown Section: Pathology & Laboratory Medicine Service (PLM) Address: 420 N James Rd, Columbus, OH, 43219 Fax Number: 614-257-5629 E-Mail Address: Marie.brown@va.gov 2. Contract Title. Point-of-Care Middleware, Remote Automated Laboratory System (RALS) 3. Background. Columbus VA Central Ohio Healthcare System has a requirement to maintain the Remote Automated Laboratory Systems (RALS) software technology currently connecting multiple devices to one data manager. The RALS software enables review and release of patient results to the Laboratory Information System (LIS) directly from each device. RALS allows the ability to manage, update, review and troubleshoot quality control results, operator and device issues remotely. 4. Scope. The contractor shall provide RALS software licensing and interface for Point-of-Care testing connectivity software that is used to post patient test results to the electronic patient record (Cerner). This software allows the end user to monitor tests completed at the point-of-care and to meet numerous accreditation requirements for laboratory tests performed throughout the VA Columbus Ambulatory Care Center located at 420 North James Rd, Columbus, OH 43219 and surrounding Community Based Outpatient Clinics (CBOCs) located in Grove City, Newark, Zanesville, Marion and Delaware Ohio. Software must be compatible with Roche Accu-Chek® Inform II Module (38 devices), Abbott i-STAT® Module (8 devices), and Abbott ID-Now (9 devices) and the VHA s current Electronic Health Record (Cerner). The software must have the capability to add more instruments when the need arises. The Technology Licensure shall include service, support, updates and hardware maintenance. 5. Specific Tasks. The contractor shall provide the RALS device modules to include: Software Components: RALS device software module for the Roche Accu-Check® Inform II glucometers. RALS device software module for the Abbott i-STAT® instruments. RALS device software module for the Abbott ID-Now instruments. RALS HL7 Interface ADT Interface; ADT in-Unit Patient Verification with positive patient identification. 5.1. 2 Other Components: a. RALS User Documentation will be provided in the current medium. b. Standard Training, instruction and consultation for the Customer required for the use of the RALS Software Technology System (STS). Hardware Components provided by the vendor: RALS Data ports, if applicable Information Management System All written deliverables shall be phrased in layperson language. Statistical and other technical terminology shall not be used without providing a glossary of terms. Conformance Standards: The contractor s performance must follow all applicable state, federal and local laws and regulations. Hours of Work: The Warranty is in effect for the entire duration of the contract. The contractor shall provide 24 hours, 7 days a week Technical Support. Preventative Maintenance: The Contractor shall provide upgrades at no cost to the government throughout the duration of this contract. The Contractor shall provide documentation of services performed. Emergency Repair Service: 24 hours, 7 days a week Technical Support. 6. Records Management All records (administrative and program specific) created during the period of the contract belong to Columbus VA Ambulatory Care Center and must be returned to Columbus VA Ambulatory Care Center at the end of this contract. 7. Quality Assurance Surveillance Plan (QASP) The QASP and its performance are as follows: Task Indicator Standard Acceptable Quality Level Method of Surveillance Incentive Safety Recall Notification Timely recall notification 100% Monthly Monitoring Exercise of Option Period & Past Performance Quality Assurance Phone support Within 24 hours 95% Monthly monitoring Exercise of Option Period & Past Performance 8. VA Information and Information System Security and Privacy Language 8.1 GENERAL: This entire section applies to all acquisitions requiring any Information Security and Privacy language. Contractors, contractor personnel, subcontractors and subcontractor personnel will be subject to the same federal laws, regulations, standards, VA directives and handbooks, as VA personnel regarding information and information system security and privacy. 8.2 VA INFORMATION CUSTODIAL LANGUAGE: This entire section applies to all acquisitions requiring any Information Security and Privacy language. a. The Government shall receive unlimited rights to data/intellectual property first produced and delivered in the performance of this contract or order (hereinafter contract ) unless expressly stated otherwise in this contract. This includes all rights to source code and all documentation created in support thereof. The primary clause used to define Government and Contractor data rights is FAR 52.227-14 Rights in Data General. The primary clause used to define computer software license (not data/intellectual property first produced under this contractor or order) is FAR 52.227-19, Commercial Computer Software License. b. Information made available to the contractor by VA for the performance or administration of this contract will be used only for the purposes specified in the service agreement, SOW, PWS, PD, and/or contract. The contractor shall not use VA information in any other manner without prior written approval from a VA Contracting Officer (CO). The primary clause used to define Government and Contractor data rights is FAR 52.227-14 Rights in Data General. c. VA information will not be co-mingled with any other data on the contractor s information systems or media storage systems. The contractor shall ensure compliance with Federal and VA requirements related to data protection, data encryption, physical data segregation, logical data segregation, classification requirements and media sanitization. d. VA reserves the right to conduct scheduled or unscheduled audits, assessments, or investigations of contractor Information Technology (IT) resources to ensure information security is compliant with Federal and VA requirements. The contractor shall provide all necessary access to records (including electronic and documentary materials related to the contracts and subcontracts) and support (including access to contractor and subcontractor staff associated with the contract) to VA, VA's Office Inspector General (OIG), and/or Government Accountability Office (GAO) staff during periodic control assessments, audits, or investigations. e. The contractor may only use VA information within the terms of the contract and applicable Federal law, regulations, and VA policies. If new Federal information security laws, regulations or VA policies become applicable after execution of the contract, the parties agree to negotiate contract modification and adjustment necessary to implement the new laws, regulations, and/or policies. f. The contractor shall not make copies of VA information except as specifically authorized and necessary to perform the terms of the contract. If copies are made for restoration purposes, after the restoration is complete, the copies shall be destroyed in accordance with VA Directive 6500, VA Cybersecurity Program and VA Information Security Knowledge Service. g. If a Veterans Health Administration (VHA) contract is terminated for default or cause with a business associate, the related local Business Associate Agreement (BAA) shall also be terminated and actions taken in accordance with VHA Directive 1605.05, Business Associate Agreements. If there is an executed national BAA associated with the contract, VA will determine what actions are appropriate and notify the contactor. h. The contractor shall store and transmit VA sensitive information in an encrypted form, using VA-approved encryption tools which are, at a minimum, Federal Information Processing Standards (FIPS) 140-2, Security Requirements for Cryptographic Modules (or its successor) validated and in conformance with VA Information Security Knowledge Service requirements. The contractor shall transmit VA sensitive information using VA approved Transport Layer Security (TLS) configured with FIPS based cipher suites in conformance with National Institute of Standards and Technology (NIST) 800-52, Guidelines for the Selection, Configuration and Use of Transport Layer Security (TLS) Implementations. i. The contractor s firewall and web services security controls, as applicable, shall meet or exceed VA s minimum requirements. j. Except for uses and disclosures of VA information authorized by this contract for performance of the contract, the contractor may use and disclose VA information only in two situations: (i) in response to a qualifying order of a court of competent jurisdiction after notification to VA CO (ii) with written approval from the VA CO. The contractor shall refer all requests for demands for production of or inquiries about VA information and information systems to the VA CO for response. k. Notwithstanding the provision above, the contractor shall not release VA records protected by Title 38 U.S.C. § 5705, Confidentiality of medical quality-assurance records and/or Title 38 U.S.C. § 7332, Confidentiality of certain medical records pertaining to drug addiction, sickle cell anemia, alcoholism or alcohol abuse or infection with Human Immunodeficiency Virus (HIV). If the contractor is in receipt of a court order or other requests for the above-mentioned information, the contractor shall immediately refer such court order or other requests to the VA CO for response. l. Information made available to the contractor by VA for the performance or administration of this contract or information developed by the contractor in performance or administration of the contract will be protected and secured in accordance with VA Directive 6500 and Identity and Access Management (IAM) Security processes specified in the VA Information Security Knowledge Service. m. Any data destruction done on behalf of VA by a contractor shall be done in accordance with National Archives and Records Administration (NARA) requirements as outlined in VA Directive 6300, Records and Information Management, VA Handbook 6300.1, Records Management Procedures, and applicable VA Records Control Schedules. n. The contractor shall provide its plan for destruction of all VA data in its possession according to VA Directive 6500 and NIST 800-88, Guidelines for Media Sanitization prior to termination or completion of this contract. If directed by the COR/CO, the contractor shall return all Federal Records to VA for disposition. o. Any media, such as paper, magnetic tape, magnetic disks, solid state devices or optical discs that is used to store, process, or access VA information that cannot be destroyed shall be returned to VA. The contractor shall hold the appropriate material until otherwise directed by the Contracting Officer s Representative (COR) or CO. Items shall be returned securely via VA-approved methods. VA sensitive information must be transmitted utilizing VA-approved encryption tools which are validated under FIPS 140-2 (or its successor) and NIST 800-52. If mailed, the contractor shall send via a trackable method (USPS, UPS, FedEx, etc.) and immediately provide the COR/CO with the tracking information. Self-certification by the contractor that the data destruction requirements above have been met shall be sent to the COR/CO within 30 business days of termination of the contract. P. All electronic storage media (hard drives, optical disks, CDs, back-up tapes, etc.) used to store, process or access VA information will not be returned to the contractor at the end of lease, loan, or trade-in. Exceptions to this paragraph will only be granted with the written approval of the VA CO. 8.3 ACCESS TO VA INFORMATION and INFORMATION SYSTEMS: This section applies when any person requires access to information made available to the contractor by VA for the performance or administration of this contract or information developed by the contractor in performance or administration of the contract. a. A contractor/subcontractor shall request logical (technical) or physical access to VA information and VA information systems for their employees and subcontractors only to the extent necessary to perform the services specified in the solicitation or contract. This includes indirect entities, both affiliate of contractor/subcontractor and agent of contractor/subcontractor. b. Contractors and subcontractors shall sign the VA Information Security Rule of Behavior (ROB) before access is provided to VA information and information systems (see Section 4, Training, below). The ROB contains the minimum user compliance requirements and does not supersede any policies of VA facilities or other agency components which provide higher levels of protection to VA s information or information systems. Users who require privileged access shall complete the VA elevated privilege access request processes before privileged access is granted. c. All contractors and subcontractors working with VA information are subject to the same investigative security and clearance requirements as those of VA appointees or employees who have access to the same types of information. The level and process of background security investigations for contractors shall be in accordance with VA Directive and Handbook 0710, Personnel Suitability and Security Program. The Office of Human Resources and Administration/Operations, Security and Preparedness (HRA/OSP) is responsible for these policies and procedures. Contract personnel who require access to classified information or information systems shall have an appropriate security clearance. Verification of a Security Clearance shall be processed through the Special Security Officer located in HRA/OSP. Contractors shall conform to all requirements stated in the National Industrial Security Program Operating Manual (NISPOM). d. All contractors and subcontractors shall comply with conditions specified in VAAR 852.204-71(d); Contractor operations required to be in United States. All contractors and subcontractors working with VA information must be permanently located within a jurisdiction subject to the law of the United States or its Territories to the maximum extent feasible. If services are proposed to be performed abroad the contractor must state where all non-U.S. services are provided. The contractor shall deliver to VA a detailed plan specifically addressing communications, personnel control, data protection and potential legal issues. The plan shall be approved by the COR/CO in writing prior to access being granted. e. The contractor shall notify the COR/CO in writing immediately (no later than 24 hours) after personnel separation or occurrence of other causes. Causes may include the following: Contractor/subcontractor personnel no longer has a need for access to VA information or VA information systems. (2) Contractor/subcontractor personnel are terminated, suspended, or otherwise has their work on a VA project discontinued for any reason. (3) Contractor believes their own personnel or subcontractor personnel may pose a threat to their company s working environment or to any company-owned property. This includes contractor-owned assets, buildings, confidential data, customers, employees, networks, systems, trade secrets and/or VA data. (4) Any previously undisclosed changes to contractor/subcontractor background history are brought to light, including but not limited to changes to background investigation or employee record. (5) Contractor/subcontractor personnel have their authorization to work in the United States revoked. (6) Agreement by which contractor provides products and services to VA has either been fulfilled or terminated, such that VA can cut off electronic and/or physical access for contractor personnel. f. In such cases of contract fulfillment, termination, or other causes; the contractor shall take the necessary measures to immediately revoke access to VA network, property, information, and information systems (logical and physical) by contractor/subcontractor personnel. These measures include (but are not limited to): removing and then securing Personal Identity Verification (PIV) badges and PIV Interoperable (PIV-I) access badges, VA-issued photo badges, credentials for VA facilities and devices, VA-issued laptops, and authentication tokens. Contractors shall notify the appropriate VA COR/CO immediately to initiate access removal. g. Contractors/subcontractors who no longer require VA accesses will return VA-issued property to VA. This property includes (but is not limited to): documents, electronic equipment, keys, and parking passes. PIV and PIV-I access badges shall be returned to the nearest VA PIV Badge Issuance Office. Once they have had access to VA information, information systems, networks and VA property in their possessions removed, contractors shall notify the appropriate VA COR/CO. 8.4 TRAINING: This entire section applies to all acquisitions which include section C.12.3. a. All contractors and subcontractors requiring access to VA information and VA information systems shall successfully complete the following before being granted access to VA information and its systems: (1) VA Privacy and Information Security Awareness and Rules of Behavior course (Talent Management System (TMS) 10176) initially and annually thereafter. (2) Sign and acknowledge (electronically through TMS #10176) understanding of and responsibilities for compliance with the Organizational Rules of Behavior, relating to access to VA information and information systems initially and annually thereafter; and (3) Successfully complete any additional cyber security or privacy training, as required for VA personnel with equivalent information system or information access [to be defined by the VA program official and provided to the VA CO for inclusion in the solicitation document i.e., any role-based information security training]. b. The contractor shall provide the COR/CO with a copy of the training certificates and certification of signing the Organizational Rules of Behavior for each applicable employee within five days of the initiation of the contract and annually thereafter, as required. c. Failure to complete the mandatory annual training is grounds for suspension or termination of all physical or electronic access privileges and removal from work on the contract until such time as the required training is complete. 8.5 SECURITY INCIDENT INVESTIGATION: This entire section applies to all acquisitions requiring any Information Security and Privacy language. a. The contractor, subcontractor, their employees, or business associates shall immediately (within one hour) report suspected security / privacy incidents to the VA OIT s Enterprise Service Desk (ESD) by calling (855) 673-4357 (TTY: 711). The ESD is OIT s 24/7/365 single point of contact for IT-related issues. After reporting to the ESD, the contractor, subcontractor, their employees, or business associates shall, within one hour, provide the COR/CO with the incident number received from the ESD. b. To the extent known by the contractor/subcontractor, the contractor/ subcontractor's notice to VA shall identify the information involved and the circumstances surrounding the incident, including the following: (1) The date and time (or approximation of) the Security Incident occurred. (2) The names of individuals involved (when applicable). (3) The physical and logical (if applicable) location of the incident. (4) Why the Security Incident took place (i.e., catalyst for the failure). (5) The amount of data belonging to VA believed to have been compromised. (6) The remediation measures the contractor is taking to ensure no future incidents of a similar nature. c. After the contractor has provided the initial detailed incident summary to VA, they will continue to provide written updates on any new and relevant circumstances or facts they discover. The contractor, subcontractor, and their employes shall fully cooperate with VA or third-party entity performing an independent risk analysis on behalf of VA. Failure to cooperate may be deemed a material breach and grounds for contract termination. d. VA IT contractors shall follow VA Handbook 6500, Risk Management Framework for VA Information Systems VA Information Security Program, and VA Information Security Knowledge Service guidance for implementing an Incident Response Plan or integrating with an existing VA implementation. e. In instances of theft or break-in or other criminal activity, the contractor/subcontractor must concurrently report the incident to the appropriate law enforcement entity (or entities) of jurisdiction, including the VA OIG, and the VA Office of Security and Law Enforcement. The contractor, its employees, and its subcontractors and their employees shall cooperate with VA and any law enforcement authority responsible for the investigation and prosecution of any possible criminal law violation(s) associated with any incident. The contractor/subcontractor shall cooperate with VA in any civil litigation to recover VA information, obtain monetary or other compensation from a third party for damages arising from any incident, or obtain injunctive relief against any third party arising from, or related to, the incident. f. The contractor shall comply with VA Handbook 6500.2, Management of Breaches Involving Sensitive Personal Information, which establishes the breach management policies and assigns responsibilities for the oversight, management and reporting procedures associated with managing of breaches. g. With respect to unsecured Protected Health Information (PHI), the contractor is deemed to have discovered a data breach when the contractor knew or should have known of breach of such information. When a business associate is part of VHA contract, notification to the covered entity (VHA) shall be made in accordance with the executed BAA. h. If the contractor or any of its agents fails to protect VA sensitive personal information or otherwise engages in conduct which results in a data breach involving any VA sensitive personal information the contractor/subcontractor processes or maintains under the contract; the contractor shall pay liquidated damages to the VA as set forth in clause 852.211-76, Liquidated Damages Reimbursement for Data Breach Costs. 8.6 BAA Standard Language: It has been determined that protected health information (PHI) will be used, disclosed, accessed, transmitted, created, stored/maintained, and/or destroyed (providing appropriate proof of destruction in compliance with VA Directive 6371) by the Contractor, and a signed Business Associate Agreement (BAA) will be required. The Contractor will adhere to the requirements set forth within the BAA, referenced in the solicitation, and will comply with all applicable VA/VHA Directives. Once awarded, Contractor and Contracting Officer will collaborate with the appropriate Facility Privacy Officer: Jareeka R. Graham (614) 257-5626 Jareeka.Graham@va.gov to implement the appropriate BAA. | Special Notice | 541512 | No Set-Aside | 10/07/2026 | 10/13/2026 | - |
Additional Details
Solicitation Number
36C26326Q1000
Archive Date
Oct 24, 2026
Office Address
Saint Paul, MN, 55101