RFI DEMS Vendor Response.docx

Request for Information (RFI) Digital Evidence Management System Vendor Response

Please provide the following information electronically. You may provide the requested information as a completed attachment or in the body of an email.

1. Contact Information:

a. Name of individual responding

b. Name of agency/organization

c. Mailing address

d. Email address

e. Phone number

2. Provide a brief history of your organization and describe your experience providing, developing, implementing, or supporting digital evidence storage, investigative technology, case management or comparable secure information-management systems.

3. Identify specific software, platforms, or systems your organization has previously developed, implemented or provided that are comparable to the capabilities contemplated by this RFI. Include, where applicable, status of development or implementation, length of time in production, type and size of organization served, number of users, and relevant governmental, public-safety investigative, or multi- jurisdictional experience.

4. Describe the proposed platform, including its overall architecture, hosting options, principal modules, supported evidence and data types, and core operational capabilities. Describe the platform's ability to provide a centralized environment for managing multiple concurrent incidents or investigative matters, maintaining detailed records, aggregating authorized information across organizational jurisdictional boundaries, and providing awareness of status, activities, and operational impacts.

5. Describe how the platform supports the complete digital evidence life cycle, including collection, transfer, preservation, integrity verification, metadata capture, indexing, organization association with an incident or investigative matter, search and retrieval, review, sharing, retention, legal hold, archival, export and authorized disposition.

6. Describe the platform’s architecture and controls for maintaining evidentiary and chain of custody. Address encryption, authentication, protection of original evidence, integrity verification, audit trails, tamper-evident or immutable logging, tracking of evidence access and activity, and controls designed to prevent unauthorized access, alteration, disclosure, or deletion.

7. Describe how your platform would support internal and external messaging, notifications, and alerts; enable collaboration across agencies and jurisdictions; maintain communication logs and message histories; support e-mail, SMS, and in-application messages.

8. Describe the platform’s role-based access controls, configurable user roles and permissions, user provisioning and deprovisioning, privileges-user controls, supervisory and administrative access, multi-agency user management, and audit logs of user activity. Describe how authorized administrators can access and manage current historical incidents or investigative information.

9. Describe the platform’s mobile and field capabilities, including functionality available through smartphones, tablets, laptops, or other authorized devices. Address ease of use, accessibility, configurable interfaces, workflow complexity, offline or limited-connectivity functionality and features designed to reduce user burden and the learning curve of new users.

10. Describe how the platform supports API integration, system-to-system data exchange, and imports and exports using standard formats. Identify capabilities for integration with existing and future federal, state, local, and enterprise systems, including identity- management environments, investigative or incident- management systems, GIS and data-visualization platforms, mobile or camera technologies, and other authorized systems. Identify any technical dependencies, limitations, or additional costs associated with integrations.

11. Describe the platform’s capabilities for providing situational awareness and common operating picture, where applicable. Address integration with GIS and data-visualization platforms; real-time or near-real-time information; configurable dashboards; reporting; analytics; supervisory reviews; historical information; and tools for monitoring operational status, evidence activity, workload, storage, retention and other relevant metrics.

12. Describe any currently available or planned artificial intelligence, machine-learning, or automation capabilities. Examples may include transcription, content recognition, classification, advanced search, summarization, redaction assistance, workflow automation, prioritization, or analytics. Describe human-review requirements, audit functions, privacy and security controls, whether State information is or would be used to train vendor or third-party models, and the ability to enable, disable, or restrict AI functionality.

13. Describe how the proposed platform would be implemented to meet the objectives of this RFI. Address implementation methodology, project phases, configuration, testing, validation, data migration, integrity verification, cutover, change management, staffing requirements, anticipated implementation timeframe, ease of deployment, and approaches for minimizing disruption to ongoing operations.

14. Describe administrator and end-user training provided as part of implementation and ongoing operations, including training materials, user guides, documentation, new-user training, and refresher training. Describe ongoing system maintenance, updates, technical support, system monitoring, issue resolution, service levels, escalation procedures, upgrades, and post-implementation assistance.

15. Describe the platform’s ability to accommodate growth in users, evidence type, and data volume, file sizes, storage requirements, and concurrent system activity. Address system availability, redundant infrastructure, backup methods and frequency, recovery time objectives (RTO), recovery point objectives (RPO), disaster-recovery testing, service-restoration procedures, and methods for maintaining access to critical information during outages or disruptions.

16. Provide a summary of available cost structures, packages, licensing models, and associated capabilities. Identify costs related to implementation, configuration, users, storage capacity, data volume, retention periods, migration, API or system integrations, training, technical support, maintenance, archival storage, data egress, professional services, optional modules, AI capabilities, and other one-time or recurring expenses. Explain how costs may change based on changes of the number of users, storage requirements, functionality, or level of service selected.

17. Identify foreseeable technical, operational, cybersecurity, migration, integration, bandwidth, staffing, implementation, legal, records-management, and cost challenges or dependencies associated with implementing and operating the proposed platform. Identify known product limitations and potential vendor lock-in considerations. Describe how State-owned evidence, data, metadata, audit histories, chain-of-custody records, integrity information, and configuration information can be exported or returned upon contract expiration, termination, or transition to another system, including available formats, anticipated timeframes, transition assistance, and associated costs. Finally, identify any emerging technologies, industry developments, capabilities, risks, or other considerations that the State should evaluate that have not otherwise been addressed in this RFI.

How to Respond

All respondents should respond to this RFI with the information requested above no later than the deadline indicated on the first page of the announcement. Responses to this RFI must be made via email.