HomeMy WebLinkAboutCC Resolution 11043 (Computer Aided Dispatch, Record Mgmt., Mobile Computing)(a)
RESOLUTION NO. 11043
RESOLUTION OF THE SAN RAFAEL CITY COUNCIL AWARDING
CONTRACT FOR COMPUTER AIDED DISPATCH, RECORDS
MANAGEMENT, AND MOBILE COMPUTING SYSTEM SOFTWARE AND
SERVICES TO SUN RIDGE SYSTEMS, INC., IN THE AMOUNT OF $338,768
AND AUTHORIZING CITY MANAGER TO EXECUTE THE AGREEMENT.
Whereas, the City's Technology Strategic Plan includes the implementation of a
new Computer Aided Dispatch/Records Management System; and,
Whereas, on the 18th day of September, 2001, pursuant to due and legal notice
published in the manner provided by law, inviting sealed bids for proposals for
the products and services hereinafter mentioned, as more fully appears from the
Affidavit of Publication thereof on file in the office of the City Clerk of the City of
San Rafael, California, the City Clerk of said City did publicly open, examine and
declare all sealed bids or proposals for financial system software application and
services in accordance with the cost proposal request (CPR) on file in the office
of said City Clerk; and
Whereas, the bid of Sun Ridge Systems Inc. in the amount of $338,768 was
and is the lowest and best bid for Police computer aided dispatch, records
management, and mobile computing and Fire computer aided dispatch software
and said bidder is the lowest responsible bidder therefor;
NOW, THEREFORE, IT IS HEREBY ORDERED AND RESOLVED that the bid
of Sun Ridge Systems, Inc., in the amount of $338,768, is hereby accepted and
included as part of the Agreement attached to and made part of this resolution
as Exhibit 1."
IT IS FURTHER ORDERED AND RESOLVED that the City Manager of said City
be authorized and directed to execute the Agreement with Sun Ridge Systems,
Inc. for said products and services, in the form attached hereto as Exhibit "I", in
the amount of $338,768.
BE IT FURTHER RESOLVED that the Assistant City Manager is hereby
authorized to take any and all such actions and make changes as may be
necessary to accomplish the purpose of this resolution, including approval of
modification of scope as provided in the Agreement in a total amount not to
exceed $20,000.
��0
(a)
I, JEANNE M. LEONCINI, Clerk of the City of San Rafael, hereby certify that the
foregoing resolution was duly and regularly introduced and adopted
at a regular meeting of the San Rafael City Council meeting held on
the eighteenth day of March, 2002 by the following vote, to wit:
AYES: COUNCILMEMBERS: Cohen, Heller, Miller, Phillips & Mayor Boro
NOES: COUNCILMEMBERS: None
ABSENT: COUNCILMEMBERS: None
JEA RE M. LEON INI, City Clerk
APPLICATON SOFTWARE LICENSE AND USE AGREEMENT
by and between
City of San Rafael
and
Sun Ridge Systems, Inc.
pursuant to
Public Safety Information System Cost Proposal Request of September 18, 2001
March 18, 2002
Exhibit "I"
CITY OF SAN RAFAEL SUN RIDGE SYSTEMS, INC.
MARCH 18. 2002 APPLICATION SOFTWARE LICENSE/USE AGREEMENT
TABLE OF CONTENTS
1.00 DEFINITIONS AND INTRODUCTORY PROVISIONS.............................................5
1.01 DEFINITION OF TERMS......................................................................................................................5
1.02 TERM........................................................................................................................................................7
1.03 INCLUDED DOCUMENTS....................................................................................................................7
1.04 SUBCONTRACTORS.............................................................................................................................7
1.05 EFFECTIVE DATE.................................................................................................................................8
2.00
PROPERTY RIGHTS.......................................................................................................8
2.01
WARRANTY OF OWNERSHIP/RIGHT TO SELL SOFTWARE....................................................8
2.02
HOLD HARMLESS AND INDEMNIFICATION-SOFTWARE.........................................................8
2.03
COPYRIGHT NOTICE...........................................................................................................................8
2.04
ACKNOWLEDGMENT OF NO ENHANCEMENT RIGHT..............................................................8
3.00 PROPRIETARY AND TRADE SECRET INFORMATION........................................8
3.01 CUSTOMER'S PROTECTION OF LICENSED SOFTWARE...........................................................8
3.02 DESIGNATION OF CONFIDENTIALITY..........................................................................................9
3.03 CUSTOMER'S RIGHTS TO COPY LICENSED SOFTWARE.........................................................9
4.00
LICENSE GRANT.............................................................................................................9
4.01
SCOPE OF LICENSE..............................................................................................................................9
4.02
RISK OF LOSS OF LICENSED SOFTWARE AND DOCUMENTATION....................................10
4.03
DOCUMENTATION.............................................................................................................................10
4.04
SCOPE OF SERVICES.........................................................................................................................10
4.05
SITE OF SERVICES..............................................................................................................................10
4.06
MODIFICATION OF SCOPE..............................................................................................................10
5.00 PROGRAM SUPPORT SERVICES..............................................................................11
5.01 LICENSED SOFTWARE AND DOCUMENTATION TRAINING..................................................11
Sun Ridge Systems, Software License Agreement Page 2 of 24
CITY OF SAN RAFAEL SUN RIDGE SYSTEMS, INC.
MARCH 18, 2002 APPLICATION SOFTWARE UCENSE/USE AGREEMENT
5.02 TRAINING..............................................................................................................................................12
5.03 LICENSED SOFTWARE AND DOCUMENTATION SUPPORT AND ENHANCEMENTS ....... 12
5.04 LICENSED SOFTWARE SUPPORT SERVICES..............................................................................13
5.05 LICENSED SOFTWARE MAINTENANCE.......................................................................................14
5.06 ON-SITE ASSISTANCE........................................................................................................................14
5.07 TRAINING FOR ENHANCEMENTS.................................................................................................14
5.08 ANNUAL LICENSED SOFTWARE MAINTENANCE AND SUPPORT FEE INCREASES .......14
5.09 PLATFORM PROTECTION................................................................................................................15
5.10 TERMINATION OF SUPPORT...........................................................................................................15
5.11 CUSTOMER RESPONSIBILITIES FOR SUPPORT........................................................................15
5.12 SUPPORT LIMITATIONS...................................................................................................................15
6.00 INSTALLATION, DELIVERY, AND ACCEPTANCE..............................................16
6.01 DELIVERY.............................................................................................................................................16
6.02 ACCEPTANCE AND PAYMENT........................................................................................................16
6.03 PPLICABLE TAXES.............................................................................................................................18
6.04 ADDITIONAL CHARGES....................................................................................................................18
7.00 CUSTOMER RESPONSIBILITIES..............................................................................18
7.01 CUSTOMER SUPPORT OF VENDOR...............................................................................................18
8.00 WARRANTY OF PERFORMANCE............................................................................19
8.01 COMPLIANCE WITH STATE AND FEDERAL REPORTING REQUIREMENTS ......................19
8.02 WARRANTY OF PERFORMANCE...................................................................................................19
8.03 YEAR 2000 COMPATIBILITY............................................................................................................20
8.04 CORRECTION OF ERRORS UNDER THE WARRANTY.............................................................20
8.05 ORAL REPRESENTATIONS...............................................................................................................20
8.06 PROGRESS REPORTS.........................................................................................................................20
8.07 NO DISABLING CODE........................................................................................................................20
9.00 LIABILITY, INDEMNIFICATION AND DEFAULT................................................21
Sun Ridge Systems, Software License Agreement Page 3 of 24
CITY OF SAN RAFAEL SUN RIDGE SYSTEMS, INC.
MARCH 18, 2002 APPLICATION SOFTWARE LICENSE/USE AGREEMENT
9.01 LIABILITY, INDEMNIFICATION AND DEFAULT........................................................................21
9.02 BANKRUPTCY/SUPPORT CESSATION..........................................................................................21
9.03 INSURANCE..........................................................................................................................................21
9.04 LIMITATION OF LIABILITY............................................................................................................22
10.00 GENERAL PROVISIONS..........................................................................................22
10.01 ASSIGNMENT.......................................................................................................................................22
10.02 GOVERNING LAW...............................................................................................................................22
10.03 ENTIRE AGREEMENT/AMENDMENTS..........................................................................................23
10.04 CONSTRUCTION..................................................................................................................................23
10.05 SERVICE OF NOTICE.........................................................................................................................23
10.06 BUSINESS LICENSE............................................................................................................................23
SIGNATURES: ............................................................................................................................ 24
Sun Ridge Systems, Software License Agreement Page 4 of 24
CITY OF SAN RAFAEL SUN RIDGE SYSTEMS, INC.
MARCH 18. 2002 APPLICATION SOFTWARE LICENSE/USE AGREEMENT
This Agreement is entered into this 18th day of March, 2002 by and between City of San Rafael,
a California municipal corporation district located at:
P.O. Box 151560
San Rafael, CA 94915-1560
hereinafter sometimes referred to as `Customer' and Sun Ridge Systems, Inc., a California
corporation with offices located at:
PO Box 5071
El Dorado Hills, CA 95762
hereinafter sometimes referred to as `Vendor.'
1.00 DEFINITIONS AND INTRODUCTORY PROVISIONS
1.01 DEFINITION OF TERMS
The Customer and Vendor agree that within the limits of common usage, a word in a
contract means what the contract says it means.
For purposes of this Agreement, the following are defined terms:
(a) The term "CPR' shall refer to the Customer's Public Safety Information System
Cost Proposal Request release on September 18, 2001. The term "Vendor's CPR
Response" shall mean the proposal response submitted by Vendor on October 10,
2001 including narratives and response forms RFO, RFI, RF2, RF3a, RF4 RF4a,
and RF5.
(b) The term "System" shall mean the Licensed Software and Documentation, and
software developed specifically under this Agreement to be delivered by the
Vendor in response to the Project Definition detailed herein.
(c) The term "Project System" shall include any and all computer code in both printed
and machine readable form developed or modified under the scope of this
Agreement, its translated or compiled version, and all specifications and other
written documentation (in printed or machine readable form) relating thereto as
well as any additional hardware, hardware component, or peripheral device directly
associated with the items covered by this Agreement.
(d) The term "Licensed Software" shall mean a licensed information processing
program or programs consisting of a series of instructions or statements which is
machine readable commonly referred to as "application software" for which a
license is purchased from a third party and is required in conjunction with the items
covered by this Agreement.
(e) The term "Documentation" shall mean any materials related to the Licensed
Software including, without limitations, user's guides, technical guides, training
Sun Ridge Systems, Software License Agreement Page 5 of 24
CITY OF SAN RAFAEL SUN RIDGE SYSTEMS, INC.
MARCH 18, 2002 APPLICATION SOFTWARE LICENSE/USE AGREEMENT
materials, Vendor guidelines and customer support instructions provided for use in
connection with the Licensed Software.
(f) The term "System Software" shall mean third party supplied Licensed Software and
Documentation that control hardware functions, commonly referred to as "operating
systems", and file management utilities, compilers and programming languages,
etc.
(g) The term "Functional Specifications" shall mean a written description of the
Customer's procedures that are to be automated by virtue of the Licensed Software
proposed by the Vendor's CPR Response, form RF4a, and the letter of clarification
dated December 7, 2001.
(h) The term "Technical Specifications" shall mean the written description of the
systems to be purchased, leased or licensed as included in the CPR, any
amendments and the Vendor's CPR Response. The technical specifications in the
CPR (form RF4a) and the Vendor's CPR Response dated 9/18/01 are deemed
included as part of the Agreement as is the entire CPR. In addition, any written
descriptions, reports, or examples of Customer systems made available to Vendor
during the CPR process for review are deemed included as part of the Agreement.
(i) The term "Enhancement" shall mean any program, any part thereof, or any
materials not included in the Licensed Software and Documentation at the time of
execution of this Agreement that is related to the Licensed Software and
Documentation.
(j) The term "Use" shall include, but not be limited to, copying any portion of the
Licensed Software or Documentation into a computer or transmitting them to a
computer for processing of the instructions or statements contained in the Licensed
Software and Documentation.
(k) The term "Updates" shall mean program logic and documentation changes and
improvements to correct known defects and maintain the operational quality of the
Licensed Software and changes required to keep it current with current versions of
the System Software or other environmental software, firmware, or hardware as
specified by the hardware manufacturer.
(1) The term "Project Definition" shall include the Customer's Functional
Specifications, Technical Specifications, and the Vendor's CPR Response for scope
and content of work, including cost and timelines. Such documents shall become a
part of this Agreement by reference and shall be signed by both Vendor and
Customer before work shall begin.
(m)The term "Source Code" shall mean all of the instructions, in both printed and
machine-readable form, needed to compile, link, and execute any or all of the
software covered by this Agreement. It must include, by definition, all of the
libraries, and other utilities to take the raw instructions and convert them into
usable, executable Object Code on the hardware environment(s) at the Customer's
site(s). It must also include all of the necessary history and documentation for a
reasonably trained technician to take over the on-going support of the systems
involved.
Sun Ridge Systems, Software License Agreement Page 6 of 24
CITY OF SAN RAFAEL SUN RIDGE SYSTEMS, INC.
MARCH 18. 2002 APPLICATION SOFTWARE UCENSEMSE AGREEMENT
(n) The term "Object Code" shall mean the machine-readable, executable form of the
software covered by this Agreement which enables the hardware environment at the
Customer's site(s) to perform the functions as defined by the Project Definition.
(o) The term "Module" shall mean a subset of the packaged Licensed Software that
relate to a specific set of functions as defined in the Cost Proposal Request
document and assigned a specific paragraph number. In the Vendor's CPR
response form RF4, some modules were cross-referenced as included with other
modules for which as specified license fee was quoted.
1.02 TERM
Except as provided for termination for cause in sections 6.02 and 9.01, this Agreement
shall continue for a term ending ten (10) years from the effective date of this Agreement as
provided in section 1.05, after which date of the agreement shall automatically extend for
successive one-year periods unless a written notice of termination has been given by either
party to the other party at least six (6) months prior to the end of such a one-year extension
period. The obligations set forth in sections 2.01, 2.02, 3.01, 3.02, 3.03, 8.02 and 9.01 shall
survive termination of this Agreement.
1.03 INCLUDED DOCUMENTS
This Agreement shall include the following documents which are listed in order of their
precedence in the application and interpretation of this Agreement:
A. This Agreement with the following attached Exhibits:
Project and Payment Schedule - Exhibit Al
Progress Report Format Exhibit A2
B. Award Configuration - Exhibit B
Licensed Software Modules -- B1
Work Assignment Schedule B2
C. Installation & Training - Exhibit C
D. Acceptance/Reliability Test Specifications - Exhibit D
Vendor CPR Response form RF4a and letter dated December 7, 2001
E. Hardware Configuration Requirements - Exhibit E
Vendor CPR Response form RF5
F. Vendor's CPR Response (included by reference)
G. Customer's Request for Proposal (CPR) (included by reference)
1.04 SUBCONTRACTORS
Vendor asserts that no subcontractors will be used under this Agreement.
Sun Ridge Systems, Software License Agreement Page 7 of 24
CITY OF SAN RAFAEL SUN RIDGE SYSTEMS, INC.
MARCH 18. 2002 APPLICATION SOFTWARE UCENSE/USE AGREEMENT
1.05 EFFECTIVE DATE
The effective date of this Agreement will be the date on which the last party signed the
contract if both parties did not sign on the same date.
2.00 PROPERTY RIGHTS
2.01 WARRANTY OF OWNERSHIP/RIGHT TO SELL SOFTWARE
Vendor hereby stipulates that it is the sole owner of all Licensed Software and
Documentation, or that it has the right to sell, lease, or grant and support such Licensed
Software and Documentation, free and clear of any liens and encumbrances. Any and all
legal actions regarding the Licensed Software and Documentation, or any previous version
of them under any name, in the past fifteen years has been fully disclosed to the Customer.
2.02 HOLD HARMLESS AND INDEMNIFICATION -SOFTWARE
In the event of a claim that the Licensed Software constitutes an infringement of a
copyright or patent, Vendor shall hold harmless and indemnify Customer and its officers,
employees and agents from every claim or demand resulting therefrom. Vendor shall, at its
own cost, risk and expenses, defend any claim on behalf of Customer and its officers,
employees and agents and satisfy any judgment rendered against any of them with respect
to infringements of copyrights, trade secrets, or patents.
2.03 COPYRIGHT NOTICE
Vendor will mark all copies of the Licensed Software and Documentation with a copyright
and trade secret notice indicating Vendor's ownership. Placing of such copyright and trade
secret notice shall not be deemed a publication or placement in the public domain.
2.04 ACKNOWLEDGMENT OF NO ENHANCEMENT RIGHT
Any Licensed Software modifications or enhancement developed by the Vendor for the
Customer under this Agreement will remain the property of the Vendor but shall be
included under the terms of this Agreement.
3.00 PROPRIETARY AND TRADE SECRET INFORMATION
3.01 CUSTOMER'S PROTECTION OF LICENSED SOFTWARE
It is the Customer's understanding that Licensed Software and Documentation, which a
Vendor considers to be proprietary and a trade secret, will be treated by the courts as a
trade secret if the Vendor's behavior toward the Licensed Software and Documentation
show an effort to preserve the secret. Such behavior may include the institution of security
measures, a designation of confidentiality and a restriction on copying the Licensed
Software and Documentation.
Customer will make reasonable effort to protect the confidential nature of the Licensed
Software and Documentation and system software by establishing written procedures for its
employees and other persons permitted access to the Licensed Software and
Sun Ridge Systems, Software License Agreement Page 8 of 24
CITY OF SAN RAFAEL SUN RIDGE SYSTEMS, INC.
MARCH 18. 2002 APPLICATION SOFTWARE LICENSE/USE AGREEMENT
Documentation and system software to follow in order to protect the Licensed Software
and Documentation and System Software from being acquired by unauthorized persons.
3.02 DESIGNATION OF CONFIDENTIALITY
Confidential information shall mean all matters relating to the Customer's business which
are clearly designated in writing as confidential by the Customer and which are disclosed
by Customer to Vendor pursuant to this Agreement. All confidential information will be
safeguarded and kept confidential by Vendor during the term of this Agreement to the same
extent that Vendor safeguards confidential information relating to its own business.
Vendor will instruct its employees to use the same care and discretion with respect to the
Customer's confidential information that they use with respect to the Vendor's confidential
information.
Vendor will require its staff to sign a written agreement expressly prohibiting the disclosure
of the Customer's confidential information. A copy of such nondisclosure agreements shall
be attached to the work assignment(s) and incorporated herein.
Customer acknowledges that the Licensed Software and Documentation contain propriet-
ary and confidential information. Information received by Customer under this Agreement
will not be considered confidential if:
(a) The information was in Customer's possession prior to the execution of this
Agreement;
(b) The information was legally acquired from third parties and did not originate with
Vendor or was in the public domain at the time it was disclosed;
(c) The information was independently developed by Customer;
d) The information was disclosed to Customer by a third party with Vendor's approval.
3.03 CUSTOMER'S RIGHTS TO COPY LICENSED SOFTWARE
Customer shall not, without prior consent of Vendor, copy in whole or in part, the Licensed
Software and Documentation provided by Vendor under this Agreement for other than the
Customer's need for a copy of the Licensed Software and Documentation for back-up
purposes or installation of System under provisions of this Agreement.
4.00 LICENSE GRANT
4.01 SCOPE OF LICENSE
Vendor hereby grants to Customer, for the term of the Agreement, a non-exclusive,
nontransferable license, to:
(a) Install, use, and execute the Licensed Software on computers owned or leased
and used by Customer at its facilities, for an unlimited number of concurrent
users, for the sole and express purpose of supporting the internal business
activities of Customer or other public agencies contracting for service with
Customer on Customer hardware environment; and
Sun Ridge Systems, Software License Agreement Page 9 of 24
CITY OF SAN RAFAEL SUN RIDGE SYSTEMS, INC.
MARCH 18, 2002 APPLICATION SOFTWARE LICENSE/USE AGREEMENT
(b) Use the Documentation only in conjunction with installation and use of the
Licensed Software.
Customer shall pay software license fees as provided in Exhibit B and in accordance with
the payment schedule identified in Exhibit A.
4.02 RISK OF LOSS OF LICENSED SOFTWARE AND DOCUMENTATION
The Vendor shall assume risk of loss and damage to the Licensed Software and
Documentation and shall replace any loss or damaged portion at Vendor expense. Risk of
loss prior to delivery shall be covered by the Vendor's insurance.
4.03 DOCUMENTATION
The Vendor shall furnish the Customer upon execution of this Agreement at a minimum,
two (2) printed copies (one as working copy and one for library purposes) and one
electronic (CD-ROM) copy of the Documentation per site, which materials shall describe
the Vendor's recommended use and application of the Licensed Software.
4.04 SCOPE OF SERVICES
The scope of services for this Agreement is defined in the Exhibits attached hereto. Any
additional services shall be provided as specified in section 4.08 below.
4.05 SITE OF SERVICES
Vendor's services are preferred to be performed at location(s) within the enterprise unless
specific work assignment calls for services to be performed at Customer location(s). If
services are provided at Vendor's location(s), Vendor shall provide office space and
facilities to Customer staff commensurate with that provided its own employees. If
services are provided at Customer's location(s), Customer shall provide office space and
facilities to Vendor's staff commensurate with that provided to its own employees.
4.06 MODIFICATION OF SCOPE
Subject to Customer's purchasing policy in San Rafael Municipal Code chapter 2.55,
Customer may at any time modify the scope of services specified in any work assignment
upon five (5) days written notice to Vendor specifying the desired modifications to the
same degree of specificity as in the original work assignment. Modification of services
shall include any increase, modification or decrease in the scope of service. Vendor shall
provide a written quote for the increased, changed or decreased services within five (5)
working days. In no event shall Vendor continue with services requested in writing to be
discontinued from the date of written notice. The parties shall then negotiate in good faith
and agree upon an increased or decreased charge which shall otherwise be governed by the
terms and condition of this Agreement and the work assignment.
Vendor shall provide the custom programming services as defined in a Work Assignment
Schedule which will be attached and made a part hereof as Exhibit B(2), and the services
specified in any future Work Assignment Schedule which may be agreed to in writing
Sun Ridge Systems, Software License Agreement Page 10 of 24
CITY OF SAN RAFAEL SUN RIDGE SYSTEMS, INC.
MARCH 18, 2002 APPLICATION SOFTWARE LICENSE/USE AGREEMENT
between the parties. Such services might include special studies; programming and
application design and development; systems analysis and design; data base and program
conversion; data conversion; implementation planning, procedures and programs;
installation evaluation; technical and user training; and specification preparation. Customer
shall request such services in writing on a Vendor -developed, Customer -approved form and
shall specify:
1) Nature of work to be performed;
2) Number of individuals required;
3) Category of experience of each;
4) Date on which assignment is to begin;
5) Location of assignment;
6) Length of assignment, including due date;
7) Source of funds (Account Number and authorized approval); and
8) Individual who will coordinate for Customer and Vendor.
Vendor shall use its best efforts to provide a quotation for each service request and will
provide a written quote within five (5) working days following receipt by the Vendor of the
Customer's request. Upon written acceptance by Customer of Vendor's quotation, Vendor
shall be authorized to proceed with the work. Such quotation shall be called the "work
assignment".
Each work assignment shall be governed by the terms and conditions of this Agreement,
the terms and conditions of the work assignment, and by such supplementary written
amendments of this Agreement or the work assignment as may be, from time to time,
executed between the parties.
In the event of a conflict between the Functional Specification of this Agreement and the
Functional Specifications of any work assignment, the Functional Specifications of the
work assignment shall govern.
No oral request for modification of services shall be binding on either party.
Further, the Vendor agrees that its responsibilities under this Agreement will not be
assigned or licensed by the Vendor without the prior written consent of the Customer.
5.00 PROGRAM SUPPORT SERVICES
5.01 LICENSED SOFTWARE AND DOCUMENTATION TRAINING
The Vendor shall provide to Customer sufficient technical and end user (non technical or
functional) training and support services to enable Customer to productively use the
Licensed Software and Documentation on the Customer -provided, Vendor -approved
hardware using the latest published release of the system software to the Customer's
satisfaction. Vendor stipulates that the days of training specified in Exhibit C attached
Sun Ridge Systems, Software License Agreement Page 11 of 24
CITY OF SAN RAFAEL SUN RIDGE SYSTEMS, INC.
MARCH 18. 2002 APPLICATION SOFTWARE LICENSE/USE AGREEMENT
hereto are sufficient under reasonable circumstances to accomplish this. The Customer
shall have the right to audio and video-tape the training session for retraining purposes.
A list of the final training schedule and costs is included in Exhibit C.
5.02 TRAINING
Vendor shall provide installation training as specified in Exhibit C directly to the various
user -groups for the application Modules at Customer facilities. Additional training at
Customer request will be available at Vendor's then current rates (for similar agencies and
similar services). Trainers shall be experienced and knowledgeable in the specific Modules
they are teaching and familiar with the procedures in similar municipal environments to the
Customer's. Customer will provide two types of training areas: 1) small group area with 2
networked workstations, desk and chairs where a trainer and two people can be trained on
the operation and use of specific Modules; and 2) a large group area with 10 networked
workstations, tables, chairs, white board, projector, and other supplies such as paper,
pencils, easel, etc. Vendor will provide necessary training materials and have session
outlines and agendas for all training sessions, provided to Customer at least five days in
advance of the scheduled sessions.
Customer may request a replacement trainer if there is demonstrable evidence that the
trainer initially scheduled has been ineffective in conducting specific training sessions. If
Vendor has been notified that a particular training session was ineffective because of the
qualifications or techniques of the trainer and uses the same trainer in a subsequent session
which also turns out to be ineffective (with documented evidence provided by Customer),
Customer will be entitled to withhold payment for the subsequent session until a makeup
session with a qualified trainer can be completed.
The training dates identified in the Project Schedule (Exhibit A) may be modified only by
mutual agreement of the Customer and Vendor. In the event the Customer cancels
scheduled training dates (excluding events beyond Customer's reasonable control), with
less than two weeks notice to Vendor, Vendor shall be compensated for all out of pocket
expenses incurred for said training. In addition, Customer shall pay vendor 10% of the
total cost of the training rates for the days that were cancelled.
5.03 LICENSED SOFTWARE AND DOCUMENTATION SUPPORT AND
ENHANCEMENTS
Regardless of whether the Customer licenses Source Code or Object Code, or a combina-
tion thereof, Vendor -provided Licensed Software and Documentation support will be
provided by Vendor in annual increments after Acceptance and Reliability test are
successfully completed.
For purposes of comparison, Licensed Software and Documentation support costs shall be
identified in annual increments. Year one support costs shall begin after acceptance and
include any warranty periods. Year two support costs shall include a full twelve months of
support cost. Vendor, however, will correct errors or malfunctions in the Licensed
Software and Documentation from the date of installation.
Sun Ridge Systems, Software License Agreement Page 12 of 24
CITY OF SAN RAFAEL SUN RIDGE SYSTEMS, INC.
MARCH 18, 2002 APPLICATION SOFTWARE LICENSE/USE AGREEMENT
Vendor will provide at no additional cost all new enhanced and updated versions of
Licensed Software and Documentation to Customer. This will be provided with detailed
installation instructions for installation, testing and validation by Customer. Updates are
distributed via email; Customer agrees to maintain an email address for this purpose
capable of receiving mail with an attachment of up to 4MB in size. Licensed Software and
Documentation support and enhancements shall include:
a) Correction of all errors and malfunctions in the Licensed Software and
Documentation;
b) Vendor -initiated Licensed Software and Documentation enhancements and new
versions for installed application and system software;
c) Charges for programming time, data conversion tools, licensed materials update,
version control, Vendor internal library functions, shipping, handling and media
costs shall all be included in the annual support fee;
d) All State and Federal -mandated changes; and
e) All changes supplied to other similar public agencies.
Licensed Software and Documentation support and enhancements shall not include
Customer -developed queries and reports.
5.04 LICENSED SOFTWARE SUPPORT SERVICES
As part of regular Annual Maintenance/Support services, the Vendor shall provide
unlimited telephone and email technician support for each major application system. This
shall include answering questions from Customer users and technical staff alike, dial -in
diagnostics to the Customer systems, and regular updates and upgrades to keep the systems
current with the state of the art and hardware environment.
5.04.1 Coverage Hours
Vendor will provide a toll free phone number and monitored email address for
Customer to contact whenever a reproducible problem with the operation and use of
the Licensed Software occurs. Normal service hours will be Monday -Friday, 8AM-
5PM PST, Vendor's published list of holidays excepted. However, for reproducible
problems preventing system operation and affects public safety, qualified technical
support via toll free telephone number will be available 24 hours, 7 days a week,
holidays included.
5.04.2 Call Response
A. For problems in which the Customer's system affects public safety due to a
Vendor software problem, Vendor personnel will work with Customer
continuously until the situation is resolved.
B. For problems in which the Customer's system affects public safety due to a
Vendor software problem, Vendor will provide a temporary fix or procedural
workaround for reported problems. If the permanent fix cannot be delivered in
the next release of the software, Vendor will provide weekly status reports to
Sun Ridge Systems, Software License Agreement Page 13 of 24
CITY OF SAN RAFAEL SUN RIDGE SYSTEMS, INC.
MARCH 18, 2002 APPLICATION SOFTWARE LICENSE/USE AGREEMENT
Customer of the progress for the permanent fix until it has been successfully
implemented on Customer's systems. Failure to provide a weekly status report
documenting reasonable progress toward problem resolution will entitle
Customer to a pro -rated credit from the next period's maintenance fees for each
week lacking such a report.
5.05 LICENSED SOFTWARE MAINTENANCE
The Vendor shall maintain Customer's Licensed Software so that it operates in conformity
with materials as set forth in the Vendor's CPR Response and subsequent related
documents including all future updated or enhanced versions. The Vendor shall use best
efforts to correct reproducible material errors or malfunctions after notification by
Customer, supply technical bulletins, updated user guides and other Documentation as they
are released by the Vendor, and supply Customer with Updates to the Licensed Software
within 30 days of their announced release.
When program maintenance is provided for a Licensed Software to be used at multiple
locations by Customer, the Vendor shall provide error corrections, Updates and
Enhancements to Customer for distribution, testing, and installation by Customer at the
additional Customer locations.
5.06 ON-SITE ASSISTANCE
Assistance by the Vendor for services not covered by this Agreement at Customer's
location shall be available at Customer's written request from an authorized representative
subject to compliance with the Customer's purchasing policies as contained in San Rafael
Municipal Code Chapter 2.55. On-site assistance will be billed at the Vendor's rates as
stipulated in Exhibit 131 of this Agreement. Expenses shall be charged at the lesser of
actual or rates as defined in said Exhibit.
If correction of any Licensed Software error or malfunction requires the Vendor to be on-
site to install a fix or correct such malfunction, the Customer will not be liable for any
labor, travel, or related expenses.
5.07 TRAINING FOR ENHANCEMENTS
The cost and Customer time requirements for training for Enhancements shall be provided
by Vendor in advance of the installation of any such Enhancement.
5.08 ANNUAL LICENSED SOFTWARE MAINTENANCE AND SUPPORT FEE
INCREASES
Vendor may increase Annual Maintenance and Support Fees identified in Exhibit A no
sooner than five years after the successful completion of Acceptance Testing on all
modules. Such increase shall be limited to the cumulative Consumer Price Index rate as
published by the Bureau of Labor Statistics (www.bls.aov) for the San Francisco -Oakland -
San Jose area (All Items, CPI -U) for the 5 year period ending in March of the fiscal year
prior to the fiscal year in which the increase will occur, provided that written notice of the
increase shall be made by May 1 for the following fiscal year, beginning July 1.
Sun Ridge Systems, Software License Agreement Page 14 of 24
CITY OF SAN RAFAEL SUN RIDGE SYSTEMS, INC.
MARCH 18, 2002 APPLICATION SOFTWARE LICENSE/USE AGREEMENT
Thereafter, support cost may increase annually after 5 years subject to the same provisions
for notice and CPI limits.
5.09 PLATFORM PROTECTION
As long as the Customer maintains continuous maintenance and support with the Vendor
for each of the modules included herein, Customer shall have the right to transfer the
licenses for any and all modules to any new hardware/platform environment then currently
marketed and supported by Vendor. Customer agrees to pay for any data conversion and
retraining costs which shall not exceed the lesser of the costs paid under this Agreement for
initial conversion and training or those charged to similar customers for similar tasks.
5.10 TERMINATION OF SUPPORT
Support may be terminated as follows:
A. Upon 90 days prior written notification by Customer to the Vendor;
B. Upon 60 days' prior written notice if the other party has materially breached the
provisions of this Agreement and has not cured such breach within such notice
period;
C. Since annual support charges are paid annually in advance, termination before
the end of a fiscal year shall require a pro -rated refund for the fees paid to the
end of the fiscal year.
Termination of support as provided herein shall not be deemed a termination of this
Agreement.
5.11 CUSTOMER RESPONSIBILITIES FOR SUPPORT
Customer agrees to have a dial in telephone line available for Vendor's use when a problem
is reported. Customer will be responsible for all costs associated with installing and
maintaining this line.
Customer must also provide and install Symantec pcANYVMERE remote access software
and Microsoft SQL Server Enterprise Manager database management software (or its
appropriate equivalent) on a designated dial in computer on the computer network.
Vendor will use this line only with Customer's permission on a per case basis. Use by
Vendor will only be possible when Customer personnel start the PC Anywhere program.
As a further security mechanism Customer can configure PC Anywhere, if desired, to an
automatic call back mode which will further restrict access to authorized callers.
Vendor will use this telephone link to connect to Customer's system to examine data files,
update and repair them when necessary, and download maintenance -related logs
automatically maintained by the Licensed Software and Documentation. Vendor will also
use this line to upload fixes to problems to Customer's system when appropriate.
5.12 SUPPORT LIMITATIONS
Vendor agrees to provide support only for public safety application software provided by
Vendor. Other software used by Customer (word processing, spreadsheet, etc.) is not
Sun Ridge Systems, Software License Agreement Page 15 of 24
CITY OF SAN RAFAEL SUN RIDGE SYSTEMS, INC.
MARCH 18, 2002 APPLICATION SOFTWARE LICENSE/USE AGREEMENT
included in this Agreement. PC and network operating system software and database
system software is similarly not included, although Vendor will assist Customer in isolating
problems to this software. Also specifically excluded is responsibility for administration,
support, or maintenance of Customer computer network, operating system, or database.
This Agreement does not include hardware maintenance or assistance in diagnosing
hardware problems with the exception that Vendor will assist Customer in determining
whether a problem is software or hardware in nature.
6.00 INSTALLATION, DELIVERY, AND ACCEPTANCE
6.01 DELIVERY
Delivery of the Licensed Software shall be complete when all modules are copied onto the
hardware environment specified and are fully operational and appropriately labeled media
and documentation are presented to Customer as a complete system backup of all software
modules and data. The documentation shall include, but is not limited to, instructions as to
how to completely re -install the contents of the media onto the hardware proposed.
6.02 ACCEPTANCE AND PAYMENT
Acceptance will be based on the following "acceptance criteria": 1) That the Vendor has
delivered and configured the Licensed Software proposed on the Customer -provided,
Vendor -approved hardware [Delivery], 2) The functions and features listed in CPR form
RF4a and subsequently amended perform as stipulated in Vendor's CPR Response
[Acceptance Testing]; and 3) That the System performs at a level consistent with what was
demonstrated by the Vendor during the evaluations and site visits [Reliability Testing].
Payment is structured in Exhibit A so that the vendor receives partial payment when
Acceptance Testing is satisfactorily completed and final payment when Reliability Testing
has been performed on all modules so that concurrent productive use of all modules is
demonstrated to function as proposed and demonstrated by the Vendor.
The Customer may terminate this Agreement, upon written notice effective immediately,
at any time during the Acceptance Testing period per the Evaluation Criteria and
Technical Specifications as specified in the CPR. Additional mutually agreed upon,
written acceptance criteria may be added by the Customer prior to the end of the
Acceptance Testing period. The Customer shall accept the Licensed Software at the close
of the Acceptance Testing period by providing Vendor with written notification of
acceptance unless Vendor fails to meet acceptance criteria stated above.
If the Customer identifies any substantive irregularities in the performance of the Licensed
Software from what was specified by the Customer in its CPR and Vendor's CPR
Response thereto and any subsequent agreement(s), the Customer shall have the right to
terminate this Agreement. At its sole option, however, the Customer may choose any or all
of the following alternatives:
A. The Vendor may be given the opportunity to extend the Acceptance Testing
Period for up to thirty (30) calendar days during which to bring such
irregularities into compliance. If after such time the perfonnance irregularity is
Sun Ridge Systems, Software License Agreement Page 16 of 24
CITY OF SAN RAFAEL SUN RIDGE SYSTEMS, INC.
MARCH 18, 2002 APPLICATION SOFTWARE LICENSE/USE AGREEMENT
not remedied such that the acceptance criteria have been satisfied, the Customer
may terminate this Agreement, or;
B. If the non-compliant component is a module of the Licensed Software,
Customer may reject the component and only pay for accepted modules, or;
C. At the Customer's sole option, notwithstanding A and B above, Customer may
designate the non-compliant component as a Project to be completed at a
mutually agreeable date. Specifications for the delivery and acceptance for
each such item will be the same as the acceptance provisions stated above and
shall include appropriate due dates. Customer may then close the initial
Acceptance Testing period for items delivered and functioning in accordance
with their specifications, pay for accepted items only, and open new testing
periods for non -delivered items. Final Reliability Testing will not be complete
until all such Projects are delivered and accepted by the Customer.
In the event the Vendor fails to satisfy the acceptance criteria during the Acceptance
Testing period, the Customer will agree to pay only those delivery, installation,
configuration, conversion, and training costs as specified in the Vendor's CPR Response
and receive a refund on any license fee deposits made to that point. Costs for Licensed
Software removal, additional labor, insurance, etc. will not be paid by the Customer.
6.02.1 ACCEPTANCE TESTING
Once the Vendor(s) has delivered, installed the Licensed Software, configured the
system for operational use, trained the designated Customer System Manager and
one backup person to operate the basic components of the proposed Licensed
Software, and Customer has loaded test data, the Acceptance Testing can begin.
The Acceptance Testing period shall be for 30 calendar days. During the
Acceptance Testing period, the Customer will test all delivered modules by
executing any or all of the features contained in the Feature/Function Checklist
according to the Vendor Compliance Code responses in CPR Response Form RF4a.
During this time, the Vendor will provide access (at no additional charge) to a
qualified technician either on-site or via telephone and dial -in modem to assist the
Customer in the testing of the applications.
If any part of the awarded subsystems should fail (i.e. not perform according to the
Vendor's Compliance score), the Customer may designate that portion as a Project
for delivery at a later date or apply other remedies as specified in 6.02 above.
6.02.2 RELIABILITY TESTING
Once the System has passed the Acceptance Test and Projects have been designated
and agreed to, the implementation of the System into productive use will begin.
This includes training of all primary users and final conversion of all relevant data.
Once the Vendor has designated a module as available for productive use (in
writing), a 30 day Reliability Test will begin. During this period all of the data,
workstations, software, and peripherals must be available to all designated users at
least 90% of the time. This will be determined by determining that any workstation
or device that is not available or involves the unavailability or repeatable failure of
Sun Ridge Systems, Software License Agreement Page 17 of 24
CITY OF SAN RAFAEL SUN RIDGE SYSTEMS, INC.
MARCH 18, 2002 APPLICATION SOFTWARE LICENSE/USE AGREEMENT
a function critical to the user's job function because of any documented replicable
software malfunction for more than 5 consecutive minutes during any 24 hour
period shall be deemed unavailable. The Reliability calculation is represented
below:
Reliability Calculation =
(Total Number of Unavailable Workstation' Devices)
(Total Number of Devices) X 30
If the Reliability Calculation is more than.10, the Reliability Test will be deemed to
have failed. Hardware or network failures other than those due to the inappropriate
sizing or configuration of the hardware and system software specified in Exhibit E
shall not cause failure of the Reliability Test.
6.02.3 PAYMENT SCHEDULE
Customer shall pay for Licensed Software and services in this Agreement according
to the payment milestones identified in Exhibit A. Vendor shall submit an invoice
for the appropriate payment milestone and Customer will process the invoice for
payment according to its normal payment processing procedures.
6.03 PPLICABLE TAXES
Vendor agrees and asserts that the taxable amount for all items subject to applicable local,
state or federal sales, use, excise, personal property or other similar taxes or duties are
included in the "License Fees and Product Cost" column of CPR forms R174 and RF5
included as Exhibit B and E. The Customer will pay taxes on only those items so indicated
at the rates prescribed by law at the time of payment. Taxes based upon net income or any
other tax normally paid by the Vendor shall be the sole responsibility of the Vendor. Items
subject to taxes not indicated in the Vendor's CPR Response as taxable which may
subsequently be charged to the Vendor by any taxing agency with reference to the
purchase, lease/purchase or license included in this Agreement shall be the sole
responsibility of the Vendor and will not be paid by Customer.
6.04 ADDITIONAL CHARGES
Out-of-pocket expenses incurred by the Vendor for travel related, supplies, and other
expenses shall be paid by Customer provided that the expenses have been prior approved
by Customer, and such approval shall not be unreasonably withheld. Such expenses shall
be limited to the lesser of actual or cost quoted in Vendor's CPR Response.
7.00 CUSTOMER RESPONSIBILITIES
7.01 CUSTOMER SUPPORT OF VENDOR
Customer shall furnish to the Vendor priority access to the Customer's system for the
period of time required by the Vendor for installation, testing, training, diagnostics, etc.
Sun Ridge Systems, Software License Agreement Page 18 of 24
CITY OF SAN RAFAEL SUN RIDGE SYSTEMS, INC.
MARCH 18. 2002 APPLICATION SOFTWARE LICENSE/USE AGREEMENT
Customer shall provide the following resources for Vendor's use in fulfillment of this
Agreement:
A. One qualified Customer staff coordinator assigned to work with the Vendor's
representative on the installation of the Licensed Software, acceptance, training,
conversion and maintenance. Customer representative shall have sufficient
authority to make decisions for Customer consistent with City Council
direction. Customer understands that Vendor will rely upon a staff member
having such authority.
B. The availability of Customer's personnel upon reasonable request of Vendor to
answer questions and advise Vendor on Customer's facilities, operations and
requirements.
C. Adequate office space at Customer's premises for Vendor personnel.
D. Customer shall provide input data in accordance with the agreed upon test and
acceptance plan and procedures for use by the Vendor in acceptance testing.
E. The Customer shall specify conversion format and procedures that the Vendor
shall complete at its expense.
F. Upon completion of installation and training, and once final acceptance is
signed off by the Customer, Customer shall be solely responsible for the
operation and use of the Licensed Software.
8.00 WARRANTY OF PERFORMANCE
8.01 COMPLIANCE WITH STATE AND FEDERAL REPORTING REQUIREMENTS
As long as Customer maintains continuous maintenance and support for the modules
included herein, Vendor shall ensure that all software modules will comply with any and
all then current State and Federal reporting requirements, such that Customer will not be
liable for program flaws which may violate any such requirements. In the event that the
State or Federal government mandates a substantial change in reporting that requires
Vendor programming resources in excess of a person -year of effort, Vendor will provide
the additional programming services at cost and distribute the cost to all then -current
licensed customers. Customer will agree to pay only its pro -rata share of such costs
regardless of whether other Vendor customers participate subject to Customer's
procurement policies and procedures.
8.02 WARRANTY OF PERFORMANCE
The Vendor shall warrant for a period equal to the term of the Agreement, commencing
with the Customer's acceptance of the Licensed Software, that the Licensed Software will
perform in accordance with its specifications as set forth in the Documentation and
Vendor's CPR Response, if properly used in the operating environment specified in the
Documentation.
The Vendor warrants that all modules are operable and all modules are interoperable with
each other and the configuration is complete and suitable for the purpose specified by the
Sun Ridge Systems, Software License Agreement Page 19 of 24
CITY OF SAN RAFAEL SUN RIDGE SYSTEMS, INC.
MARCH 18. 2002 APPLICATION SOFTWARE LICENSE/USE AGREEMENT
Customer in the CPR except as may have been specifically excluded in the Vendor's CPR
Response.
Customer shall promptly provide to Vendor such computer time and services as Vendor
may require to permit investigation and, if necessary, correction and verification of error(s).
8.03 YEAR 2000 COMPATIBILITY
The Software will "operate accurately" (as defined below), and will not abruptly end or
provide invalid or incorrect results, before, on, and after January 1, 2000. For purposes
hereof, a failure to "operate accurately" exists if any one or more of the following
properties or capabilities is lacking: (i) execution of calculations using dates with a four -
digit year; (ii) functionality (both on-line and batch) including, but not limited to, entry,
inquiry, maintenance, and update, to support four -digit year processing; (iii) interfaces and
reports that support four -digit year processing; (iv) successful transition, without human
intervention, into the year 2000 using the correct system date (e.g. 01/04/2000); (v) after
transition to the year 2000, continued processing with a four -digit year without human
intervention; (vi) correct calculation of leap year; and (vii) provision of correct results in
forward and backward data calculation spanning century boundaries, including the
conversion of previous years currently scored as two digits.
8.04 CORRECTION OF ERRORS UNDER THE WARRANTY
At no charge to the Customer, the Vendor will promptly correct technical errors or defects
in the Licensed Software during the warranty period as specified in Section 8.02 of this
Agreement so that the Licensed Software will perform as described in the Documentation
and Vendor's CPR Response.
8.05 ORAL REPRESENTATIONS
No Customer or Vendor employee has the authority to bind either party to any oral
representation or warranty.
8.06 PROGRESS REPORTS
The Vendor will use the progress report form included in Exhibit A2 that defines the
activities accomplished to date, the activities planned and any problems which have
occurred or are anticipated from the point of contract signing until completion of the
Reliability Testing. Progress reports will be prepared monthly prior to Acceptance and
monthly thereafter by the Vendor and mailed to the Customer. Progress reports will be
discontinued upon satisfactory completion of the Reliability Test(s).
8.07 NO DISABLING CODE
Vendor warrants that all Licensed Software does not contain disabling or corrupting code
which would either prevent productive use of the software during the term of this
Agreement or that would damage or destroy Customer's data.
Sun Ridge Systems, Software License Agreement Page 20 of 24
CITY OF SAN RAFAEL SUN RIDGE SYSTEMS, INC.
MARCH 18, 2002 APPLICATION SOFTWARE UCENSEWSE AGREEMENT
9.00 LIABILITY, INDEMNIFICATION AND DEFAULT
9.01 LIABILITY, INDEMNIFICATION AND DEFAULT
Customer shall in no event be liable to the Vendor or other person claiming damages as a
result of the use of the Licensed Software and Documentation, for any damages whether
direct or indirect, special or general, consequential, or incidental or arising from loss of
profits.
The Vendor agrees to indemnify, defend, and hold harmless the Customer and its officers,
directors, shareholders, employees, and agents (the "Customer Indemnified Parties") from
any and all claims, demands, liabilities, and costs, including attorney's fees, arising out of
or relating to (i) any actual infringement of a third -party's intellectual property or (ii) the
gross negligence or willful misconduct of any employee or agent of the Vendor. This
indemnity obligation shall survive the expiration, cancellation or termination of this
Agreement. Notwithstanding the foregoing, the Customer expressly waives, releases, and
agrees that neither the Vendor nor any of the Vendor Indemnified Parties shall have any
liability for any individual's or entity's lost business, direct damages, incidental or
consequential damages, or any other claim arising out of or related to the use or
implementation of the software product provided or developed as part of this Agreement.
After the successful completion of the acceptance period, failure by Customer or Vendor to
comply with any term or condition under this Agreement shall entitle the other party to
give the party in default written notice requiring it to make good such default. Failure to
make good such notified default within thirty (30) calendar days of such notice shall
constitute breach of contract by the defaulting party and grounds for termination of this
Agreement.
9.02 BANKRUPTCY/SUPPORT CESSATION
In the event of the institution of proceedings by or against Vendor under federal or state
bankruptcy laws and assignment or receivership for the benefit of creditors, Customer shall
have the right (at no additional cost) to a complete and documented copy of all related
source code corresponding to the then current released version of the Licensed Software
(for internal use and not for resale) shall be entitled to precedence in any bankruptcy
proceedings and stand before any trustee's claims for the benefit of creditors. In the event
that the Vendor ceases to provide support for the Licensed Software, the Customer shall
have the same rights as if the Vendor had declared bankruptcy.
9.03 INSURANCE
Vendor, at its own cost and expense, shall purchase and maintain during the life of this
Agreement a comprehensive liability policy that shall protect Vendor from claims for
property damage and injuries to persons, including accidental death, and name the
Customer as an additional insured under said policy in not less than the following amounts:
• General Liability including personal injury and property damage in the amount of
$1,000,000.
• Automobile Liability, all non -owned and hired automobiles used in connection
with this Agreement, in the amount of $1,000,000 for combined single limit.
Sun Ridge Systems, Software License Agreement Page 21 of 24
CITY OF SAN RAFAEL SUN RIDGE SYSTEMS, INC.
MARCH 18. 2002 APPLICATION SOFTWARE LICENSE/USE AGREEMENT
In addition, the Customer shall be named as additional insured and provide Customer with
and endorsement on such policies and shall be notified by the insurance carrier of any
change in or cancellation of coverage. Vendor further agrees during the life of this
Agreement to maintain, at vendor's expense, all necessary insurance for its employees,
including, but not limited to, Workman's Compensation, disability, and unemployment
insurance.
Vendor shall furnish a certificate of insurance countersigned by an authorized agent of the
insurance carrier on a form of the insurance carrier setting forth the general provisions of the
insurance coverage. The countersigned certificate shall name the Customer as an additional
insured under the policy. The certificate shall contain a statement of obligation on the part of the
insurance carrier to notify Customer of any material change, cancellation or termination of the
coverage at least thirty (30) days in advance of the effective date of any such material change. The
certificate shall be furnished by Vendor to Customer prior to execution of this Agreement by
Customer.
9.04 LIMITATION OF LIABILITY
In no event will the Vendor be liable for lost business, direct, special, incidental, or
consequential damages to the Customer or any other person or entity (including, without
limitation, damages for loss of business information or other pecuniary loss), however
caused, whether for breach of warranty, contract, tort (including negligence, strict liability,
or otherwise) arising out of the quality, condition, or use of the software. Customer assumes
all responsibility for the selection of the Vendor's software to achieve Customer's intended
results and for the use of and results obtained from the software. The Vendor expressly
disclaims responsibility for all liabilities resulting from its use. In no event will the Vendor be
liable for any amount that exceeds the amount paid by the Customer for the software.
10.00 GENERAL PROVISIONS
10.01 ASSIGNMENT
This Agreement may be assigned by Vendor to another person or organization which
acquires all or substantially all of the assets of Vendor or Vendor's assets are transferred
through a merger or stock sale, provided that all the responsibilities and obligations under
this Agreement are assumed by the acquiring person or organization. Any other assign-
ment by Vendor shall be made only with the prior written consent of Customer which
consent shall not be unreasonably withheld provided that in the event of such assignment
the proposed assignee has agreed to be fully responsible for Vendor obligations under this
Agreement.
10.02 GOVERNING LAW
This Agreement shall be governed by and construed in accordance with the laws of the
state of California.
Sun Ridge Systems, Software License Agreement Page 22 of 24
CITY OF SAN RAFAEL SUN RIDGE SYSTEMS, INC.
MARCH 18, 2002 APPLICATION SOFTWARE LICENSE/USE AGREEMENT
10.03 ENTIRE AGREEMENT/AMENDMENTS
This Agreement constitutes the entire understanding of the parties with respect to the
matter contained herein. There are no promises, covenants or undertakings other than those
expressly set forth herein.
This Agreement may not be amended except by writing signed by authorized
representatives of Customer and Vendor and approved by Customer's City Council.
If any of the provisions of this Agreement are declared to be invalid, such provisions shall
be severed from this Agreement and the other provisions hereof shall remain in full force
and effect.
10.04 CONSTRUCTION
A term or condition of this Agreement can be waived only by written consent of both
parties.
Title and paragraph headings contained in this Agreement are for convenient reference and
do not constitute part of this Agreement and shall not affect the interpretation of this
Agreement.
This Agreement shall be binding upon and inure to the benefit of the parties to this
Agreement and their respective successors and assigns.
10.05 SERVICE OF NOTICE
Any notice required or permitted to be sent under this Agreement shall be delivered by
hand or mailed by registered mail, return receipt requested, to the addresses of the parties
first set forth in this Agreement.
Vendor: Tony Richards
Sun Ridge Systems
PO Box 5071
El Dorado Hills, CA 95762-0002
Customer: Ken Nordhoff
City of San Rafael
P.O. Box 151560
San Rafael, CA 94915-1560
10.06 BUSINESS LICENSE
Vendor must maintain an active City Business License through the term of this agreement
as long as this License Agreement or related Software Support Agreement are in force.
10.07 COST OF ATTORNEY'S FEES
The prevailing party in any action brought to enforce the terms and conditions of this
agreement, or arising out of the performance of this agreement, shall be entitled to
recover from the losing party the reasonable costs (including claims administration) and
attorney's fees expended in connection with such action.
Sun Ridge Systems, Software License Agreement Page 23 of 24
CITY OF SAN RAFAEL . SUN RIDGE SYSTEMS, INC.
MARCH 18, 2002 APPLICATION SOFTWARE LICENSE/USE AGREEMENT
SIGNATURES:
IN WITNESS WHEREOF, the parties have executed this Agreement as of the day,
month and year first above written.
CITY OF SAN RAFAEL
Sun Ridge Systems, Software License Agreement Page 24 of 24
CI 1 Y OF SAN RAFAEL SUN RIDGE SYSTEMS, INC.
APPLICATION SOFTWARi-iCENSE/USE AGREEMENT - EXHIBIT Al: PRO]EL-, AND PAYMENT SCHEDULE
120
Install Rack1
day (
Thu 4/18/021
Thu 4/18/02 (Mark Rinkel,Tech
121
Install new PDC
-5 days I
Fri 4/19/02 I
Thu 4/25/02
122
InstalUconfigure�
hardware
j 1 day I
Fri 4/19/02 i
Fri 4/19/02 Mark Rinkel,Tech
123
Install software
1 1.5 days Mon 4/22/02 Tue 4/23/02rMark Rinkel,Tech
I
124
Migrate data from
2.5 days E
Tue 4/23/02 i
Thu 4/25/02 (Mark Rinkel,Tech
1461
old PDC
I day, Fri 11/9/01 j
i
i
125.
Install new BDC
5 days
Fri 4/26/02 j
Thu 5/2/02
126 !—
Install/configure
i 1 day
Fri 4/26/02 I
Fri 4/26/02 jMark Rinkel,Tech
i
hardware
i1271
Install software
1.5 days
Mon 4/29/02 +
Tue 4/30/02 IMark Rinkel,Tech
` —1 -
128
Migrate data from
� 2.5 days
Tue 4/30/02
Thu 5/2/02 Mark Rinkel,Tech
old BDC
1
1129
r
Install Primary RIMS
Server
i 4.5 days (
Thu 4/18/02 I
Wed 4/24/02
130
I
Install/configure
hardware
I (-
1.5 days
-----------(,--__._._.
Thu 4/18/02
Fri 4/19/02
Mark Rinkel,Tech
131
Install O/S and SQL
Server
1.5 days
Fn 4/19/02
Mon 4/22/02
Mark Rinkel,Tech
I-- - -�--
1321
---.InstalUtest back-up'
---
1.5 days i
Tue 4/23/02 Wed 4/24/02
— _. - --- --- -
[Mark Rinkel,Tech
software
133
Install PD Message
4 days ±
Wed 4/24/02 I
Tue 4/30/02
Switch Server
1
E
f 134
InstalUconfigure
hardware
1 day
Wed 4/24/02
Thu 4/25/02 Mark Rinkel,Tech
1135
Install O/S
i 1.5 days i l "u 4/25/02
Fri 4/26/02 ark Rinkel,Tech
136 i
InstalUtest back-up
software
I
1.5 days I
Mon 4/29/02'
Tue 4/30/02
I
Mark Rinkel,Tech
113
Install FD Message
g Switch Server
4 days
Wed 4/24/02
Tue 4/30/02
j
i
Install/configure
1 day
Wed 4/24/02
I
__Ik
Thu 4/25/02
—
Mar Rinkel,Tech
1138
hardware
11391
Install O/S
1.5 days
Thu 4/25/02 I
Fri 4/26/02 (Mark Rinkel,Tech
(
140 1
Install/test back-up
I
i 1.5 days
Mon 4/29/02
—
Tue 4/30/02
ark Rinkel,Tech
r
software
.141
Install Primary Fire
Server
4.5 days i Wed 4/24/02
Tue 4/30/02
1421
Install/configure
1.5days Wed 4/24/02 !
Thu 4/25/02 (Mark Rinkel,Tech
hardware
-1431
Install O/S and SQL
I Server
1.5 days Fri 4/26/02
Mon 4/29/02 Rinkel,Tech
FMark
j 144
Install/test back-up 1
software
1.5 days Mon 4/29/02
Tue 4/30/02 Mark Rinkel,Tech
11451 Analysis ;
84.5 days i Fri 11/9/01 (
Thu 3/7/02 j
1461
ATAC Software i
I day, Fri 11/9/01 j
Fri 11/9/01 ;Mark Rinkel Al Hoffman
Exhibit A 1
CITY OF SAN RAFAEL
JUN RIDGE SYSTEMS, INC.
APPLICATION
SOFTWARL .- ,CENSEJUSE
AGREEMENT - EXHIBIT Al: PROIEL. � AND PAYMENT SCHEDULE
Installation
147
Omega Group
Installation
84.5 days
I
Fri 11/9101 Thu 3/7/02
I
11481
Install CrimeView
0.5 days (
_
Fri 11/9/01 I Fri 11/9/01 (Mark Rinkel,A1 Hoffman
149
Install FireView
0.5 days
Fri 11/9/01 Fri 11/9/01 Mark Rinkel Keith Schoenthal
150
CrimeView Training
2 days I
Fri 11/9/01 Tue 11/13/01 (Mark Rinkel,Al Hoffman
151
FireView Training
2 days Fri 1119101 Tue 11/13/01 Mark Rinkel,Keith Schoenthal
.152,
Post Installation
Follow-up Training - j
2 days
Tue 3/5/021 Thu 3/7/02 Mark Rinkel,A1 Hoffman
{
CrimeView I
'
Post Installation i
1153.
Follow-up Training - j
2 days
Tue 3/5/02 Thu 3/7 02 Mark Rinkel,Keith Schoenthal
FireView I
Exhibit A 1
CITY OF SAN RAFAEL SUN RIDGE SYSTEMS, INC.
APPLICATION SOFTW neE LICENSE/USE AGREEMENT - Exh1IBIT A2: PRuuRESS REPORT FORMAT
City of San Rafael
Public Safety Information System Project
Monthly Progress Report
Vendor:
Date:
Reporting Period:
Progress since the last report:
Items behind schedule/recovery plan:
Tasks planned for next reporting period:
Items of Concern/Identified actions required of City:
Exhibit A2
Release Date: 9/18/01
City of San Rafael
Vendor:
Due Date: 10/10/01
Public Safety Information System Cost Proposal
Sun Ridge Systems
Application/Module/Component
Application Modules Solution
Cross # Con- License Fees
Customization
and Components Prop
Description Reference current &
Costs Maintenance
Users/
'X'
Qty. Product Cost
From RF4A 1st Year Annual
4.1.0 IMPLEMENTATION - REQ'I5
ACCEPTANCE TESTING
A. Preliminary s�X _
Training
B. Monitoring and
X
Support
C. Data Conversion
X
Test Data
PROJECT SUPPORT
D. Preliminary
Planning X
E. Project
X
Management
F. Procedural
X
Consulting
RELIABILITY TESTING
G. On-site
X
Technical Support
H. Test Statistics X
OTHER
I TOTAL
Exhibit 131
14.1.0 IMPLEMENTATION - REQ'D
Is 1s Is is
Release Date:
9/18/01
City of San Rafael
Due Date:
10/10/01
Public Safety Information System Cost Proposal
Application/Module/Component
Application Modules
Solution
Cross # Con- License Fees Customization
and Components
Prop
Description Reference current & Costs
Users/
'X'
Qty. Product Cost From RF4A
4.1.1 Computer Aided Dispatch - REQ'D
A.GENERAL
X
REQ'MNTS
RIMS CAD Software N/A $ 75,000
X
B. E9-1-1 Interface
E9-1-1 Interface $ 10,000
TOTAL
Exhibit 131
14.1.1 Computer Aided Dispatch - REQ'D
$85,000 Is
Vendor:
Sun Ridge Systems
Maintenance
1st Year I Annual
$ 10,500
$
10,500
$ 1,500
$
1,500
$12,000 1$12,000
Release Date: 9/18/01 City of San Rafael
Due Date: 10/10/01 Public Safety Information System Cost Proposal
Application/Module/Component
Application Modules Solution Cross # Con- License Fees Customization
and Components Prop Description Reference current & Costs
Users/
'X'
Qty. Product Cost From RF4A
4.1.2 Police - REQ'D
TOTAL 14.1.2 Police - REQ'D
Exhibit 131
$ 75,000
$ 40,000
$ 10,000
$ 12,000
1$137,000 1$
Vendor:
Sun Ridge Systems
Maintenance
1st Year I Annual
$ 10,500 $ 10,500
$ 6,000
X
6,000
A. RMS
$
RiMS Records Management Software
$ 1,000
X
1,000
B. Citations
(Included in RMS Software)
C.
X
Property/Evidence
(Included in RMS Software)
D. Mobile
X
Computing
RIMS Mobile Computer Software
E. CLETS Interfacel
X
I
IXQuery the Records Systems of other
F. Data Sharing
RIMS customers (Fairfax/San Anselmo)
TOTAL 14.1.2 Police - REQ'D
Exhibit 131
$ 75,000
$ 40,000
$ 10,000
$ 12,000
1$137,000 1$
Vendor:
Sun Ridge Systems
Maintenance
1st Year I Annual
$ 10,500 $ 10,500
$ 6,000
$
6,000
$ 1,800
$
1,800
$ 1,000
$
1,000
1$19,300
1$19,300
Release Date:
9/18/01
City of San Rafael
Vendor:
Due Date:
10/10/01
Public Safety Information System Cost Proposal
Sun Ridge Systems
Application/Module/Component
Application Modules
Solution
Cross # Con- License Fees
Customization
and Components
Prop
Description Reference current &
Costs Maintenance
Users/
IX'
Qty. Product Cost
From RF4A 1st Year Annual
4.2.4 - Police - DES'D
A. Integrated
Mapping (CAD) (Not proposed)
A. Subpoena
Processing (Not proposed)
B. Pawn Tracking X (included with RMS Software)
C. Wants and X
Warrants (Included with RMS Software)
D. Crime Analysis (Not proposed)
TOTAL
Exhibit 131
14.2.4 - Police - DES'D
Is Is Is is
Release Date: 9/18/01 City of San Rafael
Due Date: 10/10/01 Public Safety Information System Cost Proposal
Application/Module/Component
Application Modules Solution Cross # Con- License Fees Customization
and Components Prop Description Reference current & Costs
Users/
'X'
Qty. Product Cost From R174A
4.3.1 Police - OPT'L
11
A. Permit Tracking (Included in RMS)
TOTAL 1 4.3.1 Police - OPT'L
Exhibit 131
Vendor:
Sun Ridge Systems
Maintenance
1st Year I Annual
$ 1,500 $ 100 $
l
f
l I 1$1,500 Is 1$100 1$100
100
X
B. Alarm Tracking
(Included in RMS)
C.
X
Narcotics/Sex/Ars
(Included in RMS)
X
D. Field Interview
(Included in RMS)
E. Personnel
(Not proposed)
F. Training
(Not proposed)
G. Restraining
X
JCustom
Order Tracking
development
TOTAL 1 4.3.1 Police - OPT'L
Exhibit 131
Vendor:
Sun Ridge Systems
Maintenance
1st Year I Annual
$ 1,500 $ 100 $
l
f
l I 1$1,500 Is 1$100 1$100
100
Release Date:
9/18/01
City of San Rafael
Vendor:
Due Date:
10/10/01
Public Safety Information System Cost Proposal
Sun Ridge Systems
Application/Module/Component
Application Modules
Solution
Cross # Con-
License Fees Customization
and Components
Prop
Description Reference current
& Costs
Maintenance
Users/
'X'
Qty.
Product Cost From RF4A
1st Year Annual
4.3.2 Custom Deve opment
X
A. FD - Cross Staff
See RF4A
RF4A-3.54
$ 4,000
B. FD - Equip
X
Move-up
See RF4A
RF4A-3.55
$ 2,000
C. FD - Vision
Interface
X
See RF4A
RF4A-3.56
$ -
D. FD - PROQ&A
X
Intfc
See RF4A
RF4A-3.58
$ 4,000
$ 600 $ 600
E. FD - Station
X
Printers
See RF4A
RF4A-3.111
$ 300
F. FD - Paging
X
Interface
See RF4A
RF4A-3.66
$ 6,500
$ 450 $ 450
G. FD - Reflex
X
Time
See RF4A
RF4A-3.112
$ 700
H. PD - CAD Wkst
X
Notif.
See RF4A
RF4A-3.113
$ -
I. PD - CAD Keybrd
X
RP Valid
See RF4A
RF4A-3.114
$ 400
J. PD - Property ID
X
Code
See RF4A
RF4A-7.97
$ 1,200
K. PD - Mobile
X
continuous stat
See RF4A
RF4A-6.103
$ 3,000
L. PD - CAD
X
Incident Refresh
See RF4A
RF4A-3.115
$ 1,500
M. PD -Vehicle
Make Drp Dwn
X
See RF4A
RF4A-8.171
$ 600
TOTAL
1 4.3.2 Custom
Development I I
1$24,200 Is
1$1,050 1$1,050
M. itl:7m:7il
CITY OF SAN RAFAEL SUN RIDGE SYSTEMS, INC.
APPLICATION SOFTWARE LICENSE/USE AGREEMENT - EXHIBIT B2: WORK ASSIGNMENT SCHEDULE
Work AssiEnment Schedule
Project
CUSTOM PROJECT: SRS configures pager interface
CUSTOM PROJECT: Fire CAD Unit Move -up Feature Completed
CUSTOM PROJECT: ProQA Interface Completed
CUSTOM PROJECT: Fire Paging Interface
CUSTOM PROJECT: Fire 'Reflex Time"
CUSTOM PROJECT: Fire Printer Enhancement
CUSTOM PROJECT: PD Keyboard RP Validation
CUSTOM PROJECT: PD Property ID Field
CUSTOM PROJECT: PD Mobile Continuous Update
CUSTOM PROJECT: PD CAD Incident Refresh
CUSTOM PROJECT: PD Vehicle Make Drop Down
CUSTOM PROJECT: PD Data Sharing
Exhibit B2
Delivery Date
11/1/02
8/20/02
2/3/03
11/01/02
8/20/02
8/20/02
8/20/02
8/20/02
11/01102
8/20/02
8/20/02
12/16/02
Release Date: 9/18/01
City of San Rafael
Vendor:
Due Date: 10/10/01
Administrative
Software Cost Proposal
Sun Ridge Systems
Support Services
Travel/
Application Modules Solution
Transportation
and Components Prop
Service Description
Resource Level Days
Daily Rate
# of Trips Per Diem Costs
TOTAL
'X'
14.1.0 IMPLEMENTATION - RE
ACCEPTANCE TESTING
A. Preliminary
X
Training
$
B. Monitoring and
X
Support
Telephone/Dial in spt as needed
$ 1 2
$ 995
$ - $ -
$1,990
Data Conversion
IC.
X
Test Data
$
PROJECT SUPPORT
D. Preliminary
X
Planning
Project startup
$ 1 1
$ 995
1 $ 10 $ 120
$1,125
E. Project
Management X
Ongoing project management
$ 1 23
$ 995
$ - $ -
$22,885
F. Procedural
Consulting X
$
RELIABILITY TESTING
G. On-site
(Included in Line 9 - on site not
_
Technical Support X
needed)
$
(Included in Line 9 - on site not
H. Test Statistics X
needed)
$
I
$
OTHER
TOTAL
I 26
1
I 1 I 1$120
1$26,000
Exhibit C
Release Date: 9/18/011
Due Date: 10/10/01
Application Modules Solution Class Description &
and Components
Prop Location
'X'
4.1.0 IMPLEMENTATION - RE
ACCEPTANCE TESTING
A. Preliminary
Training
X SRPD - Preliminary
B. Monitoring and
Support
X
C. Data Conversion
Test Data
X
PROJECT SUPPORT
D. Preliminary
Planning
X
E. Project
Management
X
F. Procedural
Consulting -
X
RELIABILITY TESTING
G. On-site
Technical Support
X
H. Test Statistics
X
OTHER
TOTAL
Exhibit C
City of San Rafael Vendor:
Administrative Software Cost Proposal Sun Ridge Systems
Training
L°J
Travel Costs
On Site Training Off Site Training for On -Site Training
Class Rate Per Max # Class Rate per Trip Per
Days I Class I Students Students I Days I Student Day Total Mtls # Trips I Costs I Diem TOTAL
2 $ 995 6
1 2 1
$ 240 1 $ 210 $ 135 $2,710
1 1$240 11 1$210 I 1$2,710
Release Date:
9/18/01
City of San Rafael
Vendor:
Due Date:
10/10/01
Administrative Software Cost Proposal
Sun Ridge Systems
Support Services
Travel/
Application Modules
Solution
Transportation
and Components
Prop
Service Description Resource Level Days Daily Rate # of Trips
Per Diem Costs TOTAL
'X'
4.1.1 Computer Aided Dispat
A. GENERAL
X
REQ'MNTS
(No separate charge)
$
X
B. E9-1-1 Interface
(No separate charge)
$
TOTAL
I I
Is Is
Exhibit C
Release Date: 9/18/011
Due Date: 10/10/01
Application Modules Solution Class Description &
and Components Prop Location
'X'
14.1.1 Computer Aided Dispat
A. GENERAL X
REQ'MNTS Dispatchers
X
B. E9-1-1 Interface
City of San Rafael Vendor:
Administrative Software Cost Proposal Sun Ridge Systems
Training
OR
Travel Costs
On Site Training Off Site Training for On -Site Training
Class Rate Per Max # Class Rateer Tri Per
p P
Days I Class I Students Students I Days I Student Day Total Mtls # Trips I Costs I Diem TOTAL
7 $ 995 6 $ 640 1 $ 210 $ 135 $8,760
TOTAL 1 7 1995 I 1 I I 1$640 1 1 1$210 1 1$8,760
Exhibit C
Release Date:
9/18/01 l
City of San Rafael
Vendor:
Due Date:
10/10/01
Administrative Software Cost Proposal
Sun Ridge Systems
(No separate charge)
Support Services
Application Modules
Solution
(No separate charge)
Travel/
Transportation
and Components
Prop
Service Description Resource Level Days Daily Rate # of Trips
Per Diem Costs TOTAL
'X'
4.1.2 Police - REQ'D
X
A. RMS
(No separate charge)
X
B. Citations
(No separate charge)
C.
X
Property/Evidence
(No separate charge)
D. Mobile
X
Computing
(No separate charge)
E. CLETS Interface
X
Installation
X
F. Data Sharing
Installation
TOTAL
Exhibit C
$1,400
$1,400
1$
$2,800
Release Date: 9/18/011
Due Date: 10/10/01
Application Modules Solution Class Description &
and Components Prop Location
'X'
4.1.2 Police - REQ'D
X
A. RMS
SRPD-Clerks/Admin
X
B. Citations
(Included)
C.
X
Property/Evidence
(Included)
D. Mobile
X
Computing
Officers/Investigations
E. CLETS Interface
X
Follow-up Training
X
F. Data Sharing
TOTAL
Exhibit C
City of San Rafael Vendor:
Administrative Software Cost Proposal Sun Ridge Systems
Training
LOJ
Travel Costs
On Site Training Off Site Training for On -Site Training
Class Rate Per Max # Class Rate per Trip Per
Days I Class I Students Students I Days Student Day Total Mtls # Trips I Costs I Diem TOTAL
6 $ 995 12
11 $ 995 18
5 $ 995 18
1 22 12985 1
$ 400 1 $ 210 $ 135 $7,390
$ 2,400 4 $ 210 $ 135 $15,670
3 $ 210 $ 135 $6,280
Is
1 1 1 1$2,800 1 8 1$630 1 1$29,340
Release Date:
9/18/01
City of San Rafael
Vendor:
Due Date:
10/10/01
Administrative Software Cost Proposal
Sun Ridge Systems
Support Services
Application Modules
Solution
Travel/
Transportation
and Components
Prop
Service Description Resource Level Days Daily Rate # of Trips
Per Diem Costs TOTAL
'X'
4.2.4 - Police - DES-b
A. Integrated
Mapping (CAD)
(Not Proposed)
$
A. Subpoena
Processing
(Not Proposed)
$
B. Pawn Tracking
X
(Included)
$
C. Wants and
X
Warrants
(Included)
$
D. Crime Analysis
(Not Proposed)
$
$
$
$
$
$
$
$
TOTAL
I I I I I
Is Is
Exhibit C
Release Date: 9/18/011
Due Date: 10/10/01
Application Modules Solution Class Description &
and Components Prop Location
D. Crime Analysis (Not proposed)
TOTAL
Exhibit C
City of San Rafael Vendor:
Administrative Software Cost Proposal Sun Ridge Systems
Training
LO
Travel Costs
On Site Training Off Site Training for On -Site Training
Class Rate Per Max # Class Rateer Tri Per
p P
Days I Class I Students Students I Days I Student Day Total Mtls # Trips I Costs I Diem TOTAL
is 1 1$
4.2.4 - Police - DES'D
A. Integrated
Mapping (CAD)
(Not proposed)
A. Subpoena
Processing
(Not proposed)
B. Pawn Tracking X
(Included)
C. Wants and X
Warrants
(Included)
D. Crime Analysis (Not proposed)
TOTAL
Exhibit C
City of San Rafael Vendor:
Administrative Software Cost Proposal Sun Ridge Systems
Training
LO
Travel Costs
On Site Training Off Site Training for On -Site Training
Class Rate Per Max # Class Rateer Tri Per
p P
Days I Class I Students Students I Days I Student Day Total Mtls # Trips I Costs I Diem TOTAL
is 1 1$
Release Date:
9/18/01
City of San Rafael
Vendor:
Due Date:
10/10/01
Administrative Software Cost Proposal
Sun Ridge Systems
X
Support Services
Application Modules
Solution
Narcotics/Sex/Ars
Travel/
Transportation
and Components
Prop
Service Description Resource Level Days Daily Rate # of Trips
Per Diem Costs TOTAL
Order Tracking
TOTAL
Exhibit C
Is
'X'
4.3.1 Police - OPT'L
X
A. Permit Tracking
X
B. Alarm Tracking
C.
Narcotics/Sex/Ars
X
X
D. Field Interview
E. Personnel
F. Training
G. Restraining
I
X
Order Tracking
TOTAL
Exhibit C
Is
Release Date: 9/18/011
Due Date: 10/10/01
Application Modules Solution Class Description &
and Components Prop Location
'X'
4.3.1 Police - OPT'L
X
A. Permit Tracking
X
B. Alarm Tracking
C.
Narcotics/Sex/Ars X
X
D. Field Interview
E. Personnel I
F. Training
G. Restraining I X
Order Tracking
TOTAL
Exhibit C
City of San Rafael Vendor:
Administrative Software Cost Proposal Sun Ridge Systems
Trainin
L°I
Travel Costs
On Site Training Off Site Training for On -Site Training
Class Rate Per Max # Class Rateer Tri Per
P P
Days Class Students Students Days I Student Day Total Mtls # Trips I Costs I Diem TOTAL
Is
Is
Release Date:
9/18/01
City of San Rafael
Vendor:
Due Date:
10/10/01
Administrative Software Cost Proposal
Sun Ridge Systems
B. FD - Equip
Support Services
X
Application Modules
Solution
Interface
Travel/
Transportation
and Components
Prop
Service Description Resource Level Days Daily Rate # of Trips
Per Diem Costs TOTAL
Exhibit C
Installation
Installation
Installation
1$
$
$700
$1,400
$
$1,400
1$3,500
'X'
4.3.2 Custom Development
X
A. FD - Cross Staff
B. FD - Equip
Move -up
X
C. FD - Vision
Interface
X
D.FD- PROQ&A
X
Intfc
E. FD - Station
X
Printers
F. FD - Paging
X
Interface
G. FD - Reflex I
X
Time
H. PD - CAD Wkst I
X
Notif.
I. PD - CAD Keybrdl
X
RP Valid
J. PD - Property IDI
X
Code
K. PD - Mobile I
X
continuous stat
L. PD - CAD I
X
Incident Refresh
M. PD - Vehicle
Make Drp Dwn I
X
TOTAL
Exhibit C
Installation
Installation
Installation
1$
$
$700
$1,400
$
$1,400
1$3,500
Release Date: 9/18/011
Due Date: 10/10/01
Application Modules Solution Class Description &
and Components Prop Location
'X'
4.3.2 Custom Development
Exhibit C
City of San Rafael Vendor:
Administrative Software Cost Proposal Sun Ridge Systems
Training
OR
Travel Costs
On Site Training Off Site Training for On -Site Training
Class Rate Per Max # Class Rateer Tri Per
P P
Days Class I Students Students Days I Student Day Total Mtls # Trips I Costs I Diem TOTAL
Is
Is
X
A. FD - Cross Staff
B. FD - Equip
Move -up
X
C. FD - Vision
Interface
X
D. FD - PROQ&A
X
Intfc
E. FD - Station
X
Printers
F. FD - Paging
X
Interface
G. FD - Reflex I
X
Time
H. PD - CAD Wkst I
X
Notif.
I. PD - CAD Keybrd I
X I
RP Valid
J. PD - Property IDI
X I
Code
K. PD - Mobile I
X
continuous stat
L. PD - CAD I
X
Incident Refresh
M. PD - Vehicle
Make Drp Dwn I
X
1TOTAL
Exhibit C
City of San Rafael Vendor:
Administrative Software Cost Proposal Sun Ridge Systems
Training
OR
Travel Costs
On Site Training Off Site Training for On -Site Training
Class Rate Per Max # Class Rateer Tri Per
P P
Days Class I Students Students Days I Student Day Total Mtls # Trips I Costs I Diem TOTAL
Is
Is
Release Date: 9/18/2001 Public Safety Information System Cost Proposal
RFP Response Form
Due Date: 10/10/2001 Feature/Function Checklist
Subsystem Feat # Description
Feature/Function Checklist
RF4a
Vendor:
Sun Ridge Systems
Vendor Project
Rating Compl. Cost
Exhibit D1
Page 1 of 35
I Release Date:
9/18/2001
Public Safety Information System Cost Proposal
Vendor: I
I
RFP Response Form
Sun Ridge Systems
Due Date:
10/10/2001
Feature/Function Checklist
Vendor Project
Subsystem
Feat #
Description
Rating
Compl. Cost
General
1.1
All applications will run over an IP-based NT network environment.
3
3
JGeneral
1.2
Common user interface formats between modules and applications
3
3
JGeneral
1.3
System supports cross-application views of database information
3
3
General
1.4
System supports native graphical user interface at the workstation
3
3
General
1.5
System supports non-redundant data entry
3
3
General
1.6
System supports on-line, context sensitive help with local annotations
3
3
JGeneral
1.7
System supports secure, remote dial-in and/or VPN vendor support
3
3
General
1.8
Reports and other outputs can be printed on any network printer
3
3
General
1.9
Vendor supports scalable licensing provisions
3
0
General
1.10
Source code included
2
0
General
1.11
Undo capability on all data entry screens
2
3
General
1.12
System Uses industry standard RDBMS, ODBC compliant database engine
3
3
General
1.13
System includes Web enabled applications
2
0
General
1.14
System supports Import/Export capability
3
3
General
1.15
21st Century calendar accommodation
3
3
General
1.16
Application swapping with minimal keystrokes
3
0
All fields containing numbers (date, case number, booking numbers, etc) are
General
1.17
expandable at the user level to minimum of 25 characters per field
3
0
All fields requiring use of free form description by the user accommodate unlimited
General
1.18
number of characters
3
0
General
1.19
System allows user to add, update, delete code section fields
3
3
System links single name, based on soundex, if associated with multiple addresses
General
1.20
in multiple reports/supplements
3
3
General
1.21
System has "merge" capabilities for records based on:
General
1.22
name similarities identified by soundex
3
3
General
1.23
same or similar DOB
3
3
General
1.24
same or similar address
3
3
lGeneral
1.25
same or similar case number
3
3
JGeneral
1.26
same identifying numbers (SSN#, FBI number, CII, etc.)
3
3
General
1.27
System allows user to define mandatory fields in all reports
3
Vendor provides data dictionary to facilitate search of any database in the system for
General
1.28
use with custom report generation software
3
3
System Support provides annual updates for code tables (penal code, vehicle code,
General
1.29
etc.)
2
3
System accommodates one system administrator and one alternate administrator
General
1.30
simultaneously
3
3
General
1.31
System accommodates drop down lists or ability to type in free form description for:
Exhibit D1
Page 2 of 35
I Release Date:
9/18/2001
Public Safety Information System Cost Proposal
Vendor: I
I
RFP Response Form
Sun Ridge Systems
Due Date:
10/10/2001
Feature/Function Checklist
Vendor Project
Subsystem
Feat #
Description
Rating
CompL Cost
General
1.32
street name
3
3
General
1.33
city name
3
3
General
1.34
state
3
0
System accommodates use of A.K.A's for locations within geo-file both streets and
General
1.35
businesses
3
3
System translates AKA's to proper name when selected (e.g.:SRPD=San Rafael
General
1.36
Police Department)
3
3
General
1.37
System can operate in single or multi jurisdictional environment.
3
3
System has the ability to track user access for add/change, delete/display records
General
1.38
with date, time, user name and device used.
3
3
General
1.39
System can print user access report based on user defined time/date parameters.
3
0
General
1.40
System supports word processing functions including:
General
1.41
spell check
3
3
General
1.42
grammar check
3
0
General
1.43
customizable dictionary (at user level)
3
3
System supports the use of color for color-coding for easily identifiable text and fields
General
1.44
as defined by the user
3
0
System allows simultaneous use of the records database by an unlimited number of
General
1.45
users, to the extent provided by the agency hardware
3
3
General
1.46
System requires little or no computer experience to use the system
3
3
System provides the exact emulation of official state incident, arrest and
General
1.47
DMV/Accident Report forms, including allowance for on-line sketches
3
0
General
1.48
System supports future implementation of AFIS fingerprint imaging systems
2
1
System provides an automatic record history in RMS, allowing user the option to use
General
1.49
past contact information with a keyboard command or mouse click
3
3
General
1.50
System allows user to print any CAD or RMS screen
3
3
General
1.51
System includes an integrated e-mail system accessible through CAD and RMS
3
3
General
1.52
System allows agency to define format of incident and case number
3
3
System supports ability to maintain on-line user-defined, agency-specific
General
1.53
documentation and procedures
3
3
System supports ability to track User ID and revision dates when on-line user
General
1.54
documentation is revised/changed
3
0
System allows for on-line context-sensitive help features and provide the user with
the ability to ac-cess directly on the screen help information regarding the operation
General
1.55
in progress
3
3
Exhibit D1
Page 3 of 35
Release Date:
9/18/2001
Public Safety Information System Cost Proposal
Vendor:
RFP Response Form
Sun Ridge Systems
Due Date:
10/10/2001
Feature/Function Checklist
Vendor Project
Subsystem
Feat #
Description
Rating
Compl. Cost
A full set of user documentation is available in English detailing the functionality of
each application. User documentation is in narrative form and should be
understandable to non-technical users. Also, an on-line version of this
documentation is desired to allow key word searching to facilitate location of the
needed text. Current documentation describing systems design, operations,
troubleshooting, and performance tuning should be made available to the systems
General
1.56
administrator.
3
3
General
1.57
System supports redundant servers for high availability
3
3
General
1.58
System supports automatic, on-line data recovery
3
0
System hardware, operating system, applications and backup subsystem all support
General
1.59
fully automated, unattended backups
3
3
Backup subsystem supports network backup of multiple servers, databases, and
General
1.60
applications
3
0
General
1.61
All databases are compliant with open system standards (ODBC)
3
3
General
1.62
All databases use the relational database model
3
3
General
1.63
Data dictionaries and schema information are provided to client for all databases
3
0
General
1.64
System supports remote dial-up software diagnostics
3
3
General
1.65
System supports remote dial-up software update
3
3
Security
1 2.1
ISystem allows system administrator to enable and disable fields.
3
0
I
Securrity authorizations are definable for individual users or groups of users, orSecuri
1workgroup
ty
2.z
areas.
3
3
Security
2.3
Security authorizations are definable by a specific network device
2
3
Security authorizations are definable for modules. Screens inherit the security
Security
2.4
properties of the modules to which they belong
3 1
3
Security
1 2.5
IThe security system will control access to functions within modules
3
3
Access to information maintained within a workgroup will be controlled by function so
Security
2.6
that users from other workgroups can access the information only if authorized
3
3
System security supports a multi jurisdiction law en-forcement environment including
Security
2.7
the ability to define intra-jurisdiction access
3
3
Security
1 2.8
IThe query tools use the underlying database to validate user access
3
3
I
All data extraction is subject to the same security restrictions governing database
Security
2.9
access as defined in the security provisions for users of the system
3
0
1
All system access is initiated upon entry and validation of a user identification number
Security
2.10
and password
3
3
Security
2.11
1Passwords are user changeable
3
3
Security
2.12
Passwords can be modified by the System Administrator
3
3
Exhibit D1
Page 4 of 35
Release Date: 9/18/2001 Public Safety Information System Cost Proposal
RFP Response Form
Due Date: 10/10/2001 Feature/Function Checklist
Subsystem
Security
Security
Security
Security
CAD
CAD
CAD
CAD
CAD
CAD
CAD
CAD
CAD
CAD
CAD
CAD
CAD
Feat #
2.13
2.14
2.15
2.16
3.1
3.2
3.3
3.4
3.5
3.6
3.7
3.8
3.9
3.10
3.11
3.12
3.13
CAD
3.14
CAD
3.15
CAD
3.16
CAD
3.17
CAD
3.18
CAD 3.19
CAD 3.20
CAD 3.21
CAD 1 3.22
Description
The printing of a record involving criminal history information requires the entry and
capture of log information including the purpose of the printing, recipient or
destination, date, time, report number, and requestor.
System security restrictions are applied regardless of data storage location
Network security restrictions are an integral part of the application security
System records all changes of the security profile to a audit log
System differentiates addresses within and outside jurisdiction, alerting operator
when address is outside jusidiction
System allows user to define screen layout
System allows administrator to define required screens
System accomodates multiple agencies within the same geographic area (City Fire,
Fire District, and City Police)
System transfers dispatch times seamlessly from CAD to RMS after call is closed.
(System accommodates pre -selected rosters to "shift on" and "shift off' at specific
hours and days
System allows dispatcher to modify any pre -selected rosters at any time
System can accommodate the use of 1 or 2 display monitors
System associates common place names with addresses automatically
System utilizes drop-down menus for designated fields to ensure consistent data
entry
System utilizes soundex for entries in all master indexes 1
(System is capable of automatically populating call fields with ANI/ALI data at
dispatcher's discretion
System allows dispatcher to enter call for service without ANI/ALI data
System differentiates between incident location and location from where the call
originates
(System can automatically creates a new incident from the ANI/ALI data
System allows user to define programmable function keys
System allows authorized user to re -assign beats for on -duty personnnel
JSystem includes mapping software interface 1
iSystem produces "forced call" report for addresses used that are not recognized by I
the geo-file
(System allows use of A.K.A.'s and prints out full name in appropriate field (e.g.
abbreviated business names, landmarks or street names)
System recognizes intersections when entered with either street first j
(System allows calltaker to enter highway locations without street information (e.g.
Hwy 580 at Bellam)
Vendor: I
Sun Ridge Systems
Vendor Project
Rating Compi. Cost
3 0
3 3
3 3
2 0
3 3
3 0
3 0
3 3
3 3
2 0
3 0
3 3
3 3
3 3
3 0
3 3
3 3
3 3
3 3
3 0
3 3
2 0
3 3
3 3
3 3
3 3
Exhibit D1 Page 5 of 35
Release Date:
9/18/2001
Public Safety Information System Cost Proposal
Vendor Project
RFP Response Form
Due Date:
10/10/2001
Feature/Function Checklist
Subsystem
Feat #
Description
3
3
System automatically posts beat and zone information on call for service based on
CAD
3.23
geo-file
3
3
System provides closest cross streets including block number when address is
CAD
3.24
entered
CAD
3.25
System allows user to begin call for service from any field
3
3
System does not require user to close a call for service before opening a subsequent
CAD
3.26
one
CAD
3.27
System allows dispatcher to re -open a closed call for service
3
System notifies user of possible duplicate when call for service has already been
CAD
3.28
started
3 I
System automatically stamps time/date/dispatcher ID for each comment line on call
CAD
3.29
for service
CAD
I 3.30
System automatically stamps time/date/dispatcher ID when a closed call is re -opened
CAD
I 3.31
System accommodates unlimited number of comment lines for any call for service
CAD
3.32
ISystem notifies user of hazards associated with persons and/or addresses.
CAD
I 3.33
ISystern allows user to update hazard or safety information with a time/date stamp
ISystem allows multiple users to read comments on calls for service as they are
CAD
3.34
posted
I
ISystem allow multiple users to add comments to any call for service whether open or
CAD
3.35
closed I
CAD
3.36
ISystem posts comments on call for service by most recent entry first
I
System allows user to correct errors within any field without deleting other information
I
CAD
3.37
in that field
CAD
3.38
ISystem allows user to dispatch multiple units simultaneously
1System allows dispatcher to re -assign primary unit and back up units to a call for
CAD
3.39
service at any time
1System allows dispatcher to interrupt unit's assignment and re -assign the unit to
CAD
3.40
another call
CAD
I 3.41
System requires a mandatory disposition code in order to close a call for service
System automatically returns a call for service to the "pending" queue if the
CAD
3.42
assignment is interrupted and an unit is re -assigned
CAD
3.43
System allows user to change priority of call for service at any time j
System allows dispatcher to add units to an incident when the unit has responded on
CAD
3.44
their own.
Vendor: I
i
Sun Ridge Systems
Vendor Project
Rating
CompL Cost
3
3
3
0
3
3
3
3
3
3
3
3
3
3
3
3
3
3
3
3
3
3
3 I
3
3 I
3
3
0
3
3
3
3
3 I
3
3 I
3
I
3 13
3 13
3
3
3 I
3
Exhibit D1
Page 6 of 35
Release Date:
9/18/2001 Public Safety Information System Cost Proposal
Vendor: I I
RFP Response Form
Sun Ridge Systems
Due Date:
10/10/2001 Feature/Function Checklist
Vendor Project
Subsystem
Feat # Description
Rating CompL Cost
CAD
3.45 System tracks self-initiated activity and assigned calls for service
3 3
System uses the original times stamped on self-initiated call if the status of the call
changes or escalates (e.g. traffic stop turns into D.U.I. Arrest - time of traffic stop is
CAD
3.46 used)
3 3
CAD
3.47 System prompts dispatcher with recommended units based on unit location
2 0
CAD
3.48 System prompts dispatcher with recommended units based on beat and zone tables
3 3
CAD
3.49 System recommends fire units based on location of call and type of call
3 3
CAD
3.50 System is capable of recommending closest unit based on AVL data
2 0
CAD
3.51 System retains incident data even if no units respond
3 3
CAD
3.52 System adjusts recommended response is units are not in their home station
3 3
System differentiates when a fire unit is in station versus in the area of a station so
CAD
3.53 that they can be appropraitely alerted
3 0
System supports cross staffing of fire units. Example — a residential structure fire,
which calls for 2 Engines and a Truck — The rsponse order for engines should be
scanned. If the first engine that is available is one of the cross staffed units the
engines should be picked by the CAD system first, then the truck, and since Engine
57 would be the first engine the CAD system should associate that Truck 57 is not
available due to the fact that its staffing went on the engine. Conversely, if the first
engine that is available is NOT one of the cross staffed units the truck should be
picked by the CAD system first, then the engines. Example 2 — a paramedic rescue
call in Fire Station 6's area, which calls for an Engine and Rescue, while Rescue 56
and Rescue 50 are already on other calls — the Rescue should be picked by the CAD
system first, then the engine, and since Rescue 562 would be the only Rescue left
the CAD system would pick it and then should associate that Engine 56 is not
CAD
3.54 available due to the fact that its staffing went on the Rescue.
3 2 $ 4,000
System must be able to maintain adequate coverage due to the geographic barriers
stated above by recommending to the dispatch to move a company to another
station, even though it is not being dispatched directly to the scene of a call.
Example — Engine 58 is on an "assist" call, when Engine 57 and Rescue 56 get
dispatched to a medical call, in addition to the recommended units of Engine 57 and
Rescue 56 to the call, the dispatcher should have recommended to them to have
CAD
3.55 Engine 52 move to Fire Station 7.
3 0
Exhibit D1
Page 7 of 35
Release Date:
9/18/2001
Public Safety Information System Cost Proposal
Vendor: I
I
RFP Response Form
Sun Ridge Systems
Due Date:
10/10/2001
Feature/Function Checklist
Vendor Project
Subsystem
Feat #
Description
Rating
CompL Cost
Fire CAD will export call information to a Fire Records Management system that
includes at least — the assigned Fire Incident number, how the call was received, the
final location of the call, the disposition of the call, all units assigned, and their
CAD
3.56
associated times, all "milestone" times such as "under control" or "all clear'.
3
0
CAD
3.57
System allows dispatcher to over -ride recommended unit with single keystroke
3
0
System imports information from V11 Medical Priority Software produced by
CAD
3.58
NAEMD/Medical Priority
2
2
System supports multiple agencies and will assign unique incident numbers to each
CAD
3.59
agency based on their response
3
0
CAD
3.60
System maintains separate incident numbers for each agency
3
0
CAD
3.61
System automatically assigns incident numbers sequentially for each agency
3
0
CAD
3.62
System can assign incident numbers for each agency in a multi -agency response
3
0
System includes a field for recording a county assigned Ambulance Order Number
CAD
3.63
per incident
3
0
System can exchange call information and unit status with PRC CAD (County
CAD
3.64
Communications)
3
0
System integrates with a message switch which integrates a Motorola Gold Elite
CAD
3.65
MOSCAD alerting system
3
2
System can automatically send alpha -numeric pages with specifc dispatch
CAD
3.66
information
3
2
System allows two officers to be assigned to one unit and allows user to assign call
CAD
3.67
for service to one of those officers (not both) at any time
3
3
System allows dispatcher to cross-reference calls for service regardless of date of
CAD
3.68
occurrence
3
3
CAD
3.69
System provides space for unlimited emergency contacts in premise information
2
3
CAD
3.70
System includes fields in emergency contact information for:
CAD
3.71
name(s) - Unlimited
3
3
CAD
3.72
phone numbers (unlimited)
3
3
CAD
3.73
alarm company name and phone number
3
3
System can import emergency contact information from secondary source (Business
CAD
3.74
License Application)
3
0
CAD
3.75
System notifies user of prior contacts associated with addresses.
3
3
CAD
3.76
System prompts dispatcher with name of tow company on rotation basis.
3
3
CAD
3.77
System allows dispatcher to select tow company not in order of rotation
3
3
CAD
3.78
System supports ability to display electronic maps
2
0
Exhibit D1
Page 8 of 35
Release Date:
9/18/2001
Public Safety Information System Cost Proposal
0
Vendor Project
RFP Response Form
Due Date:
10/10/2001
Feature/Function Checklist
Subsystem
Feat #
Description
CAD
3.79
System electronic maps include:
CAD
3.80
unit locations
CAD
3.81
all locations for calls for service
CAD
3.82
text directions to location
CAD
3.83
System supports the ability to zoom in and zoom out while viewing electronic maps
3
3
System support the ability to display electronic photographs such as digitized mug
CAD
3.84
shots
3
3
System allows user to move around CAD screen in random order with single
CAD
3.85
keystroke, tab, or mouse click
CAD
3.86
System generates an audible tone for pending calls
CAD
3.87
System automatically time stamps every call for service with:
CAD
3.88
time call is received
CAD
3.89
time call is dispatched
CAD
3.90
time unit arrives
CAD
3.91
time call is cleared
CAD
3.92
time rescue unit departs for hospital
CAD
3.93
time rescue unit apprives at hospital
CAD
3.94
System accomodates recording receiving hospital
CAD
3.95
System accomodates recording transport mileage departure
CAD
3.96
System accomodates recording transport mileage arrival
CAD
3.97
System supports GPS/AVL integration
System can be configured to require specific fields to be completed before the call is
CAD
3.98
dispatched
System allows user to search and view closed calls for service without exiting CAD
CAD
3.99
screen
System allows user to search and view reports from the RMS without exiting CAD
CAD
3.100
screen
System allows user to view all calls for service, active and pending and all officer
CAD
3.101
activity in one status window
CAD
3.102
System tracks both "calls received as" and "calls cleared as" independently
CAD
3.103
System supports ability to purge hazard information by date
CAD
3.104
System provides a checkbox field for reporting party notification
CAD
3.105
System allows user to search unit activity without leaving CAD screen
CAD
3.106
Pending calls will be displayed with highest priority first
CAD
3.107
System supports timers for each type of call
CAD
3.108
System supports timers for specific units
Vendor: I
I
Sun Ridge Systems
0
Vendor Project
Rating
CompL Cost
2
0
2
0
2
0
2
0
1
0
3
3
2
3
3
3
3
3
3
3
3
3
3
3
3
3
3
3
3
3
3
3
2
0
3
0
3
3
3
3
3
3
3
0
3
0
2
0
3
3
3
3
3
0
3
0
Exhibit D1 Page 9 of 35
Release Date:
9/18/2001
Public Safety Information System Cost Proposal
Vendor: I
I
RFP Response Form
Sun Ridge Systems
Due Date:
10/10/2001
Feature/Function Checklist
Vendor
Project
Subsystem
Feat #
Description
Rating
Compl.
Cost
System can display recommended units immediately immediately after call is entered
CAD
3.109
without any additional steps by the dispatcher
3
3
System accomodates recording, with date and time stamp, events without creating
CAD
3.110
an incident
3
3
System accomodates printing incident information to remote station printers on the
CAD
3.111
same network
3
2
$ 300
System records reflex time (difference between time dispatched and time to respond)
CAD
3.112
for Fire Units
3
2
$ 700
CAD
3.113
System notifies Dispatcher A when Dispatcher B updates an incident
3
2
$ -
CAD
3.114
Dispatcher can choose Reporting Party validation options using the keyboard
3
2
$ 400
System refreshes radio log on the incident screen automatically when an item is
added by another dispatcher without requiring user to close and re -open incident
CAD
3.115
window
3
2
$ 1,500
Police Case
Management
4.1
System allows user to retrieve submitted report before it is approved
3
3
Police Case
System allows supervisor unlimited opportunities to return report to writer for
Management
I 4.2
correction
3
0
Police Case
Management
4.3
System allows user to link all reports and supplements related to one case
3
3
Police Case
System tracks all report returns by office and type of correction based on user
Management
I 4.4
defined time periods
3
0
Police Case
Management
4.5
System allows user with appropriate access to purge tracking systems.
3
0
Police Case
I
System allows user with appropriate access to complete UCR classification before
Management
4.6
the report is approved
3
3
Police Case
Management
4.7
System allows user to print a report at any level of completion
3
3
Police Case
Management
4.8
System can automatically send reports to specific mailboxes based on report type
3
0
Police Case
Management
4.9
System can list case assignments by officer regardless of status of report
3
3
Police Case
Management
4.10
System can list case assignments by variety of criteria, individually or in combination:
Police Case
Management
4.11
by crime
3
3
Police Case
Management
4.12
by time period (time of day as well as date)
3
3
Exhibit D1
Page 10 of 35
Release Date:
Due Date:
Subsystem
Police Case
Management
Police Case
Management
Police Case
Management
Police Case
Management
Police Case
Management
Police Case
Management
Police Case
Management
Police Case
Management
Police Case
Management
Police Case
Management
Police Case
Management
Police Case
Management
Police Case
Management
Police Case
Management
Police Case
Management
Police Case
Management
Police Case
Management
Police Case
Management
Police Case
Management
9/18/2001 Public Safety Information System Cost Proposal
RFP Response Form
10/10/2001 Feature/Function Checklist
Feat # Description
4.13 by officer
4.14 by report status
4.15 by report types (felony, misdemeanor)
4.16 by location and/or address
System allows multiple users to copy duplicate information from another users
4.17 reports, regardless of status (unapproved, approved, etc)
4.18 System allows users to view each other's case assignments
4.19 System has a case notes module that is linked to appropriate case numbers
4.20 System allows supervisors to view all reports regardless of status
System allows supervisors to assign cases to officer/investigator within his/her
4.21 division
System allows user to print summary report of all assigned cases for a division based
4.22 on user definable time parameters
System allows user to print summary report of case dispositions based on user
4.23 defined time parameters
System collates and prints summary report of crime statistics by division with
4.24 comparison statistics within user defined time parameters
System automatically applies solvability factors to reports, based on user defined
4.25 tables
System includes printable audit trail for every change made to an individual record,
4.26 including date and time of change, and person making the change
System includes 'synopsis' function enabling user to view the crime cited for each
4.27 individual case number when assigning it, without going to the report
System includes a function that allows user to 'attach' a note or memo to a report,
4.28 showing what corrections need to be made
System allows user to close a report that has no further leads through case notes,
4.29 rather than appending a one line supplement narrative
System sends report to be approved to a general supervisory'mailbox' for access by
4.30 any supervisor
4.31 System allows supervisor to approve reports in the field and in the office.
Vendor: I I
Sun Ridge Systems
Project
Cost
Exhibit D1 Page 11 of 35
Vendor
Rating
Compl.
3
3
3
3
3
3
3
3
3
3
2
3
2
3
3
3
3
0
3
0
2
3
2
0
2
3
3
3
3
3
3
0
2
3
3
0
3
0
Project
Cost
Exhibit D1 Page 11 of 35
I Release Date:
9/18/2001
Public Safety Information System Cost Proposal
Vendor:
RFP Response Form
Sun Ridge Systems
Due Date:
10/10/2001
Feature/Function Checklist
Vendor Project
(Subsystem
Feat#
Description
Rating
CompL Cost
Case
System allows approved users to assign and re-assign reports at any point in report
(Police
Management
4.32
completion
3
3
Police Case
System allows supervisor to approve supplemental reports before primary report has
Management
4.33
been submitted
3
0
Police Case
System allows user to define which report is primary when case number has multiple
Management
4.34
reports linked
3
0
Police Case
Management
4.35
System uses agency-defined, common langauge for case status codes
3
3
Police Case
System allows users to query status of any report by officer, date or any field within
Management
4.36
the report
3
3
Interfaces
5.1
System interfaces with CLETS/NCIC with single keystroke
3
2
System allows user to utilize CLETS/NCIC screens without leaving CAD or RMS
Interfaces
5.2
Application
3
2
System automatically searches all CLETS/NCIC databases and local history with
Interfaces
5.3
single command
3
2
Interfaces
5.4
System allows user to print CLETS information
3
2
System accomodates 10-20 digits for wireless ANI/ALI and future enhanced wireless
Interfaces
5.5
location fields
3
3
Interfaces
5.6
System will verify address locations against an established city-wide geobase
3
3
Interfaces
5.7
System will allow non-verified address locations to be entered
3
3
Interfaces
5.8
System will generate a report of unverified address locations
3
3
Interfaces
5.9
System is fully compliant with ESRI SDE (GIS)
3
0
Police Mobile
Computing
6.1
System supports deployment on fixed desktop workstations
3
3
Police Mobile
Computing
6.2
System supports LAN-based or workstation-based installation/execution
3
3
Police Mobile
System supports deployment on laptop computers and specialized mobile data
Computing
6.3
computers (MDC) that are PC -compatible
3
3
Police Mobile
Computing
6.4
System automatically notifies dispatchers and field supervisors of MDC logins
3
3
Police Mobile
System supports ability to automatically update unit roster information in CAD based
Computing
6.5
on MDC logins
3
3
(Police Mobile
System supports electronic messaging from Dispatch to one or more MDCs
Computing
6.6
simultaneously
3
3
Police Mobile
System supports electronic messaging from one or more network workstations to
Computing
6.7
one or more MDCs simultaneously
3
3
Police Mobile
System supports electronic messaging from one or more MDCs to one or more
Computing
6.8
network workstations
3
3
Exhibit D1 Page 12 of 35
Release Date:
9/18/2001
Public Safety Information System Cost Proposal
RFP Response Form
Due Date:
10/10/2001
Feature/Function Checklist
Subsystem
Feat #
Description
Police Mobile
Computing
6.9
System supports electronic messaging between two or more MDCs
Police Mobile
Computing
6.10
System supports the ability to notify MDC user of:
Police Mobile
Computing
6.11
number of messages received
Police Mobile
Computing
6.12
number of messages waiting
Police Mobile
Computing
6.13
messages acknowledged
Police Mobile
Computing
6.14
number and priority of queued messages
Police Mobile
System allows user access to all user originated messages for user -defined period of
Computing
6.15
time
Police Mobile
System records all messages for period of time defined by the user for audit
Computing
6.16
purposes based on:
Police Mobile
Computing
6.17
date
Police Mobile
Computing
6.18
time of day
Police Mobile
Computing
6.19
sender
Police Mobile
Computing
6.20
recipient
Police Mobile
Computing
6.21
System supports programmable functions keys in CAD and MDCs for:
Police Mobile
Computing
6.22
in-service/Log on
Police Mobile
Computing
6.23
enroute/unit responding
Police Mobile
Computing
6.24
enroute to station
Police Mobile
Computing
6.25
traffic stop
Police Mobile
Computing
6.26
on view
Police Mobile
Computing
6.27
arrived/unit on -scene
Vendor: I I
Sun Ridge Systems
Vendor Project
Rating Compl. Cost
3 3
2 0
2 3
2 3
2 3
3 3
3 0
3 3
3 3
3 3
3 3
3 3
3 0
3 0
3 0
3 3
Exhibit 01 Page 13 of 35
Release Date:
9/18/2001
Public Safety Information System Cost Proposal
Vendor: I
I
RFP Response Form
Sun Ridge Systems
Due Date:
10/10/2001
Feature/Function Checklist
Vendor Project
Subsystem
Feat #
Description
Rating
CompL Cost
Police Mobile
Computing
6.28
meal/break
3
0
Police Mobile
Computing
6.29
in-service but busy
3
0
Police Mobile
Computing
6.30
in service/report writing
3
0
Police Mobile
Computing
6.31
clear/available
3
3
Police Mobile
Computing
6.32
out of service
3
3
Police Mobile
Computing
6.33
log -off
3
3
Police Mobile
Computing
6.34
emergency
3
3
Police Mobile
Computing
6.35
enroute to jail
3
0
Police Mobile
Computing
6.36
arrived at jail
3
0
Police Mobile
Computing
6.37
vehicle inquiry
3
3
Police Mobile
Computing
6.38
display message
3
3
Police Mobile
Computing
6.39
person wanted inquiry
3
3
Police Mobile
System provides audible alert to dispatch and all MDCs when unit MDC operator
Computing
6.40
presses emergency key on MDC
2
0
Police Mobile
Computing
6.41
System archives all messaging traffic between dispatch and units
3
3
Police Mobile
Computing
6.42
System archives all messaging traffic between units
3
3
Police Mobile
System provides recipient with ability to acknowledge receipt of message from unit
Computing
6.43
MDC with one keystroke
2
3
Police Mobile
System provides unit status inquiry for MDC operator to find the status of another unit
Computing
6.44
by:
Police Mobile
Computing
6.45
unit ID
3
3
Police Mobile
Computing
6.46
case number
2
0
Exhibit D1 Page 14 of 35
Release Date:
9/18/2001
Public Safety Information System Cost Proposal
Vendor:
RFP Response Form
Sun Ridge Systems
Due Date:
10/10/2001
Feature/Function Checklist
Vendor Project
Subsystem
Feat #
Description
Rating
Compi. Cost
Police Mobile
Computing
6.47
System sends all incident information from CAD to assigned unit MDCs including:
Police Mobile
Computing
6.48
initial assignment
3
3
Police Mobile
Computing
6.49
all pending assignments
3
0
Police Mobile
Computing
6.50
call upgrades
3
0
Police Mobile
Computing
6.51
hazards/alerts
3
3
Police Mobile
Computing
6.52
CAD comments
3
3
Police Mobile
System automatically sends hazard/alert information for the incident location to the
Computing
6.53
assigned unit as part of the incident
2
3
Police Mobile
System provides the MDC operator a method of viewing hazard information for
Computing
6.54
nearby areas that may effect the response
2
0
Police Mobile
Computing
6.55
System allows the MDC operator to initiate an incident (call for service)
2
0
Police Mobile
System allows the MDC operator to call up and append text comments to active or
Computing
6.56
inactive call for service
2
3
Police Mobile
System automatically updates CAD if any additional information is added to calls for
Computing
6.57
service from unit MDCs
3
3
Police Mobile
Computing
6.58
System allows the MDC operator to close out an incident and time/date stamps
3
3
Police Mobile
Computing
6.59
System supports MDCs inquiries into:
Police Mobile
Computing
6.60
CLETS
3
3
Police Mobile
Computing
6.61
NCIC
3
3
Police Mobile
Computing
6.62
local history (database)
3
3
Police Mobile
Computing
6.63
System supports ability to complete multiple inquiries with a single entry in CLETS
3
3
Police Mobile
System support the ability for the MDC user to manually select which databases are
Computing
6.64
to be searched
2
0
Police Mobile
Computing
6.65
System supports searches by:
Exhibit D1
Page 15 of 35
Release Date:
9/18/2001
Public Safety Information System Cost Proposal
Vendor:
RFP Response Form
Sun Ridge Systems
Due Date:
10/10/2001
Feature/Function Checklist
Vendor Project
Subsystem
Feat #
Description
Rating
Compl. Cost
Police Mobile
Computing
6.66
"wild card"
2
0
Police Mobile
Computing
6.67
search string
2
0
Police Mobile
Computing
6.68
soundex or sound-alike algorithm
2
3
Police Mobile
Computing
6.69
date of birth of date ranges
2
0
Police Mobile
Computing
6.70
any field or combination of fields
2
0
Police Mobile
Computing
6.71
System supports GPS/AVL integration
2
0
Police Mobile
Computing
6.72
System support ability to invoke a function on MDC by:
Police Mobile
Computing
6.73
keyboard commands
3
3
Police Mobile
Computing
6.74
function keys
3
3
Police Mobile
Computing
6.75
touch screen
3
3
Police Mobile
Computing
6.76
pen-based
1
0
Police Mobile
Computing
6.77
point and click (drop down menus)
3
3
Police Mobile
Computing
6.78
System supports ability to validate data entry based on:
Police Mobile
Computing
6.79
date
2
3
Police Mobile
Computing
6.80
data type (alpha/numeric)
2
3
Police Mobile
Computing
6.81
tables
2
3
Police Mobile
Computing
6.82
valid address (based on geo-file)
2
0
Police Mobile
System allows MDC operator to "force" address into self-initiated call for service that
Computing
6.83
is not in geo-file
2
0
Police Mobile
Computing
6.84
System prints list of "forced addresses" initiated by MDC operators
2
0
Exhibit D1
Page 16 of 35
Release Date:
9/18/2001
Public Safety Information System Cost Proposal
Vendor:
RFP Response Form
Sun Ridge Systems
Due Date:
10/10/2001
Feature/Function Checklist
Vendor Project
Subsystem
Feat #
Description
Rating
CompL Cost
Police Mobile
System supports ability for MDC to easily toggle between report writing and other
Computing
6.85
functions with single key stroke or button
3
0
Police Mobile
System allows user to design and change screen layout for MDCs (including function
Computing
6.86
button size and locations)
1
0
Police Mobile
System supports the ability for the agency to lock down all functions and screen
Computing
6.87
layouts in MDCs and PC workstations
3
0
Police Mobile
Computing
6.88
System supports ability to maximize the use of the following options:
Police Mobile
Computing
6.89
color
3
3
Police Mobile
Computing
6.90
reverse video
2
0
Police Mobile
Computing
6.91
audible messages notification
2
3
Police Mobile
Computing
6.92
audible tones
3
3
Police Mobile
System supports retrieval of agency specific information from each MDC (e.g. hot
Computing
6.93
sheet, beat information, etc)
2
0
Police Mobile
System supports ability to accommodate future capabilities, including but not limited
Computing
6.94
to:
Police Mobile
Computing
6.95
query of new databases
2
3
Police Mobile
Computing
6.96
Image transmission
2
3
Police Mobile
Computing
6.97
fingerprint reader
2
3
Police Mobile
Computing
6.98
bar-code reader
2
3
Police Mobile
Computing
6.99
magnetic strip reader
2
3
Police Mobile
Computing
6.100
System supports use of CDPD technology
3
3
Police Mobile
Computing
6.101
System allows report to be written, edited, approved from any MDC
3
0
Police Mobile
System allows the user to transmit a report regardless of status by wireless transfer
Computing
6.102
or diskette from the MDC
3
3
Police Mobile
System continuously updates MDCs with until and call status without user
Computing
6.103
intervention
3
2 $ 3,000
Exhibit D1 Page 17 of 35
Release Date:
Due Date:
Subsystem
Police
Property/Evidence
Police
Property/Evidence
Police
Property/Evidence
Police
Property/Evidence
Police
Property/Evidence
Police
Property/Evidence
Police
Property/Evidence
Police
Property/Evidence
Police
Property/Evidence
Police
Property/Evidence
Police
Property/Evidence
Police
Property/Evidence
Police
Property/Evidence
Police
Property/Evidence
Police
Property/Evidence
Police
Property/Evidence
Police
Property/Evidence
Police
Property/Evidence
Police
Property/Evidence
9/18/2001 Public Safety Information System Cost Proposal
RFP Response Form
10/10/2001 Feature/Function Checklist
Feat # Description
7.1 System allows user to define storage location tables within property room module
System provides the following fields for all property/evidence entries in reports and/or
7.2 supplements:
7.3 quantity of each item
7.4 make
7.5 model
7.6 serial number or owner applied number
7.7 brief free form description area
7.8 year
7.9 color
7.10 property tag number
7.11 original location (locker) used by officer
7.12 location within property room
7.13 UCR type
7.14 property status (stolen, safekeeping, etc.)
7.15 date property submitted
7.16 ID of officer submitting property
System automatically combines submitting officer ID number with individual
7.17 consecutive item numbering system for every item
System supplies field for date evidence/property collected (if different from date
7.18 submitted)
System shows sum total number of property/evidence items entered in each
7.19 report/supplement on property page
Vendor:
Sun Ridge Systems
Vendor Project
Rating Compl. Cost
3 3
3 3
3 3
3 3
3 3
3 3
3 3
3 3
3 3
3 3
3 3
3 3
3 3
3 3
3 3
3 0
3 3
3 3
Exhibit D1 Page 18 of 35
Release Date:
9/18/2001
Public Safety Information System Cost Proposal
RFP Response Form
Due Date:
10/10/2001
Feature/Function Checklist
Subsystem
Feat #
Description
System tallies total number of items for all reports/supplements associated with case
Police
number in property officer's module for each case number or reports/supplements
Property/Evidence
7.20
associated with that case number
System allows unlimited entries for chain of custody through free form entries or
Police
selections from user defined pop up menus, by mouse click or single keyboard
Property/Evidence
7.21
command
Police
System provides additional mandatory fields for special property entries on property
Property/Evidence
7.22
page of report including:
Police
Property/Evidence
7.23
Firearms: caliber
Police
Property/Evidence
7.24
barrel length
Police
Property/Evidence
7.25
make
Police
Property/Evidence
7.26
model
Police
Property/Evidence
7.27
type
Police
Property/Evidence
7.28
serial number
Police
Property/Evidence
7.29
finish
Police
Property/Evidence
7.30
Bicycles: Make
Police
Property/Evidence
7.31
Model
Police
Property/Evidence
7.32
Wheel Size
Police
Property/Evidence
7.33
Color
Police
Property/Evidence
7.34
Serial number of owner applied number
Police
Property/Evidence
7.35
Type (boy's, girls)
Police
Property/Evidence
7.36
Vehicles: make
Police
Property/Evidence
7.37
model
Vendor: I I
Sun Ridge Systems
Vendor Project
Rating CompL Cost
3 1
3 3
0
3 0
3 0
3 0
3 0
3 0
3 0
3 0
3 0
3 0
3 0
3 0
3 0
3 0
3 0
3 0
Exhibit D1 Page 19 of 35
Release Date:
9/18/2001
Public Safety Information System Cost Proposal
Vendor: I
I
RFP Response Form
Sun Ridge Systems
Due Date:
10/10/2001
Feature/Function Checklist
Vendor Project
Subsystem
Feat #
Description
Rating
Compl. Cost
Police
Property/Evidence
7.38
year
3
0
Police
Property/Evidence
7.39
color
3
0
Police
Property/Evidence
7.40
license plate number and/or VIN
3
0
Police
Property/Evidence
7.41
State
3
0
Police
Property/Evidence
7.42
description
3
0
Police
Property/Evidence
7.43
style (2 dr, 4dr)
3
0
Police
Property/Evidence
7.44
Boats: Propulsion Type
3
0
Police
Property/Evidence
7.45
make
3
0
Police
Property/Evidence
7.46
model
3
0
Police
Property/Evidence
7.47
registration number
3
0
Police
Property/Evidence
7.48
name of boat
3
0
Police
Property/Evidence
7.49
length
3
0
Police
Property/Evidence
7.50
hull composition
3
0
Police
Property/Evidence
7.51
hull number
3
0
Police
System provides fields for contact information for multiple owners of each item of
Property/Evidence
7.52
property including:
Police
Property/Evidence
7.53
owner's full name
3
3
Police
Property/Evidence
7.54
owner's street address
3
3
Police
Property/Evidence
7.55
owner's apartment number
3
3
Police
Property/Evidence
7.56
owner's city
3
3
Exhibit D1 Page 20 of 35
Release Date:
9/18/2001
Public Safety Information System Cost Proposal
Vendor Project
RFP Response Form
Due Date:
10/10/2001
Feature/Function Checklist
Subsystem
Feat #
Description
Police
3
3
Property/Evidence
7.57
owner's state and zip code
Police
Property/Evidence
7.58
owner's telephone contact information (unlimited entries)
Police
System allows user to note any restrictions for release of each item of property within
Property/Evidence
7.59
each report
Police
System provides "comments" area for user to note any special instructions for each
Property/Evidence
7.60
item of property
Police
System allows unlimited number of entries by one of more officers into property
Property/Evidence
7.61
module for any report or supplement
Police
System tracks property/evidence entered in any report or supplement for UCR
Property/Evidence
7.62
statistical reports by:
Police
Property/Evidence
7.63
UCR type
Police
Property/Evidence
7.64
dollar value
Police
Property/Evidence
7.65
property status (safekeeping, found, stolen, etc)
Police
Property/Evidence
7.66
description
Police
Property/Evidence
7.67
category (firearms, narcotics, etc.)
Police
Property/Evidence
7.68
quantity
Police
System prints inventory of all items submitted under a case number based on user
Property/Evidence
7.69
defined date range and individual criteria or in combination
Police
Property/Evidence
7.70
System provides archival and printable chain of custody form to record
Police
Property/Evidence
7.71
day and date property is moved
Police
Property/Evidence
7.72
time of day property is moved
Police
Property/Evidence
7.73
person who is moving property
Police
Property/Evidence
7.74
person who is receiving property
Police
Property/Evidence
7.75
person who is releasing property
Vendor: I
I
Sun Ridge Systems
Vendor Project
Rating
Compi. Cost
3
3
3
3
3
3
3
3
3
3
3 3
3 3
3 3
3 3
3 3
3 0
3 0
3 3
3 3
3 3
3 3
3 3
Exhibit D1 Page 21 of 35
Release Date:
9/18/2001
Public Safety Information System Cost Proposal
Vendor: I
RFP Response Form
Sun Ridge Systems
Due Date:
10/10/2001
Feature/Function Checklist
Vendor Project
Subsystem
Feat #
Description
Rating
CompL Cost
Police
Property/Evidence
7.76
date of move
3
3
Police
Property/Evidence
7.77
location of property at any time
3
3
Police
System summarizes activity in the property room based on user defined date range
Property/Evidence
7.78
and following individual criteria or combination including:
Police
Property/Evidence
7.79
locations availabe within property room (e.g. # of storage bins open or square feet)
3
0
Police
Property/Evidence
7.80
category of property/evidence stored (firearms, narcotics, etc.)
3
3
Police
Property/Evidence
7.81
number of pieces in each category received
3
0
Police
Property/Evidence
7.82
number of pieces of each category purged
3
0
Police
Property/Evidence
7.83
sum of pieces of received
3
0
Police
Property/Evidence
7.84
sum of pieces purged
3
0
Police
Property/Evidence
7.85
total pieces in property room
3
0
Police
System cross-references property entered in case report with pawn module and
Property/Evidence
7.86
'alerts' user to matches
3
3
Police
System allows property officer to update status of each item without effecting original
Property/Evidence
7.87
reports/supplements (for purging, releasing, moving through chain of custody, etc)
3
3
Police
System will print individual form letter addressed to property owners to notify them
Property/Evidence
7.88
property is available for release
2
0
Police
Property/Evidence
7.89
System will print receipt for owner to sign when property is released
3
0
Police
System provides field to enter "destruction or purge" date to assist property room
Property/Evidence
7.90
audit user defined date range
3
0
Police
Property/Evidence
7.91
System will print "destruction or purge" property list based on user defined date range
3
0
Police
Property/Evidence
7.92
System interfaces with standard bar-coding software
3
0
Police
System allows scanning of photographs of evidence and/or mugshots associated
Property/Evidence
7.93
with reports/supplements
2
0
Exhibit D1 Page 22 of 35
Release Date:
9/18/2001
Public Safety Information System Cost Proposal
Vendor:
RFP Response Form
Sun Ridge Systems
Due Date:
10/10/2001
Feature/Function Checklist
Vendor Project
Subsystem
Feat #
Description
Rating
Compl. Cost
System copies all property/evidence entered on case reports to separate summary
(Police
Property/Evidence
7.94
property module for easy reference
3
0
Police
System allows authorized user to move property/evidence within summary property
Property/Evidence
7.95
module and system copy information into individual case report
3
0
Police
Property/Evidence
7.96
System can compare lost/stolen items with found/pawn items in local history
2
0
Police
System accomodates SRPD's property numbering scheme (Officer initials plus item
Property/Evidence
7.97
number - MR1, MR2, TR1, TR2, etc.)
3
2 $ 1,200
System allows user to create, edit, print any activity log by any searchable field
Police RMS
8.1
including but not limited to:
Police RMS
8.2
case number
3
0
Police RMS
8.3
date parameters
3
0
Police RMS
8.4
type of incident/violation
3
0
Police RMS
8.5
location (beat, zone and/or street address)
3
0
Police RMS
8.6
time period
3
0
Police RMS
8.7
incident summary from case report
3
0
Police RMS
8.8
incident summary from CAD
3
0
Police RMS
8.9
disposition
3
0
Police RMS
8.10
officer(s) involved
3
0
Police RMS
8.11
parties involved
3
0
Police RMS
8.12
hazard information: weapons used, related vehicles, etc
3
0
System allows user to create, edit, print specific productivity lists for officers based on
Police RMS
8.13
user defined criteria
3
0
Police RMS
8.14
System provides pre -loaded productivity reports which can be saved as a file 1
3
1
Police RMS
8.15
System allows user to create, edit, print summary productivity reports I
3
3
JPolice RMS
1 8.16
System allows users to print calls for service based on user defined parameters +
3
3
1
System allows creation of custom statistical reports at user level based on data in
(combination
Police RMS
8.17
or selected individual criteria I
3 I
3
1
(System allows custom statistical reports to be saved as a file for future use by the
Police RMS
8.18
user
3 1
0
Police RMS
1 8.19
ISystem allows a business name to be entered as a victim in reports
3 1
3
Police RMS
1 8.20
1Systems allows user to define "role" category for persons or businesses
3
3
Police RMS
1 8.21
JSystem allows user to define M.O. characteristics for persons in any role 1
3 '
0
Police RMS
8.22
ISystem allows user to define M.O. characteristics for incidents 1
3
0
(System accommodates drop down lists or pop-up menus in abbreviations acceptable
Police RMS
8.23
for state reporting for:
Police RMS
8.24
1 gender 1
3
0
Exhibit D1 Page 23 of 35
Release Date:
9/18/2001
Public Safety Information System Cost Proposal
Vendor:
RFP Response Form
Sun Ridge Systems
Due Date:
10/10/2001
Feature/Function Checklist
Vendor Project
Subsystem
Feat #
Description
Rating
Compl. Cost
physical descriptor fields including but not limited to: hair color, eye color, race,
Police RMS
8.25
scars,marks,tattoos
3
3
Police RMS
8.26
UCR property types
3
3
Police RMS
8.27
vehicle description and type fields (color, make, model, etc.)
3
0
Police RMS
8.28
user defined report types (MH=mental health; GR=gang related)
3
3
Police RMS
8.29
court jurisdiction
3
3
Police RMS
8.30
relationship or "role" identification
3
3
Police RMS
8.31
crime field
3
3
Police RMS
8.32
firearm descriptors including but not limited to: caliber, model, make, color
3
0
System allows setting up solvability code file at the user level to weight probability
Police RMS
8.33
factors for any crime report
2
3
Police RMS
8.34
System's solvability code tables include:
Police RMS
8.35
name of the solvability factor
2
3
Police RMS
8.36
weight of the factor (numeric value)
2
3
Police RMS
8.37
description of the solvability factor
2
3
System supports searches and ad-hoc reporting based on following criteria
Police RMS
8.38
individually or in any combination:
incidents within geographic area of San Rafael and adjacent cities based on street
Police RMS
8.39
parameters
3
3
incidents within geographic area of San Rafael and adjacent cities based on date
Police RMS
8.40
range
3
3
incidents within geographic area of San Rafael and adjacent cities based on officer
Police RMS
8.41
or multiple officers identifying numbers
3
3
Police RMS
8.42
incidents within date parameters, including:
Police RMS
8.43
hourly
3
3
Police RMS
8.44
daily
3
3
Police RMS
8.45
monthly
3
3
Police RMS
8.46
quarterly
3
3
Police RMS
8.47
year to date
3
3
System supports ad-hoc reporting based on all user defined fields individually or in
Police RMS
8.48
combination
3
0
System allows user to select any individual case report from a list and open it from
Police RMS
8.49
the list
3
3
System allows user access to browse list of case reports and to move between the
Police RMS
8.50
reports by a keyboard command or mouse click.
3
3
System allows for saving all lists as a file within the vendor software and in word
Police RMS
8.51
processing software (e.g. Microsoft Word)
3
0
Exhibit D1
Page 24 of 35
Date:
9/18/2001
Public Safety Information System Cost Proposal
Vendor: I
I
IRelease
RFP Response Form
Sun Ridge Systems
Due Date:
10/10/2001
Feature/Function Checklist
Vendor Project
Subsystem
Feat #
Description
Rating
Compl. Cost
System supports the following fields and the ability to search for persons based on
Police RMS
8.52
the following criteria individually or in any combination:
Police RMS
8.53
soundex
3
3
Police RMS
8.54
with hyphenated last names
3
3
Police RMS
8.55
based on physical descriptors - individually or in combination:
3
3
Police RMS
8.56
height
3
3
Police RMS
8.57
weight
3
3
Police RMS
8.58
gender
3
3
Police RMS
8.59
race
3
3
Police RMS
8.60
date of birth or age
3
3
Police RMS
8.61
scars, marks, tattoos
3
3
Police RMS
8.62
eye color
3
3
Police RMS
8.63
hair color I
3
3
Police RMS
8.64
aliases or monikers I
3
3
Police RMS
8.65
hazard notes
3
3
Police RMS
8.66
report type (e.g. missing person, runaway, etc.)
3
0
Police RMS
8.67
based on individual's role (suspect, witness, arrestee, victim, etc)
3
0
Police RMS
8.68
person's residence address
3
3
Police RMS
8.69
person's business address
3
3
Police RMS
8.70
' person's residence telephone number 1
3
3
Police RMS
8.71
person's business telephone number
3
3
Police RMS
8.72
person's pager number
3
0
Police RMS
8.73
person's cellular phone number I
3
0
i
Police RMS
8.74
last name
3
3
Police RMS
8.75
first name
3 I
3
Police RMS
8.76
middle name or initial
3 +
3
Police RMS
8.77
suffix 1
3
0
1
(System supports the following fields and supports searches for persons based on
Police RMS
8.78
any government agency issued identifying number:
Police RMS
8.79
social security number 1
3
3
Police RMS
8.80
drivers license3
3
Police RMS
I
8.81
FBI number
3
3
Police RMS
I+
8.82
I jail booking number
3
0
Police RMS
8.83
i CII or other rap sheet numbers
3
3
Police RMS
8.84
CYA (for juveniles) I
3
3
Police RMS
8.85
other government issued tracking numbers 1
2
0
I
System supports the following fields and the ability to search for persons based on
Police RMS
8.86
M.O. criteria individually or in any combination: I
Exhibit D1
Page 25 of 35
Release Date:
Due Date:
Subsystem
Police RMS
Police RMS
Police RMS
Police RMS
Police RMS
Police RMS
Police RMS
Police RMS
Police RMS
Police RMS
Police RMS
Police RMS
Police RMS
Police RMS
Police RMS
Police RMS
JPolice RMS
Police RMS
Police RMS
Police RMS
Police RMS
Police RMS
Police RMS
Police RMS
Police RMS
Police RMS
Police RMS
Police RMS
'Police RMS
Police RMS
Police RMS
Police RMS
Police RMS
Police RMS
Police RMS
Police RMS
9/18/2001 Public Safety Information System Cost Proposal
RFP Response Form
10/10/2001 Feature/Function Checklist
Feat # Description
8.87 length of hair
8.88 hair style
8.89 glasses
8.90 right or left-handed
8.91 demeanor
8.92 facial hair
8.93 speech
8.94 general appearance
8.95 hair color and eye color
System supports the following fields and the ability to search for vehicles based on
8.96 following criteria individually or in any combination:
8.97 make
8.98 model
8.99 year
8.100 type (2 dr, 4dr, etc)
8.101 color
8.102 stolen I
8.103 recovered
8.104 towed I
8.105 abandoned tow
8.106 private property tow I
8.107 impounded (30 day)
8.108 stored
8.109 released I
8.110 repossession I
8.111 ISystem allows approximation when conducting text searches I
(System supports the following fields and support the ability to search for addresses
8.112 based on following criteria individually or in any combination:
8.113 street number and/or name I
8.114 with or without apartment number I
8.115 city
8.116 state
8.117 zip code
8.118 intersection I
8.119 common name location (e.g. Staples parking lot) I
8.120 business name or a.k.a. j
8.121 beat I
8.122 zone I
Vendor:
Sun Ridge Systems
Rating
3
3
3
3
3
3
3
3
3
3
3
3
3
3
3
3
3
3
3
3
3
3
3
3
3
3
3
3
3
3
3
3
3
3
Vendor Project
CompL Cost
3
3
0
0
0
3
3
3
3
3
3
3
3
3
3
3
3
3
3
3
3
3
3
3
3
3
3
3
3
3
3
3
3
3
Exhibit D1
Page 26 of 35
Release Date:
9/18/2001
Public Safety Information System Cost Proposal
Vendor:
RFP Response Form
Sun Ridge Systems
Due Date:
10/10/2001
Feature/Function Checklist
Vendor Project
Subsystem
Feat #
Description
Rating
CompL Cost
Police RMS
8.123
hazard notes
3
3
System supports searches for reports by user defined type designation (e.g. MH
Police RMS
8.124
=mental health)
3
3
System supports the following fields and support the ability to search for
Police RMS
8.125
actions taken on towed and/or impounded vehicles based on:
3
Police RMS
8.126
location towed from
3
0
Police RMS
8.127
vehicle physical descriptor
3
0
Police RMS
8.128
date of tow
3
3
Police RMS
8.129
date of release
3
0
Police RMS
8.130
officer authorizing tow/impound action
3
3
Police RMS
8.131
employee inputting tow/impound action
3
0
Police RMS
8.132
within date range
3
3
Police RMS
8.133
case report number
3
3
Police RMS
8.134
incident number not resulting in police report
3
3
Police RMS
8.135
any combination of these factors in any order
3
3
Police RMS
8.136
System allows user to define the sorting order and filters for search including:
Police RMS
8.137
greater than values
3
3
Police RMS
8.138
less than values
3
3
Police RMS
8.139
equal to values
3
3
System supports searches based on any combination of the various parameters
for persons, addresses, vehicles or elements within each area (e.g. persons & gang
Police RMS
8.140
affiliations at known address)
3
(System displays browse list (summary) of all records which meet user defined search)
Police RMS
8.141
criteria
3
3
1
(System includes standard predefined reports printable in standard formats from PC
Police RMS
8.142
or MDC including:
3
Police RMS
8.143
crime reports 1
3
3
Police RMS
8.144
incident reports I
3
3
Police RMS
8.145
arrest reports 1
3
3
Police RMS
8.146
D.U.I. Reports 1
3
0
Police RMS
8.147
cost Recovery 1
3
0
Police RMS
8.148
D.M.V. Suspension reports
3
0
Police RMS
8.149
1 C.H.P. 180 I
3
0
Police RMS
8.150
Field Interview reports
3 1
3
Police RMS
8.151
Narcotics Influence reports (11550 H&S) I
3
0
Police RMS
8.152
missing persons I
3
3
Police RMS
8.153
citation I
3 1
3
Police RMS
8.154
supplemental (follow up) report I
3 1
3
Exhibit D1
Page 27 of 35
Release Date:
Due Date:
Subsystem
Police RMS
Police RMS
Police RMS
Police RMS
Police RMS
Police RMS
Police RMS
Police RMS
Police RMS
Police RMS
Police RMS
Police RMS
Police RMS
Police RMS
Police RMS
Police RMS
Police RMS
Police Citations
Police Citations
Police Citations
Police Citations
Police Citations
Police Citations
Police Citations
Police Citations
Police Citations
Police Citations
9/18/2001 Public Safety Information System Cost Proposal
RFP Response Form
10/10/2001 Feature/Function Checklist
Feat # Description
8.155 booking sheet
System provides all traffic collision reports in state mandated format including but not
8.156 limited to:
8.157 C.H.P. traffic collision reports (not limited to 555 and 556)
8.158 System generates monthly UCR reports in format acceptable to DOJ that include:
8.159 Part I offenses
8.160 property by type and value
8.161 property by classification
8.162 arson offenses
8.163 violence crimes against seniors
8.164 domestic violence related crimes
8.165 hate crimes
8.166 officer assault report
8.167 arrest and citation register (adult and juvenile)
1 8.168 ISystem Support includes addition of any new mandated UCR reports.
(System generates monthly reports that include Part II and miscellaneous offenses
8.169 which can be defined at user level
1 8.170 JSystem support NIBRS reporting requirements (future requirement in California) I
(The Vehicle Make field utilizes a drop-down box to make a selection from a data
8.171 validation table
9.1 ISystem links citation entries with master name, vehicle and location (address) indices)
seamlessly as information is entered
(System automatically populates duplicate fields in citation if any associated case
9.2 report or supp. exists
(System automatically populates duplicate fields on case report if citation is entered
9.3 first
(System provides drop down lists or pop up menus for same fields in citation module
9.4 as in case reports (e.g. gender, hair/eye color, race, street name, etc)
(System will alert user if driver or registered owner on citation has any outstanding
9.5 warrants in local database
9.6 System allows access to citation module as separate menu selection.
(System automatically makes citation module "pop up" in case report when the citation'
9.7 number is entered.
9.8 ISystem accommodates entire citation module on one screen. j
1 9.9 System allows user to add/modify/print citation while in the citation module j
System displays a browse list of previous and subsequent citation numbers on i
9.10 citation screen for easy reference
Vendor: I
I
Sun Ridge Systems
Vendor Project
Rating
Compl. Cost
3
3
3
0
3
1
3
3
3
3
3
3
3
3
3
3
3
3
3
3
3
3
3
3
3
3
3
3
3
3
3
3
3
3
3
0
3
3
0
3
2
3
0
0
3
3
3
0
3
3
0
$ 600
Exhibit D1
Page 28 of 35
Release Date:
Due Date:
Subsystem
Police Citations
Police Citations
Police Citations
Police Citations
Police Citations
Police Citations
Police Citations
Police Citations
Police Citations
Police Citations
Police Citations
Police Citations
Police Citations
Police Citations
Police Citations
Police Citations
Police Citations
Police Citations
Police Citations
Police Citations
Police Citations
Fire RMS
Fire RMS
Fire RMS
9/18/2001
10/10/2001
Feat #
9.11
9.12
9.13
9.14
9.15
9.16
9.17
9.18
9.19
9.20
9.21
9.22
9.23
9.24
9.25
9.26
9.27
9.28
9.29
9.30
1 9.31
110.1
110.2
110.3
Public Safety Information System Cost Proposal
RFP Response Form
Feature/Function Checklist
Description
System allows user to move to citation by highlighting number in browse list and
clicking mouse
System fills in corresponding case report number on citation (if applicable)
System displays corresponding case report number for citation highlighted in browse
list, with 'right' click on mouse
System allows user to move to the case report from the citation screen with a single
command (if applicable)
System allows user to move in and out of CLETS from citation module without
logging out.
System will search local history for outstanding warrant for driver/registered owner,
etc. and alert user
System includes free form comment field for miscellaneous information defined at
user level
System automatically includes citation when printing a case report (if applicable)
(System allows user to print citation from either the citation module or case report
module
System automatically fills in description of violation on citation when violation field is
filled in
(System provides field for "time of court appearance" on citation
(System automatically selects 'juvenile' checkbox based on Date of Birth entered
(System allows unlimited violation entries
System includes 'locate' type search feature in citation module
(System includes field for date of entry of citation
ISystem includes field for name / ID# of person entering citation
ISystem provides citation module which emulates standard citation form on the
screen and when printed
ISystem archives audit trail of changes to citations with date of change/time of
change/ID# of person making change
ISystem allows multiple users to view same citation simultaneously
ISystem does not require citation to be 'approved' before linking to master indexes
ISystem allows user to move from field to field by mouse click or single keyboard
command
ISystem interfaces with Telestaff Personnel Scheduling Software
ISystem is NFIRS 5.0 compliant
System includes user -defined fields
Vendor: I
I
Sun Ridge Systems
Vendor Project
Rating
CompL Cost
3
0
3
0
3
0
2
3
3
3
3
0
3
3
3
0
3
0
3
3
1 3
3
3
0
I 3 I
3
3 1
3
I 3 I
0
I 3 1
3 I
3 I
0
3 I
0
I 3 I
3
3 13
3 I
3
I 3 I
0
I 3 I
0
I 3 I
0
Exhibit D1
Page 29 of 35
Release Date:
9/18/2001
Public Safety Information System Cost Proposal
Vendor:
RFP Response Form
Sun Ridge Systems
Due Date:
10/10/2001
Feature/Function Checklist
Vendor Project
Subsystem
Feat #
Description
Rating
Compl. Cost
Fire RMS
10.4
System support multiple jurisdictions
3
0
Fire RMS
10.5
System supports the attachment of digital photos to a report
2
0
Fire RMS
10.6
System supports Object linking to reports
2
0
System allows user to create, edit, print any activity log by any searchable field
Fire RMS
10.7
including but not limited to:
Fire RMS
10.8
incident number
3
0
10.9
NFIR number
0
Fire RMS
10.10
date parameters
3
0
Fire RMS
10.11
type of incident/violation
3
0
Fire RMS
10.12
location (community fire servicing zones and/or street address)
3
0
Fire RMS
10.13
time period
3
0
Fire RMS
10.14
incident summary from NFIRS report
3
0
Fire RMS
10.15
incident summary from CAD
3
0
Fire RMS
10.16
disposition
3
0
Fire RMS
10.17
unit(s) involved
3
0
Fire RMS
10.18
parties involved
3
0
System allows user to create, edit, print specific productivity lists for units based on
Fire RMS
10.19
user defined criteria
3
0
Fire RMS
10.20
System provides pre -loaded productivity reports which can be saved as a file
3
0
Fire RMS
10.21
System allows user to create, edit, print summary productivity reports
3
0
Fire RMS
10.22
System allows users to print calls for service based on user defined parameters
3
0
System allows creation of custom statistical reports at user level based on data in
Fire RMS
10.23
combination or selected individual criteria
3
0
System allows custom statistical reports to be saved as a file for future use by the
Fire RMS
10.24
user
3
0
System supports searches and ad-hoc reporting based on following criteria
Fire RMS
10.25
individually or in any combination:
incidents within geographic area of San Rafael and adjacent cities based on street
Fire RMS
10.26
parameters
3
0
incidents within geographic area of San Rafael and adjacent cities based on date
Fire RMS
10.27
range
3
0
Fire RMS
10.28
incidents based on responding agency
3
0
incidents within geographic area of San Rafael and adjacent cities based on unit or
Fire RMS
10.29
multiple units identifying numbers
3
0
Fire RMS
10.30
incidents within date parameters, including:
Fire RMS
10.31
hourly
3
0
Fire RMS
10.32
daily
3
0
Fire RMS
10.33
monthly
3
0
Exhibit D1
Page 30 of 35
Release Date:
Due Date:
Subsystem
Fire RMS
Fire RMS
Fire RMS
Fire RMS
Fire RMS
Fire RMS
Fire RMS
Fire RMS
Fire RMS
Fire RMS
Fire RMS
Fire RMS
Fire RMS
Fire RMS
Fire RMS
Fire RMS
Fire RMS
Fire RMS
Fire RMS
Fire RMS
Fire RMS
Fire RMS
Fire RMS
Fire RMS
Fire RMS
Fire RMS
Fire Inspection and
Permits
Fire Inspection and
Permits
9/18/2001 Public Safety Information System Cost Proposal
RFP Response Form
10/10/2001 Feature/Function Checklist
Feat # Description
10.34 quarterly
10.35 year to date I
System supports ad-hoc reporting based on all user defined fields individually or in
10.36 combination
System allows user to select any individual case report from a list and open it from I
10.37 the list
System allows user access to browse list of case reports and to move between the
110.38 reports by a keyboard command or mouse click.
System allows for saving all lists as a file within the vendor software and in word
110.39 processing software (e.g. Microsoft Word)
110.40 System allows approximation when conducting text searches I
System supports the following fields and support the ability to search for addresses
110.41 based on following criteria individually or in any combination:
110.42 street number and/or name I
110.43 with or without apartment number
110.44 1 city I
110.45 1 state I
110.46 I zip code
10.47 + intersection I
10.48 common name location (e.g. Staples parking lot) I
110.49 business name or a.k.a. I
110.50 unit
110.51 community fire servicing zone j
10.52 hazard notes
10.53 JSystem allows user to define the sorting order and filters for search including:
110.54 greater than values
110.55 less than values
110.56 1 equal to values
System displays browse list (summary) of all records which meet user defined search i
110.57 criteria
System includes standard predefined NFIRS report printable in standard formats
110.58 from PC
10.59 Isystern can transmit NFIRS report electronically to State Fire Marshall's office
11.1 ISystern includes the following fields:
111.2 I Occupancy classification
I
Vendor:
Sun Ridge Systems
3 0
3 0
3 0
3 0
3 0
3 0
3 0
3 0
3 0
3 0
3 0
3 0
3 0
3 0
3 I 0
0
3 0
3 0
Project
Cost
Exhibit D1 Page 31 of 35
Vendor
Rating
Compl.
3
0
3
0
3
0
3
0
3
0
3
0
3
0
3 0
3 0
3 0
3 0
3 0
3 0
3 0
3 0
3 0
3 0
3 0
3 0
3 0
3 0
3 I 0
0
3 0
3 0
Project
Cost
Exhibit D1 Page 31 of 35
I Release Date:
9/18/2001
Public Safety Information System Cost Proposal
Vendor:
RFP Response Form
Sun Ridge Systems
Due Date:
10/10/2001
Feature/Function Checklist
Vendor Project
Subsystem
Feat #
Description
Rating
Compl. Cost
Fire Inspection and
Permits
11.3
Types of fire protection systems
3
0
Fire Inspection and
Permits
11.4
Hazmat location (yes/no)
3
0
Fire Inspection and
Permits
11.5
Inspector (defaults to logged in user)
3
0
Fire Inspection and
Permits
11.6
Unit number
3
0
Fire Inspection and
Permits
11.7
Duration of inspection
3
0
Fire Inspection and
Permits
11.8
Violation
3
0
Fire Inspection and
Permits
11.9
Violation count
3
0
Fire Inspection and
Permits
11.10
Type of inspection
3
0
Fire Inspection and
Permits
11.11
Free form comments field
3
0
Fire Inspection and
Permits
11.12
System supports multiple violations per inspection per location
3
0
Fire Inspection and
Permits
11.13
System supports multiple occupancy classifications per locations
3
0
Fire Inspection and
Permits
11.14
System automatically records violations on a re-inspection from an original inspection
3
0
Fire Inspection and
Permits
11.15
System supports pre fire plan information including:
Fire Inspection and
Permits
11.16
Fire Department Entry key location
3
0
Fire Inspection and
Permits
11.17
Fire Department Connection Location
3
0
Fire Inspection and
Permits
11.18
Fire Sprinkler Shutoff
3
0
Fire Inspection and
Permits
11.19
Fire Alarm Control Panel
3
0
Fire Inspection and
Permits
11.20
Main Electric Shutoff
3
0
Fire Inspection and
Permits
11.21
Main Gas Shutoff
3
0
Exhibit D1 Page 32 of 35
I Release Date:
9/18/2001
Public Safety Information System Cost Proposal
Vendor: I
I
RFP Response Form
Sun Ridge Systems
Due Date:
10/10/2001
Feature/Function Checklist
Vendor Project
Subsystem
Feat #
Description
Rating
CompL Cost
Fire Inspection and
Permits
11.22
Main Water Shutoff
3
0
Fire Inspection and
Permits
11.23
Pre Fire Plan Number
3
0
Fire Inspection and
Permits
11.24
Other
3
0
Fire Hydrant
Management
12.1
System supports the following fire hydrant fields:
Fire Hydrant
Management
12.2
hydrant manufacturer
3 1
0
Fire Hydrant
112.3
Management
community fire servicing area
3 1
0
Fire Hydrant
112.4
1
Management
water main size
3
0
Fire Hydrant
112.5
Management
bury size
3
0
Fire Hydrant
112.6
1
Management
number of outlets
3
0
Fire Hydrant
Management
12.7
type of outlets
3
0
Fire Hydrant
Management
12.8
shutoff valve distance
I 3 1
0
Fire Hydrant
112.9
Management
1 shutoff valve direction
3
I 1
0
Fire Hydrant
112.10 I
Management
type of service
I 3
0
Fire Hydrant
112.11
Management
1
date of service
1 3
0
Fire Hydrant
Management
112.12 I
date of hydrant flow
1 3
0
Fire Hydrant
Management
112.13 1
Pitot gauge pressure
3
0
Fire Hydrant
112.14
Management
1
static pressure
3
0
Fire Hydrant
Management
112.15 1
residual pressure
I
3 I
0
Fire Hydrant
Management
112.16 I
gallons per minute flowing
3
0
Exhibit D1
Page 33 of 35
Release Date:
9/18/2001
Public Safety Information System Cost Proposal
Vendor Project
RFP Response Form
Due Date:
10/10/2001
Feature/Function Checklist
Subsystem
Feat #
Description
Fire Hydrant
2
0
Management
12.17
gallons per minute at 20 lbs risidual
Fire Hydrant
Management
12.18
comments field
Fire Hydrant
Management
12.19
System calculates gallons per minute flowing based on pitot pressure and outlet size
Fire Hydrant
Systems calculates GPM@20 based on static and residual pressure and gallons per
Management
12.20
minute flowing
Fire Hydrant
Management
12.21
System updates multiple hydrants from multiple selection of hydrants
Fire Personnel
Training and
Management
13.1
System tracks training by units
Fire Personnel
Training and
Management
13.2
System tracks training by individuals
Fire Personnel
Training and
Management
13.3
System supports pre -defined types of training
Fire Personnel
Training and
Management
13.4
System tracks training dates
Fire Personnel
Training and
Management
13.5
Systems tracks training time
Fire Personnel
Training and
Management
13.6
System updates multiple training records from training roster
Fire Equipment
114.1
Management
System supports multiple type of equipment
Fire Equipment
114.2
Management
System includes the following equipment fields:
Fire Equipment
114.3
Management
size
Fire Equipment
Management
114.4
manufacturer
Fire Equipment
Management
114.5
length
Exhibit D1
Vendor:
Sun Ridge Systems
Vendor Project
Rating
Compl. Cost
3
0
3
0
2
0
2
0
3
0
3 0
3 0
3 0
3 0
3 0
3 0
3 0
3 0
3 0
3 0
Page 34 of 35
Release Date:
9/18/2001
Public Safety Information System Cost Proposal
Vendor:
RFP Response Form
Sun Ridge Systems
Due Date:
10/10/2001
Feature/Function Checklist
Vendor Project
Subsystem
Feat #
Description
Rating
Compl. Cost
Fire Equipment
Management
14.6
construction type
3
0
Fire Equipment
Management
14.7
assigned date
3
0
Fire Equipment
114.8
Management
unit assigned
3
0
Fire Equipment
Management
114.9
test date
1 3
0
Fire Equipment
114.10
Management
testing unit (default user)
1 3
0
Fire Equipment
114.11
1
Management
test status
I 3
0
Fire Equipment
114.12
1
Management
comments field
3
I 1
0
Fire Equipment
114.13
Management
1 repair date
3
I 1
0
Fire Equipment
114.14
Management
1 type of repair
3
11
0
Fire Equipment
114.15
Management
System supports sorting equipment by type
I 3 1
0
Fire Equipment
114.16
iSystem
Management
supports mass updating of equipment
, 3 1
0
Exhibit D1
Page 35 of 35
Further Comments and Clarifications for RF4A Proposal Response
December 7, 2001
1.34 Change to 0. State does not have a drop down list.
Changed to 0
1.39 User Access reports by date/time is limited to the activity log which does not
record all transactions. Other, but not all, transactions are recorded in the person
history, vehicle history, vehicle maintenance history, property history, case audit
trail, and person audit trail. These are printable in whole, not by date.
Changed to 0.
1.48 To clarify, AFIS could be supported, but some software development would be
required and there would be a cost.
Changed to 1
2.9 If this is referring to data extraction by means outside RiMS, then clearly RiMS
security restrictions will not be in effect.
Changed 0
2.15 Network security is integral to the extent that it provides an additional security
layer and can be used to limit access to the SQL Server database and therefore to
who can use RiMS.
Left a3
3.11 To be specific, RiMS does soundex matching in the two cases where we consider
it to be useful: person names and street names.
Changed to 0 - I agree, but changed to 0 to be consistent with the original wording of the
CPR
3.12 To put a finer point on it, ANVALI "population" is always done automatically.
The dispatcher never has to do anything.
Left at 3. The intent of this language is to separate caller location from incident location -
something RIMS already does.
3.15 Again, to be precise, ANVALI provides location. To actually create an incident
the dispatcher must also enter an incident type.
Left at 3
Eehibit D2 Sun Ridge Systems, Inc
3.22 The format for an intersection is Street 1/Street 2.
Left at 3
3.23 The (numerically) low cross street is displayed, not the "closest" because
realistically that is not known. There is no "block number."
Refers to 3.24? changed to 0
3.24 The call taker does not have to "close" the call but does have to press a "Temp
Save" button.
Refers to 3.26? left at 3
3.57 Factually, a unit recommendation can be easily overridden and other units
dispatched but it would likely take more than "a single keystroke".
Changed to 0
3.67 Assigning multiple officers applies only to police. RiMS does not track officers
assigned to a fire apparatus (beyond the proposed split crew tracking).
Left at3
3.98 Specific required fields are pre -determined: location and incident type.
Changed to 0
4.2 At this time there is no procedure for returning a report to an officer so, yes, it can
be "returned"/updated by the officer as many times as needed. In the future we
plan to implement formal means of doing this, but what eventuates from those
plans is not part of our proposal.
Changed to 0
4.10 These functions are accomplished via searches.
Left at3
4.21 There is no distinction by "division."
Changed to 0
4.26 To be specific, RiMS keeps audit trails for changes to cases, people, vehicles, and
property.
Left at 3 - this is resonable
Exhibit D2 Sun Ridge Systems, Inc I
4.36 This is a search function; "by all fields" is a slight exaggeration --- cases are
searchable by most fields.
Left at 3 - this is reasonable
6.4 Mobile computer login notification to the dispatcher consists of the unit appearing
as 10-8 in the unit status display.
Left at 3 - this is reasonable
6.14 A "queued" message is a "waiting" message. Messages are ordered by priority
but the priority is not explicitly displayed.
Left at 3 - this is reasonable
6.15 Actually the user designated how long a message is retained by either saving or
deleting it --- the default being to delete it.
Left at 3 - this is reasonable
6.16 The system records/logs all messages for all users all the time at the central
system. Messages at the mobile computer not retained past the user signing off.
Left at 3 - this is reasonable
6.17 The system support function keys at the mobiles for the items noted, but the keys
are not otherwise programmable. Statuses that do not have dedicated function
keys are available from a status change display.
Refers to 6.21 ?
Left at 3 - this is reasonable
6.56 Such updates are done as the call is closed.
Changed to 1
6.93 Etc. is a big word. I think we want to change this to a 0.
Changed to 0
6.101 Approval of cases from the field is planned for 2002. We do not propose to
include it in this contract.
Changed to 0
7.1 It is perhaps unclear what "storage location tables" refers to. RiMS allows
designating a bin or similar number for property's location in the property room.
Left at 3 - this is reasonable
Exhibit D2 Sun Ridge Systems. Inc 3
7.17 The purpose of this is unclear: R.iMS does not use the property item -officer
connection in any particular way.
Changed to 0
7.20 There is no "property officer's module." The specified information is part of the
case.
Changed to 1
7.22.1 These are not individual fields; they are put in the property description text field
Changed to 0
7.44 et al. These are not individual fields; they are put in the property description text
field.
Changed to 0
7.52 Property owner information is entered with respect to that person being associated
with the case. The person's name is then put in the property record.
Left at 3 - this is reasonable
7.68 Actually, we are unaware of any UCR entries that involve "quantity" of property.
Changed to 0
7.80 This involves searching the property log.
Left at 3 - this is reasonable
8.1 The wording here overreaches. Taken literally, we cannot agree that we meet it.
Changed to 0
8.13 In the broad, literal sense we cannot agree with this statement.
Changed to 0
8.14 Reports can be saved as PDF files.
Changed to 1
8.15 In general, reports are generated, but cannot be edited.
Left as 3 - this is reasonable
8.17 Custom statistical reports are implemented with the RIMS Search function.
Ethibit D1 Sun Ridge Systems, Inc 4
Left as3 - this is reasonable
8.48 Actually, there are no user defined fields, but if there were....
Changed to 0
8.66 Searching by person "category" is limited to certain categories, since they are
maintained as separate lists: arrestees, various kinds of offenders, BOLOS, and
missing persons.
Changed to 0
8.67 Same as 8.66.
Left a 0
8.88 Length of hair and hair style are the same field in RiMS.
Left at 3 - this is reasonable
8.111 Approximations are allowed in that matches on text fragments are supported for
certain fields like case narratives.
Left at 3 - this is reasonable
8.112 We would not agree that there exists the blanket ability to search everything on all
of the parameters given. Generally, such searches are implemented where they
are useful.
Left at 3 - this is reasonable
8.125 Searching tow records is limited to the search capabilities within the activity log
which is where tows are kept.
Left scores as stated - this is resonable
8.142 Other than CLETS messages, no reports are printable from mobile computers.
Left at 3 - this is reasonable (can print reports as stated from PC on network, not Mobile
PC)
9.4 Not gender.
Left at 3 - this is reasonable
Exhibit D2 Stitt Ridge Systems, Inc 5
9.5 Actually, RIMS does present this warning because there will be a warrant flag in
the person record presented to the user.
Changed to 3
9.10 And actually, this does not exist and is not proposed, although it may be added
some day. (It hasn't ever been a wish list item.)
Changed to 0
9.11 Same as 9.10.
Changed to 0
9.14 Supported but only displays the "synoptic" (on one screen) version of the case.
Left at 3 - this is reasonable
9.21 Actually it is date of appearance.
Left at 3 - this is reasonable
9.22 No! Allows 4.
Changed to 0
9.30 There is no "approval" of citations.
Left at 3 - this is reasonable
Exhibit D2 Sun Ridge Systems. Inc 6