About this file

This is an Amendment 0001 to Request for Information (RFI) 36C10B27Q0056, issued by the Department of Veterans Affairs Office of Procurement Operations Technology Acquisition Center on November 19, 2026. The amendment posts answers to questions received regarding the RFI and incorporates a revised Performance Work Statement (PWS). The RFI seeks sources to provide full lifecycle sustainment and operational support, bug/fix development, and regulatory compliance services for the Veterans Health Administration's VBECS (Blood Establishment Computer Software), an FDA-regulated Class II Medical Device Software product. Contractors must plan, manage, develop bug fixes, test, deploy, maintain, document, and continuously monitor the system throughout the DevOps lifecycle while maintaining compliance with FDA Quality System Regulations (21 CFR 820), ISO 13485:2016, and VA cybersecurity and privacy requirements.

Key qualification requirements established through the Q&A include: all assigned personnel must have a minimum of five years' experience in FDA-regulated medical device, healthcare technology, laboratory information system, blood bank information system, or similarly regulated environments; at least two staff members must be HL-7 Standard Certified (minimum version 2.5); and blood bank operations experience applies to every team member. Respondents must propose a staffing approach identifying primary positions, responsibilities, relevant experience, required certifications, and availability at award, along with a Rough Order of Magnitude (ROM) for the base period and each option period. The 15-page limitation applies to the entire RFI response, including all technical, regulatory, staffing, and company information. The PWS incorporates a new Section 5.8 addressing VBECS Ramp Up, which details transition requirements and knowledge transfer provisions. The Government will determine the appropriate acquisition strategy based on RFI responses, and if a set-aside is issued, applicable clauses will be included; key personnel will not be evaluated or designated as such.

View the file

Other files

File Type Posted
36C10B27Q0142 0001.docx DOCX document
P02 MR RFI PWS Revised Amend 0001.docx DOCX document
36C10B27Q0142.docx DOCX document
P02 MR RFI PWS.docx DOCX document
P02 RFI.docx DOCX document

On GovTribe

Work with this file

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

Text version

Request for Information 36C10B27Q0056 Amendment 0001

Contract NNG15SD38B Order 36C10A23F0033 Modification P00001

5. PROJECT NUMBER (if applicable)

CODE

7. ADMINISTERED BY

2. AMENDMENT/MODIFICATION NUMBER

CODE

6. ISSUED BY

8. NAME AND ADDRESS OF CONTRACTOR

4. REQUISITION/PURCHASE REQ. NUMBER

3. EFFECTIVE DATE

9A. AMENDMENT OF SOLICITATION NUMBER

9B. DATED

PAGE OF PAGES

10A. MODIFICATION OF CONTRACT/ORDER NUMBER

10B. DATED

BPA NO.

1. CONTRACT ID CODE

FACILITY CODE

CODE

Offers must acknowledge receipt of this amendment prior to the hour and date specified in the solicitation or as amended, by one of the following methods:

The above numbered solicitation is amended as set forth in Item 14. The hour and date specified for receipt of Offers

E. IMPORTANT:

is extended,

(a) By completing Items 8 and 15, and returning __1________ copies of the amendment; (b) By acknowledging receipt of this amendment on each copy of the offer submitted; or (c) By separate letter or electronic communication which includes a reference to the solicitation and amendment numbers. FAILURE OF YOUR ACKNOWLEDGMENT TO BE RECEIVED AT THE PLACE DESIGNATED FOR THE RECEIPT OF OFFERS PRIOR TO THE HOUR AND DATE SPECIFIED MAY is not extended.

12. ACCOUNTING AND APPROPRIATION DATA

(REV. 11/2016)

is required to sign this document and return ___________ copies to the issuing office.

is not, A. THIS CHANGE ORDER IS ISSUED PURSUANT TO: (Specify authority) THE CHANGES SET FORTH IN ITEM 14 ARE MADE IN THE CONTRACT ORDER NO. IN ITEM 10A.

15C. DATE SIGNED

B. THE ABOVE NUMBERED CONTRACT/ORDER IS MODIFIED TO REFLECT THE ADMINISTRATIVE CHANGES SET FORTH IN ITEM 14, PURSUANT TO THE AUTHORITY OF FAR 43.103(b).

RESULT IN REJECTION OF YOUR OFFER. If by virtue of this amendment you desire to change an offer already submitted, such change may be made by letter or electronic communication, provided each letter or electronic communication makes reference to the solicitation and this amendment, and is received prior to the opening hour and date specified.

C. THIS SUPPLEMENTAL AGREEMENT IS ENTERED INTO PURSUANT TO AUTHORITY OF:

D. OTHER

Contractor

16C. DATE SIGNED

14. DESCRIPTION OF AMENDMENT/MODIFICATION

16B. UNITED STATES OF AMERICA

Except as provided herein, all terms and conditions of the document referenced in Item 9A or 10A, as heretofore changed, remains unchanged and in full force and effect.

15A. NAME AND TITLE OF SIGNER

16A. NAME AND TITLE OF CONTRACTING OFFICER

15B. CONTRACTOR/OFFEROR

STANDARD FORM 30

PREVIOUS EDITION NOT USABLE

Prescribed by GSA - FAR (48 CFR) 53.243 (Type or print) (Type or print) (Organized by UCF section headings, including solicitation/contract subject matter where feasible.)

(Number, street, county, State and ZIP Code) (If other than Item 6) (Specify type of modification and authority) (such as changes in paying office, appropriation date, etc.)

(If required)

(SEE ITEM 11)

(SEE ITEM 13)

(X)

CHECK

ONE

13. THIS ITEM APPLIES ONLY TO MODIFICATIONS OF CONTRACTS/ORDERS,

IT MODIFIES THE CONTRACT/ORDER NO. AS DESCRIBED IN ITEM 14.

11. THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT

(Signature of person authorized to sign) (Signature of Contracting Officer)

November 19, 2026

Department of Veterans Affairs Office of Procurement Operations Technology Acquisition Center 23 Christopher Way Eatontown, NJ 07724

Department of Veterans Affairs Office of Procurement Operations Technology Acquisition Center 23 Christopher Way Eatontown, NJ 07724

To All Offerors/Bidders

4TBM6

36C10B27Q0056

11-12-2026

X

The purpose of this amendment is to post the answers to questions received regarding this request for information and incorporate a revised Performance Work Statement.

See Continuation Pages

Diana B. Armesto Contracting Officer

November 19, 2026

CONTINUATION PAGES

Question: (RFI Section 3.c, third bullet – Rough Order of Magnitude) – The RFI asks respondents to show, for each task, the primary positions, their responsibilities, experience, certifications and availability at award, but it does not ask for dollar figures. Could the Government please confirm whether the Rough Order of Magnitude should include estimated costs (for example, labor hours and a total estimate per task for the base period and each option period), or only the staffing approach described in the bullet?

Answer: The Government requested a Staffing Approach that includes the respondents labor categories to ensure that the Government’s requirement was understood by the respondent and in line with industry standards. The Government also requested a Rough Order of Magnitude (ROM) for all periods of performance to ensure the respondent understood the overall magnitude.

Question: (PWS Section 4.4 – Contractor Personnel and Section 6.6 – Government Furnished Property) – The draft PWS does not state the number of contractor staff, and Section 6.6 estimates 18 laptops. To prepare the Rough Order of Magnitude by task, could the Government please share the current number of contractor staff supporting VBECS by labor category, or confirm whether the 18 laptops reflect the expected team size?

Answer: The Government does not equate the Government Furnished Equipment (GFE) estimate in the Performance Work Statement (PWS) with team size. PWS Section 6.6 states that the Government will furnish desktops or laptops only when necessary, and will be limited to personnel needing direct network access. Respondents should propose the team size and labor mix necessary to meet the requirements of the PWS and should be transparent about any assumptions.

Question: (PWS Section 4.4 – Contractor Personnel, first paragraph) – The draft PWS states that all individuals assigned, including subcontractors, must demonstrate experience in Blood Bank operations. Could the Government please confirm whether this applies to every team member (including system administrators, developers and cybersecurity staff), or only to the key positions and the quality and regulatory roles?

Answer: Demonstrating experience in blood bank operations applies to every member of the team in accordance with PWS Section 4.4.

Question: (PWS Section 4.4 – Key positions table, Section 5.1.2 A.4 and Section 5.2) – The key positions table lists one HL7 SME with HL7 certification, Section 5.1.2 A.4 requires at least two staff members to be HL7 Standard Certified (minimum version 2.6), and Section 5.2 lists HL7 versions 2.3 to 2.5. Could the Government please confirm how many staff must hold an HL7 certification, and which HL7 certification and version is required?

Answer: At least two staff members must be HL-7 Standard Certified, with a minimum standard version of 2.5.

The Government agrees that there were inconsistencies in the PWS regarding the standard minimum version of the HL-7 certification. See the attached revised PWS.

Question: Relevant Past Performance: May a prospective prime contractor demonstrate the required five-year regulated healthcare or FDA medical-device software experience through committed subcontractors or named key personnel? What supporting documentation would VA consider sufficient?

Answer: All individuals assigned to the requirement shall have a minimum of five (5) years of experience performing duties comparable to those assigned under this Task Order within an FDA-regulated medical device, healthcare technology, laboratory information system, blood bank information system, or similarly regulated environment. The responses received to the RFI will assist the Government in determining the necessary supporting documentation. See the attached revised PWS.

Question: Personnel Qualifications: Does the Section 4.4 blood bank and regulated-system experience requirement apply to all assigned personnel, including infrastructure, cybersecurity, DevSecOps, and project management personnel, or only to positions directly responsible for regulated software and patient-safety activities?

Answer: All individuals assigned to the requirement shall have a minimum of five (5) years of experience performing duties comparable to those assigned under this Task Order within an FDA-regulated medical device, healthcare technology, laboratory information system, blood bank information system, or similarly regulated environment. The responses received to the RFI will assist the Government in determining the necessary supporting documentation. See the attached revised PWS.

Question: HL7 Certifications: Can VA clarify the minimum required number of HL7-certified specialists, acceptable certification standards, and the point at which certification evidence must be provided?

Answer: At least two staff members must be HL-7 Standard Certified, with a minimum standard version of 2.5.

The Government acknowledges that there were inconsistencies in the PWS regarding the standard minimum version of the HL-7 certification. See the attached revised PWS.

Timing: PWS Section 5.1.2 requires the Contractor to provide clear identification and verification of at least two staff members being HL-7 Standard Certified (minimum standard version of 2.5) in the Monthly Progress Report. The initial Monthly Progress Report is due within 20 calendar days of the start of performance, then monthly. For the RFI response, respondents could recommend how and when the certifications will be in place.

Question: Staffing at Award: Which key positions and VBECS-specific technical qualifications must be available immediately at award, and which positions, if any, may be staffed during transition?

Answer: See the attached revised PWS that incorporates PWS Section 5.8 VBECS Ramp Up.

Question: Contingent Personnel and Teaming: May respondents include contingent employees and committed subcontractors in their proposed staffing approach? Are resumes and letters of intent required, and do such attachments count toward the 15-page limitation?

Answer: The 15-page limitation is an RFI submission instruction, and attachments count toward this limitation. The PWS does not prohibit contingent employees or subcontractors.

Question: Acquisition Strategy: Does VA anticipate a small-business or veteran-owned small-business set-aside, and will any subsequent solicitation specify applicable subcontracting limitations and key-personnel commitment requirements?

Answer: Based on responses to the RFI, the Government will determine the appropriate acquisition strategy. If the Government issues a solicitation as a set-aside, the Government will include clauses for limitations on subcontracting. Key Personnel will not be evaluated or designated.

Question: Rough Order of Magnitude: Does VA require estimated FTEs, labor costs, or both for the base and option periods? Would a role-based staffing and availability matrix satisfy the current market research requirement?

Answer: The Government requested a Staffing Approach that includes the respondents labor categories to ensure that the Government’s requirement was understood by the respondent and in line with industry standards. The Government also requested a ROM for all periods of performance to ensure the respondent understood the overall magnitude.

A role-based staffing and availability matrix would be acceptable so long as it demonstrates the Respondent’s approach for each task, including identifying the primary positions, their assigned responsibilities, relevant VBECS or comparable regulated-system experience, required certifications, and availability at award for the base period and each option period. Respondents may add estimated FTEs, but it is not required.

Question: The RFI lists NAICS 541519 with a 150-employee size standard, which applies to the IT Value-Added Reseller exception. Since the Draft PWS covers services only, would VA consider 541512 or 541511 ($34.0M)?

Answer: The RFI requests that if a respondent feels that a different North American Industry Classification System (NAICS) code would be a better fit, that respondents should recommend alternative NAICS codes as part of their responses including a rationale for the NAICS code recommendation for the Government’s consideration.

Question: Will VA fund a knowledge-transfer overlap with the incumbent, given that the PWS states VA will provide no training?

Question: PWS Section 5.6, Optional Task 1 - This section states that OT 1 can be executed once per BY/OY and gives a specific number of currently planned sites for migration. What would occur if the site number was changed, i.e., CY 2027 changes from the expected 21, either higher or lower, and how would the VA like to see this section priced in the proposal? As a total for each individual PoP, or would a cost per site be preferred?

Answer: The schedule is subject to change at the direction of VA leadership. The Contractor shall provide a complete VBECS data extract up to 26 blood bank database sites that include five extracts each. Per the RFI, this section is to be firm-fixed-priced for the base and each option period, for a total of five instances.

Question: RFI Section 3.b, page 3 - The RFI requests a “brief summary of capabilities” not to exceed 15 pages and subsequently identifies specific information and technical questions for respondents to address. Please clarify whether the 15-page limitation applies to the entire RFI response, including responses to all requested technical, regulatory, staffing/ROM, and company information, or only to the “brief summary of capabilities.” If the 15-page limit does not apply to the entire response, please identify the applicable page limitations for each section (i.e., Narrative, Experience, ROM).

Answer: The 15-page limit applies to the entire response.

Question: PWS Section 4.4, Contractor Personnel - Corporate Past Performance vs. Employee Medical Device Experience: Would the Government consider a company eligible and competitive for contract award if the company possesses demonstrated corporate past performance in Continuous Integration/Continuous Delivery (CI/CD), DevSecOps, software configuration management, cybersecurity engineering, and enterprise application sustainment, but does not possess direct corporate past performance supporting FDA-regulated medical devices, provided its proposed key personnel have verifiable professional experience supporting FDA-regulated medical device systems, blood bank applications, or comparable healthcare environments, including FDA and ISO 13485:2016 compliance? Additionally, will the Government consider the qualifications and documented prior experience of proposed personnel separately from corporate past performance when evaluating technical capability and award eligibility?

Answer: As stated in the RFI, responses will be treated only as information for the Government to consider when developing its acquisition strategy.

Question: PWS Sections 5.2 and 5.2.1, Software Sustainment Support and Use of Microsoft Azure/Jira/GitHub - Technical Experience and Regulatory Specialization: Would the Government consider a technical staffing approach that combines experienced enterprise DevSecOps, CI/CD, cloud engineering, cybersecurity, and configuration management professionals with dedicated FDA medical device regulatory and ISO 13485:2016 subject matter experts, provided the proposed team collectively satisfies the PWS requirements? Alternatively, must every proposed technical resource independently possess the minimum five years of regulated medical device or comparable healthcare software experience specified in Section 4.4?

Answer: All individuals assigned to the requirement shall have a minimum of five (5) years of experience performing duties comparable to those assigned under this Task Order within an FDA-regulated medical device, healthcare technology, laboratory information system, blood bank information system, or similarly regulated environment. The responses received to the RFI will assist the Government in determining the necessary supporting documentation. See the attached revised PWS.

Question: PWS Sections 4.4 and 5.2, Contractor Personnel and Software Sustainment Support - Incumbent Knowledge Transfer and Transition Requirements: For prospective offerors that possess the required software engineering, cybersecurity, and regulatory qualifications but have not previously supported the VBECS application, will the Government provide an incumbent-to-successor transition period, access to existing system architecture documentation, configuration baselines, software repositories, and approved operating procedures to facilitate knowledge transfer? If so, what transition duration and Government-furnished technical resources should offerors anticipate when developing their staffing, implementation, and firm-fixed-price proposals?

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