Amendment 2 75H70122R00003.pdf
PDF 189 KB Posted
- Attached to
- Software Based Medical Device Support Federal contract opportunity
- Solicitation number
- 75H70122R00003
About this file
This document is an amendment to a request for proposal for software-based medical device support services issued by the Indian Health Service. The amendment provides responses to prospective offerors' questions to clarify requirements. The services include decision support, research, standardization of medical terminology, aggregation of device recalls and alerts, and other information management tasks outlined in the statement of work. The response due date is 15 November 2021 by 2:00 PM Pacific Time and proposals should be emailed to matthew.phelps@ihs.gov. The page limit for technical factors was increased from 45 to 60 pages total based on increased limits of 15 pages for technical approach and key personnel descriptions. Clarification was also provided that past performance questionnaires and CPARS records may both be included under the past performance factor.
View the file
Other files for this federal contract opportunity
| File | Type | Posted |
|---|---|---|
| Amendment 5 75H70122R00003.pdf | ||
| B05 Amendment 4 75H70122R00003.pdf | ||
| Amendment 3 75H70122R00003.pdf | ||
| Amendment 1 75H70122R00003.pdf | ||
| RFP Attachment 1 QASP Medical Device Support.docx | DOCX document | |
| RFP Attachment 2 - PPQ.docx | DOCX document | |
| 75H70122R00003 RFP Software Based Medical Support.pdf |
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
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:
(a) By completing items 8 and 15, and returning 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 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.
E. IMPORTANT: Contractor is not is required to sign this document and return copies to the issuing office.
AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT 1. CONTRACT ID CODE
2. AMENDMENT/MODIFICATION NUMBER 3. EFFECTIVE DATE 4. REQUISITION/PURCHASE REQUISITION NUMBER 5. PROJECT NUMBER (If applicable)
7. ADMINISTERED BY (If other than Item 6) CODE
STANDARD FORM 30 (REV. 11/2016)
Prescribed by GSA FAR (48 CFR) 53.243
FACILITY CODE
9A. AMENDMENT OF SOLICITATION NUMBER
9B. DATED (SEE ITEM 11)
10A. MODIFICATION OF CONTRACT/ORDER NUMBER
10B. DATED (SEE ITEM 13)
11. THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS
The above numbered solicitation is amended as set forth in Item 14. The hour and date specified for receipt of Offers is extended. is not extended.
12. ACCOUNTING AND APPROPRIATION DATA (If required) copies of the amendment; (b) By acknowledging receipt of this amendment on each copy of the offer submitted;
13. THIS ITEM APPLIES ONLY TO MODIFICATIONS OF CONTRACTS/ORDERS.
IT MODIFIES THE CONTRACT/ORDER NUMBER AS DESCRIBED IN ITEM 14.
CHECK ONE A. THIS CHANGE ORDER IS ISSUED PURSUANT TO: (Specify authority) THE CHANGES SET FORTH IN ITEM 14 ARE MADE IN THE CONTRACT ORDER
NUMBER IN ITEM 10A.
B. THE ABOVE NUMBERED CONTRACT/ORDER IS MODIFIED TO REFLECT THE ADMINISTRATIVE CHANGES (such as changes in paying office, appropriation data, etc.) SET FORTH IN ITEM 14, PURSUANT TO THE AUTHORITY OF FAR 43.103(b).
C. THIS SUPPLEMENTAL AGREEMENT IS ENTERED INTO PURSUANT TO AUTHORITY OF:
D. OTHER (Specify type of modification and authority)
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.
15C. DATE SIGNED
15A. NAME AND TITLE OF SIGNER (Type or print)
16C. DATE SIGNED
16A. NAME AND TITLE OF CONTRACTING OFFICER (Type or print)
14. DESCRIPTION OF AMENDMENT/MODIFICATION (Organized by UCF section headings, including solicitation/contract subject matter where feasible.)
PAGE OF PAGES
6. ISSUED BY CODE
8. NAME AND ADDRESS OF CONTRACTOR (Number, street, county, State and ZIP Code) (X)
CODE
15B. CONTRACTOR/OFFEROR
(Signature of person authorized to sign)
16B. UNITED STATES OF AMERICA
(Signature of Contracting Officer)
Previous edition unusable
A0002
The purpose of this amendment is to answer pre-proposal inquiries.
Please page 2 for responses.
Indian Health Service – Division of Engineering Services 701 Fifth Avenue, Suite 1650 Seattle, WA 98104
SEE BLOCK 6.
75H70122R00003
1 4
11/04/2021
10/12/2021
75H70122R00003 – Software Based Medical Device Support Amendment 02
Here are Government responses to pre-proposal inquiries:
18. Section L.2.1 - 2 Page 39 - We acknowledge that the Government is not counting the table of contents, past performance questionnaires, or resumes, will the Government also allow a cover page and acronym/abbreviation listing in the proposal that does not count against page count in the proposal, volumes 1 and 2?
Response: Yes, that is allowable.
19. Section L.2.1 - 2 Page 39 - Can the Government please confirm if a printed copy of the proposal package is required?
Response: A printed copy of the proposal is not required. Proposals are sent by email only per the instructions.
20. Section L.2.1 - 2 Page 39 - We acknowledge the Government would like all proposal text 12pt Font and double spaced, we are respectfully requesting that the Government allow 10pt font for any tables and graphics, and that tables and graphics do not need to be double spaced, will the Government allow this change to font size and spacing in only tables and graphics?
Response: Yes, that is allowable.
21. Section L.2.1 - 2 Page 39 - Can the government please provide an explanation as to why the page limit is a total of 45 pages for the technical volume, we are asking this because the Technical Proposal is limited to 10 pages, key personnel/management approach is limited to 10 pages, and relevant past performance is limited to 10 pages this totals 30 pages in all excluding items that are not counted in page count per the solicitation. Will the Government please utilize the additional 15 pages, increasing the total page count for Factor 1 Technical from 10 to 15 total pages and Factor 2 key personnel/management approach from 10 to 15 pages?
Response: That is a mistake on the part of the Government. The page limit for the technical volume is still 45 pages total. The page limit per factor can be increased as described in the question to not exceed 45 pages.
22. Section C, 3.1, p.9 - Does the new system need to track new/ replacement orders?
Response: This solicitation is not for the acquisition of medical equipment or medical device software. It is to support decision making, research, standardization (terminology), aggregate recall/alerts, and information specified in the SOW.
23. Section L.2.2 - 3 Page 41 and 42 - Can the Government please explain the statement projects submitted under Factor 1 (Technical Capability) and for Factor 1, Experience. In Factor 1 solicitation instructions is does not mention in any of the 9 elements providing projects or experience information, there is no Factor 1 Experience.
We are respectfully requesting that the government allow the insertion of projects or experience information (i.e. past performance references) in the proposal package under factor 3 past performance, as this would allow all bidders to utilize the 10 page max provided in that section excluding past performance questionnaires. The past performance questionnaires would then be provided based off the past performance references that the bidder submits in factor 3. Would this solution be within compliance and amenable to the Government?
Response: Factor 1 is Technical Capability. Factor 3 Relevant Past Performance can include both Past Performance Questionnaires (PPQs) and information pulled from https://www.cpars.gov. A description of experience is included in the PPQ and will be evaluated under Factor 3.
24. Section L.2.2 - 3 Page 42- Can the Government confirm that all completed (fully filled out and signed by applicable COR/KO) past performance questionnaires are required in the proposal package under factor 3 past https://www.cpars.gov/ performance? Should these past performance questionnaires also be sent from the applicable COR/KO directly to Mr. Matthew Phelps via email?
Response: PPQs that are part of the offeror’s proposal should be included with their technical proposal or submitted directly to matthew.phelps@ihs.gov.
25. Section G.3 Page 11- Is there a particular system/website IHS needs us to upload our invoices to in addition to sending to the CO and COR?
Response: More information will be provided or updated with the awarded contract. The current instructions state to submit the invoice electronically to the CO and the COR.
26. Section I.4 Page 20- Are bidders to price out the six months or is the 6-month being held at year-five price?
Response: The purpose of this clause is to ensure that the Government has continuity of services for an additional six months if the follow on requirement is not awarded within the initial timeframe. It is anticipated that the cost of the six month extension would mirror the rates found in the final option period price.
27. Section 1.4.2 and 1.4.3 Page 6 - How many devices are in the current inventory? Would IHS be willing to publish a small sample inventory of its medical devices?
Response: This solicitation is not for the acquisition of inventorying software or a Computerized Maintenance Management System (CMMS). It is to support decision making, research, standardization (terminology), aggregate recall/alerts, and information specified in the PWS.
28. Section B Page 2- No travel CLIN was listed. Do we need to consider any travel requirements?
Response: There is no travel anticipated for this requirement.
29. Section C, 1.4.2 and 1.4.3 Page 6- How many unique manufacturers/models are in the inventory?
Response: This solicitation is not for the acquisition of inventorying software. It is to support decision making, research, standardization (terminology), aggregate recall/alerts, and information specified in the PWS.
30. Section C, 1.4.2 and 1.4.3 Page 6- How frequently does IHS perform physical inventories?
Response: This solicitation is not for the acquisition of inventorying software. It is to support decision making, research, standardization (terminology), aggregate recall/alerts, and information specified in the
PWS.
31. Section C, 1.4.2 and 1.4.3 Page 6 - How many medical devices are considered for purchase and purchased annually?
Response: This requirement is not for the purchase of medical devices.
32. Section C 1.4.2 and 1.4.3 Page 6 - What is your monthly count for new devices onboarded throughout the enterprise?
Response: This solicitation is not for the acquisition of inventorying software. It is to support decision making, research, standardization (terminology), aggregate recall/alerts, and information specified in the PWS.
33. Section C, 1.4.2 and 1.4.3 Page 6 - What is the expectation for frequency of periodic data standardization/normalization efforts within your CMMS?
Response: The frequency of periodic data standardization has not been determined.
34. Section C, Part 3/3.2 Page 9 - With regards to the current CMMS in use, does IHS have a system administrator that will be involved in this project? If so, how will the successful offeror engage them?
Response: IHS has a CMMS administrator that will be involved in this project once a successful offeror is selected.
mailto:matthew.phelps@ihs.gov
35. Section C, Part 3/3.2 Page 9 - Are there test and development environments in which we can do the development required for 3.2? Will user licenses and accounts be provisioned to successful offeror’s technical resources by IHS?
Response: IHS is not responsible for providing test and development environments.
36. Section C, 1.4.2 and 1.4.3 Page 6 - Can the Government confirm if OC Security needs to be added to the Medical Devices?
Response: The Government is not sure what “OC Security” is referencing. But this project is not for the procurement of any medical devices.
| B05 SF30 Amendment 2 |
| B05 Amendment 2 Pg 2 |
File details come from the government source that posted it. Updated .