Agenda Item 8I — Torrance City Council, June 23, 2026

8I
Date: June 23, 2026
To: Honorable Mayor and Members of the City Council
From: Andrei Yermakov, Information Technology Director
By: Jillian Wade, Project Manager | [email protected] Subject: Information Technology – Approve First Amendment to Master Software and Services Agreement for Computer-Aided Dispatch (CAD) System to Add Records Management System (RMS). Expenditure: Approximately $5,667,471 (General Fund: Approximately $566,747.10 Annually).

RECOMMENDATION
Recommendation of the Information Technology Director that City Council approve a first amendment to the Master Software and Services Agreement and related service schedules with Versaterm Public Safety US, Inc of Delaware (C2025-285), in the amount of approximately $5,667,471, for a new contract total of approximately $13,272,463, for the acquisition, implementation, and annual subscription of a Records Management System (RMS), for a ten-year (10) period beginning December 3, 2025, and ending December 31, 2035.

FUNDING
Funding is available from the following funding sources:

Funding Source Amount
Versaterm RMS Project (TBD) - Measure SST Fund $1,774,613 Information Technology Department Operating Budget
(Annual Subscription)*
$3,892,858
Total $5,667,471
*Funding for the first year of the agreement is included in the Versaterm RMS Project (TBD).

Funding for the annual subscription costs in years 2-10 is anticipated to be available in subsequent Information Technology Operating Budgets.

DISCUSSION
On December 2, 2025, Your Honorable Body approved a Master Software and Services Agreement with Versaterm Public Safety U.S., Inc. for the implementation of a new Computer-Aided Dispatch (CAD) system to serve both the Police and Fire Departments. The City subsequently executed Contract No. C2025-285 for a ten-year term, effective December 3, 2025, through December 31, 2035. The total cost of this contract was approximately $7,604,992. 1 City Council
June 23, 2026

Page 2 ends

Project implementation commenced in January 2026 and is currently underway. During the implementation process, the project team identified that the City’s existing Records Management System (RMS) vendor is unable to develop an interface between the new Versaterm CAD system and the current RMS platform. Because integration between CAD and RMS is essential for public safety operations, the City has determined that the most effective solution is to implement the Versaterm RMS to ensure full system compatibility, data integrity, and operational efficiency.

As a result, both the Versaterm CAD and RMS systems must be implemented concurrently and are required to go live on the same date. Given that the CAD implementation has been underway for approximately three months, timely alignment of the RMS implementation schedule is critical to maintaining project continuity and avoiding delays to the overall public safety technology modernization effort.

This amendment includes one-time onboarding services fee for implementation, data migration, system configuration, and user training. It also includes a multi-year subscription covering software licensing, hosting, and technical support. The proposed ten-year agreement includes a fixed annual increase of five percent (5%), which provides long-term cost predictability while establishing a stable, integrated partnership with a proven public safety technology provider.

ATTACHMENTS

1. Master Software and Services Agreement

2. Master Software and Services Agreement – First Amendment 2 Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 3 ATTACHMENT 1
Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 4 Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 5 Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 6 Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 7 Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 8 Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 9 Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 10 Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 11 Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 12 Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 13 Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 14 Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 15 Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 16 Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 17 Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 18 Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 19 Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 20 Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 21 Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 22 Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 23 Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 24 Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 12/05/2025 | 08:02 PST
John Faulkner
CFO
Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 CEO
Steve Seoane
12/08/2025 | 10:00 PST
25 Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 26 Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 27 Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 28 Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 29 Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 30 Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 31 Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 32 Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 33 Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 34 Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 35 Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 36 Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 37 Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 38 Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 39 Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 40 Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 41 Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 42 Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 43 Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 44 Versaterm Public Safety Inc. & City of Torrance
SaaS Agreement #
Exhibit B - CAD SaaS Service Schedule for Cloud
Page |

16 I
N WITNESS WHEREOF, the Parties hereto have executed this Service Schedule as of the day and year indicated below.

V
ersaterm Public Safety US, Inc.

B
y: _________________________

N
ame: _____________________
T
itle: ______________________
D
ate: ______________________
B
y: ________________________

N
ame: _____________________
T
itle: ______________________
D
ate: ______________________

CITY OF TORRANCE,
a municipal corporation

______
_____________________________________
George K. Chen

, Mayor

A
TTEST:
______
____________________________________
Rebecca Poirier, MMC
City Clerk
APP
ROVED AS TO FORM:

PATRICK Q. SULLIVAN
City Attorney
By
:_________________________________________
Jeanne

-
Marie K. Litvin
Deputy City Attorney
Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 CFO
John Faulkner
12/05/2025 | 08:02 PST
Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 12/08/2025 | 10:00 PST
Steve Seoane
CEO
45 Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 46 Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 47 Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 48 Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 49 Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 50 Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 51 Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 52 Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 53 Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 54 Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 55 Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 56 Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 57 Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 58 Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 59 Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 60 Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 61 Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 62 Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 63 Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 64 Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 65 Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 66 Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 67 Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 68 Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 69 Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 70 Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 71 Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 72 Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 73 Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 74 Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 75 Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 76 Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 77 Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 78 Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 79 Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 80 Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 81 Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 82 Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 83 Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 84 Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 85 Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 86 Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 87 Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 88 Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 89 Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 90 Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 91 Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 92 Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 93 Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 94 Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 95 Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 96 Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 97 Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 98 Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 99 Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 100
Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 101
Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 102
Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 103
Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 104
Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 105
Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 106
Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 107
Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 108
Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 109
Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 110
Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 111
Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 112
Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 113
Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 114
Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 115
Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 116
Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 117
Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 118
Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 119
Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 120
Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 121
Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 122
Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 123
Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 124
Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 125
Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 126
Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 127
Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 128
Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 129
Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 130
Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 131
Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 132
Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 133
Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 134
Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 135
Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 136
Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 137
Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 138
Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 139
Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 140
Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 141
Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 142
Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 143
Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 144
Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 145
Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 146
Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 147
Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 148
Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 149
Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 150
Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 151
Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 152
Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 153
Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 154
Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 155
Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 156
Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 157
Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 158
Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 159
Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 160
Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 161
Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 162
Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 163
Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 164
Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 165
Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 166
Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 167
Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 168
Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 169
Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 170
Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 171
Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 172
Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 173
Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 174
Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 175
Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 176
Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 177
Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 178
Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 179
Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 180
Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 181
Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 182
Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 183
Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 184
Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 185
Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 186
Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 187
Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 188
Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 189
Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 190
Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 191
Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 192
Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 193
Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 194
Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 195
Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 196
Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 197
Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 198
Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 199
Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 200
Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 201
Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 202
Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 203
Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 204
Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 205
Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 206
Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 207
Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 208
Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 209
Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 210
Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 211
Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 212
Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 213
Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 214
Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 215
Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 216
Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 217
Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 218
Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 219
Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 220
Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 221
Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 222
Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 223
Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 224
Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 225
Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 226
Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 227
Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 228
Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 229
Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 230
Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 231
Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 232
Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 233
Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 234
Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 235
Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 236
Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 237
Docusign Envelope ID: C7FD9FFF-8886-4F62-9640-213AAA9F71F3 Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 238
Certificate Of Completion
Envelope Id: C7FD9FFF-8886-4F62-9640-213AAA9F71F3
Status: Sent
Subject: Complete with Docusign: C2025-285 Versaterm Public Safety US, Inc..pdf Source Envelope:

Document Pages: 236
Signatures: 2
Envelope Originator:

Certificate Pages: 5
Initials: 0
Sonia Delgado
AutoNav: Enabled
EnvelopeId Stamping: Enabled
Time Zone: (UTC-08:00) Pacific Time (US & Canada)
3031 Torrance Blvd
Torrance, CA 90503
[email protected]
IP Address: 204.145.129.190
Record Tracking
Status: Original
12/3/2025 12:52:09 PM
Holder: Sonia Delgado
[email protected]
Location: DocuSign
Signer Events
Signature
Timestamp
John Faulkner
[email protected]
CFO
Security Level: Email, Account Authentication
(None)
Signature Adoption: Uploaded Signature Image
Using IP Address:
2600:1702:1df0:b010:110c:4efa:c191:cfd1
Sent: 12/4/2025 1:49:05 PM
Viewed: 12/5/2025 8:01:06 AM
Signed: 12/5/2025 8:02:09 AM
Electronic Record and Signature Disclosure:

Accepted: 12/5/2025 8:01:06 AM
ID: cb3951a6-0a13-41c9-a180-34cc1d8a37ee
Company Name: City of Torrance CA
Warren Loomis
[email protected]
Security Level: Email, Account Authentication
(None)
Sent: 12/5/2025 8:02:12 AM
Viewed: 12/5/2025 10:19:33 AM
Electronic Record and Signature Disclosure:

Accepted: 12/5/2025 10:19:33 AM
ID: 0c7218b6-44e9-4909-be24-c2529c52cc7f
Company Name: City of Torrance CA
Jeanne-Marie Litvin
[email protected]
Security Level: Email, Account Authentication
(None)
Electronic Record and Signature Disclosure:

Accepted: 11/25/2025 1:19:26 PM
ID: c6e44ad6-68ac-4117-bb80-d1af8438d2dd
Company Name: City of Torrance CA
George K. Chen
[email protected]
Security Level: Email, Account Authentication
(None)
Electronic Record and Signature Disclosure:

Accepted: 12/4/2025 2:05:03 PM
ID: 209626e4-169e-4c4d-bf49-6dbd83a059dd
Company Name: City of Torrance CA
Rebecca Poirier
[email protected]
Security Level: Email, Account Authentication
(None)
Electronic Record and Signature Disclosure:

Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 239
Signer Events
Signature
Timestamp
Accepted: 12/4/2025 4:06:36 PM
ID: 85a7743e-29b6-4c05-9a71-82567f10fcb2
Company Name: City of Torrance CA
In Person Signer Events
Signature
Timestamp
Editor Delivery Events
Status
Timestamp
Agent Delivery Events
Status
Timestamp
Intermediary Delivery Events
Status
Timestamp
Certified Delivery Events
Status
Timestamp
Versaterm Legal
[email protected]
Security Level: Email, Account Authentication
(None)
Using IP Address:
2607:fea8:e120:2ea0:34dd:52a4:65c8:da7
Sent: 12/3/2025 1:02:41 PM
Viewed: 12/4/2025 1:49:03 PM
Electronic Record and Signature Disclosure:

Accepted: 12/4/2025 1:49:03 PM
ID: d660a78b-58ad-4047-b005-76ebfb24a8ea
Company Name: City of Torrance CA
Carbon Copy Events
Status
Timestamp
Jillian Wade
[email protected]
Security Level: Email, Account Authentication
(None)
Electronic Record and Signature Disclosure:

Not Offered via Docusign
Theresa Yniguez
[email protected]
Security Level: Email, Account Authentication
(None)
Electronic Record and Signature Disclosure:

Not Offered via Docusign
Sonia Delgado
[email protected]
Security Level: Email, Account Authentication
(None)
Electronic Record and Signature Disclosure:

Not Offered via Docusign
Witness Events
Signature
Timestamp
Notary Events
Signature
Timestamp
Envelope Summary Events
Status
Timestamps
Envelope Sent
Hashed/Encrypted
12/3/2025 1:02:41 PM
Payment Events
Status
Timestamps
Electronic Record and Signature Disclosure
Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 240

ELECTRONIC RECORD AND SIGNATURE DISCLOSURE
From time to time, City of Torrance CA (we, us or Company) may be required by law to provide to you certain written notices or disclosures. Described below are the terms and conditions for providing to you such notices and disclosures electronically through the DocuSign system.

Please read the information below carefully and thoroughly, and if you can access this information electronically to your satisfaction and agree to this Electronic Record and Signature Disclosure (ERSD), please confirm your agreement by selecting the check-box next to ‘I agree to use electronic records and signatures’ before clicking ‘CONTINUE’ within the DocuSign system.

Getting paper copies
At any time, you may request from us a paper copy of any record provided or made available electronically to you by us. You will have the ability to download and print documents we send to you through the DocuSign system during and immediately after the signing session and, if you elect to create a DocuSign account, you may access the documents for a limited period of time (usually 30 days) after such documents are first sent to you. After such time, if you wish for us to send you paper copies of any such documents from our office to you, you will be charged a $0.00 per-page fee. You may request delivery of such paper copies from us by following the procedure described below.

Withdrawing your consent
If you decide to receive notices and disclosures from us electronically, you may at any time change your mind and tell us that thereafter you want to receive required notices and disclosures only in paper format. How you must inform us of your decision to receive future notices and disclosure in paper format and withdraw your consent to receive notices and disclosures electronically is described below.

Consequences of changing your mind
If you elect to receive required notices and disclosures only in paper format, it will slow the speed at which we can complete certain steps in transactions with you and delivering services to you because we will need first to send the required notices or disclosures to you in paper format, and then wait until we receive back from you your acknowledgment of your receipt of such paper notices or disclosures. Further, you will no longer be able to use the DocuSign system to receive required notices and consents electronically from us or to sign electronically documents from us.

All notices and disclosures will be sent to you electronically Electronic Record and Signature Disclosure created on: 5/2/2023 12:32:32 PM Parties agreed to: John Faulkner, Warren Loomis, Jeanne-Marie Litvin, George K. Chen, Rebecca Poirier, Versaterm Legal Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 241
Unless you tell us otherwise in accordance with the procedures described herein, we will provide electronically to you through the DocuSign system all required notices, disclosures, authorizations, acknowledgements, and other documents that are required to be provided or made available to you during the course of our relationship with you. To reduce the chance of you inadvertently not receiving any notice or disclosure, we prefer to provide all of the required notices and disclosures to you by the same method and to the same address that you have given us. Thus, you can receive all the disclosures and notices electronically or in paper format through the paper mail delivery system. If you do not agree with this process, please let us know as described below. Please also see the paragraph immediately above that describes the consequences of your electing not to receive delivery of the notices and disclosures electronically from us.

How to contact City of Torrance CA:

You may contact us to let us know of your changes as to how we may contact you electronically, to request paper copies of certain information from us, and to withdraw your prior consent to receive notices and disclosures electronically as follows:

To contact us by email send messages to: [email protected]

To advise City of Torrance CA of your new email address To let us know of a change in your email address where we should send notices and disclosures electronically to you, you must send an email message to us at [email protected] and in the body of such request you must state: your previous email address, your new email address. We do not require any other information from you to change your email address.

If you created a DocuSign account, you may update it with your new email address through your account preferences.

To request paper copies from City of Torrance CA
To request delivery from us of paper copies of the notices and disclosures previously provided by us to you electronically, you must send us an email to [email protected] and in the body of such request you must state your email address, full name, mailing address, and telephone number. We will bill you for any fees at that time, if any.

To withdraw your consent with City of Torrance CA
To inform us that you no longer wish to receive future notices and disclosures in electronic format you may:

Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 242
i. decline to sign a document from within your signing session, and on the subsequent page, select the check-box indicating you wish to withdraw your consent, or you may; ii. send us an email to [email protected] and in the body of such request you must state your email, full name, mailing address, and telephone number. We do not need any other information from you to withdraw consent.. The consequences of your withdrawing consent for online documents will be that transactions may take a longer time to process..

Required hardware and software
The minimum system requirements for using the DocuSign system may change over time. The current system requirements are found here: https://support.docusign.com/guides/signer-guide- signing-system-requirements.

Acknowledging your access and consent to receive and sign documents electronically To confirm to us that you can access this information electronically, which will be similar to other electronic notices and disclosures that we will provide to you, please confirm that you have read this ERSD, and (i) that you are able to print on paper or electronically save this ERSD for your future reference and access; or (ii) that you are able to email this ERSD to an email address where you will be able to print on paper or save it for your future reference and access. Further, if you consent to receiving notices and disclosures exclusively in electronic format as described herein, then select the check-box next to ‘I agree to use electronic records and signatures’ before clicking ‘CONTINUE’ within the DocuSign system.

By selecting the check-box next to ‘I agree to use electronic records and signatures’, you confirm that:
 You can access and read this Electronic Record and Signature Disclosure; and  You can print on paper this Electronic Record and Signature Disclosure, or save or send this Electronic Record and Disclosure to a location where you can print it, for future reference and access; and
 Until or unless you notify City of Torrance CA as described above, you consent to receive exclusively through electronic means all notices, disclosures, authorizations, acknowledgements, and other documents that are required to be provided or made available to you by City of Torrance CA during the course of your relationship with City of Torrance CA.

Docusign Envelope ID: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97 243
Certificate Of Completion
Envelope Id: 094D75D1-31F8-45A3-BA00-2BB3C5AD2F97
Status: Completed
Subject: Complete with Docusign: Complete_with_Docusign_C2025-285_Versaterm_P.pdf Source Envelope:

Document Pages: 241
Signatures: 8
Envelope Originator:

Certificate Pages: 5
Initials: 0
Theresa Yniguez
AutoNav: Enabled
EnvelopeId Stamping: Enabled
Time Zone: (UTC-08:00) Pacific Time (US & Canada)
3031 Torrance Blvd
Torrance, CA 90503
[email protected]
IP Address: 204.145.129.190
Record Tracking
Status: Original
12/8/2025 9:49:04 AM
Holder: Theresa Yniguez
[email protected]
Location: DocuSign
Signer Events
Signature
Timestamp
Steve Seoane
[email protected]
CEO
Security Level: Email, Account Authentication
(None)
Signature Adoption: Pre-selected Style
Using IP Address: 68.3.82.250
Sent: 12/8/2025 9:59:30 AM
Viewed: 12/8/2025 10:00:01 AM
Signed: 12/8/2025 10:00:29 AM
Electronic Record and Signature Disclosure:

Accepted: 12/8/2025 10:00:01 AM
ID: d0ec3d35-4229-417e-b40d-6fc8d7a26d4f
Company Name: City of Torrance CA
J.K. Litvin
[email protected]
Deputy City Attorney III
Security Level: Email, Account Authentication
(None)
Signature Adoption: Pre-selected Style
Using IP Address:
2603:8001:8c00:4c66:814d:8c5c:3af:14e0
Sent: 12/8/2025 10:00:38 AM
Viewed: 12/8/2025 10:23:32 AM
Signed: 12/8/2025 10:25:39 AM
Electronic Record and Signature Disclosure:

Accepted: 12/8/2025 10:23:32 AM
ID: dee31137-e4fb-48d3-bb76-1792f73ed653
Company Name: City of Torrance CA
George K. Chen
[email protected]
Mayor, City of Torrance
Security Level: Email, Account Authentication
(None)
Signature Adoption: Pre-selected Style
Using IP Address: 47.153.31.241
Signed using mobile
Sent: 12/8/2025 10:25:48 AM
Viewed: 12/8/2025 10:42:55 AM
Signed: 12/8/2025 10:44:24 AM
Electronic Record and Signature Disclosure:

Accepted: 12/8/2025 10:42:55 AM
ID: 0ce2dd74-a854-40cc-b230-cd1d1308f838
Company Name: City of Torrance CA
Rebecca Poirier
[email protected]
Security Level: Email, Account Authentication
(None)
Signature Adoption: Pre-selected Style
Using IP Address: 204.145.129.190
Sent: 12/8/2025 10:44:32 AM
Viewed: 12/8/2025 10:53:54 AM
Signed: 12/8/2025 10:54:22 AM
244
Signer Events
Signature
Timestamp
Electronic Record and Signature Disclosure:

Accepted: 12/8/2025 10:53:54 AM
ID: b4669e2c-58a8-4596-abe4-65bb1ff562f1
Company Name: City of Torrance CA
In Person Signer Events
Signature
Timestamp
Editor Delivery Events
Status
Timestamp
Agent Delivery Events
Status
Timestamp
Intermediary Delivery Events
Status
Timestamp
Certified Delivery Events
Status
Timestamp
Carbon Copy Events
Status
Timestamp
Theresa Yniguez
[email protected]
Deputy City Clerk I
City of Torrance
Security Level: Email, Account Authentication
(None)
Sent: 12/8/2025 10:54:30 AM
Resent: 12/8/2025 10:54:36 AM
Viewed: 12/8/2025 10:57:30 AM
Electronic Record and Signature Disclosure:

Not Offered via Docusign
jillian wade
[email protected]
Security Level: Email, Account Authentication
(None)
Sent: 12/8/2025 10:54:31 AM
Electronic Record and Signature Disclosure:

Not Offered via Docusign
Sonia Delgado
[email protected]
Deputy City Clerk
City of Torrance
Security Level: Email, Account Authentication
(None)
Sent: 12/8/2025 10:54:33 AM
Electronic Record and Signature Disclosure:

Not Offered via Docusign
Witness Events
Signature
Timestamp
Notary Events
Signature
Timestamp
Envelope Summary Events
Status
Timestamps
Envelope Sent
Hashed/Encrypted
12/8/2025 9:59:30 AM
Certified Delivered
Security Checked
12/8/2025 10:53:54 AM
Signing Complete
Security Checked
12/8/2025 10:54:22 AM
Completed
Security Checked
12/8/2025 10:54:33 AM
Payment Events
Status
Timestamps
Electronic Record and Signature Disclosure
245

All notices and disclosures will be sent to you electronically Electronic Record and Signature Disclosure created on: 5/2/2023 12:32:32 PM Parties agreed to: Steve Seoane, J.K. Litvin, George K. Chen, Rebecca Poirier 246
Unless you tell us otherwise in accordance with the procedures described herein, we will provide electronically to you through the DocuSign system all required notices, disclosures, authorizations, acknowledgements, and other documents that are required to be provided or made available to you during the course of our relationship with you. To reduce the chance of you inadvertently not receiving any notice or disclosure, we prefer to provide all of the required notices and disclosures to you by the same method and to the same address that you have given us. Thus, you can receive all the disclosures and notices electronically or in paper format through the paper mail delivery system. If you do not agree with this process, please let us know as described below. Please also see the paragraph immediately above that describes the consequences of your electing not to receive delivery of the notices and disclosures electronically from us.

How to contact City of Torrance CA:

To contact us by email send messages to: [email protected]

If you created a DocuSign account, you may update it with your new email address through your account preferences.

To withdraw your consent with City of Torrance CA
To inform us that you no longer wish to receive future notices and disclosures in electronic format you may:
247
i. decline to sign a document from within your signing session, and on the subsequent page, select the check-box indicating you wish to withdraw your consent, or you may; ii. send us an email to [email protected] and in the body of such request you must state your email, full name, mailing address, and telephone number. We do not need any other information from you to withdraw consent.. The consequences of your withdrawing consent for online documents will be that transactions may take a longer time to process..

EXHIBIT C

RMS SAAS SERVICE SCHEDULE FOR CLOUD
249
ATTACHMENT 2
Exhibit C – RMS SaaS Service Schedule for Cloud
Page | 2
Service Schedule – RMS SaaS

1. This Service Schedule No. 002 is effective as of last signature below and is made by City of Torrance ("Customer") and Versaterm Public Safety US, Inc. ("Versaterm"). This "Service Schedule" and its schedules (if applicable) are incorporated into that certain Master Software and Services Agreement dated December 8, 2025 , between Customer and Versaterm ("MSA"). The terms and conditions that are specific to this Service Schedule are set forth herein. In the event of a conflict between the provisions of this Service Schedule and the Master Agreement, the provisions of Section 2 a) of the MSA shall control such conflict. Capitalized terms herein will have the meanings set forth in the MSA or the "Definitions" as further defined below.

2. Definitions
Any capitalized word or term used in this Service Schedule but not otherwise defined herein shall have the meaning given to it in the Master Software and Services Agreement.

2.1. “Critical Priority Error” means complete system failure where the Subscription Service is not available for use.

2.2. “High Priority Error” means a serious problem that materially affects the operational use of the Subscription Service.

2.3. “Major Enhancement Release” means a change or new release of the Subscription Service then in use by the Customer containing new functions, features and enhancements that have become part of the standard system.

2.4. “Minor Enhancement Release” means a change or new release of the Subscription Service then in use by the Customer designed to correct Problem(s) and/or provide minor functionality additions.

2.5. “On-Site Software” means Software, as defined in the MSA, that are installed and used on Customer’s own systems or premises, on the license terms set out herein.

2.6. “Problem” means a failure of the Subscription Service to function substantially in accordance with the Documentation.

2.7. "Production Use" means the use of one or more functional application components to collect and manage real customer information for the purpose of serving actual customer needs; this is in contrast to "testing mode", where real customer information may be used, but only for the purpose of evaluation and testing.

2.8. “Support Authority” means the Customer’s designated employee(s) authorized to approve additional, separately billable time & materials support work, beyond that included in this Service Schedule.

2.9. “Support Contact” means Customer’s designated employee, a consultant providing services directly to the Customer, or another designated Customer representative with whom Versaterm will communicate when providing Support. The Support Contact must be knowledgeable about how the Subscription Service is being used and must be familiar with the operating environment under which it is being used.

2.10. “Source Code” means a collection of computer instructions written using a human-readable programming language. Source Code includes all material including, but not limited to, design documentation, User Documentation, reference manuals, libraries for the Software, and interface software, in any form (printed, electronic, or magnetic).

2.11. “Third Party Application” means a third-party service by a Third-Party Provider(s) approved by Versaterm to which the Customer and any Authorized User facilitates Versaterm’s access to, and use of the Subscription Service, via an application programming interface or other means. 250
Exhibit C – RMS SaaS Service Schedule for Cloud
Page | 3

2.12. “Third Party Components” means any components of the Subscription Service provided by third parties, including open-source components and third-party proprietary software or services (e.g. Amazon Web Services (AWS)).

2.13. “Third Party Data” means any data owned by a third party that the Customer accesses via the Subscription Service

2.14. “Third-Party Providers” means third parties, including other vendors, federal agencies, state/provincial agencies, and local agencies that control products and/or databases with which the Subscription Service are to be interfaced but for the avoidance of doubt shall not include any Third-Party Suppliers.

2.15. “Third Party Suppliers” means any party who provides products and/or services, including Open-Source Software and Third-Party Components that contribute to the overall Subscription Service provided to the Customer by Versaterm.

2.16. “Versaterm Certified Browsers” means acceptable browsers on which Versaterm shall operate its Software.

This internal list shall be maintained by Versaterm.

3. Service Schedule Information

3.1. Software and Authorized Users
• Authorized Users
Authorized
Police Sworn Count: 219
The following Software are provided by Versaterm to the Customer:
vRMS
VGI GIS Maintenance Tool
Data Mart (VDM)
vMRE
Electronic Citations
Electronic Motor Vehicle Accident (eMVA) - California
vMobile
Versaterm Message Controller (VMC)
Based on the full scope of work as initially proposed , the following interfaces are provided by Versaterm to the Customer:

RMS- JDIC/CLETS/NCIC
Karpel (Prosecutor Case Management)
AFIS LiveScan_LACRIS
CrimeTracer
Citation Processing Center (CPC)

3.2. Subscription Term:

Initial Subscription Term: Ten years commencing upon Provisioning.

The current Subscription Term auto renews in accordance with section 3(c) of the MSA. 251
Exhibit C – RMS SaaS Service Schedule for Cloud
Page | 4

3.3. Fees:

Versaterm shall send invoices for the below Fees to Customer at the following e-mail addresses:

[email protected] ; [email protected]. Should invoice email address change, Customer shall promptly notify Versaterm.

3.3.1.Onboarding Fee
Based on the full scope of work as initially proposed , the total amount payable for Professional Services is $1,438,381.00 . An invoice for this Fee shall be issued upon commencement of the first Production Period of the Subscription Service and shall be paid in full within forty-five (45) calendar days after the invoice date.

Onboarding Milestones, as identified in the
Statement of Work (Exhibit B) Percentage Payment
Kickoff Meeting 10% $120,971.20
Provisioning (Build the Test Environment) 10% $120,971.20 Configuration Workshop #2 10% $120,971.20
Build the Production Environment 10% $120,971.20
Configuration Workshop #3 15% $181,456.80
Functional Acceptance Testing 15% $181,456.80
Ready for Use (Ready for Training) 15% $181,456.80
Final Acceptance 15% $181,456.80
SubTotal: 100% $1,209,712.00
RMS Interfaces 100% $116,304.00
End-User Training 100% $112,365.00
Total: 100% $1,438,381.00

3.3.2. Subscription Fees

3.3.2.1 Subscription Fees for the Initial Subscription Term

3.3.2.1.1 Subscription Fees Year 1:

Subscription Category Payment
RMS Software Subscription $284,837.00
RMS Interfaces Subscription $31,395.00
Configuration as a Service (CaaS) for RMS and MRE Subscription $20,000.00 Total Subscription $336,232.00
Based on the full scope of work as initially proposed , the annual Subscription Fee for the first year of the Subscription Service is $336,232.00 . An invoice for this Fee shall be issued upon the commencement of the Initial Subscription Term, as described in the Statement of Work and shall be paid in full within forty-five (45) 252
Exhibit C – RMS SaaS Service Schedule for Cloud
Page | 5
calendar days after the invoice date, which shall set the date for subsequent years. The invoice date for this subscription payment is currently targeted for August 17, 2026.

Total Fees for Onboarding and First Year Subscription: USD: $1,774,613.00

3.3.2.1.2 Subscription Fees for Years 2 through 10:
i. The annual Subscription Fees for the years 2 through 10:
a. shall be paid in full and in advance on the annual anniversary of the Initial Subscription Term start; and
b. may be increased by no more than 5% calculated based on the previous year’s Subscription Fees and is adjusted as defined in the Calculation of Subscription Fees section below.
c. Versaterm shall notify the Customer regarding any pricing increases at least sixty (60) days prior to the beginning of a Subscription Renewal Term.

3.3.2.2 Calculation of Subscription Fees
i. Calculation. During the Production Period, the annual Subscription Fee for the Software as a Service shall be calculated as the number of users in a User Class multiplied by their respective User Cost per Month (UCM) multiplied by 12.
ii. User Classes. As of the Effective Date of this Service Schedule, the User Classes are:
a. Sworn Officers:

Number of Sworn Officers (NSO) is defined as the number of sworn employees as of the date that is ninety (90) days prior to the Subscription Payment Date, as certified by the personnel orders of the Police Department and Fire Department.

The RMS UCM of NSO is currently $127.94 per user. The NSO for the first full year of the Production Period is 219 .

3.3.2.3. Subsequent Subscription Fees
In accordance with the terms of the MSA, following the expiration of the Initial Subscription Term, the Subscription Service shall automatically renew for additional one-year periods. The annual Subscription Fee for subsequent years of the Subscription Services shall be paid in full and in advance on the annual anniversary of the Initial Subscription Term start date and subject to the following yearly price increase. i. Subsequent Subscription Renewal Term. the Subscription Fees for each Subscription Renewal Term may be increased by no more than CPI + 4%, calculated based on the previous year’s Subscription Fees. ii. Versaterm shall notify the Customer regarding any pricing increases at least sixty (60) days prior to the beginning of a Subscription Renewal Term.

3.3.2.4 Itemized Interface Costs
i. The costs outlined below are based on the full scope of work as initially proposed and included in the total Onboarding Fee defined in Section 3.3.1 above. Any changes to the project scope, including 253
Exhibit C – RMS SaaS Service Schedule for Cloud
Page | 6
additional interfaces or modifications, will be billed separately. If the Customer and Vendor mutually agree to remove interfaces from this scope, credit for the removed interfaces will be applied to the final invoice. However, if the credit amount is expected to exceed the total final quoted amount, an adjustment to the milestone payment table in Section 3.3.1 will be required to ensure proper reconciliation of project costs. In addition, the annual Solution subscription cost defined in Section

3.3.2 above for the interface will be adjusted. All changes to scope and associated costs will be documented and require mutual agreement between both parties. ii. Below is an itemized breakdown of all RMS Interfaces initially proposed, including the One-Time Services and Annual Support Costs for each RMS Interface.

Total RMS Interface Cost Summaries
RMS Interfaces One-Time
Service Cost
Annual Support
Cost
D.1 RMS- JDIC/CLETS/NCIC $31,578.00 $0
D.2 Karpel (Prosecutor Case Management) $15,489.00 $12,014.00 D.3 AFIS LiveScan_LACRIS $28,851.00 $0
D.4 CrimeTracer $27,024.00 $11,899.00
D.5 Citation Processing Center (CPC) $13,362.00 $7,482.00 Total Price $116,304.00 $31,395.00

3.4. Egress and Connectivity
Versaterm will provision redundant Customer VPN end points for up to 2 connections. Each VPN connection has two tunnels that should be configured by Customer to provide redundancy. Customer is responsible for providing and configuring the required Customer Gateway VPN hardware and software.

Customer Data shall be made available for egress for a total of 300 gigabytes per month. Any egress connectivity beyond this rate shall be charged periodically at prevailing rates at the time and shall be paid in full when and as required, and according to the termination provisions set forth in Section 20 “Orderly Termination” of the MSA.

3.5. Database / Disk Storage
Initial Database Storage
a. The initial database storage shall be made available as follows:
- a maximum of 200 gigabytes for the RMS Production Databases. - a maximum of 100 gigabytes (combined) for the RMS Test/Implementation and Training Databases. b. For each Subscription Renewal Term, an automatic database storage increase of 10% of the initial database storage maximums, as listed in this subsection, will be provided to accommodate storage growth over time. For example, if it is an increase of 10%: Year 1 - 300GB, Year 2 - 330GB, Year 3 - 360 GB, Year 4 - 390 GB, Year 5 - 420 GB.

Initial Disk Storage
254
Exhibit C – RMS SaaS Service Schedule for Cloud
Page | 7
a. The initial disk storage (for multimedia attachments and logs) shall be made available for a total maximum of 500 Gigabytes.
b. For each Subscription Renewal Term, an automatic disk storage increase of 10% of the initial disk storage maximum, as listed in this subsection, will be provided to accommodate storage growth over time. For example, if it is an increase of 10%: Year 1 – 500GB, Year 2 – 550 GB, Year 3 – 600 GB, Year 4 – 650 GB, Year 5 – 700 GB
Any storage use beyond these allocations will be charged at the current prevailing rates and shall be paid in full when and as required and in accordance with Section 20 “Orderly Termination” of the MSA.

Versaterm will notify Customer of current database/disk storage consumption prior to the annual subscription renewal to allow Customer can take appropriate action (e.g., increase storage).

4. Onboarding

4.1. Sub Exhibits to this Service Schedule shall include the following documentation detailing each party’s roles and responsibilities for the onboarding of the Subscription Service:

Exhibit C.1 – RMS Statement of Work (SOW)
Exhibit C.2 – RMS Project Implementation Schedule
Exhibit C.3 – RMS Interface Control Document (ICD)
Exhibit C.4 – RMS Data Conversion
Exhibit C.5 – RMS Acceptance Test Plan
Exhibit C.6 – RMS Training Plan
Exhibit C.7 – RMS Minimum Client and Peripheral Specifications

5. License

5.1. Compliance
The Customer will be responsible to Versaterm for compliance by Customer and all its Authorized Users of the terms of Section 5 of this Service Schedule.

5.2. License for Use - Subscription Service
Subject to the terms and conditions of the MSA and this Service Schedule, and the payment of the applicable Fees, Versaterm hereby grants to Customer, for use by its Authorized Users, a non-exclusive, non- transferable, non-sublicensable license to access the Subscription Service, as further detailed in Section 3.

The Subscription Service shall be accessible through a designated secure internet platform during the Term solely for the Customer’s use in conjunction with the Customer’s operations, and not for resale, access by third parties, or for other commercial purposes. Apart from the rights enumerated herein, the Subscription Service do not include a grant to the Customer of any right to use, nor any ownership right, title, or other interest, in or relating to Subscription Service, nor in any copy of any part of the Subscription Service.

5.3. License for Use - On-Site Software, if applicable
Subject to the terms and conditions of the MSA and this Service Schedule, and the payment of the applicable Fees, and where applicable, Versaterm hereby grants to the Customer, for use by its Authorized Users, a non- exclusive license to use the On-Site Software, as further detailed in Section 3. The On-Site Software may only be used solely for the Customer’s use in conjunction with the Customer’s operations. Apart from the rights enumerated herein, the license does not include a grant to the Customer, of any right to use, nor any 255
Exhibit C – RMS SaaS Service Schedule for Cloud
Page | 8
ownership right, title or other interest, in or relating to the On-Site Software, nor in any copy of any part of the On-Site Software.

5.4. Copies of User Documentation
Versaterm will provide Customer with access to the User Documentation, as may be updated from time to time. The Customer may use the User Documentation solely in connection with the use of Subscription Service, and may reproduce the User Documentation, provided that each copy thereby produced shall be marked with Versaterm’s proprietary markings as delivered to the Customer. The Customer shall not use, print, copy, translate or display the User Documentation in whole or part for any reason other than those expressly authorized herein.

5.5. Restrictions on Use
In addition to the license restrictions set forth in Section 4 of the MSA, the Customer and its Authorized Users will not and will not knowingly permit any third party to: (i) share the Customer’s or any Authorized User’s login credentials; (ii) copy, modify, adapt, translate, or make derivative works of the Subscription Service, Third Party Data, or Third Party Components, or otherwise make any use, resell, distribute or sublicense the Subscription Service, Third Party Data or Third Party-Supplied Components other than as permitted herein; (iv) create or augment any mapping-related dataset including a mapping or navigation dataset, business listings database, mailing list, or telemarketing list for use in an implementation that is not connected to the services; (v) hide or obscure any Authorized User’s location with malicious intent or purpose; (ix) permit access or use of the Subscription Service for any activities other than to enhance the Customer’s own services, where reliance solely on or failure to use the Software could lead to death, personal injury, or property damage. The Customer and its Authorized Users will not access the Subscription Service if in direct competition with Versaterm and will not allow access to the Subscription Service by any party who is in direct competition with Versaterm and/or its Affiliates, except with Versaterm’s prior written consent.

5.6. Third Party Applications
If Customer installs or enables a Third-Party Application for use with the Subscription Service, Customer grants Versaterm permission to access Customer Data stored on that Third Party Application as required for the interoperation of that Third Party Application with the Subscription Service. In no event will Versaterm be responsible for any Third-Party Application, or any failure of a Third-Party Application to properly interoperate with the Subscription Service. If Versaterm receives information that a Third-Party Application may violate any applicable laws or third-party rights, Customer will, promptly upon receiving notice of the foregoing from Versaterm, disable any connection between such Third-Party Application and the Subscription Service to resolve the potential violation (and if Customer fails to promptly disable such connection, Versaterm shall have the right to do so).

5.7. Third Party Components
Where there are any inconsistencies or conflict between the terms and conditions of Third-Party Components and the terms herein, such additional terms shall govern the Customer’s use of the applicable Third-Party Component. Third Party Component license(s) are restricted for use solely with Subscription Service.

VERSATERM, NOT BEING THE PROVIDER OR MANUFACTURER OF THE THIRD-PARTY COMPONENTS, NOR THE PROVIDERS' OR MANUFACTURERS’ AGENT, MAKES NO EXPRESS OR IMPLIED WARRANTY OF ANY KIND

WHATSOEVER WITH RESPECT TO THE THIRD-PARTY COMPONENTS AND DISCLAIMS ANY SUCH WARRANTIES THAT MIGHT OTHERWISE EXIST.

5.8. Third-Party Data
Customer shall access and use the Third-Party Data in accordance with the terms and conditions of the agreement between the Customer and the provider of such Third-Party Data. VERSATERM, NOT BEING THE PROVIDER OR MANUFACTURER OF THE THIRD-PARTY DATA, NOR THE PROVIDERS OR MANUFACTURERS’ 256
Exhibit C – RMS SaaS Service Schedule for Cloud
Page | 9

AGENT, MAKES NO EXPRESS OR IMPLIED WARRANTY OF ANY KIND WHATSOEVER WITH RESPECT TO THE THIRD-PARTY DATA AND DISCLAIMS ANY SUCH WARRANTIES THAT MIGHT OTHERWISE EXIST.

5.9. Customer Data
As between Versaterm and Customer, Customer owns and shall retain all rights, title, and interest, including, without limitation, all Intellectual Property Rights, in and to Customer Data. Customer shall have the sole responsibility for the accuracy, quality, and legality of the Customer Data, including obtaining all rights and consents necessary to share the Customer Data with Versaterm as set forth in this Agreement. Versaterm shall not access Customer user accounts or Customer Data except: (i) during data center operations, (ii) in response to services or technical issues, (iii) as required by the express terms of this Agreement, or (iv) at Customer’s written request. Versaterm shall not collect, access, or use user-specific Customer information except as strictly necessary to provide the Subscription Service to the Customer.

5.10. Software Enhancements and Optional Modules
Versaterm shall supply the following, subject to the Customer’s payment of applicable Fees, and subject to and in accordance with the license rights, restrictions, terms, covenants, conditions, warranties, limitations, exclusions, and other provisions set forth herein:
a. Major Enhancement Release(s) and/or Minor Enhancement Release(s) if any, to the Customer at no additional charge.
i. In the event of a Major Enhancement Release, Versaterm will deploy such upgrades to the Customer’s systems, as scheduled in advance, with appropriate notification to the Customer. Customer shall have 20 days to test the Major Enhancement Release, after which, it becomes part of the Software. ii. In the event of a Minor Enhancement Release, Versaterm will deploy such updates to the Customer’s system, as scheduled in advance, with appropriate notification to the Customer. With the goal of keeping such environments reasonably current, the Customer shall have 5 days to test the update, after which, the update shall become part of the Software. b. Interface modules that are developed by Versaterm for interfacing the Subscription Service to other software products, provided that such modules are specifically included herein. c. Changes to Subscription Service. Versaterm software operates on a variety of common web browser types. Versaterm reserves the right to provide the Subscription Service using only Versaterm Certified Browsers.

5.11. Disclaimer on Use
THE AUTOMATIC VEHICLE ROUTING RECOMMENDATION COMPONENT (“AVRR COMPONENT”), IF

LICENSED UNDER THIS AGREEMENT, IS INTENDED FOR USE AS ONE FACTOR IN DETERMINING THE BEST

VEHICLE ROUTING FOR THE CUSTOMER AND IS NOT INTENDED TO BE USED AS THE SOLE SOURCE FOR DETERMINING ROUTING, NOR WHICH VEHICLES TO DEPLOY TO ADDRESS ANY EMERGENCY SITUATION.

THE AVRR COMPONENT IS HEAVILY DEPENDENT ON THE QUALITY OF THE SOURCE MAPPING INFORMATION

INPUTTED BY OR ON BEHALF OF CUSTOMER AND VERSATERM WILL HAVE NO RESPONSIBILITY OR LIABILITY

FOR ANY ROUTING ERRORS AND/OR DELAYS, NOR ANY RESULTANT DAMAGE OR LOSS ARISING AS A

RESULT OF THE MAPPING DATA OR FOR ANY DAMAGES OR LOSS CAUSED BY ANY DECISION MADE OR ACTION TAKEN IN RELIANCE ON THE AVRR COMPONENT.

6. Subscription Support

6.1. Site Access
257
Exhibit C – RMS SaaS Service Schedule for Cloud
Page | 10
When reasonably requested by Versaterm, the Customer shall provide access to its premises, staff, and authorities, provided Versaterm staff meet the security requires defined in Section 8 of this Service Schedule.

6.2. Software Support
During Production Use, Versaterm may make Support available through access to Versaterm’s designated internet platform, and direct contact with the Customer. Such Support may consist of the periodic review of current outstanding questions and usage issues, new and upcoming releases of Major Enhancement and Minor Enhancements, and the periodic review of potential environment changes that could impact the use of the Subscription Services.

6.3. Regular Telephone Support
During Production Use, Versaterm will make Support available by telephone to the Support Contact at substantially all times from 7:30 a.m. (EST) until 5:30 p.m. (Customer local time) each day except Saturdays, Sundays, and legal holidays in the jurisdiction of the Customer. To the extent possible by telephone, email, and remote communication, Versaterm will attempt to identify and provide a workaround for the Problem and will use reasonable efforts to provide a final solution for the Problem, if that applies. Versaterm will normally respond to telephone requests for Critical Priority Errors and High Priority Errors within thirty (30) minutes of receipt of the call.

Escalation Path
Customer will receive a current escalation contact directory with direct phone numbers for Versaterm personnel at multiple levels, including executive management. This directory will be updated as organizational changes occur. Customer may escalate issues directly to any appropriate level, including executive leadership, based on the nature and urgency of the matter.

6.4. 7x24 Emergency Telephone Support
Versaterm will provide 7x24 Telephone Support that extends Support for problems identified as Critical Priority Error and High Priority Error to include all hours not already provided for within Regular Telephone Support. 7x24 Telephone Support allows the Customer’s internal support staff that are technically capable and who first troubleshoot the problem, to authorize Versaterm to provide 7x24 Telephone Support.

6.5. Configuration as a Service (CaaS) for RMS and MRE
Versaterm will provide ongoing Configuration as a Service (CaaS) to support RMS and MRE configuration maintenance. This includes scheduled, quarterly updates to select RMS Administration settings and the MRE Designer configuration. These updates will be conducted collaboratively with the Customer and focus exclusively on the items listed in the Scope of Versaterm Responsibilities section below.

Quarterly Update Process
Each quarter, the Customer will maintain and prioritize a list of desired configuration updates. During the final week of the quarter, Versaterm and the Customer will meet to review and agree on a feasible set of updates to be completed as well as the schedule for deployment within each quarter, for instance; o Week 1: Versaterm will complete the agreed-upon updates in the TEST environment. o Week 2: The Customer will review and accept the changes. Once approved, Versaterm will deploy the accepted updates to the PRODUCTION environment.

Out-of-Cycle Updates
Configuration changes outside the quarterly process will only be made under the following conditions:
258
Exhibit C – RMS SaaS Service Schedule for Cloud
Page | 11
o A critical feature is non-functional or not operating as intended o A legal or regulatory mandate requires the change
o A critical business need has been identified and approved at the agency-wide level Scope of Versaterm Responsibilities under CaaS
Versaterm’s configuration responsibilities under this service are strictly limited to the following settings:
o Versaterm-Managed RMS Configuration Settings
▪ Global Tables
▪ NIBRS Tables
▪ NCIC Tables
▪ Charge/Offense Table Maintenance
▪ Map Updates
▪ Security Group Maintenance
▪ Property Location Management
▪ Handle Maintenance
▪ Member Handle Maintenance
▪ Routing Rules
▪ Release Tracking
▪ Creation/Maintenance of Text Templates (Max 5)
▪ Creation/Maintenance of Word Forms (Max 5)
▪ Creation/Maintenance of Style Sheets (Max 5)
o Versaterm-Managed MRE Configuration
▪ Full CaaS for MRE via MRE Configuration Application (MCA) ▪ Creation/Maintenance of MRE Report Types (Max 10)
▪ MRE Builds
Customer Responsibilities (Not Included in CaaS)
All configuration settings not explicitly listed in the section above are outside the scope of Versaterm’s Configuration as a Service and will are the sole responsibility of the Customer. This includes, but is not limited to, the following configuration settings:
o Customer-Managed RMS Configuration Settings
▪ MNI Duplicate Names
▪ Invalid Address Maintenance
▪ User/Personnel Maintenance
▪ Org Unit Assignment Maintenance
▪ Jurisdictional Table Management
▪ Table Publishing
o Customer-Managed MRE Responsibilities
▪ Device compliance with minimum specifications
▪ Software Installation
Note : The Customer is responsible for ensuring all devices used with the system meet or exceed minimum performance and compatibility specifications as outlined in the applicable documentation.

6.6. Termination of Corrective Action
Versaterm may, but need not, terminate its corrective efforts under this Exhibit at any time if, in its business judgment:
259
Exhibit C – RMS SaaS Service Schedule for Cloud
Page | 12
a. The Customer fails to perform its obligations described herein; or b. The Customer is not using the then current unmodified version of the Software or other versions of the Software then supported by Versaterm; or
c. Versaterm and/or the Customer is not able to reproduce the Problem in the applicable operating environment and verify that the Problem is in fact in the Software and not elsewhere; or d. The Problem is not material; or
e. Further corrective efforts are not appropriate because the Problem has been identified and is caused by an external factor not within Versaterm’s control; or f. Versaterm has declared the Problem as probably being caused by something external to the supplied Subscription Service, such as aberrations within the Customer’s network (LAN and/or WAN and/or related network equipment). Versaterm will terminate work on this Problem unless the Customer authorizes further diagnosis effort that may be billable separately under this Agreement when and if the suspected external problem source is confirmed. If confirmed as being caused by an external source, then such work will be billed on a time and materials basis at the then prevailing hourly rates for Support (whether within or outside normal support hours) and can be authorized by e-mail by the designated Support Authority or other as designated in writing to Versaterm as having that authority.

6.7. Third Party Applications
Responsibilities for Planned Updates.

Customer shall provide Versaterm with prompt notice, and in no case fewer than sixty (60) days’ advance notice, of any update by the Third-Party Provider of a Third-Party Application. Subject to alignment with Versaterm’s cloud patch schedule, Versaterm shall undertake commercially reasonable efforts to patch or update the Software in order to integrate it with the updated Third-Party Application.

Responsibilities for Planned Upgrades.

Customer shall provide Versaterm with prompt notice, and in no case fewer than ninety (90) days’ advance notice, of any planned upgrade by the Third-Party Provider of a Third-Party Application. Subject to alignment with Versaterm’s cloud patch schedule, Versaterm shall evaluate the time and resources required to patch or update the Software in order to integrate it with the upgraded Third-Party Application. The Parties shall engage in good faith negotiations to agree on the terms (including, without limitation, schedule, and price) on which Versaterm would develop a patch, update, or upgrade to integrate the Software with the Third-Party Application.

7. System Performance and Availability Standards
This Section 7 sets forth the performance and availability standards to which the Versaterm vRMS is expected to perform, provided Customer meets Versaterm’s recommended hardware and network specifications, including server, desktop workstation, and mobile configurations, and that the Customer uses the Software according to its intended design. RMS Minimum Client and Peripheral Specifications are detailed in Sub Exhibit C-7 of this Service Schedule. Specifications and requirements are subject to change to support future Major Enhancement Releases.

The measured times exclude any factors that may be caused by factors outside of Versaterm’s control, such as, but not limited to, the network.

7.1. vRMS Transaction Response Times
260
Exhibit C – RMS SaaS Service Schedule for Cloud
Page | 13
The vRMS Software performance is based on transaction response times, which are measured from operator action until visual response is observed or until the operation is completed. The types of transactions that have predictable response times include the majority of navigational and maintenance transactions.

Versaterm does not provide expected response times for data-dependent transactions, such as, but not limited to, displaying data lists, displaying dashboards, uploading MRE reports from the MDT, querying external interfaces, attaching files, printing reports, or performing browse searches. For such types of data- dependent transactions, the response time results may vary depending on the amount of data involved, the sizes of the files involved, or the types of search criteria entered.

Navigational Transactions
Navigational transactions involve the ease of movement from screen to screen or field to field. The response time for navigational transactions is expected to usually take one second (or less). Examples include:
• Tabbing from field to field in any screen within the Software • Looking up valid values for a coded field
Module Load Transactions
Module load transactions involve the loading of a program module/feature that requires loading an application and initializing the functions. The response time for module load transactions is expected to usually take two second (or less). Examples include
• Loading of programs to access modules within the Software (e.g. loading the General Offense (GO) Report program from the main Records menu (of the vRMS application) Maintenance Transactions
Maintenance transactions involve add/update transactions in the backend database tables. The response time for maintenance transactions is expected to take three seconds or less. Examples include:
• Saving new or updated information entered into the Software screens, such as adding or updating a General Offense screen (note: transaction response time does not include the time required for the end-user to make a decision if prompted by the vRMS)

7.2. Availability Standards
During Production Use of the Subscription Service, the vRMS Software shall be available in the production environment 99.99% of the time. Availability applies to the core vRMS Software application as provided by Versaterm in the production environment, excluding downtime attributable to third-party systems, customer infrastructure, external integrations, or causes beyond Versaterm's reasonable control. The following specifications define both availability and the method by which it is calculated:

Availability is expressed as a percentage of the maximum expected availability over a given period. The Software shall be available seven days per week, 24 hours per day. The percentage availability for any period will be calculated as follows:
(Total Hours in Period – Hours System Unavailable) x 100 / Total Hours in Period "Unavailability" is where the vRMS Software is completely and generally unavailable for the Customer’s use (but not the use of any one Authorized User, or subset/group of users; or access from any one vRMS desktop, or group of vRMS desktops), and does not include any unavailability attributable to:
a. Scheduled downtime for maintenance;
b. Scheduled downtime for Major Enhancement Releases and Minor Enhancement Releases; 261
Exhibit C – RMS SaaS Service Schedule for Cloud
Page | 14
c. scheduled downtime for operating system patch updates; d. downtime for upgrades or updates to system software components and tools integrated as part of the Subscription Services;
e. downtime for upgrades or updates to cloud-based Third-Party Software Components and services integrated as part of the Subscription Services;
f. downtime related to connectivity issues resulting from Customer or third-party-provided or managed Direct Connect or VPN access to hosted server or Customer internal network problems; Customer will be responsible for immediately notifying Versaterm of all third-party-managed VPN access and internal or external (e.g. internet service provider) network problems that arise; g. an incident resulting from data or infrastructure or network provided and/or performed by the Customer; h. acts or omissions of Customer or any Customer user, Authorized User, or any employee, agent, or independent contractor of the Customer;
i. lack of availability or untimely response from the Customer that require the Customer’s participation for resolution;
j. the Customer’s negligence or breach of the Customer’s material obligations under the MSA or Service Schedule;
k. any other cause(s) beyond Versaterm’s reasonable control, including but not limited to those caused by Third Party Data, Third Party Applications, Third Party Provider, or Third-Party Components or other third- party software, as well as overall internet congestion, denial of service attack, or a force majeure event.

In the event the availability standards, as set forth in this section 7.2, are not met, Customer may request a meeting, which may be conducted in-person, with a Versaterm executive to discuss the issue and develop a remediation plan at no cost to the Customer.

8. Security

8.1. Versaterm agrees that all personnel Versaterm employs pursuant to this Service Schedule shall be subject to Versaterm’s background and security checks and screening (collectively “Background Screening”) at Versaterm's sole cost and expense as set forth in this paragraph. The Background Screening shall include, as a minimum, criminal record checks, local police record checks, and credit checks. Any additional Background Screening required by the Customer must be agreed to by Versaterm and may be at additional cost.

8.2. FBI CJIS Security Addendum. Versaterm agrees to the terms and requirements set forth in the Federal Bureau of Investigation (FBI) Criminal Justice Information Services (CJIS) Security Addendum for the Term of this Service Schedule.

9. Transition Assistance

9.1. Upon termination of the MSA or this Service Schedule for any reason, and subject to Fees due being paid in full, Versaterm will return Customer’s data in a CSV or other mutually agreed upon format for each record (“Record”) and provide them to the Customer for download. Records can be uploaded to Customer’s new system by the Customer or its new vendor. The transition assistance described in this Section 9.1 is included in the Fees. All other Fees are due and payable up to the cut-off date of the Subscription Service. 262
Versaterm Public Safety Inc. & City of Torrance
SaaS Agreement #
Exhibit C.1 – RMS Statement of Work

Page 1 of 33 ends

9.2. As an optional Transition Assistance, Versaterm shall provide, at an additional fee, the database, and other managed services, as mutually agreed upon.

9.3. Notwithstanding the foregoing, Versaterm reserves the right to retain Customer Data on audit logs and server system logs and in support tickets, support requests, and direct communications with Versaterm.

10. Additional Terms

10.1. Customer acknowledges that Versaterm shall not be required to deliver the Axon RMS CFS Transfer or the Motorola Radio MCC7500 interface as previously set forth in Service Schedule B. In the event that additional work or interfaces are required for the RMS implementation, the parties agree to reallocate the fees previously agreed upon under Service Schedule B, with such fees to be adjusted accordingly prior to go-live in the event the revised scope results in fees that are less than or greater than those originally contemplated. The parties agree to formalize the foregoing modifications by way of a written amendment to Service Schedule B, to be executed following execution of the RMS Contract and prior to the commencement of CAD Interface Testing, currently scheduled for completion on or about July 17, 2026.

IN WITNESS WHEREOF, the Parties hereto have executed this Service Schedule as of the day and year indicated below.

Versaterm Public Safety US, Inc.

By: By:

Name: Name:

Title: Title:

Date: Date:

CITY OF TORRANCE,
a municipal corporation
_______________________________
George K. Chen, Mayor
ATTEST:
_______________________________
Rebecca Poirier, MMC
City Clerk
APPROVED AS TO FORM:

PATRICK Q. SULLIVAN
City Attorney
By: ___________________________
Jeanne-Marie K. Litvin
Deputy City Attorney
263
Versaterm Public Safety Inc. & City of Torrance
SaaS Agreement #
Exhibit C.1 – RMS Statement of Work

Page 2 of 33 ends

EXHIBIT C.1

RMS STATEMENT OF WORK
264
Versaterm Public Safety Inc. & City of Torrance
SaaS Agreement #
Exhibit C.1 – RMS Statement of Work

Page 3 of 33 ends

1 Overview .................................................................................................................................................4

1.1 Project Summary and Objectives .......................................................................................................................4

1.1.1 Project Objectives ......................................................................................................................................4

1.2 Related Exhibits.................................................................................................................................................4

1.3 Definitions ........................................................................................................................................................5 2 Roles and Responsibilities ........................................................................................................................6

2.1 Project Management Overview .........................................................................................................................6

2.2 Project Management Tools ...............................................................................................................................6

2.3 Project Steering Committee...............................................................................................................................6

2.4 Versaterm Project Manager ..............................................................................................................................7

2.5 City Project Manager.........................................................................................................................................8

2.6 Organizations Responsibilities During the Project..............................................................................................9

2.6.1 Versaterm Responsibilities.............................................................................................................................9

2.6.2 Versaterm Project Team ................................................................................................................................9

2.6.3 City Responsibilities .....................................................................................................................................10

2.6.4 City Project Team.........................................................................................................................................10

2.7 Project Implementation Schedule....................................................................................................................11

2.8 Task Completion And MILESTONE PAYMENT ...................................................................................................11

2.9 Change Control................................................................................................................................................11

2.9.1 Project Schedule Adjustments .....................................................................................................................11

2.9.2 Scope and Cost Change Orders....................................................................................................................12 3 Software Deliverables ............................................................................................................................12

3.1 SOFTWARE ......................................................................................................................................................12

3.2 Interfaces – for Go-Live ...................................................................................................................................12

3.3 Redundancy and Backup Deliverables..............................................................................................................12 4 Key Assumptions....................................................................................................................................13

4.1 Software Version.............................................................................................................................................13

4.2 Third-party Products, Hardware and/or Services .............................................................................................13 5 Statement of Work Tasks .......................................................................................................................14

5.1 Planning & Contract Definition Phase - Task 1..................................................................................................14

CONTENTS
265
Versaterm Public Safety Inc. & City of Torrance
SaaS Agreement #
Exhibit C.1 – RMS Statement of Work

Page 4 of 33 ends

Task #1.2 Execute Contract...................................................................................................................................14

5.2 Project Initiation Phase - Task 5.......................................................................................................................14 Task #5.1 Initiate Project ......................................................................................................................................14 Task #5.2 Project Kickoff Meeting (Timeline Milestone #1) ................................................................................. 14

5.3 Provisioning Phase - Task 6..............................................................................................................................15 Task(s) #6.1 - #6.9 Build DEV/Test Environment...................................................................................................15 Task #6.7 Prepare a Configuration Lab/Classroom ...............................................................................................16 Task #6.10 Initial RMS Environment Provisioned (Subscription Start) (Timeline Milestone #2)........................... 17

5.4 RMS/MRE Implementation & Configuration - Task 7........................................................................................18 Task(s) #7.1 - #7.4 RMS/Mobile Configuration Workshops ..................................................................................18 Task #7.3 Configuration Workshop #2 Completed (Timeline Milestone #3) ........................................................ 19 Task #7.4 Configuration Workshop #3 Completed (Timeline Milestone #5) ........................................................ 20

5.5 Interface Development Phase - Task 8.............................................................................................................20 Task(S) #8.1 – 8.4 Develop and Install Interfaces..................................................................................................20

5.6 Build Production Environments – Task 10 (Timeline Milestone #4)................................................................... 21

5.7 Testing Phase - Task 11....................................................................................................................................22 Task #11.1 Interface Integration Testing (Timeline Milestone #6) ....................................................................... 22 Task #11.2 Functional acceptance Testing............................................................................................................23 Task #11.2.3 Attach Functional Acceptance Testing Acceptance Email (Timeline Milestone #7)......................... 24

5.8 Training Phase - Task 12 ..................................................................................................................................25 Task #6.7 Prepare A Configuration Lab.................................................................................................................25 Task #12.3 Train-the-Trainer Training...................................................................................................................25 Task #12.4 Ready For Use Declared (Timeline Milestone #8)............................................................................... 26 Task #12.5.2 Agency End-User Training (Timeline Milestone #9) ........................................................................ 27

5.9 Production Cutover and Close Support - Task 13..............................................................................................29 Task #13.1 Prepare Desktops and Mobile Computers..........................................................................................29 Task #13.3 Production Cutover – Go Live ............................................................................................................. 29

5.10 Response Time and Reliability Acceptance Testing – Task 14 .........................................................................30

5.11 Final System Acceptance – Task 15 (Timeline Milestone #10)......................................................................... 31 6 Communication Plan..............................................................................................................................32 7 Risk Management Plan...........................................................................................................................32 266
Versaterm Public Safety Inc. & City of Torrance
SaaS Agreement #
Exhibit C.1 – RMS Statement of Work

Page 5 of 33 ends

This document is the Statement of Work defining the principal tasks, activities and responsibilities of the parties involved in the implementation of the Application Software, interfaces and ancillary products.

This Project is a collaboration between the Parties, City of Torrance, hereafter “City” and Versaterm, and is contingent upon both entities fulfilling their respective responsibilities as defined in the Agreement and this Statement of Work.

The purpose of this project is to implement Versaterm’s Records Management System (RMS), Mobile Report Entry (MRE), and associated components to modernize and unify records management and field operations for the Torrance Police Department. The project will enhance operational efficiency, improve situational awareness and responder safety, and establish a scalable platform for future technology integration across public safety functions. • Implement Versaterm’s RMS system to replace the City’s legacy records system, supporting coordinated incident reporting for Police Operations.
• Deploy the Versaterm Mobile Report Entry (MRE) solution to enable real-time communication, incident management, and field reporting from police patrol vehicles.
• Configure shared and discipline-specific workflows that meet the operational needs of the Police Department. • Integrate essential modules and subsystems such as mapping, arrests, property, and case management. • Ensure a reliable, secure, and highly available Software-as-a-Service (SaaS) environment that complies with the City’s IT governance policies and meets all applicable public safety security requirements, including data protection, access controls, audit logging, and business continuity standards.
• Provide comprehensive training tailored to officers, supervisors, detectives, custody and property resources and system administrators to ensure successful adoption.
• Achieve a phased or coordinated go-live for Police with minimal operational disruption, including thorough testing, cutover planning, and post-implementation support.
• Agreement (MSA)
• Exhibit C – City of Torrance – RMS SaaS Service Schedule o License Terms
o Annual Subscription Support Terms
o Price and Payment Terms
• Sub Exhibits- RMS Onboarding Services
o Exhibit C.1- RMS Statement of Work (SOW)
o Exhibit C.2- RMS Project Implementation Schedule
o Exhibit C.3- RMS Interface Control Document
o Exhibit C.4- RMS Data Conversion
o Exhibit C.5- RMS Acceptance Test Plan
o Exhibit C.6- RMS Training Plan
o Exhibit C.7- RMS Minimum Client and Peripheral Specifications 1 OVERVIEW

1.1 PROJECT SUMMARY AND OBJECTIVES

1.1.1 PROJECT OBJECTIVES

1.2 RELATED EXHIBITS
267
Versaterm Public Safety Inc. & City of Torrance
SaaS Agreement #
Exhibit C.1 – RMS Statement of Work

Page 6 of 33 ends

The definitions provided in this section apply to this Statement of Work (Exhibit C.1 – RMS Statement of Work) and all associated sub-exhibits, including but not limited to the RMS Project Implementation Schedule, RMS Interface Control Document, RMS Acceptance Test Plan, RMS Training Plan, and RMS Minimum Client and Peripheral Specifications. These definitions are intended to ensure clarity and consistency in the interpretation of terms used throughout the SOW and its related documentation. Unless otherwise specified, the terms defined herein shall apply solely to this Statement of Work and its related exhibits and shall take precedence over conflicting terminology used within these exhibits.

Term Definition
Business Day Is any working day that aligns with the Client’s 9/80 work schedule, excluding Client- Observed Holidays. Under the 9/80 schedule, Business Days are Monday through Friday, except for alternating Fridays, which are designated as non-working days.

Additionally, any holidays officially recognized by the Client will not be considered a Business Day.

Client Refers to the City of Torrance, a California municipal corporation. For the purposes of this Statement of Work, the terms "City" and "Client" are used interchangeably to describe the contracting entity receiving services under this agreement.

PM Project Manager
Project The coordinated set of activities, deliverables, and milestones described in this Statement of Work and its related exhibits, undertaken by the City and Versaterm to implement the Records Management System (RMS) and its associated components.

The Project includes all phases of planning, configuration, testing, training, deployment, and post-implementation support necessary to achieve a successful go- live and system acceptance in accordance with the terms outlined herein.

Project Plan A comprehensive document outlining the Project's objectives, scope, timeline, milestones, resources, and responsibilities, serving as a roadmap for execution, monitoring, and successful completion.

Project Status Documents Periodic reports that provide an overview of Project progress, key milestones achieved, challenges encountered, risks, budget updates, and next steps. These documents ensure stakeholders remain informed and aligned with the Project's status and any necessary course corrections.

Subject Matter Expert (SME) An individual designated by the Client or Versaterm who possesses specialized knowledge and expertise in a specific area relevant to the Project. SMEs are responsible for providing clarifications, validating requirements, reviewing deliverables, and offering guidance to ensure alignment with business objectives and technical standards. Their involvement is essential for decision-making and successful Project execution.

Cyber Incident An event that threatens the confidentiality, integrity, or availability of City information systems, data, or network infrastructure. This includes, but is not limited to, unauthorized access, malware infections, denial-of-service attacks, data breaches, or any activity that violates City cybersecurity policies or disrupts normal system operations.

1.3 DEFINITIONS
268
Versaterm Public Safety Inc. & City of Torrance
SaaS Agreement #
Exhibit C.1 – RMS Statement of Work

Page 7 of 33 ends

The City and Versaterm shall each appoint a Project Manager for the Project, each possessing the experience, knowledge, and authority to make decisions and carry out the tasks outlined in the Project Implementation Schedule and this Statement of Work.

The Project Managers will be the primary points of contact between the Parties during the Project.

Each Project Manager shall be responsible for managing their respective organization’s Project Team resources and ensuring that their assigned Project Team members fulfill their responsibilities. Each will have access to resources necessary to complete the project (personnel, documents, physical areas, etc.) and will be responsible for coordinating administrative and technical decisions within the Project.

While both Project Managers will collaborate to coordinate and support the execution of the Project, Versaterm shall have overall responsibility for managing the Project, including coordinating all implementation activities, ensuring timely completion of deliverables, and meeting the Project objectives. Versaterm’s Project Manager shall oversee the day-to-day execution and integration of workstreams to ensure a successful implementation.

The following project artifacts will be maintained on Versaterm’s dedicated Project SharePoint site:
• Schedule (will be in Gantt format) and posted to Versaterm SharePoint site. All revisions shall be made on the SharePoint file.
• Issues List
• Task List/Action Items
• Change/Decision log
• Risk List/Register
The Versaterm Project Manager will grant access to the Versaterm’s dedicated Project SharePoint site for all assigned City of Torrance RMS Project team members.

If, for whatever reason, the SharePoint site becomes less than an effective method for sharing this information (mutually agreed upon by City and Versaterm), an alternative may be created/provided.

The Project Steering Committee is the primary governance body responsible for overseeing the strategic direction and success of the Project. Comprised of executive and departmental leaders, the committee ensures alignment with city-wide priorities, resolves escalated issues, and provides cross-functional guidance. • Resource Allocation: The Project Steering Committee is responsible for securing and allocating the necessary resources— financial, human, and material—to ensure the Project's successful execution. This includes obtaining approval for budgets and ensuring that the Project team has the tools and support needed to complete the Project efficiently. 2 ROLES AND RESPONSIBILITIES

2.1 PROJECT MANAGEMENT OVERVIEW

2.2 PROJECT MANAGEMENT TOOLS

2.3 PROJECT STEERING COMMITTEE
269
Versaterm Public Safety Inc. & City of Torrance
SaaS Agreement #
Exhibit C.1 – RMS Statement of Work

Page 8 of 33 ends

• Decision Making : As the ultimate decision-maker, the Project Steering Committee resolves escalated conflicts and makes critical decisions that impact the Project's direction. They provide guidance and support to the Project manager, ensuring that decisions are made in the best interest of the organization. • Change Management : The Steering Committee is responsible for reviewing and approving all formal change orders that impact the project's scope, budget, or schedule. The committee ensures that all change requests are aligned with strategic objectives, are appropriately justified, and have been vetted by the City’s Project Manager prior to submission. Their oversight ensures that changes are managed in a controlled, transparent, and accountable manner. • Leadership and Vision: The Steering Committee is responsible for ensuring that the Project team is aligned with the Project's aims and objectives, fostering a cohesive and motivated environment. Their leadership is crucial in guiding the Project toward achieving its goals.

Versaterm shall retain overall responsibility for project management and successful implementation of all deliverables described in this Statement of Work. The Versaterm Project Manager shall coordinate and manage all implementation activities in collaboration with the City’s Project Manager. Versaterm’s Project Manager is responsible for, but not limited to, the following:
• Develop and maintain Project Implementation Schedule on Versaterm’s dedicated Project SharePoint site. Including milestones, tasks, and dependencies. The initial plan shall be drafted by Versaterm’s Project Manager, approved by the City, and maintained thereafter by Versaterm.
• Ensure all Versaterm deliverables, and implementation activities are completed in accordance with the approved Project Implementation Schedule and any authorized Change Orders. • Lead, coordinate, and oversee the installation of all licensed Versaterm Application Software as well as all System Software and Third-Party Software included in the Agreement.
• Coordinate and oversee the development efforts of all contracted interfaces. • Tracking overall Project status.
• Prepare weekly project status reports identifying overall project status, recent accomplishments, outstanding issues, risks, action items, and upcoming events.
• Maintain regular communication with City’s Project Manager, providing timely responses, no later than five (5) Business Days, to issues raised by the City’s Project Manager.
• Conduct, or participate in, regular conference calls (e.g., weekly) to discuss project status updates, open issues, and identified risks
• Work with City Project Manager and staff to resolve identified issues and mitigate project risks identified in the Project Issues Log as requiring action
• Facilitate communication between City resources and Versaterm resources for Project tasks. • Develop the Communication Plan with assistance and input from the City Project Manager.

2.4 VERSATERM PROJECT MANAGER

2.4.1 PLANNING AND EXECUTION

2.4.2 COMMUNICATIONS

2.4.3 RESOURCE MANAGEMENT
270
Versaterm Public Safety Inc. & City of Torrance
SaaS Agreement #
Exhibit C.1 – RMS Statement of Work

Page 9 of 33 ends

• Manage internal Versaterm resources and efforts (technical tasks, implementation tasks, Support during the Configuration Phase, interface development efforts)
• Communicate with City resources regarding work effort in coordination with the City Project Manager • Assist the Versaterm Implementation Specialist during onsite Configuration workshops • Assist the Versaterm Implementation Specialist in conducting Versaterm Trainer Training • Provide onsite support during the City Trainer Training; remote support may be provided in lieu of onsite presence if mutually agreed upon by the City.
• Provide onsite support during the City End-User Training; remote support may be provided in lieu of onsite presence if mutually agreed upon by the City.
• Provide onsite support during cutover
• Provide front-line support during post-cutover testing and refinement period • Prepare project Change Order Request Forms per the Agreement • Oversee invoice preparation
The City’s Project Manager will serve as the primary point of contact and will support the coordination of City-side implementation activities, in collaboration with the Versaterm Project Manager. The City’s Project Manager is responsible for the following:
• Maintaining regular communication with the Versaterm Project Manager. • Coordinate the efforts of the City’s staff.
• Coordinating City activities with the Versaterm Project Manager. • Participating in regular conference calls and onsite meetings with the Versaterm Project Manager to discuss Project status updates, project issues, risks including mitigation efforts, and upcoming activities. • Reviewing Versaterm’s Project status reports.
• Tracking and resolving outstanding City issues and action items for Action Item Log. • Providing timely responses, no later than five (5) Business Days, to issues raised by the Versaterm Project Manager. • Facilitating communication between City and Third-Party resources and Versaterm’s resources for System Infrastructure, Interface and Data Conversion tasks.
• Managing communications and coordinating project activities with Third-Party vendors directly under contract with the City.
• Coordinating Versaterm access (SharePoint, onsite, and remote) • Providing workspace at the City’s project site for Versaterm’s Project Team.

2.4.4 CONFIGURATION WORKSHOPS

2.4.5 TRAINING

2.4.6 ROLLOUT

2.4.7 OTHER

2.5 CITY PROJECT MANAGER
271
Versaterm Public Safety Inc. & City of Torrance
SaaS Agreement #
Exhibit C.1 – RMS Statement of Work

Page 10 of 33 ends

• Requesting, discussing, and reviewing Change Order Request Forms prepared by the Versaterm Project Manager. • Coordinating approval and execution of Change Orders and Amendments as needed with the Project Steering Committee.

This section describes the roles and responsibilities of key Project resources throughout the duration of the Project.

Versaterm’s overall responsibility is to establish a designated Project Team for the duration of this project that has the expertise to carry out the assigned Project tasks and responsibilities. The Versaterm Project Team will use their expertise to provide information, guidance, and suggestions to the City regarding system requirements. They will also provide best practice recommendations and guidance on system requirements, configuration options, implementation strategies, and workflow considerations.

Although Versaterm Project Team members may not be exclusively assigned to the Project, Versaterm shall allocate sufficient personnel time and resources to meet its obligations under this Statement of Work, including adherence to the Project Implementation Schedule.

When necessary and authorized by the City, Versaterm personnel may access City infrastructure, workstations, and/or Mobile Data Computers (MDCs) via VPN solely for purposes related to the Project, and only for the duration of the Project. Versaterm shall comply with all applicable City security policies and procedures governing such access. The City reserves the right to suspend or revoke access at its sole discretion in the event of a security violation or noncompliance or suspected or confirmed Cyber Incident.

Any costs incurred by Versaterm due to revoked access, including travel-related expenses, shall be the sole responsibility of Versaterm. The City shall provide VPN access at no cost to Versaterm.

The Versaterm Project Team will consist of, but not limited to a Project Manager, an Implementation Specialist, and a Technical Lead.

The Versaterm Implementation Specialist is responsible for delivering the Configuration workshops to the City Project Team, performing the configuration of the Versaterm RMS and MRE based on approved City requirements, and reviewing business re- engineering options. The Implementation Specialist shall work collaboratively with the City Project Manager and Technical SME to gather input and ensure that configuration decisions align with operational needs and technical feasibility. The Implementation Specialist shall provide guidance on best practices for business processes and ensure alignment with the system’s capabilities. The Implementation Specialist shall provide regular updates to the Versaterm Project Manager and proactively flag any configuration dependencies or decisions requiring escalation.

The Versaterm Technical Lead is responsible for delivering the technical aspects of the Project, including performing system configuration, interface coordination, infrastructure guidance, environment preparation, and system integration support. The Versaterm Technical Lead will assist in Configuration workshops, advise on security and performance best practices, and collaborate closely with the City Technical Lead. The Versaterm Technical Lead shall participate in technical discussions with City-designated third-party vendors and support data conversion planning and testing activities. The Versaterm Technical Lead shall provide regular updates to the Versaterm Project Manager and coordinate directly with the City Technical Lead on all technical deliverables and timelines.

2.6 ORGANIZATIONS RESPONSIBILITIES DURING THE PROJECT

2.6.1 VERSATERM RESPONSIBILITIES

2.6.2 VERSATERM PROJECT TEAM
272
Versaterm Public Safety Inc. & City of Torrance
SaaS Agreement #
Exhibit C.1 – RMS Statement of Work

Page 11 of 33 ends

Versaterm shall ensure that sufficient personnel and expertise are assigned to meet the obligations of this Statement of Work and to support successful Project execution. The roles identified above represent the initial core team; however, Versaterm is responsible for augmenting or expanding its Project Team, as needed, to address workload demands, meet Project milestones, and ensure timely completion of the Project.

The City’s overall responsibility is to establish a Project Team for the duration of this Project. The Project Team members should have the expertise to carry out the assigned Project tasks and responsibilities as indicated in this Statement of Work.

Although City Project Team members may not be exclusively assigned to the Project, City shall allocate sufficient personnel time and resources to meet its obligations under this Statement of Work, including adherence to the Project Implementation Schedule.

The City is responsible for providing desktop computers and mobile workstations for the City to use during the Configuration phase.

The City workstations must meet Versaterm’s minimum specifications as specified in Exhibit C.6 – RMS Minimum Client and Peripheral Specifications.

The City will provide a Project Team consisting of, but not limited to, the following roles, which may change based on project need:
• Project Manager * as defined in Section 2.5
• Technical Lead - responsible for providing subject matter expertise on the City’s technical environment, including infrastructure, integrations, mapping (GIS), and system access. This role supports Configuration workshops, interface coordination, data extraction and validation, and environment readiness. The Technical SME will work closely with the Versaterm Technical Lead to align technical deliverables and will act as the primary liaison for involving other City technical resources as needed to support the Project.
• RMS System Administrator - responsible for providing subject matter expertise on the Police Department’s records management Standard Operating Procedures (SOPs) and current Police RMS functionality. This role supports Configuration workshops, testing, and environment readiness. The RMS System Administrator will work closely with the Versaterm Implementation Team to align functional configuration of the RMS and will act as the primary liaison for involving other Police Records resources as needed to support the Project.
• Patrol Division SME - responsible for providing subject matter expertise on the Police Department’s Incident Response and Report Writing Standard Operating Procedures (SOPs) and current Police RMS/Mobile functionality. This role supports Configuration workshops, testing, and environment readiness. The Police Mobile SME will work closely with the Versaterm Implementation Team to align functional configuration of the MRE and will act as the primary liaison for involving other Police Incident Response resources as needed to support the Project. • Investigations SME - responsible for providing subject matter expertise on the Police Department’s Investigation and Case Management Standard Operating Procedures (SOPs) and current Police RMS/Mobile functionality. This role supports Configuration workshops, testing, and environment readiness. The Investigations SME will work closely with the Versaterm Implementation Team to align functional configuration of the RMS and will act as the primary liaison for involving other Police Investigation resources as needed to support the Project. • Property and Evidence SME - responsible for providing subject matter expertise on the Police Department’s Property and Evidence Standard Operating Procedures (SOPs) and current Police RMS functionality. This role supports Configuration workshops, testing, and environment readiness. The Property and Evidence SME will work closely with the Versaterm

2.6.3 CITY RESPONSIBILITIES

2.6.4 CITY PROJECT TEAM
273
Versaterm Public Safety Inc. & City of Torrance
SaaS Agreement #
Exhibit C.1 – RMS Statement of Work

Page 12 of 33 ends

Implementation Team to align functional configuration of the RMS and will act as the primary liaison for involving other Property and Evidence resources as needed to support the Project. • Custody/Detention SME - responsible for providing subject matter expertise on the Police Department’s Custody/Detention Standard Operating Procedures (SOPs) and current Police RMS/Mobile functionality. This role supports Configuration workshops, testing, and environment readiness. The Police Mobile SME will work closely with the Versaterm Implementation Team to align functional configuration of the RMS and will act as the primary liaison for involving other Custody/Detention resources as needed to support the Project.
• Crime Analyst SME - responsible for providing subject matter expertise on the Police Department’s Incident Response and Report Writing Standard Operating Procedures (SOPs) and current Police RMS/Mobile functionality. This role supports Configuration workshops, testing, and environment readiness. The Crime Analyst SME will work closely with the Versaterm Implementation Team to align functional configuration of the MRE and will act as the primary liaison for involving other Crime Analysis resources as needed to support the Project.
• Training Lead - responsible for coordinating with Versaterm on the creation of Training materials and strategizing and conducting End User and ongoing Training. This role could be assumed by one/some of the SME’s listed above. * The project team leader will have direct access to the command team as required.

The Project Implementation Schedule will be updated as necessary over the course of the Project. All changes to the schedule will be mutually agreed upon and, if required, documented via the mutually agreed upon Change Order Process.

When all Task Completion Criteria have been met for each task in this Statement of Work or the corresponding Exhibits, the Versaterm Project Manager will be responsible for providing written notification (via email) to the City Project Manager, specifying the task and confirming the criteria that were met.

All such tasks are subject to the City’s formal review and approval before being considered accepted, regardless of whether the task is associated with a milestone payment. The City Project Manager will notify the Versaterm Project Manager of the approval or will provide written feedback identifying any deficiencies if the task does not meet the defined Task Completion Criteria.

The City will retain a copy of the confirmation or feedback for documentation purposes, and milestone payments shall only be made upon the City’s formal approval of the corresponding task(s).

To maintain alignment, transparency, and control throughout the course of the Project, the following change control procedures shall apply to any modifications to the Project Implementation Schedule, scope of work, or cost:

Minor adjustments to the Project Implementation Schedule that do not affect the Project’s critical path or overall go-live date may be reviewed and approved jointly by the City and Versaterm Project Managers. Such adjustments include resource availability changes or internal task re-sequencing that do not impact major milestones.

2.7 PROJECT IMPLEMENTATION SCHEDULE

2.8 TASK COMPLETION AND MILESTONE PAYMENT

2.9 CHANGE CONTROL

2.9.1 PROJECT SCHEDULE ADJUSTMENTS
274
Versaterm Public Safety Inc. & City of Torrance
SaaS Agreement #
Exhibit C.1 – RMS Statement of Work

Page 13 of 33 ends

However, any proposed schedule change that affects the Project’s critical path or results in a delay to the agreed-upon go-live date shall be escalated to the Project Steering Committee for review and approval. The Versaterm Project Manager shall be responsible for updating the Project Implementation Schedule upon approval of the change.

All changes that affect the scope of work, deliverables, or cost shall require a formal Change Order, to be reviewed and approved by the Project Steering Committee prior to implementation. Each Change Order must include:
• A description of the proposed change,
• Its impact on the scope, schedule, deliverables, and cost, • Any associated risks or resource implications.

Change Orders shall not be considered authorized or binding until approved in writing by the City and incorporated into the Agreement by amendment if required.

This section describes the Project’s software deliverables to be provided by Versaterm. Detailed information regarding some deliverables may be found elsewhere (RMS Interface Control Document (Exhibit C.3). • Cost information for each deliverable is included in Exhibit C – City of Torrance – RMS SaaS Service Schedule. Options City elects to include in the project scope will add cost and will be paid according to the Change Order. Interfaces, options, and priced components that the City removes from scope will result in a credit toward cost, as designated by the particular Change Order.
• See Exhibit C – City of Torrance – RMS SaaS Service Schedule • See Exhibit C.3 – RMS Interface Control Documents
The Versaterm cloud RMS makes use of multiple back-end application instances, supporting an active-active configuration, that are load balanced across AWS Availability Zones (AZs). Availability Zones are separate datacenters connected to each other via low latency network links and completely separate infrastructure. This makes the RMS not only highly available, but fault tolerant as well since an outage of a single node or availability zone (datacenter), will not cause an extended outage to the end user (users will be automatically re-directed to the surviving datacenter/nodes where they may have to re-authenticate/login to the RMS). While the Versaterm RMS vCloud configuration provides resiliency across datacenters/AZs, it does not protect against an outage of the entire AWS GovCloud Region.

RMS users connect to the application by means of a highly available load balancer in the AWS infrastructure. The RMS system will utilize Open ID Connect (OIDC) to connect to Microsoft Entra ID for user authentication.

2.9.2 SCOPE AND COST CHANGE ORDERS
3 SOFTWARE DELIVERABLES

3.1 SOFTWARE

3.2 INTERFACES – FOR GO-LIVE

3.3 REDUNDANCY AND BACKUP DELIVERABLES
275
Versaterm Public Safety Inc. & City of Torrance
SaaS Agreement #
Exhibit C.1 – RMS Statement of Work

Page 14 of 33 ends

The underlying application and data files are stored across the AZs, which provides resiliency. Multiple copies of the files and database are maintained. This configuration will provide the 99.99% availability requested (See Exhibit C – City of Torrance – RMS SaaS Service Schedule: Section 7 System Performance and Availability Standards for exceptions) as well as 99.999999999% (11-9s) durability of stored data (for files stored on and backed up to AWS S3 data storage).

All the data in the RMS is encrypted at rest and in transit including database backups and data files. A strict backup mechanism further ensures that the entire environment is safe should any unforeseen problem cause major issues in the main environments. A rotation of daily and monthly snapshot backup files will be copied to AWS’s S3 file storage system, which is encrypted and highly resilient (a minimum of 3 copies of the data is kept).
• Versaterm will supply the latest available released version of the products to the City at Go-Live. • As a hosted System, Versaterm will keep the products up to date with the latest release, within the parameters of Versaterm’s Update and Upgrade processes.

These are not provided by Versaterm, but could be required for the solution:
• Mobile Printers (if printing is needed from patrol vehicles) • Smartphones (for vMobile)
• Connection to AWS GovCloud (Direct Connect is optional) • Property Barcode scanning devices
• Property Barcode printers
4 KEY ASSUMPTIONS

4.1 SOFTWARE VERSION

4.2 THIRD-PARTY PRODUCTS, HARDWARE AND/OR SERVICES
276
Versaterm Public Safety Inc. & City of Torrance
SaaS Agreement #
Exhibit C.1 – RMS Statement of Work

Page 15 of 33 ends

This section describes the Project’s major implementation tasks, identifying City and Versaterm responsibilities, prerequisites, Versaterm deliverables and completion criteria for each task.

The precursors, start dates, durations, and responsible resources for each task are tracked in the Project Implementation Schedule (Exhibit C.2). Statement of Work tasks outlined below and the tasks in the Project Implementation Schedule may not always start and complete in a sequential manner.

The Project will officially start upon the Effective Date of the Agreement.

Leading up to this task, the City and Versaterm Project Managers will have coordinated and completed all Scoping and Contract Negotiation efforts and have agreed in principle on the updated framework of the Contract. • Fully executed RMS Contract, as defined in Section 1.2 ‘Related Exhibits’ above.

The Project will officially start upon the Effective Date of the Agreement.

City and Versaterm Project Managers will collaborate to develop the agenda and materials for the Project Kick-off meeting/workshop to introduce the project to City Project Team and key stakeholders. This workshop will include a high-level presentation covering the following topics:
• Overall project scope
• Key contract elements
• City Project Team introduction
• City Project Team requirements, roles, and assignments • Versaterm Project Team introduction
• Versaterm roles and assignments
• Project Implementation Schedule
• Other key project details (e.g., risks, communication plan, change management) 5 STATEMENT OF WORK TASKS

5.1 PLANNING & CONTRACT DEFINITION PHASE - TASK 1
TASK #1.2 EXECUTE CONTRACT

VERSATERM DELIVERABLES

5.2 PROJECT INITIATION PHASE - TASK 5
TASK #5.1 INITIATE PROJECT
TASK #5.2 PROJECT KICKOFF MEETING (TIMELINE MILESTONE #1)

VERSATERM RESPONSIBILITIES
277
Versaterm Public Safety Inc. & City of Torrance
SaaS Agreement #
Exhibit C.1 – RMS Statement of Work

Page 16 of 33 ends

• Work with the City to develop the Kickoff Presentation. • Participate in the Project Kickoff Meeting.
• Provide location and logistical support for Project Kickoff meeting. • Invite the Project Team and other key stakeholders to attend the meeting. • Participate in the Project Kickoff presentation.
• Project Implementation Schedule has been finalized.
• Project Kickoff Meeting concluded.

AWS Connectivity will have already been established with the Torrance PD/FD CAD Implementation project.

Configure the RMS/MRE server Application Software within the implementation / test VMWare images and install the RMS/MRE desktop Application Software within the designated Implementation Team workspace and on each of the team’s workstations.

System implementation will be conducted on the AWS (Amazon's Web Service) “non-prod” environment. In this configuration the non-prod (non-production use) environment will contain both a test system and a training system. Both systems will be available for implementation use. The test system will be used for interface development and testing while the training system will be used for the core implementation tasks. As interfaces are completed, they will also be installed on the training system in coordination with the Customer’s team.
• Configure the Versaterm server Application Software within the implementation / test VMWare images. • Load mutually agreed upon initial tables such as ‘User Identification Numbers’. • Load the street files, if available.
• Configure the initial RMS and MRE.
• Create one operating-system printer and instruct the City on how to create additional printers. • Provide the City with the RMS Software and MRE Application Software for installation on the classroom workstations and the implementation team’s workstations.
• Assist Versaterm as needed.

CITY RESPONSIBILITIES

PREREQUISITES

TASK COMPLETION CRITERIA

5.3 PROVISIONING PHASE - TASK 6
TASK(S) #6.1 - #6.9 BUILD DEV/TEST ENVIRONMENT

VERSATERM RESPONSIBILITIES

CITY RESPONSIBILITIES
278
Versaterm Public Safety Inc. & City of Torrance
SaaS Agreement #
Exhibit C.1 – RMS Statement of Work

Page 17 of 33 ends

• Provide GIS shapefiles and map packages as required to create the Master Street Index file and initial map configuration. • Work with Versaterm to identify the initial tables to be loaded such as ‘User Identification Numbers’. • Create required operating-system printer definitions. • Create user accounts required by the City’s Implementation Team to access the Versaterm application suites. • Install and configure the RMS and MRE client Application Software on designated workspace and implementation team workstations.
• Project Kickoff Meeting concluded.
• Establish communications to AWS
• City has provided local values for select Versaterm RMS tables. • Versaterm-provided documentation on how to install and configure the client module (RMS) on City workstations. • The Versaterm server Application Software is configured within the implementation / test VMWare images; and • The RMS/MRE desktop Application Software installed on the workspace and Implementation Team’s workstations and is fully functional.

Equip a facility that will be available to the Implementation Team throughout the implementation period.

The City will provide a workspace(s) that will accommodate all implementation team members during the implementation sessions.

This space must remain operational to the implementation team members for the duration of the project for configuration and testing assignments. The workspace must be equipped with two computer projectors, a computer workstation for the instructor, and a computer workstation for each implementation team participant. The minimum effectiveness is space for five Team Members.
• Provide the City with desktops, network requirements and projection requirements for the workspace facilities. • Identify the number of workstations required for minimum effectiveness. • Provide a suitable workspace facility, including desktop workstations with two monitors for each of the Implementation Team Members, a desktop workstation for the instructor and projection facilities. • Ensure the workstations meet the minimum specifications as set forth in “Exhibit C.7– RMS Minimum Client and Peripheral Specifications”.
• Provide network access from each workstation to the Versaterm application servers.

PREREQUISITES

VERSATERM DELIVERABLES

TASK COMPLETION CRITERIA
TASK #6.7 PREPARE A CONFIGURATION LAB/CLASSROOM

VERSATERM RESPONSIBILITIES

CITY RESPONSIBILITIES
279
Versaterm Public Safety Inc. & City of Torrance
SaaS Agreement #
Exhibit C.1 – RMS Statement of Work

Page 18 of 33 ends

• The workspace is available and fully functional as described above.

Configure the RMS and install mobile Application Software within the designated Customer’s project classroom workspace and on each of the team’s workstations. This task signifies that the cloud environment has been provisioned, and the annual subscription begins.
• Configure the Versaterm server Application Software installed in the AWS Cloud. • Connect the System to the Customer’s Active Directory. • Load mutually agreed upon initial tables such as ‘User Identification Numbers’. • Load the street files, if available.
• Configure the initial RMS and MRE.
• Provide the Customer with the RMS and mobile Application Client Software for installation on the classroom workstations and the Customer’s project team’s workstations.
• Assist Versaterm as needed.
• Provide GIS shapefiles and map packages as required to create the master street index file and initial map configuration. • Work with Versaterm to identify the initial tables to be loaded such as ‘User Identification Numbers’. • Create Active Directory user accounts required by the Versaterm and the Customer’s project team to access the Versaterm application suites.
• Install and configure client Application Software on designated workspace and project team workstations. • Provisioning non-production environment.
• Versaterm-provided documentation on how to install and configure the client modules on Customer workstations and mobile devices.
• The vRMS Application Software is configured in the AWS Cloud; and • The RMS and mobile Client Application Software are installed on the workspace and project team’s workstations and is fully functional.

TASK COMPLETION CRITERIA
TASK #6.10 INITIAL RMS ENVIRONMENT PROVISIONED (SUBSCRIPTION START) (TIMELINE MILESTONE #2)

VERSATERM RESPONSIBILITIES

CUSTOMER RESPONSIBILITIES

PREREQUISITES

VERSATERM DELIVERABLES

TASK COMPLETION CRITERIA
280
Versaterm Public Safety Inc. & City of Torrance
SaaS Agreement #
Exhibit C.1 – RMS Statement of Work

Page 19 of 32 ends

The purpose of the Configuration Phase is to build and configure the System.

These tasks and deliverables include both technical tasks and software familiarity tasks. Technical tasks involve activities such as the setup of the software, the development of the interfaces, testing of data conversion runs, and building agency-specific stylesheets, reports, and dashboard configurations, whereas software familiarity tasks involve a number of activities that take place in the form of Configuration Workshops (most will be held virtually).

Configuration Workshops provide the City’s Project Team with an overall understanding of the Versaterm applications and interfaces, including various configuration options. During this Configuration Phase, configuration workshops will be mutually scheduled by the project managers. The workshops focus on reviewing/discussing the needs of each Business Unit that will be using the respective Versaterm solutions. Any additional sessions focused on special topics as deemed appropriate by City and Versaterm, will also be mutually scheduled during this phase.

The topics covered in each Workshop week are prepared by Versaterm (designed to provide gradual learning experience), where each day will incorporate a combination of product demonstrations, system configuration explanations, business practice analysis, business workflow process discussions, and some hands-on exercises. In addition to product familiarization, the Workshops also focus on discussing current-versus-future workflow processes, and the impacts the future process will have on the affected end- users.

It is the Customer and Versaterm’s intention to conduct configuration workshops in person at a classroom facility provided by the Customer, unless mutually agreed that a workshop would be conducted remotely. The classroom will remain operational to the Customer’s project team members for the duration of the project for configuration and testing assignments. The classroom facility must include 2 computer projectors, a computer workstation for the instructor and a computer workstation for each Customer’s project team participant. Each workstation should be equipped with two monitors.

During the Project Kickoff Workshop, Versaterm will have provided the City's Project Team with a high-level introduction to the Versaterm RMS and Mobile applications.

The high-level introduction involves an overview of the functionality, features, and configuration options, as well as a discussion of potential re-engineering points. The specific activities include demonstrations of the products, hands-on exercises and group discussions. Versaterm will devote time to the City’s Project Team to present their current business practices as a contribution to the discussions regarding business process reengineering. During each subsequent session, Versaterm will provide detailed demonstrations of additional configuration options and will facilitate further discussion of business process re-engineering opportunities. The result of such discussions will provide a roadmap for Versaterm’s configuration activities. • Coordinate and schedule Configuration Workshops for each line of Business with the City’s Project Manager. • Provide an agenda with objectives and business processes to review no less than ten (15) Business Days prior to the scheduled sessions.
• Provide one reproducible copy of the Documentation and any required session materials (User and Configuration guides) in soft copy at least ten (10) Business Days prior to the scheduled workshop.

5.4 RMS/MRE IMPLEMENTATION & CONFIGURATION - TASK 7
TASK(S) #7.1 - #7.4 RMS/MOBILE CONFIGURATION WORKSHOPS

VERSATERM RESPONSIBILITIES
281
Versaterm Public Safety Inc. & City of Torrance
SaaS Agreement #
Exhibit C.1 – RMS Statement of Work

Page 20 of 32 ends

• Conduct in-depth demonstrations of the Application Software, identifying functionality and features supported, re- engineering points and configuration options.
• If possible, provide hands-on exercises for the Project Team members to get familiar with the Systems. • Assist the City's Project Team in reviewing the City’s existing business processes and paper forms as compared with System data flow and table options.
• Discuss workflow analysis to assess any required business re-engineering impacts. • Review the System Configuration progress to-date during each Configuration Workshop. • Review outstanding Configuration and business process re-engineering issues. • Document any required City business re-engineering points and any issues discussed during Configuration Workshops that need to be resolved.
• Coordinate the location and scheduling of the Configuration Workshops with the Versaterm Project Manager. • Identify and schedule the Configuration Workshops attendees. • Reproduce and provide the required Documentation and materials (User and Configuration guides) for Configuration Workshops participants in both hard and soft copy formats. • Ensure that designated Configuration Workshops participants fully participate in the scheduled workshop. • Prepare and lead reviews and discussions of the City’s existing business processes identified in workshop agendas. • Identify and make notes of known/potential workflow, process, job, and/or report changes. • Development/Test environment has been set up.
• Application Software has been delivered and installed. • Configuration Workshop materials (User and Configuration guides) in hard and soft copy format for each workshop participant.
• Delivery of Configuration Workshops.
• Workshop participants have received sufficient training to navigate and assist with the System Configuration. • Any required City business process re-engineering points covered during the workshop have been identified and documented.
• All identified issues have been documented in the Action Items Log. • Configuration Workshops completed.

Versaterm and the City shall meet or participate in conference calls to review and Sign-Off on Configuration Phase.

CITY RESPONSIBILITIES

PREREQUISITES

VERSATERM DELIVERABLES

TASK COMPLETION CRITERIA
TASK #7.3 CONFIGURATION WORKSHOP #2 COMPLETED (TIMELINE MILESTONE #3) 282
Versaterm Public Safety Inc. & City of Torrance
SaaS Agreement #
Exhibit C.1 – RMS Statement of Work

Page 21 of 32 ends

• Provide milestone invoice as per • See Exhibit C – City of Torrance – RMS SaaS Service Schedule • The RMS, MRE, and vMobile Configuration Workshop #2 has been completed and accepted by the City.

Versaterm and the City shall meet or participate in conference calls to review and Sign-Off on Configuration Phase. • Provide milestone invoice as per • See Exhibit C – City of Torrance – RMS SaaS Service Schedule • The RMS, MRE, and vMobile Configuration Workshop #3 has been completed and accepted by the City. • Configuration has been accepted, and the Agency is ready for Testing.

The Interfaces identified in RMS Interface Control Document (Exhibit C.3) will be developed, installed and tested.

Interface development will follow Agile methodology to allow for contingencies (i.e., certain things can change once both Parties start developing). While Exhibit C.3 – RMS Interface Control Document, serves to provide a high-level definition of the Scope, expectations and roles/responsibilities of each Interface, there is flexibility for making changes to the Interface expectations once the development and testing process begins, so long as Versaterm and the City mutually agree to any changes.

Any changes agreed upon are to be documented within Exhibit C.3 – RMS Interface Control Document and must be executed prior to continuing with the Interface development effort.
• Collaboratively, with the City and other Interface stakeholders, design, develop and install the Interfaces in accordance with each Interface's ICD.
• Discuss with the City and other Interface stakeholders any required changes in Interface Implementation from the Interface's ICD.
• Document additional details and any exceptions and/or deviations from an Interface's ICD in a revised ICD for that Interface.
• Prepare a Change Order or Amendment, whichever is appropriate, for any significant changes to an Interface's ICD.

VERSATERM DELIVERABLES

TASK COMPLETION CRITERIA
TASK #7.4 CONFIGURATION WORKSHOP #3 COMPLETED (TIMELINE MILESTONE #5)

VERSATERM DELIVERABLES

TASK COMPLETION CRITERIA

5.5 INTERFACE DEVELOPMENT PHASE - TASK 8
TASK(S) #8.1 – 8.4 DEVELOP AND INSTALL INTERFACES

VERSATERM RESPONSIBILITIES
283
Versaterm Public Safety Inc. & City of Torrance
SaaS Agreement #
Exhibit C.1 – RMS Statement of Work

Page 22 of 32 ends

• Schedule Interface tests at least ten (10) Business Days prior to the scheduled testing. • Perform initial testing on the Interfaces and provide the City with verification of functionality. • Collaboratively with Versaterm and other Interface stakeholders participate in the design, development and installation of the Interfaces in accordance with each Interface's ICD. • Review and approve any required changes to an Interface ICD. • Arrange for execution of mutually agreed upon ICD Change Orders or Amendments. • Provide the most updated Documentation available from appropriate third-party Interface stakeholders as required by Versaterm to complete the Interfaces.
• Provide all liaison support with third-party Interface stakeholders as required to support the installation and testing of the Interfaces.
• Complete the tasks listed as City responsibilities specified in the RMS Interface Control Document (Exhibit C.3). • Coordinate with Versaterm and third-party Interface stakeholders to schedule Interface tests. • Provide test facilities for the Interfaces.
• Verify the functionality of the Interfaces.
• Set up Development/Test Environment
• Documentation for any changes to the RMS Interface Control Document. • Design Specifications for each interface defined in RMS Interface Control Document (Exhibit C.3). • Implementation of Interfaces as defined in the RMS Interface Control Document. • Training as appropriate for each interface.
• Interface Control Documents (ICDs) are updated as required to Implement the Interfaces. • The set of System Interfaces are installed and tested to verify that they operate in accordance with the ICDs contained in the RMS Interface Control Document (Exhibit C.3).

System production use will be conducted on the AWS production environment. In this configuration the production (production use) environment will contain the Production system, which includes a read-only reporting database. This Production system will be installed by Versaterm and will consist of all System implementation data and interfaces (once completed). Although not mandatory, Versaterm does recommend training be performed on the Production system in order to exercise the entire system.

Versaterm will notify the City when it is satisfied that the System is ready for Training and Functional Acceptance Testing in the Production Environment.

CITY RESPONSIBILITIES

PREREQUISITES

VERSATERM DELIVERABLES

TASK COMPLETION CRITERIA

5.6 BUILD PRODUCTION ENVIRONMENTS – TASK 10 (TIMELINE MILESTONE #4)

VERSATERM RESPONSIBILITIES
284
Versaterm Public Safety Inc. & City of Torrance
SaaS Agreement #
Exhibit C.1 – RMS Statement of Work

Page 23 of 32 ends

• Provide the AWS Cloud computing system containing the Production system. • Assist the City with AWS networking configurations and ensure access to the AWS Cloud production environment. • Provide details on required ports that must be opened or configured. • Migrate configuration data from implementation / test environment to the production environment (including City’s GIS data).
• Conduct informal system testing on the Production environment prior to the formal system testing performed by the Customer.
• Configure networking for access from the City network to the AWS Cloud Production environment. • Ensure all ports/services are opened or configured as per Versaterm requirements. • Conduct system testing on the production environment. • The Production environment is configured and tested with Torrance-specific requirements (as configured during system Implementation), and the parties agree that it is operational.

The purpose of the Interface Integration Testing is to demonstrate and verify that all interfaces specified in the RMS Interface Control Document (Exhibit C.3) meet or exceed the functionality and performance, that each interface is operational and ready for Functional Acceptance Testing, and that the data conversion was/will be successful.

The Interface Integration Testing occurs during the Configuration Phase of the implementation as interfaces are completed.

The RMS Interface Control Document (Exhibit C.3) provides details regarding the strategy, schedule, dependencies, environment, problem tracking and remedies, and completion criteria.

An Interface will be excluded from the Interface Integration Testing should the City be unable to meet the related Interface City responsibilities specified in the ICD. A Change Order or Amendment, whichever is appropriate, will be generated to document any changes.
• Provide the City with an electronic version of interface design specifications for the interfaces defined Interface Control Document.
• Coordinate and schedule the Interface Testing efforts with the City's Project Managers. • Demonstrate each interface to the City’s Project Team. • With the assistance of the City's Project Team, test each interface to ensure that it meets or exceeds the functionality and performance measurements specified in the RMS Interface Control Document (Exhibit C.3). • Document and track all defects reported by the City.
• Review and correct any discrepancies per the Acceptance Test Plan.

CITY RESPONSIBILITIES

TASK COMPLETION CRITERIA

5.7 TESTING PHASE - TASK 11
TASK #11.1 INTERFACE INTEGRATION TESTING (TIMELINE MILESTONE #6)

VERSATERM RESPONSIBILITIES
285
Versaterm Public Safety Inc. & City of Torrance
SaaS Agreement #
Exhibit C.1 – RMS Statement of Work

Page 24 of 32 ends

• Provide training to the City on interface setup, configuration, administration and usage of each interface. • Coordinate and schedule the Interface Testing efforts with all third-party Vendors and the Versaterm Project Manager. • Identify and schedule Interface Testing with the relevant City participants. • Reproduce and provide the interface design specifications from Versaterm to the relevant City participants that will be involved in the Interface Testing.
• Ensure that the designated City participants attend and participate in the scheduled Interface Testing. • Work with Versaterm to test each interface, identifying the type of correction needed to ensure that each interface conforms to the RMS Interface Control Document (Exhibit C.3). • Retest any interfaces that did not meet the specifications. • Install of the Development/Test and Production environments • Develop and install interfaces
• A tracking document to track all issues reported.
• Corrections to errors or issues identified during Interface Testing. • The City has verified that all interfaces operate as specified in the RMS Interface Control Document (Exhibit C.3). • The City’s Project Team and other select City staff are sufficiently trained to be able to administer, manage, and fully use each interface.

The purpose of Functional Acceptance Testing is to verify that the fully configured System, including the interfaces specified in the RMS Interface Control Document (Exhibit C.3), and the workflows and business processes such as data entry, reports, notifications, tasks, etc. meet the functional requirements described in the Agreement and system documentation.

The Functional Acceptance Testing occurs after the Configuration Phase and before the Training Phase of implementation. • Provide support to the Customer as it conducts the Functional Acceptance Testing. • Review, verify, and correct all defects reported by the Customer. • Review any discrepancies found during the Functional Acceptance Testing. • Correct any functional item that fails a test.

CITY RESPONSIBILITIES

PREREQUISITES

VERSATERM DELIVERABLES

TASK COMPLETION CRITERIA
TASK #11.2 FUNCTIONAL ACCEPTANCE TESTING

VERSATERM RESPONSIBILITIES

CITY RESPONSIBILITIES
286
Versaterm Public Safety Inc. & City of Torrance
SaaS Agreement #
Exhibit C.1 – RMS Statement of Work

Page 25 of 32 ends

• Generate any production data files needed for Functional Acceptance Testing. • Report all defects to Versaterm.
• Work with Versaterm to identify the correction needed to ensure that the System conforms to the System's expectations. • Notify Versaterm in writing when Functional Acceptance Testing is completed. • Configuration Phase
• Interface Testing
• GIS data processed
• Set up the Development/Test and Production environments • Document and track all defects reported by the City.
• The System and interfaces have been verified by the City to operate as specified in the Agreement The Functional Acceptance Testing is considered complete when Versaterm has remedied all deviations and the City has notified Versaterm that it has completed the Functional Acceptance Tests. • Provide milestone invoice as per • See Exhibit C – RMS SaaS Service Schedule All Functional Acceptance Testing has been completed, and City is ready to proceed with the Training Phase.

PREREQUISITES

VERSATERM DELIVERABLES

TASK COMPLETION CRITERIA
TASK #11.2.3 ATTACH FUNCTIONAL ACCEPTANCE TESTING ACCEPTANCE EMAIL (TIMELINE MILESTONE #7)

VERSATERM DELIVERABLES

TASK COMPLETION CRITERIA
287
Versaterm Public Safety Inc. & City of Torrance
SaaS Agreement #
Exhibit C.1 – RMS Statement of Work

Page 26 of 32 ends

The City is responsible for providing and preparing the necessary training facilities for training end users. • Provide the City with the technical requirements for the training facilities. • Provide network access requirements for remote training facilities being prepared by the City. • Disseminate the technical facility requirements obtained from Versaterm to members preparing training facilities for the Project.
• Establish and disseminate minimum facility and equipment requirements for members preparing training facilities for the Project.
• Ensure that the required training facilities are available and properly configured in accordance with the Project Implementation Schedule.
• Agreement Execution.
• Training facility and equipment requirements.
• Training facility and equipment requirements are available and disseminated to the members responsible for preparing the Project’s training facilities.
• The required number of training facilities is available and properly configured in accordance with the Project Implementation Schedule.

The Torrance Police Department has requested End-User-Training be provided by Versaterm Staff to all end users. For this reason, although the Train-The-Trainer activity is still included on the project schedule, associated payment milestones have been removed and Versaterm will work with TPD to develop the needed skills throughout the project. As this knowledge and ability will be required by TPD for all post project End-User-Training.

5.8 TRAINING PHASE - TASK 12
TASK #6.7 PREPARE A CONFIGURATION LAB

VERSATERM RESPONSIBILITIES

CITY RESPONSIBILITIES

PREREQUISITES

VERSATERM DELIVERABLES

TASK COMPLETION CRITERIA
TASK #12.3 TRAIN-THE-TRAINER TRAINING

VERSATERM RESPONSIBILITIES
288
Versaterm Public Safety Inc. & City of Torrance
SaaS Agreement #
Exhibit C.1 – RMS Statement of Work

Page 27 of 32 ends

• Provide the City with a re-settable training database that includes all the City’s configurations to date. • Provide Train-the-Trainer training facility requirements for the City's Project Managers. • Provide required skills and any pre-requisite training required by Train-the-Trainer participants. • Produce a reproducible set of Train-the-Trainer Training Documentation that includes the City’s requirements, in soft copy. • Assist in adapting the training scenarios to make use of familiar data and to include site-specific policy and/or process flow information.
• Provide a Training facility that meets Versaterm's requirements. • Ensure that the designated participants attend the scheduled Train-the-Trainer Training. • Training facility prepared.
• Testing successfully completed.
• Training facility requirements.
• Train-the-trainer participants pre-requisite training and required skill set. • Train-the-trainer preparation for post project
• Delivery of Train-the-Trainer training, per the Training Plan. • Participants have been adequately trained on the agreed-upon Train-the-Trainer training topics, are able to complete the training assignments/scenarios.

This task signifies that Versaterm has delivered all required software, interfaces, data conversion programs and Train-the-Trainer preparation and remedied all Critical Priority Error and High Priority Error that are critical to start End User training. • Issue written notice to the City that the System is Ready for Training. • Correct any defects mutually identified by the City and Versaterm as having to be corrected prior to the System being ready for the end-user training.
• Within ten (10) Business Days after receiving Versaterm’s “Ready for Training” notification, review the System's status and outstanding issues list and mutually identify with Versaterm any defects that must be corrected prior to its being used for end-user training.

CITY RESPONSIBILITIES

PREREQUISITES

VERSATERM DELIVERABLES

TASK COMPLETION CRITERIA
TASK #12.4 READY FOR USE DECLARED (TIMELINE MILESTONE #8)

VERSATERM RESPONSIBILITIES

CITY RESPONSIBILITIES
289
Versaterm Public Safety Inc. & City of Torrance
SaaS Agreement #
Exhibit C.1 – RMS Statement of Work

Page 28 of 32 ends

• Issue a written notice to Versaterm that the System has been verified to be ready for end-user training. • Set Up and Test Disaster Recovery Environment
• Interface Testing
• Functional Acceptance Testing
• System Performance Testing
• Train-the-Trainer Training
• Written notice to the City that the System is Ready for Training, once all defects mutually identified by the City and Versaterm have been corrected.
• Provide milestone invoice as per • See Exhibit C – City of Torrance – RMS SaaS Service Schedule • Receipt by the City of Versaterm's written notice that the System is Ready for Training. • Issuance of a written notice to Versaterm from the City that the System has been verified to be Ready for Training.

Versaterm and Versaterm-trained City trainers will provide just-in-time training to end-users. Versaterm will provide at least one (1) training support resource onsite at City facilities for the duration of the five (5) calendar weeks of the end-user training classes. The training classes should be held at centralized location and classroom time will be between 8 and 10 hours based on the local agency’s typical schedule and offered during business hours Monday through Friday. Alternative classroom time may be optional, but Versaterm will not support End-User-Training between 10pm and 6am or on weekends. • Provide at least one (1) training support resource (on-site) for the five (5) calendar weeks to lead the end-user training classes (total of 25 days for Police End User training). • Work with TPD to Prepare the required training documentation and material for each end-user attending a training session. • Provide adequate training facilities including screen projection resources and enough workstation positions for up to twenty (20) students.
• Coordinate with Versaterm on the use and location of Versaterm's onsite training resources during the five (5) calendar weeks of end-user training for the Police Department.
• Train additional trainers as necessary to staff future end-user training. • Schedule and organize the end-user training schedule. • Assign end-users to training classes at each facility.

PREREQUISITES

VERSATERM DELIVERABLES

TASK COMPLETION CRITERIA
TASK #12.5.2 AGENCY END-USER TRAINING (TIMELINE MILESTONE #9)

VERSATERM RESPONSIBILITIES

CITY RESPONSIBILITIES
290
Versaterm Public Safety Inc. & City of Torrance
SaaS Agreement #
Exhibit C.1 – RMS Statement of Work

Page 29 of 32 ends

• Assign SME support trainers to training facilities so that at least two qualified TPD trainers are present at Business Unit/Process specific end-user training classes.
• Work with Versaterm to prepare the required training documentation and material for each end-user attending a training session.
• Ensure that the designated SME support trainers and end-users attend their scheduled Business Unit/Process specific end- user training classes.
• Training facility
• Train-the-trainer training
• Ready for Use
• 1 training resource onsite for 5 calendar weeks.
• Feedback to City training resources
• Completion of end-user training classes (prior to Production Use).

Versaterm will provide, on-site at Town facilities, up to an eight (8) hour System Administration Training course to the Town’s Technical System Administrators. The course can accommodate up to 12 participants, and will provide the Town with a technical overview of the system, including, but not limited to:
• Architecture overview
• File structures and key file locations (various system logs and configuration files). • Versaterm related CRON jobs
• Introduction to the VMC (Versaterm Message Controller) • Coordinate and schedule the system administration training course with the Customer project manager. • Provide participant skills and previous training requirements. • Provide training documentation electronic format prior to the scheduled training session. • Conduct the system administration training session (including the topics shown above). • Provide training on how to troubleshoot Versaterm application problems. • Coordinate the location and scheduling of the system administration training course with the Versaterm project manager.

PREREQUISITES

VERSATERM DELIVERABLES

TASK COMPLETION CRITERIA
TASK 12.5.4 FINAL SYSTEM ADMIN TRAINING

VERSATERM RESPONSIBILITIES

CUSTOMER RESPONSIBILITIES
291
Versaterm Public Safety Inc. & City of Torrance
SaaS Agreement #
Exhibit C.1 – RMS Statement of Work

Page 30 of 32 ends

• Identify and schedule the system administration training session participants. • Provide the required documentation and training materials to system administration training session participants. • Ensure that the designated participants attend the scheduled system administration training sessions. • Production Environment Setup
• Administration training participant pre-requisite training and required skill set. • Administration training documentation and material for each participant. • Completed system administration training session.
• Participants have been adequately trained on the agreed upon administration training. • The Customer’s system administrators can perform the administrative functions defined in this task.

The City and Versaterm will coordinate the update to all City Desk Computers that will access RMS and MRE. RMS requires an HTML 5 compatible browser (Chrome Preferred). All Patrol vehicles and report-writing computers with need MRE installed. • Provide the City with the latest specifications and MRE Build. • Ensure that all Department computers have been prepared. • Final MRE Build available.
• City has completed all Computer preparation.
• Versaterm will assist and support the City in placing the System into Production Use.

PREREQUISITES

VERSATERM DELIVERABLES

TASK COMPLETION CRITERIA

5.9 PRODUCTION CUTOVER AND CLOSE SUPPORT - TASK 13
TASK #13.1 PREPARE DESKTOPS AND MOBILE COMPUTERS

VERSATERM RESPONSIBILITIES

CITY RESPONSIBILITIES

PREREQUISITES

TASK COMPLETION CRITERIA
TASK #13.3 PRODUCTION CUTOVER – GO LIVE
292
Versaterm Public Safety Inc. & City of Torrance
SaaS Agreement #
Exhibit C.1 – RMS Statement of Work

Page 31 of 32 ends

• Collaborate with the City to determine the date and time of the System cutover for Production Use. • Provide sufficient onsite resources at least one (1) full Calendar Day prior to System cutover to assist the City's Project Team in preparing.
• Assist the City in placing the system into a Production Use status. • Monitor the initial operation of the System and answer any operational questions raised by the City. • Provide sufficient onsite resources to support the first three (3) full calendar days of Production Use. • Collaborate with Versaterm to determine the System Cutover date and time. • Provide trained personnel to be the first line of Support. • Set up and staff a “Go-Live Support Room” to act as a central coordination point for Go-Live issues and support. • Coordinate with Versaterm to schedule the onsite Versaterm resources as needed to support the first three (3) calendar days of Production Use.
• End-User training
• Onsite Versaterm resources in support of the System cutover to Production Use. • Provide milestone invoice as per • See Exhibit C – City of Torrance – RMS SaaS Service Schedule • The System is successfully operating in Production Use.

After cutover to live operations, the System will undergo a thirty (30)-day test period. The City will use the System for its intended purposes and monitor system reliability, functionality, and performance. Errors will be tracked and remedied per the RMS Acceptance Test Plan (Exhibit C.5).
• Remedy reported issues per the RMS Acceptance Test Plan (Exhibit C.5). • Support the City as required during the Reliability Acceptance Test. • Operate the System in Production Use.
• Monitor system functionality, performance, and reliability.

VERSATERM RESPONSIBILITIES

CITY RESPONSIBILITIES

PREREQUISITES

VERSATERM DELIVERABLES

TASK COMPLETION CRITERIA

5.10 RESPONSE TIME AND RELIABILITY ACCEPTANCE TESTING – TASK 14

VERSATERM RESPONSIBILITIES

CITY RESPONSIBILITIES
293
Versaterm Public Safety Inc. & City of Torrance
SaaS Agreement #
Exhibit C.1 – RMS Statement of Work

Page 32 of 32 ends

• Notify Versaterm immediately of any encountered issues that impact the Reliability Acceptance Testing. • Notify Versaterm in writing of the successful conclusion of the Reliability Acceptance Testing. • System cutover to Production Use
• Correction to any encountered System issues or defects as specified in the Acceptance Test Plan. • System support as specified in Exhibit C – City of Torrance – RMS SaaS Service Schedule. • The System has operated for thirty (30) Consecutive Days without a Critical Priority Error or High Priority Error and a mutually agreeable plan to remedy all other minor errors has been developed and agreed to.

Final System Acceptance will occur after the completion of the 30-day Reliability Acceptance Testing period without an occurrence of a Critical Priority Error or High Priority Error, and when all other minor errors have been resolved or a mutually agreeable plan to remedy these errors has been developed.

If a Critical Priority Error or High Priority Error occurs during the 30-day Reliability Acceptance Testing period, the 30-day Reliability Acceptance Testing period will begin again at such time there are no Critical Priority Errors or High Priority Errors. • N/A
• Notify Versaterm in writing of Final System Acceptance when all outstanding System issues or defects that preclude Final System Acceptance have been corrected.
• Successful completion of the Reliability Acceptance Testing. • Provide milestone invoice as per • See Exhibit C – City of Torrance – RMS SaaS Service Schedule

PREREQUISITES

VERSATERM DELIVERABLES

TASK COMPLETION CRITERIA

5.11 FINAL SYSTEM ACCEPTANCE – TASK 15 (TIMELINE MILESTONE #10)

VERSATERM RESPONSIBILITIES

CITY RESPONSIBILITIES

PREREQUISITES

VERSATERM DELIVERABLES

TASK COMPLETION CRITERIA
294
Versaterm Public Safety Inc. & City of Torrance
SaaS Agreement #
Exhibit C.1 – RMS Statement of Work

Page 33 of 32 ends

• Reliability acceptance tests have been completed successfully. • City has provided a written notice of Final System Acceptance to Versaterm.

The purpose of this communication plan is to provide meaningful, timely, and responsive communications that meets the needs of our staff and stakeholders, and ultimately supports a successful project completion, adoption, and utilization of the Versaterm RMS, MRE and VMOBILE. Consequently, the project team and supporting readiness team members will regularly review and update the Plan throughout the project to ensure communication strategies and actions directly support and address key needs of the project, City staff, and citizens.

Communications
Product
Audience Key Interests/ Messages Frequency Delivery Method Moderation Level* Steering
Committee Report
Steering
Committee
• Strategic alignment
• Project milestones and risks
• Budget and resource updates
• Escalated issues requiring decision
• Approved or pending Change Orders
• Upcoming critical activities or
decisions
Monthly or
when needed
In person with
PowerPoint
City Project Manager
Weekly Status
Reports
• City PM
• Versaterm PM
• TPD Command
Staff
(Optional)
• Status Review
• Current/Recent Activities
• Upcoming Activities
• Communications
• Current Resource Use
• Timeline for Next Few Months
Weekly Email Versaterm Project
Manager
Meeting Agendas &
Minutes
Meeting
participants
• Agenda
• Participants
• Minutes
• Action Items
• Decisions
• Identified Risks
As appropriate Email Versaterm Project
Manager
Command Staff
Briefing
TPD Command
Staff
• Status Review
• Current/Recent Activities
• Upcoming Activities
• Current Resource Use
• Timeline for Next Few Months
Monthly In person with
PowerPoint,
SharePoint and/or
handouts as
appropriate
City Project Manager
• Both the Versaterm and City Project Managers shall add to the Risk Register (SharePoint list) any reasonable risks that come to their attention – whether the risk is self-identified or suggested by someone else. • Both the Versaterm and City Project Managers shall routinely (weekly) monitor and update the Risk Register including mitigation plans.
• When a risk is deemed likely or imminent, either the Versaterm or City Project Manager shall initiate the appropriate risk mitigation plan(s) as necessary and notify the appropriate team members. 6 COMMUNICATION PLAN
7 RISK MANAGEMENT PLAN
295
Versaterm Public Safety Inc. & City of Torrance
SaaS Agreement #
Exhibit C.2 – RMS Project Implementation Schedule

Page 1 of 4 ends

EXHIBIT C.2

RMS PROJECT IMPLEMENTATION SCHEDULE
296
Versaterm Public Safety Inc. & City of Torrance
SaaS Agreement #
Exhibit C.2 – RMS Project Implementation Schedule

Page 2 of 4 ends

297
Versaterm Public Safety Inc. & City of Torrance
SaaS Agreement #
Exhibit C.2 – RMS Project Implementation Schedule

Page 3 of 4 ends

298
299
Versaterm Public Safety Inc. & City of Torrance
SaaS Agreement #
Exhibit C.3 RMS Interface Control Document

Page 1 of 22 ends

EXHIBIT C.3

RMS INTERFACE CONTROL DOCUMENT
300
Versaterm Public Safety Inc. & City of Torrance
SaaS Agreement #
Exhibit C.3 RMS Interface Control Document

Page 2 of 22 ends

JDIC / CLETS.....................................................................................................................................................3 KARPEL INTERFACE........................................................................................................................................10 AFIS LIVESCAN (LACRIS) INTERFACE ..............................................................................................................12 CRIMETRACER INTERFACE.............................................................................................................................16 CITATION PROCESSING CENTER (CPC) INTERFACE ........................................................................................19

CONTENTS
301
Versaterm Public Safety Inc. & City of Torrance
SaaS Agreement #
Exhibit C.3 RMS Interface Control Document

Page 3 of 22 ends

The JDIC interface installed and launched during the Torrance Versaterm CAD Implementation will be enhanced to add query/maintenance capability from the Versaterm RMS. These transactions are delivered to JDIC (the LA County Justice Data Interface Controller) and then onto the state (CLETS, DMV) and national databases (NCIC, NLETS) where they are processed appropriately. The Versaterm NCIC Gateway is used to manage and administer the interface.

A number of transactions (query and maintenance) may be automatically triggered within the RMS.

RMS Process Overview
CLETS/NCIC access is available through the button on the RMS desktop. As with CAD, once invoked, the user is presented with a transaction list so they may select the appropriate transaction by either entering the transaction code (e.g. EA, etc.) or by selecting from a list of valid transactions (known as the NCIC transaction code list). Upon entering the transaction code, the appropriate form is displayed. Mandatory fields are indicated by the convention used throughout the Versaterm applications.

Once the transaction has been sent, the user is returned to the transaction selection screen. At this point, the user may continue with other transactions or close the NCIC subsystem and return to the Versaterm RMS.

Responses/Replies from the external system are returned to the users Versaterm RMS vMail mailbox.

Auto-maintenance transactions, triggered by the Versaterm RMS system, will present the corresponding CLETS/NCIC form, for corresponding maintenance transaction(s). That is, for any transaction that will add or update data on CLETS/NCIC as a by- product of a transaction in Versaterm, the Versaterm system will present the data in the corresponding CLETS/NCIC form for user confirmation. For auto-query transactions, these are simply generated and sent (i.e. the user is not required to confirm the data).

RMS Auto Initiated CLETS/NCIC Transactions
The following auto-initiated transactions are included with the delivery of the Versaterm RMS:

RMS Function Generated CLETS/NCIC transaction
Query Person QPER (Person Multi-Query)
Query Vehicle QVEH (Vehicle Multi-Query)
Add Seized/Towed Vehicle EVS
Add Recovered/Seized Articles ACEA
Add Recovered/Seized Guns ACEG
Add Stolen Articles* ACEA
Add Stolen Guns* ACEG
Add Missing Person* ACEM
Add Stolen Vehicle* ACEV

JDIC / CLETS

INTERFACE SCOPE

PROCESS FLOW
302
Versaterm Public Safety Inc. & City of Torrance
SaaS Agreement #
Exhibit C.3 RMS Interface Control Document

Page 4 of 22 ends

* For information added automatically, the Versaterm application will attempt to implement “auto-clear” and “update” transactions. For example, when the property is recovered, the system will allow the user to clear or update, as appropriate, the details from CLETS/NCIC based on the NIC# and other associated “stamps” returned from the original add.

Network communication to the JDIC interface is via a direct connect over TCP/IP using socket level communications. This direct connection, referred to as the “JDIC line” will be supplied and configured by the Customer and will encompass a dedicated network IP address and network port number. The data exchange methodology will conform to the California DOJ standards.

The NCIC Gateway provides the state-specific transaction formatting and communication requirements to the individual state interface. The NCIC Gateway also provides central management for NCIC configurations and user access. The following diagram illustrates the system connectivity points for the Versaterm applications (RMS) to the NCIC Gateway:

Security is controlled with a unique security matrix for NCIC – system users must be registered in the Versaterm NCIC security matrix prior to being able to run State/NCIC transactions. Optionally, an expiry date can be maintained where the user is denied access if the current date is greater than the expiry date. For each transaction, the administrator may provide or deny the transaction privileges. Setting security is a supervisor/administrator privilege, accessed through the NCIC Supervisor module.

Versaterm will complete the initial load of these values if the Customer provides them in a usable format (e.g. csv or similarly delimited file).

The following screen shot is an example of the NCIC security profile and matrix for a specific user or group:

COMMUNICATION

SECURITY AND RESTRICTING ACCESS
303
Versaterm Public Safety Inc. & City of Torrance
SaaS Agreement #
Exhibit C.3 RMS Interface Control Document

Page 5 of 22 ends

Each response is returned as a transaction message and placed in the user’s Versaterm mailbox (vMail). Lines are no more than 80 characters in width. If a query generates multiple responses, each response is delivered as an individual message.

The NCIC gateway switch provides a facility to log/audit all transactions and corresponding responses to an online database table (searchable via the NCIC Administrator interface). The audit file can grow very quickly so it is recommended that the log is archived & purged frequently or simply just purged (if retention of the audit is not an issue). Versaterm will provide a program which, through a scheduled system facility, will purge and/or archive the logs to readable ASCII files where the site may back them up periodically. The files are generated on a daily basis, i.e. one file for each day’s transactions.

The Versaterm interface to national, state and county/regional databases is the Versaterm NCIC subsystem. The Versaterm NCIC subsystem must be configured to recognize every transaction that site requires, where the NCIC subsystem has been identified as the medium by which the transaction is to be passed to an external system. To facilitate as flexible a means as possible for such configuration, an integral part of the Versaterm NCIC subsystem is its Site Configurable Transaction (SCT) Facility that is more informally referred to as the form-painter. While the SCT provides for the definition of forms that are associated with each transaction, it also provides for the definition of field and/or transaction level rules and, of equal importance, for definition of destination-format strings which govern how transactions will be assembled from the individual field details provided by a user.

It is due to the Versaterm NCIC subsystem’s leveraging of these SCT rules and destination-format strings that every transaction to be handled by the subsystem needs to be defined using the SCT. The benefit of this approach is that any NCIC-like transaction can be supported within the NCIC subsystem (e.g. NLETS message) – it does not have to be configured in an integrated fashion within the Versaterm application. Further, the Customer is capable of adjusting the transactions as the external system requirements change.

The remainder of this section provides high-level insight into how the SCT is used to define transactions that can be made available for use with the Versaterm NCIC subsystem.

Transactions are maintained using Versaterm’s Site Configurable Transaction (SCT) facility. When first invoked, a list of already defined transactions is presented. From this list, existing transactions can be modified/deleted (i.e. the highlighted entry in the list representing the transaction currently in focus) or new transactions can be created (i.e. the “Add” button).

RESPONSE DESCRIPTION

AUDITING AND LOGGING

VERSATERM NCIC SITE CONFIGURABLE TRANSACTION (SCT) FACILITY OVERVIEW

SCT FACILITY TRANSACTION DEFINITION
304
Versaterm Public Safety Inc. & City of Torrance
SaaS Agreement #
Exhibit C.3 RMS Interface Control Document

Page 6 of 22 ends

When defining new transactions, or modifying existing ones, in addition to defining a transaction code, version, type, etc., the ability to define individual fields that comprise the transaction is also required. To facilitate this, a “Modify Form” button under “Open” will open a window, similar to that illustrated below, which will permit transaction fields and labels to be defined:

When a field is defined (as shown above), characteristics such as length, default value, field-level rules, permitted values, picture clauses, lookup-table, etc. can be specified. A field tag-value unique to the transaction must also be specified. This tag-value becomes the name by which the field will be referenced when form level rules and/or destination-formats for the transaction are defined. In addition to fields, the screen painting form also allows for the (optional) definition of labels to make the form readable to the user.

With the transaction defined, form-level rules and/or destination-formats can be defined. Form-level rules are rules that are applied after the entire form has been specified as opposed to after when an individual field has been entered. Form-level rules can be defined by clicking the “Rules” tab when a transaction is opened and are useful for performing multi-field edits, specifying

FORM-LEVEL RULES
305
Versaterm Public Safety Inc. & City of Torrance
SaaS Agreement #
Exhibit C.3 RMS Interface Control Document

Page 7 of 22 ends

which destination-formats are to be used and constructing fields that can be used and when populating a destination-format. A sample form-level rules definition might be:

In this case, it is assumed a form has been defined that among others has fields with tag-values of MNU_TYPE and MNU_NUM (i.e. individual fields that when combined would form the NCIC miscellaneous-number - MNU field). If both the MNU_TYPE and MNU_NUM fields above were assigned values when the transaction was being entered then the above rule stipulates that a new variable, MNU, will be assigned the value of the MNU_TYPE field entered on the transaction form, followed by a hyphen (“-”), followed by the value of the MNU_NUM field entered on the transaction form. The resulting MNU variable can then be used later on within the rules section or even used in a destination-format definition.

To specify destination-formats, the “Destinations” tab is clicked on the NCIC transaction window. This causes a window similar to the following to be displayed:
306
Versaterm Public Safety Inc. & City of Torrance
SaaS Agreement #
Exhibit C.3 RMS Interface Control Document

Page 8 of 22 ends

The destination list capability provides flexibility in dealing where a single transaction may be sent to multiple systems.

The destination-format generally conforms to rules that tend to be specific to the state and county level message-switches that the transaction must navigate. State provided documentation is usually required to define these formats.

When specifying a destination-format, it is usually comprised from a combination of hard-coded literals (e.g. see ACQV, NAM, DOB, etc., outside of brackets/braces above) and/or variables. These variables come from SCT defined constants, from form fields as identified by their tag-value (e.g. see NAM, RAC, DOB, etc., embedded within braces above) and/or from variable names assigned values within the form-level rules section (no example provide above). There is nothing that prevents a hard-coded literal from being the same as a variable name. The destination-format parser distinguishes the appropriate context based on whether or not the value is embedded inside brackets/braces; values inside brackets/braces are variables and values outside brackets/braces are hard-coded literals.

This interface is available from the production environment across data centers provided there is connectivity from the RMS server to JDIC.

These tests are intended to ensure the CLETS/NCIC interface is accurate and complete in submitting transactions and delivering responses. The following are descriptions of the tests to be performed for the specific interface during the Functional Acceptance Test period.

FUNCTIONAL AND COMPLETENESS TEST

BUSINESS CONTINUITY/INTERFACE AVAILABILITY

INTERFACE TESTING
307
Versaterm Public Safety Inc. & City of Torrance
SaaS Agreement #
Exhibit C.3 RMS Interface Control Document

Page 9 of 22 ends

For each query/maintenance transaction, the site will verify the corresponding transaction is generated. Invalid combinations are entered to verify edits.

OPERATIONAL TESTS
For each query/maintenance transaction, the site will verify the transaction response. Each response should be compared to the transaction responses returned from the State interface contained in the legacy system.

PERFORMANCE TESTS
The performance tests include a load test where site will run a number of queries from various workstations to ensure the interface can handle the expected workload while routing responses back to the proper originators. External system response time may vary and is outside of the control of Versaterm.

EXCEPTION TESTING
The exception testing consists of “unplugging” the interface to ensure the line failure is detected and that any queries are retained in the outbound queue and subsequently submitted once the failure has been corrected.

DATA INTEGRITY TESTING
It is the responsibility of the Customer to conduct in-depth testing of the interface to ensure overall data integrity, that data is processed appropriately and that the interfaces function as required.

CUSTOMER RESPONSIBILITIES
a. Assist Versaterm in configuring the JDIC connectivity and configuration parameters. b. Configure (and test) required networking components, including firewalls, to enable communication between the Versaterm server environment(s) and JDIC
c. Provide remote access to the NCIC Admin module within the hosted RMS permitting Versaterm to configure and test remotely, as required.
d. With remote assistance from Versaterm, complete any state-required Certification testing e. Perform interface testing

VERSATERM RESPONSIBILITIES
a. Install and configure the NCIC Gateway software in the implementation server environment (initially) and then within the production server environment.
b. With assistance from the Customer, configure socket communication to JDIC. c. Install and configure the initial Versaterm NCIC/State/County transaction set (transactions). d. Perform initial functional/integration testing of the NCIC interface. e. Complete any state-required staff certifications for software providers.

RESPONSIBILITIES
308
Versaterm Public Safety Inc. & City of Torrance
SaaS Agreement #
Exhibit C.3 RMS Interface Control Document

Page 10 of 22 ends

This interface provides a one-way transfer of defendant and case information from the Versaterm RMS to the Karpel system.

Defendant and relevant case information is manually pushed to the KARPEL system through vRMS Release Tracking. The package of information pushed to KARPEL is produced for a specific defendant from the relevant GO.

The vRMS generates an XML that conforms to KARPEL’s file specifications. The XML is transferred to a web service hosted on the KARPEL server and conforms to KARPEL’s WSDL specifications.

The Versaterm extract is a delete/add architecture. The initial defendant package sent will represent the original submittal to KARPEL. Any additional data sent to KARPEL for the same case and defendant will be a complete resend of the package. There will be no Release Tracking supplemental releases. Versaterm expects KARPEL to delete any previous information sent for the defendant and case and replace it with the updated data.

A Release Tracking template needs to be created for this interface. The Template must be created with a type of “Karpel” Data files created by Versaterm RMS conform to KARPEL’s file specifications as defined in the document titled ‘Prosecutor by Karpel Law Enforcement Information Exchange Package’.

Communication for this interface is provided via web services.

Authentication for this interface conforms to KARPEL’s specifications.

KARPEL INTERFACE

INTERFACE SCOPE

PROCESS FLOW

CONFIGURATION

DATA FORMAT REQUIREMENTS

COMMUNICATION

AUTHENTICATION

BUSINESS CONTINUITY/INTERFACE AVAILABILITY
309
Versaterm Public Safety Inc. & City of Torrance
SaaS Agreement #
Exhibit C.3 RMS Interface Control Document

Page 11 of 22 ends

This interface is available in the Production environment. This interface can also be made available from the Test or Training environments provided access to a Test or Training KARPEL environment is available.

These tests are intended to ensure the interface is functional as designed. The following are descriptions of the tests to be performed for the specified interface functionality during the interface test period. .

FUNCTIONAL AND COMPLETENESS TEST
This test consists of creating sample cases in the RMS and ensuring the KARPEL XML contains correct information.

OPERATIONAL TESTS
This test ensures after system reboots, the interface is available and able to communicate with the KARPEL.

PERFORMANCE TESTS
There is no performance test for this interface.

EXCEPTION TESTING
This test consists of disabling the KARPEL webservice temporarily, to ensure the XML is generated and transferred to the webservice once it becomes available.

DATA INTEGRITY TESTING
It is the responsibility of the City to conduct in-depth testing of the interface to ensure overall data integrity, that data is processed appropriately and that the interfaces function as required.

CUSTOMER RESPONSIBILITIES
a. Provide the required network connectivity between the KARPEL system and vRMS. b. Provide updated specifications.
c. Provide authentication method and any required credentials. d. Configure the Release Tracking template.
e. Assist Versaterm as required as they perform the initial integration testing. f. Review the results from Versaterm’s initial integration testing. g. Perform integration testing as described in the Interface Testing section above.

VERSATERM RESPONSIBILITIES
a. Install and configure the interface.
b. Perform initial integration testing as described in the Interface Testing section above and review results with the Customer.

INTERFACE TESTING

RESPONSIBILITIES
310
Versaterm Public Safety Inc. & City of Torrance
SaaS Agreement #
Exhibit C.3 RMS Interface Control Document

Page 12 of 22 ends

This interface consists of an Arrest/Booking data transfer between the Versaterm vRMS JMS module and the City’s Livescan Enterprise system supplied by L-1 Identity Solutions. The interface adheres to Web Services technical specifications provided by L-1 Identity Solutions.

The Livescan system is located on Torrance Police Department premises (e.g. Jail) and is an integral component of the offender booking process. Offender fingerprints and mugshots are taken using the Livescan server located in the Jail. This server is part of the LA County Regional Identification System (LACRIS), maintained by the LA County Sheriff’s Department.

As part of the booking process at Torrance PD, when an offender is arrested and subsequently booked into the Jail, Arrest/Booking data is entered into the Versaterm vRMS Arrest (JMS) module. This could be an Arrest report transferred from the Versaterm Mobile Report Entry (vMRE) application or directly entered into the JMS. When the Jail Corrections Officer (JCO) is ready to book the Offender, the JMS booking data is transferred from the RMS to the Livescan system by initiating a query of the JMS Arrest number from Livescan (thereby invoking a Web Services query into the RMS).

Once the offender fingerprints and mugshot(s) have been taken on Livescan, the data and images are transferred by Livescan to the LACRIS system in LA County. Upon a successful transfer, the LA County booking number and mugshots (in base-64 format) are returned by Livescan to the JMS (another Web Services transaction), where the LA County Booking number and mugshots are stored.

The booking data transferred to Livescan shall include, where available, the following:
• File Number
• Home Address

AFIS LIVESCAN (LACRIS) INTERFACE

INTERFACE SCOPE

PROCESS FLOW

DATA FORMAT REQUIREMENTS
311
Versaterm Public Safety Inc. & City of Torrance
SaaS Agreement #
Exhibit C.3 RMS Interface Control Document

Page 13 of 22 ends

• House #
• Street
• City
• State
• Gender (M, F, or X)
• Race
• Hair Color
• Eye Color
• Height
• Weight
• Date of Birth (format MMDDYYYY)
• State of Birth (two character code)
• Occupation (1-22 characters, spaces, commas, hyphens, and parenthesis) • Date of arrest (MMDDYYYY)
• Time of arrest (military time, but 0000 is not allowed) • Arrest Location
• Arresting Agency
• Reporting District
• Jail Location
• Arresting Officer’s Last Name
• Arresting Officer’s ID#
• Date Booked (MMDDYYYY)
• Time booked (military time, but 0000 is not allowed)
• Booking Officer’s Last Name
• Booking Officer’s ID#
• If this is a booking for another agency, the ORI of that booking agency • The charge data set
• Book Type (usually A)
• Counts (usually always 001)
• The AJIS statute (the arrest charge from the AJIS charge table)

1. And the AJIS level such as M or F or I
• The Bail amount
• If this is a warrant arrest, then the warrant information

1. Date of Offense

2. Warrant number

3. Warrant type

4. If you want CWS to pull the abstract, there are two other fields that should be populated

1. CWS – this is a Y or a N

2. Name Check, this is used if the warrant isn’t the same name as the person being booked • Court Info, if available or known at the time of Livescan

1. Court Code

2. Court Date

3. Court Time
• Total Bail amount
312
Versaterm Public Safety Inc. & City of Torrance
SaaS Agreement #
Exhibit C.3 RMS Interface Control Document

Page 14 of 22 ends

NOTES ON BOOKING NUMBER
• If there is no booking number provided in the XML file passed from Versaterm to Livescan during the GetRecord, Livescan will assign a new booking number automatically. This booking number will be part of the UpdateRecord, should Torrance choose to implement the UpdateRecord call that Livescan does when submitting the record at the end when the jailer selects Save and Submit.
• If Torrance does pull a booking number, it must be in the XML package by the time Livescan is done.

This interface is only from the RMS production server unless the City has a test Livescan server to work with, otherwise the City will run the risk of sending test data to the production LACRIS system inadvertently. However, for the Interface Testing period it is assumed some test records will be sent to LACRIS.

FUNCTIONAL AND COMPLETENESS TEST
This test confirms that arrest/booking data is transferred from the RMS to the Livescan server in response to Web service requests initiated by the Livescan system. After querying a JMS Arrest number, the WEB service request from Livescan shall be processed on the RMS WEB service and the appropriate arrest/booking data shall be returned and processed by Livescan. The test will also ensure that when the booking (fingerprint, mugshots) is completed on Livescan, a subsequent LA County booking number and mugshot update back to the JMS will occur.

OPERATIONAL TESTS
This test confirms that the booking data transferred from the RMS/JMS to Livescan is accurate and that the appropriate data elements are populated and verified in the Livescan system. This test will also confirm that upon completing of the booking process on Livescan, the LA County booking number and associated mugshots are stored on the JMS.

PERFORMANCE TESTS
This test confirms that the Web Service call to the JMS from Livescan to retrieve booking data (to be pre-filled into Livescan forms) shall take no more than 3 seconds. This test will also confirm that the booking number and mugshot update to the JMS will take no more than 4 seconds. These times shall exclude network latency issues and any transfer time between Livescan and LACRIS.

EXCEPTION TESTING
This test confirms that when an Arrest data request from Livescan to the JMS is received by the RMS Web Service and the requested Arrest record does not exist, Livescan receives a ‘RecordDoesNotExist’ return status.

BUSINESS CONTINUITY/INTERFACE AVAILABILITY

INTERFACE TESTING
313
Versaterm Public Safety Inc. & City of Torrance
SaaS Agreement #
Exhibit C.3 RMS Interface Control Document

Page 15 of 22 ends

CUSTOMER RESPONSIBILITIES
a. Provide Web Services technical specification for the Livescan system used at Torrance PD. b. Provide network connectivity between the Livescan server and vCloud RMS. c. Make the Livescan system available during interface testing. d. Perform interface tests with Versaterm.

VERSATERM RESPONSIBILITIES
a. Develop the Web Service transactions required to support the interface as per specifications provided by L-1 Identity Solutions.
b. Install and configure Web Services interface on the vCloud RMS. c. Perform interface tests with the City.

RESPONSIBILITIES
314
Versaterm Public Safety Inc. & City of Torrance
SaaS Agreement #
Exhibit C.3 RMS Interface Control Document

Page 16 of 22 ends

interface supports the automatic extract and transfer of police reports, from the Torrance Police Department’s (TPD) Versaterm RMS (vRMS) to CrimeTracer data sharing repository.

CrimeTracer, owned by SoundThinking, was previously known as Coplink, then owned by Forensic Logic.

Each time a report is added, updated or deleted in the TPD Versaterm RMS, the report number is written to a special extract tracking table. This table tracks the reports that need to be subsequently extracted from the Versaterm RMS.

The types of reports that are extracted include: Call for Service records, General Offenses, Field Interviews, Tickets, and Criminal Description records, excluding private and invisible reports.

A scheduled task is configured to run an extract program (developed by Versaterm), on a daily basis (e.g. every morning at 4AM), which reads from the tracking table to determine which reports need to be extracted.

The extract program extracts data from the Versaterm RMS into Extensible Markup Language (XML) data files conforming to SoundThinking’s specifications. These files are stored on the Versaterm RMS server (in the cloud) and then automatically transferred to CrimeTracer (which is also in the cloud).

Once the data is ingested into the CrimeTracer data sharing repository, the data can be viewed online using SoundThinking’s CrimeTracer access point. Note that this last step is not considered part of this interface The following are 2 scheduled processes (cron jobs) that Versaterm has setup to automate the extract process:

Scheduled process to perform the extract
#COPLINKX INTERFACE PROCESS
0 2 * * * ${FGLRUN} ${RUNTIME}/42M/COPLINKX_EXTRACT.42M ${VDXDB} <OP_CODE> >> ${VDXLOG}/COPLINKX_EXTRACT_${HOSTNAME}.LOG 2>&1
Scheduled process to delete extract files older than 30 days #COPLINKX INTERFACE
VTM_CLEAN_DIR $VDXRMSIF/COPLINKX/PROCESSED 30

CRIMETRACER INTERFACE

INTERFACE SCOPE

PROCESS FLOW

CONFIGURATION
315
Versaterm Public Safety Inc. & City of Torrance
SaaS Agreement #
Exhibit C.3 RMS Interface Control Document

Page 17 of 22 ends

The Versaterm RMS data is formatted to conform to SoundThinking’s CrimeTracer specifications, version 75.

The XML files that are generated by the Versaterm RMS are also archived to a directory (named using the current date and time, e.g. 12282010_0400). These archives are meant for auditing and troubleshooting purposes (as needed).

Versaterm Cloud -to- SoundThinking cloud file transfers are supported, using outbound SFTP file transfers over a secure connection. (This required that Versaterm provide IP’s to SoundThinking in order to be whitelisted).

For cloud-to-cloud file transfers, the authentication with SoundThinking us done via username and private key.

This interface will be available regardless of which region and/or availability zone the cloud-based RMS is currently serving up the RMS. Should the cloud-based RMS move across availability zones and/or regions, the RMS will reconnect automatically to the shared folder/directory and process the files accordingly.

Built into the extract program is an error recovery process. In the event of an extract failure, errors are logged in a file available to Torrance PD vRMS administrators for review.

An extract recovery program can be run to reset the datamart extract table by date range in order to ensure that specific reports will be extracted the next time the extract is run. Optionally, the extract of data can be manually triggered by Versaterm, by running the extract program for a specified time range.

FUNCTIONAL AND COMPLETENESS TEST
This test comprises of running the extract program to ensure that the required XML data files are written to the appropriate directory on the Versaterm RMS server and to ensure the archive directory is created as well.

OPERATIONAL TESTS
This test consists of adding, updating and deleting reports on the Versaterm RMS and ensuring that these reports and associated data are successfully extracted to XML files and sent to the CrimeTracer system.

PERFORMANCE TESTS
As this is a batch interface, there are no prescribed performance tests.

EXCEPTION TESTING
Tests will be conducted to ensure the validity of the error recovery extract process described previously is adhered to.

DATA FORMAT REQUIREMENTS

COMMUNICATION

AUTHENTICATION

BUSINESS CONTINUITY/INTERFACE AVAILABILITY

INTERFACE TESTING
316
Versaterm Public Safety Inc. & City of Torrance
SaaS Agreement #
Exhibit C.3 RMS Interface Control Document

Page 18 of 22 ends

CUSTOMER RESPONSIBILITIES
a. Provide contacts at SoundThinking to collaborate with Versaterm. b. Ensure SoundThinking collaborates with Versaterm to support cloud-to-cloud outbound SFTP file transfers over a secure connection.
c. Ensure SoundThinking collaborates with Versaterm to whitelist Versaterm’s IP addresses. d. Work with Versaterm to identify and confirm the types of reports that should be extracted to CrimeTracer. e. Test the extract by adding, updating and deleting RMS reports. f. Verify and confirm the RMS data integrity in CrimeTracer. g. Perform testing as described in the Interface Testing section above and confirm that the interface works as required.

VERSATERM RESPONSIBILITIES
a. Work with the Torrance Police Department to identify and confirm the types of reports that should be extracted to CrimeTracer.
b. Configure, enable and test the extract program appropriately. c. Setup and configure a scheduled task to automatically invoke the extract program (i.e. daily). d. Collaborate with SoundThinking to setup and test cloud-to-cloud outbound SFTP file transfers over a secure connection.
e. Provide SoundThinking with Versaterm’s IP addresses to be whitelisted. f. Perform initial testing of the interface.
g. Provide support to the Torrance Police Department while they test the adds, updates and deletes of RMS reports.
h. Provide support to the Torrance Police Department while they verify and confirm the RMS data integrity in CrimeTracer.

RESPONSIBILITIES
317
Versaterm Public Safety Inc. & City of Torrance
SaaS Agreement #
Exhibit C.3 RMS Interface Control Document

Page 19 of 22 ends

The Torrance Police Department (TPD) requires a data exchange interface between the Versaterm RMS and the Citation Processing Center (CPC) solution (from Data Ticket Inc.). This interface consists of a one-way data transfer of Citation information (parking only) from the Versaterm RMS to an Amazon Web Services (AWS) Secure File Transfer Protocol (SFTP) server (both residing in the Versaterm Cloud (vCloud)), which is made accessible to 3rd party vendors via SFTP.

The identified system that would be pulling this data is:

Citation Processing Center (CPC) solution (from Data Ticket Inc.).

Note: Warning citations and voided citations are stored in the RMS but are not exported to other systems. Versaterm will attempt to extract and format the data elements detailed in the CPC specification but might not be able to map every field.

1. Eligibility criteria: All Citations with tk_type = Parking

2. Text files (tab delimited with no text qualifiers) of all completed Parking citations will be exported from the RMS (on a schedule) to an Amazon Web Services (AWS) Secure File Transfer Protocol (SFTP) server within the Versaterm Cloud. • As Parking Citations are added to the RMS, they will be queued for extract, then nightly all queued tickets will be extracted into a text file and placed on the Versaterm SFTP. • In the event that a text file fails to transfer to the Versaterm SFTP, all queued Citations will be resent the following night.
• Successfully extracted Citations will be marked as extracted and cleared from the RMS Extract queue after 30 days. • Versaterm will extract and format the data elements detailed in the Data Ticket Inc. Text file specification. With a file name of: Parking_Citations_DATE_TIME.txt
• Versaterm supports SFTP only using Private/Public key encryptions, this must also be supported by the end point.

The following is the scheduled processes (cron job) that Versaterm w setup to automate the extract process:

Scheduled process to perform the extract
#CPC INTERFACE PROCESS
0 2 * * * ${FGLRUN} ${RUNTIME}/42M/TPDCPC.42M ${VDXDB} <OP_CODE> >> ${VDXLOG}/TPDCPC_EXTRACT_${HOSTNAME}.LOG 2>&1

CITATION PROCESSING CENTER (CPC) INTERFACE

INTERFACE SCOPE

PROCESS FLOW

CONFIGURATION
318
Versaterm Public Safety Inc. & City of Torrance
SaaS Agreement #
Exhibit C.3 RMS Interface Control Document

Page 20 of 22 ends

The following is the Required Parking Citation File Layout for Data Ticket Inc.’s Citation Processing Center (CPC). The file layout is defined and owned by Data Ticket Inc., and that any changes to the CPC spec (new fields, format changes, field reordering) would need to be coordinated with Versaterm as a change request with appropriate lead time for development and testing.

Note:

Please include the header record in the text file as the first record with the data following in record number 2.

See ParkingCitation_example.txt file
Field Field Type Required(?)
1 SeqNumber Numeric (Record Number, 1, 2, 3 etc.) Y
Sequential number, not
validated
2 StringDate Blank, not used any more
3 Badge # Alpha numeric Y
4 Citation # Alpha numeric (max 16) Y
5 Department Numeric (1 if client has no departments) Y 6 Plate Alpha numeric
Plate or VIN
is required
7 State Alpha numeric (2 characters max) Y
8 Make Alpha numeric (5 characters max) Y
9 Body Alpha numeric Y
10 Color Alpha numeric Y
11 VIN Alpha numeric
Plate or VIN
is required
12 Expiration Date Alpha numeric, format (MM/DD/YYYY)
13 Street No Alpha numeric
14 Location Alpha numeric Y
15 Violation 1
Alpha numeric. This is the violation without any
description. Example, 4000(a). Y
16 Violation Description 1 Alpha numeric
17 Violation Amount 1 Numeric Y
18 Violation 2
Alpha numeric. This is the violation without any
description. Example, 4000(a).
19 Violation Description 2 Alpha numeric
20 Violation Amount 2 Numeric
21 Violation 3
Alpha numeric. This is the violation without any
description. Example, 4000(a).
22 Violation Description 3 Alpha numeric
23 Violation Amount 3 Numeric
24 Cite Warning Numeric, values 0 or 1 Y 0 for Cite, 1 for Warning 25 Fled Flag Numeric, values 0 or 1 y 1 if Driver fled before cited 26 Comment Alpha numeric (max 300 characters)
27 Cite Date Date, format MM/DD/YY H:MM:SS AM or PM y Can also be military time 28 Meter # Alpha numeric

DATA FORMAT REQUIREMENTS
319
Versaterm Public Safety Inc. & City of Torrance
SaaS Agreement #
Exhibit C.3 RMS Interface Control Document

Page 21 of 22 ends

29 Secondary Color Alpha numeric
30 Model Alpha numeric
31 Vehicle Year Integer
32 Hidden comments Alpha numeric (max 500 characters)
33 District Alpha numeric
34 Void Reason Alpha numeric (max 500 characters)
35 Latitude
36 Longitude
37 Software Version
Alpha numeric (Used in heading line only, for
internal use only.)
The following is a sample layout of the data (that TPD is currently using) for multiple citations to be contained in each extract.

SeqNumber StringDate BadgeNo CitationNo Department VPlate VState VMake VBodyType VColor VIN ExpDate StNo Location Long1 VioDesc1 VioAmt1Long2 VioDesc2 VioAmt2 Long3 VioDesc3 VioAmt3CiteWarn Fled Comment CiteDateMeterNo Sec Color Model VYear Hidden Distr Void Lat Lon End
10449 J348 B070011449 6 1ABC587 CA HOND 2 DOOR BLK 0335 3/31/2014 133 CONCORD BART STATION BR24954B SIGN VIO: CARPOOL ONLY 6-10AM 40 0 0 0 0 NO CARPOOL PERMIT(S) VISIBLE 05/30/17 08:08 AM
AVALANCHE 38.016426747991865 -121.94524061566457 end
10450 J348 B070011450 6 1BCD746 CA NISS 4 DOOR BLK 9161 8/31/2014 132 CONCORD BART STATION BR24954B SIGN VIO: CARPOOL ONLY 6-10AM 40 0 0 0 0 NO CARPOOL PERMIT(S) VISIBLE 05/30/17 08:10 AM
ELANTRA 38.01646837940981 -121.94515544965141 end
10451 J348 B070011451 6 1CDE553 CA LEXU 4 DOOR WHT 5012 3/31/2014 103 CONCORD BART STATION BR24954B SIGN VIO: CARPOOL ONLY 6-10AM 40 0 0 0 0 NO CARPOOL PERMIT(S) VISIBLE 05/30/17 01:12 PM
CAMRY 38.01649635715806 -121.94514516251537 end
The communication and configuration for the extract and transfer of the necessary Text file for this interface will be based on target locations and parameters supplied by the City (e.g. run frequency (every 20 minutes)). • Text files of all completed parking citations will be exported (on a schedule- daily at 2:30 AM PT) to an Amazon Web Services (AWS) Secure File Transfer Protocol (SFTP) within the Versaterm Cloud, where the Data Ticket Inc. can retrieve it from.
• The communication between vRMS Integration Client application and the SFTP server is provided via password less SFTP, using private/public key exchanges.

For cloud-to-cloud file transfers, the authentication with Data Ticket Inc. done via username and private key.

BUSINESS CONTINUITY/INTERFACE AVAILABILITY

COMMUNICATION

AUTHENTICATION
320
Versaterm Public Safety Inc. & City of Torrance
SaaS Agreement #
Exhibit C.3 RMS Interface Control Document

Page 22 of 22 ends

Built into the extract program is an error recovery process. In the event of an extract failure, errors are logged in a file available to Torrance PD vRMS administrators for review.

FUNCTIONAL AND COMPLETENESS TEST
This test comprises adding new citations previously specified to the Versaterm RMS and ensuring that the files are successfully extracted.

OPERATIONAL TESTS
This test comprises of running the CRON to ensure that the required data files are extracted and transferred as required.

PERFORMANCE TESTS
As this is a batch interface, there are no prescribed performance tests.

EXCEPTION TESTING
Tests will be conducted to ensure the validity of the error recovery extract process described previously is adhered to.

CUSTOMER RESPONSIBILITIES
a. Assist in testing and verifying the citation extract. b. Coordinate with Data Ticket Inc. to process files (Text File) available for Citation Processing Center c. Coordinate resource availability with City of Torrance IT and Data Ticket Inc. as required. d. Coordinate with Data Ticket Inc. on the enabling and configuring of required networking to allow Citation Processing Center to connect to the required Amazon SFTP end point in vCloud. e. Customer will perform interface testing with Data Ticket Inc.

VERSATERM RESPONSIBILITIES
a. Versaterm will develop, install and test the extract facility to create and send the necessary, Text file for this interface.
b. Provide a technical resource to support Torrance PD during the interface testing. c. Provide the necessary support for the go-live cutover of the interface.

INTERFACE TESTING

RESPONSIBILITIES
321
Versaterm Public Safety Inc. & City of Torrance
SaaS Agreement #
Exhibit C.4 - RMS Data Conversion

Page 1 of 1 ends

EXHIBIT C.4

RMS DATA CONVERSION
No Data Conversion is included in this Agreement.

Versaterm recognizes that the City wishes to convert legacy property data into the vRMS post Go-Live.

The Parties will execute a mutually agreed upon separate services contract governing such data conversion.
322
Versaterm Public Safety Inc. & City of Torrance
SaaS Agreement #
Exhibit C.5 - Acceptance Test Plan

Page 1 of 9 ends

EXHIBIT C.5

RMS ACCEPTANCE TEST PLAN
323
Versaterm Public Safety Inc. & City of Torrance
SaaS Agreement #
Exhibit C.5 - Acceptance Test Plan

Page 2 of 9 ends

Overview ..............................................................................................................................................................3 1 Interface Integration Testing .............................................................................................................................................3

1.1 Objectives............................................................................................................................................................3

1.2 Strategy ...............................................................................................................................................................3

1.3 Schedule ..............................................................................................................................................................3

1.4 Dependencies ......................................................................................................................................................3

1.5 Server Environment .............................................................................................................................................4

1.6 Problem Tracking and Remedies ..........................................................................................................................4

1.7 Completion Criteria..............................................................................................................................................4 2 Functional Acceptance Testing ..........................................................................................................................................4

2.1 Objectives............................................................................................................................................................4

2.2 Strategy ...............................................................................................................................................................4

2.3 Schedule ..............................................................................................................................................................5

2.4 Dependencies ......................................................................................................................................................5

2.5 Server Environment .............................................................................................................................................6

2.6 Problem Tracking and Remedies ..........................................................................................................................6

2.7 Completion Criteria..............................................................................................................................................6 3 Reliability Acceptance Testing ...........................................................................................................................................7

3.1 Objectives............................................................................................................................................................7

3.2 Strategy ...............................................................................................................................................................7

3.3 Schedule ..............................................................................................................................................................7

3.4 Dependencies ......................................................................................................................................................7

3.5 Server Environment .............................................................................................................................................7

3.6 Problem Tracking and Remedies ..........................................................................................................................7

3.7 Reliability / Downtime Definition.........................................................................................................................7

3.8 Completion Criteria..............................................................................................................................................9 4 Final System Acceptance ...................................................................................................................................................9 5 Defect Classifications.........................................................................................................................................................9

CONTENTS
324
Versaterm Public Safety Inc. & City of Torrance
SaaS Agreement #
Exhibit C.5 - Acceptance Test Plan

Page 3 of 9 ends

This Exhibit describes the parameters involved in the Acceptance Test Plan which will be used per the Agreement and Statement of Work. The Acceptance Test Plan involves three (3) types of acceptance tests:
• Interface Integration Testing
• Functional Acceptance Testing
• Reliability Acceptance Testing
The procedures to conduct each type of acceptance test are documented within each test plan (below). The Customer has the primary responsibility of conducting the Acceptance Tests, where Versaterm will support and assist the Customer as required.

The purpose of Interface Integration Testing is to demonstrate and verify that all interfaces specified in the Interface Control Document meet or exceed the functionality and performance expectations, and that each interface is operational and ready for Functional Acceptance Testing.

The process of testing the interfaces also provides the Customer with the knowledge necessary to complete the Functional Unit Testing for each interface.

As each interface is developed and installed, Versaterm will remotely assist the Customer’s Project Team with performing testing.

Versaterm will demonstrate each interface to Customer personnel to confirm that it adheres to the specifications documented in the Interface Control Document. The Customer personnel will test and verify the results.

Errors will be tracked and remedied.

The Interface Integration Test is formally scheduled for five (5) Business Days and will be conducted in accordance with the Project Schedule. However, individual interfaces are expected to be tested as they are ready during the Interface Development and Testing task. The Interface Integration Test period may be extended beyond the initial five (5) Business Days if there are confirmed discrepancies that prevent the Interface Integration Test from being completed successfully within the initial five (5) Business Days.

Integration Testing has the following dependencies:

OVERVIEW
1 INTERFACE INTEGRATION TESTING

1.1 OBJECTIVES

1.2 STRATEGY

1.3 SCHEDULE

1.4 DEPENDENCIES
325
Versaterm Public Safety Inc. & City of Torrance
SaaS Agreement #
Exhibit C.5 - Acceptance Test Plan

Page 4 of 9 ends

• Install the Production Environment in the Cloud
• Develop and install interfaces.
• Configure the Application Software.
• For each interface that involves another application/system, a test/development system to which the Versaterm system can connect must be available, or a plan must be in place to enable the required testing.

Interfaces will be tested in the Cloud Production Environment prior to the System being used for Production Use.

After cutover to Production Use, any interface not previously tested will be tested in the Development/Test Environment prior to being installed in the Production Environment for final testing.

Each discrepancy/issue will be documented in the Issues List.

Within ten (10) Business Days of finding and documenting a discrepancy that can be classified as Critical Priority Error or High Priority Error, in Section 6 of this document, Versaterm will correct the issue and then request, in writing, that the Customer retest the interface.

The Customer shall repeat the failed Interface Test within ten (10) Business Days of receipt of Versaterm’s written request and shall advise Versaterm, in writing, of the results within five (5) Business Days of the test’s completion.

Discrepancies that are classified as Minor Error will not prevent the Integration Test from being successfully completed.

Integration Testing will be considered successfully completed when all of the following criteria are met:
• The Customer has verified that all interfaces operate as specified in the Interface Control Document • The Customer’s Project Team and other select Customer staff are sufficiently trained to be able to administer, manage, and fully use each Interface.
• The Customer confirms, in-writing, of either acceptance, rejection or conditional acceptance of the interface integration tests for each interface within five (5) business days of completing the final tested interface.

The purpose of Functional Acceptance Testing is to verify that the fully configured System, including the interfaces specified in the Interface Control Document, meets the functional requirements described in the Agreement.

1.5 SERVER ENVIRONMENT

1.6 PROBLEM TRACKING AND REMEDIES

1.7 COMPLETION CRITERIA
2 FUNCTIONAL ACCEPTANCE TESTING

2.1 OBJECTIVES

2.2 STRATEGY
326
Versaterm Public Safety Inc. & City of Torrance
SaaS Agreement #
Exhibit C.5 - Acceptance Test Plan

Page 5 of 9 ends

The Customer will develop a Standard Acceptance Test Plan suitable for verifying the solution’s functionality.

Customer workflow processes will be the basis of the Test plan. These processes will be documented during system implementation by the Customer for use during the test period.

At the conclusion of Functional Acceptance Test development task, the Customer may use the tests to perform independent testing of the system prior to the formal Functional Acceptance Testing task. With assistance from Versaterm, the Customer will conduct Functional Acceptance Tests on the system to verify that functionality meets the test scenarios and tests.

During the Functional Acceptance Testing task, the Customer will track whether requirements pass or fail tests. If a requirement fails a test, it will be classified as a “Failure” if related to a software application error, and Versaterm shall have up to ten (10) business days to correct any Failure or provide a Customer-approved approach for correcting the Failure. Once a Failure is corrected, Versaterm and the Customer will conduct additional testing of that requirement to verify that it passes the test.

The system will be deemed to have passed Functional Acceptance Testing when all scenarios and requirements pass the test or the Customer approves Versaterm-proposed workarounds or approaches to remedy Failures. The Customer will conduct Functional Acceptance Testing with remote support from Versaterm. During Functional Acceptance Testing, Versaterm will be immediately available to answer questions and address any issues. Errors will be tracked and remedied.

The Functional Acceptance Testing period should not exceed ten (10) Business Days and will begin according to the mutually agreed upon Project Implementation Schedule and after Versaterm has provided the Customer with written notice that the System is ready for Functional Acceptance Testing. If the Customer does not believe the System is ready for the Functional Acceptance Test, it will provide the reasons in writing to Versaterm within five (5) Business Days of receipt of Versaterm’s notification.

The Functional Acceptance Testing period may be extended if there are confirmed defects that prevent the Functional Acceptance Test from being completed successfully. Functional Acceptance Testing must be successfully completed before Versaterm-delivered Trainer-Training and End-User training can commence.

Functional Acceptance Testing has the following dependencies:
• Production Environment Infrastructure available in the cloud • Integration Testing completed
• Enhancements have been installed in the Test Production environment • Geofile loaded
• Validation tables populated
• Workflows configured
• For each Interface that involves another application/system, a test/development system to which the Versaterm system can connect must be available, or a plan must be in place to enable the required testing.

2.3 SCHEDULE

2.4 DEPENDENCIES
327
Versaterm Public Safety Inc. & City of Torrance
SaaS Agreement #
Exhibit C.5 - Acceptance Test Plan

Page 6 of 9 ends

The Functional Acceptance Tests will be conducted in the Production Environment prior to the System being used for Production Use.

The Customer will document each discrepancy between observed functionality and the Agreement specifications.

The Customer will provide, in writing, a list of the discrepancies and defects to Versaterm. The Customer and Versaterm Project Managers will mutually agree on the classification of each defect according to the definitions in Section 5 of this document.

Each discrepancy/issue will be documented in Customer’s SharePoint Issues List.

Within ten (10) Business Days of receiving written notification of Functional Acceptance Testing discrepancies, Versaterm will either:
• Correct confirmed defects that prevent Functional Acceptance Testing from being completed successfully and then request, in writing, that the Customer repeats the failed Functional Acceptance Testing component(s) that resulted in the defects; or
• Provide a mutually agreeable solution to confirmed defects consisting of either a future System patch correction that will be installed at a mutually agreeable time period, or a mutually agreeable workaround.

Versaterm must remedy all defects classified as Critical Priority Errors or High Priority Errors before Functional Acceptance Testing is completed and training begins. The Customer and Versaterm Project Managers will mutually agree on any Minor Errors that must be remedied before training begins, Production Use occurs, or Final System Acceptance, and which can be remedied in a future release.

All defects will be documented and reported to Versaterm, and Versaterm will provide a schedule and/or mitigation procedure for all reported defects.

The Customer shall repeat the failed Functional Acceptance Testing within ten (10) Business Days of receipt of Versaterm’s remedy for an error, and shall advise Versaterm, in writing, of the results within five (5) Business Days of the test’s completion.

Functional Acceptance Testing will be considered successfully completed when all of the following criteria are met:
• The System and Interfaces have been verified by the Customer to operate as specified in the Agreement. • All scenarios and requirements have passed the test, or the Customer has approved Versaterm-proposed workarounds or approaches to remedy unresolved Failures.

2.5 SERVER ENVIRONMENT

2.6 PROBLEM TRACKING AND REMEDIES

2.7 COMPLETION CRITERIA
328
Versaterm Public Safety Inc. & City of Torrance
SaaS Agreement #
Exhibit C.5 - Acceptance Test Plan

Page 7 of 9 ends

Reliability Acceptance Testing ensures that the System continues to operate according to the specifications contained within the Agreement for thirty (30) consecutive calendar days after the System cutover to Production Use.

After cutover to Production Use, the System will undergo a thirty (30)-day test period. The Customer will use the System for its intended purposes and monitor system reliability, functionality, and performance. Errors will be tracked and remedied.

Reliability Acceptance Testing begins immediately following System cutover to Production Use. It ends when the System operates at an availability level of 99.99% for thirty (30) consecutive days without a Critical Priority Error or High Priority Error, and the Customer and Versaterm have mutually agreed upon a plan to remedy all Minor Errors.

Reliability Acceptance Testing is dependent on the System being enabled for Production Use.

Reliability Acceptance Testing will be conducted in the Production Environment in the Cloud.

The Customer will use the System for its intended purpose and monitor the System for defects. The Customer will document in writing and report to Versaterm any System defects encountered. The Customer and Versaterm Project Managers will mutually classify each defect according to the definitions in this Exhibit.

The Customer will immediately inform Versaterm by telephone upon discovery of a Critical Priority Error or High Priority Error, and Reliability Acceptance Testing will immediately stop. The Customer will follow-up with a written notification of the defect to Versaterm. Once the problem is resolved, Reliability Acceptance Testing will start over from day one (1) and a new thirty (30)-Day Reliability Acceptance Test period will begin.

Discovery of a Minor Error will not stop the Reliability Acceptance Testing. Versaterm will attempt to remedy Minor Errors during the Reliability Acceptance Testing period. If Versaterm is not able to fix a Minor Error during the Reliability Acceptance Testing period, Versaterm and the Customer will develop a mutually acceptable plan to remedy the defect in a future fix release.
3 RELIABILITY ACCEPTANCE TESTING

3.1 OBJECTIVES

3.2 STRATEGY

3.3 SCHEDULE

3.4 DEPENDENCIES

3.5 SERVER ENVIRONMENT

3.6 PROBLEM TRACKING AND REMEDIES

3.7 RELIABILITY / DOWNTIME DEFINITION
329
Versaterm Public Safety Inc. & City of Torrance
SaaS Agreement #
Exhibit C.5 - Acceptance Test Plan

Page 8 of 9 ends

The System will be considered “down” (i.e., not available to end-users) if a Critical Priority Error or High Priority Error is encountered during the Reliability Acceptance Testing period using the following approach:

Critical Priority Error ─ Critical errors that are defined as Loss of Data, Corruption of Data, or Loss of Productive Use of the Application. In the event this type of error occurs, the Customer will immediately notify Versaterm, and the Reliability Test period will be cancelled. Versaterm personnel shall promptly resolve the problem at no additional cost to Customer and a new Reliability Test period will begin. Upon receipt of a Critical Priority software correction, Customer has 72 hours to test the software correction and resume productive use. If Customer does not place the software correction into production within 72 hours, the new Reliability Test period will begin. Once the System operates for thirty (30) consecutive days without a Critical Priority Error, the Reliability Test will be complete.

High Priority Error ─ Non-critical errors defined by incomplete operation of a single system application where a procedural workaround is available, and productive use of the system is impacted. In the event this type of error occurs, Customer will immediately notify Versaterm, and the Reliability Test period will be suspended. Versaterm personnel shall resolve the problem at no cost to the Customer. Once repaired, the Reliability Test period will recommence at the point where it was suspended. Upon receipt of a High Priority Error software correction, the Customer has 48 hours to test the software correction and place it into production. If the Customer does not place the software correction into production within 48 hours, the Reliability Test period will resume, and the Reliability Test period will recommence at the point where it was suspended.

Failures outside of Versaterm’s control, such as individual workstation failures (e.g., a Windows operating system failure, insufficient memory, etc.), will not be considered System defects and will not affect the outcome of the Reliability Acceptance Testing as long as there is productive use of the System on other workstations.

If System unavailability is mutually agreed upon and scheduled for the purpose of Application Software updates, performance tuning, file backups, or other processes typical in an operational environment, the System will not be considered unavailable and will not impact the successful completion of Reliability Acceptance Testing.

The System will also not be considered unavailable if other factors such as the network, external agency, operator, or Cloud environment are mutually determined by the Customer and Versaterm to be the cause of encountered defects.

If the System’s unavailability is attributed to any integrated Third-Party product, both Parties will first assist each other in identifying the root cause. Once the defect has been corrected or a mutually agreeable workaround has been implemented, the System will be considered available again.

If the System’s unavailability is attributable directly to a Third-Party product interfaced or integrated with the System that is beyond Versaterm’s control, then the System shall be considered available from the point at which the defect was originally reported to Versaterm.

If the System is unavailable because of other factors that are beyond Versaterm’s control (e.g., Force Majeure, catastrophic network failures, Third-Party product Interfaces not provided by Versaterm, etc.) and these factors result in users not being able to make production use of the System, at the sole discretion of the Customer, Reliability Acceptance Testing will be suspended until the System can be placed in Production Use again. When the System is placed into Production Use again, the Reliability Acceptance Test will be resumed from the point at which it was suspended.
330
Versaterm Public Safety Inc. & City of Torrance
SaaS Agreement #
Exhibit C.5 - Acceptance Test Plan

Page 9 of 9 ends

During the Reliability Acceptance Testing period, Versaterm will not stop the System (force it to be unavailable for Production Use), upgrade the Application Software, or otherwise negatively impact the operational status of the System without the written permission of the Customer. The System will continue to operate to the best of its abilities even while/if the Reliability Acceptance Testing has been suspended due to encountered defects.

Reliability Acceptance Testing is considered complete when the System has operated for thirty (30) consecutive Days without a Critical Priority Error or High Priority Error and a mutually agreeable plan to remedy all other Minor Errors has been developed.

Final System Acceptance will occur after the completion of the 30-day Reliability Acceptance Testing and when a mutually agreeable plan to remedy all minor Errors has been developed.

The Customer and Versaterm will classify all found defects according to the following definitions for error levels:

Critical Priority Error ─ Critical errors that are defined as Loss of Data, Corruption of Data, or Loss of Productive Use of the Application.

High Priority Error ─ Non-critical errors defined by incomplete operation of a single system application where a procedural workaround is available, and productive use of the system is impacted.

Minor Error ─ Cosmetic errors that are defined as configuration issues that can be corrected by Customer, data integrity issues that must be addressed by Customer, Help file documentation errors, or enhancements that can be made in the future to the presently released version. Minor issues relating to a specific component of the System that does not affect the productive use of the System or component. Examples include a field that is right-justified rather than left-justified or the usage of an inconsistent font.

3.8 COMPLETION CRITERIA
4 FINAL SYSTEM ACCEPTANCE
5 DEFECT CLASSIFICATIONS
331
Versaterm Public Safety Inc. & City of Torrance
SaaS Agreement #
Exhibit C.6 - RMS Training Plan

Page 1 of 9 ends

EXHIBIT C.6

RMS TRAINING PLAN
332
Versaterm Public Safety Inc. & City of Torrance
SaaS Agreement #
Exhibit C.6 - RMS Training Plan

Page 2 of 9 ends

1 TRAINING PLAN OVERVIEW..........................................................................................................................3

1.1 TRAINING FACILITIES .....................................................................................................................................3

1.2 INITIAL TRAINING APPROACH ......................................................................................................................3

1.2.1 VERSATERM TRAIN-THE-TRAINER TRAINING .................................................................................... 3

1.2.2 END-USER TRAINING .............................................................................................................................. 4

1.2.3.1 STEP 1: IDENTIFY USER GROUPS .............................................................................................................................. 4

1.2.3.2 STEP 2: IDENTIFY TRAINING COURSES (AND ESTIMATED DURATION) ..................................................................... 4

1.2.3.3 STEP 3: ASSIGN COURSES TO EACH USER GROUP .................................................................................................... 4

1.2.3.4 TARGET AND TIMING RECOMMENDATIONS FOR INITIAL END-USER TRAINING...................................................... 4

1.2.4 POST-IMPLEMENTATION TRAINING .................................................................................................... 5

1.3 FINAL TRAINING APPROACH .........................................................................................................................5 2 COURSE OUTLINES .........................................................................................................................................5

2.1 RMS INTRODUCTION (RMS_INTRO) .............................................................. …………………………………………. 5

2.2 RMS DATA-ENTRY (RMS_DATAENTRY) ......................................................... …………………………………………. 6

2.3 DETECTIVE (RMS_DET)..................................................................................... …………………………………………. 6

2.4 JAIL MANAGEMENT/ ARRESTS (RMS_AR).................................................... …………………………………………. 7

2.5 PROPERTY & EVIDENCE (RMS_PROP) ........................................................... …………………………………………. 8

2.6 DATA TRANSCRIPTION QUEUE (RMS_TRANSQ).......................................... …………………………………………. 8

2.7 RECORDS SUPERVISOR TRAINING (RMS_SUP)............................................ …………………………………………. 9

2.8 SYSTEM ADMINISTRATOR TRAINING (RMS_ADMIN) ................................ …………………………………………. 9

2.9 MOBILE REPORT ENTRY TRAINING (MRE) ................................................... …………………………………………. 10

CONTENTS
333
Versaterm Public Safety Inc. & City of Torrance
SaaS Agreement #
Exhibit C.6 - RMS Training Plan

Page 3 of 9 ends

This document describes Versaterm’s recommended training approach for the implementation of the Versaterm RMS and MRE software and is intended to be used as a guide to planning and delivering training to all users.

The Training Plan and approaches may be refined and further elaborated as required during the Project, where the Customer and Versaterm will collaborate and mutually agree on any refinements.

This document also describes the course outlines that Versaterm will deliver to the Customer.

Amongst other requirements, the training facilities are required to meet CJIS security, support network encryption, and support physical access requirements.

The facilities are also expected to be dedicated solely to Versaterm application training during the end- user training periods, without requiring daily software re-installation and infrastructure re-configuration.

The following is a list of requirements/recommendations for the training facilities:
• At least fifteen to twenty (15-20) dedicated workstations that meet the minimum Versaterm RMS and MRE application requirements.
• At least one additional workstation for the training instructor. • Dedicated network access provided between each workstation and the Versaterm servers. • At least one overhead projector and screen that is viewable by all trainees (i.e., from each training workstation) and that is able to display the contents of the training instructor’s workstation monitor(s).
• One whiteboard with Dry-Erase markers.
• A network printer which is configured to be the default printer for each workstation.

The Training Phase will follow the completion of the Configuration and Initial Testing phases of the Project Implementation Schedules. The proposed training approach, as requested by the Torrance Police Department, will be End-User-Training delivered by Versaterm staff with support from TPD personnel/SMEs.

TPD agrees that two (2) TPD employees (Business Unit/Process specific Subject Matter Experts (SME)) will be present at each respective Course module training session. The purpose of this is to ensure local SMEs 1 TRAINING PLAN OVERVIEW

1.1 TRAINING FACILITIES

1.2 INITIAL TRAINING APPROACH

1.2.1 VERSATERM TRAIN-THE-TRAINER TRAINING
334
Versaterm Public Safety Inc. & City of Torrance
SaaS Agreement #
Exhibit C.6 - RMS Training Plan

Page 4 of 9 ends

support any agency policy questions which arise during the sessions, AND, to develop the skills necessary to carry forward future EUT by virtue of repetition and classroom support.

Versaterm’s recommended End-User training strategy starts with identifying the affected user groups, the courses to be taught and the duration of each course (who, what, and how long). Once these key factors are identified, the training strategy involves planning the logistics and training schedules (who, when and where).

The first step involves identifying all of the affected user groups across the Customer that will require training. For example: Records Specialist, Detectives, Patrol, Corrections Officers, Supervisors, Crime Analysts, System Administrators etc.

Following the identification of the affected user groups, the second step involves identifying the training courses that will be taught. While identifying the courses, the course objectives, the course outline, the course content, and the targeted audience will be determined at a high-level, along with the estimated duration of each course (in hours).

Following the identification of user groups and training courses, the next step involves matching up the courses to each user group based on what they will need to be trained on to perform their everyday jobs. Once the training needs of each user group are identified, the estimated total amount of training time (per user group) can be determined. For example: Dispatchers will require training in X, Y and Z which amount to a grand total of 32 hours of training.

Courses will be hosted in a single location and configured as described in section 1.1. Classroom time will be between 8 and 10 hours based on the local agency’s typical schedule and offered during business hours Monday through Friday. Alternative classroom time may be optional, but Versaterm will not support End-User-Training between 10pm and 6am or on weekends.

Ideally, all end-users would be trained prior to the production cutover date, however, as end- users may be on vacation, sick, between promotions, or otherwise unavailable to attend the training, Versaterm recommends that End-User Training be targeted for approximately 85% of affected end-users.

In addition, Versaterm recommends that End-User training be delivered within a maximum of five (5) weeks, prior to the production cutover date. This approach is referred to as “Just in Time” training, a timely strategy that eliminates the need for refresher training. This approach reduces potential knowledge loss if training were delivered over an extended period of time, too far from the production cutover date.

1.2.2 END-USER TRAINING

1.2.3.1 STEP 1: IDENTIFY USER GROUPS

1.2.3.2 STEP 2: IDENTIFY TRAINING COURSES (AND ESTIMATED DURATION)

1.2.3.3 STEP 3: ASSIGN COURSES TO EACH USER GROUP

1.2.3.4 TARGET AND TIMING RECOMMENDATIONS FOR INITIAL END-USER TRAINING 335
Versaterm Public Safety Inc. & City of Torrance
SaaS Agreement #
Exhibit C.6 - RMS Training Plan

Page 5 of 9 ends

With the “Just in Time” approach, trained end-users will be able to immediately use the production RMS system as of the production cutover date.

For the minority percentage of end-users who will not receive training prior to the production cutover date, Versaterm recommends post-implementation training for these end-users.

ALL Training provided after production cutover will be provided by TPD employees/SMEs.

Likewise, for the end-users who require refresher training after the production cutover date, Versaterm recommends that the Customer develops an on-going training plan to accommodate post- implementation training needs. Such needs to consider include, but are not limited to:
• Refresher/Remedial Training
• New Employee Training
• Transitional Training (i.e. Patrol <>Detectives)
• Elective operational/procedural changes
• Onboarding new RMS features into your business processes The Torrance Police Department has requested Versaterm provide End-User-Training to all RMS users, to include necessary curriculum for mobile CAD and RMS applications.

Torrance Police Department Training Responsibilities:

The Torrance Police Department will ensure there is at least one (preferably two) agency employees present at all training sessions to support the transfer of knowledge and be able to assist in the following scenarios:

1. Support the Versaterm Lead Instructor.

2. Answer questions from employees related to policies and/or procedures.

3. Develop the skills needed to be Lead Instructor(s)/Experts for future agency employees, remedial training and any changes moving forward.

The course details in this section outline at a high-level the materials covered in each user-group based End User Training session.

Notes:
• Each course may be modified or tailored as necessary. • The time & instructor ratios for each course are provided as ‘Best-Practices’ recommendations. • Versaterm does not provide any training for Microsoft Windows. If the Customer requires such training, it is expected that this level of training will be acquired by the Customer from a Third Party prior to training on the Versaterm products.

1.2.4 POST-IMPLEMENTATION TRAINING

1.3 FINAL TRAINING APPROACH
2 COURSE OUTLINES
336
Versaterm Public Safety Inc. & City of Torrance
SaaS Agreement #
Exhibit C.6 - RMS Training Plan

Page 6 of 9 ends

• The 2.A.x course outlines have been removed as these are specific to a Train-The-Trainer delivery method.

2.B.1.1 RMS Administrators
Course Duration 1 Day
Intended Audience Administrative PD Employees performing high level administrative functions in the RMS to include Record Supervisors and RMS Administrators Course Objectives Participants will be made familiar with the administrative functions of the RMS employed by the agency at Go-Live. This will include, but may not be limited to:

A. Understand the organization (menu layout) of the System B. Know how to use the query functionality within the System C. Understand how information is related and how to print a hardcopy D. Know how to use the browse (ad-hoc query) facility
E. Know how to use System Mail (attach Mail, etc.)
F. Know how to use the online help facility
G. Understand process to add/assign new users
H. Know processes to audit RMS actions
I. Understand RMS User and Group Security management
J. Understand additional RMS processes related to their operational role(s)

2.B.1.2 RMS Administration/Civilian Users
Course Duration 1 Day
Intended Audience Administrative PD Employees with needed access to the RMS for administrative and support purposes.

Course Objectives Participants will be made familiar with the administrative functions of the RMS employed by the agency at Go-Live. This will include, but may not be limited to:

A. Understand the organization (menu layout) of the System B. Know how to use the query functionality within the System C. Understand how information is related and how to print a hardcopy D. Know how to use the browse (ad-hoc query) facility
E. Know how to use System Mail (attach Mail, etc.)
F. Know how to use the online help facility
G. Understand additional RMS processes related to their operational role(s)
337
Versaterm Public Safety Inc. & City of Torrance
SaaS Agreement #
Exhibit C.6 - RMS Training Plan

Page 7 of 9 ends

2.B.2.1 Sworn Users (Field Operations)
Course Duration 2 Days
Intended Audience This course is designed for users who generate event reports from the field.

Typically Patrol Officers, Patrol Specialties and other users working primarily in the field.

Course Objectives Participants will understand how to use the MRE for documentation and report writing. These topics will include:

A. Prefilling CAD related event and entity details to the MRE B. General Offense Reports
C. Supplemental Reports
D. Follow Up Submittal
E. Property/Evidence
F. Field Interviews
G. Arrest Report
H. Tickets
I. Complete NIBRS and other report validation(s)

2.B.2.2 Sworn Users (Investigations)
Course Duration 2 Days
Intended Audience This course is designed for users who do not work in a field/mobile capacity on a day-to-day basis and will work directly in the RMS. These users are typically detectives and members of investigations or similar specialty units.

Course Objectives Participants will be made familiar with the necessary business process of the RMS from the Desktop working environment. This session will include, but may not be limited to:

A. Know how to enter and maintain events (general offense reports, accidents, tickets, street checks, flag records) including specific data requirements for workflow.

B. Know how to retrieve a cleared complaint to start a report C. Know how to access query
D. Know how to enter property (stolen, lost, in custody property etc.) E. Know how to enter and maintain follow-ups (and related text) F. Know how to enter person information (including different linkage factors and aliases. Understand Master vs Case Specific and the MNI validation process.

G. Know how to maintain vehicle information (including particulars) H. Know how to maintain business information (including particulars, aliases)
I. Know how to add an Arrest.

J. Know how to scan documents, attach scanned documents and/or files to a report, and how to retrieve and view scanned images and attachments
338
Versaterm Public Safety Inc. & City of Torrance
SaaS Agreement #
Exhibit C.6 – RMS Minimum Client and Peripheral Specifications

Page 8 of 8 ends

K. Know how to print hardcopies and disseminate information via Release Tracking.

L. Understand workflow management concepts for MRE Approval Process
M. Perform validation and correct edits.

N. Know how to add, retrieve and update General Offense (GO) reports O. Know how to add a supplemental to the General Offense (GO) report
P. Know how to relate text (including word-processor functions), detail pages, and clearance blocks to events
Q. Know how to assign cases (add follow-ups and related text) R. Know how to manage workflow queues

2.B.3.1 Jail Management System
Course Duration 1 – 2 Days
Intended Audience This course is intended for users who work primarily in the Jail/Holding area and are responsible for the intake, housing, management and release of arrested persons.

Course Objectives This session will cover the skills necessary to operate the Jail facility within the scope of the JMS. The length of this class will be tailored to the needs of the agency. Covered skills will include:

A. Beginning a booking process from a submitted Arrest Report B. Using questionnaires and other documentation customary during the intake process
C. Assigning Cells
D. Managing transfers
E. Inmate Property
F. Court and other scheduling
G. Release Management

2.B.4.1 In-Custody Property Management
Course Duration 1-2 Days
Intended Audience This course is designed for employees who work in the Property/Evidence unit of the agency and are responsible for the management of all property to include evidence, found and safe keeping.

Course Objectives Participants will learn the following skills:

A. Processing in new items
B. Assigning Storage Control details
C. Auditing in-custody property
D. Managing items in/out for court and other purposes
E. Generating letters, reports, et al
F. Release/Disposal of Property
339
Versaterm Public Safety Inc. & City of Torrance
SaaS Agreement #
Exhibit C.7 – RMS Minimum Client and Peripheral Specifications

Page 1 of 8 ends

EXHIBIT C.7

RMS MINIMUM CLIENT AND PERIPHERAL

SPECIFICATIONS
340
Versaterm Public Safety Inc. & City of Torrance
SaaS Agreement #
Exhibit C.7 – RMS Minimum Client and Peripheral Specifications

Page 2 of 8 ends

Overview............................................................................................................................................... - 3 - 1 Workstation Recommendations........................................................................................................... - 4 -

1.1 RMS Client Computers ....................................................................................................................... - 4 -

1.2 Mobile Data Computers (with Maps)................................................................................................. - 5 -

1.3 vMobile .............................................................................................................................................. - 6 - 2 Hardware Peripherals .......................................................................................................................... - 7 -

2.1 Property Bar Code Label Printers ....................................................................................................... - 7 -

2.2 Property Bar Code Scanners .............................................................................................................. - 7 -

2.3 Drivers License Card Swipe Readers .................................................................................................. - 8 -

2.4 Document Scanners ........................................................................................................................... - 8 -

CONTENTS
341
Versaterm Public Safety Inc. & City of Torrance
SaaS Agreement #
Exhibit C.7 – RMS Minimum Client and Peripheral Specifications

Page 3 of 8 ends

This document identifies the minimum client and peripheral specifications to be supplied by the City, to run the Application Software and adhere to the System Performance and Availability Standards specified in Section 7 of the Exhibit C- RMS SaaS Service Schedule.

The specifications included in this document are subject to change to support future Product Upgrades. When applicable, Versaterm will provide the City with updated specifications and recommendations.

OVERVIEW
342
Versaterm Public Safety Inc. & City of Torrance
SaaS Agreement #
Exhibit C.7 – RMS Minimum Client and Peripheral Specifications

Page 4 of 8 ends

The following provides the recommended workstation configurations:

Computer An IBM-compatible computer with full Windows Desktop Operating System (for desktop client installations)
Peripherals Mouse or pointing device, COMM port, USB ports Video 1200 x 800 resolution display monitor
Operating
System Microsoft Windows 7, 8.1, 10 (for desktop client installations) Memory 4 GB
CPU
Intel or AMD 2 GHz dual core processor
1 GHz or faster 64-bit (x64) processor
Hard Drive 60 GB
Network
Interface Card
(NIC)
100 mbps Ethernet network adaptor
Other Software
Adobe Acrobat Reader,
HTML5 supported browser (such as Microsoft Edge, Safari, Firefox, or Chrome). Note that Chrome is the primary browser used by Versaterm and the only browser officially certified.

Usage
• Versaterm Records Management System (RMS) desktop client installation • webRMS
• Other non-Versaterm installations (e.g. , Web browser, email, word processor, etc . ) 1 WORKSTATION RECOMMENDATIONS

1.1 RMS CLIENT COMPUTERS
343
Versaterm Public Safety Inc. & City of Torrance
SaaS Agreement #
Exhibit C.7 – RMS Minimum Client and Peripheral Specifications

Page 5 of 8 ends

Computer An IBM-compatible computer with full Windows Desktop Operating System Peripherals Mouse or pointing device, COMM port, USB ports Touchscreen recommended Video Minimum: 1024 x 768 resolution, 24-bit color depth.

MDT can be configured for displaying on non-standard screen aspect ratios.

Accelerated graphics card: 64 MB minimum / 256 MB recommended, Shader Model 2.0 minimum, latest drivers
Operating
System
Windows 7 SP1 - 32 and 64 bit,
Windows 8.1
Windows 10
Memory Recommended: 8 GB
CPU Recommended: I5 or i7 - 2.5 GHz
Hard Drive Recommended: 80 GB
Other Software HTML5 supported browser (such as Microsoft Edge, Safari, Firefox, or Chrome). Note that Chrome is the primary browser used by Versaterm and the only browser officially certified. .Net 4.5 Framework or higher
Windows Media Player for Audio
Usage
• Versaterm Mobile Data Terminal (MDT) installation (with the use of maps) • Versaterm Mobile Report Entry (MRE) installation
• webRMS
• Other non-Versaterm installations (e.g., Web browser, email, word processor, etc.)

1.2 MOBILE DATA COMPUTERS (WITH MAPS)
344
Versaterm Public Safety Inc. & City of Torrance
SaaS Agreement #
Exhibit C.7 – RMS Minimum Client and Peripheral Specifications

Page 6 of 8 ends

Device The vMobile application runs on Android and iOS.

Devices must meet the following operating system requirements to run vMobile 2.0 . • Android: version 12.0 or greater
• iOS: version 11.0 or greater
Additional requirements:
• VPN software to allow secure communications.
• Mobile Device Management software for deploying the application

1.3 VMOBILE
345
Versaterm Public Safety Inc. & City of Torrance
SaaS Agreement #
Exhibit C.7 – RMS Minimum Client and Peripheral Specifications

Page 7 of 8 ends

Description / Recommendation:
• Smart Label Printer 420 (USB) from Seiko Instruments (or equivalent) • Zebra LP2844 or TLP2844 (or equivalent)
Usage:

Bar code label printers are used in the Versaterm RMS Property sub-system to print bar code labels for in-custody items. They can also be used to print bar code labels for storage locations.

Note: Please refer to vConnect for the most up to date information on recommended property bar code label printers.
vConnect > Documentation and Downloads > Information Sheets > Bar Code Printing and Scanning Equipment
Description / Recommendation:
• Wasp WCS3900 CCD bar code scanner (corded)
• Zebra MC9300 (cordless)
• Bluetooth™-enabled scanner LS4278 with STB 4208 (cordless) Usage:

Bar code scanners are used in the Versaterm RMS Property sub-system to read bar codes, typically when performing property control and evidence continuity group transactions. They are used to facilitate the retrieval of item information by bar code number.

Note: Please refer to vConnect for the most up to date information on recommended property bar code scanners.
vConnect > Documentation and Downloads > Information Sheets > Bar Code Printing and Scanning Equipment
2 HARDWARE PERIPHERALS

2.1 PROPERTY BAR CODE LABEL PRINTERS

2.2 PROPERTY BAR CODE SCANNERS
346
Versaterm Public Safety Inc. & City of Torrance
SaaS Agreement #
Exhibit C.7 – RMS Minimum Client and Peripheral Specifications

Page 8 of 8 ends

Description / Recommendation:
• Code Reader 1400
• MagTek Mini (USB) Swipe Reader (or equivalent)
• MagTek Mini Port Powered RS-232
• L-Tron 3310 and 4810R
• ESeek M-250 and M-260 readers (or equivalent)
• Motorola DS457
Usage:

The Versaterm MRE and MDT support the use of both 2D and magnetic stripe readers to quickly enter person information. This is useful as users can perform quick person queries and prefill forms using driver’s license information.

Note: Please refer to vConnect for the most up to date information on recommended card swipe readers.
vConnect > Documentation and Downloads > Information Sheets > Card Scanner-Reader Support
Description / Recommendation:
• No specific hardware recommendation
Usage:

Modern networked scanners are recommended to scan paper documents (using the native software that the scanner comes with). The Versaterm browser-based vRMS attachment functionality browses for a file (.PDF preferred, to enable preview) on the MS Windows operating system. The located file(s) can then be attached to events, entities, detail pages, property, or narrative text within the vRMS.

Note:

Please refer to vConnect for detailed information on how connect to and configure your network scanners.

2.3 DRIVERS LICENSE CARD SWIPE READERS

2.4 DOCUMENT SCANNERS
347

Torrance City CouncilJune 23, 2026

Torrance City Council
June 23, 2026