Exhibit B: Technical Narrative Bid # 26-074 RFP

West Sacramento Police Department

Field Reporting and Law Enforcement Records Management System (RMS) Technical Narrative

Please provide a written response to all questions below. In your response, please repeat the heading of each section (beginning with a Roman numeral) followed by the sub-heading (beginning with an Arabic numeral) before answering the corresponding lettered questions.

I. VENDOR INFORMATION

1. Company Background and Business Practices

a. Provide a concise overview of the company, including legal name, headquarters location or office locations from which services will be performed, years in business, number of employees, and the specific business unit responsible for law enforcement RMS and field reporting solutions.

b. Provide details on your company's financial stability and indicators of long-term viability, including whether your company is privately held or publicly traded, whether audited financial statements are available, and whether there have been any mergers, acquisitions, divestitures, restructurings, or material ownership changes within the last five (5) years.

c. Provide a statement describing any and all local benefit the Proposer would bring to the Contract. For example, local benefit may include but is not limited to local vendors, suppliers, labor or subcontractors used in support of the project as well as fees or taxes paid to the City. To the extent practical, the local benefit described with the Proposal should be measurable.

At the end of the Contract, the Contractor shall be required to provide a report detailing the measures taken to enhance the local benefit and whether or not stated goals were met. For purposes of this section, a local vendor or service provider is one located within the City limits and in possession of a West Sacramento business license. If the solicitation has Federal funds, there will be no Local Benefit considered.

d. Describe your customer engagement programs, including user groups, advisory boards, customer conferences, peer networks, and any formal mechanism for customers to propose and vote on enhancements.

e. Describe your methodology for how product direction decisions are made, how customer feedback is incorporated into product enhancements, and how California-specific public safety and compliance requirements are incorporated into future releases.

f. For the proposed solution, include the original release date of the proposed products. Do you currently have a plan for the End of Life (EOL) of the proposed product(s)? If so, provide the anticipated timeframe.

g. How many years will you guarantee continued support of your proposed product(s)?

2. Company Structure, Legal Standing, and Certifications

a. Describe the ownership structure of your organization (sole proprietorship, nonprofit, partnership, joint venture, LLC, privately or publicly held corporation). If a corporation, provide evidence that your company is in good standing and qualified to conduct business in California. Registration with the Secretary of State to conduct business in the State of California is required.

b. Provide a statement as to whether there have been any mergers, acquisitions, or sales related to Proposer's organizational structure within the last five (5) years. If so, attach an explanation providing relevant details.

c. Does your company act as the Prime Contractor for any proposed hardware or third-party components of this solution? Describe the typical arrangement, including how third-party subcontractors are managed and supported.

d. State whether your company uses third parties, subcontractors, or implementation partners for hosting, implementation, interface development, data conversion, cybersecurity, or ongoing support. For each, identify its role and whether WSPD would contract with that entity directly or solely through your firm.

e. Identify all litigation, arbitration, regulatory actions, or material claims within the last ten (10) years involving your firm, your owners, your subcontractors, or the proposed RMS/field reporting product, where the matter relates to public safety software, implementation failure, data loss, cybersecurity, privacy, billing, or contract performance.

f. Provide a statement as to whether there is any pending litigation against the Proposer. If such litigation exists, attach an opinion of counsel as to whether the pending litigation will impair the Proposer's ability to perform the Contract.

g. Provide a statement as to whether, in the last ten (10) years, the Proposer has filed (or had filed against it) any bankruptcy or insolvency proceeding, whether voluntary or involuntary, or undergone the appointment of a receiver, trustee, or assignee for the benefit of creditors. If so, attach an explanation providing relevant details.

h. List all public safety software contracts terminated, cancelled, or not renewed within the last five (5) years for the same RMS or Field Reporting product proposed to WSPD. For each, identify the client, the scope of deployment, the year of termination, and the reason for termination.

i. Provide a statement, signed by a representative of your firm (preferably an owner, attorney, or C-level executive), certifying that you have read and met all proposal requirements and that your response to this RFP is true and accurate.

3. Company Experience

a. Provide a brief statement of how long the Proposer has been performing the services required to complete the Scope of Work. Proposer shall have a minimum of five (5) years of experience providing the services required to complete the Scope of Work to public agencies in California. If the Proposer has been in business for less than five (5) years, the experience of its principals may be used to meet this requirement.

b. Describe no more than five (5) public sector projects completed within the last five (5) years that demonstrate Proposer's experience performing services to complete the Scope of Work, including a statement as to whether Proposer has experience working for the City of West Sacramento, or a public agency similar in size to the City. Note key personnel involved in each project, and if they are proposed for this Proposal. If applicable, differentiate any work performed by a subcontractor. List any contractual relationships with the City existing now or within the past five (5) years.

c. Describe your relevant experience providing Field Reporting and Law Enforcement RMS solutions to public safety agencies.

d. What sets your company apart from other vendors in this space?

e. Identify the total number of active public safety RMS customers, the number of active California law enforcement customers, and the number of agencies currently using the same product proposed to WSPD.

4. Company Personnel

a. Provide a narrative description, along with resumes and organizational chart, of personnel to be assigned to complete tasks within the Scope of Work, clearly indicating where Subcontractors will be used, if applicable. Each resume shall list, at least, the individual’s title, education, relevant experience and duration, professional licenses, and demonstrated accomplishments. Identify the roles and responsibilities of each individual, including who will lead day-to-day work efforts and serve as the primary contact to the City.

II. TECHNICAL CAPABILITIES

1. Field Reporting – Functionality and Usability

WSPD's current field reporting environment has significantly increased report completion times (an estimated 2– 3x over its prior system) due to redundant data entry, unclear validation errors, and limited automation. Please address the following:

a. Describe your solution's approach to streamlining report entry, including estimated report completion time for a typical incident report compared to industry norms.

b. Does the system support carry-forward of suspect and victim information across multiple offenses within the same report, eliminating the need to re-enter the same person for each offense?

c. Describe how officer name, dates, and times auto-populate across related documents (incident, arrest, Probable Cause Declaration, booking application, DA Complaint).

d. Describe the narrative writing interface, including built-in spell check, support for inline photos and diagrams, autosave behavior, version tracking, and the ability to use templates or standard narrative text.

e. How does the system handle IBR/NIBRS validation errors? Are errors displayed in plain language with field-level guidance, are warnings distinguished from blocking errors, and does the system navigate the user directly to the non-compliant field?

f. Describe how the system prevents cascading validation errors (i.e., correcting one field generating new, unrelated errors).

g. Describe system performance for high-volume reports (e.g., incidents involving 100+ victims or property items) and how the application avoids lag, browser freezing, or timeout issues during lengthy data entry sessions.

h. Can required forms (e.g., juvenile arrest forms, booking applications) be configured to print in the format required by the receiving agency or jail without requiring a separate manual/paper process?

i. Describe any mobile-specific field reporting capabilities, including performance expectations on wireless/cellular connections in patrol vehicles, offline functionality, synchronization behavior, and how the system protects draft work from loss during network interruptions.

2. Workflow, Approval, and Supervisory Tools

a. Describe the report approval workflow from officer submission through supervisor review and Records finalization.

b. Can supervisors view all pending and rejected reports in a summary queue without searching by individual case number?

c. Is there a distinct rejection queue that tracks returned reports, reason codes, aging, and whether the officer has acted on the correction, separate from the standard approval queue?

d. Can supervisors modify any field (not only the narrative) during review, or must structured data corrections be returned to the officer?

e. Does the system support a missing-report/accountability list so supervisors can identify officers with outstanding or overdue submissions?

f. Describe the system's ability to display a report in a formatted print view during supervisor review, and to compare revisions or prior versions before approval.

g. Describe any mechanism allowing a supervisor to force, route, reassign, or finalize a document through the approval workflow when operational circumstances require it.

h. If an officer goes off duty before completing a required document (e.g., a Probable Cause Declaration), can an authorized supervisor or designated user start, complete, reassign, or transfer ownership of that document while preserving audit history? Describe the process.

3. RMS Core Functionality – Master Indices and Case Management

a. Describe your Master Name, Master Vehicle, and Master Property Index architecture.

b. Describe your duplicate detection and prevention functionality at the point of entry for persons, vehicles, and property, including exact match, Soundex, fuzzy matching, phonetic matching, date-of-birth logic, and configurable duplicate thresholds.

c. Describe any automated or assisted merge and unmerge tools available to reconcile duplicate master records and confirm whether merge history is auditable and reversible.

d. Does the system provide a consolidated person view showing all associated incidents, cases, arrests, citations, warrants, and bookings?

e. Describe case management functionality, including case queue views, assignment controls, and workload balancing. Do queue views display case type, subject, and status without requiring users to open individual records?

f. Can cases be assigned to a specific primary investigator and additional secondary investigators, with individual responsibility, task ownership, and update history tracked?

g. Describe workload and case-closure tracking functionality, and whether it is sufficient to replace a separate, external case-tracking system.

h. Describe how supplemental reports are linked to and made visible within the parent case/incident record.

4. Data Integration and Interfaces

WSPD's CAD environment (CentralSquare Enterprise CAD) is managed by YECA and will remain in place. A reliable, real-time CAD-to-RMS interface is required.

a. Describe your standard interface methodology for CAD-to-RMS integration, including your experience interfacing with CentralSquare Enterprise CAD and the implementation responsibilities of your firm, the CAD vendor, YECA, and WSPD.

b. Confirm that NCIC/CLETS returns run in CAD or Mobile will transfer into RMS and associate automatically with the incident record when a person or vehicle is attached to the call.

c. Confirm that changes made to CAD records after case number generation (primary officer, address, report type) will synchronize into the RMS incident and call-for-service record.

d. Confirm that person, vehicle, and property data entered in CAD will auto-populate into the related RMS incident shell without manual re-entry.

e. Describe your interface capability with Crossroads (eCitation and eCrash) for automatic import of citation and crash data into RMS, including notification to Records upon receipt.

f. Describe your interface capability with Coplogic/DORS (LexisNexis) or a comparable online citizen reporting system, including automatic import of approved reports into the Cases module.

g. Describe your interface capability, or native functionality, for property and evidence management (see Section 6 below).

h. Describe how NCIC/CLETS return data can be used directly within an RMS report without manual retyping.

i. Provide your standard interface pricing model (one-time build cost, ongoing maintenance/API costs, transaction fees if any) for the interfaces listed above, including any assumptions regarding third-party vendor coordination.

5. Records Management, IBR/NIBRS, and State Compliance

WSPD currently submits approximately 400–600 IBR/NIBRS reports per month to the California Department of Justice, with error rates ranging from 9–21%, and is not currently CIBRS/UCR compliant.

a. Describe your solution's IBR/NIBRS validation approach and how it is designed to keep agency error rates within the state's compliance threshold.

b. Describe how violation code tables, statute tables, UCR/NIBRS tables, California-specific codes, and expired or duplicate code values are maintained and updated, and whether this is managed by the vendor or the agency.

c. Does your solution offer a direct submission interface to the California DOJ CIBRS portal that eliminates the need for dual-system error reconciliation?

d. Provide CIBRS/UCR compliance rates and error-rate benchmarks from comparable California agencies currently using your solution.

e. Describe any CLERY Act reporting capability available natively within the system.

f. Describe redaction tools available for CPRA (California Public Records Act) request processing, including handling of juvenile information, victim-identifying information, and confidential informant references.

g. Describe support for a date-based press log function that can generate a summary of incidents and arrests filtered by date range, without manual compilation from individual reports.

h. Describe how sealing and expungement processes are supported within the system.

i. Describe your data retention, purge, and archival functionality, including the ability to query archived records from within the production environment on a case-by-case basis.

6. Property and Evidence Management

WSPD currently maintains a separate evidence management system (Omnigo TraQ7) requiring dual entry and manages approximately 80,000 evidence items across multiple storage locations.

a. Does your solution include a native property and evidence module, or does it require integration with a third-party evidence management system (e.g., FileOnQ, Beast)? Describe available options and identify which option you recommend for WSPD.

b. If a native module is offered, describe its full feature set, including barcode generation, intake workflow, rejection workflow, chain-of-custody tracking, and storage/location management.

c. Can multiple offenses be linked to a single evidence item, and does the system calculate reliable purge/disposition dates based on all linked offenses?

d. Describe audit logging for all changes made to evidence records.

e. Can evidence items be rejected at intake within the workflow?

f. Describe search and inventory reporting tools available to support evidence audits across a large volume of stored items and multiple storage locations.

g. If integration with an existing or new third-party evidence system is required, describe your standard interface approach and whether dual entry can be eliminated.

7. Warrants, Prosecutor, and Court Coordination

a. Describe warrant entry, tracking, and status management functionality, including support for manually entering charges/statutes not found in a standard system charge table.

b. Describe formal warrant service tracking and assignment capability within the system (rather than reliance on manual notes or physical files).

c. Describe how an “in-custody” flag is managed and whether it can be corrected or cancelled if set in error.

d. Describe person alerts linked to active warrants and how they are surfaced in officer-facing and investigative workflows.

e. Describe any bulk warrant processing capability.

f. Describe support for read-only prosecutor/District Attorney access to RMS to reduce manual packet assembly and resubmission.

g. Describe your solution’s ability to compile a complete case packet (crime report, arrest, probably cause declaration, supplementals, attachments) into a single document for download, print, or submission through a DA portal (e.g., LawSuite).

8. Reporting, Analytics, and Crime Analysis

a. Describe native dashboard and reporting tools available to command staff, supervisors, and the Crime Analysis Division without requiring custom IT queries or vendor involvement.

b. Explain the architecture used for reporting. Is there a dedicated reporting database and/or data warehouse, or would WSPD report directly against the production database?

c. If a data warehouse or reporting database is used, how frequently is it refreshed/updated?

d. What technical skill set is required for WSPD staff to create, modify, schedule, and distribute reports, dashboards, or ad hoc queries without vendor assistance?

e. Describe embedded GIS/mapping capability, including support for heat mapping and layering of citation, crash, and crime data.

f. Describe supervisory visibility into pending, rejected, and overdue reports in real time.

g. Describe options for a separate reporting server or data warehouse to support third-party reporting/analytics tools (e.g., Peregrine, Fusus, ArcGIS) without impacting production system performance.

h. Describe any AI-assisted or natural language search capability for narrative searching, related-case identification, or crime pattern detection.

i. Describe your solution's support for public-facing transparency dashboards and open data initiatives.

9. Technical Architecture and Client/Server Requirements

a. Which platform(s) does your system operate on (on-premises, cloud, hybrid), and which do you recommend for WSPD?

b. Describe the overall system architecture, including application layers, database platform, hosting environment, interfaces, mobile components, and dependencies on third-party products or middleware.

c. Provide process flow diagrams, network diagrams, and hardware/software architecture diagrams for the proposed solution.

d. Provide the minimum and suggested server configurations required to support the proposed solution.

e. Provide the best, bare-minimum, and suggested requirements for client workstations and mobile data computers.

f. What network specifications are recommended, minimal, and ideal for reliable system performance?

Please attach a network diagram to your response.

g. Which operating systems and browsers are supported on client workstations and servers, and which mobile platforms are supported for mobile field reporting?

h. What format will be used to store WSPD's data?

10. Administration and System Configuration Tools

a. What administration toolset(s) does the system come with, covering security administration, business rules, forms configuration, code table maintenance, workflow configuration, user provisioning, and interface monitoring?

b. What ongoing abilities and skill sets are needed by WSPD or IT staff to keep the system properly maintained, and what technical skill level is required for WSPD staff to use these tools effectively without vendor intervention?

c. Which tools are available for system customization, and can workflows, business rules, forms, alerts, and permissions be configured by WSPD without vendor involvement or custom code changes?

d. Is an API or other integration framework available? If so, describe its capabilities, authentication methods, rate limits, documentation availability, and any associated licensing or transaction costs.

e. What kind of regular monitoring is necessary to ensure optimal system performance, and are monitoring tools provided as part of the solution?

11. Security and Cybersecurity

a. What security instruments and tools does the system come with?

b. What defines a user's security profile, and what elements are contained within it (e.g., role, permissions, division, field-level restrictions, access level)? Describe how security controls are applied to officers, supervisors, Records personnel, investigators, administrators, and external read-only users (e.g., prosecutor access).

c. Describe compliance with CJIS security policy requirements and how ongoing compliance is maintained for hosted infrastructure, application operations, support access, remote administration, encryption, logging, and personnel screening.

d. Identify encryption standards used for data at rest and in transit, including database encryption, backups, file attachments, web sessions, and mobile communications.

e. Describe support for Single Sign-On (SSO), Multi-Factor Authentication (MFA), password policy enforcement, session controls, and conditional access restrictions.

f. What are the prerequisites for a wireless connection to the system, and are there any restrictions that apply?

g. Describe cybersecurity certifications and independently validated security audits (e.g., SOC 2 Type II, ISO 27001, penetration testing) and confirm whether summaries can be shared during evaluation under confidentiality protections.

h. Has any software provided by your company ever been compromised by ransomware, unauthorized intrusion, a data breach, a CJIS-related finding, or another material cybersecurity incident affecting a public safety customer environment? If so, summarize the incident, corrective actions taken, and whether affected customers were formally notified.

i. Do you have dedicated cybersecurity specialists assigned to the division that supports product design and implementation?

j. Describe the cybersecurity exercises your company performs to identify vulnerabilities in your system (e.g., penetration testing, engagement of outside ethical hackers).

12. Data Center, Hosting, and Business Continuity

a. If your solution is hosted, who provides the hosted storage/data center services?

b. Where is the data center physically located?

c. Does the data center have sufficient bandwidth to handle data transmittals from WSPD?

d. Which physical and electronic security measures are used to protect the data center?

e. Which procedures are used for data segregation between customers/agencies?

f. Provide a brief description of your company's continuity of business plan.

g. What is the frequency of data center audits?

h. What steps will be taken in the event of a security or data breach?

13. Disaster Recovery, Redundancy, and Backup

WSPD has experienced outages lasting several hours, including one nighttime event of approximately five to six hours, during which officers reverted to paper documentation.

a. Provide expected system uptime/availability for the proposed environment.

b. Describe your backup and disaster recovery approach, including backup frequency, retention periods, failover design, recovery time objective (RTO), recovery point objective (RPO), and the process by which WSPD would access its data during or after a service interruption.

c. What measures are in place for high availability and disaster recovery if the solution is deployed on premises?

d. Are redundancy plans in place, and have single points of failure been identified?

e. Are there provisions in place that guarantee WSPD's ability to access its own data/information at any time?

f. Describe the methods available for local data backup to WSPD- or City-managed servers, if applicable.

14. Data Conversion and Archival

WSPD's current environment includes data quality issues stemming from an incomplete historical conversion from its prior TriTech system, including an estimated one million+ Master Name Index records with significant duplication.

a. Provide pricing for full data conversion of all current CentralSquare Enterprise RMS modules into your proposed system, with a cost breakdown by module.

b. Describe your approach to data cleansing and duplicate resolution during conversion, particularly for Master Name, Vehicle, and Property Index records.

c. Describe the assumptions, exclusions, agency responsibilities, and testing activities that could affect conversion cost, duration, or data fidelity.

d. Provide pricing for conversion of evidence data currently maintained in Omnigo TraQ7, if your solution includes a native evidence module intended to replace it.

e. Provide pricing for archiving all data from all modules of the current CentralSquare Enterprise RMS application to a searchable, accessible database upon discontinuation of the current system, with a cost breakdown by module.

f. Describe how legacy/archived records would remain accessible for query and reference from within the new production environment.

III. METHODOLOGY/APPROACH

1. Implementation, Project Management, and Staffing

a. Provide your estimated implementation timeline for a department of WSPD's size and scope.

b. Summarize your project management methodology and provide a sample implementation schedule for a similarly sized agency.

c. Describe your proposed data migration strategy and quality assurance/testing procedures, including unit testing, interface testing, system testing, user acceptance testing (UAT), cutover validation, and reliability stabilization.

d. Identify the roles and responsibilities required of WSPD staff during implementation.

e. Describe the experience of your proposed Project Manager and key implementation staff with comparable California law enforcement RMS/Field Reporting implementations.

f. Confirm that the assigned Project Manager will be subject to written approval by WSPD and may be required to be interviewed by the agency prior to assignment.

g. Confirm that any subsequent change in project management staff will require WSPD's approval.

h. Confirm your ability to complete a thorough discovery process within sixty (60) days of contract signing for all proposed products.

i. Confirm your ability to deliver a comprehensive project plan within thirty (30) days of discovery being completed, subject to sign-off by WSPD's project manager.

j. Confirm that project plans will not be changed without sign-off from WSPD's Project Manager, other than minor changes that do not affect project quality or the Go-Live/Final System Acceptance timeline.

k. Provide a detailed sample project plan covering: Engagement Preparation, Solution Planning, Solution Implementation, Testing, User/System Documentation, Proposed Training, Customer Deliverables and Knowledge Transfer activities, Go-Live process and support, and Acceptance Testing methodology.

l. Confirm that work on interfaces and data conversions will begin as soon as the project plan is signed off, particularly for state and federal interfaces known to require additional lead time.

m. Provide a list of proposed project team members, including a short biography for each (with a full resume for the Project Manager), their public safety industry experience, their specific role on this project, their tenure with your company, and a list of projects they have worked on in the last five (5) years.

2. Training

a. Describe the training model offered (vendor-delivered end-user training, train-the-trainer, online, hybrid, etc.). WSPD requires full end-user training to be delivered directly by the vendor; describe whether a train-the-trainer model is offered or required.

b. Describe how training addresses WSPD's ability to understand system architecture, system configuration, interface configurations, data import/export capabilities, and workflow/approval process configuration.

c. Confirm that WSPD's designated build/configuration team will receive thorough training before system build begins, so the system can be configured with maximum agency input and knowledge.

d. Describe your ability to assist WSPD directly in the provisioning and build-out of the proposed applications.

e. Confirm that all NIBRS/California DOJ violation codes needed for CIBRS reporting will be provided by your company and imported into the solution as part of implementation.

3. Go-Live, Reliability Testing, and System Acceptance

a. Describe go-live support hours and staffing (onsite, remote, 24/7, business hours, or extended hours).

b. Confirm that experienced vendor representatives will be physically present onsite at WSPD during launch of the new system.

c. Describe how your onsite go-live resources ensure a smooth transition by providing real-time assistance, troubleshooting, training, and issue resolution as end users begin working in the live environment.

d. Describe how you will minimize disruptions, quickly address problems, and ensure the system functions as intended from day one.

e. Describe your proposed reliability testing methodology. Confirm your ability to support a 30-consecutive-day reliability test following cutover of each system component, and a subsequent 90-consecutive-day reliability test in the fully integrated environment once all components are cutover.

f. Describe your error classification and remediation process during reliability testing, including your commitment to resolve Level 1 errors (data loss/corruption, inoperative servers, or systemic workstation failures affecting multiple users or critical operations) and Level 2 errors (errors affecting productive use/operations, or failure to meet performance/availability standards with no acceptable workaround) within 24 hours, with a new test period beginning upon resolution.

g. Describe your proposed process for achieving Final System Acceptance following successful completion of the reliability test period(s).

h. Describe your Post Go-Live support model, including your ability to return onsite six (6) to twelve (12) months after Go-Live to conduct a Business Process Review (BPR) assessing what the agency is doing well, what could be improved, and what functionality is underutilized, followed by a train-the-trainer plan for WSPD's internal trainers.

4. Maintenance, Support, and Upgrades

WSPD's current mobile client version is pinned at an older release, constraining update management and patching. Please address the following.

a. Describe the support offered post go-live, including support methodologies, support tiers (Level 1, 2, 3, etc.), and expected response/resolution times for each tier.

b. Describe ad-hoc and emergency support provisions and provide telephone support hours.

c. Describe your support and help desk process (phone, web portal, knowledge base, etc.), including the process for tracking and resolving support tickets.

d. Describe customer support specifically available for interfaces and confirm support days/times for all proposed products.

e. What constitutes a qualifying “onsite support” response, and what procedures are followed if a proposed solution experiences a system crash?

f. Are there any additional fees outside of standard maintenance/support costs? Describe any differences in support levels based on contract or license dollar amounts.

g. Provide the optional cost, if available, for a dedicated full-time onsite support representative who can assist with technical issues, new-hire training, issue escalation, and upgrade support.

h. Describe all other support channels available (onsite, remote dial-in, web access, etc.) and your escalation procedures for unresolved issues.

i. Outline your Service Level Agreement (SLA) covering all levels of support, from minor questions to catastrophic system failures.

j. Describe the availability of a dedicated account manager or customer success manager, and provide customer retention/satisfaction metrics (e.g., NPS) if available.

k. Describe ongoing training resources available after go-live (online academies, webinars, documentation) and any user groups, committees, or forums your company sponsors for Field Reporting/RMS customers.

l. How frequently is the software upgraded, and how are customers notified of upcoming patches and upgrades?

m. Describe how updates and patches are implemented and applied, including the testing process used prior to releasing a new software version, and your typical timeline for deploying updates/patches to both desktop and mobile clients.

n. How much end-user and technical training is typically required when the system is upgraded?

o. During an upgrade, what happens to WSPD's existing customizations (e.g., user-defined tables and fields)?

p. How many software versions does your company support concurrently, and how is the mobile client version kept current and supported?

q. Are upgrades included at no additional cost under the maintenance, subscription, or support agreement? If not, describe the circumstances under which WSPD would be expected to pay for an upgrade, and what percentage of your customer base typically pays for upgrade-related services.

r. Describe your long-term product roadmap and how it aligns with future public safety technology needs (e.g., AI-assisted reporting, expanded mobile capability, GIS).

End of Exhibit B