CSM_Technology_Questionnaire.pdf
PDF 581 KB Posted
- Attached to
- CAO Criminal Case Management System
- Solicitation number
- 306
- Issued by
- Los Angeles County, San Francisco City, California
About this file
This is a Technology Questionnaire document related to a cloud-based Criminal Case Management System solicitation issued by the City Attorney's Office of the City of Santa Monica, California. The questionnaire serves as an evaluation tool for vendors proposing solutions for the Criminal Division's case management needs. The City Attorney's Criminal Division currently operates using Microsoft SharePoint and a legacy case management system while prosecuting criminal misdemeanor offenses, traffic infractions, and local ordinance violations referred primarily by the Santa Monica Police Department. The proposed solution must be cloud-based (SaaS), include functionality for case matter generation, auto-fill and import capabilities, document generation and tracking, restitution tracking, and seamless integration with law enforcement systems and the Los Angeles County criminal court system. The system must support role-based permissions, audit trails, robust search capabilities, subpoena generation, MS Office integration, and electronic discovery capabilities, while maintaining DOJ certification compliance and supporting legacy data migration.
The Technology Questionnaire addresses critical vendor requirements across multiple domains including proposed architecture (on-premise versus cloud deployment), backend technologies and core development platforms, database specifications, cloud environment compatibility with the City's AWS infrastructure, component and conceptual architecture, user experience and interface design, authentication and authorization mechanisms including Active Directory and LDAP support, data encryption standards for transit and at rest, API availability and associated costs, product release cycles, customization and configuration capabilities, and operational support requirements. Vendors are required to demonstrate compliance with applicable security standards including PCI DSS, HIPAA, and CJIS where applicable, define data ownership terms and service level agreements for data restoration, and describe procedures for data deletion upon service termination. The questionnaire also requires vendors to clarify initial data load procedures, customer data access methods, integration capabilities with existing City systems, and anticipated staffing and support roles needed to maintain the application throughout its operational lifecycle.
View the file
Other files
Show all 13
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
Technology Questionnaire
These questions are pertaining to all the proposed components in the architecture
Proposed Solution(s)
What does proposed solutions look like?
On-prem v/s cloud (SaaS, PaaS, IaaS) v/s hybrid
Is it browser-based?
List sample URLs for all proposed components including administration, reporting and end-user List Supported Browsers Is it Device Agnostic? (responsive/Adaptive Design)
Is it Client-Based?
Installation client (windows/ Linux etc.)
Local data storage
Back-end technologies
What is/are Core Development Platform (e.g. java, .net, react, angular etc or combination of these)
What is Database backend (e.g. sql, mysql, postgres etc.)
Cloud v/s On Prem
If on-prem, list server/network requirement. Provide Technical architecture diagram Could this be installed on City’s AWS environment?
Are there maintenance/Managed services option available?
If cloud: PaaS or SaaS: multitenant v/s single tenant Please provide Technical Architecture Diagram
Component Architecture
Please share Conceptual Architecture of all the technical components proposed.
How these components interact with each other?
How these components interact with City's environment (AD, SSO, AWS, other applications)?
User Experience
Please share user flow diagram depicting how user interact with different technical components List all user interface List all possible user roles (admin, report writer, developer etc.) and their interactions points (Urls/desktop client)
Authentication and Authorization
What mechanism are supported for user authentication and authorization (AD.LADAP)?
Could authorization be set up for the role-based security?
Data
What is the procedure for initial data load/data conversion?
How do we (as a customer) get access to our data? (ODBC connection, API access) Is data encrypted in transit, end-to-end, between the client/endpoint system?
Is data encrypted at rest within the application service, including but not limited to the database?
What are the terms governing ownership of data?
What terms and SLA have been defined around data restoration?
Describe the process for deleting customer data on request or upon termination of service.
Does the proposed solution meet the requirements of PCI DSS, HIPAA and CJIS standards where applicable? If so, please describe the ways in which you comply; for PCI, describe compliance with various sections of the DSS.
Integration
Is there a public API to support Read/Write operations?
If either API is available, are there additional charges for use of either the READ ONLY or WRITE access? Is so, please detail these charges.
Application
What is product release cycle?
How do customer request enhancement?
How are customization handled? What changes City could make in terms of configuration?
Operational Support What are operational support requirements?
What are anticipated future roles required to support the application?
File details come from the government source that posted it. Updated .