Exhibit_B__Functional_and_Nonfunctional_Requirements_v4.0.xlsx
XLSX spreadsheet 102 KB Posted
- Solicitation number
- 0000040415
- Issued by
- California
About this file
This document is an Exhibit B from a state contract opportunity that outlines the functional and non-functional requirements for a comprehensive Driver License/Identification (DL/ID) card and related services system. The requirements span multiple business focus areas including case management, commercial driving tests, DL/ID transaction processing, driver safety, driving tests, endorsements/special certificates, financial responsibility, and general system functions. The system must support multiple service delivery channels including in-person visits, online platforms, mobile applications, interactive voice response, chat, kiosks, and contact centers. Bidders are required to indicate how each mandatory requirement will be met—whether through out-of-the-box functionality, customization, or extension—and must select "Yes" or "No" to confirm whether their proposed solution meets each requirement. Failure to properly complete these designations may result in rejection of the proposal. The document contains over 300 individual mandatory functional requirements that vendors must fully address in their proposals.
The requirements establish comprehensive backend functionality for processing driver records, managing digital credentials across multiple operating systems, issuing temporary and interim documents, handling document management and scanning, processing payments and fee schedules, and maintaining audit logs for compliance and investigation purposes. The system must support complex workflows including change control and approvals for record updates, exception processing with configured thresholds, and role-based access controls with security trimming of results. Key capabilities include managing restrictions and suspensions on licenses, processing commercial driving license endorsements and special certificates, supporting the Employer Testing Program, maintaining multiple addresses and demographic options on customer records, consolidating duplicate records, and generating automated notices and correspondence. The solution must also accommodate integration with third-party testing providers, support federal and state compliance requirements for CDL testing, and provide real-time reporting and audit capabilities for oversight and investigative purposes.
View the file
Other files
Show all 42
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
Instructions
| Exhibit B Instructions |
| The functional and non-functional requirements identified in EXHIBIT B: FUNCTIONAL AND NON-FUNCTIONAL REQUIREMENTS consist of Mandatory (M) requirements. The Bidder must provide complete responses to each (M), requirements. |
| The State will evaluate each functional and non-functional requirement, including any reference materials to which the State is specifically directed for additional information to determine whether the response fully addresses the requirements in accordance with the following criteria: |
| A proposal receives a Pass if the vendor clearly demonstrates that all mandatory functional and non‑functional requirements are fully met and provides sufficient supporting detail or evidence. A proposal receives a Fail if any mandatory requirement is missing, unclear, unsupported, or requires significant modification to meet compliance. |
| Additonally, Tthe Bidder must place a checkmark in the appropriate column to indicate how the requirement will be met (e.g., out-of-the-box, through customization, or through extension (using a toolset or software component/add-on) (Columns E, F, or G)). The Bidder must further indicate the solution’s ability to meet the requirement by selecting “Yes” or “No” in the column titled “Will Solution Meet Requirement?” |
| Failure to indicate how the solution will be met (Columns E, F, or G) and if the solution will meet the requirement (Column H) may be considered non-responsive and may be the basis for rejecting the Bidder's proposal. |
| The Bidder must not modify the format, add columns or include explanatory text to its response or otherwise change the format or content of EXHIBIT B: FUNCTIONAL AND NON-FUNCTIONAL REQUIREMENTS. |
| The following provides a description of each column and the instructions for completing +EXHIBIT B: FUNCTIONAL AND NON-FUNCTIONAL REQUIREMENTS. |
| Column A: ID specifies the requirement’s identification number |
| Column B: Business Focus Area(s) specifies the requirement’s business area focus |
| Column C: Requirement provides text to describe the requirement. |
| Column D: Classification specifies if the requirement is Mandatory, Mandatory Scored, Mandatory Optional, or Optional |
| Column E: Out-of-the-Box? Bidder places a checkmark to indicate the requirement is met out-of-the-box (pre-packaged functionality) |
| Column F: Customization? Bidder places a checkmark to indicate the requirement is met with customization |
| Column G: Extension? Bidder places a checkmark to indicate the requirement is met through use of an extension |
| Column H: Will Solution Meet Requirement? Bidder selects Yes or No from drop-down list to specify whether or not the solution meets the requirement |
| Column I: Level of Effort Bidder selects an item from the drop-down list to indicate the amount of effort required to meet the requirement. |
WS3A Requirements
| Requirement ID | Business Focus Area(s) | Description | Requirement Type | Classification | Out of the Box | Customization | Extension | Will Solution Meet Requirements (Yes/No) |
| Functional | ||||||||
| W3.FR1.1 | Case Management | The solution shall present authorized Department users with a consolidated view of a customer’s interactions across all Department-configured contact channels, including display of interaction date and time, channel, interaction type, disposition or outcome, and linkage to the related case, transaction, or document where applicable. | Functional | Mandatory | FALSE | FALSE | FALSE | |
| W3.FR1.2 | The solution must ensure that the consolidated view captures each interaction’s unique identifier, source channel or system, and the timestamp of its most recent update. | Functional | Mandatory | FALSE | FALSE | FALSE | ||
| W3.FR1.3 | The solution shall support filtering, sorting, and search of the consolidated interaction history by Department-configured criteria, including return results within Department-defined performance thresholds under expected workload; and shall record the criteria applied, result count, and response-time metrics for each query user history. | Functional | Mandatory | FALSE | FALSE | FALSE | ||
| W3.FR1.4 | The solution must to enable back-end functionality to present to internal Department users a single view of a customer’s interactions across all contact channels (including but not limited to text, phone, email, messaging, chat, and in-person interactions). | Functional | Mandatory | FALSE | FALSE | FALSE | ||
| W3.FR1.5 | The solution must provide "case management style" functionality to combine and/or link all data held for a record, from initial application to include all subsequent activity and/or historic data held for the record holder. | Functional | Mandatory | FALSE | FALSE | FALSE | ||
| W3.FR1.6 | The solution shall combine and link all Department-held data for a record into a longitudinal record view. | Functional | Mandatory | FALSE | FALSE | FALSE | ||
| W3.FR1.7 | The solution must allow the record view to include, initial application through subsequent activity and historical data. | Functional | Mandatory | FALSE | FALSE | FALSE | ||
| W3.FR1.8 | The solution must allow the historical data to include association of transactions, documents, communications, and status changes to the record holder using Department-defined identifiers. | Functional | Mandatory | FALSE | FALSE | FALSE | ||
| W3.FR1.9 | The solution shall validate record linkages and prevent creation of orphaned or duplicate associations, including generation of an exception output for linkage failures with remediation status; and shall record the integrity rule evaluated, failure reason, affected identifiers, and processing timestamp. | Functional | Mandatory | FALSE | FALSE | FALSE | ||
| W3.FR1.10 | The solution shall present a chronological timeline of the longitudinal record that distinguishes record types, status transitions, and effective dates, including navigation between related records without duplicating source data. | Functional | Mandatory | FALSE | FALSE | FALSE | ||
| W3.FR1.11 | The solution shall record the timeline event identifier, event type, effective date, and source record identifier. | Functional | Mandatory | FALSE | FALSE | FALSE | ||
| W3.FR1.12 | The solution must provide the back-end functionality to retrieve and display for internal Department staff the DL/ID record and prior contact history based on an inquiry. | Functional | Mandatory | FALSE | FALSE | FALSE | ||
| W3.FR1.14 | The solution shall retrieve and display the DL/ID record and associated prior contact history for authorized Department staff based on an inquiry, including record status, key identifying attributes, and a summarized list of prior contacts with channel and date and time; and shall record the inquiry criteria submitted, records returned, and retrieval timestamp. | Functional | Mandatory | FALSE | FALSE | FALSE | ||
| W3.FR1.15 | The solution shall support Department-configured inquiry criteria and provide an export of displayed inquiry results in a Department-approved format when authorized, including security-trim results to the user’s authorized access scope; and shall record the query parameters, authorization outcome, and export event metadata. | Functional | Mandatory | FALSE | FALSE | FALSE | ||
| W3.FR1.16 | The solution must provide the functionality for notes or comments to document customer interactions for all service delivery channels and customer contact history. | Functional | Mandatory | FALSE | FALSE | FALSE | ||
| W3.FR1.17 | The solution shall capture notes or comments that document customer interactions across all Department-configured service delivery channels, including association to the customer or case record, channel, note type, author, and creation date and time; and shall record the note identifier, author identifier, creation timestamp, and associated record identifier. | Functional | Mandatory | FALSE | FALSE | FALSE | ||
| W3.FR1.18 | The solution shall preserve notes as append-only entries and allow addenda as separately time-stamped entries, including Department-configured categories and required fields to ensure consistent documentation; and shall record the addendum identifier, linkage to the original note, and category values used. | Functional | Mandatory | FALSE | FALSE | FALSE | ||
| W3.FR1.19 | The solution shall support search and retrieval of notes by Department-configured criteria and display notes in the context of the related record, including return results within Department-defined performance thresholds; and shall record the search criteria, result count, and response-time metrics. | Functional | Mandatory | FALSE | FALSE | FALSE | ||
| W3.FR2.1 | Case Management | The solution shall route record updates through a Department-configured change control workflow with defined statuses, approver roles, and required decision criteria, including support for approvals, rejections, and requests for additional information; and shall record the workflow instance identifier, current status, approver decision, and decision timestamp. | Functional | Mandatory | FALSE | FALSE | FALSE | |
| W3.FR2.2 | The solution shall prevent unauthorized or premature application of pending updates until required approvals are completed, including version history for proposed and approved values with effective dates; and shall record the before-and-after values, approval chain, and effective date applied. | Functional | Mandatory | FALSE | FALSE | FALSE | ||
| W3.FR2.3 | The solution shall provide a queue and reporting view for pending and completed approvals by status and aging and support export of approval activity; and shall record the approval queue snapshot identifier, aging calculation timestamp, and export metadata. | Functional | Mandatory | FALSE | FALSE | FALSE | ||
| W3.FR2.4 | The solution must provide the ability to support exception processing and deviations from standard business rules for authorized users. | Functional | Mandatory | FALSE | FALSE | FALSE | ||
| W3.FR2.5 | The solution must provide a workflow for change control and approval of record updates. | Functional | Mandatory | FALSE | FALSE | FALSE | ||
| W3.FR2.6 | The solution shall allow authorized Department users to initiate and process exception actions that deviate from standard business rules based on Department-configured exception types, including required reason codes, supporting documentation references where applicable, and effective date or duration; and shall record the exception identifier, exception type, reason code, initiator identifier, and initiation timestamp. | Functional | Mandatory | FALSE | FALSE | FALSE | ||
| W3.FR2.7 | The solution shall apply exception outcomes to downstream processing and enforce approvals when required by Department-configured thresholds or exception categories; and shall record the approval decision, approver identifier, approval timestamp, and the transaction identifiers affected. | Functional | Mandatory | FALSE | FALSE | FALSE | ||
| W3.FR2.8 | The solution shall provide an exception audit and reporting output that supports review by authorized oversight roles, including filtering by exception type, user, date range, and disposition; and shall record the report parameters, record count, and report generation timestamp; the report shall allow electronic and printing capability. | Functional | Mandatory | FALSE | FALSE | FALSE | ||
| W3.FR2.9 | The solution must provide the functionality to generate notices and correspondence that contain information for events within the DL workflow. | Functional | Mandatory | FALSE | FALSE | FALSE | ||
| W3.FR2.10 | The solution shall generate notices and correspondence for Department-defined events within the DL/ID workflow, including association to the triggering event, customer identifier, and applicable transaction or case identifier; and shall record the notice identifier, trigger event identifier, generation timestamp, and template version used. | Functional | Mandatory | FALSE | FALSE | FALSE | ||
| W3.FR2.11 | The solution shall support Department-configured templates with variable substitution, channel selection, and language variants (example: foreign language related to notices that are sent out and in different portals) where required and preserve a content snapshot of each generated notice; and shall record the template identifier, variable values applied, channel selected, and content snapshot reference. | Functional | Mandatory | FALSE | FALSE | FALSE | ||
| W3.FR2.12 | The solution shall track delivery, reprint, and resend actions for electronic and paper notices and provide an exception output for failures, including delivery status timestamps and retry outcomes; and shall record the delivery status history, retry attempts, and failure reason codes. | Functional | Mandatory | FALSE | FALSE | FALSE | ||
| W3.FR2.13 | The solution must enable case management functionality to allow internal Department users to make comments, record instances of changes, or note customer contacts that do not impact the driving record (such as transfers, contact points, received fax documents, email or by further communication channels), and internally share case management data to authorized Department users. | Functional | Mandatory | FALSE | FALSE | FALSE | ||
| W3.FR3.1 | Commercial Driving Tests | The solution shall capture notes or comments that document customer interactions across all Department-configured service delivery channels, including association to the customer or case record, channel, note type, author, and creation date and time; and shall record the note identifier, author identifier, creation timestamp, and associated record identifier, for test (written, knowledge, drive). | Functional | Mandatory | FALSE | FALSE | FALSE | |
| W3.FR3.2 | The solution shall preserve notes as append-only entries and allow addenda as separately time-stamped entries, including Department-configured categories and required fields to ensure consistent documentation; and shall record the addendum identifier, linkage to the original note, and category values used. Shall capture the required data elements and store in the new system. | Functional | Mandatory | FALSE | FALSE | FALSE | ||
| W3.FR3.3 | The solution shall provide an electronic verification process for businesses that are enrolled in the Employer Testing Program; upon verification of the ETP business, the system shall accept or deny the results provided. Shall capture the required data elements and store in the new system. | Functional | Mandatory | FALSE | FALSE | FALSE | ||
| W3.FR3.4 | The solution shall allow for electronic or paper submission of commercial driver license drive test results from external stakeholders. The solution shall provide ability for customer to submit required documentation via online, remote, etc. Shall capture the required data elements and store in the new system. | Functional | Mandatory | FALSE | FALSE | FALSE | ||
| W3.FR3.5 | The solution must provide the back-end functionality to support proof of completion of commercial drive test process (written, knowledge, drive) and checks of the employee/applicant to validate issuance of a commercial driver license (DL170). | Functional | Mandatory | FALSE | FALSE | FALSE | ||
| W3.FR3.6 | The solution shall manage restrictions on commercial driving licenses - including special performance evaluations and waivers, including Department-configured business rules, data elements, and validation criteria where applicable; and shall record the transaction or record identifier, processing status, and processing timestamp. |
| Note: See document in the bidders library for department configured business rules, however, the criteria is subject to change. | Functional | Mandatory | FALSE | FALSE | FALSE | |||
| W3.FR3.7 | The solution must provide the back-end functionality to manage restrictions on commercial driving licenses. | Functional | Mandatory | FALSE | FALSE | FALSE | ||
| W3.FR3.8 | The solution shall restrict access to updating commercial drive test results only to authorized users, including Department-configured business rules, data elements, and validation criteria where applicable; and shall record the transaction or record identifier, processing status, and processing timestamp. |
| Note: See document in the bidders library for department configured business rules, however, the criteria is subject to change. | Functional | Mandatory | FALSE | FALSE | FALSE | |||
| W3.FR3.9 | The solution must provide the back-end functionality to restrict access to updating commercial drive test results only to authorized users. | Functional | Mandatory | FALSE | FALSE | FALSE | ||
| W3.FR3.10 | The solution shall enable commercial drive examiners to input federally mandated information along with pass/fail results, including Department-configured business rules, data elements, and validation criteria where applicable; and shall record the transaction or record identifier, processing status, and processing timestamp. |
| Note: See document in the bidders library for department configured business rules, however, the criteria is subject to change. | Functional | Mandatory | FALSE | FALSE | FALSE | |||
| W3.FR3.11 | The solution must provide the back-end functionality to enable commercial drive examiners to input federally mandated information. | Functional | Mandatory | FALSE | FALSE | FALSE | ||
| W3.FR3.12 | The solution must allow functionality to require the commercial driver's license (CDL) applicants to complete a federally mandated training course and exam. | Functional | Mandatory | FALSE | FALSE | FALSE | ||
| W3.FR3.13 | The solution must follow the Department-configured business rules, data elements, and validation criteria where applicable; and shall record the transaction or record identifier, processing status, and processing timestamp. |
| Note: See document in the bidders library for department configured business rules, however, the criteria is subject to change. | Functional | Mandatory | FALSE | FALSE | FALSE | |||
| W3.FR4.1 | Commercial Driving Tests | The solution shall enable automated validation steps, workflow progress, and upload/storage of documentation to show proof of passing commercial drive tests under the Employer Testing Program (DL170), including validation of required document types and completeness rules defined by the Department; and shall record the document identifier, document type, capture channel, validation outcome, and validation timestamp. | Functional | Mandatory | FALSE | FALSE | FALSE | |
| W3.FR4.2 | The Solution must manage test content, scoring, eligibility checks, and the recording of all testing results and must route, assign, and automate multi-branch workflows with support for exceptions, escalations, and queue management. | Functional | Mandatory | FALSE | FALSE | FALSE | ||
| W3.FR4.3 | The solution must provide the back-end functionality to enable automated validation steps, workflow progress, and upload/storage of documentation to show proof of passing commercial drive tests under the Employer Testing Program (DL170). | Functional | Mandatory | FALSE | FALSE | FALSE | ||
| W3.FR4.4 | The solution shall support future third-party conducted commercial drive tests and testing, including Department-configured business rules, data elements, and validation criteria where applicable; and shall record the transaction or record identifier, processing status, and processing timestamp. |
| Note: See document in the bidders library for department configured business rules, however, the criteria is subject to change. | Functional | Mandatory | FALSE | FALSE | FALSE | |||
| W3.FR4.5 | The solution shall provide secure, scalable back-end services and data structures to onboard, credential, and integrate third-party testing providers to schedule, conduct, and submit results for commercial drive tests (CDL). | Functional | Mandatory | FALSE | FALSE | FALSE | ||
| W3.FR4.6 | The solution shall provide the back-end to provide general and ad-hoc reports related to the Employer Testing Program (ETP) applicants and transaction status, including Department-configured business rules, data elements, and validation criteria where applicable; and shall record the transaction or record identifier, processing status, and processing timestamp. |
| Note: See document in the bidders library for department configured business rules, however, the criteria is subject to change. | Functional | Mandatory | FALSE | FALSE | FALSE | |||
| W3.FR4.7 | The solution shall provide secure, performant back‑end services, data models, and query capabilities to generate general (predefined) and ad‑hoc (user-defined) reports covering Employer Testing Program (ETP) applicants. | Functional | Mandatory | FALSE | FALSE | FALSE | ||
| W3.FR5.1 | DL/ID Transaction Processing | The solution shall support issuance and lifecycle management for digital credentials, including digital driver licenses and digital identification cards, including Department-configured enrollment, identity proofing steps, and supported mobile operating systems and device types; and shall record the digital credential identifier, device or platform type, enrollment status, and enrollment timestamp. | Functional | Mandatory | FALSE | FALSE | FALSE | |
| W3.FR5.2 | The solution must process and generate all DL/ID indicia, including temporary and interim documents, through validated back-end issuance services. In addition, the Solution must securely capture, store, index, validate, and retrieve documents, including secure paper and system-generated documents. | Functional | Mandatory | FALSE | FALSE | FALSE | ||
| W3.FR5.3 | The solution must provide the functionality to support digital Driver's License (DL), digital Identification (ID) card, and the Department Wallet workflow to allow customers to obtain a digital DL/and ID card via smartphones or digital alternatives (Mobile DL) across multiple operating systems. | Functional | Mandatory | FALSE | FALSE | FALSE | ||
| W3.FR5.4 | The solution shall evaluate eligibility and issue the appropriate DL/ID credential type based on Department-defined criteria and conditions, including validation of required documents, qualifications, and transaction completion channel (for example: online, remote, or office appointment); and shall record the criteria evaluated, pass or fail outcomes, document verification results, and issuance decision timestamp. | Functional | Mandatory | FALSE | FALSE | FALSE | ||
| W3.FR5.5 | The solution must process and generate all DL/ID indicia, including temporary and interim documents, through validated back-end issuance services. In addition, the Solution must securely capture, store, index, validate, and retrieve documents, including secure paper and system-generated documents. | Functional | Mandatory | FALSE | FALSE | FALSE | ||
| W3.FR5.6 | The solution must provide the back-end functionality to issue original DL/ID card types. (refer to Bidders Library) | Functional | Mandatory | FALSE | FALSE | FALSE | ||
| W3.FR5.7 | The solution shall support additional types of ID cards and additional types of driver licenses. (refer to Bidders Library) | Functional | Mandatory | FALSE | FALSE | FALSE | ||
| W3.FR5.8 | The solution must provide the back-end functionality to support additional types of ID cards and additional types of driver licenses. | Functional | Mandatory | FALSE | FALSE | FALSE | ||
| W3.FR5.9 | The solution shall enable eligible customers to submit an online request for original, renewal, and duplicate/replacement DL/ID cards, including Department-configured business rules, data elements, and validation criteria where applicable; and shall record the transaction or record identifier, processing status, and processing timestamp. |
| Note: See document in the bidders library for department configured business rules, however, the criteria is subject to change. | Functional | Mandatory | FALSE | FALSE | FALSE | |||
| W3.FR5.10 | The solution must provide the back-end functionality to enable customers to submit an online request for original, renewal, and duplicate/replacement DL/ID cards. | Functional | Mandatory | FALSE | FALSE | FALSE | ||
| W3.FR5.11 | The solution shall evaluate eligibility and issue the appropriate DL/ID credential type based on Department-defined criteria and conditions, including validation of required documents, qualifications, and transaction completion channel (for example: online, remote, or office appointment); and shall record the criteria evaluated, pass or fail outcomes, document verification results, and issuance decision timestamp. | Functional | Mandatory | FALSE | FALSE | FALSE | ||
| W3.FR5.12 | The solution shall generate and deliver indicia for issued credentials in Department-approved formats and channels with clear status tracking, including electronic delivery (for example: email or mobile credential) and hard-copy fulfillment when applicable; and shall record the credential identifier, delivery channel, issuance status, and delivery status timestamp. | Functional | Mandatory | FALSE | FALSE | FALSE | ||
| W3.FR5.13 | The solution must provide the back-end functionality to issue hard copy original DL/ID card types, when a transaction has been completed at an office appointment or online/remote. | Functional | Mandatory | FALSE | FALSE | FALSE | ||
| W3.FR5.14 | The solution must provide the back-end functionality to issue original DL/ID card types electronically via Mobile DL, the Department Wallet, and hard copy. | Functional | Mandatory | FALSE | FALSE | FALSE | ||
| W3.FR5.15 | The solution must provide the back-end functionality to issue renewals, duplicates/replacements of all DL and ID card types, when all requirements are met online, remotely, at headquarters, or through field offices; the system must issue indicia electronically via e-mail, Mobile DL, the Department Wallet, and hard copy. | Functional | Mandatory | FALSE | FALSE | FALSE | ||
| W3.FR5.16 | The solution shall support issuance and lifecycle management for digital credentials, including digital driver licenses and digital identification cards, including Department-configured enrollment, identity proofing steps, and supported mobile operating systems and device types; and shall record the digital credential identifier, device or platform type, enrollment status, and enrollment timestamp. | Functional | Mandatory | FALSE | FALSE | FALSE | ||
| W3.FR5.17 | The solution shall support activation, suspension, revocation, and reissuance of digital credentials based on Department-defined events and eligibility changes, including status synchronization between digital and physical credential views where applicable; and shall record the status change event, prior status, new status, and effective date and time. | Functional | Mandatory | FALSE | FALSE | FALSE | ||
| W3.FR5.18 | The solution must provide the back-end functionality to issue a temporary license for all DL types, when all requirements are met online, remotely, at headquarters, or through field offices; the system must issue indicia electronically via e-mail, Mobile DL, the Department Wallet, and hard copy. | Functional | Mandatory | FALSE | FALSE | FALSE | ||
| W3.FR5.19 | The solution must provide the back-end functionality to issue an interim license for all DL types, when all requirements are met online, remotely, at headquarters, or through field offices; the system must issue indicia electronically via e-mail, Mobile DL, the Department Wallet, and hard copy. | Functional | Mandatory | FALSE | FALSE | FALSE | ||
| W3.FR5.20 | The solution shall evaluate eligibility and issue the appropriate DL/ID credential type based on Department-defined criteria and conditions, including validation of required documents, qualifications, and transaction completion channel (for example: online, remote, or office appointment); and shall record the criteria evaluated, pass or fail outcomes, document verification results, and issuance decision timestamp. | Functional | Mandatory | FALSE | FALSE | FALSE | ||
| W3.FR5.21 | The solution shall apply Department-defined termination dates and eligibility constraints to interim or temporary credentials and prevent use of expired credentials; and shall record the termination date assigned, rule source, and expiration enforcement outcome. | Functional | Mandatory | FALSE | FALSE | FALSE | ||
| W3.FR5.22 | The solution must provide the back-end functionality to verify and issue interim and temporary licenses and ID cards with specific termination dates, based on criteria that may include legal presence documentation and/or medical conditions (see examples in Bidders' Library). | Functional | Mandatory | FALSE | FALSE | FALSE | ||
| W3.FR5.23 | The solution must provide the back-end functionality to issue Instruction Permits both electronically and in hard-copy format based on verification of submitted documents and qualifications for all classes of licenses (refer to Bidders Library). | Functional | Mandatory | FALSE | FALSE | FALSE | ||
| W3.FR5.24 | The solution must provide the back-end functionality to issue an Instruction Permit for minors at a field office, headquarters, or remotely, based on requirements being met. | Functional | Mandatory | FALSE | FALSE | FALSE | ||
| W3.FR5.25 | The solution shall accept and evaluate permit applications and issue permits when Department-defined requirements are met, including validation of applicant eligibility, required documents, and completion of prerequisite steps. | Functional | Mandatory | FALSE | FALSE | FALSE | ||
| W3.FR5.26 | The solution shall record the application identifier, eligibility checks performed, decision outcome, and decision timestamp. | Functional | Mandatory | FALSE | FALSE | FALSE | ||
| W3.FR5.27 | The solution shall issue permits in electronic and hard-copy formats where applicable and associate the permit to the customer record, including a unique permit identifier, effective date, and expiration date; and shall record the permit identifier, issue timestamp, effective date, and expiration date. | Functional | Mandatory | FALSE | FALSE | FALSE | ||
| W3.FR5.28 | The solution must provide the back-end functionality to issue a permit for adults at a field office, headquarters, or remotely, based on requirements being met. | Functional | Mandatory | FALSE | FALSE | FALSE | ||
| W3.FR5.29 | The solution shall evaluate applications and issue DL, temporary DL, and Restricted types of DL based on defined criteria (see examples in Bidders' Library). | Functional | Mandatory | FALSE | FALSE | FALSE | ||
| W3.FR5.30 | The solution shall evaluate eligibility and issue the appropriate DL/ID credential type based on Department-defined criteria and conditions, including validation of required documents, qualifications, and transaction completion channel (for example: online, remote, or office appointment). | Functional | Mandatory | FALSE | FALSE | FALSE | ||
| W3.FR5.31 | The solution shall record the criteria evaluated, pass or fail outcomes, document verification results, and issuance decision timestamps. | Functional | Mandatory | FALSE | FALSE | FALSE | ||
| W3.FR5.32 | The solution must provide the back-end functionality to change or correct the issuance of indicia for physical and electronic identification elements (examples are name change/correction, address change, demographic changes) for all DL/ID card types. | Functional | Mandatory | FALSE | FALSE | FALSE | ||
| W3.FR5.33 | The solution shall perform name/address/demographic information changes using the single customer portal to update all the Department-related records. | Functional | Mandatory | FALSE | FALSE | FALSE | ||
| W3.FR5.34 | The Solution must maintain comprehensive tracking and status management for all driver record updates across DMV programs and must securely capture, store, index, validate, and retrieve documents, including secure paper and system-generate documents and shall generate notices and correspondence for Department-defined events within the DL/ID workflow, including association to the triggering event, customer identifier, and applicable transaction or case identifier; and shall record the notice identifier, trigger event identifier, generation timestamp, and template version used. | Functional | Mandatory | FALSE | FALSE | FALSE | ||
| W3.FR5.35 | The solution shall track delivery status for Department-generated notices and notifications, including queued, sent, delivered, and failed states with timestamps and retry outcomes, and provide an exception output for undelivered messages so the Department can measure and validate performance and correctness. | Functional | Mandatory | FALSE | FALSE | FALSE | ||
| W3.FR5.36 | The solution shall support Department-configured templates with variable substitution, channel selection, and language variants where required and preserve a content snapshot of each generated notice; and shall record the template identifier, variable values applied, channel selected, and content snapshot reference. | Functional | Mandatory | FALSE | FALSE | FALSE | ||
| W3.FR5.37 | The solution shall track delivery, reprint, and resend actions for notices and provide an exception output for failures, including delivery status timestamps and retry outcomes; and shall record the delivery status history, retry attempts, and failure reason codes. | Functional | Mandatory | FALSE | FALSE | FALSE | ||
| W3.FR5.38 | The solution must provide the back-end functionality to send to customers with an incomplete transaction electronic or paper notices on a pre-determined schedule to remind them of outstanding items/actions needed to complete the transaction. | Functional | Mandatory | FALSE | FALSE | FALSE | ||
| W3.FR5.39 | The solution must provide the back-end functionality to maintain multiple addresses (including but not limited to residential, mailing, email, and instant messaging addresses) concurrently on a customer record. | Functional | Mandatory | FALSE | FALSE | FALSE | ||
| W3.FR5.40 | The solution shall maintain multiple options for a customer record's gender designation, including Department-configured business rules, data elements, and validation criteria where applicable; and shall record the transaction or record identifier, processing status, and processing timestamp. |
| Note: See document in the bidders library for department configured business rules, however, the criteria is subject to change. | Functional | Mandatory | FALSE | FALSE | FALSE | |||
| W3.FR5.41 | The solution must provide the back-end functionality to maintain multiple options for a customer record's gender designation. | Functional | Mandatory | FALSE | FALSE | FALSE | ||
| W3.FR5.42 | The solution must provide back-end functionality supporting a history of changes to a customer record's data, including but not limited to name, addresses, and other information submitted on a customer application. | Functional | Mandatory | FALSE | FALSE | FALSE | ||
| W3.FR5.43 | The solution must provide the back-end functionality to save incomplete transactions with an indicator/system flag and enable users to return to the incomplete transaction at a later time. | Functional | Mandatory | FALSE | FALSE | FALSE | ||
| W3.FR5.44 | The solution must provide the back-end functionality to maintain rules for Restriction applicability (see examples in Bidders' Library). | Functional | Mandatory | FALSE | FALSE | FALSE | ||
| W3.FR5.45 | The solution must provide the back-end functionality to specify workflows verifying the need for retaking of all class DL and ID card photos, issuing notifications for retaking photos, and incorporating the retaken photo image. | Functional | Mandatory | FALSE | FALSE | FALSE | ||
| W3.FR5.46 | The solution must provide the back-end functionality to process Suspension on a record based on criteria (see examples in Bidders Library). | Functional | Mandatory | FALSE | FALSE | FALSE | ||
| W3.FR5.47 | The solution must provide the back-end functionality to process Revocation of privileges on a record based on criteria (see examples in Bidders Library). | Functional | Mandatory | FALSE | FALSE | FALSE | ||
| W3.FR5.48 | The solution must provide the back-end functionality to process Reinstatement of privileges on a record based on criteria (see examples in Bidders Library). | Functional | Mandatory | FALSE | FALSE | FALSE | ||
| W3.FR5.49 | The solution must provide the back-end functionality to process Cancellation of all DL/ID card types on a record based on criteria (see examples in Bidders Library). | Functional | Mandatory | FALSE | FALSE | FALSE | ||
| W3.FR5.50 | The solution must provide the back-end functionality to allow users to submit transactions in real time and provide any real-time error notification to the user. | Functional | Mandatory | FALSE | FALSE | FALSE | ||
| W3.FR5.51 | The solution must provide the back-end functionality to issue via a variety of channels (including but not limited to phone, online electronically, and in-office) for all classes of DL. | Functional | Mandatory | FALSE | FALSE | FALSE | ||
| W3.FR5.52 | The solution shall capture data without field -level limitations. For example, the solution must allow a user to enter a true full name to include number, punctuation, and symbol characters (X Æ A-Xii, hyphens, and apostrophes) for name elements of First, Middle, Last, and Suffix, including Department-configured business rules, data elements, and validation criteria where applicable; and shall record the transaction or record identifier, processing status, and processing timestamp. |
| Note: See document in the bidders library for department configured business rules, however, the criteria is subject to change. | Functional | Mandatory | FALSE | FALSE | FALSE | |||
| W3.FR5.53 | The solution must provide the back-end functionality to capture data without field -level limitations. | Functional | Mandatory | FALSE | FALSE | FALSE | ||
| W3.FR5.54 | The solution must provide the back-end functionality to enable a customer to request and purchase a copy of their own driving record. | Functional | Mandatory | FALSE | FALSE | FALSE | ||
| W3.FR5.55 | Solution must accept, store, share acceptable data following regulatory format in name field for CDLIS messaging. | Functional | Mandatory | FALSE | FALSE | FALSE | ||
| W3.FR5.56 | The solution must provide the back-end functionality to enable a customer to request and purchase a copy of a licensed driver's driving record. | Functional | Mandatory | FALSE | FALSE | FALSE | ||
| W3.FR5.57 | The solution must provide the back-end functionality to enable a customer to request and purchase a certified copy (as indicated by a watermark, official seal, logo, or other graphic element) of a driving record. The solution must generate the certified copy of the record upon completion of the transaction. | Functional | Mandatory | FALSE | FALSE | FALSE | ||
| W3.FR5.58 | The solution must provide the back-end functionality to record results of DL background checks against specified criteria for the purposes of tracking and compliance. For example, DL background checks must be performed against specified criteria for hazardous materials-related commercial DLs, ambulance DLs, and Special Certificates. | Functional | Mandatory | FALSE | FALSE | FALSE | ||
| W3.FR5.59 | The solution must provide the back-end functionality to pre-populate, prior to an in-person visit, all DL and ID card applications with a customer's submitted online data. | Functional | Mandatory | FALSE | FALSE | FALSE | ||
| W3.FR5.60 | The solution must provide the back-end functionality to allow in-person and/or remote completion of all DL and ID applications. | Functional | Mandatory | FALSE | FALSE | FALSE | ||
| W3.FR5.61 | The solution must provide the back-end functionality to allow the Department products and services (indicia) to be printed by the customer following successful transaction processing. For example, as the result of an online self-service transaction, a self-service kiosk (SSK) transaction, by authorized third party, or a Field Office window transaction. | Functional | Mandatory | FALSE | FALSE | FALSE | ||
| W3.FR5.62 | The solution must provide the back-end functionality to allow a customer to utilize self-service to see the status (for example, Mail Date Status (date mailed or returned), Valid, Suspended, Probation, Revoked) of their license. | Functional | Mandatory | FALSE | FALSE | FALSE | ||
| W3.FR5.63 | The solution shall display actions a customer must complete if their license is pending, or in order for their license to be in good standing. Including Department-configured business rules, data elements, and validation criteria where applicable; and shall record the transaction or record identifier, processing status, and processing timestamp. See Bidders Library for additional details on various license statuses | Functional | Mandatory | FALSE | FALSE | FALSE | ||
| W3.FR5.64 | The solution must provide the back-end functionality to notify users when DL/ID is incomplete or pending. | Functional | Mandatory | FALSE | FALSE | FALSE | ||
| W3.FR5.65 | The solution shall prevent transaction completion until requirements are met, including Department-configured business rules, data elements, and validation criteria where applicable; and shall record the transaction or record identifier, processing status, and processing timestamp. |
| Note: See document in the bidders library for department configured business rules, however, the criteria is subject to change. | Functional | Mandatory | FALSE | FALSE | FALSE |
| W3.FR5.66 | The solution shall allow for the removal of any Restrictions on the DL, including Department-configured business rules, data elements, and validation criteria where applicable; and shall record the transaction or record identifier, processing status, and processing timestamp. |
| Note: See document in the bidders library for department configured business rules, however, the criteria is subject to change. | Functional | Mandatory | FALSE | FALSE | FALSE | |||
| W3.FR5.67 | The solution shall include validation requirements to ensure that restriction removals occur only by authorized processes. | Functional | Mandatory | FALSE | FALSE | FALSE | ||
| W3.FR5.68 | The solution must provide the back-end functionality to allow update to the DL. | Functional | Mandatory | FALSE | FALSE | FALSE | ||
| W3.FR5.69 | The solution shall allow for the conversion of different license types (for example, from a federally non-compliant (FNC) to REAL ID), including Department-configured business rules, data elements, and validation criteria where applicable; and shall record the transaction or record identifier, processing status, and processing timestamp. |
| Note: See document in the bidders library for department configured business rules, however, the criteria is subject to change. | Functional | Mandatory | FALSE | FALSE | FALSE | |||
| W3.FR5.70 | The solution must provide the back-end functionality to allow for the downgrade/change of classes from a commercial license to a non-commercial license. | Functional | Mandatory | FALSE | FALSE | FALSE | ||
| W3.FR5.71 | The solution must provide the back-end functionality to allow for the modification of over 100 different license class types. | Functional | Mandatory | FALSE | FALSE | FALSE | ||
| W3.FR5.72 | The solution must provide the back-end functionality to allow for a licensee's record to be converted from one license class type to a different license class type. | Functional | Mandatory | FALSE | FALSE | FALSE | ||
| W3.FR5.73 | The solution must provide the back-end functionality to maintain and display prior versions of the DL/ID record. | Functional | Mandatory | FALSE | FALSE | FALSE | ||
| W3.FR5.74 | The solution must provide the back-end functionality to allow ad-hoc customer requests for eligibility to renew by mail. | Functional | Mandatory | FALSE | FALSE | FALSE | ||
| W3.FR5.75 | The solution must provide the back-end functionality to notify drivers that they must renew their DL. | Functional | Mandatory | FALSE | FALSE | FALSE | ||
| W3.FR5.76 | The solution must provide the back-end functionality to notify customers they must renew their ID card. | Functional | Mandatory | FALSE | FALSE | FALSE | ||
| W3.FR5.77 | The solution must prompt the customer to complete actions based on the current status of their driving record/ID card, including Department-configured business rules, data elements, and validation criteria where applicable; and shall record the transaction or record identifier, processing status, and processing timestamp. |
| Note: See document in the bidders library for department configured business rules, however, the criteria is subject to change. | Functional | Mandatory | FALSE | FALSE | FALSE | |||
| W3.FR5.78 | The solution must provide the back-end functionality to maintain business rules regarding actions required to renew a driver's license/ID card. | Functional | Mandatory | FALSE | FALSE | FALSE | ||
| W3.FR5.79 | The solution shall enable internal users to track status and updates for all types of DL and ID card records, including Department-configured business rules, data elements, and validation criteria where applicable; and shall record the transaction or record identifier, processing status, and processing timestamp. |
| Note: See document in the bidders library for department configured business rules, however, the criteria is subject to change. | Functional | Mandatory | FALSE | FALSE | FALSE | |||
| W3.FR5.80 | The solution must provide the back-end functionality to enable internal users to track status and updates for all types of DL and ID card records. | Functional | Mandatory | FALSE | FALSE | FALSE | ||
| W3.FR5.81 | The solution shall enable users to track status and updates for applications, .02 PAS Action, Admin Per Se, Other Address, X Number types of updates, photo retakes, proof updates, updates of route codes, mandatory actions, discretionary actions, FRs, APS comments, suspense records, RX/Term/set-asides, work order updates and miscellaneous driver record updates. | Functional | Mandatory | FALSE | FALSE | FALSE | ||
| W3.FR5.82 | The solution must provide the back-end functionality to enable external users to track status and updates for DL and ID card records appropriate to their user role permissions. | Functional | Mandatory | FALSE | FALSE | FALSE | ||
| W3.FR5.83 | The solution must provide the back-end functionality to enable users to electronically update Mail Date Status for all DL and ID cards. | Functional | Mandatory | FALSE | FALSE | FALSE | ||
| W3.FR5.84 | The solution shall enable users to electronically update Mail Date Status (date mail returned as undeliverable mail) for all DL and ID cards. | Functional | Mandatory | FALSE | FALSE | FALSE | ||
| W3.FR5.85 | The solution shall allow auto-update of the mail date file for all DL/ID and SP cards, | Functional | Mandatory | FALSE | FALSE | FALSE | ||
| W3.FR5.86 | The solution shall record behind-the-wheel drive test results (pass/fail/waive/satisfied) (based on conditions being met). | Functional | Mandatory | FALSE | FALSE | FALSE | ||
| W3.FR5.87 | The solution shall provide functionality to issue unique DL/ID card numbers based on . Department-defined criteria and conditions. | Functional | Mandatory | FALSE | FALSE | FALSE | ||
| W3.FR5.88 | The solution shall generate and deliver indicia for issued credentials in Department-approved formats and channels with clear status tracking, including electronic delivery (for example: email or mobile credential) and hard-copy fulfillment when applicable; and shall record the credential identifier, delivery channel, issuance status, and delivery status timestamps, so verification evidence is available for compliance and operational oversight. | Functional | Mandatory | FALSE | FALSE | FALSE | ||
| W3.FR5.89 | The solution shall issue indicia allocating a new serial #s for Special Certificates. | Functional | Mandatory | FALSE | FALSE | FALSE | ||
| W3.FR5.90 | The solution must provide the back-end functionality to mask certain confidential information on the DL/ID card record based on an record indicator selected by the internal user. | Functional | Mandatory | FALSE | FALSE | FALSE | ||
| W3.FR5.91 | The solution shall support confidential addresses, including: |
* Automating the transfer of data from the qualifying agencies regarding who is eligible for a confidential address
* Automating the selection of a record indicator to mask address information on the eligible DL/ID card record
| Functional | Mandatory | FALSE | FALSE | FALSE | |||
| W3.FR5.92 | The solution must provide the back-end functionality to combine DL/ID card numbers, and history of DL/ID card numbers, when multiple DL/ID card numbers have been issued to a single individual. | Functional | Mandatory | FALSE | FALSE | FALSE | |
| W3.FR5.93 | The solution shall support the consolidation of multiple DL/ID card numbers issued to a single individual including automating the identification and combination of DL/ID card numbers based on Department-configured business rules, identity matching criteria. Preserve full history and maintain the relationship between the active DL/ID number and all prior or duplicate DL/ID numbers, Ensure all associated records, transactions, and data elements tied to prior or duplicate DL/ID card numbers are retained properly linked and consolidated to the individual record. Shall record processing status, timestamp, user, and traceability. |
| Note: See document in the bidders library for department configured business rules, however, the criteria is subject to change. | Functional | Mandatory | FALSE | FALSE | FALSE | |||
| W3.FR5.94 | The solution must provide the back-end functionality to create a record for a customer that does not have a California DL/ID card issued number ("X Numbers"). | Functional | Mandatory | FALSE | FALSE | FALSE | ||
| W3.FR5.95 | The solution shall evaluate eligibility and issue the appropriate DL/ID credential type including record print outs based on Department-defined criteria and conditions, including validation of required documents, qualifications, and transaction completion channel (for example: online, remote, or office appointment); and shall record the criteria evaluated, pass or fail outcomes, document verification results, and issuance decision timestamp. | Functional | Mandatory | FALSE | FALSE | FALSE | ||
| W3.FR5.96 | The solution must provide back-end functionality to process disqualifications of all DL/ID card types. | Functional | Mandatory | FALSE | FALSE | FALSE | ||
| W3.FR5.97 | The solution shall process disqualifications of all DL/ID card types on a record based on criteria (see examples in Bidders' Library), including Department-configured business rules, data elements, and validation criteria where applicable; and shall record the transaction or record identifier, processing status, and processing timestamp. |
| Note: See document in the bidders library for department configured business rules, however, the criteria is subject to change. | Functional | Mandatory | FALSE | FALSE | FALSE | |||
| W3.FR5.98 | The solution must provide the back-end functionality to issue temporary indicia. | Functional | Mandatory | FALSE | FALSE | FALSE | ||
| W3.FR5.99 | The solution shall issue temporary indicia that enables applicants/holders of all classes of DL to be issued a time-based extension on their license based on a variety of conditions/qualifications for configurable time periods with escalating approval required as thresholds are met, allowing for over the time limit by authorized approvers, including Department-configured business rules, data elements, and validation criteria where applicable; and shall record the transaction or record identifier, processing status, and processing timestamp. |
| Note: See document in the bidders library for department configured business rules, however, the criteria is subject to change. | Functional | Mandatory | FALSE | FALSE | FALSE |
| W3.FR5.100 | The solution shall enable all applicants to update (add, change, and remove) their donor choices (including but not limited to Organ Donor and Bone Marrow Donor), including Department-configured business rules, data elements, and validation criteria where applicable; and shall record the transaction or record identifier, processing status, and processing timestamp. |
This is the start of the file's text. The full file is on GovTribe.
File details come from the government source that posted it. Updated .