Additional Response to Offeror Questions document.docx
DOCX document 24 KB Posted
- Attached to
- Slate CRM Software Implementation
- Solicitation number
- 24RFP-USD08052024
- Issued by
- Clay County, South Dakota
About this file
This document is an Additional Response to Offeror Questions related to the Slate CRM Software Implementation RFP #USD08052024 for the University of South Dakota (USD). The RFP seeks to implement a new CRM software solution to replace the existing Salesforce system. Key details include:
The RFP covers requirements such as specific response formatting, providing a scoring matrix chart, integrating with the existing Banner student information system, importing legacy Salesforce data, and meeting various reporting needs. USD's Banner instance is on-premises and there are no current plans to move it to a SaaS model. The RFP also covers workflows for admissions applications, including undergraduate, graduate, and international applications. USD staff will be able to provide data extracts from legacy systems to support the migration to the new Slate CRM.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| RFP Document.pdf | ||
| Response to Offeror Questions document.docx | DOCX document | |
| Addendum 1-RFP Document.pdf |
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
Questions and Answers for Slate CRM Software Implementation RFP Continued
RFP # USD08052024
1. Q: In Section 5.2.3.2 on page 14, you reference a "specific point-by-point response, in the order listed, to each requirement in the RFP." Would you prefer that vendors list only the number of each question, or would you like us to also include the full text of each question from the RFP?
A: The citation of the number will be just fine.
2. Q: Regarding the Matrix Chart, would you like vendors to include it with the RFP submission, or is it acceptable to provide a detailed response addressing each question from the Matrix Chart within the Detailed Response section? If you prefer the latter, should we include a "Yes/No" indication for whether the "Requirement is Met" in our responses to each question?
A: Including the scoring table in your response would be helpful for an at-a-glance view for our team. Please provide as detailed of a response as necessary in your Detailed Response section mentioning the section of the scoring table you are discussing.
3. Q: Is USD's Banner instance On-prem or SaaS? If On-prem, does USD have a timeline for moving to SaaS?
A: USD’s Banner instance is on-prem and managed by the Board of Regents Information Services department. We are not aware of an established timeline for moving to SaaS.
4. Q: Does USD have an Ellucian Experience premium license?
A: The SD Board of Regents Information Services department has a premium license that covers all six of the public universities in South Dakota. This is something not managed by USD.
5. Q: Is Ethos API integrated yet in your system?
A: Ethos API is enabled on the system wide instance of Banner. Use of the API is governed and controlled by the SD Board of Regents Information Services, not USD.
6. Q: How many total admission applications and associated workflows are planned to be built? (3.3 – bullet 3) Or are these the seven listed groups under 2.1?
A: One admission application. The workflows may vary, but we have varying requirements based on dual-credit, undergraduate, undergraduate international, graduate, graduate international.
7. Q: Is your staff able to provide data extracts for your legacy Salesforce data to be migrated to Slate? (3.1) A: Yes.
8. Q: Is your staff or support staff at the vendor able to provide data extracts / web service connection information for your third-party platforms? (3.5 Ingress integrations) A: Yes.
9. Q: Can you provide additional details related to the reporting requirements listed in 3.7 – bullet 1 – “Specific reporting requirements to be met”?
A: The main goal is training. We run reports on prospects, applicants, admits, enrollees for various territories and programs. Typically reports have been used as a funnel tool to help move applicant along the process.
10. Q: Can you list out and provide additional details for the current form-based processes referred to in 1.4.1 – bullet 3?
A: See Q23 from first Q&A.
11. Q: Do you have a designated Slate captain(s)?
A: Please see Question 10 from the first Q&A.
12. Q: Do you plan on importing/exporting more data from Slate to/from Banner than you currently do with Salesforce? Or is the plan to match the inputs and outputs as they are now?
A: Our plan is to match inputs/outputs.
13. Q: Will any remaining data flow exist from Salesforce to Banner after the conversion to Slate?
A: No, we would like this to all come from Slate.
14. Q: Are Banner integrations currently managed via flat files or APIs?
A: Currently, these are managed as flat files.
15. Q: Are changes expected in the ingress processes with Banner besides from Slate?
A: No, the same data we are putting in Salesforce from Banner, we would like in Slate.
16. Q: Are changes expected in the egress processes with Banner besides to Slate?
A: No, the same data we are putting in Banner from Salesforce, we would like from Slate.
File details come from the government source that posted it. Updated .