HomeMy WebLinkAbout14 MOBILE DATA SYS 09-20-99AGENDA
NO 14
9-20-99
DATE:
SEPTEMBER 20, 1999
Inter-Com
TO:
FROM:
SUBJECT:
WILLIAM A. HUSTON, CITY MANAGER
POLICE DEPARTMENT
MOBILE DATA SYSTEM USER AGREEMENT
RECOMMENDATION
The council authorize the City Manager to sign the Mobile Data System User Agreement with
the City of Brea for continuation of this project.
FISCAL IMPACT
$130 dollars per month per mobile data terminal for the five-year term of the agreement plus
implementation costs.
BACKGROUND
In April 1998, ten cities as a consortium applied to the federal government for a COPS MORE
grant in the amount of $6.6 million dollars to fund the acquisition and deployment of the
equipment necessary to impl?..me~t a mobile data system for the member cities. This system
will allow police officers to obtain 'information in their vehicles through electronic transmission.
This will assist in the police officers being able to receive calls for service and other information
on their computer terminals within the car, as well as obtaining record check and vehicle
registration information and other data necessary to perform their day-to-day tasks while on
Patrol. This is another portion of and parallel to the 800 MHz Radio System which is currently
in the implementation stages.
At the time of the grant application process, the City of Tustin agreed to enter into a letter
agreement with the City of Brea for the services. One of the provisions of that agreement was
that participating cities would agree that if the grant were funded, the cities would enter into a
five-year agreement with the City of Brea for data backbone services. This is the agreement.
The ongoing costs of the system will be funded as an operating cost for the police department.
Funding for the acquisition of the equipment necessary on the local level to implement the
system will be through asset forfeiture.
William A. Huston, City Manager
September 20, 1999
Page 2
The City Attorney has reviewed the agreement and has approved the agreement as to form.
It is recommended that Council authorize the City Manager to execute this agreement and
continue this project.
STEVE FOSTER
Chief of Police
SF:mm
MOBILE DATA SYSTEM USER AGREEMENT
This Agreement, made and entered into this day of 1999, by and
between the City of Brea, a municipal corporation, hereinafter sometimes referred to as "Brea,"
·
and the City of Tustin, a municipal corporation, hereinafter sometimes referred to as "User," for
the use of the City of Brea Mobile Data System, hereinafter referred to as BreaMDS~
A. Recitals.
(i) The City of Brea has heretofore established a mobile data system for public
safety purposes employing a state-of-the-art data communications system
backbone that consists of data frequencies, computer switches and remote base
stations owned by the City of Brea.
(ii) The City of Brea has heretofore obtained all necessary licenses and has
constructed all facilities necessary for the provision of BreaMDS services.
(iii) The City of Brea has capacity on BreaMDS to accommodate other users and,
further, is willing to administer and implement system enhancements and provide
for maximum system performance.
(iv) The City of Tustin desires to become a user of BreaMDS, subject to the terms
and conditions.set forth in this Agreement.
B. Aqreement.
NOW, THEREFORE, it is hereby agreed by and between Brea and User as follows:
l. Brea hereby grants to User the right to utilize BreaMDS for a period of not less
than five (5) years, unless earlier terminated as provided herein.
2. In consideration 'of being permitted to use BreaMDS, User shall pay to Brea a
monthly sum of $130.00 per mobile data computer which monthly fee shall be
MOBILE DATA SYSTEM USER AGREEMENT 2
.
.
o
o
.
.
paid throughout the term of this Agreement, unless sooner terminated as
provided herein.
Use of BreaMDS by User shall be limited to no more than 45 mobile data
computers unless adjusted by mutual wdtten consent of Brea and User.
Furthermore, User may. be limited in the number of inbound and outbound
messages as dictated by overall system needs as determined solely by Brea.
Brea agrees throughout the term of this Agreement to implement system
enhancements and take all reasonable steps to ensure optimal system
performance as may be deemed necessary by Brea in its sole discretion,
including the issuance of system operating rules and regulations.
User agrees to fully comply with BreaMDS Operational Rules and Regulations,
Exhibit "A" hereto, as issued by, and as amended from time to time by Brea.
User participating in the BreaMDS 1998 COPS MORE technology grant shall
pay the monthly rate as set forth above, prepaid for the entire five- (5) year term,
upon being invoiced by Brea.
User, if participating in-the BreaMDS 1998 COPS MORE technology grant
agrees to fully comply with any and all grant program guidelines as may be
subsequently issUed and/or amended by Brea.
Term and Termination.
a. The term of this Agreement shall be five (5) years.
b.
C.
User shall have the right to terminate this Agreement only for
nonperformance as outlined in Section 8.c of this.Agreement.
Should any of the equipment necessary to operate the system become
unavailable or commercially infeasible to procure, or become
commercially infeasible to operate, or should Brea, for any reason, lose
MOBILE DATA SYSTEM dSER AGREEMENT
.
any license necessary to operate the system, or should User fail to
comply with any of the provisions of this Agreement, Brea shall be
authorized to terminate this Agreement upon thirty (30) days prior written
notice to User.
Performance Standards.
ao
bo
Brea guarantees that BreaMDS equipment utilized by Brea in
performance of this Agreement shall operate in accordance with its
manufacturer's .specifications. It is mutually agreed, however, that.
BreaMDS has been designed to provide 95% radio coverage in those
areas as set forth in radio coverage maps contained in the Motorola
Proposal to City of Brea for an Enhanced Mobile Data Communications
System. As such, Brea cannot guarantee radio coverage in any
particular circumstances. In the event of a lack of coverage suffered by
User, Brea agrees to.informally interface between User and Motorola to
effect necessary and available modifications provided such modifications
are deemed necessary by Brea and require no financial expenditure by
Brea.
Brea guarantees that system will be functional and available 24 hours a
day, 7 days a week, no less than 98% of the time during any calendar
month, not including downtime for routine maintenance. If, at any time,
BreaMDS fails to perform as set forth above, upon receipt of written
notiCe, by mail or fax, of such deficiency, Brea agrees to take the
following remedial steps:
1) Brea will respond within one (1) hour of such notification by
advising User as 'to the remedial steps it shall take. To the extent
MOBILE DATA SYSTEM USER AGREEMENT 4
possible, Brea shall immediately commence to correct such
deficiency. If Brea is unable to correct the reported problem, Brea
shall, as soon as is practical, advise the manufacturer of the
reported deficiency. Brea shall obtain a schedule for repair from
the manufacturer that shall be immediately provided to User.
2) In the event the remedial work proposed to be performed by the
manufacturer is determined by Brea to be insufficient under
Brea's agreement with the. manufacturer, either as to the
proposed time of repair or scope of repair, Brea shall immediately
pursue any and all remedies available under its agreement:with
the manufacturer.
c. During any periods of repair pursuant to subsection B, above, User shall
be entitled to the following monthly fee adjustments:
1)
Major System Failure.
In the event BreaMDS malfunctions so as to completely prevent
User's use of system in any manner ("Major System Failure"),
User shall be entitled to a 100% reduction of its monthly User fee,
on a per-hour, prorated basis, in accordance with the following
formula:
mf
md(24) x hrs = $.
to be deducted from monthly User
fee.
VVhere mf = total monthly fee
md= total days in month
MOBILE DATA SYSTE,.. riSER AGREEMENT 5
hrs = total number of whole hours of Major (or Minor--see below)
System Failure.
2) Minor System Failure.
-In the event the BreaMDS continues.to operate, but fails to
perform in accordance with the manufacturer's specifications
("Minor System Failure"), User shall be entitled to up to a 50%
reduction of its monthly use fee, on a per-hour, prorated basis in
accordance with the following formula:
mf
md(24) x hours + 2 = $.
to be deducted from monthly
3)
User fee.
In the event of a Major or Minor System Failure, User may present
Brea with its written documentation setting forth the dates and
times of such purported failure(s) and a request for deduction.
Upon confirmation by Brea, Brea shall authorize User to deduct a
specified amount from the next monthly User fee, in accordance
with the formulas set forth above.
4) In the event a Major System Failure continues for fourteen (14)
10.
11.
consecutive days, User may terminate this Agreement.
User agrees to comply with an~-and all applicable state and federal laws and
regulations while using BreaMDS.
At User's request, Brea will provide User with a detailed quarterly report showing
average, minimum and maximum acknowledge items, and the number of
inbound and outbound messages. The report will also include a recap of overall
system performance with the same information set forth above.
MOBILE DATA SYSTEM USER AGREEMENT
12.
14.
15.
Throughout the term of this Agreement, User shall be entitled to participate in
BreaMDS User' Group. The vadous goals, benefits and privileges of the
BreaMDS User Group are set forth in the BreaMDS User Group Statement of
Purpose, Exhibit "B" hereto.
By. entering into this Agreement, User shall be entitled to utilize BreaMDS as
specified herein. User expressly acknowledges and agrees that under no
circumstances shall User be deemed to have acquired any possessory or
ownership interest of any nature, whether tangible or intangible, as to any part of
BreaMDS, or any equipment or facilities thereof, regardless of amounts paid by
User to Brea pursuant to this Agreement (even if to enhance performance), or
the total duration of User's status as a "user" of BreaMDS, or otherwise.
User hereby agrees to indemnify, defend, and hold free and harmless the City of
Brea, its elected officials, officers, agents, employees and volunteers, from and
against any and all claims, liability or actions for damages to property or for injury
Or death of any persons, which arise from User's use of BreaMDS. User
acknowledges that Brea's role in the performance of this Agreement is as a
system operator and, as such, takes no active role in User's law enforcement or
other safety-related activities or communications. Based thereon, Brea shall not
be liable to User for indemnity or otherwise, including personal injury or property
damage, arising out of any failure of BreaMDS to properly perform, except as
may otherwise be provided by law.
Any notices required or permitted to be given by the terms of this Agreement, or
by any law or statute, may be' given by a party by depositing said notice in the
U.S. mail, postage prepaid, addressed to the other party, at the address of the
MOBILE DATA SYSTEt,. JSER AGREEMENT 7
party's respective City Hall. Service of said notice should be deemed complete
five (5) days after deposit of said notice in the mail.
16.
This Agreement shall constitute the entire Agreement between Brea and User
with respect to the matters herein, and the same shall be deemed to supersede
any and all other oral or written representations or agreements which may have
been entered into between Brea and User.
17. No modification or amendment to this Agreement shall be deemed effective
18.
unless the same is in writing and executed by Brea and User.
This Agreement may be executed in any number of counterparts, each of which
shall, for all purposes, be deemed an original, and all of which shall constitute
one and the same Agreement of Brea and User.
19.
User shall not assign or attempt to transfer any rights that it might-have which
adse from this Agreement, without the pdor wdtten consent of Brea.
20.
Force Majeure.
Under. no circumstances will Brea be responsible for delays or failUres of
performance of its obligations under this Agreement that are the result of events
beyond the reasonable control of Brea. Such events include, but are not limited
to, acts of God, weather conditions, enactment of state or federal legislation
prohibiting Brea's performance or rendering it commercially impracticable, fire,
strikes, lockouts or other labor disruptions, riots, acts of war or earthquakes.
MOBILE DATA SYSTEM USER AGREEMENT
IN WITNESS WHEREOF, the parties hereto have caused this Agreement to be
executed as of the day and year first set forth above.
CITY OF BREA
By:
Tim O'Donnell, Assistant City Manager
CITY OF TUSTIN
By:
APPROVED AS TO ~DRM:
'
LOIS E. ~
city Attorn~
j:MDScontracts~MDS user agrmt-grantcity 4-99
EXHIBIT "B.
BREAMDS USER GROUP
Goal of the User Group
To provide users a forum which encoUrages dialogue to express
ongoing needs and issues. '
By regularly bdnging users together as a group, we have an opportunity
to gauge user satisfaction and know that the system is meeting
everyone's needs, and which changes (technical or operational) are
necessary for continued success.
Benefits
There are many benefits to a user group *besides
encouraging communication, including:
simply
As the service provider, Brea is much better able to support individual
agencies if the User Group is a forum for openly discussing system-wide
issues, problems and needs.
Users will establish contacts in other agencies who are working on similar
projects or have similar responsibilities.
User Group meeting attendees will hear others' discoveries and success
stories. This builds enthusiasm and provides a source of new solutions
and ideas which will benefit everyone involved in the system.
Users will become more confident in their ability to use the system as a
resource, not only because they're better inf°rmed, but because they
know they're not alonc they have Brea's and all of the other client cities
support.
Objectives
The User Group should focus on resolving needs and issues.
The User Group will give BreaMDS users a sense of contribution to the
system through active participation in meeting discussions and reviews.
Through continued participation and input, users will feel more "in
control" of what is happening on the system.
The User Group should periodically review performance and
operating standards to ensure ongoing needs are being meL
The User Group can be responsible for reviewing system performance
reports generated by Brea to'determine whether standards continue to
be adequate and propedy honored.
City of Brea's Charter
Problem reporting system
As BreaMDS is further expanded and enhanced, the User Group will be
invited to assist Brea in developing a problem reporting system to
report, track and resolve problems/issues on the system. Early ideas
for such a system include using an electronic bulletin board or fax forms.
Quarterly customer service review
Brea will review customer service issues with. the User Group on a
quarterly basis. Discussion topics can include timeliness of responses
and reports, accessibility and responsiveness of Brea staff, and problem
reporting system effectiveness.
Quarterly system performance reporting
Brea will generate a quarterly set of reports that detail ongoing system
performance with respect to agreed-upon standards.
Annual system performance review
Each year, Brea will review system performance standards issues with
the User Group. This is an opportunity to discuss whether developed
system performance standards are being adequately observed and are
meeting individual agency needs. Users can report on the results of
individual coverage tests performed annually by each agency.
Long-range strategic planning
The User Group will be invited, to participate in periodic strategic
planning sessions to determine long-range system goals and objectives.
BreaMDS modification reviews.
The User Group will be responsible to provide input to Brea regarding
how new BreaMDS clients, changes by existing users, or system
enhancements will be accommodated and implemented. These
meetings will be held on an as-needed basis.
Exhibit "A"
USER MANUAL
RESOURCE GUIDE FOR BreaMDS
POLICIES AND PROCEDURES
BreaMDS
TABLE OF CONTENTS
INTRODUCTION ............................................................................................ 3
TECHNICAL SUPPORT PROCEDURES .............................................................. 3
GENERAL ............................................................................................ 3
BreaMDS COORDINATOR ............................................................ 3
PRIORITIZATION OF SERVICE REQUESTS ............................................... 4
CONFIRMATION OF COMPLETED SERVICE REQUESTS ............................ 5
BreaMDS TECHNICAL SUPPORT HOTLINE .............................................. 5
STANDARD HOURS OF OPERATION ............................................. 5
BreaMDS TECHNICAL SUPPORT HOTLINE ..................................... 5
BreaMDS TECHNICAL SUPPORT FAX ..................... ~ ...................... 5
ROUTINE TECHNICAL SUPPORT .................................... ~ ................... '.... 5
AFTER-HOURS TECHNICAL SUPPORT. ................................................... 5
BreaMDS USER GROUP ' 6
REPORTS ..................................................................................................... 6
STANDARD BreaMDS REPORTS .; .......................................................... 6
CUSTOM BreaMDS REPORTS ................................................................ 6
FORMS ........................................................................................................ 7
BreaMDS SITE CONTACT DECLARATION ............................................... 8
OPERATOR I.D. MODIFICATION REQUEST .............................................. 9
CALL I.D. MODIFICATION REQUEST .................'. ................ ~ .............. ..... 10
TECHNICAL SERVICE REQUEST ................................................ , .......... 1 1
GLOSSARY ............ -. ..................................................................................... 12
BreaMDS SYSTEM TOPOLOGY ...................................................................... 1 3
BREAMDS 2
INTRODUCTION:
This User Guide has been developed to assist Brea Mobile Data System
(BreaMDS) users when requesting services from the BreaMDS Coordinators,
the City of Brea. The City of Brea is committed to providing timely, quality
customer service to the clients of the Brea Mobile Data System.
The BreaMDS system is an advanced integration of computers and radio
transmitters that allow emergency services vehicles to communicate with
dispatch centers, records centers and other emergency services vehicles
while in the field. The BreaMDS system accesses confidential information
from the State of California, the California Department of Motor Vehicles and
the U.S. Department of Justice. All users of this system are expected to
comply with any and all relevant Federal and State rules and regulations
while operating this system.
TECHNICAL SUPPORT PROCEDURES:
GENERAL: The Brea Mobile Data 'System is administered by the
Information Technology Division (Brea IT) of the City of Brea. Brea IT strives'
to provide quality technical support for BreaMDS users twenty,four hours a
day, seven, days a week. Requests for technical support fall into two general
categories - Routine and After-hours. Routine support is available during the
City of Brea's standard hours of operation. After-hours support is available
at any time outside of the City's standard hours of operation..
All technical support requests must be submitted in writing by an authorized
BreaMDS Site Contact to a BreaMDS C~3ordinator. To expedite handling,
please submit technical service requests on the fully-completed forms.
These forms are provided at the end of this user guide. Written requests can
be submitted by FAX to the number listed below or mailed to the following
address:
Attn.: BreaMDS Coordinator'
City of Brea
One Civic Center Circle
Brea, CA 92821
Fax: 714-671-3617
BREAMDS 3
PRIORITIZATION OF SERVICE REQUESTS: All service requests
received by a BreaMD$ Coordinator must include a priority code which will
help the BreaMDS Coordinator categorized and prioritize the service requests
from all jurisdictions. If a service request has not been assigned a priority or
has been assigned an incorrect priority, a BreaMDS System Administrator will
assign one. Please use the following scale to prioritize all service requests
before submitting them to a BreaMDS Coordinator:
Priority Criticality Description
I Critical
An example of a priority 1 service request is:
a system down condition. Priority 1 service
request should be addressed immediately.
Note: Please call the BreaMDS Technical Support
Hotline immediately with priority 1 service
requests. Follow with a FAX of the request to the
BreaMDS Technical Support FAX.
2 Urgent
An example of a priority 2 service request is:
a specific individual unable to Iogon to the
BreaMDS. Priority 2 service requests should be
addressed within one (1) business day.
3 High
An example of a priority 3 service request is: any
changes to Site Contact, Operator or Call I.D.
numbers. Priority 3 service requests should be
addressed within five (5) days business days.
4 Medium
An example of a priority 4 service request is: a
request for copies of pre-defined reports or the
development of custom reports. PriOrity 4 service
requests should be addressed within ten (10)
business days.
5' Low
An example of a priority 5 service request is: a
request for general information about equipment or
accessories. Priority 5 service requests will be
addressed as time permits.
!n addition to assigning a priority number to each service request, the
BreaMDS Site Contact is asked to designate a reasonable 'Date Desired'. A
BreaMDS Coordinator will attempt to have the service request completed by
the "Date Desired', but cannot make a guarantee of completion date.
Quantity of service requests and difficulty of tasks has a direct effect on the
actual completion date of a service request. Service requests which have a
BREAMDS 4
~Date Desired' of A.S.A.P. will be assigned a optimum date by a BreaMDS
Coordinator.
CONFIRMATION OF COMPLETED SERVICE REQUESTS: All
technical service requests submitted will be resolved as quickly as possible.
To help the BreaMDS Coordinators and a jurisdiction keep track of completed
service requests, the BreaMDS Coordinator will, upon completion, return the
service request to the jurisdiction. The BreaMDS coordinator will also fill in
the 'Date Completed' and any appropriate 'Comments' on the form before
mailing or faxing the service request back to the jurisdiction.
BreaMDS TECHNICAL SUPPORT HOTLINE: A BreaMDS Technical
Support Hotline is available'twenty-four hours a day, seven days a week.
Calls to the BreaMDS Technical Support Hotline should be made by a
jurisdiction's BreaMDS Site Contact. The BreaMDS Site Contact is
requested to verify, prioritize and have full details of the service request or.
incident prior to placing a call for technical support. Technical support hours
and phone numbers are listed 'below.
Standard Hours of Operation: 7:30 a.m. - 5:30 p.m.,
Thursday
8:00a.m. - 5:00p.m., Alternate Fridays (Closed
Friday)
Monday -
every other
BreaBreaMDS Technical Support Hotline: 714-990-7779 (24 hours)
BreaBreaMDS Technical Support Fax: ' 714-671-3617 (24 hours)
Reminder: Ail technical support ca/Is must be followed up by a written
request to ensure proper resolution of your issue.
ROUTINE TECHNICAL SUPPORT: Routine technical support is available
during Standard Hours of Operation by FAXING' a service request to the
BreaMDS Technical Support Fax or by calling the BreaMDS Technical
Support Hotline. Routine support comprises general questions, modifications
to a jurisdiction's authorized users and emergency support in the event of a
MDC or system failure. Calls for routine technical support will be placed into
the BreaMDS service request pool and resolved in the order they are
~eceived.
AFTER-HOURS TECHNICAL SUPPORT: After-hours technical support
'comprises emergency support in the event of a BreaMDS system failure only.
After-hours technical support is defined as technical support requested
outside the Standard Hours of Operation. This support is' available by calling
the BreaMDS Technical Support Hotline and leaving a voice mail message.
The voice mail message will automatically page a technician to assist you. All
other technical support calls will be referred to routine technical support
BREAMDS 5
Brea ;
during the Standard Hours of Operation.
BreaMDS USER GROUP:
A BreaMDS User Group will meet regularly to provide a forum to encourage
dialogue, exchange ideas and express on-going needs and issues. There are
several benefits to our BreaMDS User Group. First, the BreaMDS.
Coordinators will be much better able to support individual jurisdictions if the
User Group is a forum for openly discussing system-wide issues, problems
and needs. Second, users will establish contacts in other jurisdictions who
are working on similar projects or have similar responsibilities. Third, 'User
Group attendees will hear others discoveries and success stories. This
provides a source of new solutions and ideas which will benefit everyone
involved, in the system.
REPORTS:
SYSTEM STATISTICS REPORT: The System Statistics Report
will 'be available on a quarterly basis to all jurisdictions. This report will track
vital statistics on BreaMDS system performance. Items that may be included
are total system radio requests., average response time per radio request,
average system radio usage by hour, total radio requests by jurisdiction, total
service requests, total service requests by jurisdiction, and average response
time per service request.
STANDARD BreaMDS REPORTS: Several standard BreaMDS reports
will be available on the BreaMDS system.. These reports will be available to
all jurisdictions at no additional charge. The format of these reports has yet
to be determined. Report formats that are determined to be beneficial to all-
jurisdictions will be considered for inclusion in the standard BreaMDS
reports pool.
CUSTOM BreaMDS REPORTS: A jurisdiction can request customize
BreaMDS reports from a BreaMDS CoordinatOr. Each jurisdiction can
request one (1) customized BreaMDS report per calendar year at no
'additional charge. Customized BreaMDS reports requests should be
submitted'to a BreaMDS Coordinator on a Technical Service Request form
(provided at the end of this user's guide) and should include a proposed
report layout and report sorting preference. Each additional request for a
customized BreaMOS report can be developed at a cost to the requesting
BREAMDS 6
Brea ;
jurisdiction. A BreaMDS Coordinator shall provide a dollar quote to the
requesting' jurisdiction within 'seven (7) working days of receiving the
request.
Customized BreaMDS reports will be avail.able to the funding jurisdiction at
no additional charge. Other jurisdictions wishing to utilize a customized
BreaMDS report format will be charged any' additional costs associated with
customizing this report for their agency. Multiple agencies may join together
to share the development cost of any custom report. If it is determined to be
of value to all agencies by the User Group, the report v~ill become part of the
standard BreaMDS reports pool.
FORMS:
Several forms are provided on the following pages to simplify requesting
services from a BreaMDS Coordinator.
The BreaMDS Site Contact Declaration should be used to inform our
BreaMDS Coordinators who the authorized BreaMDS Site Contacts are for a
jurisdiction.
The Operator I.D. Modification Request should be used to submit lists of
Operators to be added or deleted from the Brea Mobile Data System.
The Call I.D. Modification Request should be used to submit lists of valid Call
I.D.'s to a BreaMDS Coordinator.
The Technical Service Request Should be used to submit all other service
requests not covered by the BreaMDS Site Contact Declaration, the Operator
i.D. Mod/f/cat/on Request or the Ca//i.D. Mod/f/cat/on Request.
BREAMDS 7
BREA MOBILE DATA SYSTEM
BreaMDS SITE CONTACT DECLARATION'
P/ease fill in all NON-Shaded areas and submit via mail or fax.
Jurisdiction: Priority: 2
Date Requested:
Date Desired'
Chief of Police: Phone'
or Fire Chief:
I hereby declare the following persons to be the primary and secondary BreaMDS Site
Contact
persons for the City of
Primary BreaMDS Site Contact:
Secondary BreaMDS Site Contact:
Phone'
Phone'
Secondary BreaMDS Site Contact:
Phone:
' BREA MOBILE DA TA SYSTEM
BREA MOBILE DATA SYSTEM
OPERATOR I.D. MODIFICATION REQUEST
Please fill in all NON-Shaded areas and submit via mail or fax.
JurisdictiOn: Priority:
Date Requested:
Date Desired'
BreaMDS Site Contact:
Phone:
u
MDC Operator I.D. 's must be unique within a jurisdiction
MDC Operator I.D. (Last Name, First Name) Password Add/Delete
BREA MOBILE DA TA SYSTEM
8REA MOBILE DATA SYSTEM
CALL I.D. MODIFICATION REQUEST
P/ease fill in ail NON-Shaded areas and submit via mail or fax.
Jurisdiction:
Date Requested:
Date Desired:.
BreaMDS Site Contact:
Priority:
Phone:
Call I.D.
MDC Call I.D. 's must be unique within a jurisdiction
Call I.D. Call I.D.
BREA MOBILE DA TA SYSTEM
BREA MOBILE DATA SYSTEM
TECHNICAL SERVICE REQUEST
Please fill in all NON-Shaded areas and submit via mail or fax.
Jurisdiction: Priority:
Date Requested:
Date Desired:
BreaMDS Site Contact:
Phone:
Description of Request:
(Please include any supporting documentation)
~, · ~ ..... ..~: :::~:~ ~;~ .~ · · ~ . ~.: ..~:~: .~ ..~ .... .. ~..~: :,.~. ~: · ,~? ~-.:~:*:~:~:~ .~.~:~ : .: : ~ ~: ~:*~.~: ~.~.~ ~ ~ .~ ~? ~'~ ~: ~, ~.:.~:'~* ~*~;' ~ ~?~:~ ~.~:.~.:.
~:~;~::~;~::~?~'~..~:~:~.;-;~.~:~:~::;...::::.~::~..::~;~.::~ ;;~::?~::;~::~.:~ :::,~; ;:.::..:.:~.:~;~...: ..::::.-,:~ ....... ~. ; ...... : =:~ ...... , ~ :~ ..... ~.,~.;;.:..~;:;. : ~*.~
~..:'~:~':~ ~::~. ~?~ .~ ':.:: ...?.* ~;;. <c ,: ~?~.: ::;~ .: ~?'::,:: ~.: :' .. ~:.::. ..... ~; ,?' ~g~ :%: ~ :':;: -:: · ~ :::.: ':?~: ~'.': .... '. ~.:;. ~: ~... :. ~ * ....... :'~: .:..:. ~ ..... : ,: ,~?. :~ ~: ~:~:~ ~';:.~::?::.. ;.~:~ ::~ :;:. ::~: ::; ' ....
........... ........ ~':"" ...... : ...... :':' ':?: : ....... ~ ; ::':. ;: :":;'~;'~:': :~ '~:: ;::'~ :~:'~: ': ::;~;:;~;:':~ ~:: :: .:~::'~:;' '; ' ~ · ' ";:': ·: ~ ;': :. :: ':~ .". ::?:. ~:'~:;: ::.: ~::~;;'~.:?::~: :~:;{,~'. :~':~ ;~::T.::::~:: ;:'~'?:~: ':~:~:~'~:~:~:::~: ~;'~x:'~:-
BREA MOBILE DA TA SYSTEM
GLOSSARY:
This section defines terms that are specific to the Mobile Data System. If other terms are
encountered that are unfamiliar, please contact the BreaMDS Technical SuPport Hotline
for clarification.
CAD
ComPuter Aided --Dispatch. CAD is a 'compUter used by jurisdictions to
dispatch emergency services vehicles to an incident.
CLETS California _Law Enforcement Telecommunications System.
KDT
Keyboard Data Terminal. The Motorola mOdel 480 computer terminal
located within an emergency services vehicle. Sometimes referred to
as an MDT or MDC.
BreaMDS Mobile -Data System. The
network.
entire radio/computer
communications
BreaMDS Coordinator The City of Brea's BreaMDS technician(s).
BreaMDS Site Contact THe person assigned by each jurisdiction to be responsible for
communicating between the jurisdiction and the City of Brea for
questions and requests.
MDC
Mobile _Data Computer. The Motorola
within an emergency response vehicle.
KDT or MDT.
computer terminal located
Sometimes referred to aS a
MDT
Mobile Data Terminal. The Motorola model 9100-386 computer
terminal .located within an emergency response vehicle. Sometimes
referred to as an MDC or KDT.
NLETS
National Law Enforcement Telecommunications System.
PDT
RNC
RBS
Portable -Data Terminal. A hand-held Motorola computer terminal.
Radio Network Controller. The 'central computer in the BreaMDS
system. The RNC controls the routing of messages between the host
computer (X2000) and emergency'response vehicles.
_Radio BaSe S_tation. The equipment that sends and receives signals
between emergency response vehicles and the RNC.
RMS
Records Management S_ystem. RMS is a computer used by
jurisdictions to record incident information.
BREA MOBILE DA TA SYSTEM
Brea? ; '
X2000
The BreaMDS message switching computer. The X2000 allows host
computers to connect to the radio network via the RNC.
BreaMD$ SYSTEM TOPOLOGY:
The following topology map illustrates how the BreaMDS system works. An MDC located
in an emergency services vehicle sends a request for information. The request is
transmitted from the MDC to the vehicle's radio controller, the vehicle's radio controller
transmits the request to an RBS which, in turn, transmits the request to the RNC via a
telephone connection. The RNC transmits the request to the X2000 computer which
processes the request and then routes a response back the way it came.
(See BreaMDS system topology on the following page)
BREA MOBILE DA TA SYSTEM
LETTER OF AGREE.~fENT
Th.is Letter of Ag'reement stands as evidence that if the COPS MORE ~m-ant is funded.
the following cities ag-tee to participate in the grant as a consortium with the Ci~' of
Brea. California. acting as the lead applicant agency. The cities ag-ree that the __ox-ant is
to provide funding for an enhanced backbone for BreaMDS and specified services and
equipment to the cities. The California cities a~eeing to participate include:
CiD' of Brea Cit3.' of Buena Park City of Cypress
Cir' of Placentia City of Newport Beach City of Seal Beach
Cir' of Downey Ci~' of Los A3amitos City. of Tustin
Ci~' of La Palina
o
Se~-ices to be obtained through the gu'ant include'
· Obtain a second 806 ..MHz frequency for use by Break,IDS as a data channel
· Purchase equipment to implement the new frequency using RD-L.-KP 19.2
protocol
· Mig-rate all users to the new frequency
· Rebuild the backbone of the original frequency to RD-LAP 19.2
· Implement a fully redundant, dual channel system
· Purchase all necessary end-user equipment including fL, ced. portable or
mobile MDC's with associated software
· Purchase other grant funded hardware and softxvare for various participating
cities
Participating cities a~ee that if the ~m-ant to accomplish the above is funded, they v-ii1
enter into or renew 5-year a~eements with the Ci~' of Brea for data backbone services.
which, for charter member Cities, includes a reduction in rate. Cities also agree to pay
a portion of _ma.ut writing fees related to the value of equipment, software and services
directly received, and for system backbone enhancements in proportion to their agency
size. Additionally. Cities agree to cooperate with ~m-ant writers in finding eligible
matching funds for the project within existing Ci~' budgets.
This letter agreement shall be null and void in the event the COPS MORE __m-ant
referred to above is not funded.
LETTER OF AGREEM'ENT Page 2
Frank Benest. City Manager
.-%oencv: Citw of Placentia
We. the undersigned, as authorized representatives of the participating cities, do hereby
approve this document.
Aeencv:Citv of Brea ~~
Robert D'Amam. City Mana.qer
A~oencv: City of Buena Park
David Berger. CiD- Manager
A~oencv: Citw of Cypress
Mark Ochenduszko. City .Manao_er
A,,encv: Citw of Downey
Gerald 5t. Caxon. City Mana_oer
Aeencv: City of Newport Beach
KeVin Murphy. CiD' Manager
Aeenc,;': CRv of Los .Mamitos
Robert C. DominEuez. CiD' Manager
Aeencv: CRv of Tustin
William Huston. CiD' Manager
Aeencv: CRv of Seal Beach
Keith Till, CiD' Manager
Aeencv: CRv of La Palina
Daniel Keen. City. Manager
Date
Date
Date
Simaamre
Sienamre
~~e Date
Si~e ~ D~e
Si~~e ~/~ Datl
~Si~ ' ' . ~ Dam
Dat~
Si~~e
Si~~e I Date
July 20, 1999
I'-! .'i I -'1
GA I. IFOR N IA
City of Brea
Chief Steve Foster
City of Tustin Police Department
300 Centennial Way
Tustin, CA 92780
Dear Chief Foster:
At the time of the '98 COPS MORE grant application process, the City of Tustin entered
into a Letter of Agreernent with the City of Brea for Brea MD$ services. One of the
provisions of that Agreement states, "Participating cities agree that if the grant to
accomplish the above is funded, they will enter into or renew 5-year agreements with the
City of Brea for data backbone services..."
Enclosed are two copies of the Mobile Data System User Agreement for Brea MD$
services referenced in the Letter of Agreement. A copy of the Letter Agreement is also
enclosed for your reference. Please have your City Manager sign both copies of the
Mobile Data System User Agreement and return one to me as soon as possible.
I appreciate your prompt attention to this matter. Should you have any questions, please
feel free to call me at (714) 990-7770.
Sincerely,
Tim O'Donnell
Assistant City Manager
cc: Capt. Fred Wakefield
TO:r/transmittal letter
Attachments
City Council Mart), Simonoff Bev Perry Lynn Daucher Roy Moore Steve Vargas
Mayor Mayor Pro Tem Councihnember Councilrnernber Councilrnernber
Civic & Cultural Center · 1 Civic Center Circle · Brea, California 92821-5732 · 714/990-7600 · FAX 714/990-2258