ORPHEUS_S-44300-00017134_submitted questions and answers.docx
DOCX document 17 KB Posted
- Solicitation number
- S-44300-00017991
- Issued by
- Oregon
About this file
This document contains submitted questions and answers regarding an Oregon state Request for Proposal (RFP S-44300-00017134) for ongoing maintenance, enhancement, modernization, and support of the Oregon Public Health Epidemiology User System (ORPHEUS). The State is seeking contractor services to support and improve the existing ORPHEUS application rather than develop a new software solution. Proposers must submit work samples from two relevant projects, including project name and description, with optional supporting documentation demonstrating experience in automation, interoperability, or public health practice. The proposal requirements reference the Scope of Work detailed in Section 2.4 of the RFP, and clarification was provided that references to non-existent section numbers in the original RFP should direct bidders to review the applicable subsections under Section 2.4 and the broader overview in Section 4.10.2.4.
Pricing must be submitted using Attachment E, the generic price proposal form, with costs structured as hourly rates for proposed roles such as developers and project managers, accompanied by estimated hours for each work category. The State does not require a single total cost estimate for the entire contract period. Attachment E may contain line items not applicable to this RFP, such as Equipment and Installation and Manufacturer Discounts, and proposers should modify the template as needed to reflect services specific to ORPHEUS maintenance, enhancement, modernization, and support. Attachment A was clarified as informational only and does not require inclusion in formal proposals.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| 6228-17134_Att B.docx | DOCX document | |
| 6228-17134_Att E.docx | DOCX document | |
| 6228-17134_Att D.docx | DOCX document | |
| 6228-17134_Att F.docx | DOCX document | |
| 6228-17134_ORPHEUS_Att A.pdf | ||
| 6228-17134_RFP - OHA_ORPHEUS.pdf | ||
| 6228-17134_Att C.docx | DOCX document | |
| 6228-17134_Att G.docx | DOCX document | |
| Notice of Intent to Award_6228.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
Submitted Questions (Numbers) and Answered (Letters) Hello, We would like to submit a few questions we have about the RFP for Orpheus Support and Maintenance (Number S-44300-00017134), primarily with regard to several of the items in section 3.3 (Proposal Requirements) and Attachment E (Price Proposal Form):
1. Section 3.3.2 refers to “the proposed Solution, its distinctive features, and how it will fulfill the State’s requirements”. Just to be clear, does this mean our “solution" for the ongoing maintenance, enhancement, modernization, and support of the Oregon Public Health Epidemiology User System (Orpheus), as opposed to a specific software solution?
0. Section 3.3.2 refers to the proposer’s solution for providing ongoing maintenance, enhancement, modernization, and support for the existing ORPHEUS application. The State is not seeking a new software solution. Proposers should describe their approach to supporting and improving the current ORPHEUS system.
1. Section 3.3.4 requires work samples for 2 projects. Will a Project Name and description be sufficient as a work sample, or is additional documentation and/or screenshots required?
1. For Section 3.3.4, a Project Name and project description are required. Additional documentation or screenshots are not required, but proposers may include details that demonstrate relevance to this RFP, such as past work involving automation, interoperability, or public health practice.
1. Section 3.3.7 refers to “requirements set forth in section 2.4.1" and "Attachment H”, neither of which seem to exist in the current RFP. Can you clarify what these should refer to?
2. Apologies for the confusion created here. For this section, please review the language in Section 2.4 Scope of Work/Specifications. Where a sub-section of 2.4 is listed please review
1. Similarly, section 3.3.8 refers to "the information provided in Section 2.4.2, Scope of Services and the Tasks and Deliverables described therein”, but there isn’t a section labeled 2.4.2 in the current RFP.
3. Same as above, as the general Scope of Services is covered in the sub-sections under Section 2.4, with a broader overview (sans the 2.4.2 reference) in Section 4.10.2.4.
1. Attachment E - It appears that many parts of this attachment do not apply to this RFP. Is this correct? (e.g. "Equipment and Installation" and "Manufacturer Discounts" don’t appear to be applicable)
4. Attachment E is a generic template, please update the Attachment (adding/removing items as needed) to fit your needs.
1. Attachment E - Since the Scope of Work in Section 2.4 is defined as "ongoing maintenance, enhancement, modernization, and support of … ORPHEUS”, it would seem that almost the entirety of costs for this RFP would be listed in Part 5. Are the Costs expected to be listed as an hourly rate for (daily/weekly/monthly) services? Or is it expected to be a total cost estimate for the duration of the contract (e.g. monthly cost x 24 months)?
5. Correct — the response should reflect the costs associated with ongoing maintenance, enhancement, modernization, and support for ORPHEUS. Costs should be provided as hourly rates for the roles proposed (e.g., developer, project manager), along with the proposer’s estimated hours for each category of work. The State is not requesting a single total cost for the full contract period. Proposers should use the template in Attachment E to the extent possible, even though its categories may not perfectly align with the work buckets described in the RFP.
1. Just to be clear, it appears that Attachment A is just for informational purposes, and does not need to be included in the proposal. Is this correct?
6. That is correct.
Thank you!
File details come from the government source that posted it. Updated .