CommandCentral Aware integration with 9-1-1 call data, video management systems, License Plate Recognition technology, and other system sources supports the overlay of V300 location data to provide real time intelligence. Additionally, our rules engine can be configured to notify users when specific mission parameters are met and to eliminate user distraction.
Key Features and Functionality
• Detachable Battery
• Durability
• Exceptional Audio-Visual Quality
• High Data Security
• Post-Event Evidence Retrieval
• Multiple Docking options
• Officer-Friendly User Interface
• In-Field Tagging
• Auto Activation/Triggers
Exhibit A: Contract Documentation Requirements
G Motorola Solutions Services Solution Description 21
May 10, 2022 Item #11 Page 398 of 604
DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7 SECTION 2
City of Carlsbad, CA
February 16, 2022
STATEMENT OF WORK
2.1 STATEMENT OF WORK OVERVIEW
2.1.1 2.1.2
In accordance with the terms and conditions of the Agreement, this Statement of Work ("SOW') defines the principal activities and responsibilities of all parties for the delivery of the Motorola Solutions ("Motorola") service as presented in the PremierOne Cloud Subscription Services Description document to City of Carlsbad, CA hereinafter referred to as "Customer". When assigning responsibilities, the phrase "Motorola" includes our subcontractors and third-party partners.
Deviations and changes to this SOW are subject to mutual agreement between Motorola and the Customer and will be addressed in accordance with the change provisions of the Agreement. ·
Unless specifically stated, all Motorola work is considered complete upon Motorola fulfilling the Motorola Responsibility listed in a Responsibility Table and providing the deliverable(s) listed in the Motorola Deliverables table.
Motorola and the Customer will work to complete their respective responsibilities in accordance with the mutually agreed upon governing project schedule. Any changes to the governing project schedule will be mutually agreed upon via the change provision of the Agreement.
The number and type of software or subscription licenses, products, or services provided by Motorola or its subcontractors are specifically listed in the Agreement and any reference within this document as well as subcontractors' SOWs (if applicable) does not imply or convey a software or subscription license or service that are not explicitly listed in the Agreement.
The specific software applications that comprise the System are outlined in the price page of the Agreement.
Award, Administration and Project Initiation
Project Initiation and Planning will begin following execution of the Agreement between Motorola and the Customer. Unless otherwise stated, all Motorola work will be completed remotely.
Project Management Definitions
The following project management terms are used in this document. Since these terms may be used differently in other settings, these definitions are provided for clarity. • Project Schedule means the schedule providing dates and timeframes for completion of tasks and deliverables during the course of the Project. The Project Schedule is subject to change at the mutual agreement of Motorola and the Customer.
Exhibit A: Contract Documentation Requirements
22 Statement of Work Motorola Solutions C.,
May 10, 2022 Item #11 Page 399 of 604
DocuSign Envelope ID: EEOOOOEC-B190-469F-887C-147E3BCEAFF7 City of Carlsbad, CA
February 16, 2022
2.1.3 2.2
2.2.1 • Project Management Plan is composed of the Communications Management Plan, Risk Management Plan, and Change Management Plan that provide the criteria for managing those tasks within the project.
General Customer Responsibilities
In addition to the Customer Responsibilities stated elsewhere in this SOW, the Customer is responsible for:
1. All Customer-Provided equipment including hardware and third party software necessary for access or delivery of the service not specifically listed as a Motorola deliverable. This will include end user workstations, Internet Service Provider (ISP), network equipment, telephone/CPE or TDD equipment and the like.
2. Configuration, maintenance, testing and supporting the third party systems that the Customer operates and which will be interfaced to as part of this project. The Customer is responsible for providing Application Programming Interface (API) documentation to those systems that document the integration process for the level of interface integration defined by Motorola.
3. Active participation of Customer Subject Matter Experts (SM E's) in project delivery meetings and working sessions during the course of the project. Customer SM E's will possess requisite knowledge of Customer operations and legacy system(s) and possess skills and availabilities to operate and manage the System.
4. The provisioning of Customer Code Tables and GIS data as requested by Motorola. This information must be provided in a timely manner in accordance with the Project Schedule.
5. Electronic versions of any documentation associated with the business processes identified
6. Provide a facility with the required computer and audio-visual equipment for training and work sessions as defined in the Training Plan.
7. Ability to participate in remote project meeting sessions using Google Meet.
PROJECT ROLES AND RESPONSIBILITIES
Motorola Project Roles and Responsibilities Overview
A Motorola team made up of specialized personnel will be appointed to the project under the direction of the Motorola Project Manager. Team members will be multi-disciplinary and may specialize in different products. Team members will be engaged in different phases of the project as necessary.
The personnel role description noted below provides an overview of typical project team members. There may be other personnel engaged in the project under the direction of the Project Manager.
Exhibit A: Contract Documentation Requirements
fl Motorola Solutions Statement of Work 23
May 10, 2022 Item #11 Page 400 of 604
DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7
2.2.1.1 2.2.1.2
Motorola Project Manager
City of Carlsbad, CA
February 16, 2022
Motorola's project management approach has been developed and refined based on lessons learned in the execution of hundreds of system implementations. Using experienced and dedicated people, Project Management Institute standardized processes, and integrated software tools for effective project execution and control, we have developed and refined practices that provide design, production, and testing that is optimized to deliver a high quality, feature-rich system.
A Motorola Project Manager will be assigned as the principal business representative and point of contact for the organization. Responsibilities of the Project Manager include:
1. Managing the Motorola responsibilities related to the delivery of the project.
2. Project scheduling and management of the assigned Motorola personnel and applicable subcontractors/supplier resources.
3. Management of the Change Order process per the Agreement.
4. Maintain project communications with the Customer.
5. Identification and management of project risks.
6. Collaborative coordination of Customer resources in an effort to minimize and avoid project delays.
7. Measuring, evaluating, and reporting progress against the Project Schedule.
8. Conducting remote status meetings on a monthly basis by the Project Managers to discuss project status.
9. Participate in weekly calls regarding current activities.
10. Preparing and submitting a monthly status report that identifies the activities of the previous month, as well as activities planned for the current month, including an updated project schedule and action item log.
11. Providing timely responses to issues related to project progress raised by the Customer.
Motorola Application Specialist
The Motorola Application Specialist will work with the Customer to enable the project team to support and guide the Customer with the provisioning of the System. Responsibilities of the Motorola Application Specialist will include:
1. Provide consultation services to the Customer regarding the provisioning and operation of the System.
2. Provide provisioning training to the Customer to provide the knowledge to setup and maintain the system.
3. Complete base provisioning and module configuration.
4. Complete the provisioning ownership handoff to the Customer.
5. Complete the project defined milestones and tasks as defined in this SOW.
Exhibit A: Contract Documentation Requirements
24 Statement of Work Motorola Solutions f.'
May 10, 2022 Item #11 Page 401 of 604
DocuSign Envelope ID: EE000OEC-B19D-469F-887C-147E3BCEAFF7 City of Carlsbad, CA
February 16, 2022
2.2.1.3 2.2.1.4
2.2.1.5 6. Provide guidance on the Customer's operational Change Management needs relative to the use of the System.
7. Provide training as defined by this SOW and described in the Training Plan.
Motorola GIS Analyst
The Motorola GIS Analyst specializes in geographical information technology.
Responsibilities of the Motorola GIS Analyst include:
1. Performing the GIS Analysis on the Customer supplied GIS source data.
2. Providing the Customer the results of the GIS Analysis based on the requirements of the Motorola GIS Build Requirements document.
3. Consultation services regarding the conversion of Customer GIS source data for Motorola use.
4. Provide G IS Training as defined in this SOW and in the Training Plan.
5. Import of the Customer provided GIS data into the System.
6. Geocoding Data, Centerlines to support Routing and Response Area Polygons (for CAD)
Motorola Solution Architect
The Solutions Architect is responsible for the delivery of the technical elements of the System. They confirm the delivered technical elements meet contracted requirements. They are engaged throughout the duration of the delivery.
Motorola Cloud Activations Team
The Cloud Activations team will establish the cloud tenant for the Customer environment, work with the Customer to grant Customer access, and coordinate with the Customer to establish access to CC Reporting.
2.2.1.6 Motorola Customer Success Advocate
2.2.1.7 A Customer Success Advocate (CSA) will be assigned to the Customer following the Go Live event. Their role is to assist the Customer with maximizing the use of their Motorola software and service investment by being the Customer's trusted advisor in actively managing, escalating, and logging issues with Support, Product Management, and Sales while providing ongoing Customer communication about progress, timelines, and next steps.
Motorola Customer Support Services T earn
Motorola's Customer Support team will provide ongoing support, Customer Support Plan (CSP) following Customer commencement of beneficial use of the System.
Exhibit A: Contract Documentation Requirements
G Motorola Solutions Statement of Work 25
May 10, 2022 Item #11 Page 402 of 604
DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7
2.2.2 2.2.2.1
Customer Roles and Responsibilities
City of Carlsbad, CA
February 16, 2022
The success of the project is dependent on early assignment of key Customer resources. It is critical that these resources are empowered to make provisioning decisions based on the Customer's operational and administration needs. The Customer project team should be engaged in the project from initiation until beneficial use of the system. The continued involvement in the project and use of the system will convey the required knowledge to maintain the system post completion of the project. Note that in some cases, one person may fill more than one role. The project team must be committed to participate in activities for a successful implementation. Team member roles are generally described below:
Customer Project Manager
The Customer Project Manager will act as the primary Customer point of contact for the duration of the project. The Project Manager will be responsible for managing the Customer project team including the timely facilitation of their efforts, tasks, and activities. This includes the management of any Customer vendors that are subcontractors.
Responsibilities of the Customer Project Manager include:
1. Maintaining project communications with the Motorola Project Manager.
2. Identifying the efforts required of Customer staff to meet the task requirements and milestones in this Statement of Work and Project Schedule.
3. Consolidating all project-related questions and queries from Customer staff to present to the Motorola Project Manager.
4. Reviewing the Project Schedule with the Motorola Project Manager and assisting in finalizing the detailed tasks, task dates, and responsibilities.
5. Measuring and evaluating progress against the Project Schedule. 6 . Monitoring the project to ensure that resources are available as scheduled.
7. Attending status meetings.
8. Providing timely responses to issues related to project progress raised by the Motorola Project Manager.
9. Liaising and coordinating with other agencies, Customer vendors, contractors, and common carriers.
10. Reviewing and administering change control procedures, hardware and software certification, and all related project tasks required to maintain the Project Schedule.
11. Ensuring Customer vendors' adherence to overall Project Schedule and plan.
12. Assigning one or more personnel who will work with Motorola staff as needed for the duration of the project, including at least one application administrator for CAD, Mobile, as applicable, and one or more representative(s) from the IT department.
13. Identifying the resource that has the authority to formally acknowledge and approve change orders, approval letter(s), and milestone recognition certificates and to approve and release payments in a timely manner.
14. Providing supervised building access to Motorola personnel to all facilities if necessary where any on premises components of the system will be installed during the project.
Exhibit A: Contract Documentation Requirements
26 Statement of Work Motorola Solutions fl
May 10, 2022 Item #11 Page 403 of 604
DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7 City of Carlsbad, CA
February 16, 202.2
15. As applicable to this project assuming responsibility for all fees for licenses and inspections and for any delays associated with inspections due to required permits.
16. Providing reasonable care to prevent equipment exposure to contaminants that cause damage to the equipment or interruption of service.
17. Ensuring a safe work environment for Motorola personnel.
2.2.2.2 Customer Transformation Lead
The Customer Transformation Lead, who may or may not be your Project Manager, must be able to holistically represent your organization and be able to work cross functionally between Motorola, your organization and all stakeholders involved in the delivery of your new system. The transformation lead must be empowered to acknowledge the resource and time commitments required of your organization and authorize Motorola to proceed with scheduling the Project Kickoff event.
2.2.2.3 Customer System Administrator
The Customer System Administrator is responsible for managing the technical efforts, tasks and activities of their system as defined in the Customer Support Plan (CSP).
2.2.2.4 Customer IT Personnel
IT personnel provide required information related to Azure Active Directory, LAN, WAN, ISP, wireless networks, server and client infrastructure and must also be familiar with connectivity to internal, external and third party systems to which PremierOne Cloud systems will interface.
2.2.2.5 Customer Application Administrator
The Customer Application Administrator is responsible for the management of the Customer owned application provisioning maintenance. The Application Administrator will be involved early in the project starting at the Business Process Review (BPR), attend the Provisioning Workshop and Train the Trainer Training and remain engaged throughout the project to ensure that they are able to maintain the system provisioning post Customer Provisioning handoff. Responsibilities of the Customer Application Administrator include:
1. Participate in overall delivery and training activities to gain an understanding of the software, interfaces, and functionality of the system.
2. Participate with the SMEs during the BPR, provisioning process, and training.
3. Have the authority to make global provisioning choices and decisions, and will be the point(s) of contact for reporting and verifying problems and maintaining provisioning.
4. Obtain inputs from other user agency stakeholders related to business processes and provisioning.
Exhibit A: Contract Documentation Requirements
f.l Motorola Solutions Statement of Work 27
May 10, 2022 Item #11 Page 404 of 604
DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7
2.2.2.6 Customer GIS Analyst
City of Carlsbad, CA
February 16, 2022
The Customer G IS Analyst is responsible for the development and maintenance of all of the GIS data used in the PremierOneCloud system. The Customer GIS Analyst must have working experience with Esri software including ArcCatalog, ArcMap, and ArcPro, including knowledge of model builder, toolbox tools, and general database structure. Also, it is very important to have a working relationship with the named Application Administrator(s). The GIS Administrator will be heavily involved in the data preparation for the System as well as data maintenance throughout the term of the Agreement. This will include but is not limited to the following standard responsibilities:
1. Providing GIS data in the correct schema
2. Developing, maintaining and updating GIS data
3. Support of the GIS elements used in the Cloud Services (Server and clients)
2.2.2.7 Subject Matter Experts
The Subject Matter Experts (SME) (Super Users) are the core group of users that will be involved with the business process reviews and analysis, the provisioning process, including making global provisioning choices and decisions, and training. These members should be experienced users in the working area(s) they represent, i.e. dispatch, patrol, etc. and should be empowered to make decisions related to provisioning elements, workflows, screen layouts, etc.
2.2.2.8 Customer Training Representative
Training representatives will be the point of contact for the Motorola Application Specialist when policy and procedural qu~stions arise, act as course facilitators, and are the Customers' educational monitors.
2.2.2.9 Additional Resources
Additional resources, such as trainers and database administrators may also be required.
2.2.2.10 Customer Agency Stakeholders
User agency stakeholders, if the system is deployed in a multi-agency environment, are those resources representing agencies outside of the Customer Agency. These resources will provide provisioning inputs to the SM Es if operations for these agencies differ from that of the Customer agency.
2.3 PROJECT INITIATION AND PLANNING
A clear understanding of the needs and expectations of both Motorola and the Customer are critical to the success of the project. Project Planning requires the gathering of project specific information that is critical to setting clear project expectations and guidelines, creating the Project Management Plan, Project schedule, and setting the foundation for a successful implementation.
Exhibit A: Contract Documentation Requirements
28 Statement of Work Motorola Solutions 0
May 10, 2022 Item #11 Page 405 of 604
DocuSign Envelope ID: EE0000EC-819O-469F-887C-147E38CEAFF7 City of Carlsbad, CA
February 16, 2022
2.3.1 Project Planning Session• Teleconference/Web Meeting A Project Planning Session will be scheduled after the Agreement has been executed between the assigned Motorola and Customer Project Managers.
The Business Process Review Agency Pre-Kick Off Survey is a Google survey that is sent to the Customer to collect Agency specific information such as dispatch logistics, communication center information, operational process, and workflow. The information in the survey is used to prepare for the Business Process Review.
The Aware Technical Discovery Requirements document contains information required to establish network connectivity and to perform integration and establish connectors with additional and third-party systems.
The GIS Discovery Survey is used to assist Motorola Solutions in gathering information to better understand the Customer's current capabilities and needs relating to the GIS.
The agenda will include:
• Review the Agreement documents
• Review the applications, query(ies) and interface(s) described in the PremierOne Cloud Subscription Services Description document
• Review project delivery requirements as described in this SOW • Discuss Customer involvement in provisioning and data gathering to confirm understanding of the scope and time commitments required • Review the PremierOne Agency Build Guide. The PremierOne Agency Build Guide provides a structural overview of the Customer's System. The includes the definition of Agency Type Code, Name, ID and default areas.
• Review the initial project schedule and incorporate Customer feedback resulting in the governing Project Schedule. The Project Schedule will be maintained by Motorola and updated through mutual collaboration. Schedule updates that impact milestones will be addressed via the Change Order provision of the Agreement. • Finalize the Project Management Plan
• Confirm requirements for CJIS background investigations and/or contractors, fingerprint requirements for Motorola employees and/or contractors. Required fingerprints will be submitted on Motorola Solutions provided FBI FD-258 Fingerprint cards • Review Virtual Desktop (VD) and Learning exPerience Portal (LXP) role in the delivery and discuss required Customer provided information to access them • Customer obligation to manage change among the stakeholder and user communities • Provide the Business Process Review Agency Pre-Kick Off and GIS Discovery Survey • Review project completion criteria and the process for transitioning to support Completing the Business Process Review Agency Pre-Kick Off Survey and the GIS Discovery Survey are critical Project Tasks. Delayed, incomplete, or inaccurate information may have a significant impact on the Project Schedule.
Exhibit A: Contract Documentation Requirements
@ Motorola Solutions Statement of Work 29
May 10, 2022 Item #11 Page 406 of 604
DocuSign Envelope ID: EEO000EC-B19D-469F-887C-147E3BCEAFF7 Motorola Responsibilities
1. Schedule the remote Project Planning Session
2. Provide the initial Project Schedule and Project Management Plan City of Carlsbad, CA
February 16, 2022
3. Provide the Business Process Review Agency Pre-Kick Off Survey and the GIS Discovery Survey
4. Provide the Agency Build Guide
5. Provide the Aware Technical Discovery Requirements document
6. Finalize the Project Management Plan
7. Baseline the Project Schedule
8. Provide and manage Issue/Resolution Checklist
Customer Responsibilities
1. Identify and engage project team members responsible for carrying out the system implementation.
2. Provide input to the Project Schedule dates
3. Provide information necessary to perform background checks for Motorola employees and/or contractors.
4. Review and complete the Business Process Review Agency Pre-Kick Off and the GIS Discovery Survey within ten (10) business days of the Project Planning Session so as not to impact the Project Schedule.
5. Provide required information to complete the PremierOne Cloud File Build tablesFile.
Required information is to be provided prior to GIS Check Point #1 Addressing Validation, Routing, and Boundaries.
6. Complete the information on the Aware Technical Discovery Requirements document prior to the Project Kickoff Session.
7. Review and provide feedback on the Project Management Plan Motorola Deliverables -Project Planning Session
Project Schedule Baseline
Project Management Plan
Business Process Review Agency Pre-Kick Off Survey
GIS Discovery Survey
PremierOne Agency Build Guide
Aware Technical Discovery Requirements document
Completion Criteria -Project Planning Session
The Project Planning Session is considered complete upon conclusion of the meeting.
Milestone -Project Planning Session
Mutual agreement to Project Schedule and Project Management Plan Exhibit A: Contract Documentation Requirements
30 Statement of Work Motorola Solutions 0
May 10, 2022 Item #11 Page 407 of 604
DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7 City of Carlsbad, CA
February 16, 2022
2.3.2 2.3.3
Project Kickoff Session -Teleconference/Web Meeting
The objective of the Project Kickoff meeting is to provide a high-level overview of the service and delivery process to the Customer's team. During the Project Kickoff meeting the Motorola Project Manager will provide an overview of the following:
• A high level review of the Project Deliverables
• Roles and responsibilities for the project team members • A high level review of the baseline Project Schedule including project milestones and checkpoints
• Discuss any project related questions
Motorola Responsibilities
1. Schedule the remote Kickoff Teleconference/Web Meeting
2. Prepare the Kickoff Meeting agenda.
3. Distribute any documentation that the Customer should review in advance of the Kickoff Meeting.
4. Conduct the Kickoff Teleconference/Web Meeting.
Customer Responsibilities
1. Schedule the personnel from the Customer project team to attend. This should include key stakeholders that have authority or responsibility over the project.
The Project Kickoff Session is considered complete upon conclusion of the meeting.
GIS Planning Session -Teleconference/Web Meeting
A GIS planning session will be scheduled to review the GIS Build Requirements Document and complete an overview of the GIS components of the project. The agenda will include:
• Review the Motorola GIS Build Requirements Document
• Discuss Customer GIS skill-set and responsibilities
• Review the requirements of the Customer GIS sample data that is required • Discuss any GIS related project questions
Providing the GIS Customer Data is a critical Project Task. Delayed, incomplete, or inaccurate information may have a significant impact on the Project Schedule.
Motorola Responsibilities
1. Schedule the remote GIS Planning Session
Customer Responsibilities
1. Review the GIS Build Requirements document prior the meeting.
Exhibit A: Contract Documentation Requirements
G Motorola Solutions Statement of Work 31
May 10, 2022 Item #11 Page 408 of 604
DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7
2.3.4 City of Carlsbad, CA
February 16, 2022
2. Provide the GIS sample to Motorola within ten (10) business days of the GIS Planning Meeting so as not to impact the Project Schedule
Customer delivery of sample GIS data within 10 days of GIS Planning Session.
Interface Planning Session -Teleconference/Web Meeting
An Interface Planning Session will be scheduled to discuss the user experience presented by each contracted interface as defined in the PremierOne Cloud Subscription Services Description document and the Interface Fuctional Descriptions (IFDs) in Section 8. The agenda will include:
• Conduct a review of the functionality delivered with each interface • Discuss interface deployment requirements (NOA, network information, API and access credentials required to connect to third party systems) • Review Interface Project Schedule tasks and milestones The interface deployment requirements (NDA, network information, API and access credentials required to connect to third party systems) are needed to begin deployment of the interfaces. Delayed, incomplete, or inaccurate information may have a significant impact on the Project Schedule.
Motorola is not responsible for third party vendor management, scheduling or additional cost for software, customization, development, or testing unless the work is defined in this SoW or amended to the Agreement via a Change Order.
Motorola Responsibilities
1. Identify additional information such as third party API, SDKs, data schema and any internal and 3rd party documents necessary to establish interfaces.
2. Conduct reviews of the interfaces to explain how each functions as well as any dependency on third party API, SDKs, data schema and any internal and third party documents necessary to establish interfaces with local and remote systems.
3. Provide Motorola Non-Disclosure Agreements (NOA) as required.
Customer Responsibilities
1. Provide the required interface deployment requirements (NOA, network information, API and access credentials required to connect to third party systems) within ten (10) business days of the Interface Planning Meeting so as not to impact the Project Schedule.
Exhibit A: Contract Documentation Requirements
32 Statement of Work Motorola Solutions G
May 10, 2022 Item #11 Page 409 of 604
DocuSign Envelope ID: EEO000EC-B19D-469F-887C-147E3BCEAFF7 City of Carlsbad, CA
February 16, 2022
2.3.5 Mutually accepted IFDs
Customer delivery of interface deployment requirements within 10 days of Interface Planning session.
Connectivity Planning Session• Teleconference/Web Meeting A Connectivity Planning Session will be scheduled to discuss the connectivity required for the service. The agenda will include:
• Review Azure Active Directory requirements.
• Review of connections of end user workstations to the Cloud service. • Interfaced system connectivity to the service.
• Plan for State/NCIC query connectivity (as applicable) Network and connectivity to the Cloud environment is a Customer responsibility and is crucial to the operation and use of the Cloud services. Delayed, unavailable, or inadequate network connectivity may have a significant impact on system operation and the Project Schedule.
Motorola Responsibilities
1 . Review the workstation connection process.
2. Provide the connectivity process for the included interfaces.
3. Review connectivity options for the CLETS/NCIC interface.
4. Provide the information required for DOJ approval.
Customer Responsibilities
1. Ensure resources knowledgeable on the Customer networks attend the review.
2. Provide the details related to the interfaced systems for the services.
3. Provide the requirements for connecting to the State/NCIC interface.
4. Provide the network connectivity to the end user workstations, State/NCIC, and interfaced systems.
5. Complete the base PremierOne Cloud Services connectivity requirements within ten (10) business days of the Connectivity Planning Session so as not to affect the Project Schedule.
The Connectivity Planning Session is considered complete upon conclusion of the meeting.
Exhibit A: Contract Documentation Requirements
C., Motorola Solutions Statement of Work 33
May 10, 2022 Item #11 Page 410 of 604
OocuSign Envelope ID: EEOOOOEC-B190-469F-887C-147E3BCEAFF7
2.3.6 City of Carlsbad, CA
February 16, 2022
Complete the base connectivity requirements within ten (10) days of planning session.
CommandCentral Aware -Video Management System (VMS) Design Review
The objective of the VMS Design Review is to collect all information required to connect and configure the CommandCentral Aware and VMS lnterface(s).
Motorola Responsibilities
1. Identify the specific inputs required from Customer for all VMS interfaces.
2. Add VMS interface details to the VMS Design Review Report.
Customer Responsibilities
1. Discuss information on third party API, SDKs, data schema and any internal and 3rd party documents necessary to establish interfaces with all local and remote systems and facilities within ten '( 10) days of the Project Kickoff Meeting so as not to impact the project schedule.
2. Work with the owners of the new and existing data and video equipment to establish network connectivity (where applicable).
3. Gather data required to configure VMS interfaces and provide information as CSV or in Excel spreadsheets.
4. For VMS interfaces that will be configured for each location where Network Video Recorders (NVR) and cameras are installed, the Customer must provide all camera name, coordinates and IP mapping and the network plan in CSV or Excel files prior to Motorola commencing configuration of the VMS interfaces.
The Connectivity Planning Session is considered complete upon conclusion of the meeting.
2.4 PREMIERONE CLOUD SERVICES PROJECT EXECUTION
The execution of PremierOne Cloud is done through a series of milestones that are designed to enable the success of the project. Motorola will work closely with the Customer to complete provisioning, validate operational readiness, and complete user training in preparation for operational use.
This service utilizes the PremierOne Cloud deployment model which enables the core capabilities of the service for the Customer's operations. PremierOne contains features, functionalities and modules that are capable of being enabled but may not be in the scope of this project. The features, functionalities, and modules that are within the scope of this project are described in Section 1 Subscription Services Description document.
Exhibit A: Contract Documentation Requirements
34 Statement of Work Motorola Solutions 0
May 10, 2022 Item #11 Page 411 of 604
DocuSign Envelope 10: EE0000EC-819O-469F-887C-147E3BCEAFF7 City of Carlsbad, CA
February 16, 2022
2.4.1 2.4.1.1
Understanding time is of the essence with respect to System delivery, both the Customer and Motorola will strive to perform in accordance with the Project Schedule and take steps necessary to mitigate potential delay. Motorola's implementation delivery services are based on the following durations, dependent upon the product mix of the System:
• The services sold in a PremierOne Cloud CAD deployment model are based on a six (6) month deployment.
• Actual project duration will be established as part of the Project Schedule development activities.
PremierOne Cloud Hardware and Environment
General Hardware and Environment Requirements
The Customer will provide hardware and/or an environment that conforms to the following general requirements:
Customer Responsibilities
1. Supply hardware, operating system software, third party components, and other elements not specifically identified as being provided by Motorola.
2. Provide advanced authentication for Mobile/Hand held device connectivity if required.
3. Provide a network diagram depicting all the devices, device types, and interfaces that the service will connect to and through, including, but not limited to all blocked ports, hubs, switches, routers, firewalls, and any other network equipment.
4. Provide IP addresses on the Customer's network for the required on-premise equipment (i.e the Anchor Server). All server names and IP addresses behind Motorola Firewalls cannot be changed.
5. Provide external interface connection demarcation points at locations agreed to by Motorola. These locations shall normally be adjacent to the cloud interface appliance.
6. Provide access, administrative or otherwise, to appropriate systems, locations, information, tools, and equipment to ensure proper connectivity, installation, operations, and maintenance of the service.
7. Provide 24-hour access to a secured two-way Internet connection to the cloud interface appliance and firewalls for the purposes of deployment, maintenance, and monitoring.
8. Provide a site to site VPN with at least 4 addressable IP's on the inside subnet capable of establishing and maintaining an IPSec tunnel with 75Mb/s of throughput.
9. The Motorola delivery model is reliant upon our ability to perform most tasks remotely, which requires secure, remote broadband access for remote deployment, monitoring, and support of the cloud interface Anchor Server appliance. It is understood that remote access to on-premise server and Customer's network must be supervised, which supervision will be provided. Customer-provided high-speed internet access with a minimum of 10 Mbps is required at the time of project kickoff and must remain available to Motorola throughout warranty and support periods to accommodate remote support of the service. In the event that dedicated links are required, a minimum of 7.5 Mbps upload and download access is required. It is the Customer's responsibility to ensure Exhibit A: Contract Documentation Requirements
G Motorola Solutions Statement of Work 35
May 10, 2022 Item #11 Page 412 of 604
DocuSign Envelope ID: EEOOOOEC-819D-469F-887C-147E3BCEAFF7 City of Carlsbad, CA
February 16, 2022
that the aforementioned capacity is available. In the event remote broadband access is not available to Motorola preventing us from delivering the contracted service remotely, Motorola will provide service on-site at additional cost. The additional cost will be presented to the Customer via the change provision of the contract prior to the delivery of the on-site service.
10. Provide, install, maintain, and service any software as required for anti-viral, anti- malware protection on workstations that access the service. If the software requires connectivity to a central server for maintenance and updates, the connectivity including ports and access needs to be provided.
2.4.1.2 Component Specifications
Motorola will provide Commsys Connect CIC. The Customer will provide the server hardware and firewall devices.
PremierOne Cloud Anchor Hardware
Customer Responsibilities
1. Provide, install and configure server hardware, operating system software, VMWare, firewall devices, Lantronix External Device Server and SQL Standard. Specifications will be provided at the Planning Meeting.
A. Provide a VMware host environment capable of supporting two VMs. i. Windows Server VM, 4vcpu, 16GB RAM and 3 HOD 120/120/25GB ii. Linux VM, 2VCPU, 8GB RAM and 1 HOD 20GB
B. Verify the VM has connectivity to the internet and the following addresses, which are commonly used by CloudConnect:
i. https://idm.imw.motorolasolutions.com (443) -IDM
ii. https://aware-api.usgov.commandcentral.com (443) -Ingest iii. https://admin-api.usgov.commandcentral.com (443) -Admin 1v. https://aware-publisher-ws.usgov.commandcentral.com (443) -Publisher (WebSocket)
v. https://registry.commandcentral.com (443) -Registry vi. https://oneinterfaceblobstore.blob.core . usgovcloudapi. net/( 443) -I mageNideo upload
vii. Additional Endpoints For IMW/LRRP Interfaces
viii. https://ccinterfaces-ccbroker-prod . usgov. commandcentral. com/api/ccinterfaces- ccbroker (443)-IMW/LRRP
ix. https://ccinterfaces-sasgen-prod.usgov.commandcentral.com/api/sasgen (443) - SAS Token
x. https://qrwbubhpaovhj-sbu.servicebus.usgovcloudapi.net (443) (Websocket) (inbound-outbound)
Exhibit A: Contract Documentation Requirements
36 Statement of Work Motorola Solutions G
May 10, 2022 Item #11 Page 413 of 604
DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7 City of Carlsbad, CA
February 16, 2022
2.4.1.3 Motorola Responsibilities
1. Provide the CloudConnect VM image to Customer.
2 . Remotely support installation of VM image on Customer hardware.
CommSys Connect CIC
Motorola Solutions Responsibilities
1. Provide CommSys Connect CIC.
PremierOne Cloud CAD Local Workstation
The Customer will procure and provide local (fixed) workstation hardware that conforms to the requirements laid out in this section.
• Windows 10 operating system.
• Monitor(s) -two or three with recommended resolution 1920 x 1080 (per client preference: i.e. three for CAD dispatch, two for CAD call taker, etc.). • QWERTY Keyboard with 12 function keys
PremierOne Cloud Field Workstation
The Customer will procure and provide field (mobile) workstations/devices that conform to the requirements laid out in this section.
• Android smartphones and tablets with Android 8 -10.
• iPhones and iPads with iOS 11 -13.
• Windows laptops and tablets with Windows 10.
PremierOne GIS Workstation
The Customer will procure and provide GIS workstation hardware that conforms to the requirements laid out in this section.
• Android smartphones and tablets with Android 8 -10.
• iPhones and iPADs with iOS 11 -13.
• Windows laptops and tablets with Windows 10.
CommandCentral Aware Workstation
The Customer will procure and provide Aware workstation hardware that conforms to the requirements laid out in this section.
• Processor-Intel Xeon 6136 @3.0 GHz (12 cores).
• Memory-32 GB.
• Drive-One NVMe 512G SSD.
• NIC-1 GB port NIC.
• OS-Windows 7 Professional or Windows 10 Pro.
• Graphics Card-NVIDIA Quadro P2000
• 27-inch Narrow Bezel IPS Display, 2560X1440
Network and Other Environment Specifications
Unless otherwise stated in this SOW, the Customer will provide a network environment that conforms to the requirements laid out in this section. The Customer will provide an Exhibit A: Contract Documentation Requirements
fl Motorola Solutions Statement of Work 37
May 10, 2022 Item #11 Page 414 of 604
DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7 City of Carlsbad, CA
February 16, 2022
environment sufficient to support the transaction volume generated during Customers peak operational periods.
Network Connection Requirements
PremierOne Cloud client connections must meet the following requirements:
• Stable internet connection.
• Small Jitter (packet delay variation) -below 200ms, recommended <30ms. • Small Ping roundtrip time -below 1 00ms, recommended <20ms. • Small Packet Loss -no more than 1 %.
• Bandwidth: 1 Mbps per fixed client (will vary with specific usage). • Provide cloud connectivity services for desktop CAD user clients per specifications. • Provide for outbound Internet connectivity initialized by Cloud Anchor Server.
Multiple paths are preferred for the PremierOne Cloud CAD Service. ISP connectivity to the Azure Public Edge is required for the CAD client connectivity. Interfaces to on-premise systems use a VPN device that requires connectivity to the Azure Public Edge. The Customer is responsible for providing all connections to the cloud.
Mobile Network Requirements
PremierOne Mobile functionality is designed for 3G and high-end 4G networks. 3G network connectivity is required, but faster 4G connectivity is highly recommended. The Customer will provide a 3G/4G wireless network infrastructure and connectivity with routing between the Mobile clients and the cloud that meets or exceeds these minimum requirements.
Customer Responsibilities
1. Supply Mobile Device Management (MOM) software for Handheld devices.
2. Supply Mobile Device Management (MOM) software for Mobile devices, as desired by the Customer.
3. Provide wireless connectivity for mobile clients to the Azure cloud. Optimal application performance on mobile workstations requires 4G connectivity.
Aware Network and Bandwidth Requirements
• Two (2) static IP addresses, corresponding subnet masks/default gateway, and available NTP and DNS IP to the Cloud Anchor Virtual Machines.
• Three (3) static IP addresses, corresponding subnet masks/default gateway, and available NTP and DNS IP to the Cloud Anchor Server.
• One (1) network port for each VMS server.
• One (1) network port for each VMS analytics appliance • Provide network ports that are 1 GB capable and network routable. • Minimum bandwidth needed between the Cloud Anchor server and the CommandCentral Aware platform is 1.1 Mbps.
• Low latency is critical for real-time operations. The speed with which data appears on the Aware display depends in large part on how quickly the information is presented to the Aware interface. Major contributors to the latency are network delays and the delay time from occurrence of an event to when that event information is presented to Aware from the source application (i.e., CAD, AVL, ALPR, etc.). Consequently, although the Exhibit A: Contract Documentation Requirements
38 Statement of Work Motorola Solutions 0
May 10, 2022 Item #11 Page 415 of 604
DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7 City of Carlsbad, CA
February 16, 2022
Aware strives to provide near-real-time performance, Motorola provides no guarantees as to the speed with which an event (or video stream) appears on Aware once the event is triggered.
Vigilant LPR Requirements
Bandwidth requirements:
• 1 Gbps hardwire switched network between the Vigilant server and Cloud Anchor. • Upload of ALPR data to the LEARN backoffice requires approximately 350 Kbps for each scan per second. Depending on maximum scan volume, the maximum bandwidth may need to be adjusted.
• The RTSP video feed from cameras requires a 1Gbps hardwire switched network device to allow for data communications exceeding four connected cameras.
Firewall requirement:
• CommandCentral Aware Workstation needs access to the IP addresses of Cloud Anchor and Vigilant server. Access to Cloud platform endpoints. • Ports that need to be open-TCP 80, TCP 443, TCP 331 O (or custom SQL Database Engine listening port that might have been configured for security reasons). • The basic service requirements of the system through a firewalled environment consist of: HTTPS web based calls to a cloud back-office solution (LEARN) with S3 image storage. Typically, through a mobile broadband endpoint. A local IP listener for RTSP video stream is used from cameras with TCP communications. • Ingress requirements (firewall traffic in): For Wireless Broadband we require TCP port 443 to communicate with the LEARN server backoffice to receive acknowledgement responses from the client. Camera Communications: TCP port 2000, 3000, 4000, 5000 (LAN/DSP).
• Egress requirements (firewall traffic out): For Wireless Broadband communications the ALPR client requires TCP port 443 to communicate with the LEARN server backoffice.
The HTTPS protocol is primarily used to communicate over TLS 1.0, 1.1, or 1.2 with 128-bit encryption ciphers or better. This allows for the upload of ALPR data to the LEARN web services and request for data from the LEARN services and Google Maps.
ASTRO 25 Radio and Infrastructure Requirements
The solution can be deployed to send location data information using an AST RO 25 radio equipped with a GPS receiver with minimum firmware version 7 .18.8 and at software version R15.00.00 or later. ASTRO 25 system release 7.14 or above is required if the data will be sent via the LMR system. Enhanced Data and Intelligent Middleware (IMW) in addition to a firewall to connect the system GEN and internet securely including a packet data gateway and GGSN for each zone are used to send the location updates and events can be enabled as part of that effort. Customer will be responsible to provide internet connection and will allow Motorola to add any necessary firewalls.
• GPS Activation and Enabled.
• Packet Data Interface.
• Enhanced Data Enabled.
-Supported on portables-APX 8000, APX 7000, APX 6000, APX 4000, APX 3000. -Supported on mobiles-APX 7500, APX 6500, APX 4500.
Exhibit A: Contract Documentation Requirements
G Motorola Solutions Statement of Work 39
May 10, 2022 Item #11 Page 416 of 604
DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7
2.4.2 • Enhanced Data Port List set to 4001.
ASTRO 25 Voice Priority
City of Carlsbad, CA
February 16, 2022
ASTRO Enhanced Data subscribers give priority to voice transmissions over data.
PremierOne Cloud Business Process Review (BPR)
Motorola will lead the PremierOne Business Process Review (BPR) to understand the Customer's operational processes and workflows. A BPR session will be conducted for each of the contracted System application categories: CAD, Mobile. The information collected in the BPR will provide Motorola the framework for how the System will be provisioned and configured to best meet the Customer's needs and the requirements in the Functional Matrix.
Prior to the Business Process Review, Motorola will schedule a remote session to review the Customer results of the Pre-Kickoff Business Process Survey.
The Business Process Review Customer Survey review and PremierOne Cloud Service Connectivity are required to be completed prior to the Business Process Review.
The Customer is responsible for engaging all user agencies that will be provisioned on the service to obtain required inputs. A single instance of the activities described as "the BPR" will be conducted for a combined law enforcement dispatch audience unless specifically stated otherwise in this SOW. The result will be a single provisioning profile for law enforcement and dispatch. If an additional BPR or provisioning for additional agencies is required, it will be addressed via the Change Order provision of the Agreement.
The BPR should be attended by senior operational decision makers, such as dispatch supervisors, senior call takers/dispatchers and mobile (Windows and Android/iOS) users, as applicable. Manager level personnel can help guide the discussion of policies that have the potential to be improved or modified. Customer personnel will include Motorola's responses to requirements from the Functional Requirements Matrix. The practical input based on experience in the agency's operational environment is often indispensable in the later configuration of the System to effectively meet the Customers needs.
The BPR agenda will include items such as the following:
• Business Process Review Survey Responses
• Provisioning processes for the System applications (CAD/Mobile) • Overview of the System applications
• Agency and Discipline Information (Agency Type,# of Personnel, shift types, etc) • User Permissions/Security
• Provisioning Overview -PremierOne Cloud Agency Build Guide (provided post contract) • For CAD-
-Agency Data Gathering Discussion (Includes incident types, unit status codes, dispositions, unit IDs, and personnel)
-Dispatcher/Responder Workflow -Incident creation to closure -Notifications and Status Monitors
• Reporting Review
• Operational Process Discussion (e.g. Incidents, Units, Call Taker and Dispatcher roles and responsibilities)
Exhibit A: Contract Documentation Requirements
40 Statement of Work Motorola Solutions 0
May 10, 2022 Item #11 Page 417 of 604
DocuSign Envelope ID: EE000OEC-B19D-469F-887C-147E3BCEAFF7 City of Carlsbad, CA
February 16, 2022
2.4.3 2.4.3.1
• Site Visits and Ride Alongs with specific agencies and divisions Motorola Responsibilities
1. Provide the BPR Agenda/Workbook prior to the meeting.
2. Complete the BPR Workbook.
3. Review the documented business processes and provide configuration options.
4. Review the completed BPR Workbook.
5. Conduct a single BPR session for each product in the System (e.g. One for CAD, One for Mobile (Windows and Android/iOS). CAD and Mobile BPR's will be conducted within the same on-site trip.
Customer Responsibilities
1. Review the BPR Agenda/Workbook prior to the meeting.
2. Schedule applicable resources (e.g. dispatch, police and fire/EMS, personnel for sit- alongs and ride-alongs).
3. Provide resources knowledgeable in the Customer's business processes to provide relevant documentation on the workflow and operating procedures.
4. Provide required information to complete the BPR e.g:
A. Field Modification Decisions.
B. Personnel Information Provided.
C. Workflow Configuration.
D. Document Colors.
E. Agency Logo provided -(If desired by Customer).
5. Review the completed BPR Workbook.
Customer provides information required to complete BPR Workbook during BPR session.
PremierOne GIS
GIS Scope Review
The Motorola GIS Analyst meets remotely with the Customer's GIS Administrator to discuss the approach to developing the GIS data for use with the PremierOne Cloud services.
Exhibit A: Contract Documentation Requirements
Q.l Motorola Solutions Statement of Work 41
May 10, 2022 Item #11 Page 418 of 604
DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7
2.4.3.2 GIS Scope Review topics that will be discussed include:
City of Carlsbad, CA
February 16, 2022
• For CAD -Agency Response boundaries needs, routing requirements, premise hazard areas and specifics for address validation using street centerlines, common places, address points, alias tables, and premise hazard areas. • The GIS Data Verification Report describes the Customers source feature classes and data values that have been made available to Motorola. The data is reviewed and any items identified that may impact the applicable functionality of the data within the Motorola System are noted within the GIS Data Verification Report. The GIS Data Verification Report is delivered post contract after review of the Customer GIS data.
The Customer GIS Data is required to be made available prior to the GIS Scope Review.
Motorola Solutions Responsibilities
1. Review GIS Draft Data Verification Report.
2. Discuss current GIS business practices.
3. Discuss frequency of GIS updates to current service and desired frequency.
Customer Responsibilities
1. Ensure availability of GIS administrator for this meeting.
2. Finalize the agency code and beat names for the geodatabase. All of the data will be required but the streets, address points and common places can be works in progress that can be updated as the project moves along. The agency and beat names should be final by provisioning.
Providing the Agency Code and Beat Names for the geodatabase is a critical Project Task. Delayed, incomplete, or inaccurate information may have a significant impact on the Project Schedule.
Completion of PremierOne GIS Review meeting
PremierOne Cloud CAD -GIS Boundaries Meeting
If PremierOne Cloud CAD is contracted as a System component, the Motorola GIS Analyst will meet remotely with the Customer's GIS Administrator and CAD SM Es to discuss and confirm Response Boundaries data that is loaded into the PremierOne Cloud CAD service.
Motorola will provide an overview of the available boundaries types and their function that can be used in the PremierOne Cloud CAD service.
Topics that will be discussed include confirmation of the Customer's Agency Code and Beat Names, and provide an overview of the Agency Code and Beat names role in the PremierOne Cloud CAD to determine if any modifications need to be made prior to import into the PremierOne Cloud CAD.
Exhibit A: Contract Documentation Requirements
42 Statement of Work Motorola Solutions
May 10, 2022 Item #11 Page 419 of 604
DocuSign Envelope ID: EE0000EC-819D-469F-887C-147E3BCEAFF7 City of Carlsbad, CA
February 16, 2022
The Agency Code and Beat Names are required to be provided prior to the GIS Boundaries Meeting.
Motorola Solutions Responsibilities
1. Provide an overview of the Agency Code and Beat Names role in the PremierOne Cloud CAD.
Customer Responsibilities
1. Ensure availability of GIS administrator for this meeting.
2. Confirm Agency Code and Beat Names readiness for load into PremierOne Cloud CAD.
Import of the Agency Code and Beat Names for the geodatabase is a critical Project Task. Delayed, incomplete, or inaccurate information may have a significant impact on the Project Schedule.
Completion Criteria -GIS Boundaries Meeting
Completion of PremierOne GIS Boundaries Meeting
Agency Code and Beat Names imported into PremierOne Cloud CAD
2.4.3.3 GIS CheckPoint Meetings
The Motorola GIS Analyst .and Customer's GIS Administrator will participate in up to five (5) -two (2) hour remote CheckPoint Meetings in accordance with the Project Schedule.
Meeting topics will include:
• GIS Check Point #1 Initial Data Review/Discussion
-Delivery of revised Customer GIS Data based on GIS Draft Data Verification Report is required prior to this Check Point
• GIS Check Point #2 Readiness for GIS Load
-Delivery of revised Customer GIS Data based on GIS Draft Data Verification Report updates is required prior to this Check Point
• GIS Check Point #3 Customer GIS Load Review
-Completion of PremierOne Cloud GIS Import Training is required prior to this Check Point
• GIS Check Point #4 General GIS Check-In
• GIS Check Point #5 GIS Go Live Readiness
Motorola Solutions Responsibilities
1. Conduct the GIS CheckPoint Meetings
2. Evaluate Customer GIS data as submitted
Customer Responsibilities
1. Based on the GIS Data Draft Verification Report, make required changes to meet the Motorola defined GIS requirements
Exhibit A: Contract Documentation Requirements
G Motorola Solutions Statement of Work 43
May 10, 2022 Item #11 Page 420 of 604
DocuSign Envelope ID: EE0000EC-819D-469F-887C-147E3BCEAFF7
2.4.3.4 2.4.4
2.4.4.1 Completion of PremierOne GIS CheckPoints Meetings PremierOne Cloud Services -GIS Draft Geodatabase
City of Carlsbad, CA
February 16, 2022
The draft geodatabase will be created and uploaded to the PremierOne server to support provisioning efforts and draft maps will be created for use by the CAD workstations. Error reports that are produced as a result of developing the draft geodatabase will be delivered to the Customer in updates to the GIS Data Draft Verification Report.
The final geodatabase will be delivered during the GIS Import Tool Training, which is described in the Training Plan.
Following completion of GIS Import Tool Training, the Customer will be responsible for maintenance of the geodatabase.
Motorola Solutions Responsibilities
1. Create the draft geodatabase, maps, and Routing Network.
2. Create the draft geodatabase.
3. Provide updates to the GIS Data Verification Report reflecting any issues found during the geodatabase build.
4. Provide up to three (3) draft geodatabases.
Customer Responsibilities
1. Correct any GIS errors identified in the GIS Data Verification Report from geodatabase build.
This task is completd upon delivery of the third draft geodatabase, maps and Routing Network.
Provisioning
PremierOne Cloud Provisioning
PremierOne Cloud provisioning includes the configuration of user configurable parameters (i.e unit names, personnel, status codes). The PremierOne Cloud System will be provisioned using Motorola standard provisioning parameters and will incorporate Customer specific provisioning. PremierOne Cloud CAD provisioning is defined in Appendix A -PremierOne Cloud Attachment.
Motorola will review the standard provisioning databases as documented in the Provisioning Worksheets during the BPR that will be imported into the System by Motorola. Motorola will Exhibit A: Contract Documentation Requirements
44 Statement of Work Motorola Solutions I'
May 10, 2022 Item #11 Page 421 of 604
OocuSign Envelope ID: EE0000EC-B19O-469F-887C-147E3BCEAFF7 City of Carlsbad, CA
February 16, 2022
complete the provisioning of the System based on the Customer's Call flow, process, and operational processes as applicable to the System.
Customer specific provisioning parameters will be collected from the Customer using Provisioning Worksheets. Motorola will review the Provisioning Worksheets with the Customer to identify the information that is required for the Customer specific provisioning data tables. The Customer will be responsible for completing the Pro0visioning Worksheets in the proper format and with agency specific information. The information collected in the Provisioning Worksheets will be imported into the System exactly as it is provided by the Customer. PremierOne Cloud provisioning activities will be completed for each functional application group included in the System: CAD/Mobile/CommandCentral Aware.
PremierOne provisioning data collection and import is a critical Project Milestone.
Delayed, incomplete, or inaccurate information may have a significant impact on the Project Schedule.
At the completion of the provisioning the System will be configured to allow the evaluation of processes such as Call Flow, Incident Management, Users, Permissions, etc. Motorola will schedule a remote session with the Customer to demonstrate that the PremierOne Cloud provisioning is completed in accordance with the BPR Workbook and the Customer Provisioning Worksheets.
The responsibility for maintaining the Customer provisioning will transfer to the Customer post completion of the Provisioning Workshop.
Motorola Responsibilities
1. Review the standard provisioning database with the Customer prior to the start of provisioning.
2. Provide and review the Provisioning Worksheets with the Customer.
3. Conduct a conference call with the Customer to demonstrate the completeness of the Customer Provisioning Worksheets prior to the start of provisioning.
4. For PremierOne Cloud CAD, the Motorola Application Specialist will complete the standard provisioning as defined in Appendix A -PremierOne Cloud Attachment.
5. For PremierOne Cloud Mobile (Windows and Android/iOS), the Motorola Application Specialist and the Customer's Mobile Administrator(s) will participate in up to four (4) two (2) hour remote CheckPoint Meetings in accordance with the Project Schedule as follows:
A. PremierOne Cloud Mobile Check Point #1 Initial Provisioning Review/Discussion B. PremierOne Cloud Mobile Check Point #2 Follow-up Provisioning Review/Discussion C. PremierOne Cloud Mobile Check Point #3 Customer Provisioning Review/Handoff D. PremierOne Cloud Mobile Client Installation Training (Windows, Android/iOS) is required to be completed prior to this meeting.
E. PremierOne Cloud Mobile Check Point #4 Mobile Trainer the Trainer Readiness F. Due to a large amount of Mobile provisioning being driven off of CAD provisioning, the provisioning of Mobile will generally follow the completion of the base CAD provisioning.
Exhibit A: Contract Documentation Requirements
G Motorola Solutions Statement of Work 45
May 10, 2022 Item #11 Page 422 of 604
DocuSign Envelope ID: EE0000EC-B19O-469F-887C-147E3BCEAFF7
2.4.4.2 6. Complete the import of the data from Provisioning Worksheets.
Customer Responsibilities
City of Carlsbad, CA
February 16, 2022
1. Provide required information to complete the Provisioning Worksheets within ten (10) business days of the so as not to impact the Project Schedule.
Customer completion of Provisioning Worksheets within 10 days of receipt of the worksheets.
PremierOne Cloud Provisioning Workshop(s)
Post completion of the PremierOne Cloud Functional Validation, remote Provisioning Workshop(s) will be conducted. The workshop is a remote working meeting that will include a review and hands on training of the Customer maintained provisioning. Participants in the workshop should be part of the Customer deployment team.
This workshop is not meant to be comprehensive application end user training. The purpose of this workshop is to provide the training and knowledge required to maintain the Customer provisioning.
A PremierOne Cloud provisioning workshop will be completed for each functional application group included in the System: CAD/Mobile (Windows, Android, iOS).
The responsibility of building and maintaining System provisioning will transfer to the Customer post completion of the Provisioning Workshop. Provisioning should be kept updated for operational use by the regular maintenance of all provisioning (Personnel, Units, Caution Notes, Premises).
Motorola Responsibilities
1. Provide the PremierOne Provisioning Agenda and training materials.
2. Post completion of the Provisioning Workshop Motorola will schedule up to two (2) remote two (2) hour Provisioning Check-In sessions with the Customer to verify accuracy of the Customer provisioned data in accordance with the Project Schedule.
3. Complete the PremierOne Provisioning Workshop.
4. Hand-off responsibility for maintaining provisioning data to the Customer.
Customer Responsibilities
1. Review the PremierOne Provisioning Agenda and Motorola provided training materials.
2. Assign participants that will be responsible for the maintenance of provisioning data.
3. Complete the assigned LXP courses prior to the start of the PremierOne Cloud Provisioning Workshop(s).
4 . Assume responsibility for the continued maintenance of the Customer provisioning.
Exhibit A: Contract Documentation Requirements
46 Statement of Work Motorola Solutions C.,
May 10, 2022 Item #11 Page 423 of 604
DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7 City of Carlsbad, CA
February 16, 2022
2.4.4.3 2.4.4.4
Completion PremierOne Cloud Provisioning Workshop(s)
Hand-off the responsibility for provisioning to the Customer CommandCentral Aware Provisioning
Motorola will discuss industry best practices, current operations environment, and subsystem integration in order to determine the optimal configuration for CommandCentral Solution.
Motorola Responsibilities
1. Using the CommandCentral Admin Console, provision users, groups, rules, and Based off Customer Active Directory data.
Customer Responsibilities
1. Supply the access and credentials to Customer's Active Directory for the purpose of Motorola conducting CommandCentral Solution provisioning.
2. Respond to Motorola inquiries regarding users/groups/agency mapping to CommandCentral Solution functionality.
Completion Criteria -CommandCentral Aware Provisioning
CommandCentral provisioning is complete upon Motorola completing provisioning activities in accordance with the mutually approved approach.
CommandCentral Investigate Installation and Credentialing (formerly CommandCentral Analytics Plus)
Motorola Solutions enables the CommandCentral Investigate service during the order process.
LexisNexis accreditation is required to be completed by the Customer prior to the start of the project. Motorola will provide the CommandCentral Investigate credentialing application for the Customer to complete. Following review of the application for accuracy, Motorola will schedule a site inspection which is performed by a third party vendor called Trendsource.
The inspection may take up to 1 hour. The site inspection representative is required to follow a LexisNexis questionnaire during the review. The types of questions asked during the site inspection include general information about your business, the office environment, high- level security features in place for your physical location and user workstations, and questions about how the data will be stored and secured. The representative will take a few photographs, some from the outside of your facility, and some of the general work area where data will be accessed and stored.The site inspection process is designed to avoid any review of confidential processes or practices. The representative will not ask to see the data center or any confidential/secured areas of the business, and they will not take photographs of these areas. They will not ask about proprietary controls such as firewalls or IP restrictions. The representative is not authorized to give a copy of the site inspection questionnaire to the Customer.
Exhibit A Contract Documentation Requirements
G Motorola Solutions Statement of Work 47
May 10, 2022 Item #11 Page 424 of 604
DocuSign Envelope ID: EE0000EC-819D-469F-887C-147E3BCEAFF7
2.4.5 2.4.5.1
Motorola Responsibilities
1. Provide the credentialing application to Customer.
2. Complete site inspection and provide site inspection questionnaire.
City of Carlsbad, CA
February 16, 2022
3. Remotely activate CommandCentral Investigate and initiate email that provides information on setting up the service and provisioning users.
4. Use the CommandCentral Admin tool to enable Customer access to CommandCentral Investigate. This activity is completed during the order process.
5. Connect Customer incident data ingest (PremierOne Cloud CAD).
Customer Responsibilities
1. Complete the credentialing application.
2. Participate in the site inspection and ensure a resource is available to respond to questions during the inspection.
3. Provide access to Motorola Solutions' team to connect incident data ingest.
4. Provide Motorola Solutions with crime type classification.
5. Set up users within CC Admin and set up user permissions groups.
CommandCentral Investigate subscription enabled and access verified.
CAD Client Installation
PremierOne Cloud CAD Client
The Customer will access PremierOne Cloud CAD client through a Citrix Virtual Application.
The PremierOne Cloud Clients will need to be available throughout the delivery process.
Motorola Responsibilities
1. Provide remote PremierOne Cloud client installation overview/instruction
2. Verify PremierOne Cloud Client installation for up to two (2) clients Customer Responsibilities
1. Provide the CAD client workstation in accordance with the specifications presented in the PremierOne Cloud Subscription Service Description document
2. Participate in Motorola PremierOne Cloud client installation overview/instruction
3. Complete installation for remaining PremierOne Cloud clients Customer completes CAD Client Installation on Remaining CAD Workstations Exhibit A: Contract Documentation Requirements
48 Statement of Work Motorola Solutions G
May 10, 2022 Item #11 Page 425 of 604
DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7 City of Carlsbad, CA
February 16, 2022
2.4.5.2 2.4.5.3
2.4.6 PremierOne Cloud Mobile Client Installation (Windows, Android/iOS) The Customer can download the PremierOne Cloud Mobile client from an on-line app store.
Motorola will provide the Customer app store locations from which the client can be downloaded and installed. PremierOne Cloud Mobile (Windows, Android/iOS) Installation training will be provided by Motorola as defined in the Training Plan.
Deployment of PremierOne Cloud Mobile (Windows, Android/iOS) updates is a Customer responsibility.
Customer Completes Mobile Client Installation on Mobile Devices (Windows, Android/iOS) CommandCentral Aware Client Installation
Motorola will configure Aware client software on the Customer-provided Aware workstations.
Motorola Responsibilities
1. Verify remote access capability after Customer completes physical installation of workstations.
2. Configure CommandCentral Aware client application.
Customer Responsibilities
1. Perform physical installation of the CommandCentral Aware workstations. Connect to power and network. Assign IP addresses for the network.
2. Provide remote access to the CommandCentral Aware workstations.
Configuration of and successful demonstration of CommandCentral Aware client application.
Functional Validation
Motorola will execute the PremierOne Cloud and CommandCentral Functional Validation prior to Customer training and in accordance with the Functional Validation Workbook. The purpose of this exercise is to verify and document that the PremierOne Cloud service is ready for Beneficial Use.
The following severity level definitions provide the classification of anomalies that may manifest during the functional validation review.
Critical Level Severity: An incident is deemed CRITICAL if one or multiple critical functions are unavailable or severely degraded such that the customers' core business functions and capabilities are no longer delivered or capable. The resulting critical impact to the customers' business is such that focus and resources must be applied to restoration or mitigation Data has stopped showing in the application or users are no longer able to access the product due to a system-wide outage
High Level Severity: An incident is deemed HIGH if a business function is unavailable and normal customer business activit is im acted or de raded, and a workaround ma be available Exhibit A: Contract Documentation Requirements
G Motorola Solutions Statement of Work 49
May 10, 2022 Item #11 Page 426 of 604
DocuSign Envelope ID: EE0000EC-819D-469F-887C-147E3BCEAFF7
2.4.6.1 2.4.6.2
2.4.6.3 City of Carlsbad, CA
February 16, 2022
to mitigate the effects of the service impact; however overall efficiency or effectiveness is degraded. This may apply to both critical and non-critical functions.
Recoverable application crash, All data inaccessible (e.g. videos inaccessible, missing incidents).
Medium Level Severity: An incident is deemed MEDIUM if business functions are available, however, there is a deviation from the expected or agreed upon level of service or other service condition not aligned with the other defined impact levels.
Data missing; (e.g. incomplete video thumbnails, inconsistent incident population).
Critical and High-level severity issues, whether identified during PremierOne Cloud Functional Validation or during Customer Led Scenario Validation, will be retested following any corrective action taken to resolve the issue. Corrective action may consist of a configuration/provisioning change either by Motorola or the Customer, resolution of installation or environment variables such as network access or speed or remediation plan for software defect.
Numerous Medium Level severity issues may also prevent commencement of Beneficial Use. Corrective action may consist of a configuration/provisioning change either by Motorola or the Customer, resolution of installation or environment variables such as network access or speed or remediation plan for software defect. Motorola and the Customer will mutually agree to a remediation plan to address the situation whereby numerous Medium Level severity issues are considerd "blocking" issues.
Following the corrective action, the validation scripts associated with the corrected function will be retested to verify corrections. Motorola will not conduct a full retest of all scripts in the Functional Validation Workbook but such testing may be conducted by the Customer. The Functional Validation verifies the functionality of the system and is not a validation of the provisioning.
Functional validation is provided for each Product contained in the System as follows:
PremierOne Cloud CAD Functional Validation
Motorola will schedule a remote two (2) day session with the Customer to demonstrate the CAD functional validation. PremierOne Cloud CAD functional validation verifies the functionality of the CAD service and does not include the testing of other products or interfaces.
PremierOne Cloud Mobile Functional Validation
Motorola will schedule a remote one-half (1/2) half day session with the Customer to demonstrate the Mobile functionality on one (1) PremierOne Cloud Mobile device.
PremierOne Cloud Mobile functional validation verifies the functionality of the Mobile service and will be completed post completion of the PremierOne Cloud CAD functional validation.
CommandCentral Functional Validation Demonstration
Motorola will provide a functional demonstration script and will demonstrate CommandCentral Aware functionality during a one-half (1/2) day session with the Customer.
Exhibit A: Contract Documentation Requirements
50 Statement of Work Motorola Solutions G
May 10, 2022 Item #11 Page 427 of 604
DocuSign Envelope ID: EEOOOOEC-B190-469F-887C-147E3BCEAFF7 City of Carlsbad, CA
February 16, 2022
2.4.6.4 Customer Led Scenario Validation
Post completion of the Functional Validations the Customer will begin utilizing the PremierOne Cloud services and CommandCentral Aware to perform "Day in the Life" scenario validation using scenarios developed by them that have been based on their everyday operations/workflow as well as more complex unique scenarios they may encounter. The Customer will include scenarios based on Motorola responses to the Functional Requirements Matrix.
Issues that are discovered during this validation exercise will be reported to Motorola for issue resolution in accordance with the Agreement.
2.5 PREMIERONE CLOUD REPORTING
PremierOne Cloud CAD utilizes Motorola's CommandCentral Reporting to provide reporting capability. Motorola will deliver access to CommandCentral Reporting to the Customer's identified reporting administrator.
Motorola will also establish a reporting data warehouse (ROW) in the cloud to support ad- hoc reporting with PremierOne CAD data using SQL Server Reporting Services (SSRS).
The standard CAD Reports Library will be provided.
Customer-specific or Customer defined reports are not included in the scope of this project unless defined in this SOW.
Motorola Responsibilities
1. Provide access to the CommandCentral Reporting environment to the Customer reporting administrator.
2. Provide overview/instruction to Customer reporting administrator on how to access the CommandCentral Reporting environment.
3. Develop the ROW environment in the cloud.
4. Conduct SSRS Report Builder Training.
5. Provide the Standard CommandCentral Reports and the PremierOne CAD Reports library.
Customer Responsibilities
1. Identify the agency's reporting administrator and provide their Name, Email and Phone Number.
2. Setup Azure AD for use with CommandCentral Reporting.
3. Participate in SSRS Report Builder Training.
Completion Criteria -PremierOne Cloud Reports
PremierOne Cloud Standard Reports
PremierOne SSRS Reporting in the Cloud
Exhibit A: Contract Documentation Requirements
C., Motorola Solutions Statement of Work 51
May 10, 2022 Item #11 Page 428 of 604
DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7
2.6 INTERFACE AND INTEGRATION DELIVERY
City of Carlsbad, CA
February 16, 2022
The installation, configuration, and demonstration of interfaces may be an iterative series of activities depending upon access to third party systems. Interfaces will be installed and configured in accordance with the PremierOne Cloud Service Description, Project Schedule, and Interface Functional Documents (IFDs) provided to Customer prior to contract and incorporated as an Ordering Document. Integrated functionality between Motorola developed products will be completed through the software installation and provisioning activities described herein. Integration activities that have specific requirements will be completed as outlined in this SOW.
2.7 INTERFACE DEPLOYMENT
Connectivity will be established between the Motorola system and the external and/or third party systems to which the contracted software will interface. Motorola will configure the system to support each System interface. The Customer is responsible for engaging third- party vendors if and as required to facilitate connectivity and validation of the interfaces.
Motorola Responsibilities
1. Establish connectivity to external and third party systems.
2. Configure interfaces to support the functionality described in the PremierOne Cloud Subscription Service document and the IFOs.
3. Provide the Customer with the Interface Configuration Guides.
4. Provide Customer training for the PremierOne Cloud CAD provisioning of the interface as applicable.
5. Validate each interface can transmit and or receive data in accordance with the IFDs.
Customer Responsibilities
1. Act as liaison between Motorola and third party vendors or systems as required to establish interface connectivity with the Motorola system.
2. Provide personnel proficient with and authorized to make changes to the network and third party systems to support Motorola's interface installation efforts.
3. Provide network connectivity between PremierOne and the third-party systems.
4. Complete the Interface Configuration Guides in accordance with the project schedule.
5. Complete Customer defined PremierOne Cloud CAD provisioning as applicable.
Motorola Deliverables -PremierOne Interface Deployment
Interface Configuration Guides
Interface deployment/configuration complete -Interface ready for Interface Validation Demonstration
Unknown circumstances, requirements, and anomalies at the time of initial design can present difficulties in interfacing to some third party applications. These difficulties could result in a poorly performing or even a non-functional interface. At such time that Motorola is provided with information and access to systems Motorola will be able to mitigate these Exhibit A: Contract Documentation Requirements
52 Statement of Work Motorola Solutions 0
May 10, 2022 Item #11 Page 429 of 604
DocuSign Envelope ID: EE0000EC-819O-469F-887C-147E3BCEAFF7 City of Carlsbad, CA
February 16, 2022
2.7.1 difficulties. If Motorola mitigation requires additional third-party integration, application upgrades, API upgrades, and/or additional software licenses those costs will be borne by the Customer or addressed through the Change Order provision of the Agreement.
Interface Validation
The objective of Interface Validation Demonstration is to verify that the installed interfaces perform according to the Interface Functional Documents {IFDs).
Motorola is not responsible for issues arising from lack of engagement of third-party and/or Customer resources to perform work required to enable/provision and or configure an interface to a 3rd party system, or troubleshooting any issues on the Customer's third-party systems.
Interfaces that cannot be demonstrated due to connectivity issues to external systems or the unavailability of Customer's third party system will be demonstrated to the degree the PremierOne functionality can be demonstrated. If interface validation cannot be completed in accordance with the project schedule due to connectivity issues to external systems or the unavailability of Customer's third party system, a change order may be required to perform such validation when the issue is resolved.
Motorola Responsibilities
1. Conduct a demonstration of each i~terface, with the Customer, to validate each function per the IFD.
2. Develop a remediation plan for features that do not perform in accordance with the IFD.
3. Upon completion, provide the Customer with a Project Milestone Document, to be signed and returned to Motorola. Exceptions will be noted in the Project Milestone Document.
4. Schedule follow-up validation to demonstrate resolution of any Critical and High-level severity issues as defined in this SOW.
Customer Responsibilities
1 . Provide access to a resource with access to the interfacing system to validate functionality.
2. Witness the execution of the validation and acknowledge successful completion.
3. Upon completion, sign and return the Project Milestone Document within ten (10) business days
4. Participate in the documentation of items that do not perform in accordance with the IFD and work with Motorola to develop remediation action(s).
Interface Validation Demonstration completed and Customer acknowledgement of completion Exhibit A: Contract Documentation Requirements
CD Motorola Solutions Statement of Work 53
May 10, 2022 Item #11 Page 430 of 604
DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7
2.8 2.8.1
2.8.2 City of Carlsbad, CA
February 16, 2022
PREMIERONE CLOUD AND COMMANDCENTRAL TRAINING
AND CONSULTATIVE SERVICES
Training
Training is conducted based on the quantities and terms that are specified in the Customer Training Plan. Training is made available via in-person training (PremierOne) and the Learning exPerience Portal (LXP) (PremierOne and CommandCentral). The LXP is accessed via Internet browser. Motorola will set up an instance of the LXP that provides autonomy to the agency utilizing LXP. This subscription service provides you with continual access to our library of on-line learning content and allows your users the benefit of learning at times convenient to them. Content is added and updated on a regular basis to keep information current. All Motorola tasks are completed remotely and enable the Customer to engage in training when convenient to the user.
LXP Administrators are able to add/modify users, run reports, and add/modify groups.
Motorola Responsibilities
1. Initial set up and addition of administrators.
2. Provide instruction to Customer LXP Administrators on:
A. Adding and maintaining users and groups.
B. Assigning courses and Learning Paths.
C. Running reports.
3. Delivery of in-person training courses as described in the Training Plan.
4. Conduct up to eight (8) hours of remote consultation following PremierOne CAD Train the Trainer training to develop end-user training curriculum.
Customer Responsibilities
1. Provide Motorola with names (first and last) and emails of Customer LXP administrators.
2. Provide access to learningservices.motorolasolutions.com.
3. Complete LXP Administrator training.
4. Advise users of the availability of the LXP.
5. Add/modify users, run reports, and add/modify groups.
6. Ensure attendance of personnel for in-person and virtual training courses in accordance with the project schedule and the number of students per course defined in the Training Plan.
CommandCentral Aware Professional Consulting .Services
Professional Consulting Services provide the Customer an opportunity to utilize Motorola subject matter experts as needed to address operational concerns: impromptu training, process re-engineering, or one on one personalized support.
Exhibit A: Contract Documentation Requirements
54 Statement of Work Motorola Solutions CD
May 10, 2022 Item #11 Page 431 of 604
DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7 City of Carlsbad, CA
February 16, 2022
2.8.3 Motorola Responsibilities
1. Conduct a discovery teleconference with Customer's PM and/or team to understand the Customer needs prior to scheduling on-site service.
2. Provide Customer with a summary of the needs discussed during the teleconference that serve as the focus for the on-site service delivery.
3. Upon agreement of the focus of on-site service, schedule a mutually agreeable date for delivery of on-site service.
4. Provide five days total spread across two trips of on-site service Monday through Friday, 8:00 am to 5:00 pm local time.
5. Provide Customer with a summary report of the activities completed as part of on-site service delivery.
Customer Responsibilities
1. Participate in the discovery teleconference and agree to objectives.
2. Schedule a mutually agreeable date for delivery of on-site service.
3. Coordinate availability of people or resources required for Motorola to fulfill the focus of on-site service.
Motorola Deliverables -Training and Consultative Services Virtual Training Courses
Access to and instruction for LXP
CommandCentral Aware Consultative Services
Completion Criteria -Training and Consultative Services Conclusion of and Customer acknowledgement of Motorola provided LXP Administrator instruction, in-person and virtual courses, and CommandCentral consultative services, per the Training Plan.
CommandCentral Investigate Professional Consulting Services Motorola Consulting Services provides the Customer an opportunity to use Motorola subject matter experts to address operational concerns or implementation of strategic initiatives.
The full scope of consultative services will be determined during the discovery session between Motorola and the Customer. Certain consultative services are required as part of this offer while other services, outlined in the following solution specific tables, are selected and customized to meet the needs of the Customer.
Motorola Responsibilities
1. Conduct disco'very teleconference with the Customer to understand goals and objectives for the product as well as strategic initiatives.
2. Conduct a three (3) day on-site review of day-to-day operational use of Investigate to discover how the functional areas are utilizing the solution. Includes on-the-job training for efficient use and recommendations for optimizing. A briefing will be conducted at the end of the day to provide an update on information exchanged, activities planned and any additional actions needed.
Exhibit A: Contract Documentation Requirements
CD Motorola Solutions Statement of Work 55
May 10, 2022 Item #11 Page 432 of 604
DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7 City of Carlsbacl, CA
February 16, 2022
3. Provide Customer with an After-Action Report of the activities completed and next-step recommendations.
4. Conduct an after visit teleconference with Customer's point of contact to outline the Customer's priorities according to the After-Action Report.
5. Coordinate with Customer the work that needs to be completed and designate the appropriate owner of the activity.
Customer Responsibilities
1. Participate in the discovery teleconference and agree to objectives.
2. Schedule mutually agreeable dates for delivery of on-site service.
3. Coordinate availability of people or resources required for Motorola to fulfill the focus of on-site service.
4. Confirm Customer end-users have completed required training prior to on-site service.
5. Participate in the after visit teleconference and collaborate on priorities and work items to be delivered.
Delivery of After-Action Report and completion of teleconference post the on-site visit.
2.9 PREMIERONE CLOUD AND COMMANDCENTRAL GO LIVE
2.9.1 The transition to live operations to Motorola's PremierOne Cloud system is a team approach. Motorola will assist the Customer in the transition of live operations from the Customer's legacy solution to the PremierOne System. Motorola will work with the Customer to confirm the PremierOne System Go Live date and time.
The services included in this Agreement are based on a single joint go live event of PremierOne Cloud CAD, Mobile. The separation of the go live events may result in a Change Order to add additional services. If separated, the below sections apply to each go live event.
PremierOne Cloud Go Live Planning
Motorola will work with the Customer to develop a detailed Cutover Plan. This plan includes the following information:
• Motorola and Customer resources and staffing required • Pre-cutover tasks/activities that need to be performed leading up to the go live • Readiness review meetings
• Contingency/roll-back plans
• Go live tasks and responsibilities during and after the live cut • Post live cut support resources and schedules
• Issue reporting process
Exhibit A: Contract Documentation Requirements
56 Statement of Work Motorola Solutions fl
May 10, 2022 Item #11 Page 433 of 604
OocuSign Envelope ID: EE0000EC-B 19O-469F-887C-14 7E3BCEAFF7 City of Carlsbad, CA
February 16, 2022
2.9.2 2.9.3
2.9.4 • Escalation process
Motorola Responsibilities:
1. Facilitate meetings with Customer staff to develop and document the Cutover Plan.
Customer Responsibilities:
1. Coordinate the participation of Customer technical and operational staff in cutover planning and development and documentation of the Cutover Plan.
Motorola Support Engagement
As part of go live planning, the Motorola Project Manager will complete a Customer Support Plan (included in Section 10 of these Ordering Documents) that includes Customer contact information and information required for remote access to the system. Motorola will schedule a Support Engagement meeting between the Project Managers, the Customer Support Advocate ("CSA"), the Focal Support Technician and the Customer's project team representatives. The CSA will review the Customer Support Plan with the Customer, including the process for obtaining support and the contact information.
Motorola Responsibilities:·
1. Create Customer Solution Support Plan
2. Facilitate Support Engagement Meeting
Customer Responsibilities:
1. Coordinate the participation of Customer technical and operational staff in the Support Engagement Meeting
CommandCentral Aware Production Use
Following the completion of the functional demonstration of CommandCentral Aware, the Customer may commence using CommandCentral Solution for all purposes including production use.
CommandCentral Investigate Production Use
Following the completion of the activation of CommandCentral Investigate, it is deemed available for all purposes including production use.
Exhibit A: Contract Documentation Requirements
G Motorola Solutions Statement of Work 57
May 10, 2022 Item #11 Page 434 of 604
DocuSign Envelope ID: EE0000EC-819D-469F-887C-147E3BCEAFF7
2.9.5 2.10
PremierOne Cloud Go Live Event
City of Carlsbad, CA
February 16, 2022
The transition to production use of the PremierOne solution will be conducted according to the Cutover Plan.
The cutover event represents the System Completion milestone and the transition to the Motorola Solutions Support organization in accordance with the Cutover Plan.
Motorola will provide Go Live support as listed in the cutover Plan. A summary of the applicable Go Live support services are described below:
• CAD Go Live Support includes one (1) CAD Application Specialist per twelve (12) hour shift to provide 24-hour support at one (1) location for up to three (3) days. A third CAD Application Specialist will be available for up to thirty-six (36) hours over three (3) days to be deployed as mutually agreed upon.
• CAD Post-Go Live Support (remote) will be available for up to thirty (30) days following Go Live. During this period, the PM and Application Specialist will remain engaged to provide updates on issues that occur prior to and during Go Live. The Customer Support organization will be the primary point of contact to report issues that arise after Go Live.
Motorola Responsibilities:
1. Work with Customer to schedule the date and time for the go live event 2 . Execute the Cutover Plan
3. Provide on-site resources to support dispatch and mobile operations and address questions.
4. Provide remote post-go live support for up to thirty (30) days.
Customer Responsibilities:
1. Schedule and coordinate end user participation in the live operations cutover
2. Perform and support the cutover activities defined in the Cutover Plan
3. Provide technical and operational support for the supervision and monitoring of CAD and Mobile end users 24/7 beyond Motorola onsite support
4. Inform Customer staff about the Customer Solution Support Plan and the process to contact Customer Support.
Completion Criteria -PremierOne Cloud Go Live Event
Completion of Go Live Activities
Live PremierOne Cloud system
PROJECT CLOSURE
Project Closure involves the steps to close the project and transition the PremierOne System from the delivery team to Customer Support.
Exhibit A: Contract Documentation Requirements
58 Statement of Work Motorola Solutions C.,
May 10, 2022 Item #11 Page 435 of 604
DocuSign Envelope ID: EEOOOOEC-B19D-469F-887C-147E3BCEAFF7 City of Carlsbad, CA
February 16, 2022
2.10.1 Transition to Support
The system will transition to the support phase of the Agreement per the terms and conditions of the applicable Agreements and Customer Support Plan.
2.11 OPTIONS AVAILABLE AT AN ADDITIONAL PRICE
The following solution components are presented for the City's consideration. While not required to support the PremierOne Solution, each of the following separately priced options enhance the solution by adding additional capabilities.
2.11.1 Option 1 • Motorola In-Car Cameras (Either 4RE or M500) The in-car cameras will be configured and installed in vehicles.
Motorola Responsibilities
1. Create Configuration USB.
2. Configure Each DVR as installs are completed.
3. Deliver training.
4. Perform testing in accordance with the test plan.
5. Provide thirty (30) days of remote support following production use of the in-car cameras.
Customer Responsibilities
1. Ensure availability of vehicles in accordance with agreed-upon schedule. 2 . Provide cradlepoint routers and ethernet connections in each vehicle. 3 . Install cameras in vehicles.
4. Evaluate the performance of the complete in-car camera system.
5. Acknowledge successful completion of the in-car camera implementation.
Completion Criteria -Motorola V300 Body-Worn Cameras
This task will be complete when Motorola has configured the 4RE or M500 in-car cameras and Customer acknoweldges successful completion of testing.
2.11.2 CommandCentral Community
Motorola Solutions enables the CommandCentral Community service during the order process. Deployment services are not required. Training will be made available via the LXP as described herein. Following the completion of the activation of CommandCentral components described below, implementation activities for CommandCentral Community are complete.
Exhibit A: Contract Documentation Requirements
CD Motorola Solutions Statement of Work 59
May 10, 2022 Item #11 Page 436 of 604
DocuSign Envelope ID: EEOOOOEC-B19D-469F-887C-147E3BCEAFF7 Motorola Solutions Responsibilities
City of Carlsbad, CA
February 16, 2022
1. Use the CommandCentral Admin tool to enable Customer access to CommandCentral Community. This activity is completed during the order process.
2. Connect to PremierOne Cloud CAD.
Customer Responsibilities
1. Provision policies and procedures, tags, retention periods, and user permissions.
2. Configure CommandCentral Community settings (location of agency pin, shape of agency, keywords, set up agency page, URL, which forms to deploy).
3. Provide access to Motorola Solutions' team to connect incident data ingest.
2.11.2.1 Additional Forms
Additional Forms for CommandCentral Community are provided by SeamlessDocs.
SeamlessDocs will also set up the Customer with URL information and login credentials.
Motorola Solutions Responsibilities
1. Send correct order information to SeamlessDocs.
Customer Responsibilities
1. Work with SeamlessDocs to accomplish onboarding tasks.
2. Link SeamlessDocs portal in Community Admin page.
SeamlessDocs Responsibilities
1. Onboard Customer according to normal protocols.
CommandCentral Community subscription enabled and successfully demonstrated to Customer.
2.11.3 Option 2 -Motorola V300 Body Worn Cameras
The V300 body-worn camera is the device that the Customer will use to capture video and photo content in the field. Prior to first use, each V300 camera must be configured. This process is called "Checkout" and involves connecting each camera to evidence management system to assign a configuration and officer name. This process can be done each time the officer needs to be assigned a camera, or can be done in scenarios where officers are assigned a body-worn camera to use on a more permanent basis. The transfer stations are used to charge, store and connect the body-worn camera to the backend system. Training for body worn cameras will be conducted onsite.
Motorola Responsibilities
1. Take the V300 device from "out of the box" through complete set-up.
Exhibit A: Contract Documentation Requirements
60 Statement of Work Motorola Solutions t/.l
May 10, 2022 Item #11 Page 437 of 604
DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7 City of Carlsbad, CA
February 16, 2022
2.12 2. Provision the V300 to the evidence management system.
3. Configure V300 cameras.
4. Install transfer stations.
5. Test function of the V300 cameras.
Customer Responsibilities
1 . Provide a network connection (Ethernet) to the upload seNer or directly to the transfer station for network connectivity.
2. Provide the desired network configuration so the equipment can be delivered configured, ready to deploy.
3. Choose and implement the proper wearability option to mount the V300 to their officers' uniform.
Completion Criteria -Motorola V300 Body-Worn Cameras
Work is considered complete upon V300 set-up and provisioning being finalized and completion and Customer acknowledgement of functional testing.
APPENDIX A-PREMIERONE CLOUD ATTACHMENT
The following sections describe standard capabilities and integrations that enhance your PremierOne Cloud solution. These aspects of the solution are included as part of the PremierOne Cloud subscription, providing your users with common seNices, reporting, and mapping capabilities.
2.12.1 Common Services
Common SeNices provides system administrators the flexibility to manage internal seNices throughout the PremierOne Cloud platform from a single point. Each system or seNice has common seNices, including GIS, System Security, Reporting, and the system tools for provisioning.
2.12.2 CommandCentral Reporting for PremierOne Cloud
Motorola Solutions will provide reporting insights through a curated library of ready-to-use reports. CommandCentral Reporting leverages secure, modern, scalable, and managed infrastructure that isolates reporting workloads from your PremierOne Cloud solution, ensuring a higher performance.
2.12.3 Geographic Information System (GIS) Integration
The PremierOne Cloud solution integrates with agency-hosted GIS data sets from an Esri ArcGIS SeNer (geospatial data is uploaded to the system through tools implemented within Esri ArcGIS). Geospatial information within these data sets contributes to display, location validation, and unit recommendation in PremierOne Cloud CAD. Esri's geospatial engine automatically invokes spatial queries to inform users of nearby items, refine geographic Exhibit A: Contract Documentation Requirements
G Motorola Solutions Statement of Worl< 61
May 10, 2022 Item #11 Page 438 of 604
DocuSign Envelope ID: EE0000EC-819D-469F-887C-147E3BCEAFF7 City of Carlsbad, CA
February 16, 2022
boundaries (by area, beat, sector, precinct, zone, or quadrant), and focus attention on specific locations to better inform response.
• The system's tools, made available for Arc Tool box, provide the ability to load local data manually or through an automated model.
• Address validation data is maintained in redundant Microsoft SQL Server geodatabases that store locations and boundaries both spatially and in optimized search tables. Esri ArcGIS provides routing and ET A calculations using the Network Analyst extension.
Client maps are displayed using Esri ArcGIS Engine and ArcGIS run-time SOK technologies.
• The system's Response Boundary Data Import Tool imports and aggregates boundaries in multiple layers into a single spatial table within the geodatabase for support of multi- agency/multi-jurisdictional scenarios. GIS data is a required key component of a system deployment. GIS provides the mechanism for location validation and recommendation for response.
• Solution conformant and geographically accurate GIS data is required for the proper operation of the system. Your agency is responsible for providing complete and accurate GIS data that conforms to the PremierOne GIS Data Requirements. Each agency being added to the system must have their geographic coverage included in the single geodatabase imported into CAD.
• The use of remote and/or Esri Online services is not supported. Motorola Solutions is not responsible for map availability or any degradation of client performance caused by the use of third party hosted internet map services; as these services are outside the domain of the system infrastructure and are not managed by Motorola Solutions.
2.12.4 PremierOne Cloud File Build
The following table lists the codefile items that are part of the PremierOne Cloud solution.
Codefile Item Global Code NENA/APCO Standard Customer
Table Provided : ' -:,·.·-~,-,_--____ ---:--r-· ·:·----;--•c·,-, .. ' .-.. -·-.--~ ,_.-.-:--:z.:t--;•: -'--_, ---,~.~--.. J •List and Statute Management · · :.· , ·,,,.-.. --· ; ,-.. :.,_~~""'·· ·\r·c:i~ -·:... ti! ~-~ __:~~1.~C:.~i.~-~----~~~j~-==--~-~~ ◄:_;'..h_ Article Type X NCIC
City X NCIC
Country List X NCIC
Eye Color Description X NCIC
Gender Description X NCIC
Gun Make X NCIC
Hair Color Description X NCIC
Person Build X NCIC
Person Race Description X NCIC
Person Suffix X NCIC
License Plate Type X NCIC
Skin Tone X NCIC
State List X NCIC
Exhibit A: Contract Documentation Requirements
62 Statement of Work Motorola Solutions CD
May 10, 2022 Item #11 Page 439 of 604
DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7 City of Carlsbad, CA
February 16, 2022
Vehicle Color
Vehicle Make
Vehicle Model
Vehicle Style
Vehicle Type
Incident Types
Modifying Circumstances
Incident Status -Common
Incident Source Call Origination
Common Disposition Code
Person Role
Agency Role
Incident Response Factors
Coverage Groups
Premise Hazard Types
Premise Hazard Records
Area/BeaUSectors
Location
Station Names
Resource Attribute (Capability/Skill )
Resource Type
Exhibit A: Contract Documentation Requirements
G Motorola Solutions
X NCIC
X NCIC
X NCIC
X NCIC
X
NENA
APCO
NENA
NENA
NENA
Standard
Standard
APCO
X
Standard
X
X
X
X
NENA
NENA
Statement of Work 63
May 10, 2022 Item #11 Page 440 of 604
DocuSign Envelope ID: EE000OEC-B19D-469F-887C-147E3BCEAFF7 Primary Unit Status -Common
Secondary Unit Status -Common
Unit ID -Optional
Unit Pre-Assignments
Exhibit A: Contract Documentation Requirements
64 Statement of Work
Standard
Standard
City of Carlsbad, CA
February 16, 2022
X
X
Motorola Solutions G
May 10, 2022 Item #11 Page 441 of 604
DocuSign Envelope ID: EE000OEC-B19D-469F-887C-147E3BCEAFF7 SECTION 3
COST SUMMARY
Please reference Motorola's Cost Proposal on the following pages.
3.1 PRICING SUMMARY
City of Carlsbad, CA
February 16, 2022
Description Price ($) After
Total Not To Exceed One Time Cost Based on SOW**** (Excluding Options) (50 CAD Named Users, 175 Mobile Named Users, 175 Aware Named Users, 200 LXP Users)
Total Annual Recurring Costs ***(Excluding Options) Years 2-6 Options Available for Purchase Discount*
(Including Years 1-6) (Legacy Data Query and Radio PTT IFs and CommandCentral Investigate Plus included in One Time Cost)
TOTAL SYSTEM
CAD/Mobile/Aware/Options (Years 1-6)
Discount
$1,065,179
$791,441
$0
$1,856,620
VaaS Options Price ($)
#1 Optional Purchase -Body-Worn Camera -VaaS (Years 1-5) #2 Optional Purchase -In-Car Video (60 Units) & Evidence Management-VaaS (Years 1-5)
#3 Optional Purchase -In-Car Video (94 Units) & Evidence Management -VaaS (Years 1-5)
#4 Optional Purchase Interface -Auto correlation with In-Car Video and RMS with purchase of Option 1, 2, or 3
ONE-TIME DISCOUNT** Applied to Option #1 , #2 and/or Option #3 with the purchase of CAD/Mobile/Aware
$423,079
$536,400
$840,360
$12,000
(-$100,000)
The following Options Available for Purchase have been included in the "all in" offer at no additional cost.
• Legacy Query Interface
• PremierOne CAD Radio PTT Interface
• CommandCentral Investigate Plus
**With the purchase of PremierOne Cloud CAD, Mobile, CommandCentral Aware and Body Worn Cameras or In-Car Video Motorola has provided an additional discount for Option #1 and/or Option #2.
***Includes three (3) Summit User Group Registrations Annually ****The Total Not to Exceed price is for an 18-month delivery schedule. For each month project is finished under 18 months, Motorola will credit $13,334 per month.
Exhibit A: Contract Documentation Requirements
G Motorola Solutions Cost Summary 65
May 10, 2022 Item #11 Page 442 of 604
DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7 City of Carlsbad, CA
February 16, 2022
• #1 Option -Motorola V300 Body Worn Cameras (quantity 130 devices) -Software, Hardware & Refresh:
• Video-as-a-Service includes cloud-based evidence management system, with unlimited storage and unlimited cloud sharing.
-User licenses on a per-device basis.
-CommandCentral Community (evidence capture, records, and CommandCentral Community capabilities included).
Body-worn camera (choice of mount)
-Third year technology (Hardware) refresh.
-Subscription, Support & Warranty:
• 5-year agreement (billed Quarterly or Annually)
• Advanced hardware replacement service & 24/7 support
• No-Fault hardware warranty
-USB Docking Station Video-as-a-Service Package (quantity of 10) -Transfer Station (8 Bay) Video-as-a-Service Package (quantity of 12) -V300 Additional Batteries (quantity of 130)
-Managed Software Installation Service; On-Site Assist Install, Training, Configuration, Project Management, Consultation
• #2 Option -In-Car video and evidence management software (quantity 60) -Video-as-a-Service includes the cloud-based evidence management system -CommandCentral Community (evidence capture, records, and CommandCentral Community capabilities included).
-Unlimited users, Unlimited storage & Unlimited cloud sharing -CarDetector Mobil_e LPR w/ Vigilant LEARN (PlateSearch) -In-Car Video System (Choice of forward camera)
• Includes 200GB DVR, Control panel & Infrared cabin camera • HiFi wireless microphone kit, MiKroTik WiFi Kit & Smart Power Switch • Managed Software Installation Service; On-Site Assist Install, Training, Configuration, Project Management, Consultation
• #3 Option -In-Car video and evidence management software (quantity 94) -Video-as-a-Service includes the cloud-based evidence management system -CommandCentral Community (evidence capture, records, and CommandCentral Community capabilities included).
-Unlimited users, Unlimited storage & Unlimited cloud sharing -CarDetector Mobile LPR w/ Vigilant LEARN (PlateSearch} -In-Car Video System (Choice of forward camera)
• Includes 200GB DVR, Control panel & Infrared cabin camera • HiFi wireless microphone kit, MiKroTik WiFi Kit & Smart Power Switch -Upload Server On-Premise (1) -Store and Forward Server for Fast Video Offload.
Use with in-car upload via Access Point or Body Worn Camera Transfer Stations, On-premise deployment, 1 U rack mount, 8TB of storage, 16 GB RAM, 2x1 0G network cards, ·Intel Zeon processor, 5 year Warranty
-MikroTik Configured Wireless Kit 802.11 n, Drill Mount (94) -Radio, Antenna, PoE, 2-10' Ethernet Cables, Drill Mount
-MikroTik Configured Wireless Access Point (5)
-Managed Software Installation Service; Onsite Assist install, Training, Managed Software Configuration, Project Management, Consultation Exhibit A: Contract Documentation Requirements
66 Cost Summary Motorola Solutions f.'
May 10, 2022 Item #11 Page 443 of 604
DocuSign Envelope ID: EE0000EC-B19O-469F-887C-147E3BCEAFF7 City of Carlsbad, CA
February 16, 2022
SECTION4
PAYMENT SCHEDULE
A. 10% Upon Approval of Project Plan
B. 10% Upon Completion of Software Installation
C. 20% Upon Completion of Functional Testing
D. 20% Upon Completion of Training
E. 20% Upon Completion of Go-Live
F. 20% Upon Software System Completion
Exhibit A: Contract Documentation Requirements
Motorola Solutions Payment Schedule 67
May 10, 2022 Item #11 Page 444 of 604
DocuSign Envelope ID: EEOOOOEC-819D-469F-887C-147E3BCEAFF7 SECTION 5
City of Carlsbad, CA
February 16, 2022
PROJECT SCHEDULE AND
PERSONNEL
5.1 PROJECT SCHEDULE
We are providing a representative project schedule on the following pages that reflects the preliminary project scope and duration. As part of contract negotiations or project kickoff activities, the Motorola Project Manager will collaborate with the City to develop a mutually agreeable project schedule (which may decrease overall duration) that will include the final contracted scope of work and project resources (including subcontractors).
Exhibit A: Contract Documentation Requirements
G Motorola Solutions Project Schedule and Personnel 68
May 10, 2022 Item #11 Page 445 of 604
DocuS;gn Envelope ID: EEOOOOEC-B19D-469F-887C-147E3BCEAm Carlsbad PremierOtie CAO and Awar'e • Project Schedule_031022 emie,-One Cloud CAD Cloud Deployment
Project Initiation and Planning
Contract ~):ecution
OOJ Approval Process.
Project ~~J~ment
Project Planning Se.ssion
Project Handoti with Sales
PrOJfCt -Planning Se:ssion
Prem.1e,qnl! Clou~ ~O_BP~u!"'.'_'=.(!~turMd
PremierOne CJoud GIS Survey Returned
CJIS Requirements Defined ·
Pr~ject Schedule 8aselined
ProJect Management Plans Completed
PremierOne aoud and CommandCentrat Kickoff Meeting
Kld:Off Meetin&
--GIS Planning S~si~n
-GIS Pl~nning Session
Cu~omer Piovid@S GIS Draft Data
Interface Planning S-ession
lnterf"ice Planning SesslOO -
Customer Provi nal CoMuk.ttive Servitel S days
Investigate Profes.slonat Consultatlve Servk.a S days
~mierOne Cloud CAO/Mobile ServlCe Oel~!_ry ~ ~a~
CA_!?an~~-bile lnstaJlatlon __ _ _ ~
Customer IP Address Provlded {lAN/WAN, Subnet mask., Gateways) 1 day M(crosoft Active Olrecto,y A:r.ure Setup
Mfcrosoft Active Clli"ectOfY Azure Ms1 Users Reg[stered Network Ports -Open (If Direct to lnterNet Configuration) Azure Public Edie Access
CAO User Information Provided (Name/Email)
PremlerOne CAO Eflvironment Sett.Jp (MSI Access Onfy)
Prem!erOne Mobile Environment Sl!tup (Ms1 Access Onty)
l day
1 day
1 day
I day
0 days
l l
'Thu 6/2/22 Thu6/2/U
'-• wod6/15/22 Wed_ 6/lS/]J
ThuffiW2 \\red 8/3/22
!hu8M[l2 Thu 8/11/22
Mon 10/31/22
Fri 6i3/22
Mon JcO]E/p.
Tue 6/7/22
Wed 6/8/22 Tue 6/14/22
Wed 6/15/22 Frl6/17/22
F<lll/4/22 Wed 11/23/22
t<!_Jl/4/2,2 Tue 11/8/22 _
Wed 11/9/22 Tue 11/22/22
Wed 11/23fl2 W~d 11i23/22
•Wed 11/23/22 Wed 11/2}/22
Tue6/28/22 Wed 11/30/22
Tue 6/28/22 Tue 6/28/22
Tue 7/5/22 Tue 7/5/22
Thu 11/24/22 Wed 11/30/22
Thu 11/24/22 Wed 11/30/22
l_~!_S/10/22 W•d S}l;/23
'Tue S/3lf12 Fri_6/l/2_2 ___
Tue 5/31/22 Tue 5/31/22
Tue 5/31/22
Tue-S/3-1/22
Tue 5/31/22
Tue 5/31/22-
'Tue 5/31/22 TueS/31/22
Tue S/31/22 Tue 5/31/22
Tue 5/31/22 Tue 5/31/22
Tue S/31/22 Tue 5/31/22
Wed6/1/22 Wed 6/1/22
Thu 6/2/22 Thu 6/2/22
Fri 6/l/}-2 ___ Fri 6/3122 _
Wed 6/8/22 Tue 1/10/23 w-;;i•fihi Wed 11/2/22
Wed 6/8/22 Thu 6/9/22
Fri 10/28/22 Fd 10/28/22
Mon 10/31/22 Mon 10/31/22
Tue 11/1/22 W~d l!}J,{J],_
Tue 1)/3_9/23_ _ J~!(l/2~
Tue 11/19/22 Tuo 11/29/22
Wedll/30/:,Z
Tu.S/10/22
Fri6/1o;i2
TueS/1iif22
Tue 5/10/22
Fri 6/24/22
Fri6/24/22
Fri 7/8/22
Tue-77i9/22
Tue 1/10/23
M-on9/19/22
Mon 6/13/22
Tue 5/10/22
Tue S/10/22
Mon 9/19/22
Mon 6/27/22
_ ¥9'!.?/11/22
Tue 7/19/22
May 10, 2022 Item #11 Page 446 of 604
DocuSlgn Envelope 10: EEOOO0EC-B190--469F·887C-147EJBCE,',FF7 Carlsbad Pr@f"r'lierOM CAO and Aware • Project Sch~ule_031022 D ask Name Dlrotlon "" F'.-.ish
GIS Draft Geobatabase load 1 day Wed 7 /20/22 Wed 7/2.0/22 GIS Import Training 3 days Tue 8/2/22 Thu 8/4/22
Grs CheckPoint Meeting #3 -Customer GIS Load Review 1 day Fri 8/12/22 Fd 8/12/22 GIS Checi ning 2days Frffolis/22 Mon 10/31/22
MSI Moblle Provisioning $(!sst0n #1 (2 Hr) lday Fd 10/28i22 Fri 10/28/22 MSI Mobile Ptovisioning Session #2 (2 Hr) lday Mon 10/31/22 Mon 10/31/22 MSI M_obile Provisioning Sessk>n #3 (2 Hr) ldav FrlJ,D/18/22 M 10/28/22 MSI MobUe Provisioning 5essM>n #4 (2 Hr) l~~V Mon 10/3!/22 Mon 10/31/22 CAO and Mobile Functional Validation Review 29days Fri 10/28/22 Wedl_2/7_fl2 CAO Functional Validation Review 29 davs Fri 10/28/22 Wed 12/7/22 Provide Funetio~al va}ida_tion Scripts Odays Fri 10/28/22 Fri 10/28/22 fof!l~!te F_unctional Validation ~ ~!YS FrlJ!/'.'.(22 '!:!_e.?:!f8/2_2 __ Custome.--led SceniilriO Validation 20days W<d 11/9/22 Tue 12/6/22 FunctlOnal-Valid"itionfxceptions Resolved 20days Wed 11/9/22 Tue 12/6/22 ~mp_l.e.tf? Fun.~to0.1I Vall_dation f~r ExceP.tions 1 da.y Wed 12{1/2l Wed 12/7/22 CAO Go Uve Reacfy odavs Wed 12/7/22 Wed 12/7/22
Mobile (Windows, Android/IDS) Functional Validation Revlew 20 diy5 Mon 10/31/22 Mon 11/28/22 ~~~.E_~Fu_nctional VilKfation Scripts Q~~ys M_2,n1om/22 !'On l_0fil!32 Comptete Functional Validation 3 day.s Wed 11/9/22 FriJ.1/_!}~~ Functional Validation Exceptions R~olved lOdays Mon 11/14/22 Fri 11/25/22 Cotnplete Fur.ctional Validation for Exceptions 1 day_ Mon 11)28/22 Mon 11/2.8/22 -~-~ob~~~Live Ready O__!I!~-· • M~1/2Y32 M~n llf~.l-
CA~and Mobil~/HH P!~_v.!!!_~ning Workshop ~14 days Wed7/6/22 Mon 12/12/22 CAO LMS Provisioning Workshop freReq Courses Completed 3 days Wed7/6/22 Fri 7/8/].2- CAD/MobHe/HH Provisioning Workshop Sessions Complete 3 days Thu 12/8/22 Mon 11./12/22 _CAD C~O!n,_er ProvisionJ_ng Owner Transfer Q.<f!ys MQn 12/12{22 Mon 12/12/22 ~~-~Orting ~<lay Tue12flH 22 Tuel ~£13/E Motorola Provides Access to CC Rce,orti;.g ldav Tue_l2/l3m._ _ }ue 12/13/p,.
Motorola Provides Access to ROW In the Cloud ~d~y. __ Tue 12/13/22 Tue 12/13/22 CAD lnt(!t'faces 2)]d.•ys _ Tue s7ioh2 Wcd4/S/23
_ ~ ln~~ce • State Que"'{ (NCIC/NCIC) ~11.fil'Y' Tu• S/J0/22 Mon 9/12/22 _ Define State CenificatlOn Requirements/Process/ Provide 4Sdays Tue S/10/22 Mon 7/11/22 Documentation
Review lnterfuce Functlol'\al Description (tFO) wlth Customer 1 day Tue 7/ll/22 Tue 7/12/22 Interlace Configuration Document l day Wed 7/20/22 Wed 7/20/22 132 State TCP Protocol Connection to Pl CAO provide<:! (IP Address/Port) l day Tue 7/26/22 Tue 7/26/22 B3 Erlte"r "User, ORl's, Device tdentlflers (Mnemonlc:s}into Pl 1 day W~7/27/22 Wed 7/27/22 CAD/C(!mmsys ,,., CAD Provisioning with Customer -command Line-User l day Thu 7/28/22 Thu 7/28/22 Access/Permissions-Incident (Person/Vehicle) Trigger-Query Response Formatting • Workstations ~tructured Response Services •Hot Hit:s Mobile Provisioning 1 day Frl 7/29/22 Fri 7/29/22
Interface Functional VaUdation CAO 1 day Fri 7/29/22 Fri 7/29/22 al Valtdation ~obikl l day Mon 8/1/22 Mon 8/1/22
30 ~~-T,;e 8/2/22 ____ Mon 9/12/22
eady • State Query odays Mon9/12/22 Mon 9/12/22
1 ANI/ AU, TDD 11~ days Tue 5/31/22 Monio[n/i2
NO!, R~~rn~ (!_! R~ulr~d) 1 dav Tue 5/31/22 'Tue 5/31/2_2 Review Interface Functional Description (IFO) with Customer ldav Wed 6/l/i2 Wed6/1/22 Lantronlx/FortlGate/flrewall Provided lday Tue6/2lf22. Tue 6/21/22 Lantronhc/FortiGatt/Firewall Installed lday Tue 6/21/22 Tue 6/21/22 Interface Configuration Document Sdays Fri 10/14/22 Ttw 10/20/22 FSA Mapping Sdai,is Fri 10/21/22 Thu 10/27 /22
Pl CAO Provisioning -Phone Position/CAD Mapping 1 d"' Fri 10/28/22 Fri 10/28/22 ··-Interface Ful'K'tlonal Validation ; day Mon 10/31/22 Mon 10/31/22 Interface Go live Ready• NG911,TOD Odays Mon 10/31)22 Mon_ 10/31/22 CAD Interface· Records CFS Feeds (NetRMS, Spldr Tedi, Axon I 125 days Tue S/10/22 Mon 10/31/22 . NOA RetWned (If Required) tOda~ rue sfiol2_2 __ Mo~ S/lV22 Review Interface Functlonal Descriptions (IFOs) with Customer 3 days Thu 6/2/22 Mon 6/6/22 Interlace Configun1tion Document 3 doys Fri6/l7/2.2 Tue 6/21/22 Interface Development 30 days Wed6/29/22 Tue 8/9/22
Interlace Functional Validation 3 days Wed8/l7/22 fri 8/19/22 156 Interlace GO Live Aeady • NctRMS, Spidr Tech, Axon o days Mon 10/31/22 Monl0/31/22 Page2
May 10, 2022 Item #11 Page 447 of 604
DocuSign Envelope ID: EEOOOOEC·B190-469F·887C.1◄7E3BCEAFF7 Car1~ Premfe,o.,e CAD and Awa,e -ProjKt Sc:hedule_0310:c?2 IS7 CAO Interface -lncldent Creation One-Way Inbound (DORS, Vigilant) NOA Rt:turned (lf A:equired)
Review rnterfac~ functional Descriptions (IFOsl with Customer 107 days
10 days
3 days
lntemice Configuration Oocument 3 days
l'!!erf-a~ Oevel~f!!-~nt -·60 days
Interface Functional Valldatfon 3 days
lnterfaO'.! Go Live Ready -DORS, Vigilant O d.iivs
CAD Interface -Qu;rv l~terfaCes =taserfiche, Vigilant LPR, Legacy Data 112 days Query, Oossroad5 Accident, Crossroads Citation, OORS, QueTcl NOA Returned (If Required)
Review Interface Funetlonal Descriptions (IFOs) with Customer rnterface Cot1~,a:uration Document
Customer Enterprl.5e Network Connections to CAD
CAO Provisionine with ~om·er .ccmmand Un~-User
Access/PermJSsjons-Trlgger-O.ue:ry Response Formatting
lntertate 0@velop,nent
Interlace Functional Validation
lnternlce Go-Live Ready -luerFiche, vtgllant LPR, Legacy Data Query, Crossroads Accident, C:rosstoads Citation, OORS, Q~Tel
CA~~d Mobile Training
g o-.Learnr!'i MJ~&en:!~nt~!uti«?!!._(~~) _____ _
LMS Admin Training
End User Access confirmed for LMS
Pr~mierO~CC~o Tr~;-the-TralMr
LMS Pr~R~qs __ _
PremierOne CAO Train-ttie-Tri:llner Course
_ P_!!,mierO!:Je CAO E11d User Training (6-Classes)
Pre:mie_'9ne Mobile Tr~lning_. .
PremierOne Mobile Train-the-Trainer (Police)
PremierOne Mo~le Train-the-Trainer (Fire)
P,emierOne Mobtle End User Training (CUSTOMER LEO)
CAD~Mobile Go Ll~
CAO and Mobil;: Go -Live Re.idy PCutOVcr Pl°an --
e ChedUst/Prep
e Event-S~bscfption St~
_G_o_l~~uPe_Ort (3 diys)
ive Remote Support
Mobile Support Engagement
Engagement Meeting
r SupPOrt Plan Review
ndOver
co;'..,l.ete
lOdays
7 days
lOdays
7 davs
7 days
90days
7 days
1 day
171~v_s
171 days.
ldoy
Odavs
s4-da~
l ~~V
4 days
30davs
32 days
ldoy
1 day
30days
40~
o days
s·,i,ys
lOdays
1 day
]days
30-edavs
31days
l day
1~
l da'-,1 oda
Swt Finish
Tue 5/10/22 Wedl0/5/22
Tue 5/10/22 Mon5/'l3/22
Tue 6/7/22 Thu 6/9/22
Wed6/22/22 Fri 6/24/22
Mon 7/4/22 Fri 9/23/22
Mon 10/3/22 Wed 10/5/22
Wed 10/5j2,2
Tue11/l/ll
~d_ 10/j/2_2_
Wed4/5/23
Tue 11/1/22 Mon 11/14/22
Tue 11/1/22 Wed 11/9/22
Thu 11/10/22 Wed 11/23/22 Tu• 11/1/22--Wed 11/9/22
Thu 11/10/22 Fri 11/18/22
Monll/21,hi M<m3/27/i3
Wed4/5/23
Tue6/Ujll
Tue 6/U/22
Tue Giisfff
Tue7M2
Thu12/8/U
Thu 12/8/22
Tue 1/3/23
wed1/lli23
Mon 119/23
Mon 1/9/23
Tue 1/10/23
Wed 1/11/23
Wed 4/5/2}
w_ed_4/W3
Thu 4/6/23
Thu 4/33/23
Thu 4/i7 /23-
Thu 4/27.i23
MonS/1/23
Fri 3/i?/23
Fri 3/17/23
Mon 3/27/23
Fri 4/28/23
WedS/31/23
Fri3/24/23
Tue 4/4/i3
Wed 4/5/23
Tue2/21/23
Tue 2/21/23-
~<!6/28/22
Tue 7/5/22
Tue 2/21/23
Thu 12is/22
Fr'o°l/6/23 -
Tue 2/21/23
Tue2/21/2r
Mon 1/9/23
Tue 1/10/23
Tue 2/21/23
Wed 5/31/23.
'wed4/5/23
'wed 4/12/23
Wed4/26/ii
-Thu 4/27/23
Mon 5/lii3
Wed 5/31/23
Fti 4/28/23
Fri 3/17/23
M~n ~/27/~3
_fri3fl_8/J}
Wed 5/3 23
May 10, 2022 Item #11 Page 448 of 604
DocuSign Envelope ID: EE0000EC-8 19D-469F-887C-147E3BCEAFF7 City of Carlsbad, CA
February 16, 2022
5.2 PROJECT PERSONNEL
Resumes of Project Personnel are on the following pages Full responsibility for the successful completion of the project implementation in accordance with the approved scope and schedule.
• Deploy PMP principles and methodology in project deployment process through inputs, tools techniques and outputs for integration, scope, time, cost, quality, human resource, communications, risk, procurement and stakeholder management
• Drive strategic relationships between internal teams through assembling needed knowledge, skills tools and techniques.
• Manage project budgets, implement metrics by maintaining data, mentoring, monitoring activities, being directly involved in troubleshooting, adhering to reporting requirements, escalate issues, through communication and collaboration; ·
• Fully define customer deliverables and needs: schedule, scope, and financials with detail, focused during planning through communicating regularly and providing field oversight; • Cultivate strong third party relationships through collaborating, negotiating adjusting and developing solutions to meet customer's satisfaction and acceptance • Negotiate and communicate project deliverables, scope, and expectations, and progress to the Senior Leadership Team
• Meet financial objectives by forecasting and estimating project work efforts • Manage stakeholder satisfaction through collaboration, open communication, develop scope adjustment, training, adhere to schedule, and budget constraints Proiect and Related Professional Exoerience
Motorola Project Experience
• Alhambra PD, CA-Flex CAD, Mobile, and RMS
• Kingman PD, AZ -Flex CAD, Mobile, and RMS
• Norcross PD, GA -Flex CAD, Mobile, and RMS
• Oswego County SO, NY -Flex CAD, Mobile, RMS, and Jail • Gem County SO, ID -Flex CAD, Mobile, RMS, and Jail
• Atascosa County SO, TX -Flex CAD, Mobile, RMS, and Jail Exhibit A: Contract Documentation Requirements
4' Motorola Solutions Payment Schedule 69
May 10, 2022 Item #11 Page 449 of 604
DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7 City of Carlsbad, CA
February 16, 2022
The Solutions Architect is responsible for the delivery of the technical elements of the solution, confirming they _meet contracted requirements. The SA is engaged throughout the duration of the delivery.
Implementation-related responsibilities include:
• Leads technical review of contract design
• Confirms the system design meets contractual requirements • Participates in network planning and design with customer and system/information technology group(s) • Implements interfaces
• Validates functionality and integration with 3rd party applications • Provides primary support for the system Go-Live which covers interfaces, data feeds, query responses.
Project and Related Professional Experience
Recent Motorola Project Experience:
• St. Johns County, Florida, Fire Rescue
o PremierOne CAD Implementation (2019-2020)
• City of Cayce, South Carolina
o PremierOne Cloud CAD Implementation (2020)
• Hampton County, South Carolina
o PremierOne Cloud CAD Implementation (2020)
• Lauderdale County, Alabama
o PremierOne Cloud CAD Implementation (2021)
• City of Boynton Beach, Florida
o PremierOne Cloud CAD Implementation (2021)
• St. Lucie County, Florida
o PremierOne CAD Implementation (present)
Related Experience
• Hexagon (Formerly Intergraph) -1996 -2017
o Executive Manager -2014 -2017
o Senior Technical Manager -2011 -2014
o Senior Technical Trainer/System Consultant-1996 -2011 • Dauphin County, Pennsylvania, Department of Public Safety o Telecommunicator/Supervisor/lnformation Technology Manager 1985-1 996 • 32 years of volunteer/paid-on-call fire and EMS service (1984-2016) Exhibit A: Contract Documentation Requirements
G Motorola Solutions Project Schedule and Personnel 70
May 10, 2022 Item #11 Page 450 of 604
OocuSign Envelope ID: EE0000EC-B19O-469F-887C-147E3BCEAFF7 City of Carlsbad, CA
February 16, 2022
Lead Application Specialist responsible for implementation-related activities:
• Conduct Business Process Reviews to collect information on current processes and workflows to aid in system provisioning,
• Work with customers to develop training strategies and plans and deliver provisioning and functional training courses,
• Create and modify documentation including lesson plans, workbooks, instructional activities and course documents.
• Provide "Go Live" support.
• Prepare written reports, documentation and participate in customer meetings. • Troubleshoot software anomalies during provisioning and training • Provide application and administration support for project team Professional and Project Experience
Motorola Project Experience:
• City of Nashville, TN Police and Fire
• Las Vegas Metro Police
• Indianapolis, IN Metro Police and Fire
• Peel Police (Ontario,CN)
Related Experience
• Aurora Public Safety Communications -2006 -2016
o Telecommunicator Specialist
o Telecommunicator Trainer
• Airlife Denver -2010-2011
o Flight Dispatcher
Exhibit A: Contract Documentation Requirements
G Motorola Solutions Payment Schedule 71
May 10, 2022 Item #11 Page 451 of 604
DocuSign Envelope ID: EE0000EC-819D-469F-887C-147E3BCEAFF7 M.S. -GIS Technology
B.A. -Computer Science
University of Arizona
Weber State University
City of Carlsbad, CA
February 16, 2022
Combat Engineering School, Airborne School, NCO
School
US Army and Utah National Guard
Responsibilities in Current Role
• Participate in the project kickoff, planning, installation and support of mapping/GIS for Premier One • Assist public safety agencies with GIS implementation as part of Computer Aided Dispatching systems implementation including gathering data requirements for ArcGIS, planning, and creation of the Geodatabase used for dispatch
• Train users in GIS products used with Motorola's PremierOne system • Work with customer support, product management, technical services and the business analyst group to troubleshoot trouble tickets, identify root cause and communicate user stories in a technical manner Professional and Project Experience
Recent Project Experience:
• GIS Lead for the following projects:
o Tioga & Oswego County Sheriffs office(s), New York
o Cowlitz 911, Washington
Related Experience
o GIS Analyst Ill -Flex Support (2016-2021)
. o Support Technician -Spillman Technologies (2005-2016) o Skilled with ESRI suite of products including ArcGIS Pro, Arc Desktop, Arc Enterprise • Technical skills in C, C++, Java, Perl, Python, Windows Server, Linux Exhibit A: Contract Documentation Requirements
fl Motorola Solutions Project Schedule and Personnel 72
May 10, 2022 Item #11 Page 452 of 604
DocuSign Envelope ID: EEOOO0EC-B19D-469F-887C-147E3BCEAFF7 City of Carlsbad, CA
February 16, 2022
The Solutions Architect is the post-sales technical lead who oversees the implementation and support of the CommandCentral solution from project initiation to system acceptance. • Network planning and design with customer and system technology group. • Prepare and execute network component health checks as well as on site final system acceptance test plans.
• Design and document interfaces to integrate the Motorola products with other systems. • Review requirement documents with the customer including work flow and system expectations. • Deploy interfaces to 3rd party systems
• Provide primary support for the system Go-Live which covers interfaces, data feeds and query responses.
Professional and Project Experience
Motorola Project Experience:
• Glendale PD, AZ
• Boca Raton PD, FL
• Boynton Beach PD, FL
• City of Lansing, Ml
• LVMPD, NA
• Mont ome Count , TX
Exhibit A: Contract Documentation Requirements
G Motorola Solutions Payment Schedule 73
May 10, 2022 Item #11 Page 453 of 604
DocuSign Envelope ID: EE0000EC-819D-469F-887C-147E3BCEAFF7 City of Carlsbad, CA
February 16, 2022
SECTION6
PRODUCT VALIDATION
6.1 PRODUCT VALIDATION PURPOSE
The purpose of this document is to describe the processes that will be used to verify the PremierOne Cloud CAD and Mobile System. This document provides the plan that describes the management, conduct, and reporting activities of product verification. All verification criteria will be predicated by the contract exhibits and Motorola's responses to Customer requirements in the RFP. Functional validation will be conducted only on those features and functions for which PremierOne Cloud CAD and Mobile have been provisioned.
6.2 VERIFICATION PROCESS OVERVIEW
This document details the steps that Motorola and the City will follow to prepare for and conduct the functional, interface and integration validation of PremierOne Cloud CAD and Mobile. This process will focus on demonstrating those features and functions to which Motorola complied in the RFP response and that are enabled on the City's PremierOne Cloud CAD and Mobile system.
Motorola will provide a set of specific scenarios which will be performed on the PremierOne CAD and Mobile. Additionally, the expected results for will be documented. These scenarios and their expected results will be delivered to the City for review, and once approved, will form the set of validation scenarios that will be performed.
The functional validation will be performed once the application is installed at the City's facility and Train the Trainer training has been conducted. City personnel will witness the functional validation and observe and acknowledge the res·ults. In the event that the observed results do not agree with the documented expected results, an exception/failure condition will be recorded. A resolution plan for exceptions/failures will be developed in order for the City to accept the system.
6.3 VALIDATION PROCESS ACTIVITIES
The activities that will be followed in the validation process are detailed in the sections of the document below.
6.3.1 Prepare Functional Validation Plan
A detailed functional acceptance test plan will be prepared by Motorola for the customer.
This plan will concentrate on testing the features and functions of the system that will be used by the customer and will not test areas of the system that Motorola did not comply with in the RFP response and for which provisioning was not completed (i.e. features or functions that are not applicable to the City's operations).
The validation plan will be organized as a set of scenarios, with each scenario being broken into one or more use cases.
Exhibit A: Contract Documentation Requirements
74 Product Validation Motorola Solutions 0
May 10, 2022 Item #11 Page 454 of 604
OocuSign Envelope ID: EE0000EC-B190-469F-887C-147E3BCEAFF7
6.3.1.1 Scenarios
City of Carlsbad, CA
February 16, 2022
Scenarios are high-level, cross-product workflows of the system. These scenarios are described from an end-to-end user perspective. Scenarios focus on the user domain information, but also describe the high-level functional interaction between PremierOne CAD and Mobile.
6.3.1.2 Use Cases
6.3.2 6.3.3
6.3.4 6.3.5
Use Cases are the decomposition of Scenarios into specific user and product functional interactions required to execute a task. Use Cases define the success oriented scenario and key exception cases. Note that several Use Cases may be required to execute a particular Scenario. Use Cases define functional interaction between products; specific messages and message sequence between products are defined in Interface Control Documents.
Prepare Interface Validation Plan
Motorola will develop validation plans that demonstrate that interfaces and integration operate in accordance with the approved Interface Functional Descriptions. Where appropriate, the functional validation scenarios will incorporate interface functionality.
Motorola will also document the means by which integration between the Motorola primary system components will be tested and verified.
Validation Plan Approval
The Validation Plan will be reviewed with the City and formally approved. Validation will not begin before the Validation Plan is approved.
Validation Execution
Execution of validation procedures/cases will be conducted in an orderly manner. They will be performed as described in the Validation Plan and each action and result will be properly verified by City-designated personnel. The results of each scenario will be recorded as a pass or failure and the specific details of any failures will be recorded.
System configuration will be controlled throughout the execution of the Validation Test. At the start of the period, all provisioning and configurable items will become the baseline, any subsequent changes will be configuration controlled to ensure consistency in the testing processes. A configurable item, with respect to the customer's system environment, is defined as any document, software application, or hardware component integral to the installed system.
Validation Failures
All failures identified during validation phases will be recorded in Motorola's defect tracking system. Each failure will be assigned a severity level to allow the team to prioritize their handling of the failure. The severity levels that will be used are those defined in the Maintenance and Support and Agreement.
Exhibit A Contract Documentation Requirements
0 Motorola Solutions Product Validation 75
May 10, 2022 Item #11 Page 455 of 604
DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7 City of Carlsbad, CA
February 16, 2022
Since there is some subjectivity in determining the level of severity and impact, it is critical that several perspectives are considered when the assignment of a failure's severity is made. Therefore, the determination of severity will be made by a cross-functional team containing both Motorola and the customer representatives.
A resolution plan will be developed that identifies the action(s) that were taken or will be taken to address and/or correct the failure and the method by which the corrected function will be retested.
6.4 SAMPLE FUNCTIONAL VALIDATION WORKBOOK
A sample Functional Validation Workbook has been included as a separate Excel Document.
This is an electronic document, v.4.6.x.x.
Exhibit A: Contract Documentation Requirements
76 Product Validation Motorola Solutions G
May 10, 2022 Item #11 Page 456 of 604
DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7 SECTION 7
City of Carlsbad, CA
February 16, 2022
HARDWARE AND NETWORK
SPECIFICATIONS
7.1 PREMIERONE CLOUD HARDWARE AND ENVIRONMENT
7.1.1 General Hardware and Environment Requirements
The Customer will provide hardware and/or an environment that conforms to the following general requirements:
Customer Responsibilities
1. Supply hardware, operating system software, third party components, and other elements not speci_fically identjfied as being provided by Motorola.
2. Provide advanced authentication for Mobile/Handheld device connectivity if required.
3. Provide a network diagram depicting all the devices, device types, and interfaces that the service will connect to and through, including, but not limited to all blocked ports, hubs, switches, routers, firewalls, and any other network equipment.
4. Provide IP addresses on the Customer's network for the required on-premise equipment (i.e the Anchor Server). All server names and IP addresses behind Motorola Firewalls cannot be changed. ·
5. Provide external interface connection demarcation points at locations agreed to by Motorola. These locations shall normally be adjacent to the cloud interface appliance.
6. Provide access, administrative or otherwise, to appropriate systems, locations, information, tools, and equipment to ensure proper connectivity, installation, operations, and maintenance of the service.
7. Provide 24-hour access to a secured two-way Internet connection to the cloud interface appliance and firewalls for the purposes of deployment, maintenance, and monitoring.
8. Provide a site to site VPN with at least 4 addressable IP's on the inside subnet capable of establishing and maintaining an IPSec tunnel with 75Mb/s of throughput.
9. The Motorola delivery model is reliant upon our ability to perform most tasks remotely, which requires secure, remote broadband access for remote deployment, monitoring, and support of the cloud interface Anchor Server appliance. It is understood that remote access to on-premise server and Customer's network must be supervised, which supervision will be provided. Customer-provided high-speed internet access with a minimum of 10 Mbps is required at the time of project kickoff and must remain available to Motorola throughout warranty and support periods to accommodate remote support of the service. In the event that dedicated links are required, a minimum of 7.5 Mbps upload and download access is required. It is the Customer's responsibility to ensure that the aforementioned capacity is available. In the event remote broadband access is Exhibit A: Contract Documentation Requirements
G Mot~ro/a Solutions Hardware and Network Specifications 77
May 10, 2022 Item #11 Page 457 of 604
DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7 City of Carlsbad, CA
February 16, 2022
7.1.2 7.1 .2.1
not available to Motorola preventing us from delivering the contracted service remotely, Motorola will provide service on-site at additional cost. The additional cost will be presented to the Customer via the change provision of the contract prior to the delivery of the on-site service.
10. Provide, install, maintain, and service any software as required for anti-viral, anti- malware protection on workstations that access the service. If the software requires connectivity to a central server for maintenance and updates, the connectivity including ports and access needs to be provided.
Component Specifications
Motorola will provide Commsys Connect CIC. The Customer will provide the server hardware and firewall devices ...
PremierOne Cloud Anchor Hardware
Customer Responsibilities
1. Provide, install and configure server hardware, operating system software, VMWare, firewall devices, Lantronix External Device Server and SQL Standard. Specifications will be provided at the Planning Meeting. ·
A. Provide a VMware host environment capable of supporting two VMs. i. Windows ServerVM, 4vcpu, 16GB RAM and 3 HOD 120/120/25GB ii. Linux VM, 2VCPU, 8GB RAM and 1 HOD 20GB
B. Verify the VM has connectivity to the internet and the following addresses, which are commonly used by CloudConnect:
- https://idm.imw.motorolasolutions.com (443) -IDM
- https://aware-api.usgov.commandcentral.com (443) -Ingest - https://admin-api.usgov.commandcentral.com (443) -Admin - https://aware-publisher-ws.usgov.commandcentral.com (443) -Publisher (WebSocket)
- https://registry.commandcentral.com (443) -Registry
- https://oneinterfaceblobstore.blob.core.usgovcloudapi.net/(443) -lmageNideo upload
-Additional Endpoints For IMW/LRRP Interfaces
-https :/ / ccinterfaces-ccbroker-prod. usgov. commandcentra I. com/api/ ccinterfaces- ccbroker (443)-IMW/LRRP
- https://ccinterfaces-sasgen-prod.usgov.commandcentral.com/api/sasgen (443) - SAS Token
- https://qrwbubhpaovhj-sbu.servicebus.usgovcloudapi.net (443) (Websocket) (inbound-outbound)
Motorola Responsibilities
1 . Provide the CloudConnect VM image to Customer.
2. Remotely support installation of VM image on Customer hardware.
Exhibit A: Contract Documentation Requirements
78 Hardware and Network Specifications Motorola Solutions G
May 10, 2022 Item #11 Page 458 of 604
DocuSign Envelope ID: EEOOOOEC-B19D-469F-887C-147E3BCEAFF7 City of Carlsbad, CA
February 16, 2022
7.1 .2.2 CommSys Connect CIC
7.1.2.3 Motorola Solutions Responsibilities
1. Provide CommSys Connect CIC.
PremierOne Cloud CAD Local Workstation
The Customer will procure and provide local (fixed) workstation hardware that conforms to the requirements laid out in this section.
• Windows 10 operating system.
• Monitor(s) -two or three with recommended resolution 1920 x 1080 (per client preference: i.e. three for CAD dispatch, two for CAD call taker, etc.). • QWERTY Keyboard with 12 function keys
7.1.2.4 Records Client Workstation Requirements
• Browser compatible with Citrix Virtual Application. Chrome, Internet Explorer, and Edge are examples of compatible browsers. The PremierOne Provisioning Console requires use of Internet Explorer.
7.1.2.5 PremierOne Cloud Field Workstation
The Customer will procure and provide field (mobile) workstation hardware that conforms to the requirements laid out in this section.
• Android smartphones and tablets with Android 8 -10.
• iPhones and iPADs with iOS 11 -13.
• Windows laptops and tablets with Windows 10.
7.1.2.6 PremierOne GIS Workstation
The Customer will procure and provide GIS workstation hardware that conforms to the requirements laid out in this section.
• Android smartphones and tablets with Android 8 -10.
• iPhones and iPADs with iOS 11 -13.
• Windows laptops and tablets with Windows 10.
7.1.2.7 CommandCentral Aware Workstation
The Customer will procure and provide Aware workstation hardware that conforms to the requirements laid out in this section.
• Processor-Intel Xeon 6136 @3.0 GHz (12 cores).
• Memory-32 GB.
• Drive-One NVMe 512G SSD.
• NIC-1 GB port NIC.
• OS-Windows 7 Professional or Windows 1 O Pro.
• Graphics Card-NVIDIA Quadro P2000
• 27-inch Narrow Bezel IPS Display, 2560X1440
Exhibit A Contract Documentation Requirements
f1' Motorola Solutions Hardware and Network Specifications. 79
May 10, 2022 Item #11 Page 459 of 604
DocuSign Envelope ID: EE0000EC-819D-469F-887C-147E3BCEAFF7 City of Carlsbad, CA
February 16, 2022
7.1.3 7.1.3.1
7.1.3.2 Network and Other Environment Specifications
Unless otherwise stated in this SOW, the Customer will provide a network environment that conforms to the requirements laid out in this section. The Customer will provide an environment sufficient to support the transaction volume generated during Customers peak operational periods.
Network Connection Requirements
PremierOne Cloud client connections must meet the following requirements:
• Stable internet connection.
• Small Jitter (packet delay variation) -below 200ms, recommended <30ms. • Small Ping roundtrip time -below 1 00ms, recommended <20ms. • Small Packet Loss -no more than 1 %.
• Bandwidth: 1 Mbps per fixed client (will vary with specific usage). • Provide cloud connectivity services for desktop CAD user clients per specifications. • Provide for outbound Internet connectivity initialized by Cloud Anchor Server.
Multiple paths .are preferred for the PremierOne Cloud CAD Service. ISP connectivity to the Azure Public Edge is required for the CAD client connectivity. Interfaces to on-premise systems use a VPN device that requires connectivity to the Azure Public Edge. The Customer is responsible for providing all connections to the cloud.
Mobile Network Requirements
PremierOne Mobile functionality is designed for 3G and high-end 4G networks. 3G network connectivity is required, but faster 4G connectivity is highly recommended. The Customer will provide a 3G/4G wireless network infrastructure and connectivity with routing between the Mobile clients and the cloud that meets or exceeds these minimum requirements.
Customer Responsibilities
1. Supply Mobile Device Management (MDM) software for Handheld devices.
2. Supply Mobile Device Management (MDM) software for Mobile devices, as desired by the Customer.
3. Provide wireless connectivity for mobile clients to the Azure cloud. Optimal application performance on mobile workstations requires 4G connectivity.
7.1.3.3 Aware Network and Bandwidth Requirements
• Two (2) static IP addresses, corresponding subnet masks/default gateway, and available NTP and DNS IP to the Cloud Anchor Virtual Machines.
• Three (3) static IP addresses, corresponding subnet masks/default gateway, and available NTP and DNS IP to the Cloud Anchor Server.
• One (1) network port for each VMS server.
• One (1) network port for each VMS analytics appliance • Provide network ports that are 1 GB capable and network mutable.
Exhibit A: Contract Documentation Requirements
80 Hardware and Network Specifications Motorola Solutions tJ.l
May 10, 2022 Item #11 Page 460 of 604
DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7 • Minimum bandwidth needed between the Cloud Anchor server and the CommandCentral Aware platform is 1.1 Mbps.
City of Carlsbacl, CA
February 16, 2022
• Low latency is critical for real-time operations. The speed with which data appears on the Aware display depends in large part on how quickly the information is presented to the Aware interface. Major contributors to the latency are network delays and the delay time from occurrence of an event to when that event information is presented to Aware from the source application (i.e., CAD, AVL, ALPR, etc.). Consequently, although the Aware strives to provide near-real-time performance, Motorola provides no guarantees as to the speed with which an event (or video stream) appears on Aware once the event is triggered.
7.1.3.4 Vigilant LPR Requirements
Bandwidth requirements:
• 1 Gbps hardwire switched network between the Vigilant server and Cloud Anchor. • Upload of ALPR data to the LEARN backoffice requires approximately 350 Kbps for each scan per second. Depending on maximum scan volume, the maximum bandwidth may need to be adjusted.
• The RTSP video feed from cameras requires a 1 Gbps hardwire switched network device to allow for data communications exceeding four connected cameras.
Firewall requirement:
• CommandCentral Aware Workstation needs access to the IP addresses of Cloud Anchor and Vigilant server. Access to Cloud platform endpoints. • Ports that need to be open-TCP 80, TCP 443, TCP 3310 (or custom SQL Database Engine listening port that might have been configured for security reasons). • The basic service requirements of the system through a firewalled environment consist of: HTTPS web based calls to a cloud back-office solution (LEARN) with S3 image storage. Typically, through a mobile broadband endpoint. A local IP listener for RTSP video stream is used from cameras with TCP communications. • Ingress requirements (firewall traffic in): For Wireless Broadband we require TCP port 443 to communicate with the LEARN server backoffice to receive acknowledgement responses from the client. Camera Communications: TCP port 2000, 3000, 4000, 5000 (LAN/DSP).
• Egress requirements (firewall traffic out): For Wireless Broadband communications the ALPR client requires TCP port 443 to communicate with the LEARN server backoffice.
The HTTPS protocol is primarily used to communicate over TLS 1.0, 1.1, or 1.2 with 128-bit encryption ciphers or better. This allows for the upload of ALPR data to the LEARN web services and request for data from the LEARN services and Google Maps.
7.1.3.5 ASTRO 25 Radio and Infrastructure Requirements
The solution can be deployed to send location data information using an ASTRO 25 radio equipped with a GPS receiver with minimum firmware version 7.18.8 and at software version R15.00.00 or later. ASTRO 25 system release 7.14 or above is required if the data will be sent via the LMR system. Enhanced Data and Intelligent Middleware (IMW) in addition to a Exhibit A: Contract Documentation Requirements
f1l Motorola Solutions Hardware and Network Specifications 81
May 10, 2022 Item #11 Page 461 of 604
DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7 City of Carlsbad, CA
February 16, 2022
firewall to connect the system CEN and internet securely including a packet data gateway and GGSN for each zone are used to send the location updates and events can be enabled as part of that effort. Customer will be responsible to provide internet connection and will allow Motorola to add any necessary firewalls.
• GPS Activation and Enabled.
• Packet Data Interface.
• Enhanced Data Enabled.
-Supported on portables-APX 8000, APX 7000, APX 6000, APX 4000, APX 3000. -Supported on mobiles-APX 7500, APX 6500, APX 4500.
• Enhanced Data Port List set to 4001.
ASTRO 25 Voice Priority
ASTRO Enhanced Data subscribers give priority to voice transmissions over data.
Exhibit A: Contract Documentation Requirements
82 Hardware and Network Specifications Motorola Solutions G
May 10, 2022 Item #11 Page 462 of 604
DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7 SECTION 8
INTERFACE CONTROL
DOCUMENTS
Exhibit 2: Interface Functional Descriptions
8.1 PREMIERONE CLOUD CAD INTERFACE FUNCTIONAL
DESCRIPTIONS
Table 8-1: List of Interfaces and Queries
Customer known as Interface Function
NetRMS Outbound Calls For Service Data Feed
NetRMS Query Third Party System
Spidr Tech Outbound Calls For Service Data Feed
Axon Outbound Calls For Service Data Feed
Coplogic DORS Inbound CAD Incident Create*
CLETS/NCIC Query State Query
Crossroads Accident Query Query Third Party System
Crossroads Citation Query Query Third Party System
Coplogic DORS Query Query Third Party System
LaserFiche Query Query Third Party System
QueTel Query Query Third Party System
Legacy Query (CAD) Query Third Party System
*Dependent on 3rd Party ability to write to PremierOne API City of Carlsbad, CA
February 16, 2022
8.1.1 CAD Calls For Service Data Feed Interface Functional Description The Cloud CAD CFS interface allows Cloud CAD to provide Calls for Service (CFS) data to a third-party system. The Cloud CAD Interface will extract the specified CFS data from the Motorola Solutions PremierOne Cloud CAD System and provide the data by delivering JSON files to a file drop location via the FTP, SFTP, or SMB protocol.
Exhibit A: Contract Documentation Requirements
CD Motorola Solutions Interface Control Documents 83
May 10, 2022 Item #11 Page 463 of 604
DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7 City of Carlsbad, CA
February 16, 2022
8.1.1.1 8.1.1.2
The Cloud CAD CFS interface provides specified CFS data and is based on new or updated incidents. The interface provides the current snapshot of the incident and sends updates as they occur in the Cloud CAD system. The interface will be sending incidents, incident unit and narratives near real-time.
Data Elements included in this interface are provided in the Proprietary Information section of this Product Page.
The functionality and data set provided with this interface is predefined and non-negotiable.
Supported Use Cases
1. The CFS interface will send Incident and Incident Unit data to the third party system when a new incident is created and contains a report number.
2. As part of the system configuration, the list of desired agencies can be set which will be used as a filter to determine which incidents are delivered.
3. When incidents are updated, the CFS interface will deliver a new copy of the incident file to the target system.
4. Updates are transactional and cannot be sent in timed intervals. The third party will receive each update as it occurs.
Specific Technical Requirements
Target System Version Target System Connection
Protocol
File drop in JSON format via FTP,
SFTP or SMB protocol
Send
Only -
Acknowledge
Received / Send
NOTE: Any other type of connection to the third party system (e.g. SOAP/REST API) or file format (e.g. XML) is not supported for this Standard interface. If integration with a 3rd party API or a different file format is required, a Custom interface will be needed instead. • This interface requires installation and configuration of an on-premises CloudConnect virtual machine, typically hosted on the Anchor Server
• An FTP, SFTP, or SMB server with appropriate credentials and permissions is required for the interface to write to (typically provided by the customer or 3rd party CFS consumer)
• Network connectivity needs to be established between the CloudConnect VM and the file drop server location with appropriate.ports open (depending on file delivery method chosen)
• N~twork connectivity needs to be established between the CloudConnect VM and the PremierOne cloud (see CloudConnect network requirements for details on required ports and URLs)
• Exceptions are logged in the CIE Cloud CAD logging environment • The interface will send incidents, incident unit and narrative data in one payload • All data will be provided as specified below .. No table lookups, format conversions, additions, omissions, etc. will be performed.
Exhibit A: Contract Documentation Requirements
84 Interface Control Documents Motorola Solutions
May 10, 2022 Item #11 Page 464 of 604
DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7
8.1.1.3 8.1.2
Data Elements Included in Interface:
Incident Information
• Incident Number
• Incident ID
• Agency ID
• Incident Date
• Report Number
• Incident Started Date Time
• Report Number Agency ID
• Area Name
• Sector Name
• Beat Name
• Location
• Apartment
• City Name
• Latitude
• Longitude
• Cross Street
• Intersection
• Zip Code
• State Name
• Incident Units Call sign
• Incident Unit Incident Number
• Unit History Unit Agency
• Unit History Unit ID
• Unit History Status
• Unit History Time
• Unit History Transaction Type
• Unit Current Home Station Name
• Unit Current Agency Key
• Unit Current Home Area Key
• Unit Current Unit Key
• Incident Comments
• Incident Comment User ID
• Incident Comment Date Commented
• Incident State Name
CAD Incident Create Interface Functional Description
City of Carlsbad, CA
February 16, 2022
The Incident Creation Interface allows a 3rd-party system to create incidents in Cloud CAD.
This allows the Dispatcher to process incidents initiated by external systems or devices.
A pending incident containing the information supplied by the 3rd-party system appears in the Dispatcher's pending status monitor and is handled in the same fashion as any other incident.
When an incident-generating event is created within the external system, the external system generates an incident creation request to the Cloud CAD Incident Create interface via JSON over REST API.
Exhibit A: Contract Documentation Requirements
ti Motorola Solutions Interface Control Documents 85
May 10, 2022 Item #11 Page 465 of 604
DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7 City of Carlsbad, CA
February 16, 2022
8.1.2.1 8.1.2.2
8.1 .2.3
The pending incident can be displayed in the Pending Status Monitor window. The ID generated by the external system is displayed on CAD Client as the Foreign Incident Number. This number can be used in the·lncident Recall and Incident Update commands by placing the~ (tilde) character in front of the number to indicate it is a Foreign Incident Number.
Supported Use Cases:
• Cloud CAD can receive a CFS request and create an incident • Cloud CAD user can view the incident
Unsupported Use Cases:
• For each event, the external system sends a single incident message to the Cloud CAD Incident Creation interface. No updates are expected or processed by CAD.
Specific Technical Requirements
NOTE: Any other"type of connection from the third party system (e.g. SOAP, file drop, etc.) or file format (e.g. XML) is not supported for this Standard interface. If integration with a 3rd party API or a different file format is required, a Custom interface will be needed instead. • The REST API is hosted in the Motorola Solutions cloud. Customer/3rd party system is responsible for ensuring access to the API is available. • All data will be provided as specified below. No table lookups, format conversions, additions, omissions, etc. will be performed.
Proprietary Information / Data Mapping:
Data Elements accepted from external system via Interface REST API • DisciplineCode
• NatureCode
• Comments
• lncidentSource
• Consumer
• CorrelationlD
• Priority
• Location
• Address
• FullText
• CrossStreet
• Intersection
• Building
• Floor
• Apartment
Exhibit A: Contract Documentation Requirements
86 Interface Control Documents Motorola Solutions
May 10, 2022 Item #11 Page 466 of 604
DocuSign Envelope ID: EE0000EC-819D-469F-887C-147E3BCEAFF7
8.1.3 8.1.3.1
• Subdivision
• City
• State
• ZIP Code
• Latitude
• Longitude
• Description
• Jurisdiction
• AreaKey
• SectorKey
• BeatKey
• Name
State Query Interface Functional Description
City of Carlsbad, CA
February 16, 2022
The Interface allows PremierOne users to submit transactions to State and Federal systems, via the State Message Switch. These transactions are most typically ones that perform inquiries, although transactions that enter, modify, locate, and clear information are also possible.
The State Message Switch provides links to State systems like Department of Motor Vehicles (OMV) and national law enforcement systems like National Crime Information Center (NCIC).
Query requests can be made on PremierOne CAD or Mobile clients. The PremierOne Query Service processes the request and determines which data source(s) can fulfill the request.
This information is then passed to the PremierOne Interface component, which translates the request to XML messages and passes it on to CommSys ConnectCIC. ConnectCIC handles the State connection and translates the messages to the query strings required by the State. The State Message Switch forwards the request to the appropriate system.
When a response is received, ConnectCIC parses and returns the response to the PremierOne Interface component as an XML message. The Interface parses the response and forwards it to PremierOne Messaging Service, which handles the routing of the query response to the requestor. User access to the query forms is managed by the user roles provisioned in PremierOne.
Supported Use Cases
• An authorized PremierOne user can select a query type, enter the required query parameters, and submit the query using a Query Request form. • PremierOne administrator may also create a command line version of a query form. This use case allows users to quickly submit frequently used queries. The administrator may also configure the system so queries can be submitted using person and vehicle information entered in an incident.
• Query responses are displayed in the Query Responses tab of the query window. They may also be displayed in a dedicated window outside of the main CAD client window. • Query Request forms are built upon the underlying data supplied by the External System. A form could use one or more underlying data sources. Thus, query responses from a particular form could be from multiple data sources.
Exhibit A: Contract Documentation Requirements
G Motorola Solutions Interface Control Documents 87
May 10, 2022 Item #11 Page 467 of 604
DocuSign Envelope ID: EEOOOOEC-B19D-469F-887C-147E3BCEAFF7 City of Carlsbad, CA
February 16, 2022
8.1.3.2 8.1.3.3
• In most States, the query response sent back from the State Message Switch is a block of text. This text will be displayed to the user.
• Certain responses may be parsed, by ConnectCIC, which involves examining the response and determining where certain key data such as names, addresses, and license status are placed. This structured response is available as discrete values to PremierOne. This can be used to provide a visually formatted response that emphasizes key information.
Unsupported Use Cases
• Query Responses can be formatted for Workstations and Mobile clients. Query formatting is done using Extensible Stylesheet Language Transformations (XSL T) and the result is displayed using Hypertext Markup Language (HTML). The HTML transformation provides an enhanced level of formatting beyond the raw text that is returned in the query responses. The enhanced formatting can be helpful to call out specific data elements, or display images if they are included in the response from the External System.
• A structured response may also be used to populate the person or vehicle information in an incident, without requiring the retyping of the information from a response. The user may run a query on a driver using their operator license number, and then use this feature to populate the person form with the person's details from the query response. • Cascading and drill-down queries can be provisioned by using details from the structured query response as input to subsequent queries. Cascading queries run automatically using these results and a drill-down query is run when the user clicks on the hyperlink on the response form.
Specific Technical Requirements
N/A NIA X X
• Connectivity needs to be established between PremierOne Suite and the State Message Switch, over the Custom.er Enterprise Network, using TCP protocol. The connection needs to meet the State's security requirements.
• PremierOne exceptions are logged in both the Windows Event Log on the application server and the PremierOne database.
• CommSys ConnectCIC logs query errors and parsing issues to the ConnectCIC log file on the PremierOne application server.
• User access to the query forms are managed by user roles in PremierOne. • Users need to be certified according to the State requirements and have a valid user account to access the State system. Devices used to submit queries must also meet the State security requirements.
• The query response is dependent on the State connection and response time of the data sources. Query response is displayed as it is received from the external data source. • Customer is responsible for contacting Motorola Solutions when changes occur in the Interface or Customer Enterprise Network, which might affect the Interface. • Customer is responsible for maintaining user credentials, ORls and Mnemonics as required by the State.
Exhibit A: Contract Documentation Requirements
88 Interface Control Documents Motorola Solutions
May 10, 2022 Item #11 Page 468 of 604
DocuSign Envelope 10: EE0000EC-B19D-469F-887C-147E3BCEAFF7
8.1.4 8.1.4.1
City of Carlsbad, CA
February 16, 2022
• Customer is responsible for contacting Motorola Solutions when State changes the parameters or the response formats of the queries.
Third Party Query Interface Functional Description
The Interface allows PremierOne users to submit transactions to a third-party system. These transactions are most typically ones that perform inquiries, although transactions that enter, modify, locate, and clear information are also possible.
Query requests made on PremierOne CAD or Mobile clients are routed to one of the PremierOne application servers. The PremierOne Query Service processes the request and determines which data source(s) can fulfill the request. This information is passed to the PremierOne Common Services Interface (CSI) component, which translates the request to a query string and handles the connection to the data source. When a structured response is received, CSI parses the response and forwards it to PremierOne Messaging Service, which handles the routing of the query response to the requestor.
The interface can support calls to a Stored Procedure on the third-party system database or a call to an Application Programming Interface (API) published by the third-party system to get the data. The interface also supports Open Database Connectivity (ODBC), REST Web Service and Transmission Control Protocol (TCP) connections.
This interface implementation is limited to 6 forms with basic response formatting and 2 response types per request. Motorola Solutions will provide 8 hours of training and support for Customer to provision additional queries. This interface does not include enhanced response formatting or cascading/drill down queriel?. If these features are desired, they can be added on for additional cost during contract negotiations or through the change order process.
PremierOne services manage the data transformation and exchange process. The interface may direct a single query request to multiple systems, and each system will provide its own response.
Supported Use Cases:
• PremierOne user can select a query type, enter the required query parameters, and submit the query using a Query Request form. The same query forms are available throughout the PremierOne Suite.
• User access to the query forms is managed by the user roles provisioned in PremierOne.
• PremierOne administrator may also create a command line version of a query form. This allows users to quickly submit frequently used queries. • The administrator may also configure the system so queries can be submitted using person and vehicle information entered in an incident.
• Query Request forms are built upon the underlying data supplied by the third-party system. A form could use one or more underlying data sources. Thus, query responses from a particular form could be from multiple data sources. • Query responses are displayed in the Query Responses tab of the query window. They may also be displayed in a dedicated window outside of the main CAD client window.
Exhibit A: Contract Documentation Requirements
ti Motorola Solutions Interface Control Documents 89
May 10, 2022 Item #11 Page 469 of 604
DocuSign Envelope ID: EE0000EC-819D-469F-887C-147E3BCEAFF7 City of Carlsbad, CA
February 16, 2022
8.1.4.2 • If the third-party system provides a structured response, then this data is available as discrete values to PremierOne. This can be used to provide a visually formatted response that emphasizes key information.
Unsupported Use Cases:
• Query Responses can be formatted for Workstations and Mobile clients. Query formatting is done using Extensible Stylesheet Language Transformations (XSL T) and the result is displayed using Hypertext Markup Language (HTML). The HTML transformation provides an enhanced level of formatting beyond the raw text that is. returned in the query responses. The enhanced formatting can be helpful to call out specific data elements, or display images if they are included in the response from the third-party system.
• A structured response may also be used to populate the person or vehicle information in an incident, without requiring the retyping of the information from a response. The user may run a query on a driver using their operator license number, and then use this feature to populate the person form with the person's details from the query response. • Cascading and drill-down queries can be provisioned by using details from the structured query response as input to subsequent queries. Cascading queries run automatically using these results and a drill-down query is run when the user clicks on the hyperlink on the response form.
If these additional features are desired by the Customer, Motorola Solutions will provide a change order for Customer consideration for the enhanced response formatting.
8.2 SPECIFIC TECHNICAL REQUIREMENTS:
Data Fields & Proprietary Information:
This Interface requires modification to PremierOne Interface service. Motorola Solutions is reliant on receipt of the API or Stored Procedure and the associated design documents from the Customer to implement the Interface.
Exhibit A: Contract Documentation Requirements
90 Interface Control Documents Motorola Solutions
May 10, 2022 Item #11 Page 470 of 604
DocuSign Envelope ID: EEOOOOEC-B19D-469F-887C-147E3BCEAFF7 SECTION 9
City of Carlsbad, CA
February 16, 2022
PREMIERONE CLOUD
TRAINING PLAN
9.1 OVERVIEW
Motorola Solutions considers training to be an extremely important aspect of the adoption of a new solution and requires working closely with the Customer.
Motorola's instructors are certified through the Learning and Performance lnstitute's Trainer Performance Monitoring & Assessment (TPMA) program, as well as their Online Learning Facilitators program. Motorola uses a learning management system (Learning exPerience Portal or LXP) for both online and virtual training.
9.2 CUSTOMER TRAINING ROLES
9.2.1 Customer Training Representative
9.2.2 During the Project Planning Phase, the Customer will designate a Customer Training Representative. This individual will be the contact for the Learning Management System and Motorola trainers. The Customer Training Representative will provide Motorola user names and email addresses so access to the LXP can be completed.
The Customer Training Representative should be familiar with the Customer's daily operations and must attend (or designate a replacement) each Motorola educational course. Motorola trainers will rely on this representative to be the one point of contact for Motorola staff when policy and procedural questions arise, act as course facilitator, and act as the Customer's educational monitor.
The Customer will also identify the personnel who will serve as trainers. These individuals must participate in all the Train-the-Trainer courses. In addition to the skills described below, the Customer's trainers must have prior experience as a classroom instructor and a thorough understanding of the Customer's operations.
Other courses will require participants from different areas of the Customer's operations as shown in the individual Motorola training course descriptions below.
Learning Management Administrator
The Customer will assign a Learning Management Administrator during the Project Planning Phase of the Project. The Learning Management Administrator will attend the Learning Management System Admin Overview and will be given the ability to add/modify users, run reports, and add/modify groups within the panorama. They can also build Groups, a more granular segmentation of the LXP that is generally used to separate learners of like function (i.e. dispatchers, call takers, patrol, Exhibit A: Contract Documentation Requirements
ti Motorola Solutions PremierOne Cloud Training Plan 91
May 10, 2022 Item #11 Page 471 of 604
DocuSign Envelope ID: EE0000EC-819D-469F-887C-147E3BCEAFF7 City of Carlsbad, CA
February 16, 2022
9.2.3 firefighter). Learners can be assigned a Learning Path (a collection of courses that follow a logical order which may or may not enforce linear progress).
Customer Training Attendees
Students should have a typing proficiency of 25 wpm, knowledge of PCs and Microsoft Windows, and have completed course prerequisites as listed in the course descriptions prior to the training.
9.3 PREMIERONE CLOUD TRAINING PLAN SCOPE
9.3.1 The following sections delineate the courses that are offered for the PremierOne Cloud solution. While the scope of this document presents the complete array of training offerings, only those offerings directly associated with the contracted solution will be delivered or made available to the Customer.
Customers may purchase additional courses and onsite training as desired via the initial contract or via the change provision ·of the Agreement.
The following presents each training offering available for each major functional area of the PremierOne Cloud solution. Training will be delivered in accordance with the project schedule. In some cases, courses may be delivered in a combined training session in order to realize efficiencies in training delivery and to optimize the training experience of the student.
For example, PremierOne Cloud Mobile Provisioning may be appended to a PremierOne Cloud CAD Provisioning course in order to take advantage of the workflow logic and provisioning choices of both functional areas.
PremierOne Cloud CAD
Course Module Number of
Courses Included
Learning Management System Admin Overview 1
PremierOne Cloud CAD Provisioning Workshop 1
PremierOne Cloud GIS Import Training 1
PremierOne Cloud CAD Train-the-Trainer 1
PremierOne Cloud CAD End User Training 6
SSRS Report Builder Training in PremierOne for 1
CAD/Mobile
Exhibit A: Contract Documentation Requirements
92 PremierOne Cloud Training Plan Motorola Solutions G
May 10, 2022 Item #11 Page 472 of 604
DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7
9.3.2 9.3.3
9.3.4 9.3.5
9.3.6 PremierOne Mobile
Course Module
PremierOne Cloud Mobile Provisioning Workshop
PremierOne Cloud Mobile Client Installation (Windows,
Android, iOS) Overview
PremierOne Cloud Mobile Train-the-Trainer w/Aware
Map and Incident Viewer overview
CommandCentral Aware
City of Carlsbad, CA
February 16, 2022
Number of Courses
Included
1 1
2 Course Module Number of Courses
Included
End User Training -LXP Computer Based 1
Aware Workshop -Virtual 1
CommandCentral Investigate End User
OPTION -CommandCentral Community Digital Evidence
Collection
Course Module
CommandCentral Community Digital Evidence Collection
OPTION -WatchGuard V300 Cameras
Course Module
WatchGuard RE4/M500 and/or V300 End-User Training
(Officers)
Number of Courses
Included
Number of Courses
Included
Exhibit A: Contract Documentation Requirements
G Motorola Solutions PremierOne Maintenance and Support Agreement 93
May 10, 2022 Item #11 Page 473 of 604
DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7 City of Carlsbad, CA
February 16, 2022
9.4 9.4.1
9.4.2 9.4.3
PREMIERONE CLOUD TRAINING GENERAL
INFORMATION
Training Courses
Types of training courses may include the following:
• Administrative Workshops -Provide specialized users with in-depth knowledge on the features, operational, and administrative functions of the system. • Train-the-Trainer -Instructor-led classroom training that provides key individuals with extensive hands-on use of the system using true-to-life incident scenarios so they can develop and provide training to new users.
• LXP -Online "anytime" training using the Learning Management System.
Training Facilities and Schedules
The Customer shall provide facilities for training courses which are alcohol and smoke-free. Both the on-site and virtual classes will require a computer projector connected to high~speed internet to support virtual/video classroom connection to the instructor. The workshop format also requires multi-monitor student workstations.
Students and instructors will dedicate class time to training and will not be subject to interruptions.
The Customer will:
• Mutually agree with Motorola on the Training schedules to accommodate the Customer's shift operations and other site-specific requirements. Evening courses will end by 11 :00 p.m. Weekends and Holidays will not be used as training days.
• Supply Motorola with a roster of course attendees at least two weeks prior to training courses, and they will be provided access to pre-requisite training that must be completed prior to the onsite training course start date. • Confirm the readiness of all workstations at least two days prior to each onsite training course.
Training Methods and Procedures
Designated Motorola Instructors will provide application instruction using several techniques and materials, including the following:
• Instructor Lesson Plan -The instructor's tool for planning the detailed course content on a module-by-module basis.
• Training Course Agenda -The student handout that outlines the course sequence of events including duration, and course modules. • Worksheets, Job-Aids, Quizzes, retention instructional activities.
Exhibit A: Contract Documentation Requirements
94 PremierOne Cloud Training Plan Motorola Solutions G
May 10, 2022 Item #11 Page 474 of 604
DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7
9.4.4 9.4.5
City of Carlsbad, CA
February 16, 2022
• Training Course Objectives -The instructor's predefined course objectives.
These are provided for Train-the-Trainer classes only.
• Evaluations -On the final day of a training class, the students will be asked to complete an Instructor Evaluation form. They are optional forms and anonymity is acceptable.
• Certificates of Attendance -Students completing the on-site and online classes will receive Certificates of Attendance.
• Attendance Rosters -Customers will provide to the Motorola instructor a roster listing the names of training participants ten days prior to the start of the course.
Instructors will complete Attendance Rosters of actual participants for each day of training
• Motorola PremierOne User Documentation -An electronic copy of the applicable Motorola Reference Manuals and documentation will be provided prior to training.
• The Customer is responsible for duplicating and delivering manuals to participating students prior to class commencement.
Training Environment
PremierOne Cloud CAD and Mobile has a fully functional second environment that can be used for training if desired. This training environment will enable the Customer's trainers to provide on-going training. This training environment also allows training to continue without interruption of the real time operations. Use of the training environment is covered in the Train-the-Trainer classes.
PremierOne Cloud Records training will be completed in the pre-production environment prior to Go Live.
Session Attendance
Motorola is committed to providing a quality training experience and desires that the Customer receive the maximum benefit from each training session. Each training session has been sized to provide the optimal training environment that meets the needs of the students in relation to the complexity of the material being presented.
Given the nature of the material being presented and the intensity of the training, it is imperative that maximum course numbers not be exceeded.
In the event the number of students in attendance exceeds the published maximum number of students and the list of participants identified on the training roster, Motorola will take corrective action, ensuring the integrity of the session is maintained and the students' ability to learn is protected. Motorola corrective action may include:
• Delaying the start of training until the number of students in attendance is in line with the maximum number of students allowed for the session.
Exhibit A: Contract Documentation Requirements
f1' Motorola Solutions PremierOne Maintenance and Support Agreement 95
May 10, 2022 Item #11 Page 475 of 604
DocuSign Envelope ID: EE0000EC-819D-469F-887C-147E38CEAFF7 City of Carlsbad, CA
February 16, 2022
9.4.6 9.4.7
9.5 9.5.1
• Splitting the class into multiple sessions. In such a case, the Customer will be charged for multiple occurrences of the class plus additional expenses, including travel related expenses, incurred by Motorola Solutions. • Delaying the classroom training until the Prerequisite training has been completed in the LXP by each learner.
Learning experience Portal (LXP) Requirements
The LXP is accessed via Internet browser. Motorola will set up an individual instance of the LXP that provides autonomy to the agency.
Accounts to access the LXP are created for each learner using their email address.
All learners accessing LXP content must have an account in the LXP. A learner will need to have access to the internet via workstation, laptop, tablet, or smartphone to access learning. These may also be referred to as clients within the LXP.
Audio accompanies visual display; speakers or headsets for listening are recommended. Course assessment evaluations are also accessed online. Access to these evaluations in the classroom is suggested.
LMS Learner Subscription Package
Customer resources will have access to the LMS training materials during deployment and as long as the post-live subscription is maintained. Learner level subscriptions allow access to all materials available for the applications included in this Training Plan.
PREMIERONE CLOUD COURSE DETAILS
Training Course Classifications
Motorola Solutions offers virtual and Learning Management System (LMS) training for the PremierOne Cloud Suite. Customer resources will have access to the LMS training materials during deployment and as long as the post-live LMS subscription is maintained throughout the subscription term. LMS course content is regularly updated and new courses are made available to Customers on a regular basis. As such, Motorola will provide the Customer with a list of the most current LMS prerequisite courses at the time of project kickoff.
Training Course Classifications
LMS-P Students must complete LMS prerequisites before attending training.
LMS-C Training classes are entirely conducted via LMS on demand with no in- person training component.
Virtual Virtual instructor-led training.
Exhibit A: Contract Documentation Requirements
96 PremierOne Cloud Training Plan Motorola Solutions 0
May 10, 2022 Item #11 Page 476 of 604
DocuSign Envelope ID: EE0000EC-819D-469F-887C-147E3BCEAFF7 City of Carlsbad, CA
February 16, 2022
Training Course Classifications
Ill Training from an onsite instructor conducted at the Customer's facilities.
Exhibit A: Contract Documentation Requirements
0 Motorola Solutions PremierOne Maintenance and Support Agreement 97
May 10, 2022 Item #11 Page 477 of 604
DocuSign Envelope ID: EEOOOOEC-B190-469F-887C-147E3BCEAFF7 City of Carlsbad, CA
February 16, 2022
9.5.2 Training Course Descriptions
Table 9-1: Learning Management System Admin Overview
Learning Management System Admin Overview
Goal
Training
Classification
Training
Material
Duration
Participation
Class Size
Prerequisites
Environment
Setup
Provide training to add/modify users, run reports, and add/modify groups within the Learning Management Solution.
Virtual
Up to one hour in one business day.
Those responsible for the management of assigning and overseeing LMS-C and LMS-P training.
Maximum of two students.
• Knowledge of Customer Training Requirements.
• Provide Motorola with the names (first and last) and emails of Customer LMS administrator:
• Provide access to learningservices.motorolasolutions.com.
Each workstation or device used for LMS prerequisites must have an internet connection.
Exhibit A: Contract Documentation Requirements
98 PremierOne Cloud Training Plan Motorola Solutions G
May 10, 2022 Item #11 Page 478 of 604
DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7 City of Carlsbad, CA
February 16, 2022
Table 9-2: PremierOne Cloud CAD Provisioning Workshop
PremierOne Cloud CAD Provisioning Workshop
Goal
Training
Classification
Training
Material
Duration
Participation
Class Size
Prerequisites
Environment
Setup
Provide detailed instruction on Computer Aided Dispatch (CAD) provisioning data files.
• LMS-P.
• In-Person.
• PremierOne CAD/Mobile Provisioning Guide.
• Course Outline.
• Up to 32 hours.
• Online prerequisite training.
Those responsible for making the decisions on configuration options and have participated in the business process review.
Maximum of four students.
• LMS Prerequisite training courses
• Knowledge of current Mobile and CAD application and configuration and agency SOPs.
• Microsoft and ESRI proficiency as defined in the Prerequisites Section.
• One workstation for each participant.
• Each workstation or device used for LMS prerequisites must have an internet connection.
• CAD workstation for each participant with network connection to PremierOne Cloud CAD.
• Projector.
• White board (if possible).
• Microsoft Excel should be installed on at least one training workstation.
Exhibit A: Contract Documentation Requirements
CD Motorola Solutions PremierOne Maintenance and Support Agreement 99
May 10, 2022 Item #11 Page 479 of 604
DocuSign Envelope ID: EE0OO0EC-B19D-469F-887C-147E3BCEAFF7 City of Carlsbad, CA
February 16, 2022
Goal
Training
C lassificatio
n
Training
Material
Duration
Participatio
n
Class Size
Prerequisit
es
Environme
nt Setup
Table 9-3: PremierOne Cloud GIS Import Training
PremierOne Cloud GIS Import Training
This course offers the skills and practice necessary to use the PremierOne Import tool and create the required databases and mxd docs for CAD and Mobile. The module covers the use of the import tool to build the required File Geodatabase and load to SQL databases for the PremierOne system.
Virtual.
PremierOne GIS System Administrator Training Guide.
Up to 24 hours over three consecutive business days.
GIS personnel and GIS System Administrator(s).
Maximum of four students.
• Computer knowledge and PC skills including DOS and Microsoft Windows; and basic PC functionality.
• Completion of Windows tutorials or equivalent training. • Basic understanding of geographical data and proficient in the use of ArcGIS.
• One GIS workstation.
• Connection to the internet (to support screen share ability for virtual training). ·
Exhibit A Contract Documentation Requirements
100 PremierOne Cloud Training Plan Motorola Solutions Q
May 10, 2022 Item #11 Page 480 of 604
DocuSign Envelope ID: EEOOOOEC-B19D-469F-887C-147E3BCEAFF7 Goal
Training
Classification
Training
Material
Duration
Participation
Class Size
Prerequisite
s
Environment
Setup
Note
Table 9-4: PremierOne Cloud CAD Train the Trainer
PremierOne Cloud CAD Train the Trainer
Provide selected personnel with sufficient knowledge to support a comprehensive end user training program.
In-person.
• CAD User Guide.
• Course Outline.
• LMS refresher training courses.
• Up to 32 hours over four consecutive business days.
• Online prerequisite material.
City of Carlsbad, CA
February 16, 2022
Instructors who are responsible for the in house training of employees and for ongoing user training.
Maximum of 12 students.
• Knowledge of current CAD application and customer operations. • LMS Prerequisite training courses.
• Each workstation or device used for LMS prerequisites must have an internet connection.
• CAD workstation for each participant with network connection to PremierOne Cloud CAD.
• Projector.
• White board (if possible).
Allow two weeks from the end of train-the-trainer to the beginning of end user training to allow the customer to build site-specific documentation and outline for end user classes.
Exhibit A: Contract Documentation Requirements
f.D Motorola Solutions PremierOne Maintenance and Support Agreement 101
May 10, 2022 Item #11 Page 481 of 604
DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7 City of Carlsbad, CA
February 16, 2022
Goal
Training
Classification
Training
Material
Duration
Participation
Class Size
Prerequisite
s
Environment
Setup
Note
Table 9-5: PremierOne Cloud CAD End User Training
PremierOne Cloud CAD Train the Trainer
• I I -Provide selected personnel with functional knowledge of Cloud CAD features and functions.
• CAD User Guide.
• Course Outline.
• LMS refresher training courses.
• Up to 24 hours over three consecutive business days.
• Online prerequisite material.
Calltakers/Dispatchers.
Maximum of 12 students.
• Knowledge of current CAD application and customer operations. • LMS Prerequisite training courses.
• Each workstation or device used for LMS prerequisites must have an internet connection.
• CAD workstation for each participant with network connection to PremierOne Cloud CAD.
• Projector.
• White board ~if possible).
Allow two weeks from the end of train-the-trainer to the beginning of end user training to allow the customer to build site-specific documentation and outline for end user classes.
Exhibit A: Contract Documentation Requirements
102 PremierOne Cloud Training Plan Motorola Solutions G
May 10, 2022 Item #11 Page 482 of 604
DocuSign Envelope ID: EEOOOOEC-819D-469F-887C-147E3BCEAFF7 Table 9-6: PremierOne Mobile Provisioning Workshop
City of Carlsbad, CA
February 16, 2022
PremierOne Mobile Provisioning Workshop
Goal
Training
Classification
Training
Material
Duration
Participation
Class Size
Prerequisites
Environment
Setup
Provide detailed instruction on Mobile provisioning data files. • LMS-P.
• Virtual.
• PremierOne CAD/Mobile Provisioning Guide.
• Course Outline.
• Up to four (4) two-hour remote CheckPoint Meetings in accordance with the Project Schedule.
• Online prerequisite training.
Those responsible for making the decisions on configuration options and have participated in the business process review.
Maximum of four students.
• LMS Prerequisite training courses.
• Knowledge of current Mobile and CAD application and configuration and agency SOPs.
• Microsoft and ESRI proficiency as defined in the Prerequisites Section.
• One workstation for each participant.
• Each workstation or device used for LMS prerequisites must have an internet connection.
• CAD/Mobile workstation for each participant with network connection to PremierOne Cloud CAD/Mobile.
• Projector.
• White board (if possible).
• Microsoft Excel should be installed on at least one training workstation.
Exhibit A: Contract Documentation Requirements
CD Motorola Solutions PremierOne Maintenance and Support Agreement 103
May 10, 2022 Item #11 Page 483 of 604
DocuSign Envelope ID: EE0000EC-819D-469F-887C-147E3BCEAFF7 City of Carlsbad, CA
February 16, 2022
Table 9-7: PremierOne Mobile Client Installation Overview PremierOne Mobile Client Installation (Windows, Android, iOS) Overview
Goal
Training
Classificatio
n
Training
Material
Duration
Participatio
n
Class Size
Prerequisite
s
Environ men
t Setup
Provide selected personnel with sufficient knowledge to install PremierOne Mobile client software on Windows workstations and Android or iOS SmartDevices. For Windows, this includes prerequisite third-party software. If the customer desires, an imaging solution can be presented.
Approximately 1 to 2 hours of online training material specific to the installation environment operating system.
Given varying complexities associated with the operating system environment that will support the Mobile Client (Windows, Android, iOS) the PremierOne CAD Mobile Client Installation course duration can vary.
Motorola will advise which course applies to your specific installation.
IT staff who are responsible for installing the Mobile Client software.
N/A -Available to all LMS subscribers.
Knowledge of Microsoft operating systems and basic software installation practices.
Each workstation or device must have an internet connection to the LMS system.
Exhibit A: Contract Documentation Requirements
104 PremierOne Cloud Training Plan Motorola Solutions G
May 10, 2022 Item #11 Page 484 of 604
DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7 Goal
Training
Classification
Training
Material
Duration
Participation
Class Size
Prerequisite
s
Environment
Setup
Note
Table 9-8: PremierOne Mobile Train the Trainer
PremierOne Cloud Mobile Train the Trainer
City of Carlsbad, CA
February 16, 2022
Provide selected personnel with sufficient knowledge to support a comprehensive end user training program. Also includes overview of Aware features for Map viewer and Incident viewer on Android/iOS devices.
• LXP.
• PremierOne Mobile User Guide(s).
• Approximately four hours of material.
Instructors who are responsible for the in house training of employees and for ongoing user training.
In-person -Maximum of twelve students
LXP -Available to all LXP subscribers.
• Completion of LXP-C and LXP-P courses.
• Knowledge of current Mobile application (Windows, Android, and/or iOS) and customer operations.
Each workstation or device used for LXP prerequisites must have an internet connection.
Allow two weeks from the end of train-the-trainer to the beginning of end user training to allow the customer to build site-specific documentation and outline for end user classes.
Exhibit A: Contract Documentation Requirements
G Motorola Solutions PremierOne Maintenance and Support Agreement 105
May 10, 2022 Item #11 Page 485 of 604
DocuSign Envelope ID: EEOOOOEC-8190-469F-887C-147E38CEAFF7 City of Carlsbad, CA
February 16, 2022
Table 9-9: SSRS Report Builder Training in PremierOne CAD/Mobile Goal:
Training
Classification
Course
Materials:
Duration:
Participation:
Class Size:
Prerequisite:
Environment
Setup:
Provide selected personnel with knowledge on how to create custom reports against the PremierOne Reporting Data Warehouse (ROW) using Microsoft SQL Server Reporting Service (SSRS) and Report Builder software.
In-person.
SSRS Training Guide
Up to 24 hours over three consecutive business days
Personnel who will create custom reports
Maximum of six (6) students
Class participants must have some knowledge/experience of creating "on demand" reports.
Class participants should have experience working with relational database structures as well as writing and understanding transact SQL code.
Student Workstations:
• One (1) workstation for each attendee with a connection to the PremierOne system environment.
• The following is the current list of Operating Systems and Browsers supported for the web portal.
o Windows 7, 8.1, 10; Windows Server 2008 R2, 2012,
2012 R2
o Microsoft Edge(+) Preferred
o Microsoft Internet Explorer 1 O or 11
o Google Chrome(+)
o Mozilla Firefox(+)
• Microsoft SQL Server Reporting Services installed, configured, and working.
• Microsoft Report Builder installed.
Optional:
• SQL Server Management Studio on each Student Workstation • One (1) CAD Client for the class is preferred in the case data entry needs to take place in order to report against.
System Requirements:
• Data pre-exists in the Reporting Data Warehouse (data is typically propagated during the training courses.)
Instructional Requirements:
• Instructor's workstation(s) with network connection
• Projector
• White board (if possible)
Exhibit A: Contract Documentation Requirements
106 PremierOne Cloud Training Plan Motorola Solutions CZ.,
May 10, 2022 Item #11 Page 486 of 604
DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7 Goal
Training
Classification
Training
Material
Duration
Participation
Class Size
Prerequisite
s
Environment
Setup
Table 9-10. CommandCentral Aware End User Training
CommandCentral Aware End User Training
City of Carlsbad, CA
February 16, 2022
This course provides an overview and demonstrates all the features and functions of CommandCentral Aware. It consists of six comprehensive modules: Overview, Basic Operations, Map View, Event View, Video View,
and Radio Console View.
LXP-C (Computer Based)
• Online
• Approximately one hour.
Intelligence officer -crime analyst (badge or civilian) who is stationed at the
Aware workstation to monitor events in real time and assist those responding
with detailed information coming from many disparate data feeds into the
application as well as video and voice.
N/A -Available to all LXP subscribers.
• None
Each workstation or device used for LXP must have an internet connection.
Exhibit A: Contract Documentation Requirements
G Motorola Solutions PremierOne Maintenance and Support Agreement 107
May 10, 2022 Item #11 Page 487 of 604
DocuSign Envelope ID: EE0000EC-B19O-469F-887C-147E3BCEAFF7 City of Carlsbad, CA
February 16, 2022
Goal
Training
Classification
Training
Material
Duration
Participation
Class Size
Prerequisite
s
Environment
Setup
Note
Table 9-11: CommandCentral Aware Workshop
CommandCentral Aware Workshop
Understand the functionality of applications that comprise CommandCentral Aware. Operate CommandCentral Aware
applications. Use the administrative tools to manage the applications that comprise CommandCentral Aware.
Virtual Instruction
• Online
• 24 hours total covering two sections
• Operator Section: Aware position operators (Primary) System Administrators (Secondary)
• Administration Section: System Administrators/Managers • None
Each workstation or device used for LXP prerequisites must have an internet connection.
The CommandCentral Aware Workshop course consists of several modules to address Customer training needs for the Aware solution.
This training provides information on the general Aware interface including video, messaging, mapping, and radio consoles as well as modules that address the optional applications found in the Aware solution. This course is divided into two sections: one to address the needs of customer system administrators and the second to train operators of the Aware position. The administrator content covers the information necessary to manage user, camera, reports, and other tasks that are necessary to administer the Aware solution. The operator content covers the controls and functionality of the various applications that make up the Aware solution to allow users to make the most effective use of their Aware positions.
Exhibit A: Contract Documentation Requirements
108 PremierOne Cloud Training Plan Motorola Solutions G
May 10, 2022 Item #11 Page 488 of 604
DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7 Table 9-12: CommandCentral Analytics End User
City of Carlsbad, CA
February 16, 2022
CommandCentral Community Digital Evidence Collection
Goal
Training
Classification
Training
Material
Duration
Participation
Class Size
Prerequisite
s
Environment
Setup
Configure and effectively provide dashboard data, conduct searches using Advanced Person Search. View search results using Map, Data Grid, Link Analysis, apply filters to the Data Grid.
LXP-C (Computer Based)
• Online
• 1 hour
Users who are responsible for accessing data to create dashboard analytics.
N/A -Available to all LXP subscribers.
• None
Each workstation or device used must have an internet connection.
Exhibit A: Contract Documentation Requirements
G Motorola Solutions PremierOne Maintenance and Support Agreement 109
May 10, 2022 Item #11 Page 489 of 604
OocuSign Envelope ID: EEOOOOEC-8190-469F-887C-147E3BCEAFF7 City of 9arlsbad, CA
February 16, 2022
Table 9-13: OPTION -CommandCentral Community Digital Evidence Collection CommandCentral Community Digital Evidence Collection
Goal
Training
Classification
Training
Material
Duration
Participation
Class Size
Prerequisite
s
Environment
Setup
Generate a QR code or link to enable public submission of case digital media, view submitted evidence in TipManager, edit evidence in CommandCentral Evidence, add or remove the agency from the public- facing application.
LXP-C (Computer Based)
• Online
• 0.25 hours
Users who are responsible for receiving, viewing, and collecting digital evidence from public sources.
N/A -Available to all LXP subscribers.
• None
Each workstation or device used for LXP access must have an internet connection.
Table 9-14: OPTION -WatchGuard 4RE and V300 End-User Training WatchGuard 4RE and V300 End-User Training
Goal
Training
Classification
Training
Material
Duration
Participation
Class Size
Prerequisite
s
Environment
Setup
• • ·-Configure and effectively understand how to use the system on a daily basis and how to use.the 4RE/M500 and/or V300 during a shift. •• -
• Online
• V300 Basic 30 minutes, V300 Full 45 minutes
•
• None
Each workstation or device used must have an internet connection if accessing the online training.
Exhibit A: Contract Documentation Requirements
110 PremierOne Cloud Training Plan Motorola Solutions G
May 10, 2022 Item #11 Page 490 of 604
DocuSign Envelope ID: EE0000EC-B19O-469F-887C-147E3BCEAFF7 SECTION 10
PREMIERONE
MAINTENANCE AND
SUPPORT AGREEMENT
City of Carlsbad, CA
February 16, 2022
This Maintenance and Support Agreement (the "Agreement") is entered into between Motorola Solutions, Inc., with offices at 500 W. Monroe Street, Suite 4400, Chicago, IL ("Motorola") and the entity set forth in the signature block below("Customer"). Motorola and Customer will each be referred herein as a "Party" and collectively as the "Parties". This Agreement is effective as of the date of the last signature (the "Effective Date")
For good and valuable consideration, the Parties agree as follows:
Section 1 EXHIBITS
The Exhibits listed below are incorporated into and made a part of this Agreement. In interpreting this Agreement and resolving any ambiguities, the main body of this Agreement will take precedence over the Exhibits and any inconsistency between the Exhibits will be resolved in the order in which they are listed below.
Exhibit A
Exhibit B
"PremierOne Cloud Service Customer Support Plan"
"Labor Rates"
Section 2 DEFINITIONS
"Equipment" means the physical hardware purchased by Customer from Motorola pursuant to a separate System Agreement, Products Agreement, or other form of Agreement. "Motorola" means Motorola Solutions, Inc., a Delaware corporation. "Motorola Solutions Software" means Software that Motorola owns and is covered in this Maintenance and Support Agreement.
"Non-Motorola Solutions Software" means Software that a Third Party other than Motorola owns. "Optional Technical Support Services" means fee-based technical support services that are not covered as part of the standard Technical Support Services.
"Patch" means a specific change to the Software that does not require a Release. "Products" means the Equipment (as indicated in the Covered Products Exhibit) and Software provided by Motorola.
Exhibit A: Contract Documentation Requirements
G Motorola Solutions PremierOne Maintenance and Support Agreement 111
May 10, 2022 Item #11 Page 491 of 604
DocuSign Envelope ID: EE0000EC-819D-469F-887C-147E3BCEAFF7 City of Carlsbad, CA
February 16, 2022
"Product Release" means the release of Motorola Software considered to be the next generation of an existing product or a new product offering.
"Releases" means an Upgrade to the Motorola Software.
"Residual Error" means a software malfunction or a programming, coding, or syntax error that causes the Software to fail to conform to the Specifications.
"Services" means those maintenance and support services described in the Customer Support Plan Exhibit and provided under this Agreement.
"Software" means the Motorola Solutions Software and Non-Motorola Solutions Software (Third Party) that is furnished with the System or E·quipment.
"Specifications" means the design, form, functionality, or performance requirements described in published descriptions of the Software, and if also applicable, in any modifications to the published specifications as expressly agreed to in writing by the parties.
"Standard Business Day" means Monday through Friday, 8:00 a.m. to 5:00 p.m. local time, excluding established Motorola holidays.
"Standard Business Hour" means a sixty (60) minute period of time starting at notification within a Standard Business Day(s).
"Start Date" means the date upon which this Agreement begins. The Start Date is specified in the Covered Products, Support Options and Pricing Exhibit.
"System" means the Products and Services provided by Motorola as a system and are more fully described in the Technical and Implementation Documents attached as Exhibits to the applicable system agreement between Customer and Motorola.
"Technical Support Services" means the remote support provided by Motorola on a standard and centralized basis concerning the Covered Products, including diagnostic services and troubleshooting to assist the Customer in ascertaining the nature of a problem being experienced by the Customer. Technical Support Services includes minor assistance concerning the use of the Software (including advising or assisting the Customer in attempting data/database recovery, database set up, client-server advice), and minor assistance or advice on installation of Releases provided under this Agreement. "Upgrade" means the process of installing the latest or generally available version of the installed solution product.
Section 3 SCOPE AND TERM OF SERVICES
3.1. In accordance with the provisions of this Agreement and in consideration of the payment by Customer of the price for the Services, Motorola will provide to the Customer the Services as described in the Customer Support Plan Exhibit
3.2. The term of this Agreement is six (6) years, beginning on the Start Date. Following the initial term period, this Maintenance and Support Agreement will automatically renew upon the anniversary date for successive one (1) year periods unless either party notifies the other of its intention to not renew the Agreement (in whole or part) not less than thirty (30) days before the anniversary date or requests an alternate term or this Agreement is terminated for default by a·party.
Exhibit A: Contract Documentation Requirements
112 PremierOne Maintenance and Support Agreement Motorola Solutions G
May 10, 2022 Item #11 Page 492 of 604
DocuSign Envelope ID: EEOOOOEC-B19D-469F-887C-147E3BCEAFF7 City of Carlsbad, CA
February 16, 2022
3.3. This Agreement covers all copies of the specified Products listed in the Ordering Documents that are subscribed to from Motorola to the Customer. If the price for SeNices is based upon a per unit fee, such price will be calculated on the total number of units of the Products that are licensed to Customer as of the beginning of the maintenance and support period. If, during a maintenance and support period, Customer acquires additional Products that will be covered by this Agreement, the price for maintenance and support seNices for the additional Products will be calculated and added to the total price either (1) if and when the maintenance and support period is renewed or (2) immediately when Customer acquires additional Products, as determined by Motorola. Motorola may adjust the price of the maintenance and support seNices at the time of a renewal if it provides to Customer notice of the price adjustment at least forty-five (45) days before the expiration of the maintenance and support period. If Customer notifies Motorola of its intention not to renew this Agreement as permitted by Section 3.2 and later wishes to reinstate this Agreement, it may do so with Motorola's consent provided (a) Customer pays to Motorola the amount that it would have paid if Customer had kept this Agreement current, (b) Customer ensures that all applicable Equipment is in good operating conditions at the time of reinstatement, and (c) all copies of the specified Software listed in the Description of Covered Products are covered.
3.4. When Motorola performs SeNices at the location of installed Products, Customer agrees to provide to Motorola, at no charge, a non-hazardous environment for work with shelter, heat, light, and power, and with supeNised access to the covered Products. Customer will provide all information pertaining to the hardware and software with which the Products are interfacing to enable Motorola to perform its obligations under this Agreement.
3.5. All Customer requests for covered SeNices will be made initially with the call intake center identified in the Customer Support Plan.
3.6. Motorola will provide to the Customer Technical Support SeNices and Releases as follows:
3.6.1. Motorola will provide Technical Support SeNices and correction of Residual Errors during the term of the subscription in accordance with the Customer Support Plan. Any Technical Support SeNices that are performed by Motorola outside the scope of this Agreement and the Customer Support Plan will require prior City approval and be billed at the then current hourly rates. The objective of Technical Support SeNices will be to investigate specifics about the functioning of covered Products and to determine whether there is a defect in the Product. Technical Support SeNices will not be used in lieu of training on the covered Products.
3.6.2. Motorola will provide to Customer without additional subscription fees an available software update/upgrade for the specified Products listed in the Ordering Documents. Software updates, as defined in the Customer Support Plan, are designed to be delivered remotely. SeNices for onsite delivery requested by Customer will be quoted at the time of the request.
3.6.3. Motorola will provide to Customer an available Product Release after receipt of a request from Customer, but Customer must pay for all additional license and/or subscription fees, any onsite installation or other seNices, and any necessary Equipment provided by Motorola in connection with such Product Release. Motorola's duty as described in this paragraph is contingent upon Customer's then- current installation at the time of Customer's request being within two (2) Standard Release versions of the new Standard Release available for general release. Any seNices will be performed in accordance with a mutually agreed schedule.
3.6.4. Along with Software updates to the Products listed in the Ordering Documents, Motorola will make available new purchasable products, features and modules which are separate and distinct from the mainstream Motorola Solutions Software line of Products. Newly released Products may have PremierOne subscriptions as a pre-requisite and/or share some portion of the PremierOne code base. Customers are not entitled to these products, features and modules, or upgrades to them within this Exhibit A Contract Documentation Requirements
f» Motorola Solutions PremierOne Maintenance and Support Agreement 113
May 10, 2022 Item #11 Page 493 of 604
DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7 City of Carlsbad, CA
February 16, 2022
Maintenance and Support Agreement, if they have not purchased the required subscriptions and/or licenses.
3.6.5. As part of the Software development process Motorola makes every reasonable effort to lessen impact to customer operations. Any change to existing functionality is done after thorough review of customer feedback and with announcement of said change. When it's not technically feasible to meet a particular requirement Motorola will proactively communicate the changes. Beyond these efforts Motorola does not warrant that a Release will meet Customer's particular requirement, be uninterrupted or error-free, be backward compatible, or that all errors will be corrected. Errors addressed as part of the Software Release will be corrected. Full compatibility of a Release with the capabilities and functions of earlier versions of the Software may not be technically feasible. If it is technically feasible, Motorola will make available services to integrate these capabilities and functions to the upgraded version of the Software, which services may be fee based.
3. 7. The maintenance and support Services described in this Agreement are the only covered services.
Unless optional or a la carte Technical Support Services are purchased, these Services specifically exclude and Motorola will not be responsible for:
3.7.1. Any service work required due to incorrect or faulty operational conditions, including but not limited to Equipment not connected directly to an electric surge protector, or not properly maintained in accordance with the manufacturer's guidelines. Other services may be available for an additional fee and will be addressed with an amendment to the Agreement.
3.7.2. The repair or replacement of Products or parts resulting from failure of the Customer's facilities, Customer's personal property and/or devices connected to the System (or interconnected to devices) whether or not installed by Motorola's representatives.
3.7.3. The repair or replacement of Equipment that has become defective or damaged due to physical or chemical misuse or abuse, Customer's negligence, or from causes such as lightning, power surges, or liquids.
3.7.4. Any transmission medium, such as telephone lines, computer networks, or the ISP, or for Equipment malfunction caused by such transmission medium.
3.7.5. Accessories, custom or Special Products; modified units; or modified Software.
3.7.6. The repair or replacement of parts resulting from the tampering by persons unauthorized by Motorola or the failure of the System due to extraordinary uses.
3.7.7. Operation and/or functionality of Customer's personal property, equipment, and/or peripherals and any application software not provided by Motorola.
3.7.8. Services for any replacement of Products or parts directly related to the removal, relocation, or reinstallation of the System or any System component.
3.7.9. Services to diagnose technical issues caused by the installation of unauthorized components or misuse of the System.
3.7.10. Services to diagnose malfunctions or inoperability of the Software caused by changes, additions, enhancements, or modifications in the Customer's platform or customer provided software.
3. 7.11. Services to correct errors found to be caused by Customer-supplied data, machines, or operator failure.
Exhibit A: Contract Documentation Requirements
114 PremierOne Maintenance and Support Agreement Motorola Solutions 4'
May 10, 2022 Item #11 Page 494 of 604
DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7 City of Carlsbad, CA
February 16, 2022
3.7.12. Operational supplies, including but not limited to, printer paper, printer ribbons, toner, photographic paper, magnetic tapes and any supplies in addition to that delivered with the System; battery replacement for uninterruptible power supply (UPS); office furniture including chairs or workstations.
3. 7 .13. Third-party software unless specifically listed on the Covered Products Exhibit.
3.7.14. Support of any interface(s) beyond Motorola-provided port or cable, or any services that are necessary because third party hardware, software or supplies fail to conform to the specifications concerning the Products.
3.7.15. Services related to customer's failure to use a UPS system to protect against power interruptions as related to their on-premise equipment.
3.7.16. Any design consultation such as, but not limited to, configuration analysis, consultation with Customer's third-party provider(s), and System analysis for modifications or Upgrades which are not directly related to a Residual Error report.
3.8. The Customer hereby agrees to:
3.8.1. Maintain any and all electrical and physical environments in accordance with the System manufacturer's specifications.
3.8.2. Provide standard industry precautions (e.g. back-up files) ensuring database security, per Motorola's recommended backup procedures.
3.8.3. Ensure System accessibility, which includes physical access to buildings as well as remote electronic access. Remote access can be stipulated and scheduled with the Customer; however, remote access is required and will not be substituted with on-site visits or proxies if access is not allowed or available.
3.8.4. Appoint one or more qualified employees to perform System Administration duties, including acting as a primary point of contact to Motorola's Technical Support organization for reporting and verifying problems. At least one member of the System Administrators group must have completed Motorola's End-User training and System Administrator training (if available). The combined skills of this System Administrators group includes proficiency with: the Products, the system platform upon which the Products operate, the operating system, database administration, network capabilities such as backing up, updating, adding, and deleting System and user information, and the client, server and stand alone personal computer hardware. The System Administrator will follow the Residual Error reporting process described herein and make all reasonable efforts to duplicate and verify problems and assign a Severity Level according to definitions provided herein. Customer agrees to use reasonable efforts to ensure that all problems are reported and verified by the System Administrator before reporting them to Motorola.
Customer will assist Motorola to confirm that errors are not the product of the operation of an external system, data links between system, or network administration issues. If a Severity Level 1 or 2 Residual Error occurs, any Customer representative may contact Motorola's Customer Support by telephone, but the System Administrator must follow up with Motorola's Customer Support as soon as practical thereafter.
A full list of customer system management responsibilities is provided in the Customer Support Plan section
5.2. 3.9. Intentionally deleted.
3.10. Customer will permit and cooperate with Motorola so that Motorola may periodically conduct audits of Customer's records and operations pertinent to the Services, Products, and usage of application and database management software. If the results of any such audit indicate that price has been understated, Exhibit A: Contract Documentation Requirements
CD Motorola Solutions PremierOne Maintenance and Support Agreement 115
May 10, 2022 Item #11 Page 495 of 604
DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7 City of Carlsbad, CA
February 16, 2022
Motorola will review their findings with the Customer and, if the results are supported by this review, may correct the price and immediately invoice Customer for the difference (as well as any unpaid but owing license fees).
3.11. If Customer replaces, upgrades, or modifies equipment, or replaces, upgrades, or modifies hardware or software that interfaces with the covered Products, Motorola will notify the Customer of of any price adjustments required for the new configuration.
3.12. Customer agrees not to attempt or apply any upgrades(s), alteration(s), or change(s) to the database software without the prior approval of Motorola.
Section 9. CERTIFICATION DISCLAIMER
Motorola specifically disclaims all certifications regarding the manner in which Motorola conducts its business or performs its obligations under this Agreement, unless such certifications have been expressly accepted and signed by an authorized signatory of Motorola.
Section 10. COMPLIANCE WITH APPLICABLE LAWS
The Parties will at.all times comply with all applicable regulations, licenses and orders of their respective countries relating to or in any way affecting this Agreement and the performance by the Parties of this Agreement. Each Party, at its own expense, will obtain any approval or permit required in the performance of its obligations. Neither Motorola nor any of its employees is an agent or representative of Customer.
IN WITNESS WHEREOF, the Parties have caused this Agreement as of the Effective Date.
MOTOROLA SOLUTIONS, INC. CUSTOMER
By: 7~ By: ________ _
Name: Micah Applewhite Name: _____________ _
Title: MSSSI Vice President & Director Sales Title: --------------- Date: May 5, 2022 Date: ---------------
Exhibit A: Contract Documentation Requirements
116 PremierOne Maintenance and Support Agreement Motorola Solutions G
May 10, 2022 Item #11 Page 496 of 604
DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7 City of Carlsbad, CA
February 16, 2022
Exhibit A -Customer Support Plan
QUICK CONTACTS
Toll Free Phone#
-
Email
Motorola Portal
Provide the following information:
Service Agreement Information
Customer Name: ·
Service Agreement Start/End Date:
Customer Success Advocate Contact
Name
Phone
Cellular
Email
Exhibit A: Contract Documentation Requirements
0 Motorola Solutions
I SUPPORT CENTER
------·--
1-800-MSI-HELP (1-800-674-4357)
Option 4,2,2 CAD
Option 4,4,2 RMS
[email protected]
MyView Portal
1. Site Name
2. Your Name
3. Your Call Back Number I
4. A Brief Description of the Problem
I Severity (Critical, High, Medium, Low)
I
I
PremierOne Maintenance and Support Agreement 117
May 10, 2022 Item #11 Page 497 of 604
DocuSign Envelope ID: EE0000EC-819D-469F-887C-147E3BCEAFF7 City of Carlsbad, CA
February 16, 2022
ESCALATION PLAN
Our goal is to ensure our customers receive the best possible support from Motorola Solutions, Inc. (Motorola). If you feel that your support needs are not being met, as a direct customer,. we provide an escalation process for your request to the next department or manager.
Your initial call should always be to the first department or person on the list above. If, after making this initial contact you still have unresolved issues, please see below for escalation contact information.
ESCALATION CONTACT
Level 1 Level 2 Level 3
SUPPORT CENTER
DON JACKSON
Manager, Technical Support
Mobile: (720) 355-1183
Don.Jackson [email protected]
Assigned CSA
JOSH HOWELL
Senior Manager, Technical
Support
Mobile: (616) 540-4103
Josh.Howell@motorolasolutions.
Ell!
Assigned CSM
Exhibit A: Contract Documentation Requirements
118 PremierOne Maintenance and Support Agreement
JEREMY SMITH
Head of Software Enterprise
Centralized Managed & Support
Operations
Mobile: (951) 216-8827
[email protected]
Motorola Solutions G
May 10, 2022 Item #11 Page 498 of 604
DocuSign Envelope ID: EEOOOOEC-B19D-469F-887C-147E3BCEAFF7
10.1 SUPPORT PLAN SUMMARY
10.1.1 Introduction -Serving Our Customer's Needs
City of Carlsbad, CA
February 16, 2022
Motorola is committed to helping people be their best in the moments that matter. We appreciate the opportunity to provide support pursuant to this "Support Plan," and our service delivery teams are focused on the health, service performance and reliability of the PremierOne Cloud Service ("PremierOne Cloud Service"). Your PremierOne Cloud Service Support Plan will be amended from time to time to align with industry best practices and customer needs.
10.1.2 Service Management Overview -PremierOne Cloud Services Motorola's Subscription Support Services provides support delivered through a combination of centralized resources within Motorola's SSC collaborating with product development resources that are experienced in managing mission critical services and associated technologies. The SSC operates 24 x 7 x 365, leveraging remote access to customer services for complete resolution methpds.
Service management and open communication is the key to effective service delivery and relationship building. Our Motorola services program offers end-to-end service management and includes:
• Software Support
• Motorola System Support Center
In addition to the support services provided by the SSC, a Customer Success Advocate ("CSA") will be assigned to partner with the support team in the System Support Center ("SSC") to help agencies maximize use of their software and services investment as their trusted advisors. The CSA will partner with you to ensure that the transition from implementation to service is smooth and will be available to answer questions that may arise outside of your standard agency service experience. CSAs partner with customers to drive adoption, identify goals and objectives for use of the product and engaging in an ongoing customer communication about progress toward desired outcomes, relationship timelines and next steps. CSAs provide ongoing, active engagement with an agency from deployment through renewal or expansion to maximize usage, value and product satisfaction.
Our goal is to build an outcome driven relationship that ensures your agency maximizes the value of your software investment.
The Support Plan covers the following customer locations: ~-•· r~efilled in ost-contract 1■:MUGFll•!II• Exhibit A: Contract Documentation Requirements
CD Motorola Solutions
~ift1£6l11I·
I
--_ =tiWGMi¥
I
PremierOne Maintenance and Support Agreement 119
May 10, 2022 Item #11 Page 499 of 604
DocuSign Envelope ID: EE0000EC-819D-469F-887C-147E3BCEAFF7 City of Carlsbad, CA
February 16, 2022
10.2 MOTOROLA SYSTEMS SUPPORT CENTER
If you experience problems with PremierOne Cloud Service, you have several options to get help with determi_ning the cause of the problem and finding a solution. The SSC is the central point of contact to report PremierOne Cloud Service incidents and submit change requests. The SSC can be reached 24/7 to assist with your service needs via:
■ Toll Free Telephone: 1-800-MSI-HELP (1-800-674-4357)
-Option 4,2,2 CAD
-Option 4,4,2 RMS
• MyView_Portal: low priority requests only, 24-hour turn around • Email: [email protected] (24-hour turnaround) NOTE: Critical and high priority incidents should not be reported via email or MyView Portal.
Product and service technical resources are ready to receive and take action on requests for service.
The SSC will:
■ Open a ticket and categorize the reported issue or request ■ Resolve incidents based on priority
■ Perform analysis to assist in identifying a corrective action plan ■ Escalate the incident/request to technical or service experts when required ■ Engage the next level management to ensure timely problem resolution, when necessary
■ Provide regular status updates for escalated incidents Motorola's primary objective is to restore PremierOne Cloud Service to normal operations as quickly as possible and minimize the adverse impact of service events on our customers and their mission. This serves our primary goal of maintaining the highest possible quality of service and availability. The PremierOne Cloud Service team of highly skilled, knowledgeable and experienced specialists are available to the customer as an integrated part of the support and technical issue resolution process.
All customer requests for service change requests are tracked centrally in Motorola's IT Service Management (ITSM) Toolset, resulting in a ticket number. All SSC support activity that occurs after the cutover of the service into production is tracked in this service to ensure consistent visibility of all activities.
Exhibit A: Contract Documentation Requirements
120 PremierOne Maintenance and Support Agreement Motorola Solutions G
May 10, 2022 Item #11 Page 500 of 604
DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7 City of Carlsbad, CA
February 16, 2022
All calls requiring incidents or service requests are assigned a severity in accordance with the agreed "Severity Level Response" table below. Via the ITSM, Motorola will track the progress of each ticket from initial capture to resolution. Motorola will advise and inform the customer of the ticket progress and tasks that require further investigation and assistance from the customer's technical resources.
Upon notification of the incident, the SSC will supply a ticket number for reference. For each reported or alert generated the SSC will apply a Severity Level classification, which has an assigned target response time objective. This classification provides the means to manage the appropriate response and engagement processes.
10.2.1 Reporting Incidents Using the Toll-free Number
The SSC is staffed with trained technicians who remotely access your PremierOne Cloud Service to begin troubleshooting. For accurate reporting and ticket tracking, all PremierOne Cloud Service issues are reported to the SSC.
At a minimum, when above, the SSC will require:
■ Customer name (Site)
■ Caller's name
• Caller's contact number (supply alternate call back number) ■ Description of the problem or request
■ Operational impact of the problem (Severity)
1.1 Severity Level and Response Definitions
Reporting Trouble -The SSC number is provided to all customers for PremierOne Cloud Service issues. If the issue cannot be resolved through our remote diagnostics by the SSC, then the customer technician will be required to report on-site within the above stated response times.
Response Time -The amount of time expired between the time in which the issue is reported to SSC by the customer to the time that a qualified technician is actively troubleshooting the issue.
Note: Business Days is defines as Monday -Friday excluding holidays Business Hours is defined as Monday -Friday 8am -5pm local time Incident Time -The period of time during which the service or any service component suffers an Incident. Incident Time shall commence upon either the issue is reported to the SSC by the customer. Incident Time shall end upon completion of the repair or restoration of the service or service component. Incident Time shall not include downtime attributable to (a) Force Majeure conditions (as defined in the applicable agreement); or (b) scheduled preventive maintenance that the customer was notified and consented to in advance.
Exhibit A: Contract Documentation Requirements
G Motorola Solutions PremierOne Maintenance and Support Agreement 121
May 10, 2022 Item #11 Page 501 of 604
DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7 City of Carlsbad, CA
February 16, 2022
10.2.2 Severity Response Table
SEVERITY DEFINITION
LEVEL
1 An incident is deemed CRITICAL if one or
Critical multiple critical functions are unavailable or severely degraded such that the customers'
core business functions and capabilities are no
longer delivered or capable. The resulting
critical impact to the customers' business is
such that focus and resources must be applied
to restoration or mitigation
Data has stopped showing in the application or
users are no longer able to access the product
due to a system-wide outage
2 An incident is deemed HIGH if a business
High function is unavailable and normal customer
business activity is impacted or degraded, and
a workaround may be available to mitigate the
effects of the service impact; however overall
efficiency or effectiveness is degraded. This
may apply to both critical and non-critical
functions.
Recoverable application crash, All data
inaccessible (e.g. videos inaccessible, missing
incidents).
3 An incident is deemed MEDIUM if business
Medium functions are available, however, there is a
deviation from the expected or agreed upon
level of service or other service condition not
aligned with the other defined impact levels.
Data missing; (e.g. incomplete video
thumbnails, inconsistent incident population)
4 Technical Requests -This level is meant for
Low the request for information or set of actions
regarding product or service functionality,
features and capabilities. This level is meant to
represent minor issues, such as cosmetic
issues, documentation errors, general usage
questions, configuration questions and product
or service Update requests.
RESPONSE TIME
Telephone conference
within 1 Hour of initial
voice notification
Telephone conference
within 3 Hours of initial
voice notification
during normal
business hours
Telephone conference
within 8 Hours of initial
notification during
normal business hours
Telephone conference
within 2 Business
Days of initial
notification
The customer will provide a properly trained resource who is familiar with the operation of that service that will be responsible for the administration of the PremierOne Cloud Service.
Motorola will provide remote technical consultants to support the local resource in the timely closure of performance and operational issues.
Exhibit A: Contract Documentation Requirements
122 PremierOne Maintenance and Support Agreement Motorola Solutions CD
May 10, 2022 Item #11 Page 502 of 604
DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7 City of Carlsbad, CA
February 16, 2022
10.3 CUSTOMER CONTACTS FOR NOTIFICATION
The designated personnel noted below will be the customer contacts for notification of a Critical Incident and/or for technical consultation.
Customer will be notified of any scheduled/planned maintenance that will result in a customer outage at least 7 days prior to the scheduled maintenance.
CONTACTS AND NOTIFICATIONS
SITE CONTACT NAME: I
Main Phone Number for Site:
Used when needing to speak with Site:
Motorola Contact Name Email Phone Number
-Customer Contact Names Email Phone Number
After Hours Contact Names >--Email Phone Number
10.4 CASE MANAGEMENT VIA MYVIEW PORTAL
The MyView Portal provides you an interface into our "Incident Management System". MyView Portal gives you valuable service and service information whenever you need it along with complete support tickeUincident management from submission to close.
MyView Portal provides the ability to:
• Create low priority tickets
■ Obtain status updates on existing tickets
• Supply additional information on tickets 24/7
• When updating ticket notes, please provide contact information, which includes phone number, email, etc.
Motorola does not recommend using this tool for openir)g Severity 1 or 2 tickets. To report any critical issues or to update current tickets with critical information customers should contact the SSC by calling 1-800-MSI-HELP (800-647-4357).
Exhibit A: Contract Documentation Requirements
G Motorola Solutions PremierOne Maintenance and Support Agreement 123
May 10, 2022 Item #11 Page 503 of 604
DocuSign Envelope ID: EE0000EC-819D-469F-887C-147E38CEAFF7 City of Carlsbad, CA
February 16, 2022
10.4.1 Ticket Initiation via Email
10.5 An alternative customer support tool is available for PremierOne Cloud Service Customers.
Along with the toll-free phone number and MyView Portal, customers can request technical support by email. For many customers who use their handheld device as a means to open tickets, email provides additional flexibility for initiating tickets.
To ensure proper ticket management and contractual response, email ticketing is only available for severity levels 3 or 4. In order to process a ticket via email, the email must be formatted exactly as described below:
1. Address emails to: [email protected]
2. Email Subject: Type "PSA Service Requesf' and a brief description of the service issue (this will become the ticket title).
3. Use the following template for the body of the email. Copy and paste from below, adding in the accurate and specific information of the request following the bold items listed:
-Site ID: Site ID
-Product Type: Choose from the following list:
♦ PremierOne Cloud CAD
♦ PremierOne Mobile for Cloud CAD
♦ Command Central Jail
-Contact First Name: first name or the name of the person you would like support personnel to contact
-Contact Last Name: last name or the name of the person you would like support personnel to contact.
-Phone Number: the area code and phone number where the contact person may be reached
-Severity Level: only for severity level 3 or 4.
♦ Note: All severity level 1 or 2 tickets must be opened via the toll- free SSC number
-Problem Description: a comprehensive description of the problem
4. Once the email has been sent, the customer will receive an email with the ticket numb~r for future reference. If an email response is not received, or if you need to open a severity level 1 or 2 ticket, please contact the toll-free SSC number.
CUSTOMER RESPONSIBILITIES FOR SUPPORT
The customer will provide a properly trained technical resource responsible for administration of your PremierOne Cloud Service, and familiar with your operations.
The on-site resources are to supply suitably skilled and trained on-site presence when requested by the SSC. They will validate issue resolution prior to close of the ticket in a timely manner.
Customer's on-site support personnel are responsible for the following:
Exhibit A: Contract Documentation Requirements
124 PremierOne Maintenance and Support Agreement Motorola Solutions 0
May 10, 2022 Item #11 Page 504 of 604
DocuSign Envelope ID: EE0000EC-819D-469F-887C-147E3BCEAFF7 City of Carlsbad, CA
February 16, 2022
1. Initiate Service Request: Contact Motorola through authorized tools and processes outlined in this Support Plan to initiate a technical support request ticket.
2. Work with Motorola to troubleshoot and validate resolution for any reported issues.
3. Assess Severity Level: Assist in assessing and assigning the initial and the correct severity level per the severity level definitions found in the Support Plan.
4. Escalate Appropriately: Contact Motorola to add information or make changes to existing technical support tickets or escalate service requests to Motorola management.
Motorola Services management contact information is provided in this Support Plan.
5. Maintenance on Hardware: Customer will provide all on-site hardware maintenance and service for all hardware not provided by Motorola. Customer will be responsible for purchasing on-going maintenance for third-party on-site hardware support for all hardware. Third party support on some system components may be available through the Maintenance and Support Agreement. Customer will contact the appropriate vendor directly for parts and hardware service, if not purchased through the Maintenance and Support Agreement.
6. Perform periodic reboots and ongoing performance tuning, hardware upgrades, and resource optimizations as required.
7. ISP and VPN connectivity: Provide ISP and VPN connectivity and telephone access to Motorola personnel as defined in the service description addendum to the subscription agreement.
8. Provide and maintain customer Azure subscription and services needed for integration with the PremierOne Cloud Service. At a minimum, the customer will maintain authorized users in the agency Azure Active Directory and enable SSO federation by PremierOne Cloud Service to the agency Azure Active Directory for the purpose of user authentication.
9. User Local Device/Workstation Maintenance: Apply upgrades such as OS patches, administrative tools and utilities.
10. Maintain and upgrade software that supports infrastructure applications (IE, Esri, etc.). 11 . Upgrade and maintain antivirus software, appropriately configure and maintain exclusion list.
12. Configure and maintain all products relevant to mobile network connectivity (NetMotion, Verizon, VPN related products, etc.).
13. CAD Customer Install: When directed by Motorola and under Motorola guidance install Motorola provided Citrix updates.
14. Mobile Customer Install: Install, upgrade, and test PremierOne Software Updates.
15. GIS Updates: PremierOne Map Maintenance
-Apply mapping and GIS data updates as needed.
-Ensure validity and integrity of all GIS related data introduced to the service -Record modifications made to GIS files, and confirm expected behavior within the PremierOne service .
-Distribute updated map files to Mobile customers
Exhibit A: Contract Documentation Requirements
4' Motorola Solutions PremierOne Maintenance and Support.Agreement 125
May 10, 2022 Item #11 Page 505 of 604
DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7 City of Carlsbad, CA
February 16, 2022
10.6 16. Anti-Virus and Windows UAC: Install, configure, and upgrade chosen anti-virus software. Appropriately configure user account control settings in a manner that ensures the files are accessible for service stability and successful operation. If service instability occurs after changing any service element pertaining to UAC or AV, report changes to Motorola. If unexpected behavior is experienced while UAC or AV are enabled, and does not occur after disabling UAC or AV, the customer will be responsible for diagnosing and correcting the issue.
17. Provisioning knowledge of the service: Customer must ensure that adequate provisioning training and knowledge has been provided to those authorized to access and/or make changes within PremierOne Provisioning. Provisioning changes should be tracked. This information should be supplied to Motorola to aid in troubleshooting efforts should a problem be experienced. Motorola now provides a tool to aid in provisioning change identification, but changes should be trac.ked internally by the customer as a failsafe.
18. Use of Deployment or All-In-One (AIO): Users of the deployment tool or AIO tool must be appropriately trained and understand its operation fully. Deployment packages that are no longer necessary should be purged. Customer is responsible for mobile customer deployment and should engage Motorola support if a problem is discovered.
19. ISP Bandwidth and Stability: Install, monitor and maintain ISP connections that provide stable operations and adhere to bandwidth requirements to ensure the effective operation of Motorola products and related service components.
20. Remote Access: Upon successful completion of approved background check, customer must provide remote access to requesting Motorola personnel for troubleshooting purposes. This includes, but is not limited to, VPN account access, Microsoft Active Directory Federation for domain access and access to all service elements that pertain to the operation of the PremierOne Cloud Service and functionality.
21. End User Training: Ensure that ali end users of Motorola products are adequately trained to perform their duties and not cause harm or upset of service functionality.
Motorola does offer additional training if necessary for an additional cost.
22. Change Management: Notify Motorola of any changes made to the PremierOne Cloud Service, associated interfaces, related hardware, software, network, or any other element that may adversely impact operation or functionality.
MOTOROLA RESPONSIBILITIES
1. Motorola Service Support Center: Motorola provides availability to the Service Support Center (800-MSI-HELP), 24 hours a day, 7 days a week to respond to Customer's requests for Severity 1 support. Refer to Severity Level Response Time Goals_for Severity 2, 3 and 4 response times.
2. Motorola Response: Provide remote technical support service via telephone consultation for technical issues that require a high level of PremierOne Cloud Service knowledge and troubleshooting capabilities. Remote technical support is delivered through the Exhibit A: Contract Documentation Requirements
126 PremierOne Maintenance and Support Agreement Motorola Solutions CD
May 10, 2022 Item #11 Page 506 of 604
DocuSign Envelope ID: EEOOOOEC-B190-469F-887C-147E3BCEAFF7
10.7 City of Carlsbad, CA
February 16, 2022
Motorola SSC by a staff of technical support specialists skilled in diagnosis and swift resolution of PremierOne Cloud Service performance and operational issues.
3. Case Management: Motorola will track the progress of each ticket from initial capture to resolution. Motorola will advise and inform the customer of the ticket progress and tasks that require further investigation and assistance from the customer's technical resources.
4. Subscription Services Updates: All subscription service updates, feature enhancements, state mandated changes to CIBRS, and defect repairs for the PremierOne cloud solution are provided at no additional cost during the subscription period. Updates will be applied to the training environment approximately two weeks prior to updating the production environment to allow time for user testing. During the production environment update, active user sessions are not interrupted, but the next time a user launches the client, the new version of the CAD client launches.
SECURITY
Motorola will maintain industry standard security measures to protect the Solution from intrusion, breach, corruption or security risks. During the term of the Agreement, if the Solution enables access to Criminal Justice Information ("CJI"), as defined by the Criminal Justice Information Services Security Policy ("CJIS"), Motorola will provide and comply with a CJIS Security Compliance document. Any additional security measure desired by customer may be available for an additional fee.
Motorola will provide the necessary information for its personnel that access customer CJI to submit to a background check based on submission of FBI fingerprint cards, complete CJIS Security Awareness Training and execute the CJIS Security Addendum.his the customer's responsibility to determine when the background credentialing process is required by Motorola personnel.
Customer is independently responsible for establishing and maintaining its own policies and procedures and for ensuring compliance with CJIS and other security requirements that are outside the scope of the Service provided. Customer must also establish and ensure compliance with access control and identification and authentication policies and procedures, including password security measures, lost and stolen credentials and account validation. Further, customer must maintain industry standard security and protective data privacy measures. Motorola further disclaims any responsibility or liability whatsoever for customer's failure to maintain industry standard security and data privacy measures and controls, or their role in CJIS Security Policy compliance. Motorola reserves the right to terminate the Service if customer's failure to maintain or comply with industry standard security and control measures negatively impacts the Service, Solution or Motorola own security measures.
Both parties will maintain and follow a breach response plan consistent with the standards of their respective industries to include CJIS Security Policy reporting.
Exhibit A: Contract Documentation Requirements
G Motorola Solutions PremierOne Maintenance and Suppot1 Agreement 127
May 10, 2022 Item #11 Page 507 of 604
OocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7 City of Carlsbad, CA
February 16, 2022
Motorola uses reasonable means in the design and writing of its own Software and the acquisition of third party Software to limit Security Vulnerabilities. While no software can be guaranteed to be free from Security Vulnerabilities, if a Security Vulnerability is discovered, Motorola will immediately begin investigation into the root cause of the issue and take the steps set forth in this Agreement, working to correct the issue as soon as reasonably possible.
10.8 LIMITATIONS AND EXCLUSIONS
The following activities are outside the scope of the support offered in this Support Plan:
■ On-site visits/resources
■ Provisioning efforts
■ Hardware replacement/exchange
■ Motorola implementation of on-site upgrade and expansion services ■ Customized reports. Such requests are to be directed to the CSA Exhibit A: Contract Documentation Requirements
128 PremierOne Maintenance and Support Agreement Motorola Solutions I'
May 10, 2022 Item #11 Page 508 of 604
DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BC EAFF7 City of Carlsbad, CA
February 16, 2022
Exhibit B -Labor Rates
The following are Motorola's current labor rates, subject to an annual change.
The following rates apply to Customers with a current, active Maintenance and Support Agreement. Billable rates apply to services provided outside of the scope of the Maintenance and Support Agreement and outside the selected Service Level PPM:
After 5 p.m., Saturday, Sunday, Motorola Holidays $334 per hour, 2 hours minimum The following rates apply to Customers without a current, active Maintenance and Support Agreement and a I to services available on a Time and Material basis:
After 5 p.m., Saturday, Sunday, Motorola Holidays $668 per hour, 2 hours minimum Above rates reflect labor rate only. Additional fees for on-site travel expenses, third party expenses and /or materials will be quoted at the time of customer request for services.
Exhibit A: Contract Documentation Requirements
G Motorola Solutions PremierOne Maintenance and Support Agreement 129
May 10, 2022 Item #11 Page 509 of 604
DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7 City of Carlsbad, CA
February 16, 2022
SECTION 11
FUNCTIONAL REQUIREMENTS
MATRIX
· The Functional Requirements Matrix dated January 19, 2022 is attached herein.
Exhibit A: Contract Documentation Requirements
130 Functional Requirements Matrix Motorola Solutions G
May 10, 2022 Item #11 Page 510 of 604DocuSign Envelope ID: EE0000EC-819D-469F-887C-147E3BCEAFF7 INSTRUCTIONS TAB City of Carlsbad Request for Proposals #20-13: CAD/Mobile Acquisition Functional Requirements This spreadsheet contains detailed functional requirements for the systems desired by the City of Carlsbad. These requirements are based on the needs and requirements of the Carlsbad Police Department, as well as industry standard guidelines for public safety systems design, implementation and operation. The following codes should be used to indicate the ability of the proposed system to meet the City's needs: Response Response Code Proposed system complies with requirement. C Proposed system does not comply with requirement. N Proposer recommends an alternative no-cost way to meet requirement (provide explanation in the "Comments" column). A Proposed svstem reauires software modification to comply with reauirement (provide M Vendor is proposing to use a Third-Party to provide the desired functionalitv T Provide the appropriate response code in the column next to each requirement. Where applicable and where requested, pro~ide additional information that describes the way in which the proposed system fulfills the given requirement or how an alternative to the requirement will meet the City of Carlsbad's needs. Short responses may be provided in the "Comments" column, while longer answers may be provided on a separate page. Do not insert rows into any portion of the document. Please respond to each requirement. Omitted responses will be evaluated as response codes of "N" (proposed system does not comply with requirement). Please note that requirements listed in the "General" tab are intended to be system-wide, and therefore apply to CAD and Mobile applications. Page 1 of 1
May 10, 2022 Item #11 Page 511 of 604DocuSign Envelope ID: EEOOOOEC-B19D-469F-887C-147E3BCEAFF7 GENERAL TAB City of Carlsbad, CA Request for Proposals #20-13: CAD/Mobile Acquisition General Functional Requirements 2 Ability to provide the user with feedback as to the success or failure of a system task, including, but not limited to: 3 Audible alert C 4 Visual alert C 5 !Ability for system to automatically adjust number sequencing for new calendar years. C 6 !Ability for system to automatically account for daylight savings time and any required parameter changes to daylight savings. I C 7 !Ability to adjust date to account for leap years. I C Ability for system to identify whether a system transaction 8 I occurs during the first 1 :00 -2:00 a.m. during fall daylight savings or the second 1 :00 -2:00 a.m. during fall daylight I N 9 savings. !Ability to date and time stamp all system transactions. I C 10 I Ability to have a single master time stamp for all application components. I C 11 !Ability for all date and time stamps to be system generated. I C 12 !Ability to print with a single keystroke, including but not limited to: 13 Screen C 14 Window N 15 Field N 16 mm 17 Ability for the agency to define codes for drop down menus (e.g., I C BN for brown, BL for blue). 18 I Ability for the agency to maintain code tables, without contacting I vendor. C 19 !Ability to make changes and additions to the code tables without modification to or recompilation of the application software. I C 20 I Ability to share code tables among application components. I C Page 1 of 17
May 10, 2022 Item #11 Page 512 of 604DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7 GENERAL TAB City of Carlsbad, CA Request for Proposals #20-13: CAD/Mobile Acquisition General Functional Requirements Ability for code table updates to propagate throughout the system 21 I (e.g., an update in a code table for one application component updates the same code table in other application components). 22 Ability to designate code table values as obsolete and unavailable for current use, preventing further entry of that value, yet retain the value in the table for inquiries on historical data. 23 !Ability to create a new code and merge/link historical records to a new code. 24 IAbili~ to store the date a code table Wllue becomes obsolete. 25 !Ability to store the date a code table value becomes effective. I 26 l~~ility to prevent display o(obsolete code table values on drop ~wn lists. 27 28 29 30 31 32 33 34 35 36 37 38 Ability to comply with OIS software/application security re_g_uirements. Ability to encrypt data transmissions, per CLETS/NCIC requirements. Ability to create multiple security groups. Ability to assign personnel to security groups. Ability to assign users to multiple security groups. Ability for system adminsitrator to assign users to groups based on call siqns. Ability to enable users to override the group to which they are assiqned. Ability for agencies to define access permissions for each security group. Ability to prevent users with expired CLETS/NCIC certification from accessin~ CLETS/NCIC data. Ability to provide users with a reason for preventing access to CLETS/NCIC data. -----Ability to view, add, maintain, modify and delete user profiles based on: C C N C C C C C C C C C N C C C New code table may be created, however merging or linking code tables to historical records is not supported. Page 2 of 17
May 10, 2022 Item #11 Page 513 of 604DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7 GENERAL TAB City of Carlsbad, CA Request for Proposals #20-13: CAD/Mobile Acquisition General Functional Requirements Item# General Functional Requirements Response Code Comments 39 Agency C 40 Security group C 41 User ID C 42 User name C 43 Any combination of the above C 44 Ability to restrict user access or security group access to files and data fields for specified transactions: 45 Add/create C 46 Attach to email or send via other electronic method C 47 Delete C 48 Inquiry C 49 Modify C 50 Print C 51 View C 52 Ability to assign user access or security group access to files and data fields for specified transactions: 53 Add/create C 54 Attach to email or send via other electronic method C 55 Delete C 56 Inquiry C 57 Modify C 58 Print C 59 View C 60 Ability to assign security access by physical device (e.g., PC, C terminal, tablet). 61 Ability to remotely log out a workstation (mobile or desktop). C 62 Ability to lock out a user who is deemed a security risk while that C user is on-line (e.g., logged into the system). 63 Ability to provide security at the following levels: 64 Application C 65 Database C 66 Field C 67 Record C 68 Report C Page 3 of 17
May 10, 2022 Item #11 Page 514 of 604DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7 GENERAL TAB City of Carlsbad, CA Request for Proposals #20-13: CAD/Mobile Acquisition General Functional Requirements 69 Screen 70 Transaction 71 System 72 Ability to create temporary security profiles. 73 Ability to tie security profiles to Active Directory user groups. 74 I Ability for applications to work independently in the event Active Directory becomes unavailable. I Ability to support alternate authentication technologies, including 75 I but not limited to the following (please list additional compliant I authentication technologies in the comments column): 76 ID card 77 Security token 78 Biometric scanner 79 Bluetooth 80 Ability to flag a data element as confidential information for security purposes. 81 Upon data entry l 82 After data entry I Ability for users who are not authorized to access confidential 83 I information to see that the information exists, without being able I to see the actual information. Ability for system administrator to chanqe user IDs. Ability to be logged onto multiple workstations at the same time 87 (e.g., logged into mobile computer in a vehicle and logged onto a station computer at the same time): 88 89 90 91 Different types of workstation (e.g.,Jles_kt_cip and laptop) Same types of workstations (e.g., two desktops) Ability to track user logon/logoff times and locations for time reporting purposes. .Ability to support LDAP or Active Directory authentication. C C C C C C N N N N N N N N C N C C C C C Page 4 of 17
May 10, 2022 Item #11 Page 515 of 604DocuSign Envelope ID: EEOOOOEC-B19D-469F-887C-147E3BCEAFF7 GENERAL TAB City of Carlsbad, CA Request for Proposals #20-13: CAD/Mobile Acquisition General Functional Requirements 92 93 94 95 96 97 98 99 100 mmim Ability to support two-factor IO[On. Ability to support third-party identification devices for lo_[ons. Ability to automatically logoff a user after an agency defined predetermined period of inactivity, based on: User type Location Ability to disable automatic logoff for secured workstations. Ability to save user's data prior to automatically logging off the user. Ability to save user's system preferences prior to user logoff. Ability to save multiple user preferences on the same type of device for each user. Ability to provide system generated message to system 101 I administrator or supervisor when an agency defined number of unsuccessful sign-on attempts have occurred. 102 IAbil~ty for the unsuccessful sign-on attempt message to include, at a minimum: 103 I Date and time 104 I Number of attemp_ts 105 I user ID 106 I workstation ID 107 I Ability to "lock out" a user and close applications after an agency defined number of attempted logons. 108 I Ability_ to disable "lock out" feature. 109 110 Ability to provide a secure lock-out with quick re-authentication to restrict access to systems from an unattended workstation. !Ability for the agency to define the following password and user ID 111 .. creation cntena: 112 I character limitations 113 I Minimum User ID len[th 114 I Maximum User ID length 115 !Minimum password length C C C C C C C N C C C C C C C C C C C C Page 5 of 17
May 10, 2022 Item #11 Page 516 of 604DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7 GENERAL TAB City of Carlsbad, CA Request for Proposals #20-13: CAD/Mobile Acquisition General Functional Requirements 116 Maximum password length C 117 Uppercase characters C 118 Lowercase characters C 119 Special characters C 120 Numbers C 121 Ability to use Active Directory for password maintenance. C Ability for the agency to define which user-groups can reset 122 I passwords on behalf of users (or create a security group that can I C reset passwords on behalf of users). 123. I Ability to require the user to change their passwords at agency defined intervals. I C !Ability for the agency to set a global maximum time for allowing a I 124 k . d user to eep using a passwor . C 125 Ability to maintain a history of de-activated user IDs. C 126 Ability to disable password expiration feature. C 127 I Ability to require the user to enter a new password twice (e.g., to I verify password). C 128 Ability to produce auto-notification of impending password I C expiration. 129 Ability to enforce strong passwords per CJIS requirements. I C 130 !Ability for individual system users to change their own passwords. I C 131 Ability for system administrator to add and delete users. C 132 Ability for system administrator to disable an account. C 133 Ability to mask passwords when typed. C 134 Ability to encrypt passwords when stored and sent (i.e., no clear I C text passwords). 135 r.t.l!I!.J 136 Ability to create a security group defining who has audit trail I C access permissions. 137 Ability to maintain an audit trail at the following levels: 138 Field C 139 Record C 140 Module C Page 6 of 17
May 10, 2022 Item #11 Page 517 of 604DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7 GENERAL TAB City of Carlsbad, CA Request for Proposals #20-13: CAD/Mobile Acquisition General Functional Requirements Item# General Functional Requirements Response Code Comments 141 Application C 142 Text messages N 143 CLETS/NCIC Messages C 144 Ability to view all audit trail records. C 145 Ability to log all actions including, but not limited to: 146 Keystrokes C 147 Queries C 148 Query returns C 149 Changes C 150 Updates C 151 Errors C 152 Security violations C 153 Attempted breaches C 154 File maintenance transactions (e.g., create, read, add, update, C I delete transactions) 155 Inquiries to all internal and external systems C 156 Transaction entries C 157 Print jobs C 158 Override C 159 Successful sign-on C 160 Unsuccessful sign-on attempts C 161 Unauthorized attempts to access data C PremierOne CAD's audit feature records all 162 Ability for the agency to configure which transactions are recorded N transactions associated with an incident. Viewing an in the audit log. incident's audit history displays these transactions for that incident only. 163 Ability to store audit trail data including, but not limited to: 164 User ID C 165 User name C 166 Terminal ID C 167 IP address C 168 Printer ID C 169 Security level C 170 Date and time stamp C 171 Transaction type C Page 7 of 17
May 10, 2022 Item #11 Page 518 of 604DocuSign Envelope ID: EEOOOOEC-B19D-469F-887C-147E3BCEAFF7 GENERAL TAB City of Carlsbad, CA Request for Proposals #20-13: CAD/Mobile Acquisition General Functional Requirements Item# General Functional Requirements Response Code Comments 172 Input, edit, deletion or inquiry C 173 Before and after values of modified data C 174 Type of data accessed during an inquiry C 175 Report number (if applicable) C 176 Ability to review all computer activity performed by a specified C user during a period of time. 177 Ability to log all vendor access to system (e.g., record a description C of all vendor activity). 178 Ability to maintain historical data based on an agency defined C length of time. 179 Ability to maintain file history so that field value changes can be C viewed both before and after change occurred. 180 Ability to set audit log purge criteria. C 181 Ability to perform purge based on criteria. C 182 Ability to date, timestamp, view and audit all inquiries. C 183 Ability of the system to assign a unique identifier to each record C (i.e., log ID). 184 Ability to comply with NCIC Ill logging requirements. C 185 Ability for all audit and logging functionality to be configurable. C 186 Ability to pull up a record and see (e.g., via a function key): 187 Who made last change to record C 188 Time and date stamp of last change to record C 189 Modifications made to record (before and after values) C 190 Ability to extract reports from the audit trail. C 191 Ability to secure audit log from user tampering. C 192 Ability to archive audit trails based on transaction type and/or C date. 193 Ability to manually archive information based upon user-specified C parameters (time, file size, etc.). 194 Ability to automatically archive information based upon the following parameters: 195 Agency defined time period C 196 Agency defined file size C Page 8 of 17
May 10, 2022 Item #11 Page 519 of 604DocuSign Envelope ID: EEOOOOEC-819D-469F-887C-147E3BCEAFF7 GENERAL TAB City of Carlsbad, CA Request for Proposals #20-13: CAD/Mobile Acquisition General Functional Requirements Dashboards !Ability to support dashboards to display information at a glance in 200 h f II · r · t e o owing app IcatIons: 201 CAD C 202 Mobile C I Ability for users to configure information displayed in personal 203 dash boards. C tbility for dashboards to update dynamically as information is 204 entered into the system. I C I Ability for dashboards to present information in the following 205 formats: 206 Text based C 207 Graphical C 208 Map based C 209 Reporting 210 Ability to provide a native reporting tool that can: 211 1create reports based on any operational data field in any system database I C 212 I Create reports based on multiple operational data fields in any system database I C 213 Allow the end user to design report format C 214 Access multiple files and tables C 215 Print C 216 Generate HTML reports C 217 Create reports based on SQL queries C 218 Ability for the report generating tool to handle: 219 Arithmetic operations, including fractiles and percentiles C 220 A full suite of statistical operations C 221 Logic operations C 222 I Ability for the report generating tool to handle the manipulation of: Page 9 of 17
May 10, 2022 Item #11 Page 520 of 604DocuSign Envelope ID: EEOOOOEC-B19D-469F-887C-147E3BCEAFF7 GENERAL TAB City of Carlsbad, CA Request for Proposals #20-13: CAD/Mobile Acquisition General Functional Requirements 223 I Data formats 224 I Field sizes 225 I Editin_g_ rules for a field 226 I Field headin~s 227 I Data definitions 228 I Formattin_g_ rules 229 !Ability to maintain a general library of user-created re_e_orts. 230 1Ability to connect to database for business intelligence reporting purposes. 231 I Ability to preserve all user-created reports during updates and upgrades. 232 !Ability for all authorized users to access the general library of user-created re_e_orts. 233 I Ability for users to put their own reports in a "dashboard" for later use. I Ability to send reports to individuals or groups (via system or 234 'I) agency ema1 . 235 I Ability to generate reports on a pre-determined schedule. 236 I Ability to automatically send scheduled reports to distribution groups. -----237 I Ability to auto generate reports based on agency defined thresholds. 238 tbility to notify agency defined users when thresholds have been reached/exceeded. 239 !Ability to export reports results into standard formats, including: 240 lword 241 IPDF 242 !Access 243 !Excel 244 !Text files 245 IShapefiles C C C C C C C C C C C C C C C C C C A C A N Accessible PDF also available. Data can be exported and converted to Access, but not direct export in Access. Data can be converted from Word to text file. Page 10 of 17
May 10, 2022 Item #11 Page 521 of 604DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7 GENERAL TAB City of Carlsbad, CA Request for Proposals #20-13: CAD/Mobile Acquisition General Functional Requirements Item# General Functional Requirements Response Code Comments Export will be in Web Archive (MHTML) which is an 246 HTML A aggregate of HTML files. XML is also available for export 247 Image files A Export is available in .ppt which can be converted to an lmaqe. 248 csv C 249 Ability to save reports for subsequent viewing and/or printing. C 250 Ability to delete reports after viewing and/or printing. C 251 Ability to view requested reports prior to printing. C 252 Law Enforcement Queries 253 Ability to run a query on: 254 Report number C 255 Incident number C 256 Officer information, including: 257 Name \: 258 Badge Number C 259 ID C 260 Unit number C 261 Name information, including: 262 Name C 263 Identification number (driver's license, social security number, C etc.). 264 Date of birth C 265 Address information, including: 266 Exact address C 267 Street C 268 Intersection C 269 Business name C 270 Common name C 271 Vehicle information, including: 272 Vehicle identification number C 273 License plate number C 274 Phone number C 275 Reporting District C Page 11 of 17
May 10, 2022 Item #11 Page 522 of 604DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7 GENERAL TAB City of Carlsbad, CA Request for Proposals #20-13: CAD/Mobile Acquisition General Functional Requirements Item# General Functional Requirements Response Code Comments 276 Boat Hull number C 277 Serial number for weapons C 278 Serial number for property C 279 Personal File Number (PFN) C 280 Any combination of the above C Ability for query returns to display the name/ID of user requesting 281 information (e.g., if a Dispatcher runs a CLETS query on behalf of C an officer). 282 Ability to search and query multiple databases with one query C request. 283 Ability to provide check boxes for users to indicate which N databases to query. 284 Ability for subject queries of the following databases to return C photos, when available: 285 NetRMS C 286 CLETS/NCIC C 287 DMV C 288 CalPhoto C 289 CalGangs C 290 LPR C 291 CSAR C 292 Regional Registrants C 293 SDLAW C 294 Ability to set agency defined defaults for databases to query C within each application. 295 Ability to search multiple databases with a single query. C 296 Ability to consolidate query returns when multiple databases C are queried. PremierOne CAD allows collapsible consolidation 297 Ability for multi-database query returns to indicate the C information source (e.g., CLETS, NetRMS, etc.). 298 Ability to select any result from a query and drill down for C detailed information (e.g., hyperlink). 299 Ability to drill down on query results. C 300 Ability to save queries for later use. C 301 Ability, when running a criminal history, to capture: Page 12 of 17
May 10, 2022 Item #11 Page 523 of 604DocuSign Envelope ID: EEOOOOEC-B19D-469F-887C-147E38CEAFF7 GENERAL TAB City of Carlsbad, CA Request for Proposals #20-13: CAD/Mobile Acquisition General Functional Requirements Item# General Functional Requirements Response Code Comments 302 Date C 303 Report number C 304 Name C 305 Date of birth C 306 Purpose C 307 Charges C 308 Officer identification C 309 Identification number C 310 Searches 311 Ability to search on any operational data field. C 312 Ability to search on multiple operational data fields. C 313 Ability to access multiple files and tables in a single search. C 314 Ability to search narrative fields. C 315 Ability to search audit trails. C 316 Ability to search message logs. C 317 Ability to exclude specified text when conducting narrative text C searches. 318 Ability to conduct searches based on: 319 Soundex C 320 "Wild cards" . C 321 Exact match C 322 Partial information C 323 Boolean operators ("and," "or," and "not") C 324 Date ranges C 325 Keywords C 326 Ability to narrow down searches (search within a search). C 327 Ability to select any result from a search and drill down for C Note: This functionality must be supported by the detailed information (e.g., hyperlink). database being queried. 328 Ability to restrict searches that result in large volumes of data by: 329 Providing a warning of the size of records found C 330 Requesting users to prompt the system to continue the search C 331 Requesting users to prompt the system to cancel the search C 332 Requesting users to modify the existing search criteria C Page 13 of 17
May 10, 2022 Item #11 Page 524 of 604DocuSign Envelope ID: EEOOOOEC-B19D-469F-887C-147E3BCEAFF7 GENERAL TAB City of Carlsbad, CA Request for Proposals #20-13: CAD/Mobile Acquisition General Functional Requirements 333 I Ability to limit the number of records viewed at one time. 334 I Ability to clearly indicate when additional information (e.g., more search results) is available. 335 !Ability to save searches for later use. 336 !Ability to turn on/off pagination for query returns. 337 I Ability to export search results into standard formats, including: 338 lword 339 IPDF 340 !Access 341 !Excel 342 IText files 343 lsha_e_efiles 344 IHTML 345 IPDF 346 lAbility to drill down into search returns. 347 348 !Ability for an_y_ authorized user to create BOLs. 349 I Ability to provide an audit trail for BOLs. 350 I Ability to associate a BOL with a CAD incident number. 351 !Ability to provide the followin.K fields for a BOL record: 352 I Date issued 353 I BOL exi:iiration date 354 I Nature of the BOL 355 I BOL priority 356 lsublect name 357 I Subject description: 358 !Height 359 IWei_[ht 360 I Hair color 361 I E_y_e color 362 I clothing description C C C C C A C A N A C C C C C C C C C C C C C C C Data can be exported and converted to Access, but not direct export in Access. Data can be converted from Word to text file. Export will be in Web Archive (MHTML) which is an aggregate of HTML files. XML is also available for export Accessible PDF also available. Page 14 of 17
May 10, 2022 Item #11 Page 525 of 604DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7 GENERAL TAB City of Carlsbad, CA Request for Proposals #20-13: CAD/Mobile Acquisition General Functional Requirements 363 I Date of birth 364 I Known address or location 365 I Driver's license number 366 !vehicle descri_e_tion 367 !Vehicle license plate 368 !Weapon (multiple) 369 !Known associates 370 I Last known location 371 I Direction of travel 372 I Contact Information 373 I Person issuin_[ the BOL 374 !Agency issuing the BOL 375 I Case or incident number 376 !Additional information in free-form text field 377 I Ability to search for BOL based upon a_ny of the data fields. 378 !Ability_ to search the BOL narrative. 379 I Ability to accom_rTiodate multiple subjects in a BOL. 380 I Ability to accommodate multi_ele vehicles ina soi.~ 381 I Ability to accommodate multiple weapons in a BOL. 382 !Ability to attach a file to a BOL. 383 !Ability to embed a photo in a BOL. 384 !Ability to update a BOL. 385 !Ability to set time limits for BOL retention. 386 I Ability to close a B_QL: 387 1Ability to designate groups or individuals to whom BO Ls should be sent. 388 I Ability to view history of recently created BOLs. 389 !Ability to archive ex_e_ired BOL records. 390 !Ability to search expired BOL records. 391 IAbility to export BOL as a PDF. 392 393 I Ability to access a system hel_e_ menu: 394 !Ability to use either a mouse or command line to access the help menu. C C C C C N C C C C C C C C C C C C N C C C C C C C N C C Page 15 of 17
May 10, 2022 Item #11 Page 526 of 604DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7 GENERAL TAB City of Carlsbad, CA Request for Proposals #20-13: CAD/Mobile Acquisition General Functional Requirements Item# General Functional Requirements Response Code Comments 395 Ability to provide context-sensitive help in the form of prompts C and instructions. 396 Based on user's progress in workflow N 397 Based on data field C 398 Ability to provide context-sensitive help only upon a user request. C 399 Ability to provide help facility for an operation in progress via a C function key from a screen or field within any application. 400 Ability to provide training modules through help menu. C 401 Ability to search help files by keywords. C 402 Ability to provide help facility via function key or icon from any C screen or field within any application. 403 Ability to edit text in help files to address agency specific topics. C 404 Ability to maintain agency specific documentation and procedures, including: 405 Glossary of terms C 406 Glossary of error codes C Ability to augment vendor-supplied help tables with additional 407 information (e.g., add notes to a topic that are viewable along with C the vendor-supplied information). 408 Ability for the agency to create additional/new help files to N suoolement the vendor provided system documentation. 409 Ability for help file to automatically update at the time of all C version/release updates. 410 Ability to prevent software updates from overriding agency-N specific system documentation and help files. 411 Ability for system administrator to create error messages. C 412 Ability for system administrator to edit error messaaes. C 413 Ability to track revisions to system documentation and help files, including: 414 User ID C 415 Date and time C 416 Ability to provide help files in a Windows help format. C 417 Ability to bookmark topics. C Page 16 of 17
May 10, 2022 Item #11 Page 527 of 604DocuSign Envelope ID: EEOOOOEC-B19D-469F-887C-147E3BCEAFF7 GENERAL TAB' City of Carlsbad, CA Request for Proposals #20-13: CAD/Mobile Acquisition General Functional Requirements 418 I Ability to search help file by: 419 !Keywords 420 I Phrases 421 1To£ics 422 ISimilar topics 423 424 !Ability to support multiple environments, including: 425 I Production 426 ITest 427 ITrainin_g_ 428 !Backup Ability to provide a configuration tool to enable migrating specific 429 I individual configurations from the test environment to the production environment. Ability to provide a configuration tool to enable migrating specific 430 I groups of configurations from the test environment to the production environment. 'Ability to modify the test environment and transfer modifications 431 h d . . tot e pro uct1on environment. C C C C N C N N N N There is a single environment for Test/Training. New releases are released to this enviroment for customer testing approx one week prior to production updates. Page 17 of 17
May 10, 2022 Item #11 Page 528 of 604DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7 CAO TAB City of Carlsbad, CA Request for Proposals #20-13: CAD/Mobile Acquisition Computer Aided Dispatch Functional Requirements 2 3 4 5 6 Ability for authorized user to configure any CAD workstation to manage: Either call taking or dispatch in_[ functions Both call taking and dispatchin_[ functions Ability to maintain compliance with published NENA NG911 standards. Ability to provide dedicated fields to capture all CAD transactions in an audit log. 7 I Ability to allow multiple personnel to work on a sin~e incident. 8 Ability to provide a visual identification (e.g., ID stamp) to identify which call-taker/dispatcher entered specific information into a call. 9 I Ability to support remote access to CAD. 10 I Ability to perform the following via remote access: 11 I Monitor Units 12 I Monitor Incidents 13 I Create Incidents 14 I Dispatch Incidents 15 I Run Queries Ability to achieve full application functionality via mobile devices (i.e. smartphone, tablet, other than desktop). If limited CAD 16 ltunctionality is available via mobile devices, but not all, please provide written response in the comments column identifying the available functionali!'t: 17 !Application User Interface C C C C C C C C C N N N C PremierOne CAD's audit features record all transactions associated with an incident. These include Comments, incident create, incident status, recommendations, primary units, unit actions, unit statuses, and many more. Additionally interfaces can be audited to show when an interface came offline, how long the interface was running, the interface transactions, etc. User ID and Console ID are include with all transactions made by a user 'The PremierOne Mobile client provides full functionality available from PremierOne CAD in the field. Page 1 of 48
May 10, 2022 Item #11 Page 529 of 604DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7 CAD TAB City of Carlsbad, CA Request for Proposals #20-13: CAD/Mobile Acquisition Computer Aided Dispatch Functional Requirements 18 I Ability for the agency to determine which window configuration options are configurable at the user level. I N 19 Ability for users to customize all window views, including, but not limited to: 20 Font size 21 Font color N 22 Font type N 23 Window background color N 24 Window sizes N 25 Window locations N 26 Fields displayed N 27 Order in which fields are displayed N 28 I Ability to save windows configurations based on user login, irrespective of workstation. I N 29 I Ability to maintain window configuration settings during upgrades. I N 30 !Ability to reset configuration to default settings. I N 31 I Ability to display system messages without affecting work in progress. I N Ability to have multiple windows open simultaneously (e.g., multiple 32 I incident entry windows). If there is a limit to the number of windows that can be open simultaneously, please specify in the I N comments column. 33 Ability to tile or cascade multiple windows on screen. I N 34 General Data Entry 35 Ability to support data entry via: 36 Mouse (point and click) C 37 Command line C 38 Preformatted masks C 39 I Ability to execute any CAD function using the keyboard. (List I exceptions.) C 40 jAbility to execute any CAD function using the mouse. (List exceptions.) I C Page 2 of 48
May 10, 2022 Item #11 Page 530 of 604DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7 CAD TAB City of Carlsbad, CA Request for Proposals #20-13: CAD/Mobile Acquisition Computer Aided Dispatch Functional Requirements 41 !Ability to provide multiple command lines. I C 1monitors and active work areas. 42 !Ability to provide multiple call entry masks. I C I PremierOne provides six call entry masks known as erima!}'. work areas A user can navigate/toggle to any of the six 43 !Ability to toggle between active call entry masks. I C I work areas using the alt key and number of the primary work area ex: alt +2 will toggle to work area 2 I Ability for query returns to create a separate window from the I . 'Query returns have the ability to be orphaned 44 C into its own pane, which is moveable to any query mask. screen Command lines can be cleared with a single 45 !Ability to create a new command line with a single keystroke. I C I keystroke. Additionally, new command lines can be opened from each status monitor window. In PremierOne CAD, the command line is 46 !Ability to link a command line to a distinct incident. I C !assigned per work area where each can ,display a distinct incident. There is also a lcommand line on each status monitor. The default order of the command parameters 47 !Ability to enter commands in any order on the command line. I A lean be changed to match the specific o erations of our a enc . 48 Ability to enter more than one command on a single command line. C 49 !Ability to send the same comments via one command to any unit associated with an event/incident. I C so !Ability to click on the map and populate the address field with the corresponding location information. I C 51 Ability to support: 52 Drop down menus I C 53 Auto-completion I C 54 Ability to provide word processing capabilities on narrative and comment fields, including, but not limited to: 55 Text wrap I C 56 Paragraph formattin_[ I N Page 3 of 48
May 10, 2022 Item #11 Page 531 of 604DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7 CAD TAB City of Carlsbad, CA Request for Proposals #20-13: CAD/Mobile Acquisition Computer Aided Dispatch Functional Requirements Item# CAD Functional Requirements :esponse Cod Comments 57 Bullets and numbering N 58 Copy and paste C 59 Grammar check N 60 Spell check N 61 Ability to add words to the dictionary for spell check. N 62 Ability to disable any word processing capabilities at the agency N level. 63 Time Stamps 64 Ability to automatically time stamp all system transactions. C 65 Ability to manually create a time stamp.· C 66 Ability to manually override a time stamp. C 67 Ability to capture the time a time stamp was overridden. C 68 Ability for all overridden time stamps to be recorded as a manually-C entered override time. 69 Timers Ability to configure incident timers based on agency-defined 70 parameters (e.g., unit status updates, incident type, incident status) C and times. 71 Ability to associate timers with: 72 Unit status updates C 73 Incident type C 74 Priority type C 75 Incident status (e.g., remained in pending for 20 minutes) C 76 Ability to alert user to the expiration of the timer via: 77 Audible alert C 78 Visual alert C 79 Ability to configure the alerts to repeat at agency-defined intervals C until the timer has been acknowledged. 80 Ability to manually set timers. C 81 Ability to record acknowledgement of timer alert. C 82 Ability to provide the following options when a status timer expires: 83 Modify to new time value C 84 Reset to default value C Page 4 of48
May 10, 2022 Item #11 Page 532 of 604DocuSign Envelope ID: EEOOOOEC-B19D-469F-887C-147E3BCEAFF7 CAD TAB City of Carlsbad, CA Request for Proposals #20-13: CAD/Mobile Acquisition Computer Aided Dispatch Functional Requirements Item# CAD Functional Requirements :esponse Cod Comments 85 Stop timer C Ability to alert agency defined users if an expired timer has not been 86 acknowledged after an agency defined period of time (e.g., C escalation process). 87 Flags and Alerts 88 Ability to automatically present user any flags/alerts associated with: 89 Location C 90 Weapons C 91 Warrants C 92 Medical C 93 Key information (Knox Box, gate code, etc.) C 94 Hostile occupant C 95 Officer safety (known to resist, etc.) C 96 Agency-defined C 97 License Plate C 98 Person C 99 Weapons C 100 Warrants C 101 Medical C 102 Key information (Knox Box, gate code, etc.) C 103 Hostile occupant C 104 Officer safety (known to resist, etc.) C 105 Agency-defined C 106 Other (if flags and alerts can be associated with any other identifier, C please list those in the "Comments" field) 107 Ability, upon entering an address, to automatically present user any C flags/alerts associated with the address, including but not limited to: 108 Hazard information C 109 Premise history C Ability, upon entering an address, to automatically present user any 110 flags/alerts associated within a radius of the address entered, including but not limited to: Page 5 of 48
May 10, 2022 Item #11 Page 533 of 604DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7 CAD TAB City of Carlsbad, CA Request for Proposals #20-13: CAD/Mobile Acquisition Computer Aided Dispatch Functional Requirements 111 I Hazard information 112 I Premise history 113 !Ability for alerts to include: 114 !Audible alert 115 !Visual alert 116 !Ability for the agency to confiture which alerts are audible. 117 1Ability to require dispatchers to acknowledge that they have viewed hazards. Ability, when querying a name, for user to be notified of an 118 I associated alert (e.g., if the subject is flagged in the RMS, wanted via CLETS/NClq. 119 I Ability to drill down into flags to display additional information. 120 I Ability to display incident history of address when creating an incident. 121 I Ability for users to sort summary-of past incidents by: 122 I chronological order (most recent call shown firstl 123 lcall type 124 !Ability for user to add a flag/alert. 125 !Ability to set an expiration for aflai/alert. 126 I Ability to add a temporary flag, comment or note to a location. 127 I Ability to notify agency-defined personnel of pending expiration of a temporary flag. 128 1Ability to include flagged information with dispatches sent to 129 130 lcall Recei_e_t 131 !Ability to receive call data from: 132 I E9-1-1 phone S',I_Stem 133 I Non-emergency 10-di~t phone numbers 134 IText-to-911 C C C C C C C C C C C C C C A C C N N PremierOne CAD provides various types of flag/alerts through incident priority comments, Premise/Hazard_,_ and BOLO. Notification can be manually sent through the PremierOne CAD Messaging system or a City created custom report notification. Page 6 of 48
May 10, 2022 Item #11 Page 534 of 604DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7 CAD TAB City of Carlsbad, CA Request for Proposals #20-13: CAD/Mobile Acquisition Computer Aided Dispatch Functional Requirements Ability to automatically create a call for service when a 9-1-1 call 135 I comes in through the phone system (e.g., create a call and open a call entry mask): 136 I Hard-wired 9-1-1 _e_hone line 137 Jwireless 9-1-1 line 138 Jcall Data Entry 139 !Ability to enter incidents using preformatted screens. 140 1Ability for the agency to determine what data elements are captured as part of the preformatted screen. 141 !Ability to provide dedicated fields to capture all incoming call information from the E9-1-1 system, including, but not limited to: 142 !caller name 143 !Caller tele_e_hone number 144 I caller address/location callin_[from 145 I incident location 146 !Alternate tele_e_hone number 147 !Cellular phone service _e_rovider 148 I Phase I or Phase 11 indication 149 IX/Y coordinates 150 IText messages (assuming phone system is NG9-1-1 capable) 151 152 153 154 TTY conversation Any other information captured by the E9-1-1 system Ability to translate texts submitted through NG9-1-1 in a foreign language to English. Please specify which languages can be translated in the comments column. Ability to attach multimedia messages (MMS), including videos or pictures taken by citizens, to a call. 155 I Ability to automatically populate CAD screen with information from E9-1-1 application, without manual intervention. C C C C C C C C C C C C N C C N N C The determination of data elements for capture is based on existing PremierOne CAD fields. New data elements are not able to be created. The automatic or manual population of ANI/ALI data to the incident form is a provisioning settinq in PremierOne CAD. Page 7 of 48
May 10, 2022 Item #11 Page 535 of 604DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7 CAD TAB City of Carlsbad, CA Request for Proposals #20-13: CAD/Mobile Acquisition Computer Aided Dispatch Functional Requirements 156 I Ability to populate CAD screen with information from E9-1-1 The automatic or manual population of ANI/ALI C data to the incident form is a provisioning application via manual intervention (e.g., function key, mouse click). setting in PremierOne CAD. 157 !Ability to select previous E9-1-1 data to populate call entry screen. N 158 I Ability to provide dedicated fields to enter the following information: 159 Individual (caller, witness, suspect) C 160 Multiple individuals C 161 Vehicle C 162 Multiple Vehicles C 163 Location C 164 Ability to generate an incident from a previous incident. C 165 !Ability for authorized user to add comments to a call after it has been dispatched. I C 166 !Ability for authorized user to add comments to a call (without re-opening the call) after it has been closed. I C 167 I Ability to alert dispatcher that the call taker has added information by: 168 !Audible alert I N PremierOne CAD displays a Priority Notification 169 !Visible alert I C dialog box whenever another user enters priority comments or makes priority updates to 170 I Location Capture I Ian incident. 171 I Ability to receive geographic coordinates from a cellular telephone earner. I C 172 !Ability to relate X/Y coordinates to an actual address. I C 173 !Ability to capture the following information upon receipt of a wireless 9-1-1 call: 174 X/Y coordinates C 175 Street address of tower C Approximate addresses are given via a reverse 176 I Nearest cross street I C lgeocode of the laVlong, which then will give a cross street Page 8 of 48
May 10, 2022 Item #11 Page 536 of 604DocuSign Envelope ID: EEOOOOEC-B19D-469F-887C-147E3BCEAFF7 CAD TAB City of Carlsbad, CA Request for Proposals #20-13: CAD/Mobile Acquisition Computer Aided Dispatch Functional Requirements 177 178 !Ability to provide user with choices of ALI data for location capture includin_g_: 179 lx/Y coordinates 180 !Intersection 181 I Street Address 182 !Any combination of the above 183 !Ability to transform X/Y coordinates to a map for display. 184 !Ability to capture incident location separately from caller location. 185 I Ability to enter a location for an event by the following methods: 186 Street address 187 Block number or address range 188 Commonplace name 189 Landmark 190 Intersecting street names 191 X/Y coordinates 192 Point and click on a mae_ 193 !Ability to suggest locations based on type-ahead capabilities for: 194 I Street addresses 195 I Intersections 196 I commonplace names Ability for agency to define the order in which type-ahead locations 197 lare presented to the user (e.g., Carlsbad addresses before County addresses, etc-l C C C C C C C C C C C C C C N N N C Approximate addresses are given via a reverse 1eocode of the laUlon, PremierOne CAD supports a partial address entry that will display all possible matches in the Address Verification form. PremierOne CAD supports a partial address entry that will display all possible matches in the Address Verification form. PremierOne CAD supports a partial address entry that will display all possible matches in the Address Verification form. Page 9 of 48
May 10, 2022 Item #11 Page 537 of 604DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7 CAD TAB City of Carlsbad, CA Request for Proposals #20-13: CAD/Mobile Acquisition Computer Aided Dispatch Functional Requirements 198 I Ability to type in either street first when entering intersections. 199 I Ability to save intersections as identical address points regardless of order of streets entered (e.g., 1st/Main same as Main/1st). 200 I Ability for system to automatically parse address data into address data fields including: 201 !street number 202 lstreet name 203 !street prefix 204 I street suffix (NW, SW, N~ SE) 205 I street type_J~v, Ln_,_ Bd, "None") 206 I unit ty_pe 207 !Unit number 208 ICity_ 209 !Ability for user to include directional reference for a location (e.g., NB interstate 5, SO Exit 24). 210 I Ability to auto populate location information in CAD as E911 system receives u_edated location information. I Ability to automatically override Phase I information with Phase II 211 . f in ormation. 212 I Location Verification 2 3 I Ability to verify locations for any address entered into the system 1 (e.g., CAD incident address, field initiat~Q). 214 I Ability to override _[eoverified location. 215 !Ability to log all locations that fail geofile validation. 216 !Ability to create a report of all overridden geoverified locations. 217 IAbi~i:y to use the ALI reported location address for address venf1cat1on. 218 !Ability to validate an entry upon: C C C C C C C C C C C C C C C C C C PremierOne CAD captures and stores the Street number, direction, prefix, name, type, and suffix data fields in one data element, which is then parsed for validation and displaying on the CAD map. PremierOne CAD supports this requirement as long as the directional reference is included in the GIS provided by the City. Page 10 of 48
May 10, 2022 Item #11 Page 538 of 604DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7 CAD TAB City of Carlsbad, CA Request for Proposals #20-13: CAD/Mobile Acquisition Computer Aided Dispatch Functional Requirements 219 I Operator request (e.g., press a button) 220 I Entry into location field 221 !Ability to support Phase I wireless location validation from cellular callers. 222 I Ability to support Phase II wireless location validation from cellular callers. Ability to notify dispatcher if multiple street addresses/street 223 Ina mes/intersections with the same names are found in geofile with City_ of Carlsbad locations listed first. Ability to offer a list of address options if multiple similar 224 !addresses/intersections/street names are found in geofile with City of Carlsbad locations listed first. 225 !Ability_ to display closest address matches based on: 226 I Block ran_[es 227 I Buildin_[ name 228 I Business name 229 !common place names 230 I Intersections 231 I Phonetic spelling 232 lsound$X 233 I Street name 234 I Ability to display an unlimited number of common place names during the address verification process. 235 !Ability to enter a valid street name and be £_resented with: 236 !Aliases 237 !Associated address ran_[es 238 I List of cross streets !Ability to translate call location to appropriate public safety 239 geographical boundary (e.g. district, beat, sector). 240 !Ability to translate alias names to actual street names or addresses. C C C C C C C C C C C A A C A C C C C C PremierOne CAD supports a partial address entry that will display all possible matches in the Address Verification form. PremierOne CAD supports a partial address entry that will display all possible matches in the Address Verification form. PremierOne CAD will limit the response of possible matches to 100. Page 11 of 48
May 10, 2022 Item #11 Page 539 of 604DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7 CAD TAB City of Carlsbad, CA Request for Proposals #20-13: CAD/Mobile Acquisition Computer Aided Dispatch Functional Requirements 241 I Ability to display, on a map the incident location in relation to other active incidents on the map during the incident entry process. 242 !Ability to manually verify an address without creating an incident. 243 lcall Classification and Prioritization 244 I Ability to display a drop down list containing incident types. 245 I Ability to enter the call type via the command line. 246 I Ability to support auto completion during the call classification process. 247 !Ability to accommodate call type aliases (e.g., BURG/Burgl<1_r-_yJ 248 !Ability to override the systemgenerated incident priority. 249 I Ability for an authorized user to assign a priority to an address or location for a agency-defined period of time. 250 251 Ability to allow the authorized user to manually upgrade or downgrade the system-assigned priority at any point during the call (e.g., during call-taking, after dispatch). Ability for dispatcher to change call type without impacting active call data. I Ability to maintain a history of call types if call type changes over the 252 course of an incident. 'Ability to visually identify the priority level of an incident (color-253 code). 254 I Incident Initiation 255 I Ability to initiate an incident from the input of location and type code. 256 !Ability to input all call and narrative information on one screen. Ability to display a blank form for entering new incidents with a 257 I single keystroke, mouse click or function key upon initiation of a CAD incident. 258 I Ability to copy an existing incident to create a new incident at the same location. 259 !Ability to enter incidents usin~ 260 I standard call entry screen form C C C C C C C A C C C C C C C C C PremierOne CAD assigns a priority based on an incident type. As an alternative, users can enter a _E_r_e_mise/Hazard record for the location. Page 12 of 48
May 10, 2022 Item #11 Page 540 of 604DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7 CAD TAB City of Carlsbad, CA Request for Proposals #20-13: CAD/Mobile Acquisition Computer Aided Dispatch Functional Requirements 261 ICAD command on a command line 262 I Map by clicking on a location 263 IDuplicate_Call Mana£ement 264 !Ability to notify user of potential duplicate calls on the call entry screen durin_g initial call entry process. 265 !Ability to automatically identify potential duplicate calls based on: 266 I Incident/call type 267 I Proximity to current incident 268 !Time parameter 269 !Specific incident address/event location 270 I Phone number 271 I Ability to display proximity calls on a map (e.g., to assist dispatchers in identifying possible duplicate calls). 272 !Ability for the agency to configure the duplicate call identification algorithm (e.g., defined proximity, definition of "recently closed"). 273 !Ability to include the following in the potential duplicate call identification _e_rocess: 274 I Recently closed calls 275 I Pend in_[ calls 276 !Self-initiated calls 277 !Active calls 278 !Ability to manually identify a duplicate call and transfer the duplicate call information into the primary call. 279 I Ability to provide the user with the following information about possible duplicate incidents: 280 I incident details 281 I caller _e_hone number C C C N C C C A A C C C C C C C C The time parameter is based on recently closed incidents. As an alternative, PremierOne CAD displays a Previous Phone Check based on a matching phone number from past lnciden~ As an alternative, PremierOne CAD will display potential duplicate calls with location information and the ability to open the incident for further details. The user must view the potential duplicate incident to validate the following information, items 235-241. This is a one-click feature from the Potential Duplicates window. Page 13 of 48
May 10, 2022 Item #11 Page 541 of 604DocuSign Envelope ID: EEOOOOEC-B190-469F-887C-147E3BCEAFF7 CAD TAB City of Carlsbad, CA Request for Proposals #20-13: CAD/Mobile Acquisition Computer Aided Dispatch Functional Requirements Item# CAD Functional Requirements :esponse Cod Comments 282 Incident status C 283 Incident type C 284 Time the incident was initiated C 285 Units assigned C 286 Original dispatcher C 287 Disposition code C 288 Ability for the dispatcher to do any of the following if a CAD incident is determined to be a duplicate call: Add to the original incident record a second complainant with 289 complete complainant information and additional incident C comments 290 Close a duplicate incident and cross-reference it to the original CAD C incident 291 Create an entirely new incident using existing address data C 292 Ability to filter duplicate calls out of reports. C 293 Premise Information Retrieval 294 Ability to automatically initiate, upon address verification, an C address inquiry to search for associated premise information in CAD. 295 Ability to search for premise information based on: 296 Address C 297 Sub-address (e.g., unit number, building floor, apartment number) C Premise Hazard searches are based on proximity. 298 Partial address information (e.g., all addresses with apartment 14) C Premise Hazard searches are based on proximity. 299 Block ranges C 300 Current business name C 301 Historic business name (unlimited number) C 302 Common place names C 303 Intersections C 304 Radius from an address/location C 305 Polygon search on map N 306 Ability to search for premise information on locations not associated C with incidents. Page 14 of 48
May 10, 2022 Item #11 Page 542 of 604DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7 CAD TAB City of Carlsbad, CA Request for Proposals #20-13: CAD/Mobile Acquisition Computer Aided Dispatch Functional Requirements !Ability to automatically show premise history related to a current 307 incident (over an agency defined period of time). 308 !Ability to indicate the number of _e_ast incidents at a location. Ability to retrieve and attach to a CAD call any information 309 I associated with the premise (e.g., pre-plan information, previous calls for servicel, Ability to provide users with the choice of automatically or manually 310 I including a hyperlink to any attachment associated with a location (e.g. floor plans). 311 !Ability for map to display all known hazards within a user-defined radius. 312 I Ability to record in the incident history that premise history has been viewed by the user. Ability to recall any incident or premise history that has been viewed 313 l(e.g., does not allow for only one time view of premise history or incident)._ Ability for premise information to be available to user but not 314 I prevent operator from continuing current work (e.g., window does not cover entire workstation screen). 315 I Incident Schedulin_1 316 !Ability to enter incidents scheduled for dispatching at a later time, maintaining the O!iginal time of entry. 317 IA~ili~y to identify the user that creates a scheduled call for service within the scheduled call. 318 I Ability to visually differentiate a scheduled call from a standard call when the scheduled call populates the pending call queue. I Ability to modify incidents scheduled for dispatching at a later time, 319 . . . h . . I . f maintaining t e ongina time o entry. 320 !Ability to generate a call for service at specified intervals (e.g., directed p_atr~_s hours after the last directed patrol left). A C C C C C C C C C C N Premise history will appear after the address has been verified. The display of this information does not obstruct the work of the dispatcher. The PremierOne CAD map will.display all known hazards related to the incident. The radius/proximity is defined by the System Administrator. PremierOne CAD requires an acknowledgement for Priority/Critical Premise Hazard alerts. Information stored in the audit log. Page 15 of 48
May 10, 2022 Item #11 Page 543 of 604DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7 CAD TAB City of Carlsbad, CA Request for Proposals #20-13: CAD/Mobile Acquisition Computer Aided Dispatch Functional Requirements 321 !Ability to cancel incidents scheduled for dispatching at a later time maintaining the original time of entry. 322 !Ability to query all scheduled incidents (including cancelled scheduled incidentsL 323 !Ability to schedule an incident for a specific unit. 324 1Ability to require an acknowledgement of the scheduled incident from a unit. 'Ability to issue automated reminders prior to scheduled events 325 . d . . h ct· maturing an appearing in t e pen mg queue. tbility to provide timers to notify users of a scheduled call at a 326 predefined amount of time prior to the scheduled incident. 327 !Ability for scheduled incident to automatically enter the pending queue. 328 IAbility for officers to self-dispatch to scheduled incidents. 329 330 !CAD Incident Retrieval 331 !Ability to alert a dispatcher to the arrival of a new incident via: 332 !Audible alert 333 !Visual alert 334 !Ability to alert a dispatcher to the arrival of new incident information via: 335 !Audible alert 336 !visual alert 337 I Ability to visually differentiate updated call information from previously_ entered data. - ---Ability to indicate whether the updated information has been 338 !viewed by the primary dispatcher {e.g., font changes color after viewed, etc.). 339 I Ability to retrieve a CAD incident and review all available information already entered up to the point of incident retrieval. 340 !Ability to sort pending incidents by: 341 I Priori_ty 342 I Location C C C C C C C C C C C C C N C C C The acknowledgement from the mobile unit is a timestamp process from the user. Page 16 of 48
May 10, 2022 Item #11 Page 544 of 604DocuSign Envelope ID: EEOOOOEC-B19D-469F-887C-147E3BCEAFF7 CAD TAB City of Carlsbad, CA Request for Proposals #20-13: CAD/Mobile Acquisition Computer Aided Dispatch Functional Requirements Item# CAD Functional Requirements :esponse Cod Comments 343 Incident type C 344 Time in pending queue C 345 Beat number C 346 Incident number C 347 Ability to keep incidents in pending queue indefinitely. C Ability to forward an incident to another dispatcher (example: 348 "advise only" incidents, second dispatcher does not need to C dispatch resources for the incident). 349 Resource Recommendation 350 Ability to automatically provide appropriate resource recommendations based on any combination of: 351 AVL location C 352 Beat/station location responsibility C 353 Closest unit taking into account: 354 Natural boundaries C 355 Obstacles C 356 Traffic C 357 Speed limits C 358 Street network C 359 Street direction C 360 Equipment availability C 361 Incident location (e.g., unique response for specific location) C 362 Incident type C 363 Incident priority C 364 Occupancy type (e.g. residential, office building) C 365 Pre-defined response plans (response area plan) C 366 Special conditions (e.g., heightened response) C 367 Special equipment required C 368 Special skills units required C 369 Type of units required C 370 Number of units required C 371 Unit status C Page 17 of 48
May 10, 2022 Item #11 Page 545 of 604DocuSign Envelope ID: EEOOOOEC-B19D-469F-887C-147E3BCEAFF7 CAD TAB City of Carlsbad, CA Request for Proposals #20-13: CAD/Mobile Acquisition Computer Aided Dispatch Functional Requirements Ability to support numerous resource recommendation algorithms 372 I based on agency defined parameters (e.g., priority 1 calls are I dispatched according to closest available unit and all other calls are C dispatched based on beat assignments). Ability to prioritize unit response based on incident type so that 373 I appropriate units are automatically recommended and/or I C dispatched in priority order. I Ability to re-recommend closest units when a new unit comes into 374 . service. C 375 !Ability to alert dispatcher when a new unit becomes available. C 376 !Ability when upgrading an incident, for new unit recommendations I to take into account units already on-scene. C Ability for system to update the unit recommendation if user makes 377 I relevant incident information changes (e.g., type, location, alarm I C level). 3 I Ability to log recommendation overrides in the audit trail (e.g., log 78 recommended units versus dispatched units). I C 379 I Ability for dispatchers to supplement a resource recommendation with an additional unit and/or unit type. I C I Ability to visually identify whether a civilian ride-along is associated I 380 . h wit a unit. C 381 Ability to visually identify whether a trainee is associated with a I C unit. 382 Response Plans 383 Ability to develop response plans based on: 384 Geographic area (beat, sector, etc.) C 385 Address C 386 Multiple response route configuration (e.g., divided highway). C 387 Time of day C 388 Call type C 389 Resource availability C 390 Ability to assign a single response plan with multiple call types. C 391 Ability to include multiple agencies in response plans. C 392 Ability to generate temporary response plans. C Page 18 of 48
May 10, 2022 Item #11 Page 546 of 604DocuSign Envelope ID: EEOOOOEC-B19D-469F-887C-147E3BCEAFF7 CAD TAB City of Carlsbad, CA Request for Proposals #20-13: CAD/Mobile Acquisition Computer Aided Dispatch Functional Requirements Item# CAD Functional Requirements :esponse Cod Comments 393 Ability for user to override response plan recommendation. C 394 Ability to load a new response plan without stopping or pausing C application operations. 395 Ability for a communications supervisor to update the response C plans (e.g., without assistance from technical support or vendor). 396 Resource Determination 397 Ability to bring up a list of special skills/equipment for: 398 All personnel logged on C 39.9 A selected person C 400 Unit C 401 Ability to identify all personnel with a specific skill (e.g., language, training) by: 402 Logged on and available C 403 Logged on and not available (e.g., on another incident) C 404 Not logged on C 405 Ability to display potentially available resources based on unit status: 406 Assigned to a CAD call C 407 Assigned to a CAD call with a lower priority C 408 Unassigned C 409 Resource Dispatch 410 Ability for dispatcher to select and assign/re-assign recommended units using any of the following methods: 411 Command line entry C 412 Function key C 413 Mouse (drag and drop onto map) C 414 Ability to dispatch units by: 415 Accepting the proposed application recommended units C 416 Selecting and dispatching units other than those recommended by C the application 417 Selecting some, but not all, of the recommended units C 418 Ability to log recommendation overrides in the audit trail (e.g., C recom'mended units and dispatched units). Page 19 of 48
May 10, 2022 Item #11 Page 547 of 604DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7 CAD TAB City of Carlsbad, CA Request for Proposals #20-13: CAD/Mobile Acquisition Computer Aided Dispatch Functional Requirements 419 I Ability to automatically assign the initial unit dispatched as the default primary unit. I 420 Ability for CAD to do the following upon dispatch: 421 Assign the recommended or requested units 422 Remove the incident from the pending queue 423 Send the incident to the assigned unit's mobile computer 424 Start the status timers 425 Update the status display 426 I Ability to dispatch more than one unit at a time to the same call. I !Ability to assign or add multiple units to an incident with a single 427 command. I I Ability to assign a unit to an incident to which it was not originally 428 recommended. I 429 !Ability to provide dispatcher notification that dispatches have been I successfully delivered. 430 !Ability to resend a dispatch to the originally dispatched unit. I I Ability for primary dispatcher to be the only user that can dispatch a I 431 call. 432 Ability for any authorized user to dispatch a call. I 433 Field-Initiated Calls for Service I Ability for field personnel to initiate a call for service from the 434 mobile computer (e.g., traffic stop). I I Ability for Dispatchers to add additional units to a self-initiated 435 incident. I !Ability for units to add themselves as additional units to a self-436 initiated call based on call type. I 437 !Ability to ca_pture AVL coordi~ates when field personnel initiate a call for service from the mobile computer. I I Ability to capture unit ID number when incidents are initiated by a 438 unit in the field. I 439 I Ability to geovalidate addresses of self-initiated incidents. I C C C C C C C C C A C C C C C C C C C PremierOne Mobile users can manually acknowledge receipt of incident information on their MDT through a timestamp. PremierOne Mobile meets this requirement as long as the user permissions is correct. PremierOne Mobile meets this requirement as long as the user permissions is correct. PremierOne Mobile meets this requirement as long as the user permissions is correct. PremierOne Mobile meets this requirement as long as the user permissions is correct. PremierOne Mobile meets this requirement as long as t~e_ user permissions is correct. PremierOne Mobile meets this requirement as long as the user permissions is correct. Page 20 of 48
May 10, 2022 Item #11 Page 548 of 604DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7 CAD TAB City of Carlsbad, CA Request for Proposals #20-13: CAD/Mobile Acquisition Computer Aided Dispatch Functional Requirements 440 'Ability for dispatcher to link a field-initiated call to another incident. 441 !Ability to use one command line to enter a field-initiated incident and place the initiatin_[ unit on-scene. I Ability to provide dedicated fields to record the following 442 · f · h . · I d . ff. in ormatIon w en a unit Is pace in a tra Ic sto_~ status: 443 I Location of the stop 444 I Number of occupants in the vehicle 445 !Vehicle license plate 446 I State of registration 447 !Vehicle identifier (make, model, color) 448 I Driver information 449 1 Ability to limit field self-initiated calls to specific call types. 450 !Ability to notify dispatcher of any self-initiated call for service. 451 I Unit Assi1_nment to CAD Incident 452 I Ability to update unit status to associate the dispatched unit or units with the CAD incident. I Ability for the dispatcher to assign a unit to be the primary unit for 453 an incident. 454 IAbility for dispatcher to change the primary unit during an incident. I Ability for dispatcher to change the primary unit after closing an 455 incident. 456 !Ability to record the change of primary unit in the incident record. 457 !Ability to take a unit off a call and reassign the unit to a new call via: C C C C C C C C C C C C C C C PremierOne Mobile meets this requirement as long as the user permissions is correct. PremierOne Mobile meets this requirement as long as the user permissions is correct. PremierOne Mobile meets this requirement as long as the user permissions is correct. PremierOne Mobile meets this requirement as long as the user permissions is correct. PremierOne Mobile meets this requirement as long as the user permissions is correct. PremierOne Mobile meets this requirement as long as the user permissions is correct. PremierOne Mobile meets this requirement as long as the user permissions is correct. PremierOne Mobile meets this requirement as long as the user permissions is correct. PremierOne Mobile meets this requirement as long as the user permissions is correct. PremierOne Mobile meets this requirement as lonq as the user permissions is correct. Page 21 of 48
May 10, 2022 Item #11 Page 549 of 604DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7 CAD TAB City of Carlsbad, CA Request for Proposals #20-13: CAD/Mobile Acquisition Computer Aided Dispatch Functional Requirements 458 ISin~command 459 I Drag and drop Ability for a dispatched call for service to return to the pending 460 I queue if a unit is reassigned prior to the assigned call being dispositioned. 6 I Ability to use one command to both dispatch and put "on scene" 4 1 field personnel (e.g., if field personnel is "out with another unit"). 462 !Ability to hold an incident for a specific unit. 463 I Ability to hold an incident for a period of time and remove it from the pending queue in CAD and Mobile. I Ability to automatically (without user intervention) notify the 464 dispatcher of a held incident when the unit becomes available. 465 !Call Preem.e_tion 1Ability to pull a unit off an incident and reassign the unlt to a new 466 incident. 1Ability to return CAD incident to the pending dispatch queue if all 467 units are removed from an active incident. !Ability to visually indicate a preempted call (e.g., highlight last unit 468 . d) ass,gne . 469 !Ability to support a swap feature to allow two units to swap incidents with a sin_gle command. 470 lcall Stacking[Qu~uin_[ 471 !Ability to hold an lncident for a specific unit. 472 I Ability to hold more than one incident for a given unit or resource (call stacking). 473 I Ability to automatically (without user intervention) notify the dis_E>_atcher of a held incident when the unit becomes available. C C C C C C A C C C C C C C Call stacking allows incidents to be stacked aaainst a unit. Stacked calls are managed on a Stacked Incident Summary screen. From there the dispatcher can allow a stacked incident to be automatically dispatched once the unit is available or manually dispatched/swapped/reassianed. Page 22 of 48
May 10, 2022 Item #11 Page 550 of 604DocuSign Envelope ID: EEOOOOEC-819D-469F-887C-147E3BCEAFF7 CAD TAB City of Carlsbad, CA Request for Proposals #20-13: CAD/Mobile Acquisition Computer Aided Dispatch Functional Requirements mEllmil'I Ability for the agency to set time limits for stacked calls by priority 474 l(e.g., a queue limit of two hours for priority 5 calls and one hour for priority 3 calls). 475 !Ability for administrator to turn call stackin_[ on and off. 476 !Ability to stack calls based on call type. 477 478 I unit Placement in Service 479 1Ability to log one or more units on-duty/off-duty with a single command. 480 Ability to automatically assign a beat to a unit upon logon. 481 Ability to assign a unit to multi_Eie beats. 482 Ability to modify a unit's assignment during a shift. 483 Ability to define a roster (e.g. squad, company). 484 I Ability to place all units in a previously defined roster on or off-duty. I Ability to allow for a single unit exception when placing a roster on 485 or off duty. 486 !Ability to designate a unit available for onl_y_ certain: 487 lcall type 488 lcall priority 489 !Ability for units to lo_[ themselves into or out of service. 490 1Ability to prevent units from logging themselves into and out of service. 491 Ability to indicate a unit does not have a mobile computer. 492 • Assigned Unit Status Display 493 Ability to monitor an unlimited number of units. 494 !Ability to display the followingunit information: 495 !Beat 496 lcall type 497 lease number 498 I current incident number 499 I current location 500 I Current status 501 I Elapsed time in status C C C C C C C C C C C C C C C C C C C C C C C Page 23 of 48
May 10, 2022 Item #11 Page 551 of 604DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7 CAD TAB City of Carlsbad, CA Request for Proposals #20-13: CAD/Mobile Acquisition Computer Aided Dispatch Functional Requirements Item# CAD Functional Requirements :esponse Cod Comments 502 Group C 503 Last known location C 504 Logged onto Mobile (Y/N) C 505 Original location C 506 Call priority C 507 Radio ID C 508 Special note or comments . C 509 Special skills/training C 510 Home district C 511 Unit ID/call sign C 512 Unit type C 513 Vehicle number C 514 Ability to automatically update and display unit status data. C 515 Ability to sort displayed data by any unit information (e.g., shift, C incident, unit, location, status). 516 Ability to filter the units to be displayed in a single status monitor C (e.g., by beat, status, out of service (mechanical)). 517 Ability to visually differentiate, through color, text and/or symbols, unit status: 518 On CAD unit status display C 519 On map display C 520 Unit Activity Tracking 521 Ability to record all unit assignments. C 522 Ability to record all unit locations. C 523 Ability to record all unit status changes. C 524 Ability to record all elapsed time on a call. C 525 Ability to review unit status history within the CAD application. C 526 Ability to update location and note mileage for multiple stops. C 527 Ability to record multiple arrival times, including: 528 Arrival at a staging area C 529 Arrival at the incident location (e.g., room within a building} C 530 Arrival at the scene (e.g., general location) C 531 Ability to record multiple units arriving: 532 At one time (all at once) C Page 24 of 48
May 10, 2022 Item #11 Page 552 of 604DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7 CAD TAB City of Carlsbad, CA Request for Proposals #20-13: CAD/Mobile Acquisition Computer Aided Dispatch Functional Requirements 533 I Ability to place "at the scene" units that were not originally 534 dispatched to the call. 535 !Ability to assign (potentially multiple) units to a specific location which is different from the incident location. 536 I Ability for a dispatcher to change the location of a unit at any time while the unit is still assigned to an incident. 537 !Ability to update the location of a unit without altering the original incident location. 538 !Status Monitoring 539 !Ability to initiate status chan_ges via_the following methods: 540 I Data fields 541 I Function ke_y 542 I Mouse click (e.g., screen icon) 543 !Ability to automatically notify users monitoring or displaying the incident that information has chan_[ed via a visual alert. 544 I Unit Clearance !Ability to clear one unit from a CAD incident while allowing the 545 other assigned units to remain on the call. 546 I Ability to select any number of units to clear from CAD incident. 547 I Ability to clear all units simultaneously_ from a CAD incident. I lAbility to require a disposition to be entered prior to clearing the 548 . . f C . 'd primary unit rom a AD inc, ent. 1---i,---549 550 !CAD Call Display 551 !Ability to monitor an unlimited number of calls for service. (If limited, indicate the maximum in the "comments" field.) 5 2 !Ability to dynamically display (e.g., automatically update) incident 5 status data in a summary window (status monitorl C C C C C C C C C C C C C C C Each unit status timestamp can store a unit location, separate from the incident location. Each unit status timestamp can store a unit location, separate from the incident location. Each unit status timestamp can store a unit location, separate from the incident location. A screen icon status change is not available. However, other mouse click functionality such as right-click to a status sub-menu can initiate a status chanqe. The data available for display within a status monitor window is limited by the data applicable for that window type and 950 items. Page 25 of 48
May 10, 2022 Item #11 Page 553 of 604DocuSign Envelope ID: EE0000EC-B 19D-469F-887C-147E3BCEAFF7 CAD TAB City of Carlsbad, CA Request for Proposals #20-13: CAD/Mobile Acquisition Computer Aided Dispatch Functional Requirements 553 I Ability to review incident information in reverse chronological order. 554 !Ability to display a window listing pending and holding incidents entered from any CAD workstation. 555 !Ability to allow for an unlimited number of agency-defined incident statuses. 556 I Ability to view incident details of one or more incidents at a time. 5 7 !Ability to click on an active incident and highlight all assigned units 5 in the unit monitorin_[ window. 558 I Ability to show incidents on the CAD mapping display. 559 I Ability to accommodate multiple locations for one ca~ 560 ICAD Incident Updates 561 I Ability_ to add new or additional information to a CAD incident. 562 !Ability for multiple operators to simultaneously modify the same incident. 563 !Ability to automatically identify (e.g., ID stamp) the operator adding information to a call. 564 !Ability to display the following information when additional information is added to an incident: 565 !Time information was added 566 I 1D of person entering information 567 IAbili~y. to display new information added to the incident without requmng the user to open the call. Ability to simultaneously notify dispatcher and dispatched units of 568 I u_e_dated information. 569 !Reopening CAD Incidents 570 !Ability to reopen closed incidents. 571 !Ability to r_eopen a closed call without losing previously recorded date and t1mestam~p_s. __ 572 !Ability to assign units to reo_e_ened calls. C C C C C C C C C C C C C C C C C The PremierOne CAD Pending Queue will display pending and holding incidents from any CAD workstation. Status Monitors can display Pending and Active incident details. Additional Status Monitors can be created for specific agency needs. Page 26 of 48
May 10, 2022 Item #11 Page 554 of 604DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7 CAD TAB City of Carlsbad, CA Request for Proposals #20-13: CAD/Mobile Acquisition Computer Aided Dispatch Functional Requirements !Ability for dispatchers to add comments to a CAD call record after 573 the call is closed without reopen in_[ the incident. 574 I Ability to add a case number to a clos-ed incident. 575 I Ability to change the disposition code of a reo.e_ened call. 576 I Ability to date and timestamp a reof)ened call multi.e_le times. 577 !Cross-Referencing Calls 578 !Ability to cross-reference an unlimited number of active incidents. 579 !Ability to cross-reference an unlimited number of closed incidents. 580 1Ability to cross reference one call to another by inserting a hyperlink to the cross referenced call. 581 582 I CAD Incident Cancellation 583 !Ability to cancel an incident with a sin~e command. 584 1Ability to mandate that the user enter a reason for canceling an incident prior to the sy~tem executin_[ the command to cancel. Ability to automatically remove the incident from the pending or 585 lactive incidents queue and add the disposition (e.g., cancelled) upon execution of a command cancel in_[ an incident. Ability to automatically clear all dispatched units from the incident 586 I upon incident cancellation (e.g., upon invoking the cancel command 1. 587 !Disposition Recording 588 !Ability for.the agency to define disposition codes. I Ability to differentiate between an initial disposition and final 589 ct· .. 1spos1t1on. 590 !Ability to support an unlimited number of disposition types. 591 !Ability to require a disposition code before an incident can be cleared. 592 IA_bility_f~r either dispatchers or field personnel to enter the d1s.e_os1t1on code. C C C C C A C C C C C C C C C PremierOne refers to this feature as Associated Incidents and requires the clicking of a button, rather than a hyperlink, to access the referenced call. Page 27 of 48
May 10, 2022 Item #11 Page 555 of 604DocuSign Envelope ID: EE0000EC-819D-469F-887C-147E3BCEAFF7 CAD TAB City of Carlsbad, CA Request for Proposals #20-13: CAD/Mobile Acquisition Computer Aided Dispatch Functional Requirements !Ability to enter comments of an unlimited length with a disposition I 593 code. C 594 I Report Initiation I Ability to notify responding officer whether a report is required I 595 b d d" . . d C ase on IsposItIon co e. 596 Ability to transfer call for service data to: 597 RMS l C 598 Report writing application ] C 599 Ability to transfer call for service data: 600 Upon transfer to dispatcher c 601 Upon incident closure C 602 On demand (i.e., manual initiation of transfer) N 603 CAD Incident Closure 604 Ability to close a call that does not require the dispatch of resources. I C Ability to enter a closing disposition code at the time of call creation 605 Ito avoid having the call appear in the pending queue (e.g., call is I N created and closed prior to the dispatching of resources). 606 I Ability to change an incident disposition after a call is closed, but I maintain a history of the original disposition. C 607 !Ability to clear more than one selected unit from an incident while I C leaving one or more selected units on the incident. 608 Ability to clear a single unit from an incident without clearing other I C assigned units from the incident. 609 Ability to clear multiple units without closing the incident. C 610 Ability to clear multiple units with a single disposition. C 611 I Ability to require a disposition prior to allowing a call to be closed. I C (bility to close an incident when the final unit is cleared from the I 612 . .d C IncI ent. 13 614 , application. Page 28 of 48
May 10, 2022 Item #11 Page 556 of 604DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7 CAD TAB City of Carlsbad, CA Request for Proposals #20-13: CAD/Mobile Acquisition Computer Aided Dispatch Functional Requirements Item# CAD Functional Requirements :esponse Cod Comments 615 Ability to select multiple map layers for display, limited only by the C number of available map layers. 616 Ability to display the following on the map: 617 Location of 9-1-1 caller C 618 Location of all pending and active 9-1-1 calls C 619 Incident location during address verification C 620 Units based on AVL or last known locations (regardless of status) C 621 Ability to select units to display on map by user-defined criteria including, but not limited to: 622 Beat C 623 Incident number C 624 Incident type C 625 Status C 626 Type C 627 Unit ID C 628 Ability to pull up a call for service and have it automatically show up C on the map. 629 Ability for users to prevent the map from automatically zooming to N an active call for service. 630 Ability to zoom in and center map display on: 631 Incident location during address verification C 632 CAD incident in active window C 633 Last known location of a selected unit (AVL or unit status) C 634 Vehicle activating emergency button C Ability to click on a unit and follow it on the CAD map at a user-635 defined zoom level and maintain the level of zoom as the CAD map C is updated. Ability to prevent the zoom level from automatically modifying 636 during an active incident (e.g., not automatically zooming out when C new units are added). 637 Ability to update unit status from the CAD map. C 638 Ability to click on an incident on the CAD map and review incident C information. Page 29 of 48
May 10, 2022 Item #11 Page 557 of 604DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7 CAD TAB City of Carlsbad, CA Request for Proposals #20-13: CAD/Mobile Acquisition Computer Aided Dispatch Functional Requirements 639 I Routing 640 Ability to provide directions to an incident from a unit's last known location or, if available, current location based on AVL. 641 I Ability to adjust routing recommendations based on closed streets. 642 I Ability for operational user to close streets by clicking on a specific area (e.g., street, hundred block area) from the CAD map. 643 I Ability for user to define an expected duration for street closures. 644 I Ability to alert user when the expected duration for a street closure has expired. 645 !Ability to push closed street information to mobile com.e_uters. 646 !Ability to push all map updates to the Mobile map. 'Ability to project anticipated response times between two points on 647 a map. 648 Ability for dispatcher to view the quickest route (based on time) from dis.E>_atched unit location to incident. Ability for dispatcher to view shortest route {based on mileage) 649 'from dis.E>_atched unit location to incident. I Ability to incorporate live traffic conditions into routing 650 d . recommen atIons. 651 652 Perimeters Ability to create perimeter locations by drawing a perimeter on the mappingpisplay. Ability to create a perimeter by identifying the location and requisite 653 I perimeter size (e.g., 300 yards around incident location) and have the perimeter location automatically generated. 654 655 Ability to display the drawn perimeter on the map and have it displayed for all responding units on their Mobile computers. _Ab_ility to dispatch units to perimeter locations. 656 !Ability for units to place themselves on a designated perimeter location. C C C C C C C C C C N C A C N N The user can click on the center of the circle to be drawn on the map then specify a radius, if needed. Page 30 of 48
May 10, 2022 Item #11 Page 558 of 604DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7 CAD TAB City of Carlsbad, CA Request for Proposals #20-13: CAD/Mobile Acquisition Computer Aided Dispatch Functional Requirements 657 !Ability to annotate the map. 658 !Ability for a user's annotated map to be shared with other users. 659 660 !Ability to support the use of a continuous, real-time AVL system. 661 662 663 Ability to support location technology outside of vehicle (e.g., on the personL device other than MDT-'-etc.). Ability to automatically refresh current vehicle location at aQency-d~fined time and/or distance intervals. Ability to alert agency defined users if AVL data is not successfully transferred at the aQency defined pollinQ rate. 664 !Ability to turn AVL on/off by: 665 !Agency 666 !Unit 667 IAbili~y to default to agency-defined defaults for dispatching when AVL IS turned off. 668 Ability to automatically mark a unit on-scene when it comes within a certain number of feet of the incident location. 669 !Ability for the agency to define what constitutes on-scene. 670 !Ability to prevent use of on-scene function if unit is not within an agency-defined radius of incident. 671 !Ability to log the specific X/Y coordinate from where the unit was dispatched prior to responding to an incident. C C N C C A A A C N N N A Supplemental location description can be identified to give further information about the incident location APX radios emergency, PremierOne Mobile AVL units can be filtered from the CAD map display by their agency, units, and vehicle es. AVL units can be filtered from the CAD map display by their agency, units, and vehicle es. As it pertains to automatically marking a unit on-scene, there are no provisioning options to define a unit as on-scene within a certain radius of the incident location. PremierOne CAD logs an AVL units X/Y coordinates based on the GPS reporting cadence. This data can be used to determine the unit's location around the time of dispatch, however likely not at the exact time. Page 31 of 48
May 10, 2022 Item #11 Page 559 of 604DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7 CAD TAB City of Carlsbad, CA Request for Proposals #20-13: CAD/Mobile Acquisition Computer Aided Dispatch Functional Requirements 672 !Ability to generate reports from AVL data, includin__g_: 673 !Vehicle route 674 I Speeds along the route 675 !Ability to provide an AVL playback utility based on: 676 IDate 677 ITime 678 !Unit 679 !Ability to export AVL playback data in common file type. 680 681 I Contractor Rotation List 682 I Ability to support an automated contractor rotation list. 683 I Ability fo~ the application ~o recommend a contractor based on any combination of the followin__g_: 684 I Equipment Required 685 I Type of tow 686 I Order in Rotation 687 I Incident Location 688 ITime of day (e.g., hours of operation) 689 !Agency 690 I Ability to automatically place a contractor at the end of the rotation list after selected for service. 691 692 693 694 695 Ability to assign a contractor based on: Date ran£,e Dav of month Time of day Ability to record that a contractor was selected from the service rotation list. 696 I Ability to recommend the next available contractor if the initial contractor Is unavailable. 697 I Ability to record reason why a contractor was not selected. 698 I Ability to record contractor response. 699 !Ability to temporarily remove a contractor from the list for an a_gency-defined len__g_th of time. C C C C C N C C C C C C C C N N N N C C C C The user is presented with a dropdown list of action codes for the proposed contractor. Page 32 of 48
May 10, 2022 Item #11 Page 560 of 604DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7 CAD TAB City of Carlsbad, CA Request for Proposals #20-13: CAD/Mobile Acquisition Computer Aided Dispatch Functional Requirements 700 I Ability to place contractor at top of list if incident is cancelled by the agency. 701 702 703 Ability_ to override contractor recommendation. Ability to entE!r a_c:ontractor that is not e_art of the rotation. Ability for all actions regarding the contractor rotation and selection to be associated with an incident record. 704 I Towe~_ Vehicle History 705 I Ability to attach tow history to a call for service record. 706 I Ability_ to document reason for the tow. 707 !Ability to associate multiple vehicles with a single tow incident. 708 I Ability to track the total number of vehicles towed per incident. 709 710 ICAD Reporting and Analysis 711 I Ability to provide a native reporting tool that can: 712 713 1create CAD reports based on multiple operational data fields in the CAD database 714 I Ability to generate the following standard reports from within the CAD ap£1icat1on: 715 I Incident analysis by day of week 716 I Incident analysis by hour of day 717 lincident analysis b_y day of week and hour of day 718 I Incident analysis b_y geographic area 719 I Incident analysis by shift 720 I Incident analysis by beat 721 I incident analysis by call type 722 I Incident analysis by dis_e_osition 723 I Incident analysis by workstation 724 lincident analysis by call-taker 725 I Incident analysis by dis_e_atcher 726 I incident analysis by priority code 727 I Incident analysis by geographic area by hour of day 728 I Incident analysis by unit 729 IBydispatcher: A C N C C C C C ·C C C C C C C C C C C C C C C The user must cancel the contractor before the incident is closed to put the contractor on the top of the list. Page 33 of 48
May 10, 2022 Item #11 Page 561 of 604DocuSign Envelope ID: EEOOOOEC-B19D-469F-887C-147E3BCEAFF7 CAD TAB City of Carlsbad, CA Request for Proposals #20-13: CAD/Mobile Acquisition Computer Aided Dispatch Functional Requirements Item# CAD Functional Requirements :esponse Cod Comments 730 Time from call receipt to call entry for all priority levels, by incident C number 731 Time from call entry to call dispatch for all priority levels, by C incident number 732 Time from dispatch to on-scene for all priority levels, by incident C number 733 By call center: 734 Time from call receipt to call entry for all priority levels C 735 Time from call entry to call dispatch for all priority levels C 736 Time from dispatch to on-scene for all priority levels C 737 By date range: 738 Time from call receipt to call entry for all priority levels C 739 Time from call entry to call dispatch for all priority levels C 740 Time from dispatch to on-scene for all priority levels C 741 False alarm reports C 742 Fractile reports C 743 Fractile reports by unit C 744 Processing time by method of call receipt C 745 Response times by geographic area C 746 Response times by type of call/priority C 747 Response times by original call destination C 748 Response times by assigned unit C 749 Total and average time on call -by day of week C 750 Total and average time on call -by geographic area C 751 Total and average time on call -by hour of day C 752 Total calls for service by: 753 Date or date range C 754 Disposition C 755 Time of day C 756 Location C 757 Total incidents by date by nature or disposition C 758 Any combination of the above C 759 Ability to provide an analytical tool that reviews workload by, but not limited to: Page 34 of 48
May 10, 2022 Item #11 Page 562 of 604DocuSign Envelope ID: EEOOOOEC-B19D-469F-887C-147E3BCEAFF7 CAD TAB City of Carlsbad, CA Request for Proposals #20-13: CAD/Mobile Acquisition Computer Aided Dispatch Functional Requirements Item# CAD Functional Requirements :esponse Cod Comments 760 Workstation N 761 Call taker/dispatcher N 762 Officer N 763 Ability to report on unavailability of field personnel resources. N 764 Ability to report on unavailability of equipment resources. N 765 Ability to account for unavailable resources in response time N calculations. 766 Ability to capture a snap shot, based on day and time parameters, C of: 767 A workstation C 768 General CAD system C Ability to generate, from within the CAD application, a daily listing of 769 incidents and personnel assigned to the incidents including, but not limited to: 770 Actual dispatch location C 771 Call taker/dispatcher ID C 772 Date/time received C 773 Disposition C 774 Field personnel name C 775 Field personnel ID C 776 Incident location C 777 Incident number C 778 Ability to print audit report of changes to incident records including: 779 Transaction type (deletion, edit, etc.) C 780 Unit ID C 781 Workstation/terminal ID C 782 Before and after value C Ability to generate a list of incidents to be shared with the public List of incidents can be generated and shared 783 C with public but would need clarification on based on agency-specific business rules. agency-specific business rules. 784 Ability to generate a report containing a summary of incidents for an C agency-defined period of time for distribution to the public. Page 35 of 48
May 10, 2022 Item #11 Page 563 of 604DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7 CAD TAB City of Carlsbad, CA Request for Proposals #20-13: CAD/Mobile Acquisition Computer Aided Dispatch Functional Requirements Item# CAD Functional Requirements :esponse Cod Comments 785 Ability to schedule a report to populate a public-facing site with N agency-defined incident data. 786 Ability to schedule a report with agency-defined incident data to be N automatically sent to an agency-defined set of users . 787 CAD Queries 788 Ability to query the following databases from within CAD: 789 RMS C 790 CLETS/NCIC C 791 DMV C 792 All databases simultaneously C 793 Ability for subject query returns to include associated photos, if available in the following databases: 794 RMS C 795 DMV C 796 CALPhoto C 797 Ability to query call for service records based on: 798 Date range C 799 Time range C 800 CAD Incident number C 801 Unit ID C 802 Officer name/ID C 803 Call taker ID· C 804 Dispatcher ID C 805 Reporting party name C 806 Person of interest C 807 Location C 808 Any location in an incident C 809 Block range for a location C 810 Radius from a location C 811 Polygon area from a location C 812 Any operational data element in the call for service record C 813 Any combination of the above C Page 36 of 48
May 10, 2022 Item #11 Page 564 of 604DocuSign Envelope ID: EEOOOOEC-B19D-469F-887C-147E3BCEAFF7 CAD TAB City of Carlsbad, CA Request for Proposals #20-13: CAD/Mobile Acquisition Computer Aided Dispatch Functional Requirements Item# CAD Functional Requirements :esponse Cod Comments Ability to populate the query mask with data in the incident record 814 without cutting and pasting (e.g., with a function key or one or two key strokes): 815 Person Information C 816 Vehicle Information C 817 Ability to automatically query all of the following databases upon single query of a name: 818 RMS (Master Indices) C 819 CLETS/NCIC C 820 DMV C 821 Ability to automatically query the license plate against the RMS, C DMV, LPR and CLETS databases when a unit is on a vehicle stop. 822 Ability to automatically run a registered vehicle owner upon return C of a license plate query. 823 Ability to query: 824 Initial call type C 825 Final call type C 826 Ability to query and view the following by any public safety boundary layer (beat, sector etc.): 827 Active calls C 828 Assigned calls C 829 Priority calls C 830 Waiting (pending) calls C 831 Ability to query unit history by any combination of: C 832 Date and time range (e.g., start and end date and time parameters) C 833 Call type C 834 Unit ID C 835 Badge number C 836 Ability to query resource availability by: 837 Dispatch group C 838 Geographic area (e.g., beat, sector) C 839 Special skills C Page 37 of 48
May 10, 2022 Item #11 Page 565 of 604DocuSign Envelope ID: EEOOOOEC-B19D-469F-887C-147E3BCEAFF7 CAD TAB City of Carlsbad, CA Request for Proposals #20-13: CAD/Mobile Acquisition Computer Aided Dispatch Functional Requirements 840 I Unit types (e.g., patrol units, investigations) 841 I Ability to query unit status by: 842 I Date and time range 843 I Dispatch g_roup 844 IBad_g_e number 845 !Geographic area (e.g., beat, sector) 846 I incident type 847 !Unit ID 848 I Unit types (e.g., patrol units, inv!!sti~ations) Ability to automatically attach query returns to the unit and/or 849 !incident history when a query includes reference to a unit or incident. 850 I Ability to sort query results by any criteria (e.g., most recent to oldest, by priority). 851 I Ability to attach query entries to a unit or incident history (e.g., CLETS entries). 852 !Ability to limit query returns to an a~ency-defined number. 853 I Ability_ to hyperlink query returns to incident records. 854 I Ability ~o att~ch query returns from external systems into the call notes via a single keystroke by: 855 I Attachment (file) 856 I Hyperlink 857 !Ability to send query results to a user's mobile application. 858 IAbili!Y_ to print query returns with a_sir,gLe_keystroke. 859 860 861 I General Messaginj_ Features 862 I Ability to support a messaging system that can transmit messages to and from mobile and deskto.2_ workstations. I Ability to send messages to a user who is not logged into CAD and 863 cache that message for retrieval when the user logs onto CAD. 864 · !Ability for message server to continuously attempt to deliver a messaQe until received and confirmed. C C C C C C C C C C C C C N N C C N C C C Page 38 of 48
May 10, 2022 Item #11 Page 566 of 604DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7 CAD TAB City of Carlsbad, CA Request for Proposals #20-13: CAD/Mobile Acquisition Computer Aided Dispatch Functional Requirements Item# CAD Functional Requirements :esponse Cod Comments 865 Ability to support a minimum of the following messaging functions to and from any CAD address: 866 Desktop-to-desktop messaging C 867 Desktop-to-dispatch messaging C 868 Desktop-to-unit messaging C 869 Unit-to-desktop messaging C 870 Unit-to-unit messaging C 871 Ability to display the following identifiers within a message: 872 Sender name/ID C 873 Sender date C 874 Sender time C 875 Sender workstation ID C 876 Receiver name/ID C 877 Receiver date C 878 Receiver time C 879 Receiver workstation ID C 880 Receiver unit ID C 881 Ability to assign a priority to a message (e.g., routine, urgent, C emergency). 882 Ability to change a priority assigned to a message (e.g., routine to C urgent or emergency). 883 Ability to store messages for later viewing. C 884 Ability to purge text messages after an agency-determined period of C time. 885 Ability for messages to be sorted by most recent or first received. C 886 Ability for agency to configure the display of emergency key C notification. 887 Sending Messages 888 Ability to create easily accessible agency defined message forms for C specific message types. 889 Ability to create, edit and save message groups. C 890 Ability to create a dynamic message group consisting of all logged on users. C Page 39 of 48
May 10, 2022 Item #11 Page 567 of 604DocuSign Envelope ID: EEOOOOEC-B19D-469F-887C-147E3BCEAFF7 CAD TAB City of Carlsbad, CA Request for Proposals #20-13: CAD/Mobile Acquisition Computer Aided Dispatch Functional Requirements Item# CAD Functional Requirements :esponse Cod Comments 891 Ability to send broadcast messages. C 892 Ability to reply all to broadcast messages. C 893 Ability to select a recipient from the unit status window within CAD. C 894 Ability for users to select an unlimited number of people as part of a message group. C 895 Ability to reply all to group messages. C 896 Ability for agency to define message character limitations. C 897 Ability to add to a message before forwarding to another user. C Ability to enter unlimited narrative with wrap-around feature. (If 898 characters are limited, indicate the maximum in the "comments" C section.) 899 Ability to automatically populate the "To" field on the message mask C when selecting recipients. 900 Ability to select recipient by: 901 Name C 902 Unit ID C 903 Badge Number A Badge number is not a dedicated field but could be searched from the Notes field. 904 Terminal ID C Ability to select a recipient by a single command to create a 905 message (e.g., double click on a logged on user and message screen C pops up). 906 Ability to attach files to messages, including but not limited to: 907 MS Office C 908 PDF C 909 JPEG C 910 AVI C 911 WAV C 912 MP3 C 913 MP4 C 914 Ability to embed photos in messages. C 915 Ability to set agency-defined file size limit. N 916 Ability to automatically compress and resize media to comply N with agency defined file size limits. Page 40 of 48
May 10, 2022 Item #11 Page 568 of 604DocuSign Envelope ID: EEOOOOEC-B19D-469F-887C-147E3BCEAFF7 CAD TAB City of Carlsbad, CA Request for Proposals #20-13: CAD/Mobile Acquisition Computer Aided Dispatch Functional Requirements Item# CAD Functional Requirements :esponse Cod Comments 917 Ability to send a message to all units handling a specific incident. C Ability to transmit a reply message to the originator of a currently 918 displayed message without having to reenter the originator's C address. 919 Ability to transmit a "reply all" message to multiple recipients that C were part of the originator's message group. 920 Ability to forward a message. C 921 Ability to create messages that are retained in the system and sent C at pre-specified times. 922 Ability to provide a notification for delivery of messages to the C device. 923 Ability to provide a notification for non-delivery of messages. C 924 Ability for a user to remove himself or herself from a message C thread. 925 Ability to recall an unread message. C 926 Receiving Messages 927 Ability to notify receiver via an audible and/or visual flag that a new C message has arrived in mailbox. 928 Ability to prevent incoming messages from interfering with current C work. 929 Ability to notify receiver of an unread message after an agency N defined time period. 930 Ability to notify receiver of total number of unread messages. C 931 Ability to provide a visual distinction between the following: 932 External messages N 933 General messages C 934 System messages N 935 Query returns C 936 Unread messages C 937 High priority messages C 938 Ability to move high priority messages to the top of a user's C message inbox. Page 41 of 48
May 10, 2022 Item #11 Page 569 of 604DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7 CAD TAB City of Carlsbad, CA Request for Proposals #20-13: CAO/Mobile Acquisition Computer Aided Dispatch Functional Requirements 939 I Ability to identify high priority messages by type of priority (e.g., felony warran!_return versus user-defined urgency). 940 IAbil!ty of the r_eceiving user to enter a single keystroke command to retrieve and display the messa_[e. 941 1Ability for messages to be queued in an "inbox" for later viewinQ at the convenience of users. 942 I Ability to query message logs by agency-defined criteria (e.g., date/time range, sender, recipient, device). 943 I Ability to note time o_e_ened/read by receiver. 944 !Ability to queue and display m~ssage waiting by priority. 945 !Ability to clear a message from the queue. 946 !Ability to retain a messaQe in the _g_ueue. 947 !Ability for supervisors to moni!<)_r_messa_g_es. 948 !Ability to search m-essaQes by keyword. 949 !Ability to establish messaQe data retention limits. Ability to establish different retention limits for messages 950 I containing different types of media (e.g., 9-1-1 recordings, video). 951 !Ability for supervisors to search messages by a text string (e.g., to identify inappropriate language us~) 952 I Ability to save message logs for an agency-determined period of time. 953 I Ability to purge message logs after an agency-determined period of time. 954 955 !CAD Table Maintenance 956 !Ability for CAD fields to default to agency-defined values. C C C C C C C C C C N N C A C F6 Message searches are by mailbox, date range, attachments, message text, subject, from address, to address, cc, bee, and labels. The saving of message logs is based on system provisioned mailbox folder sizes and 1t. The provisioning of default CAD fields does not apply to every available field on the incident form. For example, pertinent default codes can be provisioned for a Traffic Stop incident form or the call source code for E9-1-1 or non-emerQency line calls. Page 42 of 48
May 10, 2022 Item #11 Page 570 of 604DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7 CAD TAB City of Carlsbad, CA Request for Proposals #20-13: CAD/Mobile Acquisition Computer Aided Dispatch Functional Requirements Item# CAD Functional Requirements :esponse Cod Comments 957 Ability to include, at a minimum, the following data tables: 958 Call source (e.g., officer-initiated, 9-1-1, 10-digit) C 959 Call types and priorities C 960 Commands C 961 Command aliases C 962 Devices C 963 Dispositions C 964 Equipment C 965 Vehicle ID C 966 Event error logs (so vendor can identify and troubleshoot errors) C 967 Location C 968 Common place names C 969 Landmarks C Same as common places 970 Response plans N 971 Patrol and command area definitions N 972 Personnel, including emergency contact information and C Address Book current assignment 973 Series (incident number sequence, etc.) C 974 Street alias file N This is part of GIS 975 Table size N 976 Tow/contractor rotation C 977 Timers C 978 Unit status types (i.e., assigned, unassigned, assigned but available) C 979 Users C 980 Special skills C 981 Terminals C 982 Units C 983 ReportinQ District N 984 Beat (time-based) N 985 Agency-defined N 986 Ability to accommodate agency-defined unit identifiers. C 987 CAD Configuration Page 43 of 48
May 10, 2022 Item #11 Page 571 of 604DocuSign Envelope ID: EEOOOOEC-B19D-469F-887C-147E3BCEAFF7 CAD TAB City of Carlsbad, CA Request for Proposals #20-13: CAD/Mobile Acquisition Computer Aided Dispatch Functional Requirements Item# CAD Functional Requirements :esponse Cod Comments 988 Ability to configure commands (e.g., V = vehicle stop). C 989 Ability to create agency-defined data entry screens. N 990 Ability to configure the field entry sequence. N 991 Ability to configure status code colors. C 992 Ability to create conditional fields. N This capability is provided on a limited number of fields. 993 Ability to create mandatory fields. N This capability is provided on a limited number of fields. 994 Ability for agency to add data elements on any screen. N 995 Ability for agency to change data elements on any screen. N 996 Ability for agency to configure alerts: 997 Associated message displayed C 998 Aµdible indicator C 999 Visual indicator C 1000 Premise File Maintenance 1001 Ability to update/create CAD premise history files. C 1002 Ability to automatically update premise history when an incident occurs. C 1003 Ability to capture the following information when creating premise history: 1004 Date and time stamp C This information is not a dedicated field in the 1005 Date of incident A Premise Hazard record but can be added to the Comments field. This information is not a dedicated field in the 1006 Disposition A Premise Hazard record but can be added to the Comments field. This information is not a dedicated field in the 1007 Type of incident A Premise Hazard record but can be added to the Comments field. This information is not a dedicated field in the 1008 Incident number A Premise Hazard record but can be added to the Comments field. 1009 Narrative text of unlimited length (if limited, indicate maximum in C the "comments" field) · Page 44 of 48
May 10, 2022 Item #11 Page 572 of 604DocuSign Envelope ID: EEOOOOEC-B19D-469F-887C-147E3BCEAFF7 CAD TAB City of Carlsbad, CA Request for Proposals #20-13: CAD/Mobile Acquisition Computer Aided Dispatch Functional Requirements 1010 I Ability to capture and maintain specific premise information, including but not limited to the following:_ 1011 I Emergency contact information 1012 I Hazardous conditions (e.g., officer responder safety) 1013 !chemicals 1014 I Medical information 1015 !Agency defined premise information 1016 I Previous calls for service based on at least the followin_[: 1017 !Address/Location 1018 I contact information 1019 I Date and time 1020 I Incident number 1021 I Incident type Ability to capture and maintain specific premise information by 1022 I groups of addresses (e.g., all apartments in an apartment complex, all houses in a subdivision). Ability to capture and maintain specific premise information by 1023 I groups of addresses by polygon (e.g., all apartments in an apartment complex, all houses in a subdivision_)_. __ 1024 I Ability to store premise information for a specific apartment unit/suite number. 1025 I Ability to store premise information for an agency-defined length of time. 1026 I Ability to purge premise information from a location (e.g., if it is known that the tenant/owner generating the incidents has moved). 1027 I Ability to archive premise information from a location (e.g., if it is known that the tenant/owner generating the incidents has moved). C C A A A C C C C C C C C C C N This information is not a dedicated field in the Premise Hazard record but can be added to the Comments field. This information is not a dedicated field in the Premise Hazard record but can be added to the Comments field. This information is not a dedicated field in the Premise Hazard record but can be added to the Comments field. Premise hazard area are supported. Page 45 of 48
May 10, 2022 Item #11 Page 573 of 604DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7 CAD TAB City of Carlsbad, CA Request for Proposals #20-13: CAD/Mobile Acquisition Computer Aided Dispatch Functional Requirements Item# CAD Functional Requirements :esponse Cod Comments Ability to define valid date ranges for time limited premise A purge date can be provisioned for the time 1028 information at a given location (e.g., information valid between A limited premise information. 1 and ). 1029 Ability to restart archived premise file information. N 1030 Ability to archive expired premise file information. C 1031 Ability to include in a premise record the following information when premise information is added or changed: 1032 Expiration date C 1033 Unit ID of person entering information A The PremierOne CAD user ID is stored on the Premise Hazard record. 1034 Ability to attach files to a premise record (e.g., floor plans, building C diagrams, special instructions). 1035 Ability to access files attached to a premise record: 1036 In CAD environment C 1037 In Mobile environment C 1038 Hazard File Maintenance 1039 Ability to enter hazards associated with: 1040 Persons C 1041 Specific locations C 1042 Address ranges C This information is not a dedicated field in the 1043 Vehicles A Premise Hazard record but can be added to the Comments field. 1044 Ability to define an unlimited number of hazard types. C 1045 Ability to record with an entered hazard: 1046 Expiration date C 1047 Time and date stamp at time of entry C 1048 ID of person entering information C 1049 Ability to assign expiration dates to hazards. C 1050 Ability to create lists of hazards by category C 1051 Ability to search hazards by: 1052 Date range C 1053 Hazard type C 1054 Location C 1055 Location range C Page 46 of48
May 10, 2022 Item #11 Page 574 of 604DocuSign Envelope ID: EEOOOOEC-B19D-469F-887C-147E3BCEAFF7 CAD TAB City of Carlsbad, CA Request for Proposals #20-13: CAD/Mobile Acquisition Computer Aided Dispatch Functional Requirements 1056 !Ability to print hazards and hazard lists 1057 ICAD Notes File Maintenance I Ability to create an unlimited number of types of notes fields, 1058 . Id" b 1· . d me u mg ut not 1m1te to: 1059 I Gate codes-1060 I Utility phone number 1061 1062 1063 1064 1065 Ability for a communications supervisor to monitor system configuration and current staffing (e.g., who is signed-on, at what position, at what time, and with what responsibilities). __ _ Ability for a CAD workstation to be configured as a supervisor workstation upon logon of a user with a CAD supervisor _erofile. Ability for a supervisor to choose logon type (supervisor vs. dispatcher) upon workstation lo_g_on. 1066 I Ability for a communications supervisor to monitor activity on any user workstation. 1067 I Ability for supervisor to override actions taken by any other operator. 1068 IA_bility to notify dispatcher of any changes made by supervisor. !Ability to identify dispatch origin (e.g., dispatcher or dispatch 1069 . ) f d"f" . supervisor _o mo 1 1cat1ons. 1070 CAD Testing/Training_ Environment Ability to support a CAD testing/training environment that mirrors 1071 I • • • • the funct1onahty of the CAD production environment. 1072 I Ability to support a CAD testing/training environment that mirrors the configuration of the CAD production environment. 1073 !Ability to visually distinguish testing/training environments from _eroduction environments. 1074 !Ability to designate any production workstation as a training workstation based on user log on. 075 I Ability for testing and training to occur without impacting the 1 d . . pro uct1on environment. C C C C C C C C C C C C C C C C Page 47 of 48
May 10, 2022 Item #11 Page 575 of 604DocuSign Envelope ID: EEOOOOEC-B19D-469F-887C-147E3BCEAFF7 CAD TAB City of Carlsbad, CA Request for Proposals #20-13: CAD/Mobile Acquisition Computer Aided Dispatch Functional Requirements 1076 I Ability to update testing/training system with historical data from production system at agency defined intervals or upon demand. 1077 I Ability to support a separate test E911 connection (or a canned script of E911 information)._ 1078 !Ability to support a separate test mobile connection (or a canned script of mobile information). 1079 ICAD Recovery Ability to retain and display last-known unit and incident status 1080 lin the event of a catastrophic system failure (e.g., at the workstation, remote external logging device or similar solution). Ability to load incidents from the backup environment into the 1081 I production environment upon restarting system after a system failure. 1082 !Ability to reset numbering after CAD system has been restarted. 1083 I Ability to retain CAD numbering sequence after system has been restarted. Ability to add incidents retroactively independent of incident 1084 I number order or sequential time sequence (i.e., incident 15 may have occurred after incident 20) in the event that the CAD system is unavailable for a time. Ability to process retroactive incidents and assign incident numbers 1085 hn the same manner as new incidents; the supervisor can override the times associated with the incident. Ability to set aside a block of call for service numbers in the event of 1086 la catastrophic CAD failure to enable a manual workflow and tracking. __ 1087 I Ability to indicate in the audit trail that an incident was entered retroactively. !Ability to perform CAD catch-ups after system downtime, without 1088 requiring users to log back in. C N C N N C C C C C C C Incident update tool allows you to move from inc# to inc# and doesn't require you to go in order. Page 48 of 48
May 10, 2022 Item #11 Page 576 of 604DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7 MOBILE TAB City of Carlsbad, CA Request for Proposals #20-13: CAD/Mobile Acquisition Mobile Functional Requirements 2 3 4 5 6 7 8 9 10 11 12 13 14 Ability for the system to automatically refresh without user intervention_, as new information becomes available. Ability to receive call updates without moving the user out of the current screen bein_[ viewed. Ability to notify users that new information is available without automatically refreshing the call for service screen. Ability to log all mobile transactions with the following information: Agency Date and time of transmission Location Mobile Terminal ID User ID Vehicle ID Ability to provide a visual alert if Mobile application loses connection to CAD. Ability to provide application functionality if disconnected from the network, includin_g_J>_ut not limited to: Mobile map 15 I Dispatch commands 16 I Unit status updates 17 18 19 20 Self-initiated calls Ability to continuously attempt to reconnect to CAD system in the event connectivity is lost. Ability for users to pull software/files (e.g., code tables, updates) on demand. Ability to support an automatic download of software/files (e.g., code tables, updates) at logon. C C C C C C C C C C C C C C C C C Commands can be performed on the mobile device, but not received from CAD. Unit status can be changed on the mobile device, but will not be communicated to CAD. PremierOne Mobile updates can be executed based on the customers needs. User will get notified that updates are available and can acknowledge the update. The update will take place in the background without interfering with operational performance. Page 1 of 24
May 10, 2022 Item #11 Page 577 of 604DocuSign Envelope ID: EE0000EC-819D-469F-887C-147E3BCEAFF7 MOBILE TAB City of Carlsbad, CA Request for Proposals #20-13: CAD/Mobile Acquisition Mobile Functional Requirements Item# Mobile Data Computing Functional Requirements 21 Ability to schedule an automatic download of software/files (e.g., code tables, updates). 22 I Ability to provide functionality on the following mobile devices: 23 !Laptops 24 !Tablets 25 liOS 26 !Android 27 !Windows 28 lsmartphones 29 liOS 30 !Android Ability to integrate actions taken on handhelds into MDT (e.g., 31 I queries and returns performed on handheld appear on MDT when users return to vehicle~ 32 I Ability to accommodate the followin_[ screen orientations: 33 I Portrait 34 I Landscape 35 Ability for users to configure screen views, including but not limited to: 36 I Fu II screen 37 !Split sc_reen 38 lsin~e frame 39 I Multiple frames on a sin~e screen 40 I Multiple frames on multiple screens (e.g., extended display) 41 42 43 Ability for users to freeze hot call information on the Mobile screen (suspect car, name, photo) without being interrupted by call updates. Ability to provide a visual indication of a new call if a user is active in a different window of the Mobile application. Response Code C C C C C C C C C N C C C C C C C C C Comments PremierOne Mobile updates can be executed based on the customers needs. User will get notified that updates are .available and can acknowledge the update. The update will 'take place in the background without interfering with operational performance. PremierOne Mobile could be extended to another display, but the application can not be split to display on multiple Page 2 of 24
May 10, 2022 Item #11 Page 578 of 604DocuSign Envelope ID: EEOOOOEC-B19D-469F-887C-147E3BCEAFF7 MOBILE TAB City of Carlsbad, CA Request for Proposals #20-13: CAD/Mobile Acquisition Mobile Functional Requirements Item# Mobile Data Computing Functional Requirements Response Code Comments 44 Ability to maintain any work in progress (e.g., queries, updates to call notes, etc.) when: 45 User navigates away from page C 46 User is dispatched to a new call C 47 Ability to provide screen display formats that are consistent C across the application. 48 Ability for user to toggle between windows. C 49 Ability to view multiple windows at the same time (e.g., side by C side or cascade). so Ability for user to minimize or expand any window. C 51 Ability to support touch-screen functionality. C 52 Ability to support voice activated (voice command) functionality. N 53 Ability to support text-to-voice functionality. C 54 Ability to accept input from: PremierOne Mobile currently supports the Mag Stripe 55 3D barcode reader (e.g., driver's license, registration) N reader. PremierOne Mobile does not support requirement but could be considered for a future release. 56 Card swipe device C 57 Command entries on a command line C 58 Fingerprint reader N 59 Function keys (one touch keys) C 60 Point-and-click devices (i.e., mouse, trackball, touch pad) C 61 Ability for users to configure the display of their Mobiles, including: 62 Font color C 63 Font size C 64 Window size C 65 Window location C 66 Day/Night mode C 67 Ability to configure a default for the following application settings: 68 Audible message C 69 Audible tones C 70 Color C Page 3 of 24
May 10, 2022 Item #11 Page 579 of 604DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7 MOBILE TAB City of Carlsbad, CA Request for Proposals #20-13: CAD/Mobile Acquisition Mobile Functional Requirements 71 72 73 74 75 Ability to switch to/from Day/Night mode with one function key. Ability to completely black out mobile application screen. Ability to switch to/from blackout mode with one function key. Ability to store a user profile for mobile display configuration for auto-configuration upon lo_[ on. Ability to store multiple user profiles based on device (e.g., CF-33, CF-20, etc,l. Ability for users to create a user-defined summary of call information to appear prominently at the top of the screen for 76 lthe duration of a call (e.g., anytime a suspect description is included, it would appear at the top of the screen if the user has selected that field). 77 78 79 80 81 82 83 84 85 86 87 88 89 Ability to allow users to return to application default settings. Ability for users to select a configuration scheme that accommodates color-blindness. Ability to support multiple on-screen button configurations (e.g., left side, right side, top or bottom). Ability to cut and paste from one application or window to another. Ability to configure the screen display with a combination of any of the following_ information during normal oe~ations_: Availability of wireless connectivity_ Call status Communication verification and other Mobile operational status indicators Current unit Current unit status (regardless of who assigned the updated statusl Current s_ystem date and time Incident number Case number (if provided) C N N C N N C C C C C C C C C C C C 1The incident summary screen· can be modified by the System Administrator to meet the agencies needs. Page 4 of 24
May 10, 2022 Item #11 Page 580 of 604DocuSign Envelope ID: EE0000EC--B19D-469F--887C--147E3BCEAFF7 MOBILE TAB City of Carlsbad, CA Request for Proposals #20-13: CAD/Mobile Acquisition Mobile Functional Requirements 90 91 92 93 94 95 96 97 98 99 100 101 Messa.[e alert Radio talk group (if assigned) Screen name/descri_IJ_tion Unit ID User ID User name Vehicle location Ability to view multiple calls simultaneously (e.g., in different windows 1. Ability for user to configure how data is displayed (e.g., incident screen_,_ unit screen), including but not limited to: Sus_e_ect information Location information Premise history 102 I Vehicle descri_IJ_tion 103 !Ability to configure the unit status screen display, including but not limited to: 104 I Filter by workgroup (patrol traffic, etc.) 105 I sort by workgroup 106 I Filter by uni! status 107 I sort by unit status I 108. ~Ability to notify users that a software update is available for manual download. 1----1-109 110 111 112 113 114 llS 116 117 Ability to support single keystroke commands. Ability to define sub-menus for buttons and function keys so they are based on legacy commands. Ability for agency to define keystroke shortcuts for: Common tasks (e.g., copy/paste) Status U_IJ_dates Form retrieval (e.g., NClf call disposition) Ability to configure a Mobile button (tool bar or function key)_to launch any third-party program (e.g., MS Word). C N C C C C C C C C C C C C C C C C C C C C C Page 5 of 24
May 10, 2022 Item #11 Page 581 of 604DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7 MOBILE TAB City of Carlsbad, CA Request for Proposals #20-13: CAD/Mobile Acquisition Mobile Functional Requirements 118 !Ability to initiate an emergency message transmission from a touch screen button or hot key. 119 I Ability to automatically transmit the following information to agency-defined groups in an emergency situation: 120 I Last known location 121 I current location (with AVL) 122 I Current location (with GPS using smartphone) 123 I Reference to incident 124 I user ID 125 I User name 126 I Closest unit to the unit activating the emergency key 1Ability to configure emergency key to capture agency defined 127 combination of above information. Ability to present the user initiating the emergency key with a 128 !visible and audible indication that emergency key has been activated prior to broadcast to other users. 129 130 131 132 Ability to delay emergency key activation by an agency defined period of time (e.g., two second pause before activation to allow personnel to deactivate key if necessary). Ability for Agency to configure where the emergency button appears on the screen (e.g., fixed or floating). Ability for dispatch to select which consoles receive visible/audible alerts of emergency key activation. Ability to send to all Mobile and CAD users (except the sender) an emergency notification with unit ID and location (if known) when the emergency key is activated. 133 !Ability to prevent emergency notification from appearing on the sender's screen. 134 I Ability for the following users to cancel activation of the emergency key: 135 I User that initiated the emergenc_y_key 136 I Dis.e_atcher 137 I Ability for the Mobile screen to revert to its prior view after the user dismisses an emergency message. C C C C C C C C c· C C C C C C C C C Page 6 of 24
May 10, 2022 Item #11 Page 582 of 604DocuSign Envelope ID: EEOOOOEC-819D-469F-887C-147E3BCEAFF7 MOBILE TAB City of Carlsbad, CA Request for Proposals #20-13: CAD/Mobile Acquisition Mobile Functional Requirements 138 I Ability to automatically send location coordinates and unit ID upon triggenngan emergency key. Ability for system administrator to turn off emergency key 139 I functionality b_y: 140 !Agency 141 !Device 142 143 144 I Ability to require both user identification and password to logon. 145 !Ability to support a single password sign-on to CAD, the Mobile and the operatinQ system. 146 I Ability to require any agency-determined combination of the following information to logon to the Mobile application: 147 !Equipment 148 I Password 149 !Unit ID 150 !Radio ID(s) 151 I Status (e.g., in service, out-of-servicel 152 IA[ency-defined 3 I Ability for agency to set the time a Mobile can remain inactive 15 before automatically logging out the user. 154 155 I Ability for agency to define logon requirements (e.g., what data is required at time of logon). Ability to support multiple individuals or roles at logon (e.g., FTO, multi-officer vehicle, etc.) 156 IAbili_ty for a resource to be logged on but not available for service. 157 tbility for a unit logged on to automatically default to "available" status. Ability to save data entered into user logon fields that remains 158 lthe same from session to session (e.g., all information other than password). C C C C C N N C C C C C C C C C C Not operating system PremierOne Mobile requires minimum fields for entry upon logon, but this list can be expanded to meet agency needs. Page 7 of 24
May 10, 2022 Item #11 Page 583 of 604DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7 MOBILE TAB City of Carlsbad, CA Request for Proposals #20-13: CAD/Mobile Acquisition Mobile Functional Requirements 15 I Ability for a user to logoff the system and save information on 9 the Mobile includin~ 160 I I n-pro_gr~s_s _reports 161 I Messa~es 162 !Notes 163 louery_returns 164 !Ability to store the following until manually deleted by the user: 165 I In-progress reports 166 I Messages 167 !Notes 168 louery_returns I Ability to support a user-initiated download of software/files at 169 I · h · f · · h . I rf ogon wit out inter enng wit operat,ona pe ormance. 170 I Ability to support an automatic download of software/files at logon without interfering with operational performance. 171 I Ability to separate Mobile logoff from designating status as off-shift. 172 173 Ability for agency to define logoff requirements (e.g., what data is required at time of lo_[off). Ability to automatically notify CAD of logon/logoff. 1 174 (bility fo_r_ users to be logged onto multiple mobile sessions s,multane_cJusly. 175 176 !Ability to view all incident information available in CAD on the Mobile. 177 !Ability for Mobile users to view all AVL data available in CAD. 178 !Ability to provide the same messaging features as the CAD application. 179 IAbilit\' for mobile status updates to be reflected in CAD. 180 !Ability to receive dispatch alerts and/or indicators without losing current work. C C C C C This information is retrievable via PremierOne CAD C This information is retrievable via PremierOne CAD C This information is retrievable via PremierOne CAD C This information is retrievable via PremierOne CAD C C C C C C C C C C C Page 8 of24
May 10, 2022 Item #11 Page 584 of 604DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7 MOBILE TAB City of Carlsbad, CA Request for Proposals #20-13: CAD/Mobile Acquisition Mobile Functional Requirements in CAD to be bile environment. ing 184 !General Messaging Features 185 I Ability to support a messaging system that can transmit messages to and from mobile and desktop workstations. I C 186 Ability to display the following identifiers within a message: 187 Sender name/ID C 188 Sender date C 189 Sender time C 190 Receiver name/ID C 191 Receiver date C 192 Receiver time C Ability to send messages to a user who is not logged into the 193 I mobile device and cache that message for retrieval when the I C user logs on. !Ability to store and forward messages transmitted or received if I 194 k . . . ·1 I networ connect1v1ty 1s temporan y ost. C 9 !Ability to centrally log when a terminal is off network and where I 1 5 it was disconnected (to understand blackout areas in the City). N I Ability for message server to continuously attempt to deliver a 196 ·1 · d d f d message unt1 receive an con 1rme . I C 197 !Ability for user to retrieve cached messages upon logon. I C 198 I Ability to assign a priority to a message (e.g., routine, urgent, emergency). I C 199 Ability to change a priority assigned to a message (e.g., routine I C to urgent or emergency). 200 Ability to store messages for later viewing. I C 201 I Ability for messages to be sorted by most recent or first received. I C Page 9 of24
May 10, 2022 Item #11 Page 585 of 604DocuSign Envelope ID: EEOOOOEC-B19D-469F-887C-147E3BCEAFF7 MOBILE TAB City of Carlsbad, CA Request for Proposals #20-13: CAD/Mobile Acquisition Mobile Functional Requirements Ability to alert users of agency-defined keywords or hot words 202 !included in a message requiring the user to validate prior to I N sending (e.g. message includes "gun"). 203 Ability for authorized users to cancel non-CLETS/NCIC text message returns. I C 204 Sending Messages 205 I Ability to create easily accessible agency defined message forms I for specific message types. C 206 I Ability to create and save message groups. I C 207 I Ability to create a dynamic message group consisting of all logged on Mobile users. I C 208 !Ability to send broadcast messages to all users. I C 209 !Ability for users to select an unlimited number of people as part I of a message group. C 210 ]Ability for field users to create unique groups. C 211 Ability for field users to save unique groups to the user's N refile. 212 Abilit for agenc to define messa e character limitations. N 213 !Ability to enter unlimited narrative with wrap-around feature. C 214 1Ability to add to a message before forwarding to another user. I C 215 Ability to automatically populate the "To" field on the I C messaqe mask when selecting recipients. 216 Ability to select recipient by: 217 Name C 218 Group C 219 Call signs C 220 Unit ID C 221 Badge Number C Ability to select a recipient by a single command to create a 222 I message (e.g., double click on a logged on user and message I C screen pops up). 223 Ability to attach files to messages. C 224 Ability to embed photos in messages. C Page 10 of 24
May 10, 2022 Item #11 Page 586 of 604DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7 MOBILE TAB City of Carlsbad, CA Request for Proposals #20-13: CAD/Mobile Acquisition Mobile Functional Requirements 225 !Ability to set agency-defined file size limit. 226 I Ability to automatically compress and resize media to comply with agency defined file size limits. 227 I Ability to send a message to all units handling a specific incident. 228 229 230 Ability to transmit a reply message to the originator of a currently displayed message without having to reenter the or~nator's address. !Ability to transmit a "reply all" message to multiple recipients 1that were part of the originator'sl'l1~ssage group. Ability to forward a messa_[e. 231 !Ability to create messages that are retained in the system and sent at pre-sJ)ecified times. 232 I Ability to provide sender with a notification for delivery of messa_[es to the device. 233 !Ability to provide a notification to sender for non-delivery of messa_[es. 234 235 236 Ability to provide a voice message functionality (e.g., messaging application records sender's voice and transmits the message as voice to recipient). Receiving Messages Ability to notify receiver via an audible and/or visual flag that a new messa_[e has arrived in mailbox. 237 I Ability to prevent incoming messages from interfering with current work. !Ability to notify receiver of an unread message after an agency 238 defined time _e_eriod. 239 !Ability to notify receiver of total number of unread messages. 240 !Ability' to provide a visual distinction between the followin_[: 241 !General messag_es C C C C C C C C C N C C C C C Each agency may define Send and Receive size limitation on PremierOne Mobile messages. This size limitation is applied to the entire message, not just the attachment. Each agency may define Send and Receive size limitation on PremierOne Mobile messages. This size limitation is ~pplied to Jhe e_ntire messa~e. not just the attachment. Page 11 of 24
May 10, 2022 Item #11 Page 587 of 604DocuSign Envelope ID: EEOOOOEC-B19D-469F-887C-147E3BCEAFF7 MOBILE TAB City of Carlsbad, CA Request for Proposals #20-13: CAD/Mobile Acquisition Mobile Functional Requirements 242 !System messages 243 I Query returns 244 I Unread messag_es 245 !Ability to identify high priority messages by type of priority (e.g., ' felony warrant return versus user-defined urgency). 246 I Ability of the receiving user to enter a single keystroke command to retrieve and display the message. 247 !Ability for messages to be queued in an "inbox" for later viewing at the convenience of users. 248 I Ability for authorized users to query message logs by agency-defined criteria (e.g., date/time range, sender, recipient, device). 249 I Ability to note time opened/read by receiver in the message log. 250 I Ability to note time delivered in the message log. 251 !Ability to queue and display message waiting by priority. 252 !Ability to clear a message from the queue. 253 I Ability to retain a message in the _g_ueue. 254 255 256 257 258 Ability for supervisors torr1_011itor messa_ges. Ability to search messages by keyword. Ability to establish messa_g_e data retention limits. Ability to establish different retention limits for messages containing different types of media (e.g., 9-1-1 recordings, video). Ability for authorized users to search messages by a text strini:i (e.Q._,_ to identify inappropriate lani:iuai:ie use). 259 I Ability to save message logs for an agency-determined period of time. 260 IAbil_itY to purge message logs after an agency-determined period oft1me. 261 262 !Ability for map to function without wireless connectivit_'l: 263 !Ability to manage map layers to minimize the amount of data transmitted wirelessl_'l 264 !Ability to support AVL functionality. C C C C C This is a button or Function key C C C C C C C C C N N N C C C C C Page 12 of 24
May 10, 2022 Item #11 Page 588 of 604DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7 MOBILE TAB City of Carlsbad, CA Request for Proposals #20-13: CAD/Mobile Acquisition Mobile Functional Requirements Item# Mobile Data Computing Functional Requirements Response Code Comments 265 Ability to update unit and incident locations on map without C resetting the entire map. 266 Ability for map to function in the background and not supersede C other applications. 267 Ability to display compass direction between two user selected C points. Ability to configure map to dynamically turn and zoom in while 268 getting closer to destination based on location and direction of C the vehicle. 269 Ability for user to configure map to remain static and point north C based upon directions. 270 Ability to maintain incident location identifier on the map until C an agency-defined action (e.g., unit arrives on-scene, etc-.) 271 Ability to select n:iap layers for display (Satellite imagery, LPR C layers, etc.). 272 Ability for Mobile map to display the same common places that C exist in CAD. 273 Ability to display the following information on the map: 274 Active incidents C 275 User's location C 276 Location of other field units C 277 Unit statuses C 278 Ability to click on a unit or incident in the incident queue or unit C status bar and have it displayed on the map. 279 Ability to center map display on: 280 Current vehicle location (with AVL) C 281 Midpoint between vehicle location and incident location N 282 Dispatch location C 283 Vehicle activating emergency activation key C 284 Specified geographic area (e.g., entering an address via N text entrv) 285 Incident location C 286 Ability to filter display by: 287 Unit type C Page 13 of 24
May 10, 2022 Item #11 Page 589 of 604DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7 MOBILE TAB City of Carlsbad, CA · Request for Proposals #20-13: CAD/Mobile Acquisition Mobile Functional Requirements Item# Mobile Data Computing Functional Requirements Response Code Comments 288 Unit status C 289 Incident type C 290 Incident priority C 291 Incident number C 292 Ability to use touch screen for pinch-to-zoom feature. C 293 Ability to automatically zoom to the call location upon dispatch C receipt. Ability to prevent the zoom level from automatically modifying 294 during an active incident (e.g., not automatically zooming out C when new units are added) Ability to access agency-generated files (e.g., apartment complex 295 map, mobile home map, school map, mall map) upon clicking on C Premise hc:izards are accessible via the mobile map. the associated location on the map. : 296 Ability to display historic incidents on the map. C 297 Ability to display full address on a map. C 298 Ability to click on a unit or incident in the incident queue or unit status bar and have it displayed on the map. 299 Ability to display both unit location and incident location on the C map upon dispatch receipt. 300 Ability to auto zoom as unit approaches incident location to C display more detailed map information (e.g., street names). 301 Ability for mapping client to load automatically upon system C boot. 302 Ability to make temporary marks on map (e.g., to note locations N of a perimeter). 303 Ability to share temporary marks on map with field units, including but not limited to: 304 Freestyle lines N 305 Stylus N 306 Pins N 307 Arrows N 308 Agency-defined icons N 309 Routing Page 14 of24
May 10, 2022 Item #11 Page 590 of 604DocuSign Envelope ID: EEOOOOEC-B19D-469F-887C-147E3BCEAFF7 MOBILE TAB City of Carlsbad, CA Request for Proposals #20-13: CAD/Mobile Acquisition Mobile Functional Requirements Item# Mobile Data Computing Functional Requirements Response Code Comments 310 Ability to automatically provide route from user's current C location (on Mobile using AVL) to dispatched location. 311 Ability to display block numbers. N 312 Ability to provide route from user's current location (on Mobile C using AVL) to user selected point on the mobile map. 313 Ability to provide audible routing information. C 314 Ability to provide text-based routing information. C 315 Ability to toggle on/off audible routing. C 316 Ability to toggle on/off text-based routing. C 317 Ability to support quickest-time routing for all dispatches. C 318 Ability to support shortest route for all dispatches. C 319 Ability to provide estimated travel time. C 320 Ability to highlight on the map the recommended route from C current location to a dispatched incident site. Ability to suggest multiple routes if other routes are within an 321 agency-defined time period (e.g., suggest multiple routes if C within .5 minutes) 322 Ability to recalculate directions to incident/specified location on C the fly. 323 Ability to take into account the following when calculating routing directions: 324 Street speed limits C 325 Closed streets C 326 Dispatch entered obstacles C 327 Mobile user entered obstacles C 328 Distance between vehicle and incident location C 329 Height limitations on overpasses C 330 Current traffic conditions 331 Ability for Mobile user to turn recommended route feature C on/off. 332 Ability to clearly display potential obstacles along route. C Road closures as an example are clearly indicated on the mao. Page 15 of24
May 10, 2022 Item #11 Page 591 of 604DocuSign Envelope ID: EE0000EC-B19O-469F-887C-147E3BCEAFF7 MOBILE TAB City of Carlsbad, CA Request for Proposals #20-13: CAD/Mobile Acquisition Mobile Functional Requirements Ability to record all routing displays within CAD (e.g., map 333 I displays, travel time, travel time estimation, etc.) for analysis to improve routing logarithms. 334 Ability to automatically rotate and zoom map so that unit is automatically displayed moving the same direction. 335 336 I Ability to view all active calls in a sin~e window. 337 !Ability to view all pending calls in a single window. 338 I Ability to sort calls from highest priority to lowest priority. 339 IAbility_t_o view unit status by: 340 !Assigned territory (beat, d~trict, etc.) 341 Individual unit ------342 343 Ability to open any active incident to view dispatch data, units and incident notes. 344 !Dispatch Receipt 345 !Ability to receive dispatches on the Mobile. 346 !Ability for dispatched calls for service to open automatically on mobile computers. 347 !Ability to alert mobile users that a new dispatch has arrived: 348 !Audible alert 349 I Visual alert 350 I Ability to acknowledge disf)atch without losin~ current work. 351 1Ability to bring dispatch to forefront of the application without losin~ current work. 352 I Ability to receive dispatches on multiple mobile telecommunications devices including, but not limited to: 353 I Mobile computers 354 I smart phones 355 liOS 356 !Android 357 !Tablets N N C C C C C C C C C C C C C C C C C PremierOne offers ARL Playback, and stores the ETA of routes with CAD recommendations. PremierOne does not store travel times. Travel times can calculated using Unit History or ARL Playback and calculating the time between En Route and Arrival Statuses for a specific unit using the PremierOne Reporting Services. PremierOne Mobile does not support this requirement but could be considered for a future release. Page 16 of 24
May 10, 2022 Item #11 Page 592 of 604DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7 MOBILE TAB City of Carlsbad, CA Request for Proposals #20-13: CAD/Mobile Acquisition Mobile Functional Requirements Item# Mobile Data Computing Functional Requirements Response Code Comments 358 iOS C 359 Android C 360 Windows C 361 Ability for all personnel dispatched to an incident to receive C notification when other personnel are en route. Ability for all personnel dispatched to a call to receive 362 notification of status and location changes of other personnel C dispatched to the call. 363 Ability for Mobile users to add themselves to an incident. C 364 Ability to alert Dispatch when Mobile users add themselves to an C incident. 365 Ability to access and read all call comments associated with a call C regardless of whether assigned to the call. Ability to display the following information in distinct fields or 366 tabs (as opposed to in the call narrative) upon receipt of dispatch: 367 Assisting unit(s) C 368 Comments/narrative (unlimited) C 369 Date and time incident entered C 370 Driver registration information C 371 Dispatch Time C 372 Incident location with cross streets C 373 Incident priority C 374 Incident type C 375 Caution notes/hazard information C 376 Incident talk group N 377 Number of previous calls at a specific location (e.g., Building 10, C Apartment 3) 378 Number of previous calls within a radius of a specific location C (e.g., Buildings 10, 11 and 12). 379 Phone number at incident location (if different) C 380 Pre-plan information C 381 Primary unit assigned C 382 Recommended route C Page 17 of24
May 10, 2022 Item #11 Page 593 of 604DocuSign Envelope ID: EEOOOOEC-B19D-469F-887C-147E3BCEAFF7 MOBILE TAB City of Carlsbad, CA Request for Proposals #20-13: CAD/Mobile Acquisition Mobile Functional Requirements 383 I Reporting party information (e.g., name, phone, address) 384 I suspect information 385 I Premise information 386 I System _[enerated incident number 387 I weapons involved 388 !Agency-defined 389 l~bility to_ directly access (e.g., hyperlink, drill down) p~evious call information related to the address of the call for service. 390 I Incident Updates 391 I Ability to display most current incident data at the top of the screen without requirin_[ the user to scroll. Ability to receive supplemental incident information (e.g., 392 I location, suspect, vehicle information) without interrupting or overlayin_[ current screen. Ability for supplemental information to be visually distinct from 393 I information previously received by Mobile user (e.g., separate font color, highlighted). ----394 l~bility to transmit status information to the CAD system in real time. 395 I Premise and Hazard Information I Ability to alert user of availability of information associated with 396 a location (gate codes, hazards, premise history, pre-plans, etc.). Ability to indicate type of information that is attached to a call 397 l(e.g., gate code, hazard) so that user can decide whether or not to retrieve the information. 398 Ability for field units to have the option of pulling up or not pulling up information attached to the call. I Ability to drill down in premise history to find links to incidents, 399 h' I persons, ve ,c es, etc. I Ability to drill down in premise proximity history to find links to 400 . 'd h' I inc, ents, persons, ve ,c es, etc. 401 I Self-Initiated Calls for Service C C C C C N C C C C C C C C C C Page 18 of 24
May 10, 2022 Item #11 Page 594 of 604DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7 MOBILE TAB City of Carlsbad, CA Request for Proposals #20-13: CAD/Mobile Acquisition Mobile Functional Requirements Item# Mobile Data Computing Functional Requirements Response Code Comments 402 Ability to initiate a call for service from the Mobile, including: 403 Call for service C 404 Traffic stop C 405 Subject stop C 406 Non-enforcement activity (e.g. training, field Inspections) C 407 Other agency defined call types. C 408 Ability to initiate a call for service with a function-key. C 409 Ability to auto populate incident location on field initiated calls for service with unit's location, including but not limited to: 410 X/Y coordinates C 411 Cross-streets C 412 Ability to override the auto-populated incident location to a C location other than the unit's location. 413 Ability to geovalidate auto populated location information on ·c field initiated calls for service. 414 Ability for field initiated calls for service to update: 415 Premise history C 416 Unit history C 417 Subject record C 418 Vehicle record C 419 Ability for users to indicate that they are currently out of their C vehicle, but otherwise available for dispatch. 420 Perimeters 421 Ability to receive suggested perimeter positions from dispatch. N 422 Ability for suggested perimeter positions to appear mobile map upon receipt. N 423 Call Disposition 424 Ability to clear calls from the Mobile. C 425 Ability to require a call clearance code in order to clear a call C from the Mobile. 426 Ability to select disposition code from a drop-down list. C Page 19 of 24
May 10, 2022 Item #11 Page 595 of 604DocuSign Envelope ID: EEOOOOEC-819D-469F-887C-147E3BCEAFF7 MOBILE TAB City of Carlsbad, CA Request for Proposals #20-13: CAD/Mobile Acquisition Mobile Functional Requirements 27 428 429 430 bility to provide a text field for disposition comments. Ability to limit the potential disposition codes that could be applied to close_ a call based on call t_',tpe. Ability for system to reject a disposition if unsuitable for the 431 I General Queries 432 1Ability to query the following systems from the mobile com_e_uter: 433 ICAD 434 IRMS 435 ICLETS/NCIC 436 IDMV 437 I Crossroads accident reporting/e-citations 438 ILPR 439 I Regional Registrants (NetRMS) 440 ICOPLOGIC DORS I Ability to search and query all appropriate databases without 441 · · rf f b'I d' h . impacting pe ormance o mo I e 1spatc operations. 442 I Ability to query and retrieve premise information for an address not associated with a call for service. 443 I Ability to initiate que_ries with a single key stroke~ 444 1Ability to use predefined data entry forms/screens ('masks) to minimize data transmitted durin_[ queries. 445 I Ability for agency to create standard query screen formats (masks). Ability to scan imitate a query and populate data in a query mask 446 !through input from third party devices, including but not limited to: 447 IDL Swipe 448 13D barcode scanner C C C C C C, C C C C C C C C C C C N Motorola Solutions has included an interface to meet this requirement. Motorola Solutions understands this requirement to be ALPR, whi_c:tl we have provided an interface for. Motorola Solutions has included an interface to meet this requirement. Motorola Solutions has included an interface to meet this requirement. Motorola Solutions has included this interface. Page 20 of24
May 10, 2022 Item #11 Page 596 of 604DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7 MOBILE TAB City of Carlsbad, CA Request for Proposals #20-13: CAD/Mobile Acquisition Mobile Functional Requirements Item# Mobile Data Computing Functional Requirements Response Code Comments 449 Ability to provide pre-defined data entry/query forms, including, but not limited to: 450 Accident Investigation C 451 Driver license query C 452 Incident status C 453 Location C 454 License plate query C 455 Logon/logoff C 456 Missing person information C 457 Name query C 458 Premise information query C 459 Previous events C 46.0 Ability to access query forms by: 461 Command line entry C 462 Drop down menus C 463 Configurable buttons on screen C 464 Dedicated function keys C 465 Ability to cache previous queries based on user profile. C 466 Ability to purge historical queries. C 467 Ability to purge historical query results. C 468 Ability to indicate which fields are required for multi-C database query requests. 469 Ability to reformat date from query screens to databases C 1queried to meet the required format for each database. 470 Unit History Queries 471. Ability to query unit history detail by: 472 Date and time range (i.e., start and end dates or times) C 473 Badge Number C 474 Unit ID C 475 First Name C 476 Last Name C 477 Incident Queries 478 Ability to query and retrieve incident records by one or more of the following factors: 479 Any operator ID associated with the incident C Page 21 of 24
May 10, 2022 Item #11 Page 597 of 604DocuSign Envelope ID: EE0000EC-B19O-469F-887C-147E3BCEAFF7 MOBILE TAB City of Carlsbad, CA Request for Proposals #20-13: CAD/Mobile Acquisition Mobile Functional Requirements Item# Mobile Data Computing Functional Requirements Response Code Comments 480 Any unit ID assigned to the incident C 481 Beat C 482 Caller phone number C 483 Caller name C 484 Call type C 485 Case exists (Y/N) C 486 Case number C 487 Incident comments C 488 Incident narrative C comments search available 489 Involvements N 490 Cross streets C 491 Date and time range (e.g., start and end data and time C parameters) 492 Dispatch operator C 493 Dispatch terminal C 494 Disposition codes C 495 Unit ID "c 496 Personnel ID C 497 Primary unit C 498 Entry operator C 499 Entry terminal C 500 Geographic area (e.g., area, beat) C 501 User defined radius from a location N 502 Incident number C 503 Incident priority C 504 Incident type C 505 License plate C 506 Location or partial location C 507 Name (suspect, reporting party, witness, victim) C 508 Census tract N 509 license Plate Queries 510 Ability to query the license plate against the following databases: 511 RMS C Page 22 of 24
May 10, 2022 Item #11 Page 598 of 604DocuSign Envelope ID: EEOOOOEC-B19D-469F-887C-147E3BCEAFF7 MOBILE TAB City of Carlsbad, CA Request for Proposals #20-13: CAD/Mobile Acquisition Mobile Functional Requirements Item# Mobile Data Computing Functional Requirements Response Code Comments 512 DMV C 513 CLETS C 514 Ability to conduct multiple license plate searches simultaneously. C 515 Ability to run the registered owner of the vehicle in a license C plate query return. 516 Ability to identify the number of times a license plate has been C queried. 517 Firearms Queries 518 Ability to query firearms against the following databases: 519 RMS C 520 AFIS C 521 Article/Property Queries 522 Ability to query property against the following databases: C 523 CLETS C 524 CAPSS C 525 Vehicle Queries 526 Ability to query vehicles against the following databases: C 527 DMV C 528 svs C 529 NCIC C 530 Person Queries 531 Ability to query people against the following databases: C 532 LEDS C 533 CLETS/NCIC C 534 RMS C 535 Query Returns 536 Ability to save all query returns until user clears data. C 537 Ability to save all stored query returns after logoff (e.g., returns C are still there the next time user logs onto the system). Ability to produce an alert when a query return contains a record 538 marked as potentially hot (e.g., contains agency-defined keywords such as stolen, wanted, missing): Page 23 of 24
May 10, 2022 Item #11 Page 599 of 604DocuSign Envelope ID: EE0000EC-B19O-469F~887C-147E3BCEAFF7 MOBILE TAB City of Carlsbad, CA Request for Proposals #20-13: CAD/Mobile Acquisition Mobile Functional Requirements 539 ,Audible alert I C C 540 Visual alert Ability for mobile query returns to appear on dispatcher's screen 541 las well as the mobile computer screen if the return contains an I C agency-defined keyword (e.g., stolen, missing, wanted, felony). 542 I Ability for user to prevent a mobile query return from appearing I on dispatcher's screen. C 543 !Ability to attach any database query return to incident records. I C Ability to drill down into query returns regarding a potentially 544 I hazardous subject, vehicle, and/or location to find the details of I C that hazard. 545 Ability to sort query results on any returned field. C 546 Ability to sort query returns by officer name. C Page 24 of 24
May 10, 2022 Item #11 Page 600 of 604DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7 1 2 3 4 5 6 7 8 9 10 11 12 13 14 INTERFACES TAB City of Carlsbad, CA Request for Proposals #20-13: CAD/Mobile Acquisition 'Ability to safely and securely provide a one-way interface from the Vesta E911 System to the CAD application. Ability to import E911 data into the CAD system to pre-fill the CAD incident mask. If any data elements cannot be imported from the E911 system, please indicate those fields in the "Comments" field. Ability to parse address information when transferring data from the E911 system to the CAD system so that it transfers into appropriate address fields. Ability to su_pport the import of E911 data via: Automatic data transfer Manual intervention Ability to geoverify the E911 imported address immediately upon transfer. Ability to determine a physical address from X/Y coordinates imported from the E911 phone system. Ability to transfer E911 call receipt time to CAD to track E911 time stamps. Ability to plot incoming E911 calls on the CAD application map. Ability to import information from text-to-911. Ability to comply and maintain compliance with published NENA and APCO NG-911 standards (to include the import of text). Ability to support the import of Wireless Phase 1 data. C C C C C C C C C C C Motorola Solutions has provided an integration to meet this requirement. Additional details can be found in the SeNices Solution Description. Motorola Solutions has provided an integration to meet this requirement. Additional details can be found in the SeNices Solution Description. Motorola Solutions has provided an integration to meet this requirement. Additional details can be found in the SeNices Solution Description. Motorola Solutions has provided an integration to meet this requirement. Additional details can be found in the SeNices Solution Description. Motorola Solutions has provided an integration to meet this requirement. Additional details can be found in the SeNices Solution Description. Motorola Solutions has provided an integration to meet this requirement. Additional details can be found in the SeNices Solution Description. Motorola Solutions has provided an integration to meet this requirement. Additional details can be found in the SeNices Solution Description. Motorola Solutions has provided an integration to meet this requirement. Additional details can be found in the ~e~rvic~es Solution Description. Motorola Solutions has provided an integration to meet this requirement. Additional details can be found in the SeNices So_lu_tion Description. Motorola Solutions has provided an integration to meet this requirement. Additional details can be found in the SeNices Solution Descrip.1iQn_.__ Motorola Solutions has provided an integration to meet this requirement. Additional details can be found in the SeNices Solution Description. Motorola Solutions has provided an integration to meet this requirement. Additional details can be found in the SeNices Solution Description. Page 1 of 4
May 10, 2022 Item #11 Page 601 of 604DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7 15 16 17 18 19 20 21 22 23 24 25 26 27 28 INTERFACES TAB City of Carlsbad, CA Request for Proposals #20-13: CAD/Mobile Acquisition Interface Functional Requirements Ability to query NCIC through the County's IBM WebSphere message switch from the CAD and Mobile applications. Ability to conduct NCIC queries from within the CAD and Mobile applications. Ability to run queries automatically upon execution of selected commands (e.g., run plates upon entering a traffic stop). Ability to attach NCIC returns to the CAD incident record. Ability to highlight keywords in NCIC query returns (e.g., wanted person, stolen vehicle). Ability for the agency to define the keywords subject to highlight. Ability to safely and securely provide a one-way push of CAD information into relevant NetRMS mobile report writing fields. Ability to safely and securely provide a one-way push of CAD information into relevant NetRMS records management system fields. C C C C C C C C Motorola Solutions has provided an interface to meet this requirement. Additional details can be found in the Services_ Solution Description. Motorola Solutions has provided an interface to meet this requirement. Additional details can be found in the Services Solution Description. Motorola Solutions has provided an interface to meet this requirement. Additional details can be found in the Services Solution Description. Motorola Solutions has provided an interface to meet this requirement. Additional details can be found in the Services So_l_l.Jtion Description. Motorola Solutions has provided an interface to meet this requirement. Additional details can be found in the Services Solution Description. __ _ Motorola Solutions has provided an interface to meet this requirement. Additional details can be found in the Service_s Solution DescriptiQ_n. Motorola Solutions has provided an interface to meet this requirement. Additional details can be found in the Services Solution Description. Motorola Solutions has provided an interface to meet this requirement. Additional details can be found in the Services Solution Description. Page 2 of 4
May 10, 2022 Item #11 Page 602 of 604DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7 INTERFACES TAB City of Carlsbad, CA Request for Proposals #20-13: CAD/Mobile Acquisition 30 31 32 33 34 35 36 37 Ability to safely and securely provide a two-way interface between CAD and City GIS (ESRI ArcSDE) to enable a query from CAD to the City GIS database for updates, and to accept returns. Ability to safely and securely provide a one-way interface from 38 lthe City's license plate reader system to notify dispatchers of a "hit". 39 !Ability for dispatchers to acknowledge "hit" and create a CAD call 40 Abilil 41 ltro1 42 43 Ability to safely and securely provide a one-way interface from the Coplogic DORS application to the CAD application to create calls for service for agency-defined reports submitted in the Coplogic application. N C C C A staging file geodatabase (.gdb) is created to consolidate the needed data from one or more sources. PremierOne Data Import Tools are used to map the appropriate layers from the source schema to the staging/production schema. These Motorola provided tools are installed as a Toolbox within ESRl's ArcGIS for Workstation. ArcGIS Models and/or Python scripting is used to simplify the process and Motorola Solutions has provided an interface to meet this requirement. Additional details can be found in the Services Solution Description. Motorola Solutions has provided an interface to meet this requirement. Additional details can be found in the Services Solution Description. Motorola Solutions has provided an interface to meet this requirement. Additional details can be found in the Services Solution Description. Page 3 of 4
May 10, 2022 Item #11 Page 603 of 604DocuSign Envelope ID: EE0000EC-B19D-469F-887C-147E3BCEAFF7 44 46 47 48 49 so 51 52 INTERFACES TAB City of Carlsbad, CA Request for Proposals #20-13: CAD/Mobile Acquisition Interface Functional Requirements Abil Ability to safely and securely provide a query interface to the QueTel evidence management system to perform querles of property, physical evidence and digital evidence from within the CAD and Moblle applications. C Motorola Solutions has provided an interface to meet this requirement. Additional details can be found in the Services Solution Description. Page 4 of 4
May 10, 2022 Item #11 Page 604 of 604
DocuSign Envelope ID: EEOOOOEC-B19D-469F-887C-147E3BCEAFF7 SECTION 12
City of Carlsbad, CA
February 16, 2022
ADDITIONAL DOCUMENTATION
CORRESPONDENCE
The City requires that all official correspondence regarding the requested services be made part of the final agreement.
MOTOROLA SOLUTIONS RESPONSE
Motorola understands and agrees.
Exhibit A: Contract Documentation Requirements
t.\l Motorola Solutions Additional Documentation Correspondence 131
Computer-Aided Dispatch System
Replacement & In-Car Video
Javier Ruiz, Public Safety IT Manager
Christie Calderwood, Police Captain
May 10, 2022
{city of
Carlsbad
PRESENTATION
•Overview
•Request for proposals and Core Team formation
•Vendor responses
•Features
•Benefits
•Options
•Costs
•Recommendations
ITEM 11: Police CAD Replacement
{ City of
Carlsbad
OVERVIEW
•Current computer-aided dispatch system (Tiburon) is
17 years old
•Identified a need for replacement in 2019
•City hired consultant in 2020 and formed a core team
to review proposals from prospective companies
ITEM 11: Police CAD Replacement
{ City of
Carlsbad
RFP & CORE TEAM
•DeltaWrx: assisted with RFP creation, contract
negotiation, and will assist with the
implementation process
•Core team: Records Manager, Communications
Manager, Patrol Lieutenant, PSSB Lieutenant,
Senior Management Analyst, Public Safety IT
Manager, Senior Applications Analyst
ITEM 11: Police CAD Replacement
{ City of
Carlsbad
VENDOR RESPONSE AND
ONSITE DEMONSTRATIONS
•A group of patrol officers, community service
officers and dispatchers joined the Core Team on
site visits and gave feedback on the solution they
felt best fit the Police Department
•Motorola Solutions was selected as future vendor
ITEM 11: Police CAD Replacement
{ City of
Carlsbad
FEATURES OF CAD SYSTEM
•Cloud-based system (Premier One Cloud)
•Mobile and handheld (Android and iOS) ready
•Automatic vehicle location and mapping upgrades
•Radio and 911 integration (automatic vehicle
location)
•Real-time crime center (Command Central Aware)
•Legacy data query, ability to query multiple database at once •Command Central Community, ability for public to upload video directly into system •Command Central Analytics Plus, reporting and dashboard features •Interfaces for existing technologies
ITEM 11: Police CAD Replacement
ITEM 11: Police CAD Replacement
PREMIERONE
CLOUD SUITE
SYSTEM
DIAGRAM
... -... ; ' , \
I \
I \
I~\,-,
I ~ ,, ' [n] II PremierOne Cloud ' \\
~,, I CAD \ _
1 ...... CommandCentral I , \
Aware User / ~ \
I ■= \ , = Motorola Solutions , ~ 1 Azure Services , commandCentral ; ~ Reporting \
I & I p~~~e~~;re 1' I■ I J~ : I r.;7 I CommaodCeolral ~ I -=-••• ~ I Aware I J.. --==------------,, Other Motorola Cloud 1 B I ~ Resources and 1 C':::::::"":7 ♦ 11 ■ Services 11 PremierOne
CAD Mobile
\ CommandCentral I \ Admin 1 I ·I a ...
State Switch
on-Premise System
', , 1------~ OPTIONAL t _;
...--~\ I I I■ I l Anchor Server
with On-Premise
Connectors
---ANI /ALI
commandCentral 1~ CommandCentral 1 \ Community , \ Analytics , \ ,. ' ; \ , ... , ' , ..... __ ... ' , ... _ ... -------...... ; ... ... ... , Customer Azure ',
' Services , I \ -., ,,... ■■■ ·--...... , ■-.. ~----"{! \ I ■ \ I I
\ Enterprise Applications Customer Azure AD I
\ , ' , ... _ ... ... _________________ _
FEATURES OF IN CAR-VIDEO
•Transparency for the community•Enhanced officer safety•Reduction in police department liability•Provides additional evidence for court conviction purposes, like the body worn cameras•Adds a mobile LPR system to each vehicle ITEM 11: Police CAD Replacement
BENEFITS TO SOLUTION
•Faster transition and deployment process
•Secure and flexible solution---cyber security and analytics •Future ready, the cloud platform will evolve
alongside Carlsbad Police Department & the
incorporation of future technologies
•Carlsbad Police Department will have access to a cutting-edge CAD system and in-car video system ITEM 11: Police CAD Replacement
{ City of
Carlsbad
BENEFITS
ITEM 11: Police CAD Replacement
BENEFITS
ITEM 11: Police CAD Replacement
{ City of
Carlsbad
OPTION 1
•Authorize the City Manager to execute an
agreement with Motorola for the replacement of
the current Computer Aided Dispatch system with
the new CAD vendor-Motorola-for a total cost of
$1,856,620
ITEM 11: Police CAD Replacement
{ City of
Carlsbad
OPTION 2
•Authorize the City Manager to execute an
agreement with Motorola to replace the CAD
(Option 1), and the purchase of an In-Car
Video System for an amount not to exceed
$2,879,018 over 6 years (includes cellular and
maintenance fees)
ITEM 11: Police CAD Replacement
{ City of
Carlsbad
OPTION 3
•Not update the computer aided dispatch
system and in-car video system
ITEM 11: Police CAD Replacement
{ City of
Carlsbad
PRICING
ITEM 11: Police CAD Replacement
. 1r1eemem s
mplemen _a Jon ,& J __ Year · ain_enance
Compur e,r-a· · ed dis1pa c mai · enance Yiears -6
11-car ideo __ a1in enam~e, Ye,airs 2-5
To . I reem1en·1 s Oo
S12 rvic,1M
Cellular Co~, -e,ars .. 51
To _.al Co __ o lniJal Agreemen _ ,& 'Se ice,s
s
Op i'on 2
-5,5 79 ____ , __ _, I 70,16,5,2
79 2 735 05,3 8,78, 33
. 3,'965
022 398, , -__ , ---
RECOMMENDATIONS
Receive report on new CAD proposal and evaluate options to either approve:
•Option 1, the purchase of Motorola CAD system for an amount not to exceed $1,856,620 over a 6-year period, or •Option 2, the CAD replacement and 60 in-car video systems, for an amount not to exceed $2,879,018 Staff’s recommendation is Option 2.
ITEM 11: Police CAD Replacement
{ City of
Carlsbad
-THANK YOU-
QUESTIONS
ITEM 11: Police CAD Replacement
{ City of
Carlsbad