Attachment_4_-_Non-Functional_Requirements.xlsx
XLSX spreadsheet 54 KB Posted
- Solicitation number
- RFP 026-2630601-RA
- Issued by
- Orange County, San Diego City, California
About this file
The document is a Non-Functional Requirements Attachment for the County of Orange, Office of the District Attorney (OCDA) Case Management System (CMS) Request for Proposal. The RFP seeks qualified respondents to implement, maintain, and support a new CMS, with the solicitation released on August 7, 2024, and proposals due on September 18, 2024, at 2:00 pm. Key dates include a pre-proposal submission meeting on August 14, 2024, and potential interviews during the week of November 4, 2024, with services expected to commence in February 2025. The comprehensive attachment outlines 321 non-functional requirements across categories such as Auditing, Availability, Content Management, Data Integrity, Document Management, Integration, Security, and Usability.
The document provides detailed response instructions for vendors, requiring them to indicate how each non-functional requirement can be met using specific response codes: Out of the Box (O), Configuration (G), Customization (C), Third-Party Solution (3), Future Release (F), or No (N). Vendors must provide comments for responses involving configuration, customization, third-party solutions, or future releases. The requirements cover critical aspects of the CMS, including security access, regulatory compliance, performance, recoverability, reporting capabilities, and user experience. The RFP emphasizes the need for a flexible, secure, and comprehensive case management solution that can integrate with various justice partners and support the complex operational needs of the Orange County District Attorney's Office.
View the file
Other files
Show all 45
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
| County of Orange, Office of the District Attorney (OCDA) |
| Request for Proposal |
| Non-Functional Requirements - Instructions |
| Instructions |
| This Attachment contains Non-Functional Requirements requested for the OCDA CMS. |
Instructions: The Respondent shall use the response codes below to indicate whether the Solution meets the requirements or whether the Respondent recommends changes to the stated requirement.
Complete this Attachment and submit as an MS Excel file as part of the Respondent's Proposal Package.
| Field | Definition / Instructions |
| ReqID | Requirement Identification Number: This should be used to refer to requirements in correspondence |
DO NOT EDIT THIS FIELD
Level 1 Capability Specifies which category or subcategory the requirement falls under
DO NOT EDIT THIS FIELD
Requirement The description of the requirement
DO NOT EDIT THIS FIELD
Respondent Response The Respondent's response to whether and how the Non-Functional Requirement will be met.
Indicate how the requirement, as currently written, will be met by the Respondent's proposal using the following codes:
Respondent Response Definitions:
O - Out of the Box - The requirement can be met out of the box N - No - The requirement cannot be met G - ConfiGuration - The requirement can be met with some configuration C - Customization - The requirement can be met with some customization 3 - 3rd Party - The requirement can be met with the help of a third-party Respondent F - Future Release - The requirement will be met in a planned future release
Only one response per requirement will be accepted.
An omitted response will be assumed to be the same as a response code of "No".
Respondent Comment A Respondent comment is required when the response is either G, C, 3, or F.
When a comment is required, describe how the requirement will be met.
Additionally, Respondents may provide suggested changes to improve the requirement, or comments on the Respondent's response. (Optional).
Level 1 Definitions
| County of Orange, Office of the District Attorney (OCDA) |
| Request for Proposal |
| Non-Functional Requirements - Definitions |
| Level 1 Capability | Definition |
| Auditing | Ability to perform and track audits within the CMS solution in accordance and compliance with a set of rules, laws, or other regulatory mandates. |
| Availability | Ability to ensure suitable recoverability and protection of the future CMS solution from system failures, natural disasters or malicious attacks. |
| Content Management | The ability to upload, store, and access diverse content (documents, files, audio, video, etc.) within the CMS solution. |
| Data Integrity | The ability to ensure quality, completeness, validity, and security of data stored in the CMS solution. |
| Document Management | Ability to perform data management tasks within the CMS solution tailored for typical unstructured documents (including compound documents). This includes managing the flow of documents through their appropriate life cycles. |
| Environment | The ability to operate the CMS solution within multiple technical environments (e.g., testing, production, etc.). |
| Expunctions and Redactions | The ability of the CMS solution to expunge or redact specific data, information, or documents within a case record or the entire case record depending on the circumstances and/or directive mandates. |
| Integration | The ability to enable the CMS solution to transmit data to and / or from other independent applications and solutions within the organization’s internal and external application ecosystem. This includes orchestrating the integrated flow of multiple activities performed by disparate applications and providing access to data and functionality from independently designed applications through the CMS solution. |
| Maintain Secure Access to Prosecution Records | The ability to manage and maintain access and ensure security over prosecution records within the CMS solution. |
| Maintain Statutes and Codes | The ability to add, update, and otherwise maintain prosecutorial statutes and codes within the CMS solution. |
| Maintainability | The ability to identify, troubleshoot, repair, and improve software code within the CMS solution. |
| Manageability | The ability to manage the CMS solution to ensure consistent and continued performance and overall health of the solution. |
| Performance | The ability to measure and monitor the performance of the solution based on user actions and system activities. |
| Recoverability | The ability of the CMS solution to recover and restore its operations in the event of an error, breach, or other unforeseen failure. |
| Regulatory | Ability to set-up and configure the CMS solution to adhere to laws, regulations, guidelines, and specifications relevant to business' operations and audit needs. |
| Reliability | The ability of the solution to consistently perform at the level expected without error or failure. |
| Reporting | The ability to access, pull, export, and manipulate data stored in the CMS solution. |
| Security | The ability of the CMS solution to address security breaches, ensure security of information contained therein, and proactively mitigate potential security risks. |
| Serviceability | The ability to monitor the CMS solution and perform necessary maintenance services on a component of the solution or the solution as a whole. |
| Usability | The ability of users to easily access, navigate through, and perform relevant functions in the CMS solution. |
Non-Functional Requirements
| County of Orange, Office of the District Attorney (OCDA) |
| Request for Proposal |
| Non-Functional Requirements - Response Template |
Req. ID Level 0 Capability Level 1 Capability Requirement Vendor Response Author: Vendor Response Definitions:
O - Out of the Box - The requirement can be met out of the box N - No - The requirement cannot be met G - ConfiGuration - The requirement can be met with some configuration C - Customization - The requirement can be met with some customization 3 - 3rd Party - The requirement can be met with the help of a third-party vendor F - Future Release - The requirement will be met in a planned future release Comment Required Vendor Comment (Required when response is either G, C, 3, or F)
| NF1 | Non-Functional | Auditing | Ability for all logs to be non-repudiated logs |
| NF2 | Non-Functional | Auditing | Ability to log all user activities and actions (including but not limited to search, view, add, modify, delete, reports run, etc.) |
| NF3 | Non-Functional | Auditing | Ability to save all actions (including but not limited to changes made, signature added, etc.) taken on a document and / or case record to an audit log |
| NF4 | Non-Functional | Auditing | Ability to query and view a record of all transactions completed in the system including the associated user ID, date, time and transaction type |
| NF5 | Non-Functional | Auditing | Ability to export reports and query results of audit information to external products (including but not limited to Excel) for further processing |
| NF6 | Non-Functional | Auditing | Ability to prevent unauthorized modifications or deletion of audit log records |
| NF7 | Non-Functional | Auditing | Ability to maintain an audit trail of case status updates, inclusive of the time in between status change |
| NF8 | Non-Functional | Auditing | Ability to notify a user that the section that was in update status has been completed while they were editing and prior to saving |
| NF9 | Non-Functional | Auditing | Ability to notify a user of the specific updates made to the case record section that was being editing prior to saving |
| NF10 | Non-Functional | Auditing | Ability to record, track, and maintain security logging indefinitely with the ability to export historical data to external data storage to manage size of audit files |
| NF11 | Non-Functional | Auditing | Ability to log all activity around rights administration, including all rights granted and removed from users |
| NF12 | Non-Functional | Availability | Ability for monitoring tools to demonstrate that the system is operating within acceptable levels regarding online users, user-specific activities, system uptime, transaction response times, etc. Please describe monitoring tools provided with the system. |
| NF13 | Non-Functional | Availability | Ability to support active and passive availability (e.g. redundant failover installation with active syncing of data as defined by customer) |
| NF14 | Non-Functional | Availability | Ability to support local and online scenarios: active local, backup/sync online; active online, back up local |
| NF15 | Non-Functional | Availability | Ability to support offline storage and access to case data and the ability to sync/reconcile with online (e.g. case check out, cache mode) |
| NF16 | Non-Functional | Content Management | Ability to support multiple file types |
| NF17 | Non-Functional | Content Management | Ability to support configurable file sizes |
| NF18 | Non-Functional | Content Management | Ability to associate a file with multiple cases and store only once |
| NF19 | Non-Functional | Content Management | Ability to categorize a file type (e.g. 911 audio, Dashcam video, etc.) |
| NF20 | Non-Functional | Content Management | Ability to view/play content within application and support multiple formats and codecs) |
| NF21 | Non-Functional | Content Management | Ability to manage storage locations for files based on size, age or other factors through multiple methods and availability (e.g. cloud, on prem server or other storage solution) |
| NF22 | Non-Functional | Content Management | Ability to ingest attachments from an external party and place in quarantine to be scanned for viruses before being ingested and accessed by users |
| NF23 | Non-Functional | Data Integrity | Ability to designate fields for which data is required to be entered |
| NF24 | Non-Functional | Data Integrity | Ability to define required relationships between screen-form data fields (including but not limited to if data is entered in one field, data must exist or be entered in the related field) |
| NF25 | Non-Functional | Data Integrity | Ability to be to retain inactive code values in reference tables so as to maintain referential integrity with individual case records |
| NF26 | Non-Functional | Data Integrity | Ability to support scanning of files for viruses and malware prior to adding a file to a the system case record |
| NF27 | Non-Functional | Data Integrity | Ability to update code tables and lists optionally without impacting current case records |
| NF28 | Non-Functional | Data Integrity | Ability to run Ad Hoc reports and user defined queries utilizing all of the available fields that make up a case or party record |
| NF29 | Non-Functional | Data Integrity | Ability to save commonly utilized queries / searches |
| NF30 | Non-Functional | Data Integrity | Ability to bulk upload data |
| NF31 | Non-Functional | Data Integrity | Ability to consolidate data at external data sources (including but not limited to external warehouse, etc.) |
| NF32 | Non-Functional | Data Integrity | Ability to be notified of updates of code tables by Global Administrator or Jurisdiction Administrator that may be applied to a Case Record |
| NF33 | Non-Functional | Data Integrity | Ability to apply configurable data entry validation functions (including but not limited to drop down lists, mandatory fields, date masks, etc.) |
| NF34 | Non-Functional | Data Integrity | Ability to apply configurable data entry validation functions based on case type (including but not limited to adult, juvenile, etc.) |
| NF35 | Non-Functional | Data Integrity | Ability to hash video files to maintain file integrity |
| NF36 | Non-Functional | Data Integrity | Ability to validate data against internal/external sources and flag inconsistencies |
| NF37 | Non-Functional | Data Integrity | Ability to create and edit templates |
| NF38 | Non-Functional | Document Management | Ability to associate specific fields in the system database with corresponding fields in the system form templates |
| NF39 | Non-Functional | Document Management | Ability to create and edit a set of form that meet necessary rules and regulations incorporated into the system |
| NF40 | Non-Functional | Document Management | Ability to store documents related to a case with links between the system metadata and individual documents |
| NF41 | Non-Functional | Document Management | Ability to open and view contents of a zip file within the system |
| NF42 | Non-Functional | Document Management | Ability to integrate with Document Management Systems to allow the intake, tracking, managing, and storing of the system generated documents |
| NF43 | Non-Functional | Document Management | Ability to annotate scanned images determining if the annotations will be a part of the case record or not |
| NF44 | Non-Functional | Document Management | Ability to retain redacted copies of documents |
| NF45 | Non-Functional | Document Management | Ability to electronically file mark document (including but not limited to image or icon that is in the background of a document generally akin to an official seal versus a file stamp generally utilized for certification, dates and times, etc.) |
| NF46 | Non-Functional | integration | Ability to click a link on a the system screen (including but not limited to docket) to view document(s) corresponding to the selected data |
| NF47 | Non-Functional | Document Management | Ability to view all images and documents associated with a case record with the ability to print locally |
| NF48 | Non-Functional | Document Management | Ability to print all images and documents associated with case records |
| NF49 | Non-Functional | Document Management | Ability to produce certified copies with corresponding fee assessments and certification stamps |
| NF50 | Non-Functional | Document Management | Ability to scan documents relating to an entry on the case (including but not limited to motion event is added and the user can scan the motion directly connected to the event) |
| NF51 | Non-Functional | Document Management | Ability to print multiple documents in a single request (including but not limited to all documents for a case, all documents related to a party) |
| NF52 | Non-Functional | Document Management | Ability to generate multiple documents to attached to the case records of multiple cases in a single transaction (including but not limited to creation of multiple change notices associated with bulk change of court calendar) |
| NF53 | Non-Functional | Document Management | Ability to manually add documents to the case record (i.e. documents not eFiled) by file upload or scanning |
| NF54 | Non-Functional | Document Management | Ability to apply a file stamp or file mark (with configurable content) to documents added to the case record |
| NF55 | Non-Functional | Document Management | Ability to perform key word searches on documents images attached to case records |
| NF56 | Non-Functional | Document Management | Ability to access a repository within the system of approved, pre-developed forms for authorized users to utilize |
| NF57 | Non-Functional | Document Management | Ability to select a pre-developed form for editing to become a court order |
| NF58 | Non-Functional | Document Management | Ability to prevent edits to a specific instance of an order from changing the master version of the pre-developed form |
| NF59 | Non-Functional | Document Management | Ability to store large volume of digital evidence for extensive period of time for reasonable cost |
| NF60 | Non-Functional | Document Management | Ability to upload multiple files to multiple cases at one time |
| NF61 | Non-Functional | Document Management | Ability to track all actions and activities taken on documents |
| NF62 | Non-Functional | Document Management | Ability to track movement of documents within and outside of the solution (who created the document, who opened the document, etc.) |
| NF63 | Non-Functional | Document Management | Ability to associate a file with multiple cases and store only once |
| NF64 | Non-Functional | Document Management | Ability to scan documents in bulk to a case |
| NF65 | Non-Functional | Document Management | Ability to scan documents to a case or cases using bar codes to route the document to the appropriate case |
| NF66 | Non-Functional | Document Management | Ability to scan directly into a case |
| NF67 | Non-Functional | Document Management | Ability to categorize a document type (e.g. offense report, affidavit, medical records, etc.) and automatically categorize ingested documents (via scanning, email, or integration) based on defined characteristics (e.g. layout, bar code, OCR document title) |
| NF68 | Non-Functional | Document Management | Ability to support automated redaction based on business rules, document patterns and create a ne redacted copy and maintain original document |
| NF69 | Non-Functional | Document Management | Ability to apply electronic signature using a pin |
| NF70 | Non-Functional | Document Management | Ability to configure documents to be generated by case type (such as pre-trial motions) |
| NF71 | Non-Functional | Document Management | Ability to change / configure retention time frames |
| NF72 | Non-Functional | Document Management | Ability to archive files that are still accessible |
| NF73 | Non-Functional | Environment | Ability to provide access to multiple environments (including but not limited to Prod, Test, Dev, QA, Training, etc.) that mirror the production environment's services and interfaces. Describe your proposed environments and what they will be used for, including the environment where Training and Testing would occur and how the multi-jurisdiction characteristics of the system impact this architecture. |
| NF74 | Non-Functional | Environment | Ability for the non-production environments to include reliable, current configuration matching the production environment |
| NF75 | Non-Functional | Environment | Ability for the test environment to include current infrastructure patch levels to successfully test integrations against new the system features |
| NF76 | Non-Functional | Expunctions and Redactions | Ability to expunge (not available to public, but still exists for internal view) and redact (data is hidden but the original still exists for internal review) in its entirety preventing future access of the case while still maintaining the record in the database for auditing and statistical purposes |
| NF77 | Non-Functional | Expunctions and Redactions | Ability to purge records |
| NF78 | Non-Functional | Expunctions and Redactions | Ability to bulk purge records |
| NF79 | Non-Functional | Expunctions and Redactions | Ability to mark records as privileged, searchable but not accessible, not visible at all |
| NF80 | Non-Functional | Expunctions and Redactions | Ability to redact audit log files for expunged cases |
| NF81 | Non-Functional | Expunctions and Redactions | Ability to perform global redactions based on court order/user request |
| NF82 | Non-Functional | Expunctions and Redactions | Ability to support redacting any field from UI through configuration and role based security |
| NF83 | Non-Functional | Integration | Ability to share data and standard formats to a published open data portal (including but not limited to internally share, external parties, groups, organizations, etc.) |
| NF84 | Non-Functional | Integration | Ability to exchange files through SFTP |
| NF85 | Non-Functional | Integration | Ability to pull and update information from Justice Partners (including but not limited to eDefender, Vision, etc.) |
| NF86 | Non-Functional | Integration | Ability to support SOAP protocols for exchanging information via web services |
| NF87 | Non-Functional | Integration | Ability to support REST and/or JSON styles for exchanging via web services |
| NF88 | Non-Functional | Integration | Ability to support PCDeck for exchanges of a fix record length |
| NF89 | Non-Functional | Integration | Ability to integrate with Court system to access data (i.e. eFile e-mail address, and atty status; daily import of flat file; automated integration). In the comments, please describe integration capabilities anticipated |
| NF90 | Non-Functional | Integration | Ability to integrate with justice partners (including but not limited to Law Enforcement Agency records management systems) to access data (including but not limited to defendant information, arrest reports, custody status, etc.). In the comments, please describe integration capabilities anticipated |
| NF91 | Non-Functional | Integration | Ability to integrate with non-justice partners or other County systems |
| NF92 | Non-Functional | Integration | Ability to integrate with the various law enforcement agency subpoena solutions in the County |
| NF93 | Non-Functional | Integration | Ability to integrate with eDefender to quickly share discovery information with defense counsel |
| NF94 | Non-Functional | Integration | Ability to log the execution and timing of all interface transactions and data exchanges |
| NF95 | Non-Functional | Integration | Ability to log integration errors |
| NF96 | Non-Functional | Integration | Ability to correct data integration errors based on logs |
| NF97 | Non-Functional | Integration | Ability to reprocess data message and confirm correction of errors |
| NF98 | Non-Functional | Integration | Ability to automate and monitor for API errors (outbound or inbound) |
| NF99 | Non-Functional | Integration | Ability to integrate with asynchronous or synchronous methods as applicable and provide visibility to API/transaction status to identify problems (including but not limited to HTTP, REST, etc.) |
| NF100 | Non-Functional | Integration | Ability to integrate with internal and external justice partners, including but not limited to the following justice partners: Law Enforcement, Sheriff's Dept., Probation, Superior Court, Public Defender, ILJAOC, Crime Lab, Court of Appeals, Dept. of Justice, Bar Association, State Compensation Board, Cal State Dept. of Justice, Defense Attorneys, OCDA Investigation Bureau, OCDA DNA Program, OCDA Digital Evidence Program, Victim Services / Restitution, Attorney General's Office |
| NF101 | Non-Functional | Integration | Ability to integrate with justice partners and other authorized agencies to send case data through a secure mechanism (including but not limited to party information, case type, offense codes, documents) |
| NF102 | Non-Functional | Integration | Ability to conform to National Information Exchange Model |
| NF103 | Non-Functional | Integration | Ability to integrate with external calendars such as Outlook |
| NF104 | Non-Functional | Integration | Ability to support real time updates of case information from external sources, such as: custody status, case disposition, court register of actions entries, discovery uploads |
| NF105 | Non-Functional | Maintain Security Access to Prosecution Records | Ability to maintain (including but not limited to add, modify, disable) user profiles with designated system roles |
| NF106 | Non-Functional | Maintain Security Access to Prosecution Records | Ability to maintain history of permissions/roles granted to users |
| NF107 | Non-Functional | Maintain Security Access to Prosecution Records | Ability to determine access to system records (including but not limited to case/party) based on user/roles |
| NF108 | Non-Functional | Maintain Security Access to Prosecution Records | Ability to determine access to specific fields and screens within a case record or party record based on user/roles |
| NF109 | Non-Functional | Maintain Security Access to Prosecution Records | Ability to determine access to view or modify documents based on user/roles |
| NF110 | Non-Functional | Maintain Security Access to Prosecution Records | Ability to determine access levels of users to perform actions (including but not limited to add, update, delete, inquiry) to a case or party record based on user/roles |
| NF111 | Non-Functional | Maintain Security Access to Prosecution Records | Ability to run audit reports on user(s) access of records for a time period |
| NF112 | Non-Functional | Maintain Security Access to Prosecution Records | Ability to run audit reports against non-repudiated logs |
| NF113 | Non-Functional | Maintain Security Access to Prosecution Records | Ability to track information that can be reported on user activity (including but not limited to case updates, other reports run, data access, requests, etc.) |
| NF114 | Non-Functional | Maintain Security Access to Prosecution Records | Ability to configure reports (including but not limited to limit the reported information into a date range, etc.) |
| NF115 | Non-Functional | Maintain Security Access to Prosecution Records | Ability to configure reports to automatically run and be added to a predefined location |
| NF116 | Non-Functional | Maintain Security Access to Prosecution Records | Ability to distinguish the level of access an individual must have in order to access a document |
| NF117 | Non-Functional | Maintain Security Access to Prosecution Records | Ability to assign one or multiple administrative authorizations to each user role (e.g., Individual, Manager, Administrator) |
| NF118 | Non-Functional | Maintain Security Access to Prosecution Records | Ability to define security profiles either for roles or individuals (including but not limited to Manager can review all documents in their queue while support staff can only view documents assigned to their queue ) |
| NF119 | Non-Functional | Maintain Security Access to Prosecution Records | Ability to assign an individual user to multiple security profiles |
| NF120 | Non-Functional | Maintain Security Access to Prosecution Records | Ability to allow a user to have elevated security rights for a single case record (including but not limited to Special Prosecution team can see all data and documents on specific case types; while others only can see limited data) |
| NF121 | Non-Functional | Maintain Security Access to Prosecution Records | Ability to establish a hierarchy for security profiles |
| NF122 | Non-Functional | Maintain Security Access to Prosecution Records | Ability to perform security and solution functions only for a local user base (including but not limited to victim's advocacy, sexually violent crimes, etc.) |
| NF123 | Non-Functional | Maintain Security Access to Prosecution Records | Ability to alter the security of an individual content item (including but not limited to document, case, etc.) |
| NF124 | Non-Functional | Maintain Security Access to Prosecution Records | Ability to alter the security of a content group or aggregation as a unit |
| NF125 | Non-Functional | Maintain Security Access to Prosecution Records | Ability to apply security controls to individual documents |
| NF126 | Non-Functional | Maintain Security Access to Prosecution Records | Ability to apply security controls to individual case records |
| NF127 | Non-Functional | Maintain Security Access to Prosecution Records | Ability for case records to be automatically assigned security controls based on predetermine business rules (including but not limited to case type, age of defendant) |
| NF128 | Non-Functional | Maintain Security Access to Prosecution Records | Ability to maintain (including but not limited to modify, delete, add) document access authorization |
| NF129 | Non-Functional | Maintain Security Access to Prosecution Records | Ability for a document to be scanned into the system with a user's pre-determined security group |
| NF130 | Non-Functional | Maintain Security Access to Prosecution Records | Ability to leverage OCDA scanning hardware to allow documents to be scanned and uploaded directly into the system |
| NF131 | Non-Functional | Maintain Security Access to Prosecution Records | Ability to flag a party in the system that would create an alert if a user searched for that party |
| NF132 | Non-Functional | Maintain Security Access to Prosecution Records | Ability to support Active Directory integration and inherit rights and roles from AD |
| NF133 | Non-Functional | Maintain Security Access to Prosecution Records | Ability to define access to a case or elements of a case (e.g. notes or an attachment) by role, by user name, by unit |
| NF134 | Non-Functional | Maintain Statutes and Codes | Ability to add configuration to all code tables within the system |
| NF135 | Non-Functional | Maintain Statutes and Codes | Ability to modify configuration to all code tables within the system |
| NF136 | Non-Functional | Maintain Statutes and Codes | Ability to enter the reason for configuration modifications |
| NF137 | Non-Functional | Maintain Statutes and Codes | Ability to disable configuration to all code tables within the system |
| NF138 | Non-Functional | Maintain Statutes and Codes | Ability to assign a date range for which a given code value is to be in effect in the system |
| NF139 | Non-Functional | Maintain Statutes and Codes | Ability for configuration codes to automatically begin and discontinue based on configured dates |
| NF140 | Non-Functional | Maintain Statutes and Codes | Ability to designate roles/users to maintain (including but not limited to add, modify, or disable) configuration for their specific office |
| NF141 | Non-Functional | Maintain Statutes and Codes | Ability to determine what tables a role/user is able to maintain (including but not limited to add, modify, or disable) |
| NF142 | Non-Functional | Maintain Statutes and Codes | Ability to determine which actions a role/user may conduct within a code table (including but not limited to view, add, modify, or disable) |
| NF143 | Non-Functional | Maintain Statutes and Codes | Ability to configure automated responses that display to the user explaining why an action cannot be performed (including but not limited to notify a user why a fee cannot be added to the case) |
| NF144 | Non-Functional | Maintain Statutes and Codes | Ability to define and maintain bail schedule associated with a code |
| NF145 | Non-Functional | Maintain Statutes and Codes | Ability to define and maintain punishment range associated with a code |
| NF146 | Non-Functional | Maintain Statutes and Codes | Ability to define and maintain one or more charging language paragraphs for a code and be able to apply an effective date |
| NF147 | Non-Functional | Maintain Statutes and Codes | Ability to define multiple configurable offense code charge categories |
| NF148 | Non-Functional | Maintainability | Ability for the vendor to provide support via remote access, through a VPN connection (or other means of secure remote access) |
| NF149 | Non-Functional | Maintainability | Ability to maintain the system configuration parameters without the need for support from the system vendor and without the need to modify the system code (where practical). In the comments, please describe limitations related to establishment of such capabilities |
| NF150 | Non-Functional | Maintainability | Ability to support upgrade capabilities that allows the vendor to upgrade to the latest version of the vendor’s product without requiring OCDA reconfigure the system. Please include in the comments how you plan to support this requirement. |
| NF151 | Non-Functional | Manageability | Ability to maintain a person record (including but not limited to defendant, witnesses, attorneys, victim's, law enforcement, etc.) where all transactions and activities related to the person record are tracked and associated with that person |
| NF152 | Non-Functional | Manageability | Ability to support person record matching when adding a new person record to minimize duplicate records |
| NF153 | Non-Functional | Manageability | Ability to combine/merge person records dictating what data is saved/replaced |
| NF154 | Non-Functional | Manageability | Ability to separate a person record into two records to address misidentification and stolen identity |
| NF155 | Non-Functional | Manageability | Ability to associate the same person record with multiple cases and multiple associations to cases (including but not limited to defendant, witness, victim, etc.) |
| NF156 | Non-Functional | Manageability | Ability to separate specialty party (including but not limited to law enforcement, investigator, attorney, etc..) information from other case participants |
| NF157 | Non-Functional | Manageability | Ability to handle the necessary file sizes for evidence (including but not limited to graphics, audio, etc.) |
| NF158 | Non-Functional | Manageability | Ability to categorize specialty parties by type (including but not limited to law enforcement, investigator, attorney, etc..) on the system screens and reports |
| NF159 | Non-Functional | Manageability | Ability to notify designated recipient(s) after a configurable number of retries related to integration with 3rd party solutions |
| NF160 | Non-Functional | Manageability | Ability to send notifications (including but not limited to email, text) based on configurable system (including but not limited to system usage exceeds a certain threshold). Please describe how your software supports this requirement. |
| NF161 | Non-Functional | Manageability | Ability for users to set and re-set when, how often, and at what time they receive notifications |
| NF162 | Non-Functional | Manageability | Ability to terminate a the system service (including but not limited to transaction that is degrading overall system performance) |
| NF163 | Non-Functional | Manageability | Ability to migrate or sync environments (including but not limited to synchronize data from production into a training environment ) |
| NF164 | Non-Functional | Manageability | Ability for the vendor to implement new jurisdictions with baseline and local configuration to the system without impacting current jurisdictions already utilizing the solution |
| NF165 | Non-Functional | Manageability | Ability to be to include a role of Global Administrator with rights to administer solution functions and configuration applicable to all jurisdictions |
| NF166 | Non-Functional | Manageability | Ability to define systemwide the system elements and reference table values (including but not limited to case types, offense codes, document codes, etc.) |
| NF167 | Non-Functional | Manageability | Ability to propagate a configuration across the entire system to support configuration of multiple departments simultaneously |
| NF168 | Non-Functional | Manageability | Ability to structure tiers of users to be able to self-manage configuration (including but not limited to Global Administrator, Jurisdiction Administrator). Please describe in the comments the features available to be self-managed, what role(s) can manage them |
| NF169 | Non-Functional | Manageability | Ability to be to include a role of Jurisdiction Administrator with rights to administer solution functions and configuration applicable only to a single jurisdiction |
| NF170 | Non-Functional | Manageability | Ability to utilize a user interface to administer tables, rules and other configuration settings within their security context. |
| NF171 | Non-Functional | Manageability | Ability to prevent jurisdiction level configuration updates from updating the systemwide baseline |
| NF172 | Non-Functional | Manageability | Ability for Jurisdiction Administrators to modify authorized components of the system baseline configuration for OCDA only |
| NF173 | Non-Functional | Manageability | Ability for any modifications of the system baseline configuration by Jurisdiction Administrators to be easily reverted back to the baseline (including but not limited to check a box to utilize systemwide baseline) |
| NF174 | Non-Functional | Manageability | Ability to account for state and jurisdiction specific holidays and weekends when calculating dates and durations |
| NF175 | Non-Functional | Manageability | Ability to define a jurisdiction-specific calendar |
| NF176 | Non-Functional | Manageability | Ability to automatically adjust the solution time for daylight savings time on all solution components |
| NF177 | Non-Functional | Manageability | Ability to notify a defined set of recipients of configuration changes |
| NF178 | Non-Functional | Manageability | Ability to provide visibility of configuration changes (including but not limited to report, screen, rights and roles, configuration, network system, etc.) |
| NF179 | Non-Functional | Manageability | Ability to import data from external data stored in a delimited data file format (including but not limited to for data migration) based on user security profiles. |
| NF180 | Non-Functional | Manageability | Ability to export data from the system in a defined file format |
| NF181 | Non-Functional | Manageability | Ability to manage workflow queues with data from across the county |
| NF182 | Non-Functional | Manageability | Ability to configure workflow queues to specific users and offices/divisions |
| NF183 | Non-Functional | Performance | Ability to generate solution administration and performance reports (including but not limited to activity, inactivity, audit trails, effectiveness, reject rates, solution metrics) |
| NF184 | Non-Functional | Performance | Ability to support response times of critical functions as defined by OCDA |
| NF185 | Non-Functional | Recoverability | Ability to support redundancies which allow for continued solution access in the event of a solution component outage (including but not limited to clustering, replication) |
| NF186 | Non-Functional | Recoverability | Ability to support load-balancing where users are automatically redirected to a different access point for continued solution access |
| NF187 | Non-Functional | Recoverability | Ability to automatically failover to a replicated / backup solution at any time |
| NF188 | Non-Functional | Recoverability | Ability to work disconnected and then upload changes to system back up |
| NF189 | Non-Functional | Recoverability | Ability to save in-process data entry during a solution outage |
| NF190 | Non-Functional | Regulatory | Ability to provide a digital certificate that meets OCDA defined requirements (including but not limited to use public key infrastructure (PKI) technology, be X.509 compliant, include an image of a users electronic signature, etc., as defined in Orange County Laws and Regulations) |
| NF191 | Non-Functional | Regulatory | Ability to be compliant with all Criminal Justice Information Services (CJIS) security standards (including but not limited to digital and physical security standards) |
| NF192 | Non-Functional | Regulatory | Ability to be accessible to law enforcement agencies and other authorized users via the County's network |
| NF193 | Non-Functional | Regulatory | Ability to monitor and provide functionality for Federal and State mandates that OCDA must legally support |
| NF194 | Non-Functional | Reliability | Ability to utilize a Master Time Clock that utilizes Network Time Protocol (NTP) in order to ensure consistent and accurate time throughout all solution components |
| NF195 | Non-Functional | Reliability | Ability to synchronize with a central solution clock |
| NF196 | Non-Functional | Reporting | Ability to generate reports using code look-up values (including but not limited to penal codes) in effect as of the date of the event(s) included in the report |
| NF197 | Non-Functional | Reporting | Ability to access all data in the system database repository for reporting and query purposes |
| NF198 | Non-Functional | Reporting | Ability to provide a data dictionary that describes and maintains information on each data element (including but not limited to data element name and type, description of the data element, and the format of each data element) to assist with functions such as reporting |
| NF199 | Non-Functional | Reporting | Ability to provide an Entity Relationship Diagram (ERD) that allows OCDA to understand the system’s underlying data tables and relationships for internal use (including but not limited to report development). |
| NF200 | Non-Functional | Reporting | Ability to perform predefined and ad-hoc queries using industry standard logical operators (including but not limited to nested queries, joins, and/or, etc.) |
| NF201 | Non-Functional | Reporting | Ability to access data through Power BI or other reporting tools as defined by OCDA |
| NF202 | Non-Functional | Reporting | Ability to stand up a reporting server or data mart |
| NF203 | Non-Functional | Reporting | Ability to export all data |
| NF204 | Non-Functional | Security | Ability to support HTTPS and automatically redirect requests for HTTP to HTTPS |
| NF205 | Non-Functional | Security | Ability to notify a user that their login credentials is already logged in to another instance of the system |
| NF206 | Non-Functional | Security | Ability for users to reset their login password |
| NF207 | Non-Functional | Security | Ability to create password for each user that can be reset by a Jurisdiction Administrator |
| NF208 | Non-Functional | Security | Ability for a Global Administrator to define rules that govern password format and strength (including but not limited to must be ### characters, must include combination of character types, cannot use user ID as password, cannot use own name, phone number) |
| NF209 | Non-Functional | Security | Ability for the solution to automatically validate entered passwords |
| NF210 | Non-Functional | Security | Ability to require that passwords be changed at defined intervals (including but not limited to 180 days) |
| NF211 | Non-Functional | Security | Ability for the solution to issue prompts to users to reset passwords as the time period approaches |
| NF212 | Non-Functional | Security | Ability to support federated identity access management (including but not limited to active-directory, azure, etc.) across County and Non-County (Local, State, etc.) entities |
| NF213 | Non-Functional | Security | Ability to provide multi-factor authentication |
| NF214 | Non-Functional | Security | Ability to create a unique user-id for users that does not utilize data that may change in the future (including but not limited to user e-mail, user name) |
| NF215 | Non-Functional | Security | Ability to issue an email to the user in the event a login attempt failed |
| NF216 | Non-Functional | Security | Ability to issue a SMS alert to the user in the event a login attempt failed |
| NF217 | Non-Functional | Security | Ability to provide users the ability to logout at any time from any screen |
| NF218 | Non-Functional | Security | Ability to automatically log a user out of the system once they close the window (including but not limited to user clicks icon "x" button on top right corner rather than specific logout function) |
| NF219 | Non-Functional | Security | Ability to utilize system rights and roles that are defined in a federated identity access management (including but not limited to active-directory, etc.) |
| NF220 | Non-Functional | Security | Ability to allow specific assigned roles to access party and/or case information |
| NF221 | Non-Functional | Security | Ability to automatically log a user out of the system after a pre-configured period of inactivity |
| NF222 | Non-Functional | Security | Ability to configure the duration of the timeout setting that ends a user's session |
| NF223 | Non-Functional | Security | Ability to remotely “terminate” a user’s session |
| NF224 | Non-Functional | Security | Ability to lock users out of the system |
| NF225 | Non-Functional | Security | Ability to seal a range of cases based on specific criterion manually or electronically |
| NF226 | Non-Functional | Security | Ability to support sealing a case (including but not limited to complete case or partial elements of the case - to include: artifacts, photos, etc.) |
| NF227 | Non-Functional | Security | Ability to seal specific parties (including but not limited to defendant, witness, victim, etc.) where only those with specific rights and roles can view party name and record |
| NF228 | Non-Functional | Security | Ability to seal sections of a case with the necessary security level in the notes (including but not limited to confidential, private, etc.) |
| NF229 | Non-Functional | Security | Ability to unseal a case or components of a case (including but not limited to defendant name, hearing dates, etc.) |
| NF230 | Non-Functional | Security | Ability to be FIDO2 compliant |
| NF231 | Non-Functional | Security | Ability to integrate with industry leading third-party multifactor authentication products and vendors (including but not limited to OKTA, Ping identity, Microsoft, etc.) |
| NF232 | Non-Functional | Security | Ability to conform to National Institute of Standards and Technology (NIST) |
| NF233 | Non-Functional | Security | Ability to include measures for the detection and prevention of unauthorized access intrusion attempts, including notifying OCDA of abnormal activities (including but not limited to geolocating threats). Describe how this requirement would be met. |
| NF234 | Non-Functional | Security | Ability for users to generate security reports utilizing user defined fields (including but not limited to username, timeframe, security context, etc.) |
| NF235 | Non-Functional | Security | Ability to generate reports from non-repudiated logs |
| NF236 | Non-Functional | Security | Ability to not store sensitive credentials (including but not limited to database connection information, passwords, etc.) in plain text |
| NF237 | Non-Functional | Security | Ability to define field and data element level permissions |
| NF238 | Non-Functional | Security | Ability to define transaction and function level permissions |
| NF239 | Non-Functional | Security | Ability to define screen or window level permissions |
| NF240 | Non-Functional | Security | Ability to encrypt all export data files from the system with a unique key along with recovery mechanism to protect the data exports. |
| NF241 | Non-Functional | Security | Ability to log all data exports with details regarding the specific records exported |
| NF242 | Non-Functional | Security | Ability to indicate that only resources (including but not limited to investigators, victim's assistance, support staff, attorney, etc.) assigned to a case has access to the specific case seeing only information on that case based on their particular rights and roles |
| NF243 | Non-Functional | Security | Ability to encrypt data in transit and data at rest at least at TLS 1.3/ FIPS 140-2 and based on rules such as document types, sensitive data, etc. |
| NF244 | Non-Functional | Security | Ability to apply security and access control permissions consistently on both desktop and mobile devices |
| NF245 | Non-Functional | Security | Ability to support login access trough AD credentials |
| NF246 | Non-Functional | Security | Ability to support granting access to individuals outside of Active Directory (e.g. special prosecutor) |
| NF247 | Non-Functional | Security | Support notifications of any security breach or intrusion into vendor hosted facilities |
| NF248 | Non-Functional | Security | Ability to capture hosting requirements |
| NF249 | Non-Functional | Serviceability | Ability to be hosted in a vendor-provided cloud platform |
| NF250 | Non-Functional | Serviceability | Ability to support an on-premise solution if required |
| NF251 | Non-Functional | Serviceability | Ability to be a web-based system (preferred) |
| NF252 | Non-Functional | Serviceability | Ability to run the system on a desktop computer utilizing any commonly utilized browser (including but not limited to Chrome, Internet Explorer, Firefox, Safari, Edge - versions back to n-2) |
| NF253 | Non-Functional | Serviceability | Ability to run certain system functions on a mobile device using either an app or browser (including but not limited to calendar look-up, case information updates, victim service inquiries) |
| NF254 | Non-Functional | Serviceability | Ability to manage and push out service changes on a schedule (including but not limited to automated deployments, etc.) |
| NF255 | Non-Functional | Serviceability | Ability to be usable without requiring the deployment of end-user workstation / client-side components or workstation setting changes |
| NF256 | Non-Functional | Serviceability | Ability to not require any browser plug-ins, extensions, or add-in applets to function |
| NF257 | Non-Functional | Serviceability | Ability to set benchmarks and notifications (including but not limited to immediate workflow notification, email, etc.) |
| NF258 | Non-Functional | Serviceability | Ability to utilize industry standard languages and tools (including but not limited to C#, C++, etc.) |
| NF259 | Non-Functional | Serviceability | Ability to integrate with all industry standard monitoring tools (including but not limited to tracking system outages, security vulnerabilities, SLAs, etc.) |
| NF260 | Non-Functional | Serviceability | Ability to self-monitor tool within applications |
| NF261 | Non-Functional | Usability | Ability to utilize single and / or dual monitors while utilizing the system |
| NF262 | Non-Functional | Usability | Ability for a user to concurrently open multiple the system windows |
| NF263 | Non-Functional | Usability | Ability to process multiple functions concurrently with the same login credentials |
| NF264 | Non-Functional | Usability | Ability to support multiple input methods based on user device and preference (including but not limited to mouse, keyboard, touchscreen) |
| NF265 | Non-Functional | Usability | Ability to have online help functions assisting users with standard solution usage and functionality |
| NF266 | Non-Functional | Usability | Ability to apply a configurable Bates stamp which includes a sequential number that is unique within a case/defendant to selected documents |
| NF267 | Non-Functional | Usability | Ability for the solution to associate jurisdictional definitions when a user hovers over specific text or areas on a screen |
| NF268 | Non-Functional | Usability | Ability to inform users of "What's New" (revisions, additions, deletions) when accessing documentation that has been updated |
| NF269 | Non-Functional | Usability | Ability for a user to use a type-ahead feature for drop-down lists (including but not limited to user enters "te" and cursor jumps to drop-down list values starting with "te") |
| NF270 | Non-Functional | Usability | Ability to conduct complex search "and / or" , "and / and" , etc. |
| NF271 | Non-Functional | Usability | Ability for a user to perform searches using individual or multiple fields (including but not limited to case number (full or partial), attorney, party names) |
| NF272 | Non-Functional | Usability | Ability to use wild cards and designate whether partial matches are acceptable or not |
| NF273 | Non-Functional | Usability | Ability to search the system data and documents using keywords, wild cards, and Boolean operands (and, or, not) |
| NF274 | Non-Functional | Usability | Ability for a user to sort search results |
| NF275 | Non-Functional | Usability | Ability for a user to initiate a subsequent search on the search results set |
| NF276 | Non-Functional | Usability | Ability for a user to abort a search |
| NF277 | Non-Functional | Usability | Ability to use standard word processing capabilities (including but not limited to word wrap, spell check, backspace, delete, undo, insert, overtype) in free-form text fields |
| NF278 | Non-Functional | Usability | Ability to pre-populate information from integrated justice partners (including but not limited to booking data, courts, etc.) |
| NF279 | Non-Functional | Usability | Ability to highlight fields which must be completed and prevent users from proceeding to the next screen until valid information is entered |
| NF280 | Non-Functional | Usability | Ability to sort documents based on user defined criterion |
| NF281 | Non-Functional | Usability | Ability to automatically display additional fields based on entered data (including but not limited to the next line for additional data is displayed when one line is filled in or when a user selects an option from a list) |
| NF282 | Non-Functional | Usability | Ability to prevent errors or repetitive requests from inadvertent multiple clicks by a user |
| NF283 | Non-Functional | Usability | Ability to highlight errors (including but not limited to data entry, submission failures) and prompt user for correction |
| NF284 | Non-Functional | Usability | Ability to access information via desktop, mobile, tablet, portal |
| NF285 | Non-Functional | Usability | Ability to display visual indicators to denote that a transaction is in progress |
| NF286 | Non-Functional | Usability | Ability to display visual indicators to denote that a transaction is complete |
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 .