Vendor_-_Q_and_A_Set_1_-_2-29-2024_-_Final_for_Addendum_1.docx
DOCX document 63 KB Posted
- Solicitation number
- 0000029823
- Issued by
- Sacramento County, Sacramento City, California
About this file
This document is a Question and Answer set related to Request for Proposal (RFP) 3213 issued by the California Employment Development Department (EDD) for Shared Customer Portal Maintenance and Operations and Enhancements. The RFP seeks professional services to assist with the maintenance and operations of the existing Shared Customer Portal (SCP) and provide enhancements to the system. The document provides responses to 23 questions from potential bidders covering topics such as transition of current operations, key staff requirements, translation services, identity management integration, user provisioning, and various functional and technical requirements.
The RFP covers the entire state of California, with specific references to the jurisdictions of Sacramento County and Palo Alto City. There are no set-aside requirements mentioned, and the current incumbent vendor is not specified. The document indicates that there will be no transitional period from the current vendor to the new vendor, and EDD will assist with knowledge transfer. The contract term and any renewal options are not provided.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| Vendor_-_Q_and_A_Set_2_-_3-19-2024_-_Addendum_2_-_FINAL.docx | DOCX document | |
| EXHIBIT_C_-_Cost_Workbook_SCP_Enhancements_-_Addendum_4.xlsx | XLSX spreadsheet | |
| Vendor_-_Q_and_A_Set_3_-_3-27-2024_-_Addendum_4_-_FINAL.docx | DOCX document | |
| EXHIBIT_B-_FUNCT_AND_NON-FUNCT_REQs-Addendum_4.xlsm | XLSM spreadsheet | |
| Exhibit_L_-_Confidentiality_Agreement_-_Addendum_4.docx | DOCX document | |
| Shared_Customer_Portal_Enhancements_RFP-Addendum_4.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
| State of California | RFP 3213 |
| Employment Development Department | Shared Customer Portal |
| Maintenance and Operations | |
| and Enhancements |
QUESTION AND ANSWER SET #1
| # |
| Section /Documents |
| Page # |
| Question |
| Answer |
| 1 |
| Cost Workbook |
| 111 |
| The State has not specified a duration, cost, or scoring for transitioning current M&O responsibilities from the current vendor to the winning vendor. When and how does the State envision this transition process occurring? |
| There will be no transitional period from current vendor to new vendor and EDD will assist with knowledge transfer. M&O for the Existing Portal System will commence upon contractors’ resources being onboarded. |
| 2 |
| Attachment 13.5, |
Attachment 13.7, Attachment 13.9 112, 122,
| The RFP states desirable key staff requirements for experience with EDD systems (e.g., "Attachment 13.7 DS 17 - Technical experience with an EDD system and interface."). Can State confirm "EDD system" means any UI or DI system similar in scope/scale to EDD's current systems? |
| Please refer to revisions in RFP 3213 Shared Customer Portal Enhancements, Addendum 1, Part 2, Attachment 13.5 – Business Solution Analyst – Qualifications Form, Requirement 14, Attachment 13.7 – Technical Architect – Qualifications Form, Requirement 17 and Attachment 13.9 – Technical Lead – Qualifications Form, Requirement 16. |
| 3 |
| Section 8.5.17.2 Claim Intake Navigator |
| 157 |
| Will EDD be responsible for providing translation to Spanish, Simplified Chinese, Traditional Chinese, Vietnamese, Tagalog, Korean, and Armenian? |
| Yes, EDD will provide this. |
Please refer to revisions in RFP 3213 Shared Customer Portal Enhancements, Addendum 1, Part 2, Attachment 15 – Statement of Work, Section 8.5.17.1 – Enhanced User Administration.
| 4 |
| Section 22. Reporting |
| 174 |
| Does the State expect the winning vendor to provide operations support for the existing Okta and Socure Identity proofing solutions? |
If so, please provide the number of SDLC environments for these solutions / platforms.
Please refer to revisions in RFP 3213 Shared Customer Portal Enhancements, Addendum 1, Part 2, Exhibit B – Functional and Non-Functional Requirements.
There are six (6) SDLC environments; two (2) development, two (2) test, one (1) pre-production, one (1) production.
There are three (3) Socure environments. Additional non-production environments may be added to support EDDNext modernization efforts, including those for Data and Analytics in the RFP.
| 5 |
| Exhibit_B-Functional and Non-Functional Requirements |
Does the State currently leverage any vulnerability and code scanning tools to perform network, infrastructure, and/or code scans for EDD applications?
If so, please provide the list of tools.
Yes, EDD has vulnerability and code scanning tools in place to perform network, infrastructure, and/or code scans for EDD applications.
A list of these will be provided to the Contractor upon contract award.
| 6 |
| Exhibit_B-Functional and Non-Functional Requirements |
Is Salesforce shield included in the current setup?
Has the State implemented Data Detect, Event Monitoring, Field Audit Trail, and Platform Encryption capabilities in the EDD Salesforce implementation?
Yes, Salesforce shield is included in the current setup.
Yes, the State has implemented these capabilities in the EDD Salesforce implementation.
| 7 |
| Exhibit_B-Functional and Non-Functional Requirements |
| Does the State have any existing SIEM integration with the Salesforce platform? |
| Yes, the State has an existing SIEM tool that is integrated with the Salesforce platform. |
| 8 |
| Exhibit_B-Functional and Non-Functional Requirements |
| Can the state elaborate on the current integration between Okta and Salesforce for identity lifecycle management: are the users getting provisioned roles, permission sets, personas, etc. into Salesforce based on roles in Okta? |
| Salesforce stages users, Okta workflows update/create the Salesforce users using APIs between the applications. |
| 9 |
| Exhibit_B-Functional and Non-Functional Requirements |
| How does the State currently provision and deprovision users into LDAP (i.e., are users provisioned into LDAP (e.g., Active Directory)) with group memberships via Okta or another identity management solution? Please elaborate. |
| Currently provisioning and deprovisioning of users are provisioned into LDAP (Active Directory) with AD groups and manually provisioned and deprovisioned in Salesforce. Users will be accessing Salesforce app/environments via EDD SSO tools like Workspace One or Microsoft Entra ID. |
| 10 |
| Attachment 13.5 Business Solution Analyst |
| 111 |
| Is the first part of Requirement 11 an incomplete sentence or does the ending of “and” lead to part “a.” requirement that is on next row? |
| Please refer to revisions in RFP 3213 Shared Customer Portal Enhancements, Addendum 1, Attachment 13.5 – Business Solutions Analyst – Qualifications Form, Requirement 11. |
| 11 |
| Attachments 13.x Qualification Forms |
Some requirements asking for x amount of ands experience allow for indicating a project can be used to partially fulfill the requirement and some requirements just say “Yes” or “No” that the identified project has the full years to meet the requirement. Can multiple projects experience be used to meet a requirement “total experience required”?
Example: Attachment 13.1 Engagement Manager Req. 11 asks for 7 years experiences as engagement manager but only allows for Yes/No response while Attachment 13.5 Business Analyst Solution Req. 11 asks for 4 years experience and allows for “Partial” to be allowed.
Please refer to revisions in RFP 3213 Shared Customer Portal Enhancements, Addendum 1, Attachment 13.5 – Business Solution Analyst – Qualifications Form, boxes 11-14.
| 12 |
| Attachment 15 SOW Exhibit A SOW |
| Please confirm if either of these should be submitted with the response and which Volume. Neither are noted in Section 6.5 Final Proposal and Content that lists out which attachments should be provided in which Volume. However, Exhibit A is noted in the 7.3.6 Proposal Requirements Evaluation table as a Pass/Fail submission item, but Exhibit A just says it’s a placeholder for Attachment 15. |
| Please refer to revisions in RFP 3213 Shared Customer Portal Enhancements, Addendum 1, Part 1, Section 6.5.2 Volume 2: Response to Proposal Requirements and Section 7.3.6 Proposal Requirements Evaluation. |
| 13 |
| Attachment 16 |
Attachment 17
| Please confirm if and where Attachments 16 and 17 should be submitted. Neither are mentioned in Section 6.5 Final Proposal and Content, 7.3.5 Administrative Requirements Evaluation, or 7.3.6 Proposal Requirements Evaluation. |
| Per section 3.15 of RFP 3213, “…These forms are required to be submitted with the Final Proposal.” |
Please refer to revisions in RFP 3213 Shared Customer Portal Enhancements, Addendum 1, Part 1, Section 6.5.1 Volume 1: Response to Administrative Requirements, Section 7.3.5 Administrative Requirements Evaluation, and Section 7.3.6 Proposal Requirements Evaluation.
| 14 |
| 8.5.17.1 Enhanced User Administration |
| 157 |
| For Epic 1 Enhanced User Administration – For the Block and Release functionality, is the feature intended to be a merge of accounts or a block/flag of duplicate accounts? |
| EDD customers occasionally will create a new account when an existing account exists, creating a conflict in myEDD. The Block and Release function allows an EDD user to clear the conflict so that the customer can use the new account. The function does not merge accounts. Instead, it changes the account state so that the desired email address can be used again. |
| 15 |
| 8.5.17.1 Enhanced User Administration |
| 157 |
| For Epic 1 Enhanced User Administration – For the Migrate BPO database feature, what is the number of records and objects (tables) intended for migration from BPO to salesforce? |
| There are 6 to 10 data tables and the approximate number of records is 300M to 325M. There are 72 to 100 fields total. |
| 16 |
| 8.5.17.2 Claim Intake Navigator |
| 157 |
| For Epic 2, Claim Intake Navigator Feature 4, what is the approximate number of FAQ webpages that would be replaced by the claim intake navigator? |
Feature 4: Guide Customers - Replace the large number of dense FAQ webpages and use dynamic sorting to lead customers to the appropriate services.
The intent is not to replace the FAQ webpages. The intention is to refine the information in this link and its subpages:
https://edd.ca.gov/en/claims/.
| 17 |
| Exhibit B – Requirement 11 |
What is the size of the data to be migrated in terms of three variables:
1. Number of Tables to be migrated,
2. Number of records to be migrated,
3. Number of Fields to be migrated?
There are 6 to 10 data tables and the approximate number of records is 300M to 325M. There are 72 to 100 fields total.
| 18 |
| Attachment 10 |
Attachment 13
| Attachment 10 Start and End Date instructions states, “All experience must have occurred within the last twelve (12) years prior to the RFP release date (1/11/2012)” and Attachment 13 Start and End Date instructions state “All experience must have occurred within the last twelve (12) years prior to the RFP release date (1/11/2011)”. Please confirm 2011 or 2012. |
| Please refer to revisions in RFP 3213 Shared Customer Portal Enhancements, Addendum 1, Part 2, Attachment 13 – Key Staff Qualifications Form - Instructions. |
| 19 |
| 3.13.2.1 |
| 30 |
| DVBE Participation Requirement: We are seeking clarification regarding DVBE participation. Is this a mandatory requirement or a bidding incentive requirement ? |
| Per RFP 3213 Shared Customer Portal Enhancements, Part 1 Section 3.13.2.1, DVBE Participation Requirement (M), this is a mandatory requirement. |
| 20 |
| Attachment 11: Bidder Qualification Form |
| 85 |
| Is there an opportunity to adjust the bidder qualifications to align with the Shared Customer Portal, rather than a claim management system? |
In our question, we were trying to point out that several of the minimum qualifications for both firms and staff really ask for experience with Benefit Systems (systems that deal with claim applications, case management, eligibility determination, etc.), but the Shared Customer Portal does not have any of that functionality. For example, the first bidder qualification states:
“Experience as a system integrator for at least one (1) large US state government benefits system using SaaS technology that processes at least four (4) million claims per year. Minimum of 4 years."
In the context of SCP, this experience isn’t aligned with SCP functionality. SCP really deals with secure account registration, MFA enrollment, Single Sign-On (SSO), logins, MFA challenge, and user profile updates. Our proposal was to review the existing minimum qualifications to make sure that the experience requested aligns to the actual work that would be conducted under this project. For example, adjusting the above qualification to require experience building systems with X number of logins or MFA enrollments - where this experience would be directly applicable to enhancing and building upon the existing SCP solution. We would suggest to review the mandatory qualifications with the EDDNext leadership team to ensure they fully align with the project scope.
Please refer to revisions in RFP 3213 Shared Customer Portal Enhancements, Addendum 1, Attachment 11 – Bidder Qualifications Form.
| 21 |
| Attachment 10: Bidder Qualifications Form – Instructions |
| 83 |
| Is there an opportunity to edit out #5 of the Project Contact Person Information (Project Reference Person): Identify the name of a person at the company in which the project was completed. Include person's contact information. This person must have been: #5. “Not be an employee of EDD” |
| Please refer to revisions in RFP 3213 Shared Customer Portal Enhancements, Addendum 1, Attachment 10 – Bidder Qualifications Form - Instructions |
| 22 |
| Attachment 13: Key Staff Qualification Form – Instructions |
| 93 |
| Is there an opportunity to edit out #5 of the Project Contact Person Information (Project Reference Person): Identify the name of a person at the company in which the project was completed. Include person's contact information. This person must have been: #5. “Not be an employee of EDD” |
| Please refer to revisions in RFP 3213 Shared Customer Portal Enhancements, Addendum 1, Attachment 13 – Key Staff Qualifications Form - Instructions. |
| 23 |
| Attachment 13.6 Technical Architect Qualifications |
| 120 |
| Technical Architect, min qual #15, How we can assemble the experience requested. For example, it asks for experience with a system with 5000 users and 300 million rows. Can we assemble the 300 million rows across our experience with systems over the years? |
| Please refer to revisions in RFP 3213 Shared Customer Portal Enhancements, Addendum 1, Attachment 13.7 – Technical Architect – Qualifications Form. |
Each project must meet the minimum number of rows and minimum number of users.
File details come from the government source that posted it. Updated .