Attachment_C_Mid-Level_Requirements.pdf
PDF 273 KB Posted
- Solicitation number
- 0000038843
- Issued by
- California
About this file
This document is Attachment C of Request for Information (RFI) 25-IC0054 for the State of California, detailing mid-level requirements for an online payment and applications system for licensing. The system is designed to support both public visitors and internal/external users in managing license applications, renewals, payments, and related administrative functions. The RFI encompasses 55 functional and non-functional requirements organized across multiple areas including user management, access management, online applications, license renewal, payment processing, workflow management, continuing education management, examination management, and system administration. Key functional capabilities include electronic application submission with draft-saving functionality, license renewal processing, document repository management, multi-method payment processing (credit card, debit card, electronic funds transfer), and workflow automation triggered by business rules.
The non-functional requirements establish technical specifications requiring the system to support at least 5,000 concurrent users with 99.9% annual availability, page load times within 2 seconds, and scalable database infrastructure supporting approximately 200 gigabytes minimum capacity with 10 million initial records and 20 gigabytes annual growth. Security requirements mandate compliance with industry standard best practices including Transport Layer Security encryption, Federal Information Processing Standards 140, NIST SP 800-53 moderate-level controls, and multi-factor authentication. The system must be developed using Microsoft stack technology, follow n-tier architecture principles, comply with Web Content Accessibility Guidelines 2.1 Level AA standards, and support integration with external systems including the U.S. Postal Service, state-approved payment vendors, and examination proctoring services. Data backup and disaster recovery capabilities must be compatible with the Department of Professional Regulation's Rubrik platform.
View the file
Other files
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
RFI-25IC0054 ATTACHMENT C - MID-LEVEL REQUIREMENTS
Requirement Type
Functional Area
Functional User Management Functional Access Management Functional Online Application Functional License Renewal Functional Data Validation Functional Document Functional Payment Processing Functional Workflow Functional Application Management Functional Application Review & Assignments Functional Audit & Compliance Functional Communication Functional Continuing Education (CE) Management Functional Examination Management Functional Interfaces & Integrations Functional License Management Functional Reporting & Search Functional System Administration Non-Functional Security Non-Functional Usability Non-Functional Performance Non-Functional Data Base Non-Functional Application Architecture Non-Functional Availability Non-Functional Data Backup Non-Functional Interfaces Non-Functional Maintainability Non-Functional Privacy & Compliance
RFI - 25-IC0054 ATTACHMENT C - MID-LEVEL REQUIREMENTS
Number Requirements Functional Area Requirement Users Impacted
BR01 Functional User Management The system shall allow users without an existing online account to register for a new account.
Public Visitor
BR02 Functional User Management The system shall allow users to manage accounts. Internal & External User
BR03 Functional Access Management The system shall follow processes including challenge response and email verification to mitigate security risks.
External User
BR04 Functional Access Management The system shall allow role-based access and privileges. Internal User BR05 Functional Access Management The system shall allow authorized users to login and logout of the system Internal & External User
BR06 Functional Online Application The system shall allow users to view and enter information through secure web interface and submit applications electronically.
Internal & External User
BR07 Functional Online Application The system shall assign a unique application ID. Internal User BR08 Functional Online Application The system shall allow applicants to save draft applications. Internal & External User
BR09 Functional Online Application The system shall provide the submittal confirmation including the details of the submitted transaction and invoice.
Internal & External User
BR10 Functional License Renewal The system shall allow users to renew licenses electronically. Internal & External User
BR11 Functional Data Validation The system shall enforce data validation rules, including document-related validations. Internal & External User
BR12 Functional Document The system shall maintain a document repository. Internal & External User BR13 Functional Document The system shall allow users to upload and manage documents. Internal & External User
BR14 Functional Payment Processing The system shall calculate a payment amount for the transaction including late fees and fee exemptions.
Internal & External User
BR15 Functional Payment Processing The system shall allow users to manage payment statuses. Internal User BR16 Functional Payment Processing The system shall generate electronic receipts. Internal & External User BR17 Functional Payment Processing The system shall maintain payment statuses and payment history. Internal & External User
BR18 Functional Payment Processing The system shall allow users to select payment method for any payments including electronic, bank check and cash.
Internal & External User
BR19 Functional Payment Processing The system shall allow users to pay for applications electronically using credit card, debit card, and electronic funds transfer (EFT).
Internal & External User
BR20 Functional Workflow The system shall execute workflow for each application submission for further processing.
Internal & External User
BR21 Functional Workflow The system shall trigger and execute workflows as per DPR business rules for operations including field updates, status changes, submission and assignment updates, notifications, emails and overrides.
Internal & External User
BR22 Functional Application Management The system shall provide a public homepage. Public Visitor BR23 Functional Application Management The system shall provide a user homepage for authenticated users. Internal & External User BR24 Functional Application Management The system shall allow users to manage applications after submittal. Internal & External User
BR25 Functional Application Management The system shall maintain application submissions enabling users to view associated data information and documents.
Internal User
BR26 Functional Application Management The system shall manage, track and display application statuses. Internal & External User BR27 Functional Application Management The system shall pre-populate applications with existing data. Internal & External User
BR28 Functional Application Review & Assignments The system shall create assignments for teams and/or users for review processing. Internal User
BR29 Functional Application Review & Assignments The system shall allow users to approve, deny, or request additional information Internal User BR30 Functional Application Review & Assignments The system shall manage, track, and display assignment details. Interna User BR31 Functional Application Review & Assignments The system shall record approval/denial reason codes. Internal User
BR32 Functional Application Review & Assignments The system shall allow users to view and enter information through secure web interface for reviewing the application submissions.
Internal & External User
BR33 Functional Application Review & Assignments The system shall allow users to perform assignments actions including start, reassign, hold or complete.
Internal User
BR34 Functional Application Review & Assignments The system shall generate a digital license certificate upon approval. Internal & External User BR35 Functional Audit & Compliance The system shall capture a history of changes for certain records. Internal & External User BR36 Functional Communication The system shall facilitate emails and notifications for users. Internal & External User
BR37 Functional Communication The system shall email and/or notify users when critical dates are approaching including license renewals.
External User
BR38 Functional Continuing Education (CE) Management
The system shall manage, track and display CE course statuses. Internal & External User
BR39 Functional Continuing Education (CE) Management
The system shall maintain and allow users to manage continuing education data including creating new courses and instances.
Internal User
BR40 Functional Continuing Education (CE) Management
The system shall maintain sponsor course attendance data. Internal User
BR41 Functional Examination Management The system shall allow users to manage eligibility status based on exam results. Internal User
BR42 Functional Examination Management The system shall maintain and track examination registration, results, and eligibility status.
Internal User
BR43 Functional Interfaces & Integrations The system shall expose APIs to support data sharing with other systems as required . Internal User
BR44 Functional Interfaces & Integrations The system shall support scheduled, automated interaction with internal and external systems through web services and file-based batch processing.
Internal & External User
BR45 Functional Interfaces & Integrations The system shall interface with U.S. Postal Service (USPS) to provide address verification and standardization.
Internal User
BR46 Functional Interfaces & Integrations The system shall interface with state-approved vendors to process credit and electronic funds transfer (EFT) transactions.
Internal User
BR47 Functional Interfaces & Integrations The system shall interface with examination proctor services for managing examinations data
Internal User
BR48 Functional License Management The system shall maintain and allow users to manage licenses. Internal User BR49 Functional License Management The system shall support the creation of user license badges Internal User BR50 Functional Reporting & Search The system shall allow users to perform searches and run reports. Internal User
BR51 Functional Reporting & Search The system shall allow users to view search results or reports and take further actions including export.
Internal User
BR52 Functional Reporting & Search The system shall provide the capability of creating dashboards for key metrics Internal User BR53 Functional System Administration The system shall allow users to manage user access and actions. Internal User
BR54 Functional System Administration The system shall allow users to manage documents and templates including document security levels.
Internal User
BR55 Functional System Administration The system shall allow users to manage text and values. Internal User
TR01 Non-Functional Security The system shall include a security framework that follows industry standard best practices including Transport Layer Security (TLS) encryption and Federal Information Processing Standards (FIPS) 140 publication encryption standards.
Internal & External User
TR02 Non-Functional Security The system shall prevent unauthorized access that may cause security risks and support data encryption as per State guidelines and DPR standards.
Internal & External User
TR03 Non-Functional Security The system shall provide encryption and/or hashing, for both data in motion and data at rest, where necessary.
Internal & External User
TR04 Non-Functional Security The system shall meet all applicable moderate level National Institute of Standards and Technology (NIST) SP 800-53 controls.
Internal & External User
TR05 Non-Functional Security The system shall support authorization and authentication of all users including multi-factor authentication (MFA).
Internal & External User
TR06 Non-Functional Usability The system shall comply with Web Content Accessibility Guidelines (WCAG) version
2.1 or newer, at a minimum Level AA success criteria.
Internal & External User
TR07 Non-Functional Usability The system shall be accessible by mainstream browsers. Internal & External User TR08 Non-Functional Usability The system shall provide industry-standard graphical interface features. Internal & External User
TR09 Non-Functional Usability The system shall provide responsive user interface layout to optimize viewing in different screen orientations and sizes.
Internal & External User
TR10 Non-Functional Performance The system shall support at least 5000 concurrent users to perform create, read, update, and delete transactions based upon their user role.
Internal & External User
TR11 Non-Functional Performance The system shall meet or exceed the performance metrics of all create, read, update, and delete (CRUD) functions.
Internal & External User
TR12 Non-Functional Performance The system shall load user pages within 2 seconds. Internal & External User
TR13 Non-Functional Data Base The system shall support a large database and maintain security and integrity of such data.
Internal & External User
TR14 Non-Functional Data Base The system shall support a scalable database with a minimum 200 GB in size and approximately 10 million initial records.
Internal & External User
TR15 Non-Functional Data Base The system shall support database size of 50 GB for storing document images and files with an expected annual growth of 20 GB.
Internal & External User
TR16 Non-Functional Data Base The system shall be flexible and have data model loosely coupled with consumers of data.
Internal & External User
TR17 Non-Functional Application Architecture The system shall be developed using open standards consistent with State’s Coding Standards, be based on n-tier architecture, and be scalable.
Internal & External User
TR18 Non-Functional Application Architecture The system shall provide the ability for users to manage dynamic application parameters, settings, and lookup values without the actual need of updating source code.
Internal & External User
TR19 Non-Functional Application Architecture The custom components of the system shall be coded using Microsoft stack to allow for maintenance and future enhancements.
Internal & External User
TR20 Non-Functional Application Architecture The system shall meet the State's cloud hosting requirements. Internal & External User TR21 Non-Functional Application Architecture The system shall support concurrent data access to multiple authorized users. Internal & External User
TR22 Non-Functional Application Architecture The system shall support comprehensive code logging and error tracing framework. Internal & External User
TR23 Non-Functional Availability The system shall meet or exceed the 99.9% availability annually. Internal & External User TR24 Non-Functional Availability The system provide Disaster recovery capability as defined by DPR Internal & External User TR25 Non-Functional Data Backup The system shall backup data to DPR's Rubrik platform. Internal & External User TR26 Non-Functional Data Backup The system shall allow configurable data retention capabilities. Internal & External User
TR27 Non-Functional Interfaces The system shall log all inbound and outbound interface transactions for audit and troubleshooting.
Internal & External User
TR28 Non-Functional Maintainability The system shall support configurable workflows. Internal & External User
TR29 Non-Functional Maintainability The system shall provide the ability for users to manage business rules without an actual need of updating source code.
Internal & External User
TR30 Non-Functional Maintainability The system shall utilize DPR's source code repository for all custom code implementation and storage.
Internal & External User
TR31 Non-Functional Privacy & Compliance The system shall allow configurable data retention capabilities. Internal & External User
File details come from the government source that posted it. Updated .