EXHIBIT_B-_FUNCT_AND_NON-FUNCT_REQs-Addendum_4.xlsm

XLSM spreadsheet 97 KB Posted Jan 11, 2024

Attached to: Shared Customer Portal Maintenance and Operations and Enhancements
Solicitation number: 0000029823
Issued by: Sacramento County, Sacramento City, California

About this file

Written by GovTribe AI · Apr 3, 2024

This document is an Addendum to the Request for Proposal (RFP) for the Shared Customer Portal (SCP) Enhancements project Maintenance & Operations and Enhancements for the California Employment Development Department (EDD). The RFP covers the need for professional services to assist the EDD with maintenance and operations of the existing SCP Portal and enhancements to the system. The RFP includes detailed functional and non-functional requirements for the solution, including access management, data management, reporting, security, system integration, and user interface capabilities. The RFP is applicable to the state of California as well as the local jurisdictions of Sacramento County and Palo Alto City.

The RFP does not provide specific pricing terms or set asides. There is no information on incumbents, funding requirements, or award dates. The term of the contract is not specified, but the RFP indicates that the vendor must provide system support throughout the term of the contract.

View the file

Other files

File	Type	Posted
Vendor_-_Q_and_A_Set_2_-_3-19-2024_-_Addendum_2_-_FINAL.docx	DOCX document	Jan 11, 2024
EXHIBIT_C_-_Cost_Workbook_SCP_Enhancements_-_Addendum_4.xlsx	XLSX spreadsheet	Jan 11, 2024
Vendor_-_Q_and_A_Set_3_-_3-27-2024_-_Addendum_4_-_FINAL.docx	DOCX document	Jan 11, 2024
Exhibit_L_-_Confidentiality_Agreement_-_Addendum_4.docx	DOCX document	Jan 11, 2024
Shared_Customer_Portal_Enhancements_RFP-Addendum_4.pdf	PDF	Jan 11, 2024
Vendor_-_Q_and_A_Set_1_-_2-29-2024_-_Final_for_Addendum_1.docx	DOCX document	Jan 11, 2024

On GovTribe

Work with this file

Download the original file
Contacts named in this file
Similar government files
Ask GovTribe AI about this file

Try for free Login

Text version

The file's text, extracted by GovTribe without its formatting.

SCP Enhancements Requirements

EXHIBIT B: FUNCTIONAL AND NON-FUNCTIONAL REQUIREMENTS - ADDENDUM 4

SCP Enhancements - System Requirements

SOW Bidder Package

Updated - February 27, 2024

Epic			Category	Requirement ID	Requirement	Existing Functionality	Type	Priority	Contractor Agrees to Provide the Requirement YES/NO
Enhanced User Administration	Claim Intake Navigator	Enhanced Data Analytics							Enhanced User Administration	Claim Intake Navigator	Enhanced Data Analytics
Y	Y	Y	Access Management	1	Solution must allow access via EDD's virtual/remote desktops and EDD telework equipment.	Y	Non-Functional	Mandatory
Y	n/a	Y	Access Management	2	Solution must provide role based user access.	Y	Non-Functional	Mandatory		n/a
Y	n/a	Y	Access Management	3	Solution must provide the administrative capabilities to manage role based access.	Y	Functional	Mandatory		n/a
Y	n/a	Y	Access Management	4	Solution must support single sign on (SAML) authentication utilizing ICAM.	Y	Non-Functional	Mandatory		n/a
Y	Y	Y	Access Management	5	Solution should allow authorized users to impersonate system users for troubleshooting purposes.	N	Non-Functional	Desirable
Y	Y	Y	Alerting	6	Solution must have solution wide messaging feature to alert users to system maintenance or alerts.	Y	Functional	Mandatory
Y	Y	Y	Data Management	7	Solution must provide customizable data retention policy(ies) for database(s), indexes (s), log(s) and other system artifacts as applicable.	N	Non-Functional	Mandatory
n/a	n/a	Y	Data Management	8	Solution must provide the capability for data to be imported, exported and be available in a non-proprietary data format.	N	Non-Functional	Mandatory	n/a	n/a
Y	Y	Y	Data Management	9	Solution provider must provide or update existing data model documentation.	N	Non-Functional	Mandatory
Y	n/a	Y	Data Management	10	Solution must support data validation and transformation.	N	Functional	Mandatory		n/a
Y	Y	Y	Data Migration	11	Solution software vendor and/or System Integrator must provide data migration/data conversion services.	N	Project-Transition	Mandatory
y	Y	Y	Data Migration	12	Solution software vendor must make available at no charge all necessary tools and software required for data migration/conversion.	N	Project-Transition	Mandatory
Y	n/a	Y	Data Migration	13	Solution must provide data migration and data conversion for a minimum of 1 terabyte of data.	N	Project-Transition	Mandatory		n/a
Y	Y	Y	Data Migration	14	Vendor must complete unit testing and initial round of business reconciliation testing.	N	Project-Transition	Mandatory
Y	Y	Y	Data Migration	15	Vendor must be able to prove that all data has been migrated into the new system correctly.	N	Project-Transition	Mandatory
Y	Y	Y	Data Migration	16	Vendor must provide the Data Conversion Model(s).	N	Project-Transition	Mandatory
Y	Y	Y	Data Migration	17	Vendor must provide the source-to-target / destination for field level data and conversion scripts.	N	Project-Transition	Mandatory
Y	Y	Y	Data Migration	18	Vendor must work with EDD to establish Data Migration success metrics.	N	Project-Transition	Mandatory
Y	Y	Y	Design	19	Solution must implement safeguards to protect its memory from unauthorized code execution.	N	Non-Functional	Mandatory
Y	Y	n/a	Design	20	Solution must prevent multiple users from updating the same data elements, records and/or transaction at the same time.	Y	Non-Functional	Mandatory			n/a
Y	Y	Y	Design	21	Solution must provide all new services in the Salesforce cloud platform to achieve reduced systems maintenance and reuse of cloud technology already in use by EDD.	Y	Non-Functional	Mandatory
n/a	n/a	Y	Design	22	Solution database shall integrate with SQL Server 2019 or newer.	Y	Non-Functional	Mandatory	n/a	n/a
Y	Y	Y	Design	23	Solution must support RESTful web service API calls.	Y	Non-Functional	Mandatory
Y	n/a	Y	Design	24	Solution must support federated data searches.	N	Non-Functional	Mandatory		n/a
Y	Y	Y	Design	25	Solution must provide the capability to access and consume REST or SOAP (if only option) web services.	Y	Non-Functional	Mandatory
Y	n/a	n/a	Design	26	Vendor must assist EDD teams with deprecation of migrated functionality in the legacy Admin Utility.	N	Non-Functional	Mandatory		n/a	n/a
Y	Y	n/a	Design	27	System must interface with other EDD systems as needed to provide feature functionality.	Y	Functional	Mandatory			n/a
n/a	Y	n/a	Design	28	System should determine the eligible benefits program(s) based on the customer input.	N	Functional	Desirable	n/a		n/a
n/a	Y	n/a	Design	29	System should allow customers to navigate to the application which will let users to apply for the eligible services.	N	Functional	Desirable	n/a		n/a
Y	Y	Y	Design	30	System must support Responsive web design such that System should respond to the user's behavior and environment based on screen size, platform and device orientation	Y	Functional	Mandatory
Y	Y	n/a	Design	31	System must adhere to EDD web template(s).	Y	Non-Functional	Mandatory			n/a
Y	Y	Y	Design	32	System must support exchanging data with the Data warehouse	N	Functional	Mandatory
Y	Y	Y	Design	33	Solution must provide EDD approved safeguards around PII.	Y	Non-Functional	Mandatory
Y	Y	Y	Design	34	Solution must be fully accessible and operational 24/7/365 less scheduled maintenance windows.	Y	Non-Functional	Mandatory
Y	Y	Y	Implementation Services	35	Solution must utilize EDD approved version control to track changes.	Y	Non-Functional	Mandatory
Y	Y	Y	Implementation Services	36	Project artifacts must include an EDD approved user acceptance testing plan.	N	Project-Transition	Mandatory
Y	Y	Y	Implementation Services	37	Project artifacts must include EDD approved content for our business continuity and technology recovery plans.	N	Project-Transition	Mandatory
Y	Y	Y	Implementation Services	38	Project artifacts must include an EDD approved implementation plan for each project phase.	N	Project-Transition	Mandatory
Y	n/a	Y	Design	39	Solution must provide sorting by column for all table views and queries.	N	Functional	Mandatory		n/a
Y	Y	Y	Logging	40	Solution audit logs must be forwarded to the EDD's centralized audit logging solution	Y	Non-Functional	Mandatory
Y	n/a	Y	Logging	41	Solution must record all transactions based on user profile.	Y	Non-Functional	Mandatory		n/a
Y	n/a	Y	Logging	42	Solution monitor must log customer management tasks (change password, etc.).	Y	Functional	Mandatory		n/a
Y	Y	Y	Performance	43	Solution must scale and load balance to account for system traffic and adjust to workload volumes and types as business needs change.	Y	Non-Functional	Mandatory
Y	Y	Y	Policy	44	Solution must comply with NIST 800-53 rev5 for FIPS – 199 Moderate systems.	Y	Non-Functional	Mandatory
Y	Y	Y	Policy	45	Solution must implement and comply with CA Policy 4983.1 (https://www.dgs.ca.gov/Resources/SAM/TOC/4900/4983-1)	Y	Non-Functional	Mandatory
Y	Y	Y	Policy	46	Solution must comply with Section 5300 of the State of California Statewide Information Management Manual (SIMM).	Y	Non-Functional	Mandatory
Y	Y	Y	Policy	47	Vendor must comply with EDD approved release management processes.	Y	Non-Functional	Mandatory
Y	Y	Y	Reporting	48	Solution must produce reports with trending information for System.	Y	Non-Functional	Mandatory
n/a	n/a	Y	Reporting	49	Solution should provide a reports dashboard.	N	Functional	Desirable	n/a	n/a
n/a	n/a	Y	Reporting	50	Solution must generate standardized, custom and ad hoc reporting.	N	Functional	Mandatory	n/a	n/a
n/a	n/a	Y	Reporting	51	Solution must allow for reports to be generated, including ad hoc, based on user's role within System.	N	Non-Functional	Mandatory	n/a	n/a
n/a	n/a	Y	Reporting	52	Solution must produce reports that allow for filtering and sorting of data.	N	Non-Functional	Mandatory	n/a	n/a
n/a	n/a	Y	Reporting	53	Solution must provide reports which allow the user to select desired time period for daily, weekly, monthly, quarterly, annually, or between specified beginning and ending dates.	N	Non-Functional	Mandatory	n/a	n/a
n/a	n/a	Y	Reporting	54	Solution must allow users to create ad hoc reports consisting of all available data elements through a user interface.	N	Non-Functional	Mandatory	n/a	n/a
n/a	n/a	Y	Reporting	55	Solution must provide reports which are either real time or near-real time.	N	Non-Functional	Mandatory	n/a	n/a
Y	n/a	Y	Reporting	56	Solution must provide reports which are available to authorized users through roles based access.	N	Non-Functional	Mandatory		n/a
Y	Y	Y	Reporting	57	Solution must provides the capability to identify, track, as well as monitor frequency and duration of system errors via Dashboards and Reports.	N	Non-Functional	Mandatory
n/a	n/a	Y	Reporting	58	Solution must provide administrative capabilities for authorized users to update standardized report templates.	N	Non-Functional	Mandatory	n/a	n/a
n/a	n/a	Y	Reporting	59	Solution must provide reports which are available electronically that can be exporting in pdfs, data delimited, comma delimited (CSV), or text file formats.	N	Non-Functional	Mandatory	n/a	n/a
n/a	n/a	Y	Reporting	60	Solution must allow authorized users to create dashboard views in addition to standardized and ad hoc reports based on available data.	N	Non-Functional	Mandatory	n/a	n/a
n/a	n/a	Y	Reporting	61	Solution must provide administrative capabilities for authorized users to add, remove or move data elements on established / standardized report templates	N	Non-Functional	Mandatory	n/a	n/a
n/a	n/a	Y	Reporting	62	Solution must provide reports which are available electronically, and can be printing to local and remote printers to produce a hardcopy.	N	Non-Functional	Mandatory	n/a	n/a
n/a	n/a	Y	Reporting	63	Solution must provide the capability to export electronic report content using filters to select the report data elements and date element ranges.	N	Non-Functional	Mandatory	n/a	n/a
n/a	n/a	Y	Reporting	64	Solution must provides the capability to create reports to provide statistical count to data and metadata created and/or capture within System and audit processes.	N	Non-Functional	Mandatory	n/a	n/a
n/a	n/a	Y	Reporting	65	Solution vendor must replace legacy system business process, operational and system performance reports.	Y	Non-Functional	Mandatory	n/a	n/a
n/a	n/a	Y	Reporting	66	Solution vendor may deliver up to additional custom reports for business, operational and system needs identified through Solution design and build.	N	Non-Functional	Desirable	n/a	n/a
n/a	n/a	Y	Reporting	67	System must support the creation and customization for reports using EDD standard tools.	N	Functional	Mandatory	n/a	n/a
n/a	n/a	Y	Reporting	68	System must provide ad hoc reporting capability allowing EDD Staff the ability to analyze user data for irregularities, trends, and patterns.	N	Functional	Mandatory	n/a	n/a
n/a	n/a	Y	Reporting	69	System must provide a report(s) containing the data elements currently included on reports received by Investigation Division, that is available online.	N	Functional	Mandatory	n/a	n/a
n/a	n/a	Y	Reporting	70	System must allow ad-hoc reports to be saved as standard reports.	N	Functional	Mandatory	n/a	n/a
n/a	n/a	Y	Reporting	71	System must allow user defined reports to be saved as user reports.	N	Functional	Mandatory	n/a	n/a
n/a	n/a	Y	Reporting	72	System must be able to report on all detected critical functionalities including total number of events and/or transactions by date, time, transaction.	N	Functional	Mandatory	n/a	n/a
n/a	n/a	Y	Reporting	73	System reports should support drill down into specific line items.	N	Functional	Desirable	n/a	n/a
Y	n/a	Y	Security	74	Solution must provide the capability to establish user roles based hierarchy.	N	Functional	Mandatory		n/a
Y	Y	Y	Security	75	Solution must be compatible with the EDD security infrastructure and toolset for technology used to protect solutions and data from unauthorized access attempts, as well as security breaches due to intentional or accidental causes.	Y	Non-Functional	Mandatory
Y	n/a	Y	Security	76	Solution must manage internal user access levels using EDD's Lightweight Directory Access Protocol (LDAP) implementation.	Y	Non-Functional	Mandatory		n/a
Y	Y	Y	Security	77	Solution must integrate with existing security products for all web-based interactions to detect potential security breaches.	Y	Non-Functional	Mandatory
Y	Y	Y	Security	78	Solution must conform to EDD ISO security policies and procedures regarding personally identifiable information (PII) in information solutions.	Y	Non-Functional	Mandatory
Y	Y	Y	Security	79	Solution must issue or obtain Public Key Infrastructure (PKI) certificates from a Secretary of State approved Certification Authority.	Y	Non-Functional	Mandatory
Y	Y	Y	Security	80	Solution must use Extended Validation (EV) Transport Layer Security (TLS) certificates on websites that process, store or transmit financial transactions and Personal Information (per California Civil Code Section 1798.3).	Y	Non-Functional	Mandatory
Y	Y	Y	Security	81	Solution must support SAML (Security Assertion Markup Language).	Y	Non-Functional	Mandatory
Y	Y	Y	Security	82	Solution must utilize existing EDD enterprise Intrusion Detection and Prevention (IDS/IPS) solutions.		Non-Functional	Mandatory
n/a	n/a	Y	Security	83	System must not allow reports to be viewed, exported, or printed by users that do not have permission to view, export, or print them.	N	Functional	Mandatory	n/a	n/a
Y	n/a	Y	Security	84	Solution must prevent access not autehnticated from Azure Active directory or secured EDD asset.	Y	Functional	Mandatory		n/a
Y	n/a	Y	System Administration	85	Solution must provide reportable audit logs of work item modifications whether they are generated by staff or automated business rules.	N	Functional	Mandatory		n/a
Y	n/a	Y	System Administration	86	Solution must support authorized users to configure user permissions.	Y	Functional	Mandatory		n/a
Y	n/a	Y	System Administration	87	Solution should allow for tiered delegation of workflow administration authority to authorized users.	Y	Functional	Desirable		n/a
Y	n/a	Y	System Administration	88	Solution must allow authorized users to control/force quit logged in users.	Y	Functional	Mandatory		n/a
Y	n/a	Y	System Administration	89	Solution must keep logs of all activities.	N	Functional	Mandatory		n/a
Y	n/a	Y	System Administration	90	Solution must allow user profile changes at the group level.	Y	Functional	Mandatory		n/a
Y	n/a	Y	System Administration	91	Solution must allow user profile changes in bulk.	Y	Functional	Mandatory		n/a
Y	n/a	Y	System Administration	92	Solution must allow for different permission levels and rights that can be customized by authorized users.	Y	Functional	Mandatory		n/a
Y	n/a	n/a	System Administration	93	Solution must provide auditing capability that reports on updates, adds or deletions during transactions.	Y	Non-Functional	Mandatory		n/a	n/a
Y	Y	Y	System Integration	94	Solution must support data conversion from existing systems.	N	Non-Functional	Mandatory
Y	Y	Y	System Integration	95	Solution must integrate/interface with all EDD required external and internal entities and systems based upon federal, state and EDD business rules, regulations and policies.	Y	Non-Functional	Mandatory
Y	Y	Y	System Integration	96	Solution must integrate with third party logging software.	Y	Functional	Mandatory
n/a	n/a	Y	System Interface	97	System must support exporting data from the Salesforce platform to the data warehouse to support federated search and reporting.	Y	Functional	Mandatory	n/a	n/a
n/a	n/a	Y	System Interface	98	System must support exporting data from ID Proofing to the data warehouse.				n/a	n/a
Y	Y	Y	System Interface	99	Solution must have the capability to interface with EDD legacy systems.	N	Non-Functional	Mandatory
n/a	n/a	Y	System Interface	100	Solution must have the capability to adding new interfaces	Y	Non-Functional	Mandatory	n/a	n/a
Y	Y	Y	System Interface	101	Solution must allow for exporting report data to third party applications.	N	Functional	Mandatory
n/a	Y	Y	System Interface	102	Solution must provide the capability to interface with existing online and batch applications to retrieve data from content management systems	N	Functional	Mandatory	n/a
Y	Y	Y	System Interface	103	Solution must interface with multiple legacy EDD systems.	N	Non-Functional	Mandatory
Y	Y	Y	System Maintenance	104	Solution must perform backup and recovery functions during schedule maitenance windows.	Y	Non-Functional	Mandatory
Y	Y	Y	System Monitoring	105	Solution must support data extraction.	N	Functional	Mandatory
n/a	Y	n/a	System Performance	106	Solution must support an average of 20,000 average concurrent users and surge to 200K concurrent users.	Y	Non-Functional	Mandatory	n/a		n/a
Y	Y	Y	System Performance	107	Solution performance must not degrade during enterprise antivirus scanning practices	Y	Non-Functional	Mandatory
Y	Y	Y	System Performance	108	Solution must be fully operational and available as defined by the contractual SLAs.	Y	Non-Functional	Mandatory
Y	Y	Y	Design	109	Solution must be browser-based.	Y	Non-Functional	Mandatory
Y	n/a	Y	System Performance	110	Solution must not degrade perfomance during query, export, report generation, or any other user function.	N	Non-Functional	Mandatory		n/a
Y	Y	Y	Training	111	Project artifacts must include user guides, online help screens, and all necessary training materials for each project phase.	N	Project-Transition	Mandatory
Y	Y	Y	Training	112	Vendor must provide hands-on training during technical support incidents to allow for the transition of technical support to EDD.	N	Project-Transition	Mandatory
Y	Y	Y	Training	113	Vendor must develop and deliver a Training Management Plan.	N	Project-Transition	Mandatory
Y	Y	Y	Training	114	Vendor must provide a listing and analysis of the required skills needed for EDD staff to use System and to support project lifecycle activities.	N	Project-Transition	Mandatory
Y	Y	Y	Training	115	Vendor must provide the maintenance and operations support training curriculum and ensure quality training products.	N	Project-Transition	Mandatory
Y	Y	Y	Training	116	Vendor must provide the maintenance and operations support training instructional methods and deliverables to be used to provide training to existing staff.	N	Project-Transition	Mandatory
Y	Y	Y	Training	117	Vendor must provide the maintenance and operations support training instructional methods and training deliverables to be used to train future support staff.	N	Project-Transition	Mandatory
Y	Y	Y	Training	118	Vendor must provide Train the Trainer curriculum, perform Train the Trainer training sessions, interactive training activities, as well as mock training exercises and scenarios.	N	Project-Transition	Mandatory
Y	Y	Y	Training	119	Vendor must provide a listing and analysis of the required skills needed for EDD to take over from Vendor to successfully support project lifecycle activities.	N	Project-Transition	Mandatory
Y	Y	Y	Training	120	Vendor must develop a knowledge plan and complete knowledge transfer to EDD staff by system implementation and must include all necessary manuals.	N	Project-Transition	Mandatory
Y	Y	Y	Training	121	Vendor must partner with EDD to develop the instructional methods to be used for Vendors deliverables to be used to train future staff (such as computer based training or video of knowledge transfer training) in order to be brought up to speed from the perspective of a new support staff position.	N	Project-Transition	Mandatory
Y	Y	Y	Training	122	Vendor must partner with EDD to develop technical and system administrative support staff training, shadowing, mentoring and guided hands on activities.	N	Project-Transition	Mandatory
Y	Y	Y	Training	123	Vendor must partner with EDD to develop support staff instructional methods to ensure the effective transition of maintenance and operational support responsibilities to state staff.	N	Project-Transition	Mandatory
Y	Y	Y	Training	124	Vendor must provide hands on report development training to state staff.	N	Project-Transition	Mandatory
Y	Y	Y	Training	125	Vendor must provide instructor led as well as online training and video delivery of training content.	N	Project-Transition	Mandatory
Y	Y	Y	Training	126	Vendor must provide a listing and analysis of the required skills needed to transition System to EDD staff.	N	Project-Transition	Mandatory
Y	Y	Y	Training	127	Vendor must develop and deliver a system maintenance and operations knowledge transfer plan.	N	Project-Transition	Mandatory
Y	Y	Y	Transition to Support	128	Vendor must provide project management services, during all project phases.	N	Non-Functional	Mandatory
Y	Y	Y	Transition to Support	129	Project artifacts must include an operations manual that is maintained throughout the term of the contract.	N	Project-Transition	Mandatory
Y	Y	Y	Transition to Support	130	Vendor must provide system support throughout the term of the contract.	Y	Project-Transition	Mandatory
Y	Y	Y	Transition to Support	131	Project artifact content must include solution specific backup and recovery procedures.	N	Non-Functional	Mandatory
Y	Y	Y	Usability	132	Solution must meet the government-agency standard Section 508's Web Content accessibility Guidelines (WCAG) version 2.1 or later, if approved and in effect at the time of contract start date, for ADA compliance.	Y	Non-Functional	Mandatory
Y	n/a	n/a	User Interface	133	Solution must migrate existing Admin Utility Front End functionality to Portal platform	N	Functional	Mandatory		n/a	n/a
Y	Y	n/a	User Interface	134	Solution may support the streaming playback of multiple video content formats (eg: .mp4, .mov, .avi, .flv, .wmv, or .mkv).	N	Functional	Desirable			n/a
n/a	Y	n/a	User Interface	135	Solution must support text for the 7 most commonly used languages, including but not limited to: Spanish, traditional Chinese, simplified Chinese, Vietnamese, Tagalog, and Korean, and Armenian.	N	Functional	Mandatory	n/a		n/a
Y	Y	Y	User Interface	136	Solution must provide point and click navigation, hot-keys, menu-driven, graphics, and keyboard shortcuts.	Y	Functional	Mandatory
Y	Y	Y	User Interface	137	Solution should provide an online help library with an index of topics available and allow for keyword search.	N	Functional	Desirable
Y	Y	n/a	User Interface	138	Solution navigation must include a "back" button in each view to take user to the previous view.	Y	Functional	Mandatory			n/a
n/a	Y	n/a	User Interface	139	System should allow 'claim intake navigator' to direct users to assist them in deciding appropriate benefit program for them.	N	Functional	Desirable	n/a		n/a
n/a	Y	n/a	User Interface	140	System will present questions and suggestions based on customer inputs	N	Functional	Mandatory	n/a		n/a
n/a	Y	n/a	User Interface	141	System should allow customers to enter information to help them determine which benefits they are eligible for.	N	Functional	Desirable	n/a		n/a
Y	Y	n/a	User Interface	142	System should follow the EDD user input standards to disallow specific characters as input.	N	Functional	Desirable			n/a
Y	n/a	n/a	User Interface	143	Solution must enable the user to search for users based on program defined search criteria.	N	Functional	Mandatory		n/a	n/a
Y	n/a	n/a	User Interface	144	Solution must display for the support representitive the search results for UI, DI, ACES-BOS, Salesforce and ICAM.	Y	Functional	Mandatory		n/a	n/a
Y	n/a	n/a	User Interface	145	Solution must enable email correspondence in customer's selected language.	Y	Functional	Mandatory		n/a	n/a
Y	n/a	n/a	User Interface	146	Solution must enable the user to update the customer's myEDD account email address.	Y	Functional	Mandatory		n/a	n/a
Y	n/a	n/a	User Interface	147	Solution must enable the user to block the customer's myEDD account.	Y	Functional	Mandatory		n/a	n/a
Y	n/a	n/a	User Interface	148	Solution must enable the user to view myEDD account history action including account creation, change account email/password/security question/MFA, and added or removed roles.	Y	Functional	Mandatory		n/a	n/a
Y	n/a	n/a	User Interface	149	Solution must enable the user the ability to release an email from an active myEDD account with no entitlements so it can be updated on a different existing and active myEDD account with roles.	Y	Functional	Mandatory		n/a	n/a
Y	n/a	n/a	User Interface	150	Solution must enable the user to release the same myEDD email multiple times if the myEDD user mistakenly creates another account instead of updating an existing account after an initial email release.	Y	Functional	Mandatory		n/a	n/a
Y	n/a	n/a	User Interface	151	Solution must enable the user to remove myEDD user roles.	Y	Functional	Mandatory		n/a	n/a
Y	n/a	n/a	User Interface	152	Solution must enable the user to unblock a myEDD account.	Y	Functional	Mandatory		n/a	n/a
Y	n/a	n/a	User Interface	153	Solution must enable the user to search for released myEDD account emails.	Y	Functional	Mandatory		n/a	n/a
Y	n/a	n/a	User Interface	154	Solution must enable the user to swap EDDCANs between two different claimant SSNs.	Y	Functional	Mandatory		n/a	n/a
Y	Y	Y	Design	155	System must prevent unauthorized users from accessing System.	Y	Functional	Mandatory
Y	n/a	n/a	User Interface	156	Solution must enable the user to initiate a password change for a claimant.	Y	Functional	Mandatory		n/a	n/a
Y	n/a	n/a	Design	157	Solution must be available to EDD authorized personnel only.	Y	Functional	Mandatory		n/a	n/a
Y	n/a	Y	Design	158	The system must support multiple inbound and outbound interfaces.	Y	Functional	Mandatory		n/a
Y	n/a	n/a	Design	159	System must support implementing new interfaces consistent with myEDD systems.	Y	Functional	Mandatory		n/a	n/a
Y	n/a	n/a	Design	160	The system must support decoupling systems to share data via secure web API calls.	Y	Functional	Mandatory		n/a	n/a
Y	n/a	n/a	Design	161	The system must support decoupling the appliation layer from data layer.	Y	Functional	Mandatory		n/a	n/a
Y	n/a	n/a	Design	162	System must interface outbound with BPO Database, UIO and SDIO Webservices, ACES-BOS web services, Salesforce, Okta, Email Synch Services, Mainframe, BICC-Data Warehouse.	Y	Functional	Mandatory		n/a	n/a
Y	n/a	n/a	Design	163	System must interface inbound with BPO Database, UIO and SDIO Webservices, ACES-BOS web services, Salesforce, Okta, Email Synch Services, Mainframe, BICC-Data Warehouse.	Y	Functional	Mandatory		n/a	n/a
Y	n/a	n/a	Design	164	System must notify in near realtime the lines of business applications when a myEDD user changes their email address.	Y	Functional	Mandatory		n/a	n/a
Y	n/a	n/a	Design	165	System must create unique user identifcation (EDDCAN) across all lines of business for new users.	Y	Functional	Mandatory		n/a	n/a
Y	n/a	n/a	Design	166	System must manage unique user identificaiton (EDDCAN) across all lines of business for all external myEDD users. (UIO, SDIO, BICC, Mainframe, BPO Database).	Y	Functional	Mandatory		n/a	n/a
Y	n/a	n/a	Design	167	System must maintain unique user identification (EDDCAN) in Portal platforms (including but not limted to Okta and Salesforce).	Y	Functional	Mandatory		n/a	n/a
Y	n/a	n/a	Design	168	System must support associating a myEDD account to a unique user identiication (EDDCAN).	Y	Functional	Mandatory		n/a	n/a
Y	n/a	n/a	Design	169	System must authenicate external user via uniquie ID/PIN pair in Portal platforms (including but not limted to UI IVR).	Y	Functional	Mandatory		n/a	n/a
Y	n/a	n/a	Design	170	System must create uniquie ID/PIN pair in Portal platforms (including but not limted to UI IVR) for external user.	Y	Functional	Mandatory		n/a	n/a
Y	n/a	n/a	Design	171	System must manage uniquie ID/PIN pair in Portal platforms (including but not limted to UI IVR) for external user.	Y	Functional	Mandatory		n/a	n/a
Y	n/a	n/a	Design	172	System must block uniquie ID/PIN pair in Portal platforms (including but not limted to UI IVR) for external user.	Y	Functional	Mandatory		n/a	n/a
Y	n/a	n/a	Design	173	System must unblock uniquie ID/PIN pair in Portal platforms (including but not limted to UI IVR) for external user.	Y	Functional	Mandatory		n/a	n/a
Y	n/a	n/a	Design	174	System must ingest mainframe claimant files (SDI, UI) to assoiucate the claim data with EDDCANs (including but not limted to BPO Batch Process).	Y	Functional	Mandatory		n/a	n/a
Y	n/a	n/a	Design	175	System must export associated EDDCAN Claimant pair to mainframe in claimant files (SDI, UI) (including but not limted to BPO Batch Process).	Y	Functional	Mandatory		n/a	n/a
Y	n/a	n/a	Design	176	System must support sFTP file exchange with mainframe system and other systems.	Y	Functional	Mandatory		n/a	n/a
Y	Y	Y	Design	177	Solution must pass static code scans without any High and/or Critical findings via an EDD approved application.	N	Project-Transition	Mandatory

DETAILED FUNCTIONAL REQUIREMENTS

&P of &N & August 2016

M&O

EXHIBIT B: FUNCTIONAL AND NON-FUNCTIONAL REQUIREMENTS - ADDENDUM 4

SCP Enhancements - M&O System Requirements

SOW Bidder Package

Updated - February 27, 2024

Category Requirement ID Requirement Existing Functionality Type Contractor Agrees to the Requirement - YES/NO

MFA Enroll	MO1	The system will support mandatory MFA enrollment as a factor via email.	Y	Functional
MFA Enroll	MO2	The system will enabe the user to select MFA recovery questions	Y	Functional
MFA Enroll	MO3	The system will support up to one (1) optional MFA enrollment factor of SMS or Voice.	Y	Functional
MFA Enroll	MO4	The system will not support international numbers for SMS or for Voice.	Y	Functional
MFA Challenge	MO5	The system will challenge the user with a configured factor when user access the system.	Y	Functional
Expired Password	MO6	The system will prompt the user to reset their password when user accessed the system with an expired password.	Y	Functional
Portal Functionality	MO7	The system will enable authenticated users to access UIO, SDIO, and BOS line of business applications.	Y	Functional
Portal Functionality	MO8	They system will enable users to manage their account to set language, preference, email address, password, recovery question, and factor enrollment.	Y	Functional
Admin Utility	MO9	The system will enable password reset from Admin Utility.	Y	Functional
Timeout	MO10	The system will log out inactive users after 30 minutes.	Y	Functional
Timeout	MO11	The system sessions (without a user logged in) will expire after 30 minutes.	Y	Functional
Password Recovery	MO12	The system will start the password recovery process when the user enters an email for a known account.	Y	Functional
Password Recovery	MO13	The system will challenge the user with their recovery question and data elements pertaining to ther account.	Y	Functional
Password Recovery	MO14	The system will reset the user password on succssful challenge answers.	Y	Functional
Alerts Banner	MO15	The system must have system wide messaging to alert users to system maintenance or alerts.	Y	Functional
Technical	MO16	The Salesforce system should cache the following values from Okta daily:

* Group

* Password policy	Y	Functional
	Login Screen	MO17	The system login screen should present the user with email and password fields to allow them to log in	Y	Functional
	Login Screen	MO18	The system login screen should present the user with an option to reset their password	Y	Functional
	Login Screen	MO19	The system login screen should present the user with an option to register, which links to registration screen	Y	Functional
	Registration Screen	MO20	The system should ensure the provided email address (including permutations) is not already used in Salesforce or Okta before allowing the user to register	Y	Functional
	Email Verification	MO21	The system will provision the user in Okta after the user has provided valid registration attributes.	Y	Functional
	Email Verification	MO22	The system will verify registration via email to the email address registered.	Y	Functional
	Email Verification	MO23	The system will not honor email registration verification after 48 hours.	Y	Functional
	Email Verification	MO24	The system must support text for the 7 most commonly used languages: Spanish, traditional Chinese, simplified Chinese, Vietnamese, Tagalog, and Korean, and Armenian.	Y	Functional
	Portal Functionality	MO25	Solution must support SIEM integration(s).	Y	Functional
	Portal Functionality	MO26	Solution must support ID proofing integration(s).	Y	Functional

DETAILED FUNCTIONAL REQUIREMENTS

&P of &N & August 2016

File details come from the government source that posted it. Updated Apr 2, 2024.