About this file

36C10B19R0014 36C10B19R0014 VDIF Solicitation Questions and Answers- Round 2.docx

View the file

Other files

File Type Posted
36C10B19R0014-029.docx DOCX document
36C10B19R0014-030.docx DOCX document
36C10B19R0014-028.docx DOCX document
36C10B19R0014-027.docx DOCX document
36C10B19R0014-026.docx DOCX document
36C10B19R0014-025.docx DOCX document
36C10B19R0014-024.docx DOCX document
36C10B19R0014-022.docx DOCX document
36C10B19R0014-021.docx DOCX document
36C10B19R0014-014.docx DOCX document
36C10B19R0014-017.xlsx XLSX spreadsheet
36C10B19R0014-018.pdf PDF
36C10B19R0014-020.docx DOCX document
36C10B19R0014-013.docx DOCX document
36C10B19R0014-012.docx DOCX document
36C10B19R0014-011.docx DOCX document
36C10B19R0014-019.docx DOCX document
36C10B19R0014-015.xls XLS spreadsheet
36C10B19R0014-010.docx DOCX document
36C10B19R0014-016.xls XLS spreadsheet
36C10B19R0014-003.docx DOCX document
36C10B19R0014-008.xls XLS spreadsheet
36C10B19R0014-004.docx DOCX document
36C10B19R0014-009.xlsx XLSX spreadsheet
36C10B19R0014-006.docx DOCX document
36C10B19R0014-001.docx DOCX document
36C10B19R0014-005.docx DOCX document
36C10B19R0014-002.docx DOCX document
36C10B19R0014-007.docx DOCX document
36C10B19R0014-000.docx DOCX document
Show all 30

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

36C10B19R0014 VDIF Solicitation- Q&A Round 2

Question No.
Solicitation Section
Question/Comment/Suggestion
VA Response
1.
Vol. V – Veterans Employment
Is it acceptable to submit the spreadsheet (Attachment G) and pdf (Attachment H) as separate files?
Yes

Accordingly, Solicitation Section, 2. PROPOSAL FILES, (c) Content Requirements Table for Volume V has been revised

)2.
Vol. II – Past Performance
Is it acceptable to submit Section 1 as a separate file (.xls) from Section 2 (.pdf)?
Yes.

Accordingly, Solicitation Section, 2. PROPOSAL FILES, (c) Content Requirements Table for Volume II has been revised

3.
Schedule B
CLIN 5001 lists the Units as "EA", with the "EA" equaling a 4-5 FTE Scrum Team for a period of 12 months. Would the government consider changing the Unit to "Month", in order to align with the Unit type and billing cycle of the other CLINs, hence allowing for monthly invoicing as work is performed, as opposed to annual invoicing as currently stated?
No, the unit price for CLIN 5001 shall not be revised; however, the line item has been revised to include clarifying language.

The Government intends upon exercise of the optional scrum team to amortize the scrum team price across a 12-month period which will allows monthly invoicing.

4.
Schedule B
CLINs 0003, 1003, 2003, 3003, and 4003 state that it includes 1 Scrum Team. On page 71, in the PWS Section 5.3 VDIF EP Integration (OEHRM Funded), it indicates that VA anticipates the Base Period to have five scrum teams, Option Period 1 to have four scrum teams, Option Period 2 to have three scrum teams, and Option Periods 3 and 4 to have one scrum team each. Is it the intent of the government that these anticipated scrum teams be priced out in the 0003, 1003, 2003, 3003, and 4003 CLINs assigned for VDIF EP Integration, or that only ONE of the anticipated scrum teams will be priced within those CLINs, with any additional scrum teams being exercised through CLIN 5001?
Only one scrum team (1) is to be priced out in 0003, 1003, 2003, 3003, and 4003 for the VDIF EP Integration. Any additional scrum teams shall be exercised through CLIN 5001.
5.
Solicitation page 142
It states "File sizes shall not exceed 7MB." Can the Government please clarify if this limit refers to the maximum size of our complete response with all attachments, or is it referring to the maximum size of any single attachment (such as, for example, Volume 2)? Given that Volume I has a page limit but Volumes II through VI do not have page limits, we believe that the stated limit is referring to any single attachment and not the maximum size of all attachments together.
The size of all files contained in 1 email shall not exceed 7MB. Offerors may submit multiple emails.
6.
Past Performance
Can prime offerors use Past Performance references where the work was performed as a subcontractor?
No, Prime contracts only. The solicitation states, Offerors shall submit up to five (5) contracts (including Federal, State, and local government and commercial) (prime contracts, and/or task/delivery orders) in performance at any point during the three (3) years immediately prior to the proposal submission date, which are relevant to the efforts required by this solicitation.
7.
Attachment F Price Evaluation spreadsheet CLIN 0003
In PWS 5.3, the government states that “VA anticipates VDIF EP Integration support levels to be as follows:

· Base Period: five agile scrum teams

· Option Period 1: four agile scrum teams

· Option Period 2: two agile scrum teams

· Option Period 3: one agile scrum team

· Option Period 4: one agile scrum team”

In Attachment F, the description for CLIN 0003 reads: “1 Scrum Team for Sustainment Tasks IAW PWS Paragraph 5.3 - VDIF EP Integration….”

Please confirm that Offerors should include only the cost of one scrum team in the pricing for CLIN 0003, as opposed to the five scrum teams that are anticipated per the PWS.

If it is the government’s intent that only one scrum team is to be priced in CLIN X003, please confirm that the government will fund the anticipated additional scrum teams (4 additional in the base) by exercising CLIN X003 multiple times, as opposed to utilizing CLIN 5001.

Yes, only the cost of one scrum team in the pricing for CLIN 0003.

The Government will not be exercising CLIN 0003 multiple times for additional scrum teams.

For additional scrum teams, the Government intends to exercise CLIN 5001 Also see response to Q4.

8.
Attachment F Price Evaluation spreadsheet CLIN 5001
Please confirm that the Prime Contractor may invoice the government monthly for each exercise of CLIN 5001.
Yes, also see response to Q4.
9.
Section B, Pgs. 9,23, 34
Section B: 0002 Base Period - 1 Scrum Team for Sustainment Tasks IAW PWS Paragraph 5.2 - VDIF EP Environment Sustainment inclusive of subparagraph 5.2.1 and 5.2.5. Additionally, Paragraph 5.4 – VIP Agile Process IAW PWS Paragraph 5.4 inclusive of subparagraphs 5.4.1 and 5.4.3

Question: Section B identifies this CLIN at 12 months. Is the government asking us to only bid 1 scrum team for sustainment work? If no, please update Section B for all Base and Optional CLINS related to 0002.

Yes, the Government is requiring a bid price for 1 scrum team for sustainment work in CLIN 0002 and subsequent Option CLINS.

Also see response to Q4.

10.
Section B, Pgs. 11, 23, 28 and 71
Section B: 0003 Base Period - 1 Scrum Team for Sustainment Tasks IAW PWS Paragraph 5.3 - VDIF EP Integration. Additionally, paragraph 5.4 - VIP Agile Process IAW PWS Paragraph 5.4 inclusive of subparagraph 5.4.1 and 5.4.3

Question: Section B identifies this CLIN at 12 months yet on page 71 "VA anticipates VDIF EP Integration Support level to be as follows: Base Period: Five agile scrum teams...." Please update Section B for Base and Optional CLINS related to 0003.

See response to Q7.

11.
Section B, Pgs. 17
Section B: 5001 Optional Task 5.5 – Additional Technical Support IAW PWS paragraph 5.5 inclusive of all subparagraphs 5.5.1, 5.5.2, and 5.5.3. …. EA= cost of 1 scrum team for 4-5 Full Time Equivalents (FTEs) for a 12 month period and associated line items 0004AA through 0004BE.:

Question: Is the Government providing the 4-5 FTE as recommended size of a Scrum Team?" If no, please update Section B.

Yes

12.
PWS Section 5.1.2, Pg. 47
PWS Section 5.1.2 states that “...based on the importance of HealthShare as the HIE...the Contractor shall be required to be a current InterSystems Certified HealthShare implementation partner, whose membership in the program is contingent upon the partner developing and maintaining a high level of InterSystems technology expertise...Furthermore, the Contractor shall maintain the Certified Implementation Partnership throughout the periods of performance.”

Question: Please verify whether the prime contractor or a team member must be a member of the “InterSystems Certified HealthShare implementation partner program”. If the prime contractor must be a member of the “InterSystems Certified HealthShare implementation partner program”, please explain the rationale for that requirement, particularly since this is a new Solicitation requirement that was not specified in any of the previously issued Solicitation-related documentation and is also a brand new (less than 45-days) certification program.

A. The Prime must be a partner;

B. The InterSystems Certified HealthShare implementation partner is a requirement;

C. This is a requirement based on the importance of HealthShare as the Health Information Exchange.

The HealthShare Certification is key to performance as the sustainment and application integration requirements are dependent on the use of the HealthShare platform.

13.
PWS Section 5.2.1, Pg. 55
PWS Section 5.2.1 describes the eventual deployment of VDIF-EP to “AWS VA Enterprise Cloud (VAEC)” and requires that the contractor support this environment.

Question: The PWS, however, does not provide sufficient technical information to enable prospective offerors to accurately respond to the Solicitation (e.g., ticket volumes, nature of tickets, peak load volumes, etc.). Please provide the technical information that supports successful VDIF-EP operation and as a DR/failover environment in AITC.

The PWS has provided technical requirements; however, the requirement is for scrum teams that will perform the sustainment and application integration tasks as prioritized by the VA.

14.
PWS Section 5.2.1, Pg. 55
Question: PWS Section 5.2.1 does not provide sufficient technical information to enable potential offerors to understand how to maintain or sustain VDIF-EP as deployed in the AWS VAEC. Additionally, PWS Section 5.2.1 does not provide sufficient technical information to inform offerors why AZC (Azure) VAEC cannot also be considered an equivalent. Please provide the technical rationale that supports the successful operation of VDIF-EP in the AWS VAEC
The program has already been analyzed by the VA and the determination was made to deploy the VDIF-EP in the AWS VA Enterprise Cloud. No further rationale will be provided.
15.
Volume II – Past Performance
"Offerors shall submit up to five (5) contracts (including Federal, State and local government and commercial) (prime contracts, and/or task/delivery orders) in performance at any point during the three years immediately prior to the proposal submission date, which are relevant to the efforts required by this solicitation. Areas of relevance include enterprise level tier 2 and 3/4 sustainment of VDIF EP Core Components hosted on the HealthShare/HealthConnect application suite and/or VDIF EP Core Components integration with Cerner suite of application."

Question: Please clarify how a non T4NG Prime would have VA specific tier 2 and 3/4 sustainment of VDIF EP Core Components hosted on Health Share/HealthConnect? This was released on FBO under a small business set aside yet the relevancy of past performance is specific to a contract vehicle that has awarded most task orders for VDIF core components (table 1 page 53-54).

The VDIF EP Core Components is not VA specific; therefore, not T4NG specific.

Volume II, Past Performance includes commercial instances.

16.
Volume II – Past Performance
"Offerors shall submit up to five (5) contracts (including Federal, State and local government and commercial) (prime contracts, and/or task/delivery orders) in performance at any point during the three years immediately prior to the proposal submission date, which are relevant to the efforts required by this solicitation. Areas of relevance include enterprise level tier 2 and 3/4 sustainment of VDIF EP Core Components hosted on the Health Share/HealthConnect application suite and/or VDIF EP Core Components integration with Cerner suite of application." - Then in the first round of Q&A during the RFI the Government responded "“Offeror” refers to the proposed prime contractor, only. The Past Performance evaluation or its proposal submission instructions does not include major subcontractors."

Question: Since the government released this as a Small Business set aside, and the scope is complex, please explain why the government is only requesting Prime contractor past performance when evaluating risk and capability knowing that no one Small Business will be able to complete the scope of work successfully without a team?

To clarify, the solicitation is not restricting teaming (subcontracts) but merely not defining a “major” subcontractor.

A major subcontractor has not been defined as the solicitation requires the Offeror (Prime) to provide an InterSystems Certified HealthShare implementation partner certification number and verification the certification is current.

This is a Prime requirement based on the importance of HealthShare as the Health Information Exchange; and the Prime bears the obligation to perform the work whereby a subcontractor has no contractual obligation to the Government.

Further, the HealthShare Certification is key to performance as the sustainment and application integration requirements are dependent on the use of the HealthShare platform.

17.
General
Question: It is our understanding that the philosophy that the VA adopted when VAEC was awarded was that vendors were free to pick either AWS or Azure as part of their solution but had to provide their rationale and an estimate of the required Cloud credits within their response. Is that understanding accurate, and if so, why has that philosophy changed since that time?
In this requirement, the program has already been analyzed by the VA and the determination was made to deploy the VDIF-EP in the AWS VA Enterprise Cloud.
18.
General
Question: It is respectfully requested that the Solicitation closing date be extended until 30 April 2019 to enable the VA to publish its answers to the offerors’ questions, the offerors to make the necessary adjustments to their proposals and, more importantly, to enable prospective Small Business offerors to gain the required InterSystems Certified HealthShare implementation certification.
An extension to April 30, 2019 will not be granted.

Any delays in the award of this effort will increase the risk of meeting the target Enterprise Health Record Modernization Initial Operating Capability date of March 2020.

Additionally,the Government released a draft solicitation

19.
General
Question: As of the time of market research (24-Dec-2018) and solicitation (15 March 2019), there has been no publicly available information on the InterSystems website regarding the InterSystems Certified HealthShare implementation partner program, and it is our understanding that there are only a limited number of Small Businesses that currently have the required certification. Accordingly, it is respectfully requested that the Government determine to which potential offerors InterSystems has made this program known and offered the required certification.
The Government has verified that the InterSystems Certified HealthShare implementation certification is available to vendors who meet the eligibility requirements.

It is incumbent upon potential Offerors to further research information for obtaining the certification.

20.
General
Question: To ensure a “level playing field” for this acquisition, it is respectfully requested that the Government determine whether InterSystems has limited or prioritized access to this program to certain potential offerors and withheld the ability to achieve the required certification from others.
See Q19.

File details come from the government source that posted it.