The file's text, extracted by GovTribe without its formatting.
City of Pasadena Functional Requirements
INSTRUCTIONS FOR COMPLETING FUNCTIONAL REQUIREMENTS
1) Vendor Response For each numbered line item requirement, the vendor must indicate Y, 3P, C, F, or N with an “X” in the Vendor Response column, according to the following legend:
| Y |
| Fully supported by the current release of the software. |
| 3P |
| Supported with third party software (i.e. software not directly owned or controlled by the vendor submitting the proposal. |
| C |
| Customization is required to meet the requirement (e.g. changes to the underlying code must be made; a report must be specifically designed; causes additional upgrade work in order to implement new versions or upgrades, etc.) |
| F |
| Future functionality: Supported in the next release of the software. |
2) If the vendor responds with 3P, C, or F, the vendor must provide additional information in the comments column:
· For “3P”, the vendor must explain what third party software application or service is required, any integration requirements, and the vendor’s relationship with this third party.
· For “C”, the vendor must explain the nature and amount of customization required, and experience with the same or similar modifications.
· For “F”, the vendor must explain the functionality in the new release, the expected general availability release timing and provide surety that the functionality will be included.
3) The vendor must also identify which module(s) the required functionality is part of in the final column when applicable.
The information must be completed and submitted in the format provided.
Key Functional Criteria (R=Required, P=Preferred, E=Explore) Vendor Response
Y 3P C F N Comments *If vendor responds with 3P, C, or F, additional information must be provided as noted on Instructions page.
Applicable Module(s)
General System Features
| R |
| 1. The in-car digital video system shall consist of a digital video recorder, miniature color camera, a microphone mounted within the law enforcement vehicle. It shall be capable of providing a clear audio and video record of incidents. |
| R |
| 2. The color camera shall be capable of recording video in multiple resolutions, up to 4K resolution. |
| R |
| 3. The camera system will include the following views at a minimum: one human-equivalent FOV camera facing forward, one wide-angle view facing forward, one IR-capable camera in the prisoner compartment(s) as equipped, and one rearward-facing camera. |
| R |
| 4. The camera shall be optimized for nighttime performance. |
| R |
| 5. The camera shall not obstruct the driver’s field of view. |
| R |
| 6. Mobile Data Computer Interface – The system shall have the ability to interface with the vehicle's mobile data computer (MDC) with optional software provided by the vendor that allows the user to perform at least the following functions; login and logout, camera and microphone activation, record and stop, record event categorization and record event playback. Describe the solution. |
| R |
| 7. The system shall include an in-car microphone that can be mounted anywhere within vehicle. The system shall provide a separate audio channel for recording conversations picked up by this microphone. |
| R |
| 8. Each in-car digital video recording system shall be supplied with a comprehensive Installation / Programming / Operations manual. |
| R |
| 9. The system will be capable of Automated License Plate Reader (ALPR) functionality. This should be able to integrate with law enforcement information systems such as FLOCK or equivalent systems. Describe how this system turns every deployed vehicle into a sensor on our network to develop criminal intelligence. |
| R |
| 10. Does the system incorporate analytical tools so that after the fact, we can review routes during an emergency response and synch this map view with the recorded video during playback? |
| R |
| 11. System must be able to integrate with Versaterm CAD RMS system in order to tag video with the appropriate General Offense (incident) numbers. |
| R |
| 12. The system must have the ability to integrate with the evidence.com portal for sharing of evidence with our external partners in the District Attorney’s office, City Prosecutor’s office, other police agencies, and to fulfill Public Records Act requests. |
| R |
| 13. The system will allow for a “single pane of glass” for reviewing body-worn camera (BWC) footage from the department’s existing AXON BWCs and synched MAV footage; this can be accomplished by exporting to the evidence.com portal, importing BWC footage to the vendor’s portal, or through third party software. The vendor will also describe this process and any potential costs involved in this. |
| R |
| 14. The system shall provide a reporting capability that identifies all in‑car video recordings that remain uncategorized/untagged. The report shall allow authorized users to view, filter, and export a list of untagged videos, including details such as date/time of recording, unit ID, officer ID, and any other available metadata. |
| E |
| 15. The system will allow for reviewing recorded footage using a mobile device (such as a phone or laptop), either through a wireless LAN or via WAN access. Please describe how this is accomplished. |
| R |
| 16. Does the system have AI search, redaction, and transcription tools? Are there tools for map analysis during recorded events which can be synched with video? Describe these. |
| R |
| 17. The system will need to integrate with real time crime center software in the future; please describe your integration with Fusus, Oracle, etc. |
| R |
| 18. The system will have the capability to record footage originally recorded in the background before it is overwritten, sometimes referred to as “record after the fact”; this will allow the system to be used as an investigative tool when footage was not originally saved. Please describe your process to do this. |
Digital Video Recorder
| R |
| 19. The system shall be designed for mobile applications. It shall mount in standard equipment consoles or glove boxes found in most law enforcement vehicles. It can also be mounted in any remote location of the vehicle (i.e., trunk, etc.). |
| R |
| 20. System shall not require removal of the factory radio or be mounted in the factory radio location. |
| R |
| 21. Media shall record to digital device (hard drive, flash memory, etc.) in the vehicle; eMMC memory will not be accepted. |
| R |
| 22. System shall be capable of automatically capturing and appending both pre-event and post-event video. These settings are to be independently adjustable and restricted by a supervisor. Pre- and post-event times shall be continuous with the record event. |
| R |
| 23. System shall be able to playback previously recorded video while simultaneously recording new video on the equipped cameras and microphones. |
| R |
| 24. The system shall offer the capability of maintaining the location of the patrol vehicle by Global Positioning System (GPS). When installed, the system shall be able to show vehicle coordinates and speed in the on screen text and recorded metadata. Additionally, GPS shall allow the system to automatically and continually update its date and time to ensure accuracy across the fleet. |
| R |
| 25. Digital video files shall be transferred from the system via wireless upload technology. System shall be capable of manual transfer through removal of storage media. |
| R |
| 26. System shall automatically transfer video the moment the vehicle is in range of the wireless network. The user shall not be required to initiate the transfer in any way. |
| R |
| 27. System shall support a vehicle driving off or losing its network connection during video transfer without losing any video. The user shall not be required to interface or initiate this in any way. |
| R |
| 28. The system shall protect the buffered version of the event until the server confirms receipt of the entire record event. |
| R |
| 29. System shall be able to authenticate video prior to removal from the vehicle. |
| R |
| 30. The power control switch shall allow the system to automatically power on after the vehicle’s ignition is switched on and shut down at a specified time to preserve the vehicle’s battery. |
| R |
| 31. The system shall include a simple method for selecting a programmed officer name from a list for rapid login at shift changes; this includes dual officer login for two-man units. |
| I |
| 32. System will synchronize with the department’s Active Directory for Officer single sign-on (SSO) logins. |
| R |
| 33. System shall be fully functional if the Officer fails to login. |
| R |
| 34. Manual activation of the system into the RECORD mode shall be attainable by means of a backlit push button on the face of the control panel or MDC integrated software. |
| R |
| 35. Automatic trigger of the system into the RECORD mode shall be accomplished by any of the following user programmable methods: |
a. Activation of the vehicle’s emergency lights.
b. Activation of any auxiliary input.
c. Exceeding of a predetermined GPS speed threshold.
d. System detection of a g-force event above a configured threshold.
e. Activation of a Taser Conducted Energy Weapon within 30’ of the vehicle.
f. Activation of a Taser Signal (formerly Signal Sidearm) within 30’ of the vehicle.
| R |
| 36. To allow the user to covertly record, the system shall have the ability for the user to quickly disable the system’s screen and LED indicators while automatically activating all audio and video recording—a stealth mode for either blacked out conditions or surreptitious recording of prisoners. |
| R |
| 37. The system shall include a background record mode to record at all times. When this mode is active, the system shall record whenever the system is turned on. When the system is set to RECORD mode, the system shall stop the background record and immediately begin a separate recording. Once the event has concluded and the officer presses the STOP button, the file closes and background record mode starts automatically. |
| R |
| 38. System shall have a graphical user interface for converting any portion of the hard drive buffer (background record mode) as a new event recording. |
| R |
| 39. System shall allow record events to be categorized via the on screen menu. Categorization selections shall be administratively configurable. |
| R |
| 40. Activation of the system’s STOP mode shall be accomplished only by pressing the backlit STOP button on the face of the control panel or MDC integrated software. |
| R |
| 41. The system shall have a means of detecting when the system is inadvertently left in RECORD mode. The system shall allow an option to prompt the user. |
| R |
| 42. When the PLAY button is pressed a list of all prior recordings on the DVR shall appear on the LCD monitor screen or MDC integrated software for review. |
| R |
| 43. The system shall be able to ensure that the user cannot delete or edit video data from the vehicle; only system administrators will have the ability to delete recordings. |
| R |
| 44. System shall record event metadata including but not limited to event category, date, time, officer name(s), record status, emergency lighting status, brake status, and GPS coordinates for fast searching and video navigation. |
| R |
| 45. The system shall have an on-screen Disc Usage Meter that graphically shows the user how much video is on the storage media and how much space remains. Additionally, the system shall have audible and visual warnings when the drive is nearing its capacity. |
| ?R |
| 46. The system will be able to background record footage; the system will be able to store a minimum of 40-60 hours of footage before the recording loop is overwritten at 1080p resolution for the main camera and 720p for the prisoner compartment. |
| R |
| 47. The system shall be manufactured in a factory that is IS0-9000 certified. |
| R |
| 48. The system shall be FCC Part 15 accepted. |
System Configuration for Motorcycles
| E |
| 49. All of the specifications described in items 10 - 46 for the digital recorder shall be applicable and optimized for use with BMW R1250/1300 series of motorcycles. The motorcycle configuration shall utilize weatherproofed components. |
| E |
| 50. The LCD monitor shall include weatherproofing for moisture resistance and a sunshield for optimal outdoor visibility. |
Back Office and Client Software
| R |
| 51. System shall push configurations and firmware upgrades wirelessly and without any user intervention in the car. Settings shall be group based to allow a single setting change to affect a large number of cars instantly. All push operations shall be fully authenticated and encrypted to ensure no wireless snooping and spoofing. |
| R |
| 52. Once pushed to the in-car system wirelessly, firmware upgrades shall occur without any user intervention in the car. |
| R |
| 53. System shall have fully customizable user and group based permissions that allow administrators to tailor each user's ability to use the system. |
| R |
| 54. System shall allow the City to define and enforce customizable data‑retention policies, ensuring that any evidence or data collected is automatically deleted or archived on a schedule or manually, in accordance with the Pasadena Municipal Code, City administrative rules, and Police Department regulations. Data shall not be retained beyond the City‑designated period unless deliberately preserved in connection with an investigation. |
| E |
| 55. System shall have import and export digital video and audio capabilities in a non-proprietary format, so that it can potentially integrate with stationary cameras deployed within the department. Please specify the file types supported by the system. |
| E |
| 56. System shall authenticate photographs, including identifying the camera used to take them. |
| R |
| 57. System shall track all evidential file usage, such that all videos, photographs, and documents will be auditable to identify when moved, reviewed, or exported. |
| R |
| 58. When exporting video, the system shall automatically include a standalone playback application to be included with the exported video. When used on another computer, the playback application shall run solely from the export media (DVD, USB, etc.) and not require any software installation on the local playback computer. Video shall also be accompanied by a full audit log showing every time the event was moved, reviewed, or exported with full MD5 hash verification data. |
| R |
| 59. When exporting other forms of digital evidence (photographs, documents, etc.), the files shall be accompanied by a full audit log showing every time the file was moved, reviewed, or exported with full MD5 hash verification data. |
| R |
| 60. System shall be roles based, and not device based to allow the video to be viewed, imported, and exported by a user with the appropriate permission from any client computer. |
| R |
| 61. Vendor shall provide the option of on-site storage solution capable of maintaining approximately two years’ worth of data on server, based upon needs and categories set in software. |
| R |
| 62. System shall provide means to archive data flagged to be kept beyond two year retention period. |
| R |
| 63. Vendor shall offer 3, 5 and 7 year maintenance services to extend coverage after the one-year warranty expires; as part of this description, please describe the lifecycle of your current product, with when it was introduced and how long it will be supported. |
| R |
| 64. The in‑car video system shall support configuration of the preformatting of characters (e.g., “PA2026-XXXXX”) that is automatically applied to all video file names or labels to ensure consistent and uniform identification of recordings across the organization; this will be in keeping with the GO numbers generated by the Versaterm CAD system. |
| R |
| 65. The vehicle impact sensor shall acknowledge significant vehicle impact and shall activate the RECORD mode on the system to capture the incident through the pre-event record function. |
| E |
| 66. The City currently uses Motorola’s EL4 system to store MAV video data; will the proposed system allow this data to be migrated? Will the migration keep metadata intact? Please describe how your firm will handle this data. |
General Technology
| R |
| 67. Mainstream server/platform. Prefer Microsoft SQL Server and Microsoft Windows Server. |
| R |
| 68. Indicate platforms supported. |
| R |
| 69. Indicate databases supported. |
| R |
| 70. Indicate source code language. |
| R |
| 71. Web services: Describe your support (e.g. XML messaging, SOAP, Web API, etc.). |
| R |
| 72. Utilizes software framework, such as .NET |
| R |
| 73. Describe your Active Directory and LDAP integration. |
| R |
| 74. Web-enabled architecture with published open Application Program Interfaces (APIs). Describe your integration tools, such as APIs and Web services. |
| R |
| 75. Security to menu or screen level by group or user. |
| R |
| 76. Remote access: Briefly describe your remote access capabilities, supported technologies and plans. |
| R |
| 77. Disaster recovery and emergency backup: Briefly discuss your capabilities, options, strategy and recommendations. |
| I |
| 78. Application configuration tools – Describe how your system may be reconfigured to meet business operational changes using configuration tools versus customization. |
| R |
| 79. Capability to handle unique security roles (needs); assign role-based access to the system. |
| R |
| 80. Describe the wireless and wired networking and bandwidth requirements for all features and functions of proposed system to perform satisfactorily. |
| R |
| 81. Describe the Wireless Infrastructure and Wireless Access Point proposed and whether these are using proprietary vs standard communication and security protocols. |
| R |
| 82. Advise if the proposed system supports the use of Meraki Wireless Access Points security standards. |
| R |
| 83. What integration does this system have with Real Time Crime Center or Real Time Intelligence Center software, such as Fusus, Oracle, etc. |
Data Ownership and Security
| R |
| 84. Describe data ownership with regard to learning for AI, ML, and automated decision-making systems and your safeguards to prevent unauthorized use of customer data. |
| R |
| 85. Data must be stored using a US-based servers with applicable safeguards using government-approved systems, such as the Azure cloud or equivalent. Please describe your data handling, and how backups are and exported data are secured. |
| R |
| 86. Provide your procedures for responding to legal requests for customer data, including notification practices. |
| R |
| 87. If data can be viewed on a mobile device, can data also be stored on a mobile device? If so, describe any security safeguards that are applied. |
Installation and Support
| R |
| 88. The vendor will provide installation (either through their own personnel or through a certified third-party installer) into the vehicles; as part of this process, the vendor will provide all materials needed to ensure the system is fully operable to include (but not limited to): cables, fuse blocks, antennae, etc. |
| R |
| 89. Are there any specialized tools required to maintain the system, either for the software or hardware? |
| R |
| 90. Is there a training and/or certification process for Pasadena City employees to maintain the system. |
In-Vehicle Mobile Audio and Video (MAV) Recording RFP – City of Pasadena Exhibit “A” – City of Pasadena Functional Requirements A-15