ExF_Technical Documentation of System Features and Functionality - CCCLS Mod.pdf

PDF 152 KB Posted

Attached to
CCCLS Database Support, Enhancement, & Maint OB 50896616
Solicitation number
RFP QAAA 2027000079 1
Issued by
Denver County, Denver City, Colorado

About this file

This is a Technical Documentation exhibit for a Colorado Department of Early Care (CDEC) system supporting criminal justice information (CJI) management and background investigations for child care licensing. The document outlines comprehensive system requirements for supporting the CCCLS (likely referring to a child care licensing system) modification, encompassing personnel security protocols, business operations, analytics, technical infrastructure, and security standards. The system must be built on .Net 5 using C# programming language and operate on an AWS CJIS-compliant solution in .govcloud, with multi-factor authentication required for all users. Key functional requirements include user administration with permissions-based access controls, criminal background check (CBC) management, sex offender list maintenance, provider lookup capabilities, report generation, CJIS audit compliance, and integration with Salesforce for Trails Abuse and Neglect data. The system must maintain strict role-based access control across all operations including data entry, editing, viewing, and printing functions.

The offeror must ensure the production environment maintains 99.950% uptime monthly with scheduled maintenance performed outside business hours and unplanned outages resolved within four hours. All data must be encrypted at rest and in transit to FIPS 140-2 standards with minimum 256-bit strength FIPS 197 certification, including field-level encryption for confidential data such as Social Security numbers. The system requires comprehensive audit logging at user, database, and server levels; point-in-time database recovery capabilities; role-based permissions including administration, read-only, read-write, and audit roles; and centralized user authentication and authorization management. No offshore resources are permitted to access or store CJI data, and the offeror must meet the same personnel security standards as Colorado state employees. The solution must support modular expansion and scalability, operate through standard web browsers meeting OIT standards, and provide data export upon contract termination with full referential integrity at no additional cost.

View the file

Other files

On GovTribe

Work with this file

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

Text version

Exhibit F

High Level System Information Describe the Offeror's capabilities to support the following requirements

Personnel Describe how the Offeror will support these criteria No off-shore resources permitted to work with CJI data, including access to data or storage of data offshore.

Business Requirements Describe how the Offeror will support these criteria Home/Landing Page Admin - User Search (Permissions based) Admin - User Detail - Add (Permissions based) Admin - User Detail - Edit (Permissions based) CBC - CBC Search (Permissions based) - Maintain and update as needed.

CBC - Add CBC - Maintain current and if needed identify and configure specific roles and staff members permissions CBC - Edit CBC ---Edit abilities and screens vary based on Role and Field level Edit. Limited ability to edit certain data from CBI Navigation Panel/Bar functionality and features Providers Lookup Screen Name Removal for LW Sex Offender List - For Colorado - Based on a address comparison with program address information. Maintain existing Sex Offender List - Out of state - Tracks out of state sex offender information - Address comparison takes place in system.

Reports - Maintain existing reports for Providers, Applicants, BIU, Licensing specialist, etc. These include internal and external System email notifications developed are sent to licensing specialists alerting reports are available.

Batch Reports ---This includes all current and newly required background reports from CBI for the BIU team for weekly Notifications sent to CBC based upon CJIS requirement.

System includes the processing of name removal and providing this information to CBI. System specific time frames are in If provider closure is done, provider is flagged and notification is sent to BIU to confirm true closure and include staff information.

Weekly name removals notification sent to CBI.

The system will allow CDEC the ability to restore historical records for viewing in each account that features a name or criminal record that may have been taken down accidentally. This will be based on BIU specific role or System Admin only.

This should also only be allowed during certain time frames. (Permissions required) There at times when the inclusion of new fields and design functionality to track, work, and store all criminal related information will change or update. This might include: new fields, letters, roles, records, etc.

Maintain history tracking for all data in the system.

The system sends reports through Move-It daily. Maintain all email in compliance with CJIS guidelines for email and encryption protocol.

Printing abilities dependent on roles and reports.

The system will allow reporting for CJIS audit and other BIU purposes. These include, but are not limited to the following:

Number of individual who were given an eligible during a specific time frame, number of may takes, must takes, Icons; etc.

The system has and must continue to track user changes. This is available at a field level and accessible by role only.

The system is built for manual entry of FBI information. If changes are needed, Offeror would support changes needed by the Background Investigation Unit. This may include automatic upload of FBI information.

The system provides CJIS compliance surrounding all items in the BIU Background Check Process.

The system connects applicants to multiple license numbers for background purposes. Individuals connected to multiple license numbers have the background information linked to all license numbers.

Business Requirements (continued) Describe how the Offeror will support these criteria The system receives data from Salesforce pertaining to Trails Abuse and Neglect. This is based on matching logic within the systems and API.

The system operates on an AWS CJIS compliant solution in .govcloud The system is built in .Net 5 The programming language is C# The System has a Multi-factor authentication required for login to system.

We pass limited information to our PDIS Salesforce system pertaining to background statuses.

Access control are role-based and granular and enforced at each level, including separate accounts for users and elevated privileges.

Testing completed in collaboration with CDEC BIU Staff.

Analytics and Reporting Describe the Offeror's capabilities to support the following analytic and reporting requirements System should track all transactions including user, date, time, and what was viewed, printed, modified on the application, database, and server layers.

System has On-demand and/or ad-hoc customized reporting and/or analytic tools.

Reports include filters to all users to produce reports using data fields.

Reports are based on role access.

System includes BIU, Supervisor, and user dashboard capabilities and include information based on the customizability by user role.

General Technical Requirements Describe the Offeror's ability to support the following General Technical requirements

System support will utilize separate environments for development, testing, and staging prior to production, with the appropriate isolation between. Provide documentation regarding the promotion of code through environments.

Testing and conversion should not use live or real data. If it does, it will need to be encrypted and hardened to standards.

Describe your software configuration management process. Including all artifacts related to a software release organization and storage in a configuration management tool and the process to back-out any application updates if required.

Provide a rigorous transfer to production process. All solution software changes will be reviewed and approved by authorized personnel before placing into production libraries.

The support will allow for modular expansion.

The system requires the use of a web browser, it must meet the OIT standards for web browser.

The Offeror will provide for software upgrades/system maintenance that does not affect the production system (no downtime during the business operations window) in a load-balanced environment.

The support will include configuration control for all configurable elements, including auditing, rollback, roll-forward, and configuration change transactions with the ability to both import and export configurations to maintain configuration integrity.

System has one single rules repository where Department business rules are defined, updated and maintained while maintaining role based access. The business rules may be deployed at multiple locations.

General Technical Requirements (continued) Describe the Offeror's ability to support the following General Technical requirements

Describe your version control capabilities. A set of business rules may have multiple versions, some of which can be concurrently deployed. This is important because, in some instances, past business rules may need to be retroactively applied.

The Offeror will make provisions for a procedure, that at no additional cost, all data can be exported upon termination of contract with full referential integrity.

The support will include an archival and retrieval processes if data is archived.

Clearly identify responsibilities, costs, and entitlements related to minor and major upgrades, hotfixes, and patches.

The system includes system-driven notification capabilities.

The data within the system and sent to and from the system must be secure. Describe your processes to ensure the data within the solution will be secure. Explain your data encryption efforts (e.g. the data encrypted at rest and in flight) and practices employed to guard against vulnerabilities.

Include a warranty from the point of delivery against known viruses, malicious software and backdoor access. Ensure there will be no ability for the Offeror or the Offeror's agents to access data without authorization from the State of Colorado subsequent to the Support of the system.

If the application is to be installed as an application on client computers and/or mobile devices, specify the minimum and recommended desktop and/or mobile device requirements (hardware configuration, software compliment) with the purpose clearly identified. Note if the system can be made as a ThinApp, or otherwise served by Thin Clients.

Incident reporting/response procedures shall be identified and documented.

OIT and potentially FBI/CBI collaboration will be required.

The system uses edit checks to avoid duplicate customers being entered into the system comparing customers (e.g., name, driver's license or ID, SSN, street and city address, etc.).

Rules should be defined using a set of simple user interfaces. Department employee(s) will be able to maintain the rules. Any changes or updates will be made in a joint effort with the Offeror and BIU staff this will include any training necessary to ensure all parties are familiar with procedures.

Enumerate any anticipated 3rd party software licenses to be used in the applications (both commercial and OSS)

Availability Requirements Describe the Offeror's ability to support the following Availability requirements The Offeror will ensure the production environment is available no less than 99.950% of the time per month. Availability of the Test, Sandbox, and Training environments will be available upon agreed times with CDEC.

The Offeror will perform scheduled maintenance or planned system outages outside of the business day, unless prearranged, and final approval from BIU and CDEC.

The Offeror will notify system users of system unplanned outages and should resolve outages within 4 (four) hours, or should provide an approved work around for delivering files to their destinations.

Operations and Maintenance Describe the Offeror's ability to support the following Operations and Maintenance requirements Describe your support services to be provided to CDEC users.

Maintain a prioritized application change request list. All change requests will be accompanied by detailed requirements.

Application enhancements and updates will be based on this list and the direction of the Department.

Describe your processes to alert the customer of data breaches or potential breaches.

Develop the system utilizing IT best practices, be tested, and free of bugs and/or defects at time of delivery (production implementation).

User Interface/User Experience Requirements Describe the Offeror's ability to support the following Operations and Maintenance requirements

Maintain field and screen validation including, but not limited to: a visual distinction between mandatory and non-mandatory fields; field validation of data upon entry of the screen for posting; screen validation upon submission; display errors on the appropriate screen in plan language for the user.

Include robust editing and validation routines for all mandatory fields, including clearly indicating data that fails validation.

Maintain or provide specific actionable plain-English error messaging.

Maintain and provide standard graphical user interface (GUI) items, such as drop-down menus, to make selection easier for frequently used fields, such as form names, commands, and all code tables. The solution will allow for adding/updating items in the drop-down menu.

Maintain users with standard form navigation and allow easy movement from one work area to another via mouse or keyboard.

Maintain default, configurable values for fields based on previous input, referential lookup, or other mechanisms.

Maintain support, where applicable, the ability to execute multiple transactions in the same screen or session.

Maintain a consistent look-and-feel, including cognitive ergonomics, workflow progression and complexity in order to minimize training and maximize intuitive user interaction.

Maintain full Boolean searching, including phonetic indices where appropriate.

Maintain the recognized sounds-like phonetic algorithm search.

Maintain the user interface response time of .5 seconds or less.

Include file/data integrity evaluation and recovery capabilities beyond backup and selective recovery.

Maintain support the use of pointing devices, hot keys, key combinations, buttons, touch screens, and hyperlinks.

Support pre-fill fields in appropriate preformatted screens, eliminating redundant data entry and without impacting the usability.

Allow users to move forward and backward to complete data fields.

Maintain lookup tables for valid values for fields.

Infrastructure Requirements Describe the Offeror's ability to support the following Infrastructure requirements The system is adaptable and use extensible architecture for future expansion and scalability without the need for architectural modifications.

The system is designed to support the capacity requirements to accommodate increases in throughput and workload over the lifetime of the system.

Database Requirements Describe the Offeror's ability to support the following Database requirements The system provides a logging feature that should contain logs entries, changes, and/or deletions to any data (data transaction recovery log).

The system processes data in real time. This means that any data changes entered while the hardware is online will take effect immediately.

Have point-in-time recovery capabilities. This means that upon any failure, the database can be recovered to the last point of consistent state.

Identity and Access Requirements Describe the Offeror's ability to support the following Access requirements System has role and permissions-based privileges and granted via security groups.

Roles include no less than administration, read-only, read-write, audit, add/update users.

Roles may be field, screen, site-specific, multi-site, or application-wide.

Require users to log on to the system.

The systems provide the ability to change password at setup, at sign-on, and during the course of a logged-in session for local accounts.

System provides a means for users to recall or reset their password - Forgot My Password. System has the ability to reset a password for the user, if necessary.

System allows system administrators the ability to easily configure and update user roles and privileges while the application is online.

System has a single centralized repository for users and their access information (authentication, authorization, and accounting, also referred to as AAA) so that users have one username and one set of authentication credentials (such as a password) and that all user attributes and authorization are managed in one place, including date of entry.

Security Requirements Describe the Offeror's ability to support the following Security requirements Encryption of data in transit to FIPS 140-2 standards Designated confidential data (e.g., Social Security Number) shall be encrypted at rest and in transit throughout public or private networks.

Must be at least to 256 bit strength and FIPS 197 certified, including encrypt data down to field level.

Your process/methodology for asset classification to ensure that sensitive or confidential information is encrypted during storage and transmission.

The Offeror will meet the same personnel security standards as state employees as outlined in the Personnel Security Policy, P-CISP-012.

Technical Requirements

File details come from the government source that posted it. Updated .