36C26221Q0044 0002 - RFQ Amendment.docx
DOCX document 98 KB Posted
- Attached to
- 7A21--VISN 22 POC Middleware Federal contract opportunity
- Solicitation number
- 36C26221Q0044
View the file
Other files for this federal contract opportunity
Show all 24
On GovTribe
Work with this file on GovTribe
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
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 __________ 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)
None 00262 Department of Veterans Affairs Network Contracting Office 22 4811 Airport Plaza Drive Suite 600 Long Beach CA 90815
00262 Department of Veterans Affairs Network Contracting Office 22 4811 Airport Plaza Drive Suite 600 Long Beach CA 90815 To all Offerors/Bidders
36C26221Q0044 11-03-2020
X
X X
1:00PM PST, 12/11/2020
This Solicitation (RFQ) is hereby amended for the following reasons:
1) Hour and Date for receipt of offers is extended to 1:00PM PST, 12/11/2020.
2) Please see Page 2 for the complete list of vendor questions and answers.
Vendor Questions and Answers
| Key |
| Question |
| Answer |
| 1 |
| Given the upcoming holiday and resources being unavailable, would it be possible to extend the due date of this solicitation to 12/9/2020? |
| Extension will be granted with a new deadline for December 11, 2020 at 1:00PM PST. |
| 2 |
| Does single program point of contact refer to single program point of contact for each participating facilities under VISN22 or One Single Program Point of Contact across all of the 8 participating VA Healthcare system? |
| One Single Primary Program Point of Contact across all participating sites. |
| 3 |
| Does VISN22 plan for single instance of POC data management system (middleware solution) across all of the participating VA Healthcare system/ facilities or multiple instances of POC data management system (middleware solution) to support each of the participating VA Healthcare System/ facilities that are listed under section 1.6? |
| Multiple instances. |
| 4 |
| Is Connectivity intended for any off-site or CBOC (Community Based Out Reach Clinic) within each healthcare system listed above? |
| Yes. |
| 5 |
| Will each healthcare system use their own distinct instance of VISTA LIS (Laboratory Information System)/CPRS ( Computerized Patient Record System). Additionally, are there any shared LIS environments (for e.g. Does VA Greater LA Healthcare system & VA Loma Linda Healthcare system share same LIS environment)? |
| Yes, each facility has their own distinct CPRS, LIS only shared between facility + CBOCs. |
| 6 |
| Will the solution need to receive and process ADT from any Healthcare Information systems implemented at VA? If so, are they sending from a single source or multiple sources. |
| ADT is in use for several sites, currently, but not all. |
| 7 |
| Is VA San Diego Healthcare System uses Clinitek Status or visual Multistik 10SG ? |
| Visual Multistik 10SG. |
| 8 |
| Will all Vista LIS & CPRS environment support HL7 results interfacing? If not, please specify required connectivity method? |
| Yes. |
| 9 |
| Refer 3.3.1, Can you please explain or point to what are the Office of Information and Technology and Information Security directives? |
| Please refer to attached documents: |
- VA Directive 6500
- VA Handbook 6500.6 Appendix A
| 10 |
| Section 3.1.1 refers to the Middleware Hardware and Software solution. Does the scope of the RFP include vendors to quote for Hardware as in Servers, Software as in OS and SQL RDBMS besides the Middleware solution which is the POC Database manager? |
| Yes, each site available hosting resources must be reviewed by site. Facilities are likely to utilize virtual servers, however, pricing for physical servers may be requested. Vendors are required to furnish any hardware and software that are required to run the Middleware solution. |
| 11 |
| Link for 3.3.6.1 does not work, can you please provide the pdf file? |
| Please refer to attached documents: |
- (Insert Company Name) VA LAN Extension MOU 2017.12.11 - TEMPLATE
- (Insert Company Name) VA MOU Appendix A POC List 2017.12.18 - TEMPLATE
- (Insert Company Name) VA MOU ISA Checklist 2017.12.18
- 2020 MOU ISA New Template Brown Bag
- Appendix C Template 2018.08.08
- MOU ISA Annual Review SharePoint User Guide
- MOU ISA Intake Form Instructions
- MOU ISA Review Form-
- VA MOU ISA Approved Final Template-09092020
- OIS MOU ISA SOP Final_20191007
| 12 |
| Under the Attachment A, required licenses Tab, please refer to the column D & E. |
What does the Column D denote i.e., Download location Count, how do we interpret this?
What does Column E denote i.e., Facility comments – Should we include the quantity in this column to the quantity in Column C to calculate the licenses?
Column D and E combined equals the total number of connections needed for each type of instrument/meter. "n/a" equals 1 connection needed.
| 13 |
| The VAs current IT solutions for certain platforms require multiple suppliers' products. Based on our history with the VA, many suppliers' products will provide basic connectivity but not all features/functions that the VA has come to expect. Please provide direction how the VA would like suppliers to respond if multiple supplier products are needed to meet the requirements of the VA. |
| Each individual vendor offer must be complete and meet all requirements outlined in section (viii) 52.212-1, Instructions to Offerors, and 52.212-2, Evaluation, of the solicitation. All offers will be reviewed and treated separately, in which the award will go to a single Awardee. |
| 14 |
| Can/will the VA issue DOs to separate suppliers to provide a complete connectivity solution for a single product line/platform? |
| No, the contract award and corresponding Delivery/Task Orders will be issued to a single Awardee. |
| 15 |
| Is it acceptable for suppliers to provide details in the RFP response which outlines other suppliers' products which are required to provide all of the functionality the VA requires? |
| Yes, this is acceptable. However, each individual vendor offer must be complete and meet all requirements outlined in section (viii) 52.212-1, Instructions to Offerors, and 52.212-2, Evaluation, of the solicitation. All offers will be reviewed and treated separately, in which the award will go to a single Awardee. |
| 16 |
| Please clarify the difference between tabs "Schedule of Pricing" and "Implementation" in Attachment A, as they seem to be requesting similar information. |
| Schedule of Pricing: Vendors are to provide a complete list of contract line items that will be available for order from the IDIQ. This will include prices for potential future addon items and services. |
Implementation: Vendors are to provide a list of line items that will be needed for the initial implementation and annual licensing.
| 17 |
| 36C26221Q0044, 3.1, Completed Enterprise Risk Assessment. See Attachment E – VA_Dir_6550_June_2019.pdf - I’m not finding this attachment. |
| An updated version of the document "36C26221Q0044" has been published on beta.sam.gov. Please see the updated document "RFQ - 36C26221Q0044 v2" that corrects the reference to Attachment C - VA Directive 6550, Appendix A. |
| 18 |
| Attachment+B+-+Middleware+SOW, 3.3.3 - Please provide a copy of VHA Lab POC HL7 Interface Specifications Document as we are unable to open from website |
| Please refer to attached document "lab_52_poc_hl7_spec.docx". |
| 19 |
| 36C26221Q0044, 3.1, Completed Enterprise Risk Assessment. See Attachment E – VA_Dir_6550_June_2019.pdf - This section references Attachment E as VA_Dir_6550_June_2019.pdf, however all other references throughout the Solicitation Notice reference Attachment E as the Past Performance References, not VA_Dir_6550_June_2019.pdf. Can you confirm? |
| An updated version of the document "36C26221Q0044" has been published on beta.sam.gov. Please see the updated document "RFQ - 36C26221Q0044 v2" that corrects the reference to Attachment C - VA Directive 6550, Appendix A. |
| 20 |
| 36C26221Q0044, 52.212-4, CONTRACT TERMS AND CONDITIONS – COMMERCIAL ITEMS (OCT 2018) - Will this Solicitation Notice become the agreement between the parties upon award? Or will there be an opportunity for a version of Contractor’s standard terms and conditions for use of Contractor’s software to be incorporated in addition to the Government’s Contract Terms and Conditions? |
| In general, the contract will be subject to the Government's terms and conditions. |
| 21 |
| Attachment+D+-+VA+Handbook+6500.6+Appendix+C - What is the definition of “VA Information” as used throughout the document? |
| VA information pertains to any data contained in, or acquired from, the VA's information systems. |
| 22 |
| Attachment+D+-+VA+Handbook+6500.6+Appendix+C, 2. b. - Is this applicable? If so, how? |
| Yes, contractors that will be visiting onsite will require background check and PIV cards issued. |
| 23 |
| Attachment+D+-+VA+Handbook+6500.6+Appendix+C, 3. l. - COMPANY does not transmit or store PHI/PI at COMPANY. Remote access to PRODUCT for transferring software for installation and upgrade as well as implementation and support activities. Do we qualify for needing to complete this |
| All contractors require an MOU-ISA, therefore a Contractor Security Control Assessment (CSCA) does not need to be completed. |
| 24 |
| Attachment+D+-+VA+Handbook+6500.6+Appendix+C, 4, c - Is this referencing the build of the system or the build of the application? |
| The system will include both the hardware and software. |
| 25 |
| Attachment+D+-+VA+Handbook+6500.6+Appendix+C, 4, l - What does “all other vulnerabilities” mean? |
| If a new security vulnerability is identified, we would expect cooperation to mitigate risk in a timely manner, as defined in Appendix C, Section 4L. |
| 26 |
| Attachment+D+-+VA+Handbook+6500.6+Appendix+C, 5 - Is this section even applicable if the software is hosted by VISN 22? - Can we verify that all of section 5 is not applicable since the software is customer hosted? Subsection a. starts with scoping of the information system, but the other subsections do not. |
| Section 5 is applicable regardless of where it is hosted. |
| 27 |
| Attachment+D+-+VA+Handbook+6500.6+Appendix+C, 5, c - What does "Self-Certification by the contractor" mean? |
| Upon termination of the contract, contractors must provide written confirmation that data destruction requirements have been met according to Section 3c. |
| 28 |
| Attachment+B+-+Middleware+SOW, 3.1.2 - Please provide a copy of Attachment C – VA Directive 6500 |
| Please refer to "Attachment C - VA Directive 6550" which has already been uploaded to beta.sam.gov. |
| 29 |
| Referring to: 3.1 Completed Enterprise Risk Assessment. Attachment C – VA Directive 6550, Appendix A; we are proposing a software solution that is not an FDA classified medical device. Is this form still applicable? |
| Yes, this form is still required. |
| 30 |
| Does the VA VISN 22 prefer to host the POC Solution within their data center or is the preference to have a vendor hosted solution? |
| Preference would be for the solution to be VA hosted. However, if vendor hosted solution is VA approved, it will be considered. |
| 31 |
| For each of the eight listed locations, are all of the devices at one physical location; or are there multiple addresses associated with each location? If multiple, how many physical locations are there per each site? |
| Devices may be spread out across multiple addresses associated with each location. |
GLA: 10 locations SD: 8 locations LB: 7 locations LL: 8 locations ALB: 7 locations PRES: 7 locations PHX: 9 locations + 1 in Spring of 2022 TUC: 7 locations
| 32 |
| Please identify the number of each device in use at each location. |
| Please refer to document "Attachment A - Schedule", tab "Required Licenses". |
| 33 |
| In Attachment A, Summary by Facility and Summary by Product Type tabs, please confirm meaning of asterisks by some devices. |
| Please disregard asterisks. |
| 34 |
| The link in Attachment B at does not work: 3.3.6.1 https://vaww.portal2.va.gov/sites/infosecurity/FY15CRISPAudit/CRISPRemediationContract/WorkSite/SitePages/MOU-ISA_Version2.aspx. Can you please provide additional guidance regarding the requested documentation describing our approach to receiving an MOU/ISA with the VA? |
| Please refer to attached documents: |
- (Insert Company Name) VA LAN Extension MOU 2017.12.11 - TEMPLATE
- (Insert Company Name) VA MOU Appendix A POC List 2017.12.18 - TEMPLATE
- (Insert Company Name) VA MOU ISA Checklist 2017.12.18
- 2020 MOU ISA New Template Brown Bag
- Appendix C Template 2018.08.08
- MOU ISA Annual Review SharePoint User Guide
- MOU ISA Intake Form Instructions
- MOU ISA Review Form-
- VA MOU ISA Approved Final Template-09092020
- OIS MOU ISA SOP Final_20191007
| 35 |
| Is Section 5.1 of Attachment B regarding installation and implementation provided as information or does it require a response? |
| For instructions on how to complete this requirement please refer to Document "RFQ - 36C26221Q0044 v2", Section viii: 52.212-1 - Instructions to Offerors, Subsections 3. Connectivity and Conformance and 4. Support Features. |
| 36 |
| Attachment B lists the following attachments that are referred to just as they are listed. |
SECTION C
1. ATTACHMENTS AND SUPPORTING DOCUMENTATION
1.1 Attachment A – Schedule
1.2 Attachment B – Middleware SOW (This document)
1.3 Attachment C – VA Directive 6500
1.4 Attachment D – VA Handbook 6500.6 Appendix C
1.5 Attachment E – VA_Dir_6550_June_2019
1.6 Attachment F – Past Performance References
However, the RFQ 36C26221Q0044 document lists the following attachments, which are the ones that are actually included:
See attached document: Attachment A - Schedule.
See attached document: Attachment B - Middleware SOW.
See attached document: Attachment C - VA Directive 6550.
See attached document: Attachment D - VA Handbook 6500.6 Appendix C.
See attached document: Attachment E - Past Performance References.
The list of attachments provided in Section C of Attachment B - Middleware SOW have been corrected with a new document version "Attachment B - Middleware SOW v2" published to beta.sam.gov by way of solicitation amendment. Please see 36C26221Q0044 0001 Amendment for details.
| 37 |
| Attachment E is referred to in the RFQ 36C26221Q0044 in section 3.1 Completed Enterprise Risk Assessment. See Attachment E - VA_Dir_6550_June_2019 but this attachment is not included with the RFQ. Can you please clarify which document we need to use to complete an Enterprise Risk Assessment? |
| With the updated RFQ document "RFQ - 36C26221Q0044 v2", this section has been corrected to state: |
3.1 Completed Enterprise Risk Assessment. See Attachment C – VA Directive 6550, Appendix A.
File details come from the government source that posted it. Updated .