Questions_and_Answers_RFP_19-236-SOL-00012_Amd0002.docx
DOCX document 38 KB Posted
- Attached to
- Health Information Technology Systems & Support (HITSS) Interoperability Platform & Application Support Services Federal contract opportunity
- Solicitation number
- 19-236-SOL-00012
About this file
Questions and Answers_Amendment0002
View the file
Other files for this federal contract opportunity
| File | Type | Posted |
|---|---|---|
| eRx_Expanded_DeployDiag_v20190328_Legacy.pdf | ||
| bepr020u.local.pdf | ||
| bepr020t.local.pdf | ||
| sf30_Amendment0002.pdf | ||
| eRx_Expanded_DeployDiag_v20190328_Network.pdf | ||
| ePrescribing_2_0_Software_Design_Document_v1_0_FINAL.pdf | ||
| Additional_Terms_and_Conditions_Amendment_0002.doc | DOC document | |
| SF30_19-236-SOL-00012_Amd0001.pdf | ||
| Additional_Terms_and_Conditions.doc | DOC document |
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
Q&A
| Solicitation Page # |
| Section Title |
| Question |
Answers
| 1 |
| 2 |
| B.2 Contract Pricing |
| The Labor Categories listed in B.2 and described in Part 6 (“Labor Categories / Roles and Responsibilities) are, with one exception, all senior resources. We would anticipate that the required O&M tasks could also be supported with staff possessing less experience with oversight from the senior resources. In addition, Optional Tasks 5.0.7 and 5.0.8 (“Innovation Work” and “Transition and Innovation Operationalization Work” respectively) account for different type of work, e.g., these efforts tend to be more strategic and business centered than the current O&M related tasks that CLINs/Labor Categories would allow. As such, please confirm that, following contract award, additional CLINs and Labor Categories will be incorporated into the contract through amendments or other change control mechanisms. |
| It’s not anticipated additional CLINS or labor categories will be incorporated. |
| 2 |
| 2 |
| B.2 Contract Pricing |
| The Labor Categories described in Part 6 (“Labor Categories / Roles and Responsibilities) include a Security Architect, but there are no CLINs included with a labor category of Security Architect. Please confirm whether or not a Security Architect labor category is needed in the tables of Section B.2 and how it will be included (e.g., base year, optional years, optional CLINs, etc.). |
| A Security Architect is needed for new or enhanced development of products. It should be included as optional labor. |
| 3 |
| 10 |
| 1.1 Description of Services/ Introduction |
| Please confirm that IHS will support all required secure connections between contractor’s sites and the facilities to be supported under this contract (e.g., VPN, secure webservices, etc.). |
| IHS will provide VPN access and facilitate access to federal/tribal/urban sites. |
| 4 |
| 15 |
| 3.1 Licenses, Products, and Equipment |
The RFP states that the “Contractor shall be responsible for providing all hardware, software, and software licenses required”. Please provide the following clarifications:
1. Since this is a labor-hour contract, please confirm that the contractor will be reimbursed for provision of hardware, software, software licenses, and other materials.
1. What existing software licenses are currently in use for O&M services? Specifically, for: Source Version Control, IT Service Management (e.g., Jira), Source Code Propagation, Software Deployment, Testing, Defect Management, System Monitoring, Data Obfuscation Tools, etc.
1. Does IHS have licenses that will be made available to the selected contractor? If so, for which software?
1. The government will pay associated licensed software, for Intersystems Healthshare, Server based SQL, associated with supported software products under this contract. All client software is the responsibility of Offeror. 2. The government holds licenses for production and testing environments for:
Healthshare 2017 Microsoft VSTS
3. Licenses will be made available for:
Healthshare
VSTS
SQL
PlanView
| 5 |
| 16 |
| 4.1 General |
| The RFP states that the “Contractor shall furnish all supplies, equipment, facilities and services required”. Since this is a labor-hour contract, please confirm that the contractor will be reimbursed for provision of supplies, equipment, facilities, and non-personnel services (e.g., third party certification costs, third party inspection costs, third party security and privacy controls validation, etc.). |
| Contractor’s labor rates must consider the mentioned costs. |
| 6 |
| 20 |
| 5.4.3 Agile Portfolio Management |
| Agile Portfolio Management: |
Does IHS plan to procure new tools in support of Agile Portfolio Management?
IHS has purchased PlanView and uses VSTS in tandem.
| 7 |
| 23 |
| 5.8 Testing |
| The requirement states, “The Contractor shall work collaboratively with other Contractors to support integration testing, alpha testing, and beta testing. The Contractor shall be responsible for ensuring compliance with the published integration, alpha, and beta testing schedules. The Contractor shall also coordinate with the respective product owners during all testing activities. The Contractor shall ensure that program, project, and executive leaders always have a situational awareness of the user acceptance level of their respective products. |
(a) Please clarify how many and what specific other contractors the Offeror/Contractor will be required to work with to support the various types of testing? Will the Offeror/Contractor be responsible for maintaining an overall testing environment for all of these products to be integrated and tested together?
(b) Is the Offeror/Contractor required to provide situational awareness on all products or only “their” (the Offeror’s delivered products) products?
a.) The following contract companies are incumbent contractors supporting HITSS projects:
General Dynamics Information Technology, Integrated Government Solutions, Respec. Integrated Testing environments are maintained by government or other contractors outside of this RFP. Modular development/testing environments will be maintained by all respective contractors.
b.)The Offeror/Contractor is required to provide situational awareness on only the products maintained under the contract.
| 8 |
| 23 |
| 5.9 Implementation and Deployment Support |
| What support is expected for ‘open source community coordination’? And does it entail any level of deployment support or post-deployment support? |
| No support is expected from the open source community or is contract required to support the open source community. |
| 9 |
| 25 |
| 5.15 Project Documentation Support |
| (a) Are there any existing project documentation tools the contractor will be required to use in support of this task? |
(b) Will the contractor have the ability to implement changes to existing tools?
a.) All documentation shall be submitted using Microsoft Word or provided by government.
b.) No changes to existing tools are anticipated.
| 10 |
| 34 |
| Section E – Inspection and Acceptance |
| For QASP item #1 (Customer Service): |
1. What is the source from which the Contractor will receive stakeholder requests?
2. How will the Contractor receive stakeholder requests?
3. Please confirm that the measure of one business day is initiated when the Contractor receives the request per the agreed reporting tool (i.e., not email).
4. Please confirm that the estimated resolution time notification may exceed 48 hours if agreed by the parties.
5. Please clarify whether the Contractor will have direct contact with the Interoperability Platform users or whether another contractor will be receiving customer calls via a call center operated outside if this contract.
1. Stakeholder request are submitted via the Office of Information Technology Helpdesk ticketing system.
2. Tickets are triaged by helpdesk and sent via written message to assigned contract teams.
3. The measure begins at the time the ticket is sent to contractor.
4. There are instances where resolution time may exceed 48 hours but those should be few. Where there are delays, COR or Federal project lead must be notified.
5. Calls will be received via IHS helpdesk and routed to Offer. Upon receipt there may be a need to have direct contact with users.
| 11 |
| 34 |
| Section E – Inspection and Acceptance |
| For QASP item #2 (Quarterly Software Builds): |
1. Please confirm that the Agency will work with Contractor to define a release testing process that includes user acceptance testing responsibilities for IHS.
2. Please confirm that the Agency will work with Contractor to define a release process that incorporates prioritization, testing and defect severities, and overall governance process jointly run by Contractor and Agency.
1. IHS will work with Offeror to discuss established release processes as well as work with Offerors on release testing responsibilities.
2. IHS will work with Offeror to define established release processes that incorporate prioritization, testing and defect severities, and overall governance process.
| 12 |
| 35 |
| Section E – Inspection and Acceptance |
| For QASP item #3 (Deliverable Schedule): |
Please confirm the following deliverable approval process will be used during the life of the contract or that such a process will be agreed prior to final contract signature:
1. The COR will provide deliverable approvals within 10 days of receipt of the deliverable.
2. Alternatively, if COR deems the deliverable not approved, then, within 10 business days of receipt of deliverable, the COR will provide written comments describing defects and associated resolution items.
3. Contractor will provide the revised deliverable within 5 business days of receipt of COR written comments.
4. COR will have 5 business days to approve the revised deliverable or provide written comments exclusively on the corrections made by Contractor in the second submission of the deliverable.
Section E item 3 remains as written in the RFP.
| 13 |
| 36 |
| Section E – Inspection and Acceptance |
| For QASP item #6 (Customer Satisfaction for Software Products): |
1. Since the RFP does not include a clear definition of how which customers will be included in the rating process nor a definition of the rating criteria, please confirm that this customer satisfaction rating process will be defined and agreed between parties during contract initiation.
Customer for Software Products satisfaction rating process will be defined and agreed between parties during contract initiation but is largely dependent on project scope.
| 14 |
| 36 |
| Section E – Inspection and Acceptance |
| For QASP item #7 (Customer Satisfaction for Problem Report Handling): |
1. Since the RFP does not include a clear definition of how which customers will be included in the rating process nor a definition of the rating criteria, please confirm that this customer satisfaction rating process will be defined and agreed between parties during contract initiation.
Customer Satisfaction for Problem Report Handling will be defined and agreed between parties during contract initiation.
| 15 |
| 36 |
| Section E – Inspection and Acceptance |
| For QASP item #8 (Customer Satisfaction for Training): |
1. Since the RFP does not include a clear definition of how which customers will be included in the rating process nor a definition of the rating criteria, please confirm that this customer satisfaction rating process will be defined and agreed between parties during contract initiation.
Customer Satisfaction for Training will be defined and agreed between parties during contract initiation.
| 16 |
| 37 |
| Section E – Inspection and Acceptance |
| For QASP item #9 (Tested Users Completion of Ten 10 User Tasks): |
1. Who selects the tested users?
2. How are the tested users confirmed to have the prerequisite skills to use the functionality associated with the tasks?
3. How are the “top ten user tasks” selected? Using what criteria? By who?
4. Please confirm that this performance measure rating and process will be defined and agreed between parties during contract initiation
1. The agency as an established testing process and identifies individuals and sites.
2. Testers and Users are federal, tribal and urban personnel who have participated in the requirements elicitation processes and regularly perform operations with the associated software functionality desired.
3. The top ten user tasks are selected by Federal personnel and dependent on importance and priority to the agency.
4. Additional conversation on this metric (tested users complete the top ten user tasks) will be further discussed and agreed upon during contract initiation.
| 17 |
| 38 |
| F.3 Hours of Operation |
| 1. Since this O&M contract is supporting clinical systems, are there exceptions to provision of the Contractor not working during Government facility is closed due to local or national emergencies, administrative closures, or similar closings (e.g., Federal government shutdown)? |
2. For 24/7/365 after-hour coverage for emergency situations, what is the definition and/or criteria for “emergency situations”?
1. Contractors are anticipated to work during government closures if funding supports activity. All other emergencies would require CO approval. See details referring to federal holidays.
2. Examples of emergency situations include such situations as: IT systems are not operational, database corruption, fail over solutions are unavailable. Any situation that prevents operations or endangers operations and data supported under this RFP.
| 18 |
| 38 |
| F.4 Place of Performance |
| The solicitation states “The work to be performed under this contract will be performed at the Contractor’s site.” Are there any permanent Government site seats available for Contractor and Subcontractor personnel? |
| 1. All work shall be performed at contractors’ site. |
| 19 |
| 41 |
| Deliverable #21 |
| Please provide definition and explanation of the Program and Project Kanban Boards. |
| 1. Kanban boards are used to provide the work or workflow visualization. IHS uses these at a Program level for all HIT development efforts as well as for phases of an individual project. The Program level Kanban is maintained by the HITSS Program office. Project Kanban are managed by the project development team. |
| 20 |
| 43 |
| Phase In/Phase Out Period |
| 1. Please describe the incumbent contractor’s responsibilities during the Phase Out Period of their contract. |
2. Please describe the Agency’s responsibilities during the Phase In/Phase Out Period.
1. The incumbent contractor will provide information on established support processes (e.g., patching, backups etc.) and explanation on system architecture and products as well as documentation and transition any work in process.
2. The agency will ensure all technical materials, access and information is made available to the awardee, introduce appropriate Federal Staff and introduce established processes associated with software development and release management.
| 21 |
| 75 |
| I.12 HHSAR 352.239-74 Electronic and Information Technology Accessibility (DEC 2015) |
| Item (c) for Section 508 compliance does not include a description of the applicable Section 508 standards that apply to this contract. Please provide. |
| Offerors are to identify the applicable 508 standards and approach. |
| 22 |
| 78 |
| Element 3. Operations and Maintenance (O&M) |
| The RFP states that “The Offeror shall provide a documented Integrated Master Plan (IMP) that details required routine maintenance tasks with cadence to meet system operations and management requirements for each of the task areas 5.01 - 5.06 of the PWS.” |
1. Given the 25-page limit for the entire Technical Response, can the government please confirm if it is acceptable for the Offeror to describe the process by which and IMP is created and give examples of maintenance tasks to be performed? This approach will allow for coordination with government leads following contract award and result in a more comprehensive and tailored IMP with events, accomplishments, and criteria for all PWS 5.0 and 5.1 tasks.
1. Can the government please specify preferred format for the IMP as part of the proposal response (i.e., embedded picture or editable table, MS Project)?
1. Would the government consider including the IMP as an appendix that is outside the defined page limitations?
1. Yes descriptions at a high level are acceptable.
2. The IMP should be developed in a format that best depicts the offerors high level understanding of the work outlined in the RFP.
3. IMP should be articulated within the primary proposal and the page limit will be increased by three (3) pages.
| 23 |
| 78 |
| L.1.1 Technical Capability Element 2: Executive Technical Summary |
| “The submission shall include a clear delineation of technology or methodology that will be utilized to support the original PWS tasks and how these will benefit the agencies as a result.” |
1. Please confirm that the “original PWS tasks” are 5.2 – 5.20.
1. The “original PWS tasks” are 5.2 – 5.20.
| 24 |
| 79 |
| Element 4 HITSS Central Services Innovation |
| 2. Please confirm that the Government is expecting a RFP response for this Element that describes, at a summary level (given the 25 page limit), how the Contractor will develop architecture model, identify technologies, and data model for upgrading the legacy eRX software. |
3. Does the Government anticipate that “eRX enhancement” means development of new code within the eRX solution, or does it mean the replacement of eRX with an industry provide COTS solution?
2. The government is expecting summary level detail.
3. This is development of new code.
| 25 |
| 26&27 |
| PWS 5.18.2 |
| The subject PWS section references Earned Value Management (EVM) and Contractor Performance Reporting (CPR). Given the relatively small size and labor-hours nature of the contract, would the Government consider removing EVM and CPR requirements from the PWS? |
| Because this work ties to the larger Health Information Technology Investment EVM and CPR are required for reporting to HHS. No it will not be removed. |
| Contract Pricing |
| Will the Government consider adding optional labor categories during PoP based on tasks assigned? |
| At this time no additional labor categories are anticipated. |
| 27 |
| L.1.1 – Element 3 – Page 78 |
| Task 5.0 Operations and Maintenance (PWS) |
| Is the Integrated Master Plan included or excluded from the 25-page limit for the Technical Proposal? |
| Included and three (3) additional pages added. |
| 28 |
| B.2 – Pages 2 through 9 |
| Contract Pricing |
| Does IHS expect all 8 non-optional CLINs / labor categories to be full-time resources? If no, please provide an expected labor mix. |
| Yes all non-optional labor categories are anticipated to be full time resources. |
| 29 |
| B.2 – Pages 2 through 9 |
| Contract Pricing |
| Are optional CLINs / labor categories expected to be full-time resources? |
| No. Optional labor will be used for specific short term projects as additional resources as requested by government. |
| 30 |
| B.2 – Pages 2 through 9 |
| Contract Pricing |
| Please clarify how many optional and non-optional personnel are supporting IHS today for this contract work. |
| The incumbent has approximately eight non-optional staff supporting base activities. Optional labor is distinct individuals used only as requested by the government. Non optional labor is not used to fulfill optional labor task under any circumstance. |
| 31 |
| B.2 – Pages 2 through 9 |
| Contract Pricing |
| In each of the 8 functional areas, how many personnel are currently on contract? |
| Existing incumbent resources total eight personnel for the base work. |
| 32 |
| 2 |
| B.2. Contract Pricing |
| CLIN numbering for the Base Year and Option Years, Base Labor and Optional Labor is the same (0001, 0002, 0003, etc.). |
Does IHS intend to revise the CLIN numbering at award so it varies across option years and labor type (base vs. optional labor?)
Yes – numbering will be revised as appropriate.
| 33 |
| 11, 31 |
| 1.3.d. General Information – Objectives, Section C, Part 6: Labor Categories/ Roles and Responsibilities |
| Objective 1.3.d states that software security architectural services are part of this effort and the Labor Category “Security Architect” is included in Section C, Part 6. This labor category is not included within Section B.2 Schedule of Prices. |
Will IHS please clarify if Security Architect should be added to Section B.2 Schedule of Prices?
Security Architect services will be required and should be included in schedule of prices under optional labor, via contractor proposed labor category.
| 34 |
| 11 |
| 1.4 Scope -Task Areas |
| Task Areas G and H are listed as Optional Tasks, but do not align cleanly with optional tasks 5.19 and 5.20 on page 27. |
Will IHS clarify the titles of the optional tasks?
Task Areas G and H are Tasks that may/may not be undertaken. These tasks will be invoked at the discretion of the government and applicable to applications covered under this RFP as optional tasks. Additional Optional Labor will fulfill these tasks as need.
| 35 |
| 12 |
| 1.6.1 Quality Control |
| Section 1.6.1 states that the “Quality Control Plan (QCP) shall be digitally submitted to the Contracting Officer (CO) and Contracting Officer’s Representative (COR) within ten (10) calendar days of the start date of the contract…” while the deliverable table in Section F.5 on page 40 states it is due two months after contract start. |
Will IHS please clarify the due date of the QCP and the QASP?
The plan shall be submitted two months after award.
| 36 |
| 20 |
| 5.4 Program Management Support, 5.4.1 Program Planning |
| The solicitation states “this task includes the staffing of an Agile Program Management Office (PMO) that is capable of integrating Agile and waterfall projects into an integrated and published product roadmap.” |
With the staffing levels indicated in B.2 Contract Pricing (page 2), does IHS expect the contractor to staff a PMO?
Instantiation of an Agile PMO will not be required on the contract. The contractor will provide staff such as Project Mangers, Business Analyst to support agile development work within established agency PMO processes and procedures.
| 37 |
| 25 |
| 5.13 SME Support |
| The RFP requests SME support, but no SME role is specified as part of the base or optional work. |
Will IHS add this role to the RFP? Or is it expected that proposed personnel will fulfill this need?
Anticipated SME support is expected from Clinical Informaticist whom are familiar with best practice methods of health care delivery goals and objectives of interoperability products within the EHR/EMR and health care setting. Two position are identified in optional labor section and will be used as needed for limited durations.
| 38 |
| 25 |
| 5.16 Software Development Life Cycle (SDLC) Tools |
| Will IHS provide software licenses for VSTS, PlanView, etc? |
| Yes, IHS will manage the licensing around VSTS, PlanView etc, |
| 39 |
| 27 |
| 5.19 Application Re-Engineering And Centralized Development (Supports OPTIONAL TASK Area) |
| Will IHS please clarify what is meant in the heading by “Supports Optional Task Area”? Is 5.19 an optional task or is it part of the base work? |
| Task areas 19 and 20 will only be performed at the direction of the government. |
| 40 |
| 28 |
| Section C, Part 6: Labor Categories/ Roles and Responsibilities |
| There is no labor category listed for an Application Developer Journeyman, although that labor category is listed in the optional work labor categories for each contract year starting on page 3. |
Will IHS provide a labor description for the Application Developer Journeyman role?
Labor Description: Functioning as a software developer focused on the development of applications, SOA infrastructure, COTS/GOTS integration, interfaces and web services with an Ensemble environment.
Researching and developing critical applications to include HIT interoperability enabled applications.
Writing system documentation, provide input to end-user documentation Supporting software and system integration testing for developed applications.
Required Skills:
Bachelor’s Degree is required; BS Computer Science, Electronics Engineering or other Engineering or Technical discipline is desired 2 to 3 Years’ experience with Ensemble, Java, SQL, XML, Hibernate. HL7.
Service Oriented Architecture knowledge and Experience with agile software development practices (unit testing, and continuous integration).
Ability to easily adapt to new technologies and skillsets Excellent written and verbal communication skills and candidate must be customer service oriented Highly motivated team player who performs well in a team-oriented environment
| 41 |
| 55 |
| H.8. Security Requirements for Government Owned/Contractor Operated (GOCO) and Contractor Owned/Contractor Operated (COCO) Resources |
Does IHS anticipate establishing a direct WAN connection with the contractor facility to provide IHS Network connectivity to contractor systems or will contractors VPN into the IHS network utilizing an IHS supplied VPN client? If contractors will VPN into the IHS network, will an Authority to Operate (ATO) still be required or will an Interconnectivity Security Agreement (ISA) be utilized instead?
If an ATO is required and there is no direct IHS network connection, will a quarterly Independent Assessment be required for individual endpoint devices utilizing the IHS supplied VPN client? Will the scope of the ATO extend beyond those individual endpoints?
No WAN connection will be established. All work will be conducted on the IHS VPN virtual desktop solution. No agreements are anticipated.
| 42 |
| 61 |
| H.9.A.3 Data Jurisdiction |
| “The contractor shall store all information within the security authorization boundary, data at rest or data backup, within the continental United States (CONUS).” |
Due to this requirement, will IHS confirm that all personnel are required to be located CONUS?
Yes all personnel are required to be located in CONUS.
| 43 |
| 61 |
| H.9 FedRAMP Privacy and Security Requirements |
| Will IHS confirm that this clause would only pertain if the offeror were providing a cloud solution? |
| This clause applies to cloud solutions only. |
| 44 |
| 78 |
| L.1.1 Technical Capability, Element 1. Corporate Resume |
| Sections L.1.1 instructs Offerors to provide three (3) detailed corporate experience narratives and an additional two relevant experience narratives for each of the proposed subcontractors. |
Will IHS please allow additional page count for subcontractor narratives as this significantly increases the amount of corporate experience references required and impairs our ability provide an adequate response to the remaining technical elements?
The page limit is increased by three (3) pages.
| 45 |
| 80 |
| L.1.2 Management Approach/ Key Personnel |
| The solicitation states, “each resume shall be limited to three (4) pages…” |
Will IHS please clarify if resume page count is limited to three pages or four pages?
Three (3) pages
| 46 |
| General |
| NA |
| 1. The current contract for the equivalent services as described in this RFP is not expected to conclude until September 2021. Will that contract be terminated early, or will both the new Contractor and the legacy contractor provide services to the Government concurrently? |
If the new Contractor and the legacy contractor are to provide services to the Government concurrently, how will responsibilities and contractual obligations be assigned to each contractor while maintaining independence across contractual and delivery responsibilities?
The current contract for services described in this RFP is currently provided under a bridge contract with the incumbent. The bridge order will expire within two months of the award resulting from this RFP.
| 47 |
| 1 |
| Cover page |
| Given that the answers to questions and the information shared about the current eRX system may significantly impact the content of the technical and cost proposals, we request that the due date of the proposal be extended to May 3rd or two weeks after issuance of answers, whichever is later. |
| The new due date is changed to April 15, 2019, noon Eastern. |
| 48 |
| 2 |
| B.2 Contracting Pricing |
| The Schedule of Prices tables provided in this section include “TOTAL CEILING AMOUNT”. Since there are several optional tasks for innovation and modernization which is scope of work not yet determined, please confirm that a ceiling amount would not be determined based on these CLINs. In addition, please confirm that the pricing being requested is solely for evaluation purpose and that no funding limitations will be determined based on the selected vendor’s Cost Proposal. |
| Contract Total Ceiling Amount is to be identified in each table for both Base and Optional Labors under the schedule of prices. |
| 49 |
| 77 |
| L.1 Content of the Technical Proposal |
| Please confirm that graphics and tables contained in the response may use other font sizes/types (e.g., Arial – 8). |
| This is allowed. |
| 50 |
| 78 |
| L.1.1 Technical Capability |
| Under Element 1, the RFP asks for a significant amount of contract information about experience. Given the 25 page limit for the Technical Response, and the need to use the prescribe font type and size, we request that the requested contract narratives be excluded from the page count limit so IHS will be able to receive more complete answers in other sections of the Technical Response. |
| The page limit has been increased to 28 pages and the narrative must be included with the technical response. |
| 51 |
| 78 / 80 |
| L.1.1 Technical Capability Element 1: Corporate Resume and L.1.3 Relevant Past Performance |
| Given a limited page count (25) within Technology Capability Section, the requirements include 3 detailed corporate experiences for the prime, and 2 detailed corporate experiences for each proposed subcontractor. In addition, providing detailed responses for Elements 2-6 requirements. |
Would the government please consider moving the Corporate Resume detailed component for each prime and subcontract to the L.1.3 Relevant Past Performance section (10 pages) or provide the detailed corporate experiences (prime and subcontractors) into an Appendix similar to the resumes?
The page limit has been increased to 28 pages and corporate resume must be included with the technical capability response.
| 52 |
| 80 |
| L1.3 Relevant Past Performance |
| Element 1 requests that Past Performance Questionnaires be returned by Bidders’ past/current clients by April 12th. This is a very quick response due date for clients who are focused on their organization’s mission. We request that the Government accept and evaluate Past Performance Questionnaires that are returned to the Government after the due date. |
| Due date is updated to April 15th, noon Eastern. |
| 53 |
| 81 |
| L.1.4 Price |
| The RFP states: “For evaluation purpose, the following equation with government designated quantities will be used to arrive at each proposal’s total overall price. The total ceiling price for each period includes the pricing for the optional labor.” |
1. Please confirm that the pricing being requested is solely for evaluation purpose and that no funding limitations will be determined based on the selected vendor’s Cost Proposal.
Please clarify whether “total ceiling price for each period…” means that the total contract value is being determined using the Schedule of Prices defined in section B.2 Contract Pricing section.
Awardee’s total proposal evaluation price represents the contract ceiling price. The total ceiling price for each period includes the pricing for both base & optional labor.
| 54 |
| 81 |
| L.3 Minimum Acceptance Period |
| Given the Proposal Section Template described in L.4, where does the Government want Bidders to document their Minimum Acceptance Period response? |
| With the price proposal. |
| 55 |
| 83 |
| Section M – Evaluation Factors for Award |
| The RFP states that “The Government will award a hybrid contract”. Please describe what the Government means by a “hybrid contract”? |
| This is a labor hour contract. Correction has been made on the RFP. |
| 56 |
| 80 |
| L.1.3 Relevant Past Performance |
| “Offerors are required to provide the evidences and detailed corporate experience narratives for three (3) contracts performed in the past or currently in process for the relevant services to what is being solicited under this solicitation. Also, information shall be submitted for at least two relevant experience for each of the proposed subcontractor.” |
Please confirm that the Prime is to provide detailed corporate experience narratives for 3 contracts and 3 questionnaires; and for each proposed subcontract provide 2 detailed corporate experience narratives and submit 1 questionnaire.
Yes, Prime is to provide detailed corporate experience narratives for 3 contracts and 3 questionnaires; and for each proposed subcontract provide 2 detailed corporate experience narratives and submit 1 questionnaire.
| 57 |
| I.6 – Page 70 |
| HHSAR 352.223-71 Instructions to Offerors – Sustainable Acquisition (Dec 2015) |
| Is the Sustainable Acquisition Plan included or excluded from the 25-page limit for the Technical Proposal? |
| This can be submitted as an Appendix. |
| 58 |
| L.1.2 – Page 79 |
| Management Approach / Key Personnel |
| Section L.1.2 states: “Each resume shall be limited to three (4) pages…” Please clarify whether resumes are limited to 3 or 4 pages. |
| Three (3) pages. |
| 59 |
| K – Page 76 |
| Representations, Certification, and Other Statements of Bidders |
| Please clarify in which volume we are to include the Reps and Certs (paragraph [b]). |
| This can be submitted as an Appendix. |
| 60 |
| 69-70 |
| Section I – Contract Clauses |
| There is no reference to include FAR 52.229-4, Federal, State, and Local Taxes in this section. |
Will IHS please include this clause within the contract?
No, contracting officers are to insert the clause at 52.229-3, Federal, State, and Local Taxes, in solicitations and contracts if—
(1) The contract is to be performed wholly or partly in the United States or its outlying areas;
(2) A fixed-price contract is contemplated; and
(3) The contract is expected to exceed the simplified acquisition threshold.
This RFP is to award a labor hour contract, and also, 52.229-4 is for noncompetitive awards.
| 61 |
| 70 |
| I. 6 HHSAR 352.223-71 Instructions to Offerors - Sustainable Acquisition (Dec 2015) |
| Section I.6 states that Offerors must include a Sustainable Acquisition Plan in their technical proposals, however Section L does not mention the plan. For this contract there are no products that will be purchased on behalf of the government and for Services; we will not be providing any services where this clause would apply. |
Please confirm that Offerors indeed must provide a Sustainable Acquisition Plan and if so, please clarify where the plan should be located in the proposal as well as dedicated page count.
This can be submitted as an appendix and the offeror is to determine the applicability of the clause to their potential contract performance.
| 62 |
| 76, 81 |
| K.1 52.212-3 -- Offeror Representations and Certifications -- Commercial Items (Oct 2018); L.3 Minimum Acceptance Period |
| The solicitation includes several sections, such as K.1 and L.3, which require the Offeror to submit information. However, there is no page count allocated to this information. |
Will IHS please clarify where in the proposal submission package these items should be included and adjust page count accordingly?
Representations and Certifications can be submitted as an appendix and the minimum acceptance period can be submitted with the price proposal.
| 63 |
| 77 |
| L.1 Content of the Technical Proposal |
| The solicitation states the “font size to be used for the proposal shall be no smaller than Times New Roman – 11.” |
Will IHS allow for the font size of tables and graphics to be 10 point instead of 11 point?
Allowed
Can the Govt clarify if this is a new opportunity or if there an incumbent currently preforming on the contract. If there is an incumbent, can the government provide the name and contract number of the incumbent?
The incumbent is General Dynamics Information Technology. The incumbent’s original contract number is GS35F4357D/IND12PD00750.
We are a staff scheduling/workforce management software company, headquartered in Rockville, MD. Is there an element of the RFP that might apply to us? Can you explain exactly what services and products are being sought in the above solicitation?
In general, the RFP identifies a need for software development and support services. Please refer to the RFP to determine if your company can meet the requirements outlined in the RFP.
1. Whether companies from Outside USA can apply for this?
(like,from India or Canada)
All work must be performed in the USA. The proposal shall reference applicable regulation, law and/or approval for the award eligibility if the offeror is from outside the USA.
2. Whether we need to come over there for meetings?
There will be meetings held requiring travel to Rockville, Albuquerque or other sites.
3. Can we perform the tasks (related to RFP) outside USA?
(like, from India or Canada)
All work must be performed in the USA. The proposal shall reference applicable regulation, law and/or approval for the award eligibility if the offeror is from outside the USA.
4. Can we submit the proposals via email?
Best Regards!
Offeror’s are authorized to email their proposals by the established due date. Proposals received after the established due date may be considered unacceptable and rejected.
| 70 |
| General |
| NA |
| The file containing the RFP is called “Additional_Terms_and_Conditions”. This would imply that the RFP consists of additional documents. Can you please make available? |
| All applicable files are included in the FBO posting. |
| During intro you mentioned the scope of the contract being only the centralized services, is that correct? |
| Yes |
| Can you share diagrams of the system flow you described? |
| Yes |
| Can you expand on what "validation" occurs with the XML file before it's transmitted to the pharmacy? |
| Validation includes review of required fields specified by Surescripts requirements. |
| Is there a strategy to support emerging FHIR (Fast Helathcare Interoperability Resources) standard? |
| None planned at this time. |
| Is this contract still set aside for Small Indian Firms? |
| Yes |
| So no work is required to be done on the local Ensemble as part of this contract? |
| No work is required on local health facility Ensemble instances. |
| The diagrams will also be published when ready, is that correct? |
| Yes |
File details come from the government source that posted it.