HomeMy WebLinkAboutContract CAG-19-323
•
11".••
• • tyler
• Pec:Psno>
LICENSE AND SERVICES AGREEMENT
This License and Services Agreement is made between Tyler Technologies, Inc. and Client.
WHEREAS,Client selected Tyler to license the software products and perform the services set forth in the
Investment Summary and Tyler desires to perform such actions under the terms of this Agreement;
NOW THEREFORE, in consideration of the foregoing and of the mutual covenants and promises set forth in this
Agreement,Tyler and Client agree as follows:
SECTION A—DEFINITIONS
• "Agreement" means this License and Services Agreement.
• "Business Travel Policy" means our business travel policy. A copy of our current Business Travel Policy
is attached as Schedule 1 to Exhibit B.
• "Client" means City of Renton,WA.
• "Defect" means a failure of the Tyler Software to substantially conform to the functional descriptions
set forth in our written proposal to you,or their functional equivalent. Future functionality may be
updated, modified, or otherwise enhanced through our maintenance and support services,and the
governing functional descriptions for such future functionality will be set forth in our then-current
Documentation.
• "Developer" means a third party who owns the intellectual property rights to Third Party Software.
• "Documentation" means any online or written documentation related to the use or functionality of the
Tyler Software that we provide or otherwise make available to you, including instructions, user guides,
manuals and other training or self-help documentation.
• "Effective Date" means the date on which your authorized representative signs the Agreement.
• "Force Majeure" means an event beyond the reasonable control of you or us, including, without
limitation,governmental action, war, riot or civil commotion,fire, natural disaster, or any other cause
that could not with reasonable diligence be foreseen or prevented by you or us.
• "Hosting Services"means the hosting services we will provide for the Tyler Software as set forth in the
Investment Summary,for the fees set forth therein.
• "Investment Summary" means the agreed upon cost proposal for the software, products, and services
attached as Exhibit A.
• "Invoicing and Payment Policy" means the invoicing and payment policy. A copy of our current
Invoicing and Payment Policy is attached as Exhibit B.
• "Maintenance and Support Agreement" means the terms and conditions governing the provision of
maintenance and support services to all of our customers. A copy of our current Maintenance and
Support Agreement is attached as Exhibit C.
••' tyler
s
• "RFP and Tyler's Response" means Request for Proposal and Tyler's response to that proposal as Exhibit
E.
• "SLA" means the service level agreement. A copy of our current SLA is attached hereto as Schedule 1 to
Exhibit C.
• "Statement of Work" means the industry standard implementation plan describing how our
professional services will be provided to implement the Tyler Software, and outlining your and our roles
and responsibilities in connection with that implementation. The Statement of Work is attached as
Exhibit D.
• "Support Call Process" means the support call process applicable to all of our customers who have
licensed the Tyler Software. A copy of our current Support Call Process is attached as Schedule 2 to
Exhibit C.
• "Third Party Terms" means, if any, the end user license agreement(s) or similar terms for the Third Party
Software, as applicable.
• "Third Party Hardware" means the third party hardware, if any, identified in the Investment Summary.
• "Third Party Products" means the Third Party Software, Third Party Hardware, and Third Party Services.
• "Third Party Services" means the services provided by third parties, if any, identified in the Investment
Summary.
• "Third Party Software" means the third party software, if any, identified in the Investment Summary.
• "Tyler" means Tyler Technologies, Inc., a Delaware corporation.
• "Tyler Software" means our proprietary software and related interfaces identified in the Investment
Summary and licensed to you through this Agreement.
• "we", "us", "our" and similar terms mean Tyler.
• "you" and similar terms mean Client.
SECTION B — SOFTWARE LICENSE
1. License Grant and Restrictions.
1.1 We grant to you a license to use the Tyler Software, for the number of licenses identified in the
Investment Summary, for your internal business purposes only, in the scope of the internal business
purposes disclosed to us as of the Effective Date. You may make copies of the Tyler Software for backup
and testing purposes, so long as such copies are not used in production and the testing is for internal
use only. Your rights to use the Tyler Software are perpetual but may be revoked if you do not comply
with the terms of this Agreement. You may add additional licenses at the rates set forth in the
Investment Summary for twelve (12) months from the Effective Date by executing a mutually agreed
addendum. If no rate is provided in the Investment Summary, or those twelve (12) months have
expired, you may purchase additional licenses at our then -current list price, also by executing a mutually
agreed addendum.
1.2 The Documentation is licensed to you and may be used and copied by your employees for internal, non-
commercial reference purposes only.
• ° ° tyler
.❖.e
1.3 You may not: (a) transfer or assign the Tyler Software to a third party; (b) reverse engineer, decompile,
or disassemble the Tyler Software; (c) rent, lease, lend, or provide commercial hosting services with the
Tyler Software; or (d) publish or otherwise disclose the Tyler Software or Documentation to third parties
unless required by law.
1.4 The license terms in this Agreement apply to updates and enhancements we may provide to you or
make available to you through your Maintenance and Support Agreement.
1.5 The right to transfer the Tyler Software to a replacement server hardware system is included in your
license. You will give us advance written notice of any such transfer and will pay us for any required or
requested technical assistance associated with such transfer.
1.6 We reserve all rights not expressly granted to you in this Agreement. The Tyler Software and
Documentation are protected by copyright and other intellectual property laws and treaties. We own
the title, copyright, and other intellectual property rights in the Tyler Software and the Documentation.
The Tyler Software is licensed, not sold.
License Fees. You agree to pay us the license fees in the amounts set forth in the Investment Summary.
Those amounts are payable in accordance with our Invoicing and Payment Policy.
3. Limited Warranty. We warrant that the Tyler Software will be without Defect(s) as long as you have a
Maintenance and Support Agreement in effect. If the Tyler Software does not perform as warranted, we will
use all reasonable efforts, consistent with industry standards, to cure the Defect as set forth in the
Maintenance and Support Agreement.
SECTION C —PROFESSIONAL SERVICES
1. Services. We will provide you the services, if any, itemized in the Investment Summary and described in the
Statement of Work. You will receive those services according to our industry -standard implementation plan,
which outlines roles and responsibilities in calendar and project documentation. We will finalize that
documentation with you upon execution of this Agreement.
Professional Services Fees. You agree to pay us the professional services fees in the amounts set forth in the
Investment Summary. Those amounts are payable in accordance with our Invoicing and Payment Policy.
You acknowledge that the fees stated in the Investment Summary are good -faith estimates of the amount of
time and materials required for the requested services. We will bill you the actual fees incurred based on
the in -scope services provided to you.
Additional Services. The Investment Summary contains, and the Statement of Work describes, the scope of
services and related costs (including programming and/or interface estimates) required for the project
based on our understanding of the specifications you supplied. If additional work is required, or if you use
or request additional services, we will provide you with an addendum or change order, as applicable,
outlining the costs for the additional work. The price quotes in the addendum or change order will be valid
for thirty (30) days from the date of the quote.
••� ° tyler
4. Cancellation. We make all reasonable efforts to schedule our personnel for travel, including arranging travel
reservations, at least two (2) weeks in advance of commitments. Therefore, if you cancel services less than
two (2) weeks in advance (other than for Force Majeure or breach by us), you will be liable for all (a) non-
refundable expenses incurred by us on your behalf, and (b) daily fees associated with cancelled professional
services if we are unable to reassign our personnel. We will make all reasonable efforts to reassign
personnel in the event you cancel within two (2) weeks of scheduled commitments.
Services Warranty. We will perform the services in a professional, workmanlike manner, consistent with
industry standards. In the event we provide services that do not conform to this warranty, we will re -
perform such services at no additional cost to you.
6. Site Access and Requirements. At no cost to us, you agree to provide us with full and free access to your
personnel, facilities, and equipment as may be reasonably necessary for us to provide our services, subject
to any reasonable security protocols or other written policies provided to us.
Client. Assistance. You acknowledge that the provision of services for the Tyler Software is a cooperative
process that may require the time and resources of your personnel. You agree to use all reasonable efforts
to cooperate with and assist us as may be reasonably required. This cooperation includes at least working
with us to schedule the services outlined in this Agreement. We will not be liable for failure to meet any
deadlines and milestones when such failure is due to Force Majeure or to the failure by your personnel to
provide such cooperation and assistance (either through action or omission).
SECTION D — MAINTENANCE AND SUPPORT
This Agreement includes the period of free maintenance and support services identified in the Invoicing and
Payment Policy. If you have purchased ongoing maintenance and support services and continue to make
timely payments for them according to our Invoicing and Payment Policy, we will provide you with
maintenance and support services for the Tyler Software under the terms of our standard Maintenance and
Support Agreement.
If you have opted not to purchase ongoing maintenance and support services or fail to make timely payment
under this Agreement, the Maintenance and Support Agreement does not apply to you. Instead, you will
only receive ongoing maintenance and support on the Tyler Software Products on a time and materials
basis. In addition, you will:
(i) receive the lowest priority under our Support Call Process;
(ii) be required to purchase new releases of the Tyler Software Products, including fixes,
enhancements and patches;
(iii) be charged our then -current rates for support services, or such other rates that we may
consider necessary to account for your lack of ongoing training on the Tyler Software Products;
(iv) be charged for a minimum of two (2) hours of support services for every support call; and
(v) not be granted access to the support website for the Tyler Software Products or the Tyler
Community Forum.
•% _96 tyler
SECTION E —THIRD PARTY PRODUCTS
To the extent there are any Third Party Products set forth in the Investment Summary, the following terms and
conditions will apply:
1. Third Party Hardware. We will sell, deliver, and install onsite the Third Party Hardware, if you have
purchased any, for the price set forth in the Investment Summary. Those amounts are payable in
accordance with our Invoicing and Payment Policy.
2. Third Party Software. Upon payment in full of the Third Party Software license fees, you will receive a non-
transferable license to use the Third Party Software and related documentation for your internal business
purposes only. Your license rights to the Third Party Software will be governed by the Third Party Terms.
2.1 We will install onsite the Third Party Software. The installation cost is included in the installation fee in
the Investment Summary.
2.2 If the Developer charges a fee for future updates, releases, or other enhancements to the Third Party
Software, you will be required to pay such additional future fee.
2.3 The right to transfer the Third Party Software to a replacement hardware system is governed by the
Developer. You will give us advance written notice of any such transfer and will pay us for any required
or requested technical assistance from us associated with such transfer.
3. Third Party Products Warranties.
3.1 We are authorized by each Developer to grant or transfer the licenses to the Third Party Software.
3.2 The Third Party Hardware will be new and unused, and upon payment in full, you will receive free and
clear title to the Third Party Hardware.
3.3 You acknowledge that we are not the manufacturer of the Third Party Products. We do not warrant or
guarantee the performance of the Third Party Products. However, we grant and pass through to you
any warranty that we may receive from the Developer or supplier of the Third Party Products.
4. Maintenance. If you have a Maintenance and Support Agreement in effect, you may report defects and
other issues related to the Third Party Software directly to us, and we will (a) directly address the defect or
issue, to the extent it relates to our interface with the Third Party Software; and/or (b) facilitate resolution
with the Developer, unless that Developer requires that you have a separate, direct maintenance agreement
in effect with that Developer. In all events, if you do not have a Maintenance and Support Agreement in
effect with us, you will be responsible for resolving defects and other issues related to the Third Party
Software directly with the Developer.
SECTION F — HOSTING SERVICES
1. We will either host or engage Third Party Services in order to host the Tyler Software set forth in the
Investment Summary for the fees set forth therein. You agree to pay those fees according to the Invoicing
• • ° tyler
and Payment Policy. In exchange for those fees, we agree to provide the Hosting Services according to the
terms and conditions set forth in this Section F, and the other applicable terms of this Agreement. If you fail
to pay those fees, after advance written notice to you, we reserve the right to suspend delivery of our
applicable Hosting Services. If, after your failure to pay hosting fees after our written notice to you and our
suspension of applicable Hosting Services, you require access to the Hosting Services in order to fulfill a
public records request, we will reasonably cooperate with you to help you fulfill that request. Our
cooperation will not be considered a waiver of any requirement to pay Hosting Fees.
2. We will utilize hosting services through a Third Party Services provider in accordance with the terms set
forth in the Investment Summary. The fees contained in the Investment Summary are subject to annual
increases. You acknowledge and agree that, in our sole discretion, we may migrate the Hosting Services to a
replacement system (including our own) and will undertake reasonable efforts to complete such transfer
during maintenance windows as set forth in the SLA. We will undertake reasonable efforts to provide you
with advance written notice of any such transfer. You agree to provide all reasonable assistance and access
in connection with any such transfer. In the event the Tyler Software is transferred to our data center and
we provide hosting services directly to you, the terms of the SLA will also apply.
3. Where applicable, we will perform or cause to have performed upgrades of the applications, hardware, and
operating systems that support your Hosting Services. These upgrades are performed in commercially
reasonable timeframes and in coordination with third -party releases and certifications. We will make
available information on industry -standard minimum requirements and supported browsers for accessing
the Hosting Services.
SECTION G - INVOICING AND PAYMENT; INVOICE DISPUTES
1. Invoicing and Payment. We will invoice you the fees for the license(s), products, and services in the
Investment Summary per our Invoicing and Payment Policy, subject to Section G(2).
Invoice Disputes. If you believe any delivered software or service does not conform to the warranties in this
Agreement, you will provide us with written notice within forty-five (45) days of your receipt of the
applicable invoice. The written notice must contain reasonable detail of the issues you contend are in
dispute so that we can confirm the issue and respond to your notice with either a justification of the invoice,
an adjustment to the invoice, or a proposal addressing the issues presented in your notice. We will work
with you as may be necessary to develop an action plan that outlines reasonable steps to be taken by each
of us to resolve any issues presented in your notice. You may withhold payment of the amount(s) actually in.
dispute, and only those amounts, until we complete the action items outlined in the plan. If we are unable
to complete the action items outlined in the action plan because of your failure to complete the items
agreed to be done by you, then you will remit full payment of the invoice. We reserve the right to suspend
delivery of all services, including maintenance and support services, if you fail to pay an invoice not disputed
as described above within fifteen (15) days of notice of our intent to do so.
SECTION H —TERM I NATION
1. For Cause. If you believe we have materially breached this Agreement, you will invoke the Dispute
Resolution clause set forth in Section J(3). You may terminate this Agreement for cause in the event we do
not cure, or create a mutually agreeable action plan to address, a material breach of this Agreement within
•,tyler
.•,Pa
the thirty (30) day window set forth in Section J(3). In the event of termination for cause, you will pay us for
all undisputed fees and expenses related to the software, products, and/or services you have received, or
we have incurred or delivered, prior to the effective date of termination.
2. Lack of Appropriations. If you should not appropriate or otherwise receive funds sufficient to purchase,
lease, operate, or maintain the software or services set forth in this Agreement, you may unilaterally
terminate this Agreement effective on the final day of the fiscal year through which you have funding. You
will make every effort to give us at least thirty (30) days written notice prior to a termination for lack of
appropriations. In the event of termination due to a lack of appropriations, you will pay us for all
undisputed fees and expenses related to the software and/or services you have received, or we have
incurred or delivered, prior to the effective date of termination. Any disputed fees and expenses must have
been submitted to the Invoice Dispute process set forth in Section G(2) at the time of termination in order to
be withheld at termination. You will not be entitled to a refund or offset of previously paid license and
other fees.
Force Maieure. Except for your payment obligations, either you or we may terminate this Agreement if a
Force Majeure event suspends performance of scheduled tasks for a period of forty-five (45) days or more.
In the event of termination due to Force Majeure, you will pay us for all undisputed fees and expenses
related to the software and/or services you have received, or we have incurred or delivered, prior to the
effective date of termination. Any disputed fees and expenses must have been submitted to the Invoice
Dispute process set forth in Section G(2) at the time of termination in order to be withheld at termination.
You will not be entitled to a refund or offset of previously paid license and other fees.
4. Data and records transfer. Upon termination of the contract Tyler will provide the Client with a copy of all
data and records in an acceptable format to the Client.
SECTION I — INDEMNIFICATION, LIMITATION OF LIABILITY AND INSURANCE
1. Intellectual Property Infringement Indemnification.
1.1 We will defend you against any third party claim(s) that the Tyler Software infringes that third party's
patent, copyright, or trademark, or misappropriates its trade secrets, and will pay the amount of any
resulting adverse final judgment (or settlement to which we consent). You must notify us promptly in
writing of the claim and give us sole control over its defense or settlement. You agree to provide us with
reasonable assistance, cooperation, and information in defending the claim at our expense.
1.2 Our obligations under this Section I(1) will not apply to the extent the claim or adverse final judgment is
based on your: (a) use of a previous version of the Tyler Software and the claim would have been
avoided had you installed and used the current version of the Tyler Software; (b) combining the Tyler
Software with any product or device not provided, contemplated, or approved by us; (c) altering or
modifying the Tyler Software, including any modification by third parties at your direction or otherwise
permitted by you; (d) use of the Tyler Software in contradiction of this Agreement, including with non -
licensed third parties; or (e) willful infringement, including use of the Tyler Software after we notify you
to discontinue use due to such a claim.
-00
-*: tyler
1.3 If we receive information concerning an infringement or misappropriation claim related to the Tyler
Software, we may, at our expense and without obligation to do so, either: (a) procure for you the right
to continue its use; (b) modify it to make it non -infringing; or (c) replace it with a functional equivalent,
in which case you will stop running the allegedly infringing Tyler Software immediately.
1.4 If an infringement or misappropriation claim is fully litigated and your use of the Tyler Software is
enjoined by a court of competent jurisdiction, in addition to paying any adverse final judgment (or
settlement to which we consent), we will, at our option, either: (a) procure the right to continue its use;
(b) modify it to make it non -infringing; (c) replace it with a functional equivalent; or (d) terminate your
license and refund the license fees paid for the infringing Tyler Software, as depreciated on a straight-
line basis measured over seven (7) years from the Effective Date. We will pursue those options in the
order listed herein. This section provides your exclusive remedy for third party copyright, patent, or
trademark infringement and trade secret misappropriation claims.
2. General Indemnification.
2.1 We will indemnify and hold harmless you and your agents, officials, and employees from and against any
and all third -party claims, losses, liabilities, damages, costs, and expenses (including reasonable
attorney's fees and costs) for (a) personal injury or property damage to the extent caused by our
negligence or willful misconduct; (b) our violation of a law applicable to our performance under this
Agreement; or (c) if caused by Tyler during our performance under this Agreement, a "breach of the
security of the system" as that term is defined in Wash. Rev. Code § 19.255.010 et seq. You must notify
us promptly in writing of the claim and give us sole control over its defense or settlement. You agree to
provide us with reasonable assistance, cooperation, and information in defending the claim at our
expense.
2.2 To the extent permitted by applicable law, you will indemnify and hold harmless us and our agents,
officials, and employees from and against any and all third -party claims, losses, liabilities, damages,
costs, and expenses (including reasonable attorney's fees and costs) for (a) personal injury or property
damage to the extent caused by your negligence or willful misconduct; or (b) your violation of a law
applicable to your performance under this Agreement. We will notify you promptly in writing of the
claim and will give you sole control over its defense or settlement. We agree to provide you with
reasonable assistance, cooperation, and information in defending the claim at your expense.
3. DISCLAIMER. EXCEPT FOR THE EXPRESS WARRANTIES PROVIDED IN THIS AGREEMENT AND TO THE
MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, WE HEREBY DISCLAIM ALL OTHER WARRANTIES
AND CONDITIONS, WHETHER EXPRESS, IMPLIED, OR STATUTORY, INCLUDING, BUT NOT LIMITED TO, ANY
IMPLIED WARRANTIES, DUTIES, OR CONDITIONS OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR
PURPOSE.
4. LIMITATION OF LIABILITY. EXCEPT AS OTHERWISE EXPRESSLY SET FORTH IN THIS AGREEMENT, OUR
LIABILITY FOR DAMAGES ARISING OUT OF THIS AGREEMENT, WHETHER BASED ON A THEORY OF
CONTRACT OR TORT, INCLUDING NEGLIGENCE AND STRICT LIABILITY, SHALL BE LIMITED TO YOUR ACTUAL
DIRECT DAMAGES, NOT TO EXCEED TWO TIMES THE ONE-TIME FEES SET FORTH IN THE INVESTMENT
SUMMARY. THE PRICES SET FORTH IN THIS AGREEMENT ARE SET IN RELIANCE UPON THIS LIMITATION OF
••:. tyler
LIABILITY. THE FOREGOING LIMITATION OF LIABILITY SHALL NOT APPLY TO CLAIMS THAT ARE SUBJECT TO
SECTIONS 1(1) AND 1(2).
S. EXCLUSION OF CERTAIN DAMAGES. TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, IN NO
EVENT SHALL WE BE LIABLE FOR ANY SPECIAL, INCIDENTAL, PUNITIVE, INDIRECT, OR CONSEQUENTIAL
DAMAGES WHATSOEVER, EVEN IF WE HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
6. Insurance. During the course of performing services under this Agreement, we agree to maintain the
following levels of insurance: (a) Commercial General Liability of at least $1,000,000; (b) Automobile Liability
of at least $1,000,000; (c) Professional Liability of at least $1,000,000; (d) Workers Compensation complying
with applicable statutory requirements; and (e) Excess/Umbrella Liability of at least $5,000,000. We will add
you as an additional insured to our Commercial General Liability and Automobile Liability policies, which will
automatically add you as an additional insured to our Excess/Umbrella Liability policy as well. We will
provide you with copies of certificates of insurance upon your written request.
SECTION J — GENERAL TERMS AND CONDITIONS
1. Additional Products and Services. You may purchase additional products and services at the rates set forth
in the Investment Summary for twelve (12) months from the Effective Date, and thereafter at our then -
current list price, by executing a mutually agreed addendum. If no rate is provided in the Investment
Summary, or those twelve (12) months have expired, you may purchase additional products and services at
our then -current list price, also by executing a mutually agreed addendum. The terms of this Agreement will
control any such additional purchase(s), unless otherwise specifically provided in the addendum.
2. Optional Items. Pricing for any listed optional products and services in the Investment Summary will be valid
for twelve (12) months from the Effective Date.
3. Dispute Resolution. You agree to provide us with written notice within thirty (30) days of becoming aware
of a dispute. You agree to cooperate with us in trying to reasonably resolve all disputes, including, if
requested by either party, appointing a senior representative to meet and engage in good faith negotiations
with our appointed senior representative. Senior representatives will convene within thirty (30) days of the
written dispute notice, unless otherwise agreed. All meetings and discussions between senior
representatives will be deemed confidential settlement discussions not subject to disclosure under Federal
Rule of Evidence 408 or any similar applicable state rule. If we fail to resolve the dispute, either of us may
assert our respective rights and remedies in a court of competent jurisdiction. Nothing in this section shall
prevent you or us from seeking necessary injunctive relief during the dispute resolution procedures.
4. Taxes. The fees in the Investment Summary do not include any taxes, including, without limitation, sales,
use, or excise tax. If you are a tax-exempt entity, you agree to provide us with a tax-exempt certificate.
Otherwise, we will pay all applicable taxes to the proper authorities and you will reimburse us for such taxes.
If you have a valid direct -pay permit, you agree to provide us with a copy. For clarity, we are responsible for
paying our income taxes, both federal and state, as applicable, arising from our performance of this
Agreement.
5. Nondiscrimination. We will not discriminate against any person employed or applying for employment
concerning the performance of our responsibilities under this Agreement. This discrimination prohibition
9
x.1%. tyler
will apply to all matters of initial employment, tenure, and terms of employment, or otherwise with respect
to any matter directly or indirectly relating to employment concerning race, color, religion, national origin,
age, sex, sexual orientation, ancestry, disability that is unrelated to the individual's ability to perform the
duties of a particular job or position, height, weight, marital status, or political affiliation. We will post,
where appropriate, all notices related to nondiscrimination as may be required by applicable law.
6. E-Verify. We have complied, and will comply, with the E-Verify procedures administered by the U.S.
Citizenship and Immigration Services Verification Division for all of our employees assigned to your project.
7. Subcontractors. We will not subcontract any services under this Agreement without your prior written
consent, not to be unreasonably withheld.
8. Binding Effect; No Assignment. This Agreement shall be binding on, and shall be for the benefit of, either
your or our successor(s) or permitted assign(s). Neither party may assign this Agreement without the prior
written consent of the other party; provided, however, your consent is not required for an assignment by us
as a result of a corporate reorganization, merger, acquisition, or purchase of substantially all of our assets.
9. Force Majeure. Except for your payment obligations, neither party will be liable for delays in performing its
obligations under this Agreement to the extent that the delay is caused by Force Majeure; provided,
however, that within ten (10) business days of the Force Majeure event, the party whose performance is
delayed provides the other party with written notice explaining the cause and extent thereof, as well as a
request for a reasonable time extension equal to the estimated duration of the Force Majeure event.
10. No Intended Third Party Beneficiaries. This Agreement is entered into solely for the benefit of you and us.
No third party will be deemed a beneficiary of this Agreement, and no third party will have the right to make
any claim or assert any right under this Agreement. This provision does not affect the rights of third parties
under any Third Party Terms.
11. Entire Agreement; Amendment. This Agreement represents the entire agreement between you and us with
respect to the subject matter hereof, and supersedes any prior agreements, understandings, and
representations, whether written, oral, expressed, implied, or statutory. Purchase orders submitted by you,
if any, are for your internal administrative purposes only, and the terms and conditions contained in those
purchase orders will have no force or effect. This Agreement may only be modified by a written amendment
signed by an authorized representative of each party.
12. Severability. If any term or provision of this Agreement is held invalid or unenforceable, the remainder of
this Agreement will be considered valid and enforceable to the fullest extent permitted by law.
13. No Waiver. In the event that the terms and conditions of this Agreement are not strictly enforced by either
party, such non -enforcement will not act as or be deemed to act as a waiver or modification of this
Agreement, nor will such non -enforcement prevent such party from enforcing each and every term of this
Agreement thereafter.
14. Independent Contractor. We are an independent contractor for all purposes under this Agreement.
••;:•. tyler
10
15. Notices. All notices or communications required or permitted as a part of this Agreement, such as notice of
an alleged material breach for a termination for cause or a dispute that must be submitted to dispute
resolution, must be in writing and will be deemed delivered upon the earlier of the following: (a) actual
receipt by the receiving party; (b) upon receipt by sender of a certified mail, return receipt signed by an
employee or agent of the receiving party; (c) upon receipt by sender of proof of email delivery; or (d) if not
actually received, five (5) days after deposit with the United States Postal Service authorized mail center
with proper postage (certified mail, return receipt requested) affixed and addressed to the other party at
the address set forth on the signature page hereto or such other address as the.party may have designated
by proper notice. The consequences for the failure to receive a notice due to improper notification by the
intended receiving party of a change in address will be borne by the intended receiving party.
16. Client Lists. You agree that we may identify you by name in client lists without your permission solely to
identify you by name as a client, and in marketing presentations, and promotional materials only with your
permission and until you opt out by providing us notice in accordance with paragraph 15.
17. Confidentiality. Both parties recognize that their respective employees and agents, in the course of
performance of this Agreement, may be exposed to confidential information and that disclosure of such
information could violate rights to private individuals and entities, including the parties. Confidential
information is nonpublic information that a reasonable person would believe to be confidential and
includes, without limitation, personal identifying information (e.g., social security numbers) and trade
secrets, each as defined by applicable state law. Each party agrees that it will not disclose any confidential
information of the other party and further agrees to take all reasonable and appropriate action to prevent
such disclosure by its employees or agents. The confidentiality covenants contained herein will survive the
termination or cancellation of this Agreement. This obligation of confidentiality will not apply to
information that:
(a) is in the public domain, either at the time of disclosure or afterwards, except by breach of this
Agreement by a party or its employees or agents;
(b) a party can establish by reasonable proof was in that party's possession at the time of initial
disclosure;
(c) a party receives from a third party who has a right to disclose it to the receiving party; or
(d) is the subject of a legitimate disclosure request under the open records laws or similar applicable
public disclosure laws governing this Agreement; provided, however, that in the event you receive
an open records or other similar applicable request, you will give us prompt notice and otherwise
perform the functions required by applicable law.
18. Business License. In the event a local business license is required for us to perform services hereunder, you
will promptly notify us and provide us with the necessary paperwork and/or contact information so that we
may timely obtain such license.
19. Governing Law. This Agreement will be governed by and construed in accordance with the laws of your
state of domicile, without regard to its rules on conflicts of law.
20. Multiple Originals and Authorized Signatures. This Agreement may be executed in multiple originals, any of
which will be independently treated as an original document. Any electronic, faxed, scanned, photocopied,
or similarly reproduced signature on this Agreement or any amendment hereto will be deemed an original
• ° a a tyler
.,•,a,
11
signature and will be fully enforceable as if an original signature. Each party represents to the other that the
signatory set forth below is duly authorized to bind that party to this Agreement.
21. Cooperative Procurement. To the maximum extent permitted by applicable law, we agree that this
Agreement may be used as a cooperative procurement vehicle by eligible jurisdictions. We reserve the right
to negotiate and customize the terms and conditions set forth herein, including but not limited to pricing, to
the scope and circumstances of that cooperative procurement.
22. Contract Documents. The order of priority in the event of any conflict is (1) this Agreement including its
Exhibits A-D; (2) Tyler's Response; and (3) the RFP. This Agreement includes the following exhibits:
Exhibit A
Investment Summary
Exhibit B
Invoicing and Payment Policy
Schedule 1: Business Travel Policy
Exhibit C
Maintenance and Support Agreement
Schedule 1: Service Level Agreement
Schedule 2: Support Call Process
Exhibit D
Statement of Work
Exhibit E
RFP and Tyler's Response
[REMAINDER INTENTIONALLY LEFT BLANK; SIGNATURE PAGE FOLLOWS]
°
• ° ° tyler
°.,.
12
IN WITNESS WHEREOF, a duly authorized representative of each party has executed this Agreement as of the
date(s) set forth below.
TYLER TECHNOLOGIES C. CLIENT—CITY OF RENTON
By: By: cidlik
Name: Sherry Clark Name: Id') /4
Title: Sr. Corporate Attorney Title: /1 v1 /4 t
Date: October 31, 2019 Date:
Address for Notices: Address for Notices:
Tyler Technologies, Inc. City of Renton
One Tyler Drive 1055 South Grady Way
Yarmouth, ME 04096 Renton, WA 98057
Attention: Chief Legal Officer Attention: IT Service Desk
Approved as to Form:
Shane Moloney, City Attorney
tyler
13
•
ty
• ,jer
Exhibit A
Investment Summary
The following Investment Summary details the software, products, and services to be delivered by Tyler
Technologies, Inc. to you under your License and Services Agreement. This Investment Summary is effective
as of the Effective Date. Capitalized terms not otherwise defined will have the meaning assigned to such
terms in your License and Services Agreement.
[REMAINDER OF PAGE INTENTIONALLY LEFT BLANK]
• tyler
14
b
Quoted By:
Seth Dinehart
Q r
••Ofa�s �y��r!
Quote Expiration:
11=019
Quote Name:
City of Renton - Brazos eParking
�• technologies
Quote Number:
2019-86067-3
Quote Description:
SoflwarelServices Only -3 Parking Licenses and
Abandoned Vehicle Module
Sales Quotation For
Renton Police Department
1055 S Grady Way
Renton. WA 98057-3232
Phone: +1 (425) 430-7500
Tvler Softwore
Brazos
eCitation - Brazos Rapid Extension Framework - PDA
3 $2,550
$2.550
$536
Interface: Washington State AOC Court Case Mgmt System
1 S3,250
$3,2M
$683
Interface: Genetech AutoVu
1 $3,250
$3,250
$683
Task: Abandoned Vehicle
1 $3,250
$3.250
3683
Device Level Interface: New Wodd Mobile
1 s0
$0
$0
TOTAL:
$12,300
$2,585
Tyler Software and Related Services -Annual
ra -
Brazos
Brazos Hosting Fee
1
$861
$861
Brazos Adhoc Reporting
1
$1.250
so
MOD: Spatial Mapping Report and GeoLocation
1
61,500
$0
TOTAL:
$861
Professional Services
Brazos Project Mgmt (plus per diem as needed if not remote)
2
$1,000
$2,000
Set Up & Confg
1
$10,000
$10.000
Training
1
S2,000
$2,000
Device Level Interface: Set Up & Configuration
1
$0
$0
New World Interface: Set Up & Configuration
1
s0
$0
Summary
Total Tyler Software
Total Tyler Annual
Total Tyler Services
Total Third Party Hardware, Software and Services
Summary Total
Contract Total
TOTAL:
One Time Fees Recurring Fees
S12,300
$2,585
s0
$861
$14,000
so
50
$o
$26,300
S3,446
$29,746
15
$14,000
••Y a tyler
•
••:•:•• t y
ler
• technologies
Exhibit B
Invoicing and Payment Policy
Tyler Technologies, Inc. will provide you with the software, products, and services set forth in the Investment
Summary of your License and Services Agreement. Capitalized terms not otherwise defined will have the
meaning assigned to such terms in your License and Services Agreement.
Invoicing: We will invoice you for the applicable license fees, products, and services in the Investment Summary
as set forth below. Your rights to dispute any invoice are set forth in your License and Services Agreement.
Payments specified in Exhibit D (SOW), Attachment E (Schedule), to be invoiced upon Client's acceptance as set
forth in the applicable Attachment A (Work Acknowledgement).
1. Tyler Software.
1.1 License Fees: License fees are invoiced in the following intervals:
• $5,800 upon the completion of Task 4 (Sign -off of Work Plan by Client) in Exhibit D (SOW),
Attachment E (Schedule).
• $3,250 upon completion of AutoVu interface.
• $3,250 upon completion of Washington State AOC interface.
1.2 Maintenance and Support Fees: Maintenance and support fees for the first annual term are waived
for one year from the Effective Date. Maintenance and support fees for years two through five shall
not exceed amounts listed in Exhibit A (Investment Summary) and subsequent years shall not
increase by more than 5% during any subsequent renewal term, over the fees payable by Client
during a prior term.
2. Professional Services.
2.1 Professional Services: Professional services are billed as delivered and invoiced as follows:
• $2,000 Project Management: Upon completion of Task 4 (Sign -off of Work Plan by Client) in
Exhibit D (SOW), Attachment E (Schedule).
• $10,000 System Setup and Installation: Upon Task 12 (Final Acceptance)
• $2,000 Training: Upon completion of Task 10 (Training of Pilot Users)
2.2 Payment for Professional Services are due 45 days after the date of invoice.
2.3 Requested Modifications to the Tyler Software: Requested modifications to Tyler Software are
invoiced 50% upon delivery and Client approval of specifications and 50% upon final acceptance.
You must report any failure of the modification to conform to the specifications within thirty (30)
days of final acceptance; otherwise, the modification will be deemed to be in compliance with the
specifications after the 30-day window has passed.
••� •• tyler
16
3. Other Services and Fees.
3.1 Hosting Fees: Hosting Fees for the Tyler Software identified on the Investment Summary are
invoiced annually in advance on the Effective Date and will renew automatically for additional one
(1) year terms at our then -current Hosting Services fee, unless terminated in writing by either party
at least thirty (30) days prior to the end of the then -current term.
4. Third Party Products.
4.1 Third Party Software License Fees: License fees for Third Party Software are invoiced when we make
it available to you for downloading.
4.2 Third Party Software Maintenance: The first year maintenance for the Third Party Software is
invoiced when we make it available to you for downloading.
4.3 Third Party Hardware: Third Party Hardware costs are invoiced upon delivery.
4.4 Third Party Services: Third Party Services fees are invoiced upon delivery.
5. Expenses. The service rates in the Investment Summary do not include travel expenses. Expenses will be
billed as incurred and only in accordance with our then -current Business Travel Policy, plus a 10% travel
agency processing fee. Our current Business Travel Policy is attached to this Exhibit B at Schedule 1.
Copies of receipts will be provided on an exception basis for an administrative fee. Receipts for mileage
or miscellaneous items less than twenty-five dollars are not available.
Payment. We prefer to receive payments electronically. Our electronic payment information is:
Bank: Wells Fargo Bank, N.A.
420 Montgomery
San Francisco, CA 94104
ABA: 121000248
Account: 4124302472
Beneficiary: Tyler Technologies, Inc. — Operating
• ° • tyler
17
••®'D®� t jer
yhnologies
Exhibit B
Schedule 1
Business Travel Policy
1. Air Travel
A. Reservations & Tickets
Tyler's Travel Management Company (TMC) will provide an employee with a direct flight within two
hours before or after the requested departure time, assuming that flight does not add more than
three hours to the employee's total trip duration and the fare is within $100 (each way) of the
lowest logical fare. If a net savings of $200 or more (each way) is possible through a connecting
flight that is within two hours before or after the requested departure time and that does not add
more than three hours to the employee's total trip duration, the connecting flight should be
accepted.
Employees are encouraged to make advanced reservations to take full advantage of discount
opportunities. Employees should use all reasonable efforts to make travel arrangements at least
two (2) weeks in advance of commitments. A seven (7) day advance booking requirement is
mandatory. When booking less than seven (7) days in advance, management approval will be
required.
Except in the case of international travel where a segment of continuous air travel is six (6) or more
consecutive hours in length, only economy or coach class seating is reimbursable. Employees shall
not be reimbursed for "Basic Economy Fares" because these fares are non-refundable and have
many restrictions that outweigh the cost -savings.
B. Baggage Fees
Reimbursement of personal baggage charges are based on trip duration as follows:
• Up to five (5) days = one (1) checked bag
• Six (6) or more days = two (2) checked bags
Baggage fees for sports equipment are not reimbursable.
°
• ° ° tyler
18
2. Ground Transportation
A. Private Automobile
Mileage Allowance — Business use of an employee's private automobile will be reimbursed at the
current IRS allowable rate, plus out of pocket costs for tolls and parking. Mileage will be calculated
by using the employee's office as the starting and ending point, in compliance with IRS regulations.
Employees who have been designated a home office should calculate miles from their home.
B. Rental Car
Employees are authorized to rent cars only in conjunction with air travel when cost, convenience,
and the specific situation reasonably require their use. When renting a car for Tyler business,
employees should select a "mid -size" or "intermediate" car. "Full" size cars may be rented when
three or more employees are traveling together. Tyler carries leased vehicle coverage for business
car rentals; except for employees traveling to Alaska and internationally (excluding Canada),
additional insurance on the rental agreement should be declined.
C. Public Transportation
Taxi or airport limousine services may be considered when traveling in and around cities or to and
from airports when less expensive means of transportation is unavailable or impractical. The actual
fare plus a reasonable tip (15-18%) are reimbursable. In the case of a free hotel shuttle to the
airport, tips are included in the per diem rates and will not be reimbursed separately.
D. Parking & Tolls
When parking at the airport, employees must use longer term parking areas that are measured in
days as opposed to hours. Park and fly options located near some airports may also be used. For
extended trips that would result in excessive parking charges, public transportation to/from the
airport should be considered. Tolls will be reimbursed when receipts are presented.
3. Lodging
Tyler's TMC will select hotel chains that are well established, reasonable in price, and conveniently
located in relation to the traveler's work assignment. Typical hotel chains include Courtyard,
Fairfield Inn, Hampton Inn, and Holiday Inn Express. If the employee has a discount rate with a local
hotel, the hotel reservation should note that discount and the employee should confirm the lower
rate with the hotel upon arrival. Employee memberships in travel clubs such as AAA should be
noted in their travel profiles so that the employee can take advantage of any lower club rates.
••.,'s•• tyler
19
"No shows" or cancellation fees are not reimbursable if the employee does not comply with the
hotel's cancellation policy.
Tips for maids and other hotel staff are included in the per diem rate and are not reimbursed
separately.
Employees are not authorized to reserve non-traditional short-term lodging, such as Airbnb, VRBO,
and HomeAway. Employees who elect to make such reservations shall not be reimbursed.
4. Meals and Incidental Expenses
Employee meals and incidental expenses while on travel status within the continental U.S. are in
accordance with the federal per diem rates published by the General Services Administration.
Incidental expenses include tips to maids, hotel staff, and shuttle drivers and other minor travel
expenses. Per diem rates are available at www.psa.gov/perdiem.
Per diem for Alaska, Hawaii, U.S. protectorates and international destinations are provided
separately by the Department of Defense and will be determined as required.
A. Overnight Travel
For each full day of travel, all three meals are reimbursable. Per diems on the first and last day of a
trip are governed as set forth below.
Departure Day
Depart before 12:00 noon
Depart after 12:00 noon
Return Day
Return before 12:00 noon
Return between 12:00 noon & 7:00 p.m
Return after 7:00 p.m.*
Lunch and dinner
Dinner
Breakfast
Breakfast and lunch
Breakfast, lunch and dinner
*7:00 p.m. is defined as direct travel time and does not include time taken to stop for dinner.
The reimbursement rates for individual meals are calculated as a percentage of the full day per diem
as follows:
• Breakfast 15%
• Lunch 25%
• Dinner 60%
20
****:. tyler
B. Same Day Travel
Employees traveling at least 100 miles to a site and returning in the same day are eligible to claim
lunch on an expense report. Employees on same day travel status are eligible to claim dinner in the
event they return home after 7:00 p.m.*
*7:00 p.m. is defined as direct travel time and does not include time taken to stop for dinner.
5. Internet Access —Hotels and Airports
Employees who travel may need to access their e-mail at night. Many hotels provide free high
speed internet access and Tyler employees are encouraged to use such hotels whenever possible. If
an employee's hotel charges for internet access it is reimbursable up to $10.00 per day. Charges for
internet access at airports are not reimbursable.
6. International Travel
All international flights with the exception of flights between the U.S. and Canada should be
reserved through TMC using the "lowest practical coach fare" with the exception of flights that are
six (6) or more consecutive hours in length. In such event, the next available seating class above
coach shall be reimbursed.
When required to travel internationally for business, employees shall be reimbursed for photo fees,
application fees, and execution fees when obtaining a new passport book, but fees related to
passport renewals are not reimbursable. Visa application and legal fees, entry taxes and departure
taxes are reimbursable.
The cost of vaccinations that are either required for travel to specific countries or suggested by the
U.S. Department of Health & Human Services for travel to specific countries, is reimbursable.
Section 4, Meals & Incidental Expenses, and Section 2.b., Rental Car, shall apply to this section.
**-*:. tyler
21
••�°°• ty ler
• technologies
Exhibit C
Maintenance and Support Agreement
We will provide you with the following maintenance and support services for the Tyler Software. Capitalized
terms not otherwise defined will have the meaning assigned to such terms in the Agreement.
1. Term. We provide maintenance and support services on an annual basis. The initial term commences on
the Effective Date and remains in effect for one (1) year. The term will renew automatically for additional
one (1) year terms unless terminated in writing by either party at least thirty (30) days prior to the end of
the then -current term.
Maintenance and Support Fees. Your year 2 maintenance and support fees for the Tyler Software are listed
in the Investment Summary, and your payment obligations are set forth in the Invoicing and Payment Policy.
We reserve the right to suspend maintenance and support services if you fail to pay undisputed
maintenance and support fees within forty-five (45) days of our written notice. We will reinstate
maintenance and support services only if you pay all past due maintenance and support fees, including all
fees for the periods during which services were suspended.
3. Maintenance and Support Services. As long as you are not using the Help Desk as a substitute for our
training services on the Tyler Software, and you timely pay your maintenance and support fees, we will,
consistent with our then -current Support Call Process:
3.1 perform our maintenance and support obligations in a professional, good, and workmanlike manner,
consistent with industry standards, to resolve Defects in the Tyler Software (limited to the then -current
version and the immediately prior version); provided, however, that if you modify the Tyler Software
without our consent, our obligation to provide maintenance and support services on and warrant the
Tyler Software will be void;
3.2 provide telephone support during our established support hours;
3.3 maintain personnel that are sufficiently trained to be familiar with the Tyler Software and Third Party
Software, if any, in order to provide maintenance and support services;
3.4 provide you with a copy of all major and minor releases to the Tyler Software (including updates and
enhancements) that we make generally available without additional charge to customers who have a
maintenance and support agreement in effect; and
3.5 provide non -Defect resolution support of prior releases of the Tyler Software in accordance with our
then -current release life cycle policy.
-"-*: a tyler
22
4. Client Responsibilities. We will use all reasonable efforts to perform any maintenance and support services
remotely. Currently, we use a third -party secure unattended connectivity tool called Bomgar, as well as
GotoAssist by Citrix. Therefore, you agree to maintain a high-speed internet connection capable of
connecting us to your PCs and server(s). You agree to provide us with monitored local administrative
privileges as we may reasonably require to perform remote services. We will, at our option, use the secure
connection to assist with proper diagnosis and resolution, subject to any reasonably applicable security
protocols. If we cannot resolve a support issue remotely, we may be required to provide onsite services. In
such event, we will be responsible for our travel expenses, unless it is determined that the reason onsite
support was required was a reason outside our control. Either way, you agree to provide us with monitored,
full and free access to the Tyler Software, working space, adequate facilities within a reasonable distance
from the equipment, and use of machines, attachments, features, or other equipment reasonably necessary
for us to provide the maintenance and support services, all at no charge to us.
5. Hardware and Other Systems. If you are a self -hosted customer and, in the process of diagnosing a software
support issue, it is discovered that one of your peripheral systems or other software is the cause of the
issue, we will notify you so that you may contact the support agency for that peripheral system. We cannot
support or maintain Third Party Products except as expressly set forth in the Agreement.
In order for us to provide the highest level of software support, you bear the following responsibility related
to hardware and software:
(a) All infrastructure executing Tyler Software shall be managed by you;
(b) You will maintain support contracts for all non -Tyler software associated with Tyler Software (including
operating systems and database management systems, but excluding Third -Party Software, if any); and
(c) You will perform daily database backups and verify that those backups are successful.
Other Excluded Services. Maintenance and support fees do not include fees for the following services: (a)
initial installation or implementation of the Tyler Software; (b) onsite maintenance and support (unless Tyler
cannot remotely correct a Defect in the Tyler Software, as set forth above); (c) application design; (d) other
consulting services; (e) maintenance and support of an operating system or hardware, unless you are a
hosted customer; (f) support outside our normal business hours as listed in our then -current Support Call
Process; or (g) installation, training services, or third party product costs related to a new release.
Requested maintenance and support services such as those outlined in this section will be billed to you on a
time and materials basis at our then current rates. You must request those services with at least one (1)
weeks' advance notice.
7. Current Support Call Process. Our current Support Call Process for the Tyler Software is attached to this
Exhibit C at Schedule 1.
••-0°• ty(er
V-
23
••�°�� t ler .•. y
technologies
Exhibit C
Schedule 1
Service Level Agreement
Agreement Overview
This SLA outlines the information technology service levels that Tyler will provide to Client to ensure the
availability of the Hosting Services that Client has requested Tyler to provide. All other support services are
documented in the applicable Support Call Process. All defined terms not defined below have the meaning set
forth in the Agreement.
Definitions
Attainment: The percentage of time a service is available during a billing cycle, with percentages rounded to the
nearest whole number.
Client Error Incident: Any service unavailability resulting from Client's applications, content or equipment, or the
acts or omissions of any of Client's service users or third -party providers over whom Tyler exercises no control.
Downtime: Those minutes during which the applicable software products are materially unavailable for Client's
use. Downtime does not include those instances in which only a Defect is present.
Service Availability: The total number of minutes in a billing cycle that a given service is capable of receiving,
processing, and responding to requests, excluding maintenance windows, Client Error Incidents and Force
Majeure.
Service Availability
The Service Availability of the applicable software products is intended to be 24/7/365. Tyler sets Service
Availability goals and measures whether Tyler has met those goals by tracking Attainment.
Client Responsibilities
Whenever Client experiences Downtime, Client must make a support call according to the procedures outlined in
the applicable Support Call Process exhibit. Client may escalate through the hosting hotline. Client will receive a
support incident number. Any Downtime is measured from the time Tyler intakes Client's support incident.
•
• •'• tyler
24
To track attainment, Client must document, in writing, all Downtime that Client has experienced during a billing
cycle. For purposes of this Service Level Agreement, billing cycle shall be based on each calendar quarter. Client
must deliver such documentation to Tyler within thirty (30) days of a billing cycle's end.
The documentation Client provides must substantiate the Downtime. It must include, for example, the support
incident number(s) and the date, time and duration of the Downtime(s).
Tyler Responsibilities
When Tyler's support team receives a call from Client that a Downtime has occurred or is occurring, Tyler will
work with Client to identify the cause of the Downtime (including whether it may be the result of a Client Error
Incident or Force Majeure). Tyler will also work with Client to resume normal operations.
Upon timely receipt of Client's Downtime report, outlined above, Tyler will compare that report to Tyler's own
outage logs and support tickets to confirm that a Downtime for which Tyler was responsible indeed occurred.
Tyler will respond to Client's Downtime report within thirty (30) days of receipt. To the extent Tyler has
confirmed Downtime for which Tyler is responsible, Tyler will provide Client with the relief set forth below.
Client Relief
When a Service Availability goal is not met due to Client's confirmed Downtime, Tyler will provide Client with
relief that corresponds to the percentage amount by which that goal was not achieved, as set forth in the Client
Relief Schedule below.
Notwithstanding the above, the total amount of all relief that would be due under this SLA will not exceed 5% of
the fee for any one billing cycle. Issuing of such credit does not relieve Tyler of its obligations under the
Agreement to correct the problem which created the service interruption. A correction may occur in the billing
cycle following the service interruption. In that circumstance, if service levels do not meet the corresponding
goal for that later billing cycle, Client's total credits will be doubled, with equal relief being provided in that later
billing cycle.
Client Relief Schedule
Targeted Attainment
Actual Attainment
Client Relief
100%
8-99%
Remedial action will be taken at no
additional cost to Client.
100%
5-97%
Remedial action will be taken at no
additional cost to Client. 4% credit
of fee for affected billing cycle will
be posted to next billing cycle
••° °• tyler
••� .
25
100% 95% Remedial action will be taken at no
additional cost to Client. 5% credit
of fee for affected billing cycle will
be posted to next billing cycle
Client may request a report from Tyler that documents the preceding billing cycle's Service Availability,
Downtime, any remedial actions that have been/will be taken, and any credits that may be issued. That report is
available by contacting the hosting hotline through the support portal(s).
Applicability
The commitments set forth in this SLA do not apply during maintenance windows, Client Error Incidents, and
Force Majeure.
Tyler performs maintenance during limited windows that are historically known to be reliably low -traffic times. If
and when maintenance is predicted to occur during periods of higher traffic, Tyler will provide advance notice of
those windows and will coordinate to the greatest extent possible with Client. When maintenance is scheduled to
occur, Tyler will provide approximately two (2) weeks' advance written notice to the contact information that
Client supplies on Client notification form. When emergency maintenance is scheduled, Client will receive an
email at that same contact point.
Force Majeure
Client will not hold Tyler responsible for meeting service levels outlined in this SLA to the extent any failure to do so is
caused by Force Majeure. In the event of Force Majeure, Tyler will file with Client a signed request that said failure be
excused. That writing will include the details and circumstances supporting Tyler's request for relief with clear and
convincing evidence pursuant to this provision. Client will not unreasonably withhold its acceptance of such a
request.
••::•. tyler
26
e%*
.,.t y
• tecer
hnologies
Exhibit C
Schedule 2
Support Call Process
Support Channels
Tyler Technologies, Inc. provides the following channels of software support:
(1) Tyler Community — an on-line resource, Tyler Community provides a venue for all Tyler clients with
current maintenance agreements to collaborate with one another, share best practices and resources,
and access documentation.
(2) On-line submission (portal) —for less urgent and functionality -based questions, users may create
unlimited support incidents through the customer relationship management portal available at the Tyler
Technologies website.
(3) Email —for less urgent situations, users may submit unlimited emails directly to the software support
group.
(4) Telephone —for urgent or complex questions, users receive toll -free, unlimited telephone software
support.
Support Resources
A number of additional resources are available to provide a comprehensive and complete support experience:
(1) Tyler Website — www.tylertech.com —for accessing client tools and other information including support
contact information.
(2) Tyler Community —available through login, Tyler Community provides a venue for clients to support one
another and share best practices and resources.
(3) Knowledgebase —A fully searchable depository of thousands of documents related to procedures, best
practices, release information, and job aides.
(4) Program Updates — where development activity is made available for client consumption.
Support Availability
Tyler Technologies support is available during the local business hours of 8 AM to 5 PM (Monday — Friday) across
four US time zones (Pacific, Mountain, Central and Eastern). Clients may receive coverage across these time
zones.
Tyler's Brazos eCiations solutions offers 24/7 support of the product and software.
Tyler's holiday schedule is outlined below. There will be no support coverage on these days.
New Year's Day
Thanksgiving Day
Memorial Day
Day after Thanksgiving
Independence Day
Christmas Day
••:;.. tyler
27
Labor Day
Issue Handling
Incident Tracking
Every support incident is logged into Tyler's Customer Relationship Management System and given a unique
incident number. This system tracks the history of each incident. The incident tracking number is used to track
and reference open issues when clients contact support. Clients may track incidents, using the incident number,
through the portal at Tyler's website or by calling software support directly.
Incident Priority
Each incident is assigned a priority number, which corresponds to the client's needs and deadlines. The client is
responsible for reasonably setting the priority of the incident per the chart below. The goal of this structure is to
help the client clearly understand and communicate the importance of the issue and to describe expected
responses and resolutions.
Priority
Level
Characteristics of Support Incident
Support incident that causes (a)
complete application failure or
application unavailability; (b)
1
application failure or unavailability in
Critical
one or more of the client's remote
location; or (c) systemic loss of multiple
essential system functions.
Support incident that causes (a)
repeated, consistent failure of essential
functionality affecting more than one
2
user or (b) loss or corruption of data.
High
Priority Level 1 incident with an existing
circumvention procedure, or a Priority
Level 2 incident that affects only one
3
user or for which there is an existing
Medium
circumvention procedure.
28
Resolution Targets
Tyler shall provide an initial response to Priority Level 1
incidents within one (1) business hour of receipt of the
support incident. Tyler shall use commercially
reasonable efforts to resolve such support incidents or
provide a circumvention procedure within one (1)
business day. Tyler's responsibility for lost or corrupted
data is limited to assisting the client in restoring its last
available database.
Tyler shall provide an initial response to Priority Level 2
incidents within four (4) business hours of receipt of
the support incident. Tyler shall use commercially
reasonable efforts to resolve such support incidents or
provide a circumvention procedure within ten (10)
business days. Tyler's responsibility for loss or
corrupted data is limited to assisting the client in
restoring its last available database.
Tyler shall provide an initial response to Priority Level 3
incidents within one (1) business day of receipt of the
support incident. Tyler shall use commercially
reasonable efforts to resolve such support incidents
without the need for a circumvention procedure with
the next published maintenance update or service
pack. Tyler's responsibility for lost or corrupted data is
limited to assisting the client in restoring its last
available database.
•
• •°• tyler
Priority
Level
Characteristics of Support Incident
Resolution Targets
Support incident that causes failure of
Tyler shall provide an initial response to Priority Level 4
4
non -essential functionality or a
incidents within two (2) business days. Tyler shall use
Non-
cosmetic or other issue that does not
commercially reasonable efforts to resolve such
critical
qualify as any other Priority Level.
support incidents, as well as cosmetic issues, with a
future version release.
Incident Escalation
Tyler Technology's software support consists of four levels of personnel:
(1) Level 1: front-line representatives
(2) Level 2: more senior in their support role, they assist front-line representatives and take on escalated
issues
(3) Level 3: assist in incident escalations and specialized client issues
(4) Level 4: responsible for the management of support teams for either a single product or a product group
If a client feels they are not receiving the service needed, they may contact the appropriate Software Support
Manager. After receiving the incident tracking number, the manager will follow up on the open issue and
determine the necessary action to meet the client's needs.
On occasion, the priority or immediacy of a software support incident may change after initiation. Tyler
encourages clients to communicate the level of urgency or priority of software support issues so that we can
respond appropriately. A software support incident can be escalated by any of the following methods:
(1) Telephone —for immediate response, call toll -free to either escalate an incident's priority or to escalate
an issue through management channels as described above.
(2) Email — clients can send an email to software support in order to escalate the priority of an issue
(3) On-line Support Incident Portal — clients can also escalate the priority of an issue by logging into the
client incident portal and referencing the appropriate incident tracking number.
Remote Support Tool
Some support calls require further analysis of the client's database, process or setup to diagnose a problem or to
assist with a question. Tyler will, at its discretion, use an industry -standard remote support tool. Support is able
to quickly connect to the client's desktop and view the site's setup, diagnose problems, or assist with screen
navigation. More information about the remote support tool Tyler uses is available upon request.
e
• • tyler
V11
29
s � tyler
0 technologies
Exhibit D
Statement of Work
[REMAINDER OF PAGE INTENTIONALLY LEFT BLANK]
v -' tyler
tec!rtn;rp�>•
30
Exhibit D
Statement of Work
Brazos eParking
Software and Implementation Services
Prepared for:
City of Renton, WA
Prepared by:
Tyler Technologies, Inc.
www.tylertechnologies.com
August 12, 2019
tyler
• technologies
Empowering people who serve the public"
TABLE OF CONTENTS
Acronyms......................................................................................................................................................1
Definitions..................................................................................................................................................... 1
ProjectScope & Summary............................................................................................................................ 2
ImplementationStages.................................................................................................................................4
DataConversion............................................................................................................................................5
KeyProject Assumptions.............................................................................................................................. 5
Outof Scope.................................................................................................................................................. 6
Risk/Mitigation Strategy............................................................................................................................... 7
CriticalSuccess Factors................................................................................................................................. 9
Future Amendments to Scope....................................................................................................................10
ProjectManagement..................................................................................................................................10
Staffing........................................................................................................................................................10
Documentation........................................................................................................................................... 12
ProjectStatus Meetings..............................................................................................................................12
SOWAttachments Listing........................................................................................................................... 14
Attachment A— Work Acknowledgment.................................................................................................... 15
AttachmentB —Change Order Form..........................................................................................................16
Attachment C — Hardware / Software Requirements.................................................................................17
Attachment D — Brazos Solutions Summary...............................................................................................18
Attachment E — Project Deliverables and Project Schedule....................................................................... 24
0 •
1
••:•• tyler
•• technologies
Acronyms
The following acronyms are used throughout the Statement of Work (SOW).
• WP —Work Plan
• RMS — Records Management System
• CMS — Court Management System
• ECS — Electronic Citation System
• HH - Handheld
• MDT — Mobile Data Terminal (any laptop mobile platform running a standard operating
system)
• SYNC — A process through which citation data is transmitted from the device to the
Brazos server and through which new software for the MDT's are transmitted from the
Brazos server to the device.
Definitions
The following definitions are used throughout the SOW.
• Acceptance of Deliverable —Written notification from City of Renton to Tyler, signed by
the responsible City of Renton Project Manager, indicating that the Deliverable has been
evaluated and satisfies the Acceptance Criteria of each deliverable
• Deliverables - Any materials procured or prepared by Brazos or services provided by
Tyler to City of Renton
••:0 tyler
ile technologies
Project Scope & Summary
This Statement of Work provides the understanding of the objectives, approach, schedule, and
deliverables for this engagement.
Any standard interfaces purchased are detailed in SOW Attachment D — Brazos Solutions
Summary. It is important for the Client to read the portion of the attachment related to each
interface purchased to understand its full functionality.
The summary scope of this project includes the following:
1. The ECS will, at a minimum, conform to the requirements as outlined in the Parking
Citation System RFP, as referenced in License and Service Agreement Exhibit E. Further
details of how each requirement will be accomplished will be determined at the Kick -Off
Meeting and subsequent requirements gathering meetings.
2. The ECS will provide the ability to add additional customized forms not specified in the
executed Sales documentation (at an additional cost).
3. The ECS must enable officers to enter text notes.
4. The ECS must conform to Washington Administrative Office of the Courts (AOC) citation
numbering system and other requirements (may need to submit sample citation to
court for certification/approval).
5. The ECS must allow the City to customize the layout of the citation printout as
permitted by the State of Washington and/or King County participating agencies.
6. The ECS must create an electronic data file when a citation is completed and approved
and provide the ability to transfer that data file which will then be made available for
import into the CMS / RMS / 3rd Party systems as specified in the contract. The ECS
audit trail must provide tracking of exported data's receipt acceptance/failure into CMS
/ RMS / integrated 3rd Party systems.
7. The ECS will include the Citation Entry Screen (CES) that will allow authorized users with
the ability to enter data from manual (paper) citations into the ECS through the secure
web portal.
8. The ECS must be able to import citation payment information provided by the CMS and
update ECS records appropriately.
9. The ECS must be able to import vehicle information (including Registered Owner
information) from Tyler's NW (New World) Message Switch and from Genetec's AutoVu
system. This information will be used by the ECS to auto -population fields in Citations,
Warnings, Abandoned Vehicle Notices and Abandoned Vehicle Letters.
10. The ECS will use ADFS (Active Directory Federated Services) integration so City staff can
use their Renton domain credentials to log onto the ECS system.
° tyler
• t���nn«iv�=,es
11. The ECS will provide an Abandoned Vehicle Report and a map view of all unresolved
abandoned vehicles which will include a differentiator (such as color) between those
less than 72 hours old and greater than 72 hours old.
••::®• tyler
•• technologies
r ;
-(U 40 C
-
'4' a-
CLE
a a
in
C.
L7'
aan'sol: POOM/aseyd
> � a �
a
� a. 'C
L.Y
N
}
a
t� a
c 'a'
E
2u'issa oad an]I/uoi}:)npoad
a0 m 1
C
na
`+-
61
a w
o s
•CCn
c
0 6 v+
a a
w
,7 id .w
a
V
w .e
o
.y vi '.0
c a
b � N -M
�C
7, �i r
4^ u, D-
u
�
w
-Bur}sal aaueidaD:)V �g guiuleil :aasn ,pu3
- .c CL
Q
r^ c a
�f'a
y '.m O
a C ha
ob c`�
w-
o
a_ w n
"D
'�
a -
i.L' u
V
V .
uoilePPA uoiiean ljuoJ''8 Nululell.
aasn aao
} W)
a C
iA w O hq
�c �C .a,
(J
'•.G,
i'.V C
C
`'C �w
.m `m a w 'E
.O
a
.�
a w
n � c n
a n a, a
�}
`u
c a ro
a 2
�n a
E C aJ
a,
^ rt
ru w
d V
O c w G
w C
-C)
V'
v
4n
aL
aui jaQ O SSassV
ba
u w
C
O. iC c
p
a,
_O C '6J i4
ry7 a.+ y UJ 4U .Qi
E °J E
�
E s c
C iCa ,
c .� n
C_ M � p. �
c w w c
� a � � �� d
E
� ` 'C
o .40
C
C. C ..
C o
w e tw
6 s o ,a
w on C of
n_+ c
" a
a
°
iw a 'c
_ 5
w M L
a
u
O U r7
ra '�.1 •�
C 0.
6J C
d n_
L ua.rleiliui !g lluluueld
Each stage, as established above, is designed to provide a point at which a full review of the stage
objectives is assessed for completeness. When a stage is complete, a Work -Acknowledgement
Form [see SOW Attachment A (sample) — Work Acknowledgement Form] is completed and signed
by the Client signifying acceptance of that stage and the beginning of the next stage. Each stage is
dependent on the results of the previous stage, and therefore each stage of the methodology
cannot begin until the previous stage is completed and approved.
Data Conversion
Data Conversion is referenced in the Implementation stages methodology graphic; however, no
data conversion is included within the scope of this project for City of Renton. The graphic is
representative of the standard implementation methodology utilized throughout the various
product lines offered by Tyler Technologies.
Key Project Assumptions
• Client and Tyler shall review their responsibilities before work begins to ensure that Services
can be satisfactorily completed.
• Client will provide Tyler with monitored access to its equipment, systems, and personnel to
the extent needed to complete the defined Services.
• Client will provide work space for Tyler Services for work completed on Client premises.
• Tyler shall initially implement the most current version of the Tyler software at the time of
the contract signing. During the implementation, Tyler will provide newer releases of the
software that meet or exceed the version available at contract signing.
• Client will maintain primary responsibility for the scheduling of Client employees and facilities
in support of project activities.
• Client will allow users unauthenticated access to the following web addresses provided by
Tyler to ensure adequate access to system resources:
o syncsvc.brazostech.com (ports 80 and 443)
o syncsvc2.brazostech.com (ports 80 and 443)
o Reports2014.brazostech.com (ports 80 and 443)
o www.brazostech.com (ports 80 and 443)
o my.brazostech.com (ports 80 and 443)
o brazossupport.tylertech.com (ports 80 and 443)
• Client is responsible for proper site preparation, hardware, software, and network
configuration (for synchronization of HH devices) in accordance with Tyler specifications as
set forth in Attachment C
• Client has, or will provide, access licenses and documentation of existing system to any 3rd
party system software which Tyler will be required to read, write or exchange data.
•
••:•:•• tyler
•• technologies
• Client has, or will provide, a development/testing environment for interface testing as they
are developed by Tyler.
• Tyler shall be responsible for implementing a functioning version of the application software
(assuming Client has installed the proper hardware, software, and networking devices).
• All deliverables and timelines assigned to the Client will be held to the same standards of
delivery as those assigned to Tyler Technologies.
• Installation of Hardware required in City Vehicles shall be completed by the participating
agencies Personnel and facilities. They may decide to purchase mounts on their own or opt to
purchase from Tyler.
• The Client will deploy initially 3 handheld devices/printers. The specific type/brand yet to be
determined during project implementation.
• Deployment of the Tyler Brazos ECS for the Client will utilize the existing Tyler hosted server
environment.
• All Client personnel involved in the Project will participate fully in the training provided by
Tyler Technologies.
• If an Interface to any CMS / RMS / Device systems are included in this Phase of the project, it
should be reflected in the contract, and will include the synchronization of tables/files.
Interfaces included.
o Court Interface —
■ Washington AOC — Vehicle Related Violations
■ Court Payment Import
o ALPR — AutoVu by Genetec
■ Additional Specifics to be determined as Implementation Team is still waiting
on SOW from Genetec
o ADFS (Active Directory Federated Services)
o NWLERMS — New World Law Enforcement Records Management System
o Device Level Interface — NW Mobile 2018.1. Upgrading to 2018.4 in near future
■ Integration to run returns via NW Message Switch which will allow return
data to be parsed to populate parking citations, parking warnings and
abandoned vehicle notices
Out of Scope
0
000•0o tyler
• Custom interfaces. Custom interfaces involve the development of a standard, repeatable
process for transferring information into or out of the Tyler software. These interfaces may
take the form of a user -initiated import/export program, an API, or a web service. There are
no custom interfaces included in the scope of the agreement unless detailed in Attachment D
— Brazos Solutions Summary.
• Custom reports. Custom reports involve the development of new reports that are not offered
as part of the standard reporting package and modifications to existing reports. There are no
custom reports included in the scope of the agreement unless detailed in Attachment D —
Brazos Solutions Summary.
• Undocumented requirements. Undocumented requirements include requirements not
specified in this Statement of Work and associated attachments.
• Post System Acknowledgement Configuration. System Acknowledgement requirements are
met at the completion of End User Training and User Acceptance Testing stage. Any changes
requested of the Tyler implementation team to alter the configuration, post
acknowledgement of these milestones, must be documented through a Change Order and
may incur additional time and/or costs. Client may have access to built-in configuration tools,
so, when available, is free to reconfigure or create a new configuration as required or desired.
If assistance using these tools is required, additional change orders may apply.
Risk/Mitigation Strategy
Unavailability/Incompatibility of Staff
Risk: Tyler recognizes that individuals assigned to projects may become unavailable due to
various causes. Further, Tyler recognizes that individuals sometimes clash for reasons of
incompatibility. Tyler schedules team members based on all the projects to which those
individuals are assigned. Unavailability may occur due to unforeseen circumstances such as family
matters or the employee's departure from Tyler employment. Incompatibility creates intolerance
in project objectives and tasks and creates unnecessary delays and can lead to project failure if
not corrected.
Mitigation: In the event a Tyler project member is determined to be unavailable, a Tyler manager
will consult with Client on alternatives such as a temporary replacement or substitute of the
person. Likewise, a similar response is expected from the Client if their team member is
unavailable.
Incompatibility is addressed first through attempts to resolve the compatibility issues between
individuals. Failing resolution, team members must be replaced. In the event a Tyler team
member is determined to be incompatible, Tyler will replace with a new team member and
provide time to orient to the project before assuming their respective responsibilities.
Client Staff unavailability
a
tyler��•�oo
Risk: Delays in the project timeline will occur if appropriate Client staff is unavailable to meet
with or respond to Tyler for timely decisions and or directions.
Mitigation: Client should ensure that staff assigned to this project is given sufficient priority and
authority to work with Tyler while completing other Client responsibilities in a timely fashion.
Decisions must be made in hours and days, not weeks.
Scope Changes
Risk: Poorly defined projects always take longer than expected or cost more than expected
because of poorly defined scope at the beginning of the project.
Mitigation: Both parties must ensure that the scope of the project is well stated and completely
defined to the best of each party's knowledge. Functional requirements should be reviewed
carefully to ensure completeness. Change Orders are required to document any subsequent
impact on schedule and/or costs.
Activity Focus
Risk: Activity Focus is the risk that minor activities consume time that should otherwise be
dedicated to major activities of the project, with the end result of time and/or costs overrunning
budget. This risk is sometimes associated with efforts that lead to scope changes. Examples
include meetings of little substance or that go longer than they need, or time consumed
investigating undocumented functionality or other activities not in scope.
Mitigation: Project Managers for both Parties must guard themselves to avoid focus drift by
ensuring the focus is squarely on meeting deadlines, services, and configuration requirements of
the implementation as planned and documented in the planning, assessment and definition
stages.
Achievable Goals
Risk: The expectations of this project are set too high or are not explicit or clear to Client Staff
and thus not communicated to Tyler through Functional Requirements and clearly stated scope.
Mitigation: The parties must ensure, through the Contract and Task Orders, that the goals of the
project are explicit, well defined and attainable, and that both parties have "signed off' on the
requirements.
Technology Age
Risk: This risk is highly dependent on the choice of Tyler products, the M DT's to be used for data
capture, and whether the Client is hosting any of those products. If the Client will be hosting its
own servers, the technology utilized should be robust enough to meet the Client's needs for
several years into the future. Technology that barely meets minimum requirements today will be
insufficient as the system and its needs grow.
Q
8 •�i OHO �
t l e r
�� ` kllli)�O,riF
Mitigation: Tyler will assist Client in determining optimal technology and plans to guard against
premature obsolescence.
Critical Success Factors
In order to successfully execute the services described herein, there are several critical success
factors for the project that must be closely monitored. These factors are critical in
expectations between the Client and Tyler, identifying and monitoring project risks, and
promoting strong project communication.
Knowledge Transfer - While Tyler cannot guarantee specific expertise for Client staff as a
result of participating in the project, Tyler shall make reasonable efforts to transfer
knowledge to the Client. It is critical that Client personnel participate in the analysis,
configuration and deployment of the Tyler software in order to ensure success and to transfer
knowledge across the organization. After completion of the production phase, the Client will
be responsible for administering the configuration and introduction of new processes in the
Tyler system.
Dedicated Client Participation —Tyler fully understands that Client staff members have daily
responsibilities that shall compete with the amount of time that can be dedicated to the Tyler
implementation project. However, it is critical that the Client understands and acknowledges
that its staff must be actively involved throughout the entire duration of the project as
defined in the Project Plan. Tyler shall communicate any insufficient participation of Client
and Tyler resources, as well as the corresponding impact(s), through Project Status Reports.
Acknowledgement Process —Acknowledgment must be based on criteria. The objectives and
tasks of each stage of a project provide the basic criteria by which to judge acceptance of a
stage is to be granted. Within each stage additional criteria will be developed by team
members on which to judge future stages. For example, User Acceptance Testing will be
based on criteria developed in earlier stages.
As resources are consumed, Tyler shall provide the Client with a Work Acknowledgement Form
[see Attachment A -(Sample) Work Acknowledgement Form] to formalize receipt. The Work
Acknowledgment Form is subsequently signed by the appropriate Client stakeholder(s) and faxed
or emailed to Tyler. Timely and honest acceptance is required to maintain project momentum.
Failure to properly establish acceptance criteria or failure to accept a properly completed stage
will cause delays in the project.
In an effort to ensure quality and complete satisfaction with each stage of the project, Tyler's
Professional Services Division has established the following rule: A Signed Work
Acknowledgement Form (see Attachment A) is required upon completion and Client-
tyler9
• t� �, I ut�ii�>i'�r ,
acknowledgement of the resources consumed on the project. Stage signoff is also required
before proceeding to the next stage in the process.
Managing Project Scope - In an effort to implement the project on time and within budget,
both Tyler and Client agree to limit the software and professional services to only those items
identified in this Statement of Work. Expanded scope results in additional costs.
Change orders or contract addendums for additional items outside the scope of the defined
project requirements must be submitted in advance and signed by project stakeholders before
work can be accomplished on those items. Likewise, reductions of the defined scope will also
require a Change Order.
Future Amendments to Scope
Future changes in the project scope, beyond the capability of a Change Order, will assume the
appropriate processes outlined in this Statement of Work and in the Agreement, unless future
scope changes require a different or modified process. If no new Statement of Work is required,
then new functionality and payment requirements are provided for in an amendment to the
initial Agreement.
Project Management
Tyler performs ongoing project management services throughout the implementation in order to
plan and monitor execution of the project. Project management includes the following tasks:
• Project plan
• Project document management
• Issue log management and escalation
• Status reporting
• Change order management
• Resource management
• Executive project oversight via Executive Sponsor and Project Review Committee
By mutual agreement, some project management tasks are shared between the Tyler Project
team and the Client Project Manager/Stakeholders.
Staffing
Every reasonable effort is made to maintain a consistent project team from Tyler for the duration
of the project. Should the Client have concerns related to assigned resources, those concerns
should be submitted to the Tyler Project Manager or Tyler Management Staff for review and
consideration. Tyler will make staffing decisions based on appropriate skill set and other soft skills
of resources deemed compatible to the success of the project.
Tyler Brazos Team
Project Manager — TBD upon contract execution
•
10
••::•®tyler
•• technologies
As Project Manager, TBD will be responsible for establishing and administering controls to ensure
the quality of deliverables are acceptable to the Client, monitoring project activities to ensure
project schedules are met, and providing monthly Full Status Meetings. Project Manager will be
able to authorize changes and will be expected to refer any problems or issued that cannot be
resolved by on -site implementation staff to company management.
Technical Lead — TBD upon contract execution
The Technical Lead will be responsible for design and architecture of the Tyler Brazos software.
Training Lead — TBD upon contract execution
The Training Lead will be responsible for ensuring that all the Client personnel specified in this
SOW are appropriately trained according to the requirements of their participation in the project.
City of Renton Team
Project Manager— Debbie Scott / 425-430-6939 / dscott@rentonwa.gov
The Project Manager for the Client will be responsible for establishing and administering controls
to ensure the quality of deliverables are acceptable to the Client. The Project Manager will also
make decisions about any changes to the implementation plan or technical aspects of the system.
Resource — Department Lead (POLICE) — Dianne Ford & Shailey Wilkinson
Resource — Department Lead (COURT) — Bonnie Woodrow
Resource — Department Lead (IT) — Debbie Scott
Project Schedule
Upon execution of the contract, the parties will subsequently collaborate during the project
planning and initiation stage to determine a start date for services to be rendered. Upon
initiation of these services, Tyler shall work with Client to collaboratively define a baseline or
preliminary project schedule/plan. Given the fact that project schedules are working documents
that change over the course of the project, Tyler shall work closely with Client to update,
monitor, agree, and communicate any required changes to the project schedule. A Sample
Project Schedule is included in Attachment E — Deliverables and Project Schedule.
Development Tools
No special development tools are required for the Tyler software. Tyler source code is not
accessible (unless through the requirements of an Escrow Agreement).
0
• 9�0 tyler
11 ��•��®
• tE, hru;io�,i�>_,
The configuration tools are built into the software, and the Client has full access. The Tyler
implementation staff will use these same configuration tools to set up the system with the Client.
The Client will receive training on the use of these tools. If assistance with using these tools is
required, additional change orders may apply.
Documentation
Tyler -provided documentation
Over the course of the 6-stage implementation lifecycle, the Tyler project team will provide
stage -specific documentation in a range of formats (both editable and non-editable). Examples
include:
• Data collection documents (MS Excel and/or MS Word) for configuration
• Training documentation templates (MS Word and MS PowerPoint)
• Other documentation as required for the specifics of the project
Client -provided documentation
A definitive list of Client -provided documentation is not possible until all aspects of the
implementation are determined, usually in the beginning stages of the project. Certainly, the
Client's assistance in completing the Tyler -provided forms and requests for configuration
information is essential to a successful project. The Tyler Project Manager will provide the Client
with details of the documentation necessary for each product to be successfully implemented.
The list below is a sample of the types of documentation that is likely to be requested.
Documentation originated by the Client includes:
• Application Programming Interface documents (API's) for any third -party software system to
which the Tyler software will interface and exchange data
• Workflow documentation on the Client's current business processes
• Copies of pertinent ordinances or other controlling authorities
• Fee schedules, when applicable
• Copies of existing forms and other documents presented to the public and expected to be
derived from the Tyler Software
Project Status Meetings
Communication is crucial to the success of the project. Regular communication between Tyler
and the Client staff are required.
0
1000
12 tyler
•• te��::I�r�t7ioFiE .
Full Status Meetings
Monthly Reports to the Client Staff (may be done remotely)
• Presented by Tyler project manager
• The full status meeting schedule will begin upon acceptance of the SOW
• Status of major activities
• Target dates for completion of remaining tasks
• Potential delays in reaching target dates and the basis for those delays
• Proposed revisions to the overall work schedule — if any
Progress Meetings
Bi-weekly in writing — prepared by Tyler Project Manager
• Recap of previous period's work
• Preview of next period's tasks
• Status of major activities
• Target dates for completion of remaining tasks
• Potential delays in reaching target dates and the basis for those delays
• Proposed revisions to the overall work schedule — if any
Communication Plan
The purpose of the Communication Plan is to define and document on -going
communication commitments between Tyler and the Client. The Project Manager will
provide a contact list to Tyler for each agency representative for direct
communications with that respective agency. These individuals will be responsible for
department policy, budget and overall strategic direction of the project.
The Tyler Project Manager, will create, maintain, and distribute a contact list for all
project team members. This list will be distributed to all team members as required or
requested via email and will include phone extension, cell number, email addresses,
etc. of all Tyler project team members, the Client project team members as applicable.
0
13 .,. ptyler
SOW Attachments listing
SOW Attachment A — (Sample) Work Acknowledgement Form
This form provides the means for the Client to accept work provided or provide reason for denial
of a work.
SOW Attachment B — (Sample) Change Order Form
Any change in the project must have a completed and approved Change Order.
SOW Attachment C - Hardware / Software Requirements
This document provides the recommended hardware/software requirements for the Tyler
system. Performance using systems which do not meet these requirements may not have
expected performance levels.
SOW Attachment D — Brazos Solutions Summary
This document provides a summary description of the purpose and function of the Brazos
applications included in the scope of this project.
SOW Attachment E — Deliverables and Project Schedule
This document provides a summary of project deliverables and project schedule.
•
•:: •®
14 • t ter
•• technologies
Attachment A — Work Acknowledgment
Work Acknowledgment
Client:
Date:
Visit/Deliverable:
Accomplishments Performed by Notes
I am satisfied with the work performed for this stage, and/or deliverable.
ElI am NOT satisfied with the work performed for this stage, and/or
deliverable.
In an effort to ensure quality and complete satisfaction with each phase of the project Tyler Technology's
Professional Services division has established the following rules:
1. Projects will not be allowed to move from one phase to another without a sign off indicating
satisfaction with the work performed. The Tyler Technology project team will immediately stop all
other tasks, complete the phase at hand, and obtain sign off before moving to the next phase.
2. Customer understands that any payment not received within 45 days of invoice will result in work
stoppage. All related project tasks will be stopped until payment is received.
Print Name:
Signature:
Date:
(Please return signed copy to the Tyler Technologies project team)
a
�0e°
15 c, tyler
•
• ����. ku�cic��r�l�
Attachment B — Change Order Form
Change Order Form
Client:
Date:
Generated By:
Authorized By: _
Change Overview:
Narrative Description of Change:
Impact of Change:
Schedule Impact: Delay of milestone & sub -tasks on Tyler Technologies Implementation Project Plan including:
Task Proposed Date Changes
Cost Impact:
Change Detail Credit Debit Total
Revision No.:
No changes may be made to this project without the agreement of the Project Manager(s) and must be approved by
the Project Director. Submit endorsed Chance order to the Tvler Technologies Proiect Manager.
Date Approved Comments Approved By Signature
i
• •••
tyler16
•• •�®
•• technologies
Attachment C — Hardware / Software Requirements
Brazos eCitation — Hardware
Since the system is being hosted, the only hardware requirements would be network access so
the users can Sync the handheld devices.
We will provide a list of IP addresses during the project requirements gathering process that they
will need to allow users to access hosted websites, and also sync to upload data and download
changes.
Tyler's software is designed to operate on networks and operating systems that meet certain
requirements. Systems that do not meet the required specifications may not provide reliable or
adequate performance, and Tyler cannot guarantee acceptable results.
00
17
•�0 0 . tyler
;10 technologies
Attachment D — Brazos Solutions Summary
Brazos eCitation Applications
Tyler Technologies will work with the Client to deliver the Electronic Citation System (ECS). The
system will be installed on HH devices and allow officers to capture all information for
citations/warnings, print a copy or copies of the citation for the violator, and electronically
transfer all information into the respective Court/RMS/3,d Party system(s).
Tyler is committed to delivering a successful Electronic Citation System (ECS) project to our
customers. Our implementation approach has been highly successful, and we feel that this
process provides the best method to minimize risks and ensure a successful project. The key is to
involve the customer in all phases of developing and implementing software specifically for them,
to meet their specific needs. This process is comprised of the following:
• Kick-off Meeting. An on -site or conference call -style meeting (to be determined by Tyler) with
the project owners to define roles, responsibilities, and outline the schedule. This meeting
will also include review of all initial requirements of the SOW document and RFP and
identification of areas within the SOW that will require modification/clarification.
• Completion and acceptance of the final SOW document. Tyler will update the SOW and
provide it to the Client for review. The SOW will include all significant work tasks, steps,
timeframes and deliverables required to complete Phase I, including software installation,
interface customization, implementation, testing, and training.
• Setup and Configuration. Tyler Technologies will work with the Client to install the ECS client
software, import offenses, layout the defendant's receipt, configure reports, and any other
configuration required by the Client. The Client will perform any tasks related to enabling the
department to install any vehicle mounted hardware and setting up the printers prior to Tyler
arriving onsite for the initial training.
• Begin Pilot. The pilot program should involve up to 14 key officers per 2-day session, with 1 of
these 2-day sessions included in the contract. These users, designated by the Client, should
adapt to this technology quickly. They will be given full software training in order to
understand and become familiar with the technology. The training process includes going out
on the street and writing warning -citations with a Tyler trainer to ensure comfort with the
technology. This includes officer handheld device trials and final selection.
Operational Pilot/Rollout. The operational phase of the pilot begins once the officers are
familiar with the technology and we have verified successful data transfer to any/all CMS and
RMS systems specified in the contract. At this point the pilot officers will begin writing actual
citations. This process serves two purposes: 1) validation of the entire process prior to
engaging the entire police force, and 2) providing positive feedback to circulate within the
department prior to full rollout.
0
•• .
18 . t ier
•• technologies
Post Action. Finally, after the operational pilot/rollout, we will convene with the project
owners to determine what went well and what improvements are required of the system,
process, or any other aspect of the project. A full project review will be documented by Tyler
and provided to the Client Project Manager.
The delivery and training processes are the most significant keys to the success of this project.
We will jointly determine the Operational Pilot duration, depending upon officer success and
satisfaction and their recommendations for deployment. When all parties agree, full rollout
training and deployment will begin.
Training
Tyler will provide all training associated with the Electronic Citation System (ECS) and will identify
the Training Lead at the beginning of the project.
In order for this project to be successful, the officers need to know not only the basics of the
software but first -level troubleshooting tips for the hardware and operating system as well. It is
our experience that the officers must be proficient in the mobile hardware for this project to
have the long-term success that the Client and Tyler are looking to achieve.
The delivery and training processes are the most significant key to the success of this project. The
Tyler Training Lead will ensure that all levels of the Client personnel who utilize the Tyler Brazos
Solution will receive adequate training. Tyler will incorporate measurement tools to assist in
monitoring the end -users' competence in using the system.
Classroom Training. The Train -the -Trainer course shall involve all officers specified to participate
in the Operational Pilot (limit = 14 Officers). They will be given full software training in order to
understand and become familiar with the technology. The training process includes producing
several test citations with a trainer to ensure comfort with the application. Also provide training
on how to setup existing printers to work with Brazos.
Practical Application. The practical application phase begins once the officers are familiar with
the technology. At this point the pilot officers will begin writing real citations.
Administrator Training. The Tyler Brazos ECS provides powerful management tools with great
ease of use for agency administrators and management. Tyler will provide sufficient training to
designated management personnel for them to be able to utilize those tools as well as have a
solid understanding of the capabilities of the system.
eCitation Client Software
The Tyler Brazos ECS client software will be installed on TO BE DETERMINED allowing the officers
to write, print, and push citations electronically to the Court software system(s). All ECS software
is embedded on the Tablet/MDT/PDA and is completely functional with or without a network
connection. The software will be configured for the Client and the Client will have the ability to
•
19
••::•. t ler
e• technologies
define, approve and modify the layout of all screens and print jobs under the scope of this
agreement.
The software will have the ability to:
• Allow officers to quickly and easily capture citation information.
• Print the citation in the field for the violator using a Bluetooth or USB connection to a mobile
printer.
• Push citations via a network connection.
• The Client will have the ability to VOID a citation on the MDT/PDA, after save but before
sync. Notations as to the reason for VOID can also be required.
• The citation number sequence shall follow a unique numbering system dictated by the
Client.
• Ticket types will consist of Parking Citations, Warnings, and Abandoned Vehicle Notices.
• Charges identified will be specific to each Ticket type as further defined during the design
phase.
• Ability for System Administrator to add/modify/delete statutes, codes, etc., as further
defined during the design phase.
The applications included in the scope of this project are:
• eParking
• Abandoned Vehicle Notice and Letters
• Spatial Mapping
• COGNOS Reporting
ECS Server Software
The Client will utilize the Hosted Tyler Brazos ECS server for all reporting, interface and
administrative functions. There are no limitations to the number of users of the system and any
future hardware/software requirements or upgrades are the responsibility of the Client. The ECS
server provides the following benefits:
0
•°�°
tyler20
•..�®
•• technologies
• Access to add/change/delete any dropdown on the MDT/PDA (i.e. offenses, streets, officers,
etc.).
• Access to all reports (i.e., Citation Detail and over 35 other standard reports).
• Configuration and management of all users of the ECS for both the server and the clients.
• View and query images of citations captured via the mobile devices via internet browser.
• Creation/modification of interfaces to new/existing systems.
• Citation Entry Screen (CES) for entry of either paper tickets or modification to previously
captured information by an authorized court assigned user (Program should also have some
type of tracking capabilities for changes made in the CES).
Synchronization (Device to ECS Server)
The Tyler Brazos Solution allows officers to create, save, and print citations or other record types
with or without network connectivity. When an officer creates a citation, it is saved to non-
volatile memory on the device. The citation record can then be uploaded to the ECS server via
one of the following methods:
Real-time via cellular connection (aircard required)
• 802.x wireless connection to hotspots or LTE modems
• Ethernet LAN connection
The frequency and method of upload is defined and controlled by the Client via the Tyler Brazos
web -based configuration tool, BuildIT. Once uploaded, the data are processed through the
system according to the agency -specific workflow, which is also defined and controlled by the
Client via Build IT. All new updates and changes are also passed from the ECS Server to the device
through this same process.
Interfaces
Functionality of below interfaces must at a minimum meet the requirements of the RFP (License
and Service Agreement Exhibit Q.
• Court Interface
o Washington AOC—(VRV) Vehicle Related Violations
■ This interface will export ticket data, a ticket image, associated ticket
photos, non -printed ticket comments and Registered Owner information
for actual tickets (not warning or voids) and send this information to the
VRV system.
■ This interface will also record VRV success and failure information within
the Brazos software.
■ The Client will determine the frequency and timing of the export.
0
• ���
tyler21
i j.�C�Q
• tt i„l„l;.g lw'
o Court payment information will be imported and Brazos records updated.
• ALPR—AutoVu by Genetec
o This interface will auto -populate tickets with the following data at a minimum:
■ License Plate Number
■ License Plate State
■ First Read Date & Time
■ Second Read (Hit) Date & Time
■ Location
■ Photos
o Accepted violations (Hits) are to be sent to Brazos and available to all handheld
devices for issuing.
• ADFS (Active Directory Federated Services) integration
o This interface will allow City staff to use their Renton domain credentials to log
onto the ECS system.
• NWS (New World Systems)
o LERMS
■ This is a standard Tyler interface.
o Message Switch
■ Integration to run returns, parse return data, and populate parking
citations, warnings and abandoned vehicle notices.
■ Registered Owner information will be stored to the record for export to the
Court and for auto populating Abandoned Vehicle Letters.
■ Returns are to be run (based on License Plate Number and State) as soon as
plate is identified, whether it be fed from AutoVu, hand entered or OCR
from a handheld device scan/picture (when feature becomes available).
Reports
The following reports are required (whether using standard reporting or through customization).
• Abandoned Vehicle Letters
o The ECS system will automatically populate the address label section of the letter
based on Registered Owner information.
• Abandoned Vehicle Status Report
•
zz
••::.. t ler
•• technologies
o The ECS will provide an Abandoned Vehicle Report and a map view of all
unresolved abandoned vehicles which will include a differentiator (such as color)
between those less than 72 hours old and greater than 72 hours old.
•
23
.t yler
•• technologies
Attachment E — Project Deliverables and Project Schedule
Project Deliverables
Existing Citation Process
The existing process flow will be identified and documented in partnership with the Client and
Tyler as a separate appendix during the design phase of the project.
Proposed System
The proposed process flow will be identified and documented in partnership with the Client and
Tyler as a separate appendix during the design phase of the project
Interface Development Specifications
Tyler will work with Client to develop an interface specifications document for each interface.
Each document must be signed off by Client before development begins.
Acceptance Testing Plan (ATP)
The ATP will provide the Client with the testing plan for verification of the installed system,
including interfaces, which will allow the Client to certify the ECS performs in according with the
requirements. The testing plan will include strategies and test cases to assist with the
verification. The Client will have the ability to certify the ATP prior to both the certification from
Tyler as well as the beginning of the acceptance test.
System Installation
TYLER BRAZOS ECS SERVER —Tyler will host the ECS server, database server and verify operation
of the system. Any hardware purchases required to meet system specifications are the
responsibility of City of Renton.
TYLER CLIENT SOFTWARE —The Tyler Brazos Client Software will be installed on the
MDT's/PDA's. The initial installation will be completed by City of Renton and/or Participating
Agencies. If the Client elects to have Tyler perform the installation, the hardware will be sent to
Tyler for off -site installation and verification at an additional cost.
TYLER INTERFACES — During the setup and configuration process, connectivity for any included
interfaces will also be verified. The Client will provide Tyler personnel with the proper access to
complete tasks required to complete this effort. Any installation requirements with regards to
security or setup must be provided to Tyler one -week prior to the scheduled interface testing.
HARDWARE IN VEHICLES — Tyler will not install any hardware in the vehicles.
•
•••®•• tyler24 • •_•
•• technologies
Training
OPERATIONAL PILOT/FULL ROLLOUT — Tyler will provide full Train -the -Trainer training to the
officers specified by the Client to participate in the pilot/full rollout (limit = 14 Officers). The
training will consist of two formal days of training.
Day 1 should occur in a classroom setting where the officers will be thoroughly exposed to
training that covers the hardware, operating systems, application, troubleshooting, and
proper care/maintenance.
• Day 2 is focused on field training and includes Tyler personnel at the side of the Client
officers, as the officers complete citations in "real world" environments.
This training may incorporate such tactics as DL checks, standard traffic stops, etc. to ensure that
all the officers involved are exposed to several different types of scenarios and receive the
maximum effective training. Upon completion of the field training portion, Tyler will train the
officers on how to review their citations via the web -based tool and any workflow processes
specified by the Client. Tyler will also train any specified supervisors in procedures for reviewing
citations and voids, as well as statistical reports.
SYSTEM ADMINISTRATOR — Instructor -led, hands-on training will be provided for up to three (3)
Client staff members who will ultimate be actively involved in administering the ECS.
Milestones
1) Contract Award
2) Contract Signature
3) Kick -Off Project
4) Sign -off of Work Plan by City (Payment 1)
5) Interface Development Specifications (Payments 2 & 3)
6) Order hardware
7) Setup Configuration of ECS (off -site)
8) Create ATP Plan
9) On -Site testing
10) Training of 'Users' (Payment 4)
11) Acceptance Testing by City
12) Final Acceptance (Payment 5 — Includes integration acceptance) (Final Payment) and full
Rollout of Project
Schedule
This schedule is a sample draft only. It does not represent all tasks/activities relevant for this
project and is intended to serve as an illustration only. It does not represent a commitment by
Tyler or the Client and will be modified post Kick -Off Meeting.
T— Tyler, C — City of Renton, J —Joint (both are responsible)
25
•�� ��� tyler
�� technologies
Task
Total
Deliverable
Phase
Task
Activity
Description
Duration
Duration
Owner
Deliverables
Acceptance
(Weeks)
Payment
1
First Phase
_
1
Contract Award
TBD
J
2
Contract Signature
TBD
C
3
Kick -Off Project
TBD
TBD
J
Official Work Plan
1
On -Site Meeting/Conference Call
J
2
Gather requirements from all project owners
J
3
Build official Work Plan
J
4
Verify Work Plan with hardware vendors
Work Plan to be
!
signed off by Client
C
$5,800 t
4
Sign -off of Work Plan by Client
3 Days
2.5w
2 000
$7,800!!
5
Interface Development Specifications
Court Interface (Washington AOC - VRV & Court
Specifications
$1,625
1
Payments)
Document to be
signed off by Client
Specifications
$1,625
2
ALPR—AutoVu by Genetec
Document to be
signed off by Client
ADFS (Active Directory Federated Services)
Specifications
3
integration
Document to be
signed off by Client
6
Order hardware
TBD
T
7
Setup Configuration of ECS (off -site)
3 weeks
5.5w
1
Setup and Configure mobile software
T
2
Receive all incoming interface samples to load
C
into mobile device from Client
3
Setup and Configure all interfaces
T
Interface
Documentation
4
Layout the citation printouts
T
Sample Layouts forApproval
6
Install mobile software onto Client hardware (off-
T
site)
7
Test solution using VC hardware
T
8
Create sample interface files for Client system(s)
J
9
Test sample interface files
J
10
Approve sample interface files
C
8
Create ATP Plan
1w
1
Build ATP Plan
T
••::®
26 • tyler
•• technologies
2
Approve ATP Plan
C
i�
I
9
On -Site testing
TBD
6.5w
1
Test MDTs and connectivity to server
T
2
Test all interfaces for server
T
3
Test web -citation entry screen
T
j4
Test web -based reporting
T
5
Certify ECS based upon ATP
T
10
Training of Users
3d
7w
$2,000
i
1
Train officers on Classroom Train -the -Trainer and
Field Training
J
2
System Administrator Training
J
3
Court Training
a
11
Acceptance Testing by Client
32d
TBD
1
Evaluate Hardware
2
Compile and Evaluate hardware observations
3
Finalize hardware selection
4
Initial Acceptance Test for "go live"
5
Initiation of Final Acceptance Period
30d
12
Final Acceptance and Full Rollout
1d
T
Client signs off on
project
$10, 000 +
$1,625 +
$1,625 =
$13, 250
Task are TBD
13
End of Phase I
Debrief of all project
principals
Grand Total
$26,300
•
•�°27 •0 tyler
•• technologies
t y
ler
® technologies
Exhibit E
RFP and Tyler's Response
[REMAINDER OF PAGE INTENTIONALLY LEFT BLANK]
•••°•• tyler
„r kgR 5
31
City of Renton, Washington
Request for Proposal
Parking Citation System
Issue Date: May 10, 2019
Due Date: May 31, 2019
www.RentonWA.gov
Page 1
REQUEST FOR PROPOSAL
Notice is hereby given that the City of Renton requests proposals for:
Parking Citation System
Vendors who wish to submit proposals are encouraged to inform the City of their intent to submit a
proposal by emailing intent to ParkingCiteSystem@rentonwa.gov.
You may submit your proposal by email to:
Pa rki neCiteSyste m @ rentonwa.gov
Proposals received later than 4:00 PM on May 31, 2019 Pacific Time will not be considered.
Please submit any questions regarding this RFP to ParkingCiteSystem@rentonwa.gov by May 17, 2019.
Responses to questions will be posted on the City of Renton website at http://www.rentonwa.gov/bids by
May 24, 2019. It is the responsibility of any proposer to review the City's website for any RFP revisions or
answers to questions prior to submitting a proposal.
This is a competitive negotiation process in accordance with RCW 39.04.270. The City of Renton will
consider all the evaluation information obtained during the competitive negotiation process. The City of
Renton reserves the right to reject any and all proposals in part or in full for any reason. The City also
reserves the right to change, cancel, or re -issue this RFP at any time. This RFP does not obligate the City of
Renton to pay any costs incurred by the respondents in the preparation and submission of a proposal, nor
does it obligate the City to accept or contract for any expressed or implied services.
The successful vendor must comply with local, state, and federal requirements regarding equal opportunity
and employment practices and the City of Renton Professional Services Agreement. The City is committed to
a program of equal employment opportunity regardless of race, color, creed, sex, age, nationality or
disability. Women and minority business enterprises are encouraged to submit proposals.
Published: May 10, 2019
Page 2
Table of Contents
Page Number
1. INTRODUCTION............................................................................................................................................... 4
1.1.
Purpose of this RFP............................................................................................................................. 4
1.2.
About the City of Renton, WA............................................................................................................. 4
1.3.
Primary use case of the Parking Citation System................................................................................ 4
1.4.
Technology environment at the City................................................................................................... 5
2. RFP INFORMATION.......................................................................................................................................... 6
2.1.
Procurement schedule........................................................................................................................6
2.2.
RFP Contact information..................................................................................................................... 6
2.3.
Letter of intent.................................................................................................................................... 6
2.4.
Questions regarding this RFP.............................................................................................................. 6
3. SCOPE,
GOALS AND OBJECTIVES..................................................................................................................... 6
3.1.
Scope of this project............................................................................................................................ 6
3.2.
Goals and objectives of this project.................................................................................................... 7
4. RFP SUBMISSION
.............................................................................................................................................7
4.1.
Proposal identification........................................................................................................................ 7
4.2.
Proposal submission and format......................................................................................................... 7
4.3.
Proposer responsibility....................................................................................................................... 7
4.4.
Proposal completeness....................................................................................................................... 8
4.5.
Public record and proprietary material............................................................................................... 8
4.6.
Proposal validity duration................................................................................................................... 8
4.7.
Errors in proposals........................................................................................................ ....... 8
...............
4.8.
Withdrawal of proposals..................................................................................................................... 8
4.9.
Rights to Submitted Material.............................................................................................................. 8
5. RFP EVALUATION,
SELECTION, AWARD PROCESS........................................................................................... 8
5.1.
Proposal evaluation............................................................................................................................. 8
5.2.
Clarifications........................................................................................................................................9
6. CONTRACT AWARD AND EXECUTION............................................................................................................. 9
6.1.
Selected proposals.............................................................................................................................. 9
6.2.
Awarding proposal.............................................................................................................................. 9
6.3.
Conditions........................................................................................................................................... 9
6.4.
Contract...............................................................................................................................................9
6.5.
Warranties, License Agreement and Maintenance Agreement.......................................................... 9
6.6.
Non-endorsement.............................................................................................................................10
6.7.
No cost before receipt.......................................................................................................................
10
7. RFP RESPONSES
(VENDOR INSTRUCTIONS)............................................................... ................ I...................
10
7.1.
Proposal content...............................................................................................................................
10
7.2.
RFP Submittal Document - Spreadsheet...........................................................................................
10
7.3.
RFP Submittal Document — License Agreement................................................................................
12
7.4.
RFP Submittal Document — Maintenance Agreement......................................................................
13
7.5.
RFP Submittal Document —Warranty Agreement............................................................................
13
7.6.
RFP Submittal Document —Sample Contract Markup......................................................................
13
Page 3
1. INTRODUCTION
1.1.Purpose of this RFP
The City of Renton, WA (the "City") is seeking proposals for a Parking Citation System.
Through this Request for Proposals (RFP), the City seeks to select a company or firm to provide
mobile ticketing software, hardware, documentation, implementation, and training services. This
document details the system software, hardware, service, and company information on which the
City will base its selection. Feature requirements outlined in the requirements spreadsheet must be
met or exceeded. Installation services and training will be required.
1.2.About the City of Renton, WA
The City of Renton serves about 104,100 residents in the Puget Sound region and ranks as the eighth
largest city in Washington State'.
The vision of the City of Renton is to be the center of opportunity in the Puget Sound Region where
families and businesses thrive. The mission of the City of Renton, in partnership and communication
with residents, businesses, and schools, is dedicated to:
• Providing a safe, healthy, welcoming atmosphere where people choose to live
• Promoting economic vitality and strategically positioning Renton for the future
• Supporting planned growth and influencing decisions that impact the city
• Building an inclusive informed city with opportunities for all
• Meeting service demands through high quality customer service, innovation, a positive
work environment, and a commitment to excellence
The City operates under the laws of the State of Washington as an "optional municipal code city".
Renton is governed with a mayor -council form of government with eight (8) elected officials.
City operations are performed by more than 700 employees at the direction of the Mayor. The City
provides a host of services to residents and local businesses: Police, Utilities (water, wastewater,
and storm water), Transportation (Street construction and maintenance), Parks and Recreation,
Economic Development, Land Use Planning and Regulation, Municipal Courts, and General
Government services (Animal control, and museum system).
1.3.Primary use case of the Parking Citation System
The City will use the Parking Citation System to enforce the Renton Municipal Code and Revised
Code of Washington (RCW) as they relate to vehicle parking. Through integration and automation, it
will also provide citation information to the Courts (both AOC and Renton Municipal Court). This
system will primarily be used by two Parking Enforcement Officers in two Parking Enforcement
vehicles.
"April 1 Official Population Estimates." Office of Financial Management, State of Washington Office of Financial Management, 1 Apr.
2018, www.ofm.wa.gov/washington-data-research/population-demographics/population-estimates/apri1-1-official-population-estimates.
Page 4
1.4.Technology environment at the City
• Desktops and Laptops —The computing environment at City includes approximately 700
workstations throughout the City. Computers are configured with Microsoft Windows 7 or
Microsoft Windows 10 64-bit operating system. All hardware is less than 5 years old, and
includes a minimum of an Intel i5 processor and at least 4 GB of RAM. Each computer is
managed by a Microsoft Active Directory domain. The standard desktop software suites in most
of the City are Microsoft Office 2013 and 2016. Some staff also use city issued mobile devices
such as smartphones and tablets.
• Servers —The City's server environment is comprised of both physical and virtual servers running
the latest versions of Microsoft Windows operating system. New system implementations
requiring server resources shall run in a vitalized environment.
• Database Management System (DBMS) —The City utilizes and supports the latest versions of
Microsoft SQL Server in a high availability environment.
• Email System —The City's standard email platform is Microsoft Exchange Server 2010.
• Network Infrastructure — the City has a fiber gigabit Metropolitan Area Network to
approximately 43 city facilities and parks. The city also leverages a wide -area WiFi and LTE
network connectivity for mobile users. All Windows OS mobile devices connect to the
Enterprise network through Net Motion VPN access.
• Software Updates — If a system requires updates to be installed on local machines, it is the
expectation that the City's IT Division will coordinate and install the updates with assistance
from a vendor where appropriate.
• Internet Browser —The City currently supports Microsoft Internet Explorer, Google Chrome, and
Mozilla Firefox web browsers.
• Backup and Disaster Recovery —The City currently has an enterprise backup system to backup
servers, systems, applications, and user data based on the retention schedule of the type of data
being stored.
• Retention Requirements The City must meet applicable laws for State of Washington retention
schedules (RCW 40.14) for records. The City is legally obligated to retain records in a way that is
compliant with the State of Washington's document retention laws. The City must be able to
identify records, apply the appropriate retention policy, and properly dispose of records in
accordance with applicable laws when the retention period has been satisfied.
• Public Disclosure Requirements —The City must meet applicable public disclosure laws for email
content (RCW 42.56). The City is legally obligated to fulfill public disclosure requests in
accordance with applicable laws. The City must be able to properly identify records to fulfill a
given request, ensure immutability of the record, and have the ability to redact information that
is exempt from disclosure. The City must be able to export all records that is responsive to the
given request its native format (? or ?) and make it available on GovQA (https:Hgovga.com).
Systems need to improve the City employee experience and efficiency in fulfilling public records
requests. City staff receive a large volume of ever increasing public disclosure requests each
year. Solutions implemented must afford City staff a user-friendly way to quickly search for and
identify all records that are responsive to a public disclosure or eDiscovery request, and
efficiently manage each request from intake to fulfillment.
Page 5
2. RFP INFORMATION
2. 1. Procurement schedule
Milestone
Date (Pacific Time Zone)
RFP Published
May 10, 2019
Questions due via email
May 17, 2019 @4:00 PM
Responses to questions posted by
May 24, 2019 @4:00 PM
Proposals due no later than
May 31, 2019 @4:00 PM
Conduct Vendor Interviews/Site visits (optional)
June 2019 *
Select Vendor
June 2019 *
Contract Finalization
July 2019 *
Kick Off Project
July 2019 *
* Estimated dates
Table 1 —Procurement Schedule
2.2.1117P Contact information
During the RFP process, a designated contact person will be responsible for official coordination and
communication with Responder concerning questions, project status, and announcements. During
the RFP process, the City of Renton requires vendors to not contact other City of Renton staff
regarding the RFP processes; failure to comply with this requirement may disqualify those proposals
from further consideration. The following email address is the City's only official point of contact for
this RFP: ParkingUteSystem@rentonwa.aov
2.3.Letter of intent
Vendors who wish to submit proposals are encouraged to inform the City of their intent to submit a
proposal by emailing intent to Parking0teSystem@rentonwo.aov
2.4.Questions regarding this RFP
Interested parties must direct all questions regarding this RFP to ParkinaCiteSystem@rentonwa.aov
by the date and time specified in section 2.1.
It is the responsibility of the proposer to review the City's website for any RFP revisions or answers
to questions prior to submitting a proposal. Responses to questions will be posted on City's website
at.http://rentonwa.gov/bids by the date and time specified in section 2.1.
3. SCOPE, GOALS AND OBJECTIVES
3.1.Scope of this project
3.1.1. Implement a solution for issuing parking citations and abandoned vehicle notices.
Page 6
3.1.2. Project includes the system, specified integrations, and implementation services including
project planning, installation, configuration and training.
3.1.3. Enable users to efficiently manage records and produce reports and statistics.
3.1.4. Solution is to be successfully integrated with the City's existing License Plate Reader (LPR)
system, AutoVu by Genetec. This integration will forward information generated by AutoVu to
the Parking Citation System, minimizing the need for staff to hand -enter information stored in
AutoVu.
3.1.5. Solution is to successfully export and transmit citation data and images in the Washington
State specified format for consumption by the Washington Courts Data Exchange Vehicle
Related Violations (VRV) system.
3.1.6. Scope does not include data migration from current citation system.
3.2.Goals and objectives of this project
3.2.1. Configure citation and abandoned vehicle notices using City of Renton branding and
complying with both City's and Washington State's Office of the Court requirements.
3.2.2. Reduce citation issuing time and decrease opportunities for human error through integration,
minimizing the number of fields Parking Enforcement Officers need to populate manually.
3.2.3. Provide quality photo evidence to the Courts for issued citations taken by users or received
through the LPR integration.
3.2.4. Timely and reliable transmission of Citation information to the Court, which can also be
tracked through reporting, audit trail or other easily accessible means.
4. RFP SUBMISSION
4.1.Proposal identification
Proposals must be made in the official name of the firm or individual under which business is
conducted (showing official business address) and must be signed by a person duly authorized to
legally bind the person, partnership, company, or corporation submitting the proposal. A
corporation must indicate place and date of incorporation.
4.2.Proposal submission and format
Your proposal must be submitted via email on or before the due date detailed in section 2.1 to
ParkingCiteSVstem@rentonwa.sov. Section 7 of this RFP defines the file format of each submittal
attachment.
4.3.Proposer responsibility
Proposers are solely responsible for the timeliness of their submittals. As such, budget adequate
time to ensure proposals are delivered before the deadline.
Page 7
4.4.Proposal completeness
By submitting a proposal, proposers certify that such proposal constitutes their full and complete
response to the RFP and evidences their acknowledgement that additional written material outside
of such proposal shall not be considered by the City in connection with this RFP, unless the City
provides a written request for additional information.
4.5.Public record and proprietary material
Proposals may be released in total as public information in accordance with the requirements of the
laws covering same. Any proprietary information must be clearly marked. Marking the entire
proposal as proprietary will neither be accepted nor honored. If a request is made to view a
Responder's proposal, City of Renton will comply according to the Public Records Act, Chapter 42.56
Revised Code of Washington (RCW).
4.6.Proposal validity duration
Proposal and cost schedule shall be valid and binding for at least 90 days following proposal due
date and will become part of the contract that is negotiated with the City.
4.7.Errors in proposals
The Successful Responder is responsible for all errors or omissions in its proposal and any such
errors or omissions will not serve to diminish their obligations to the City. The City reserves the
right to make corrections or amendments due to errors identified in the proposal by either the
Successful Responder or the City. The City may waive minor irregularities contained within the
proposal documents.
4.8.Withdrawal of proposals
Responders may withdraw a submitted proposal, at any time up to the proposal closing date and
time. To accomplish this, a request by an authorized representative of the Responder must be
submitted to the City contact person. After withdrawing a previously submitted proposal, the
Responder may submit another proposal at any time up to the proposal closing date and time.
4.9.Rights to Submitted Material
All Proposals and related correspondence submitted shall become the property of City of Renton
when received.
S. RFP EVALUATION, SELECTION, AWARD PROCESS
5.1.Proposal evaluation
All proposals meeting the requirements of this RFP shall be reviewed and rated by an evaluation
committee according to the following criteria:
• Ability of the product to perform the technical and functional requirements
• Project management and implementation plan
• Cost, rates, and fees
Page 8
• Proposal responsiveness
0 Firm/Consultant qualifications, experiences, references and experience
5.2.Clarifications
The City reserves the right to obtain clarification of any point in a Responder's proposal or to obtain
additional information necessary to properly evaluate a proposal. Failure of a Responder to respond
to such a request for additional information or clarification may result in rejection of the Responder
proposal. The City's retention of this right shall in no way reduce the responsibility of Responder to
submit complete, accurate, and clear proposals.
6. CONTRACT AWARD AND EXECUTION
6.1.Selected proposals
Selected proposers may be contacted to arrange in -person interviews and/or product
demonstrations with the evaluation committee.
6.2.Awarding proposal
The City reserves the right to make an award without further discussion of the proposal submitted.
Therefore, the proposal should be initially submitted on the most favorable terms the vendors can
offer. It is understood that all proposals will become a part of the official file without obligation to
the City.
6.3.Conditions
The general conditions and specifications of the RFP as proposed by the City and the successful
vendor's response, and amended by agreements between the City and the vendor, will become part
of the contract documents. Additionally, the City will verify vendor representations that appear in
the proposal. Failure of the vendor's products to meet the mandatory specifications may result in
elimination of the vendor from competition or in contract cancellation or termination.
6.4.Contract
The vendor selected as the apparently successful vendor is expected to enter into a contract with
the City as described in the sample provided in Exhibit A.
6.5.Warranties, License Agreement and Maintenance Agreement
The Warranties, Software License Agreement and Maintenance Agreement will be negotiated and
signed at the same time as the contract. Successful Responder shall submit policies regarding and
copies of all Warranties, License and Maintenance Agreements on the proposed solution with
associated costs.
Page 9
6.6.Non-endorsement
In selecting a Responder to supply products and/or services, the City is neither endorsing nor
suggesting that the Successful Responder's product is the best or only solution. The Successful
Responder agrees not to refer to the City in any literature, promotional material, brochures, sales
presentation, or the like without the City's express written consent.
6.7.No cost before receipt
No cost chargeable to the proposed contract may be incurred before receipt of a fully executed
contract.
7. RFP RESPONSES (VENDOR INSTRUCTIONS)
7.1.Proposal content
In order to thoroughly analyze the responses to the RFP, vendors are required to prepare their
proposals in accordance with the instructions outlined in this section. Vendors whose proposals
deviate from these instructions may be considered non -responsive and maybe disqualified at the
discretion of the City. All RFP Submittal Documents detailed below must be submitted at the time of
Respondent submitting in one email.
Vendors must present their products, services and applicable features in a clear and concise manner
that demonstrates the vendors' capabilities to satisfy the requirements of this RFP. Emphasis should
be concentrated on accuracy, clarity, comprehensiveness and ease of identifying pertinent
information and suitability of the product and services.
7.2.1117P Submittal Document - Spreadsheet
RFP Response
TemplaiteAsx
Respondents must download, fill out and submit the above excel spreadsheet. Before submitting,
rename the file in the following format:
ParkingCiteSystem_2019_[CompanyName]_Spreadsheet.xlsx where [CompanyName] is the name of
yourcompany. Example: ParkingCiteSystem_2019_City0fRenton_Spreads heet.xlsx
Following is a description of the different tabs found in the spreadsheet:
Information and Questions: Answer questions in this tab with information about your company and
proposed solution.
Executive Summary: Provide a high-level overview of your proposed solution.
Qualifications and Experience: Describe Respondent's experience implementing your proposed
solution in a local government setting. Please include the qualifications and experience for any
proposed sub -contractors in the narrative.
Alternative: If Respondent's qualifications and experience narrative does not format well
within the provided excel spreadsheet, respondent may choose to submit a separate .pdf,
Page 10
.doc or .docx document. The name of the document should be in the following format
ParkingCiteSystem_2019_[CompanyName]_Qualifications.[pdf]. In the spreadsheet
narrative section, enter'See [DocumentName] document'.
Approach and Methodology: Create a narrative which shows Respondent's understanding of the
project's requirements and documents a logical approach to the project scope of work. Include a
general work plan, as well as the proposed approach to undertaking the scope of work.
Alternative: If Respondent's approach and methodology narrative does not format well
within the provided excel spreadsheet, Respondent may choose to submit a separate .pdf,
.doc or .docx document. The name of the document should be in the following format
ParkingCiteSystem_2019_[CompanyName]_Approach.[pdf]. In the spreadsheet narrative
section, enter'See [DocumentName] document'.
Project Management Philosophy and Schedule: Create a narrative which describes how
Respondent intends to manage all aspects of the work to be performed, including schedules for
completion of tasks/subtasks, procedures for scheduling, and cost control. The Project management
proposal must include project kick off meeting, regularly scheduled project team meetings, written
progress reports, issue and risk management techniques.
Alternative: If Respondent's project management philosophy and schedule narrative does
not format well within the provided excel spreadsheet, respondent may choose to submit a
separate .pdf, .doc or .docx document. The name of the document should be in the
followingformat ParkingCiteSystem_2019_[CompanyName]_ProjectManagement.[pdf]. In
the spreadsheet narrative section, enter'See [DocumentName] document'.
Functional Requirements: Fill out the Functional Requirements form with information about your
proposed product. Following is a definition and instructions on how to complete the form:
Ref #: This field is a unique identifier of each requirement as assigned by the City.
Requirement: This is a description of the functional requirement.
Type: This field designates the type of requirement with the following definition:
R - Required (Proposed system must have this requirement)
O - Optional (Proposed system should have this feature, but it is not require)
Code: Use the following codes to define how well your solution currently meets the
requirement:
3 - System can completely meet this requirement with no custom code and no
additional expense.
2 — System can meet requirement with minor code modifications with no impact on
future releases. These modifications will be available and implemented with no
impact to the project schedule and does not have an additional cost associated with
the feature.
Page 11
1— System will not meet requirement and will require modification(s). Testing and
production of modifications will be in place prior to implementation date, however,
the customer will assume a cost above the basic system cost for future updates. If
additional costs are needed for this feature, please enter them in the 'Comment'
column next to the feature and itemize them on the 'Costs' tab of the worksheet.
0 — System will not meet requirement and modification in time for implementation
is not possible.
N/A —The requirement does not apply to the proposal. If this value is used, provide
a comment as to why Respondent chose this value.
Comments: Provide any relevant information about this requirement. Please note any uses
of third party software, ad -hoc query tools, and creative use of existing features or custom
modifications. Although costs are required on a different worksheet, please provide a
realistic dollar estimate if there is additional cost associated with a feature.
Cost: Since the City expects to complete a "not to exceed/fixed price" contract, the budget for the
proposal must not exceed the specified amount, and must be broken down into hours, hourly rates
and expenses for each task and subtask. All prices are to be in U.S. dollars. All applicable taxes to be
paid by the City must be separately shown.
Vendors must itemize the unit and extended price for each product and service proposed as part of
the proposed solution. Cost information must include all expected implementation and operating
costs, both one-time and ongoing. Specific model numbers and capacities should be included.
Information about licensing must be provided. Vendors should describe and quote optional
components (including query tools, report writers, etc.) as individual and separate items. Any
upgrade to the base system needed for optional components must be included in the cost of those
components.
In addition to the breakdown of costs described above, provide an hourly rate for professional
services that may be required to complete our project, but was not originally scoped. The quoted
rate(s) is expected to be applied for the duration of the project (as described herein). They should
include, but are not limited to: training, project management, programmer/analyst, and technical
support analyst.
The bottom of the costs worksheet provides a location where vendor can propose a payment
schedule narrative. With each deliverable and amount, explain why those particulars were chosen.
Indicate all costs associated with each product and/or service included in the proposal. Also include
aggregate pricing if price advantages are available.
Client References: Populate the list with a minimum of three (3) client references who currently use
the proposed solution. References are preferred to be local government agencies physically located
within a 50-mile radius to the City of Renton. The City reserves the right to contact references
without prior notification.
7.3.1117P Submittal Document - License Agreement
Submit the Respondent's proposed license agreement for the solution. Respondent may choose to
submit the file in one of the following formats:.pdf, .doc or .docx. Before submitting, rename the
file in the following format: ParkingCiteSystem_2019—[CompanyName]_LicenseAgreement.pdf
where [CompanyName] is the name of your company. Example:
ParkingCiteSystem_2019_CityOfRenton_LicenseAgreement.pdf.
Page 12
7.4.RFP Submittal Document - Maintenance Agreement
Submit the Respondent's proposed maintenance agreement for the solution. Respondent may
choose to submit the file in one of the following formats:.pdf, .doc or .docx. Before submitting,
rename the file in the following format:
ParkingCiteSystem_2019_[CompanyName]_MaintenanceAgreement.pdf where [CompanyName] is
the name of your company. Example:
ParkingCiteSystem_2019_CityOfRenton_MaintenanceAgreement.pdf.
7.5.1117P Submittal Document — Warranty Agreement
Submit the Respondent's proposed warranty agreement for the solution. Respondent may choose
to submit the file in one of the following formats:.pdf, .doc or .docx. Before submitting, rename the
file in the following format: ParkingCiteSystem_2019—[CompanyName]_WarrantyAgreement.pdf
where [CompanyName] is the name of your company. Example:
ParkingCiteSystem_2019_CityOfRenton_WarrantyAgreement.pdf.
7.6.1117P Submittal Document - Sample Contract Markup
Draft PSA with
Network Cyber Secu
Successful respondent is expected to enter into a contract with the City. Download the above
sample contract and mark up and comment on language changes Respondent would like to
negotiate. Before submitting, rename the file in the following format:
ParkingCiteSystem_2019_[CompanyName]_ContractMarkup.pdf where [CompanyName] is the
name of your company. Example: ParkingCiteSystem_2019_CityOfRenton_ContractMarkup.pdf.
Page 13
Information and Questions
Company Information
Company Name:
Tyler Technologies
Company Address:
5101 Tennyson Dr
City, State, Zip:
Plano, TX 75024
Website Address:
www.tylertech.com
Year Founded:
1966
Location and Date of Incorporation:
Delaware 1966
RFP Contact
Name:
Seth Dinehart
Title:
Account Executive
Phone Number:
707.761.6587
Email Address:
seth.dinehart@t lertech.com
Company Full -Time Employees
Total Number of Employees in the Company:
4600
Number of Employees on Proposed Product
Implementation Team:
15
Number of Employees on Proposed Product
Support Team:
6
Number of Employees on Proposed Product
Research and Development Team:
6
Product Customer Base
Total Customers using solution:
820
Total Local Government Customers in
Washington State using solution:
3
Do you have a local user group in Washington
State?
No
On-Prem System
Do all server components support virtual
server installation?
Tyler proposes our hosted server environment, which does not require VMWare. If the agency prefers a local server
installation for eCitation, Brazos supports VMWare.
Does the server software support Windows
Server 2016 or newer?
Yes
Does the system's database support Microsoft
SQL Server 2014 or newer in a clustered
environment?
Yes
If system has a website or web service, does it
support [IS 8.0 or newer?
Yes
If system has workstation clients, can
workstation clients be installed and upgraded
by Microsoft System Center?
N/A
Hosted System
Who is the hosting provider?
Amazon Web Services - GovCloud
Where is the hosting located?
Amazon Web Services - GovCloud - located in the US
What type of infrastructure is used?
Amazon Web Services- GovCloud
Where is the primary data being stored?
Amazon Web Services - GovCloud
Does the City own the data if the contract is
terminated?
Yes
How and where is the backup data being
stored?
We take system snapshots of all file data once every 4 hours and snapshots of the database once per hour. Each
snapshot Is a full backup of everything needed to restore all data that is being backed up. These backups are stored
Is the system on a dedicated or shared
environment?
Shared
If a shared environment, how is the data
segregated from other shared environments?
Since we utilize the hosted model for a significant number of customers, we have implemented industry best -
practices for server hardening and the security measures required for security. These include intrusion detection,
antivirus, turning off all unneeded ports, complete form and user authentication, etc.
If a shared environment, how is security
managed and what controls are in place?
Since we utilize the hosted model for a significant number of customers, we have implemented industry best -
practices for server hardening and the security measures required for security. These include intrusion detection,
antivirus, turning off all unneeded ports, complete form and user authentication, etc.
Who has access to the infrastructure,
hardware, software and data?
The infrastructure and hardware are maintained by AWS.
Brazos requires a valid login to both the website and the Brazos software. The users are each assigned a role(s) that
defines what they have access to, what they can add/change/delete/view, etc., and the user profiles are completely
controlled by the customer. The users can also be assigned to a "group" with certain profiles and security access
defined.
Does the customer have any control in
The customer is notified before any changes or upgrades are applied.
applying patches, upgrades and changes to the
solution?
What application and data access audit logs
Brazos includes a workflow/review/approval process which will be configured to exactly meet the needs and
are available and how often are they used to
requirements of the customer as described earlier. The customer controls who can make changes to the system,
audit security?
citation records, etc. Timestamps and signatures on approvals, voids, etc. are required as dictated by the customer.
Brazos records all entries, edits, deletions as well as user logins, and failed login attempts. We also provide standard
audit reports so that the customer can see at any time where every ticket number in their jurisdiction resides. If
customer would like to capture additional information such as record creation, submission for review, approval,
rejection/change request, deletion, etc., and provide a notes field in an audit report, this is configured in BuildlT as
well. We have implemented this audit functionality with many of our existing customers.
System Security
Does the proposed solution use data
Yes - AES-256 encryption algorithm
encryption at rest? Name Algorithm(s)
Does the proposed solution use data
All data transferred to and from the devices are performed over a TLS 1.2 connection via webservices. We can also
encryption in transit? Name algorithm(s)
utilize installed certificates on client machines, but most customers do not elect this route due to potential
maintenance issues. This includes downloads, uploads, software distribution and error reporting. All
communications are compressed and then encrypted via AES.
Does the proposed solution use Microsoft
Tyler requires a valid login to both the website and the Brazos software. The users are each assigned a role(s) that
Active Directory or Active Directory Federation
defines what they have access to, what they can add/change/delete/view, etc., and the user profiles are completely
Services (ADFS) for all user and security
controlled by the customer. The users can also be assigned to a "group" with certain profiles and security access
authentication? If no, please describe login
defined.
security environment.
We also allow for LDAP integration for the website, which allows the agency to manage roles within the existing
Microsoft Active Directory implementation.
Support and Maintenance
What type of support is provided (Self-service,
Our Toll -Free Support Center Hotline is available 24x7x365. Using our web -based technology we offer the most
email, phone)?
comprehensive maintenance program in the Industry. As long as the customer stays current with the annual
maintenance contract, all of the following will be provided FOR NO ADDITIONAL CHARGE.
The maintenance agreement will automatically renew for the number of licenses, servers, and interfaces in place at
the time of renewal unless cancelled by the customer.
What are the hours of support?
24x7x365
What are the support response and expected
During the term of the Maintenance Agreement, Tyler will provide support for those experiencing an error, defect,
resolution times for Critical, Urgent, High and
malfunction, or nonconformity in the Covered Software.
Low priority issues?
Upon receipt by Tyler of notice from Licensee through the Support Center Hotline of an error, defect, malfunction, or
nonconformity in the Covered Software, Tyler shall respond as provided below:
Severity 1. Produces an emergency situation in which the Covered Software is inoperable, produces incorrect
results, or fails catastrophically.
Tyler will provide a response by a qualified member of its staffto begin to diagnose and to correct a Severity 1
problem as soon as reasonably possible, but in any event a response via telephone will be provided within one (1)
hour. Tyler will continue to provide best efforts to resolve Severity 1 problems in less than forty-eight (48) hours. The
resolution will be delivered to Licensee as a work -around or as an emergency software fix. If Tyler delivers an
acceptable work -around, the severity classification will drop to a
Severity 2.
Severity 2. Produces a detrimental situation in which performance (throughput or response) of the Covered
Software degrades substantially under reasonable loads, such that there is a severe impact on use; the Covered
Software is usable but materially incomplete; one or more mainline functions or commands is inoperable; or the use
is otherwise significantly impacted.
Tyler will provide a response by a qualified member of its staffto begin to diagnose and to correct a Severity 2
problem as soon as reasonable possible, but in any event a response via telephone will be provided within four (4)
hours. Tyler will exercise best efforts to resolve Severity 2 problems within five (5) days. The resolution will be
delivered to Licensee in the same format as Severity 1 problems. If Tyler delivers an acceptable work -around for a
Severity 2 problem, the severity classification will drop to a Severity 3.
Severity 3. Produces an inconvenient situation in which the Covered Software is usable but does not provide a
function in the most convenient or expeditious manner, and the user suffers little or no significant impact.
Tyler will exercise best efforts to resolve Severity 3 problems in the next maintenance release.
Severity 4: Produces a noticeable situation in which the use is affected in some way which is reasonably correctable
by a documentation change or by a future, regular release from Tyler.
Tyler will provide, as agreed by the parties, a fix or fixes for Severity 4 problems in future maintenance releases.
Where is support personnel physically
College Station, TX
located?
Is there a dedicated support manager or
Yes
account representative?
How are upgrades, patches and other
Web
maintenance performed?
Which remote access tools are used by
As part of the Brazos Software Maintenance Agreement, Tyler uses a third -party secure unattended connectivity tool
support?
called Bomgar, as well as GotoAssist by Citrix, to remotely log into the device (hand held/tablet/laptop/M DC) for
maintenance and support. From deployment, implementation and on to support, Tyler has the ability to jump on a
session at a moment's notice to provide quality customer service speeding up processes; greatly reducing risk to the
implementation and accelerating our ability to respond to issues.
Service level Agreements (SLAB)
What SLAB are available (uptime, reliability,
Please refer to the attached SLA for uptime, reliability, and performance guarantees.
performance, etc.)?
What types of credits are available if SLAs are
Please refer to the attached SLA for details.
not met?
Product Roadmap and Upgrades
What is the product road map strategy?
Brazos does not provide a detailed roadmap of developments or changes. Part of our strategy for providing
outstanding support is keeping all of our customers on the current version of software. Any time we release major
or minor updates to the software, that software is updated to the server and automatically download to all devices
(with no IT intervention). We typically provide minor releases at least once per month with major releases once per
quarter.
How do customer requests get incorporated
As long as the customer stays current with the annual maintenance contract, we will make any change to any part of
into the product?
the solution (including updates requested by the Courts) at NO ADDITIONAL CHARGE! Our'No Change Order' policy
will ensure that the agencies will continue to have a relevant and superior solution for many, many years and will
save thousands of dollars in the future.
How are changes to the solution
Tyler's Lead Systems Engineer and the Brazos product staff will be responsible for installing updates and
communicated to customers?
communicating major updates or changes to both the Court or RMS systems.
Describe both minor system enhancements
Major notifications for updates that impact the citations written during the release will be called in to the customer's
and major system upgrades are provided in
Point of Contact so the officers may be notified that they can re -sync their handheld devices or laptops running
terms of frequency, cost, training, and impacts
Brazos. All minor software upgrades that will not affect the officer's day-to-day processes will be automatically
to staff during the upgrade process.
pulled down upon next sync.
Notifications for updates that impact the courts will be handled through the customer's Point of Contact. Any minor
upgrades to the court software that will not affect the court's day-to-day business will be automatically pulled down
upon the next import.
Implementation
Describe what level of support is provided
A successful implementation of Tyler products requires building a strong link between Tyler and the customer with
during system rollout.
designated personnel from both organizations making up a cohesive team. The team functions most effectively
when all members are committed to the project and contribute equally toward its success; open and consistent
communication between all team members is essential.
Tyler's staff has the experience and the expertise to organize the project and manage it properly for our customers.
From the initial implementation of the Tyler software to maintenance and support long after the implementation is
complete, Tyler will take responsibility for all aspects of the project. We assist with each crucial step to facilitate the
change to Tyler making it as effortless as possible. The Brazos project team consists of 6-8 members, excluding any
personnel that assist in a supporting but non -essential capacity.
Provide detailed explanation of how software
Hardware is delivered to the Tyler Brazos office where the software is installed and tested before deliveryto the
installation is handled.
customer. Any changes after the initial installation can be installed wirelessly.
Training
How many training hours are included with
A two-day Train -the -Trainer class is included in the proposal.
the proposed system?
How many training hours are typically
Generally two days is adequate. The trained officers then train the remaining users.
required for a comparable sized customer?
What resources are needed for training? i.e.
Classroom adequate for 15 attendees.
classroom size, technology, materials needed,
etc.
Retention and Public Disclosure
Is the system capable of meeting the
Yes
retention requirements listed in section 1.4
Technology environment at the City? List any
issues or concerns.
Is the system capable of meeting the Public
Yes
Disclosure requirements listed in section 1.4
Technology environment at the City? List any
issues or concerns.
Executive Summary
Tyler's Brazos solution is the most complete eCitation solution in the industry. Not only does Brazos provide a device -
independent electronic citation solution that can be used on handheld, laptop, tablet, and cellular devices, it is a
complete turnkey solution that covers the full gamut — from data capture to processing to transmittal straight into any
system you'd like. Our solution includes a robust back -end capability that is not found with other solutions. Some
examples of those capabilities are:
O Complete control over every drop -down in our applications from the website (i.e. locations, offenses, officers, etc.).
O Full administrative control over all users and devices to control which users can view or modify all data fields.
O Citation Detail Reports which look exactly like the violator copy and can optionally print with the photographs,
fingerprints, signatures, video and/or audio notes.
O Complete control over the citation numbers including complete audit reports to account for all citation numbers.
O Web -based Citation Entry Screen for entry of any paper tickets. This will allow all reports to be complete as well as
retaining all electronic interfaces for 'paper' tickets.
O Detailed statistical reporting for the officers such as count reports, location reports, selective traffic enforcement
reports, racial profiling reports and many others.
O Complete history of each device including number of tickets, who was logged in, last sync dates, and any errors or
activities performed on those devices.
O Detailed workflow for citations that can include approvals, rejections, and current status of each record with
regards to each export.
Each of these features is available for every application within the Brazos system, including eParking, Field Reporting and
eCrash. In fact, Brazos eCrash is currently in use in 12 states and is the state-wide eCitation and Accident Reporting
system for every law enforcement official in the State of Nevada.
Our success is based heavily on the fact that our system has been designed by the officers themselves. We employ a
highly collaborative approach to implementing our solution, and we hire off -duty police officers to conduct our training.
With our extensive experience, we understand the nuances of the law enforcement community. This experience
minimizes the risk to the agency by not having to "reinvent the wheel," thereby limiting the customizations to the user
interface and providing the officers with a usable system very quickly.
Benefits of Brazos
Increased Safety: Officer safety is of the utmost importance in the citation process. One key benefit to electronic citations
is the minimum number of trips between the subject's car and the officer's car.
Increased Productivity: By using the Brazos solution, officers will experience a dramatically decreased time to complete
the citation — from the beginning of the citation to the completion of printing the violator's receipt. One Brazos client has
completed the entire process in one minute and 21 seconds on an actual traffic stop. Although this represents the best -
case scenario, officers will certainly notice an improvement over handwritten citations.
Data synchronization also occurs easily and efficiently. With the Brazos solution, the client dictates and completely
controls the frequency of uploads. Officers can upload the citations/warnings/etc. to the e-citation server, download any
new lookup information and download/install any software upgrades in real-time — hourly, daily, etc. —all with the tap of
the screen. IT never needs to deploy anything to these devices.
Increased Efficiency: The Brazos solution improves the accuracy of citation data entry. With data validations, error checks,
autofill based on key data elements (as defined by the client) and automated workflow routing, citations can feed directly
into the court/RMS systems Our system is built on an enterprise framework called the Mobile Application Environment
Tool Kit (MaeKIT), which allows any Windows, Android, or iOS device to communicate directly with any industry -standard
database without the need for a dedicated intermediary server or workstation. The primary platform is entirely web -
based, the devices transfer data using industry -standard XML and all data are secured through multiple layers of access
control, encryption and compression. The Brazos solution was built entirely without programming using MaeKIT. Because
of MaeKIT, Brazos can almost identically match the look, feel and practice of each client's existing citation system.
Brazos Implementation Approach
We know that implementing anew system is not easy, so we have tailored our solution to assist our customers in as many
ways as possible from start to finish. Our proposal provides a full range of services designed to help you get the most out
of our products which includes:
O Needs Assessment & Kickoff — to ensure that the Brazos implementation team understands your needs thoroughly.
O Setup & Configuration — getting the details right.
O Verification — making sure all of those needs are met to your specifications.
O Pilot Testing — making improvements.
O Full Rollout — training your officers, fine tuning, and turn -over to Support.
Brazos Support
We pride ourselves on customer service and on our support after the sale. Our Support Center Hotline is available
24x7x365.
Using our web -based technology we offer the most comprehensive maintenance program in the industry. Not only do
our customers receive all upgrades and major/minor version of software, we will make any change to any part of the
solution at NO ADDITIONAL CHARGE! Our'No Change Order' policy will ensure that our customers will continue to have a
relevant and superior solution for many, many years and will save thousands of dollars in the future.
Commitment
At Tyler, we are uniquely qualified to meet the needs of the City of Renton through our experience, our software, and our
absolute commitment to customer satisfaction. That commitment, along with the consistent evolution of technology and
software features, has resulted in a retention rate of 99 percent and long-term relationships with our users. With more
than 15,000 customers, this partnership is an integral part of who we are and what we do. Our customers have a direct
impact on the evolution of the software and the processes involved in implementing and supporting it.
Qualifications and Experience
With decades of exclusive public sector experience, Tyler is the market leader that provides integrated software and
services; our singular focus, subject matter experts and in-depth products result in a sustainable client partnership that
delivers the industry's most comprehensive solution. We provide the industry's broadest line of software products and
offer clients a single source for all their information technology needs, in several major areas: Financial & Human
Resources, K-12 School Solutions, Public Safety, Courts & Justice, Property Appraisal & Tax, Permitting & Land
Management, Public Maintenance Management, Citizen Services, Land & Vital Records, and Document Management.
We are known for long-standing client relationships, functional and feature -rich products, and the latest technology. In
addition to software products, Tyler provides related professional services including installation, data conversion,
consulting, training, customization, support, disaster recovery, and application and data hosting.
Tyler always puts its clients first. We succeed because we take our client's success seriously, and we have a proven record
of delivering superior software solutions and services. The overwhelming majority of clients are up and running on time
and within budget. Whether it's developing, enhancing, and implementing our software, or providing excellent service
and client support —we succeed because our clients succeed. We want clients for life. Many of Tyler's first clients, across
every solution, are still clients today — some with relationships that span decades.
Public Sector Focus
Tyler's business units have provided software and services to customers for more than fifty years and have long-standing
reputations in the local government market for quality products and customer service. Tyler is the largest company in the
United States focused solely on providing software solutions to the public sector. While many of our competitors compete
in multiple vertical markets, Tyler is singularly focused on the public sector. It's 100 percent of our business.
Tyler recognizes that the public sector is generally stable, risk averse, and craves community accessibility, security, and
transparency. That is why local government and school entities seek reliable and efficient software and services from
Tyler —a vendor who is professional, reputable, dedicated, and achieves results. Tyler has the experience to understand
the unique requirements of the public sector, the necessary resources to invest in its products, and the ability to deliver
quality services.
Tyler's expansive offering of professional services is designed to complement its software offerings and produce the
optimum working environment for local government customers.
O Consulting
O Conversion
O Customization
O Training
O Live ongoing support
O Network management
Financial Stability
Tyler consistently maintains a solid balance sheet and strong cash flow and low debt, experiencing consistent revenue
growth with 28 consecutive quarters of profitability, and a total revenue for 2018 of $935 million. While experiencing
significant growth opportunities from an increase in staff and expanding territories, we anticipate additional product
offerings and new technology will accelerate this growth substantially in the future. We believe a debt -free balance
sheet, substantial cash reserves, and a committed customer base put Tyler in a great position in our industry to
weather any unexpected turbulence in the economy.
Brazos Background
Brazos was founded in 2000 by Mike McAleer specifically to focus on the emerging handheld technology field and today is
100% focused on this technology. Since being introduced to law enforcement by one of our partners, Motorola, who
considered our toolkit technology to be a perfect fit for electronic citation and other law enforcement functions, Brazos
has implemented our electronic citation solution in over 820 law enforcement agencies across 35 states, including multi-
department/multi-agency and state DPS implementations. Brazos is a time -tested, proven solution that led the market
fnr nvnr 1 C vn- - nrl —ill rnn+in.— +n rin rn in +hn fei+irrn %Aln rnnnrl mnrn nn Rr- —c rnr n—k - n4 4^,,^l^mm^n++h-.n
IUI UVCI 1J Yed[b dnu Will LUIIUfIUU LU UU JU III Ule IUIUIe. VVe Spt[IU If1Ufe Ufl DfdLUJ IeJedIL11 dnu UevelUpIllefll Uldll
other solution providers and continue to strive to find new and innovative ways to provide mobile solutions to assist the
law enforcement community.
In 2015, Brazos was acquired by Tyler Technologies. As part of Tyler, Brazos continues to offer industry -leading mobile
software solutions to law enforcement agencies and is committed to the Public Safety marketplace. We hire former law
enforcement (currently we have 10 people with law enforcement experience) for all of our operations positions. These
people provide both the relevance of solutions to our development team as well as to the officers we are training. We
take a long-term approach both to this solution and to our customers and look forward to the opportunity to partner with
Renton.
s
• ° tyler i0o°o City of Renton, WA
Parking Citation System RFP
METHODOLOGY AND APPROACH
Tyler's Brazos solution is the most complete eCitation solution in the industry. Not only does Brazos
provide a device -independent electronic citation solution that can be used on handheld, laptop, tablet,
and cellular devices, it is a complete turnkey solution that covers the full gamut —from data capture to
processing to transmittal straight into any system you'd like. Our solution includes a robust back -end
capability that is not found with other solutions.
For this project, Tyler is proposing our Brazos eParking with an additional Abandoned Vehicle form. The
solution will run on our hosted server, and interfaces include integration with the LPR System (AutoVu by
Genetec), the Washington State ACC Export/Integration, and the Renton Municipal Court Journal CMS.
We are proposing the Zebra TC75 handhelds with Brother RuggedJet mobile printers for creating and
issuing citations and abandoned vehicle notices in the field.
Brazos Solution Overview
The Brazos solution provides officers with the tools to create citations via handhelds, tablets, or laptops,
run State/NCIC returns wirelessly using the Brazos Message Switch or the agency's existing message
switch and update citation information in real-time or batch. The solution is so flexible that we set up the
environment however the client wants it —run on a local server or hosted by Tyler.
Also, because MaeKIT was built as a framework to rapidly extend database functionality to handheld
devices and laptops, it excels at interfacing with legacy systems, even in-house developed database
applications. MaeKIT also allows our clients to leverage their investments in handheld/portable devices
across many functions, with no limit to what can be extended to the existing devices. Citizen Relationship
Management (CRM), Code Enforcement, animal control, City/County/State services, work orders, vehicle
management, equipment checkout and asset management tracking are just a few of the additional tasks
that can be quickly designed and deployed to the existing force of handheld devices using the MaeKIT
platform.
Flexibility is the hallmark of the Brazos solution. As you look at the actual screens of a device configured
for electronic citation, it becomes difficult to differentiate one vendor's offering from another's. But the
Brazos solution is different from others in that it operates on the device without any function -specific
programming code. Almost every other vendor has written the solution as a program that runs on the
device with the specific purpose of performing that function, essentially limiting the device to that
function. The Brazos device runs a configuration interpreter that can interpret any configuration — it was
neither designed nor specifically programmed to do anything other than interpret the configuration
designed for it via our web -based configuration tool, BuildlT. This means that the same device running the
same Brazos software can be put to work to do just about anything — all developed using the web -based
BuildIT and simply picked up by the device whenever it synchronizes. That is a powerful paradigm offering
unlimited flexibility.
Screen Layout and Design
BuildlT offers a state-of-the-art drag and drop design interface for managing the configuration of devices.
This drag and drop interface is completely web -based and operates via any standard browser without
having to install or manage client software. The designer shows a life -like view of the target device and
allows you to drag and drop fields wherever you want them on the screen. You can resize, hide/show, and
move fields from tab to tab. Then the next time the units in the field synchronize, all changes will be
downloaded — it is that flexible and that easy.
5/31/19
•
. ®�® tyler City of Renton, WA
• Parking Citation System RFP
e.;
Screen captures from the BOOT design interface: Though they look like areal handheld device and laptop running the
Brazos software, they are actually design screens from BuildlT. The physical devices would look exactly the someway —
that is how true to reality the designer is; it is unparalleled in the industry.
Different devices can be configured to do different functions —they do not all have to have the same
capability loaded. Not only that, but MaeKIT allows our clients the flexibility to match the best device with
the best function as they move forward. As client come up with more and more functions to be
performed on the handheld devices and laptops, MaeKIT will be there to support each and every one.
Brazos supports any Windows, Android, and i0S operating systems. Therefore, what runs on a Motorola
also runs on a Panasonic, an iPad, and a laptop/MDC, for example. This allows additional flexibility in
current and future hardware choices. Clients are not locked into one configuration of hardware. As a
matter of fact, many different manufacturers and configurations can be running simultaneously.
MaeKIT Applied to eParking Enforcement
Brazos prides itself on being able to customize nearly every aspect of the project to meet the exact
process -flow desired by the customer. Using the unparalleled flexibility of MaeKIT, Brazos is 100 percent
tailored to the meet the needs of each client. Every aspect of the project (tasks, screens, print jobs,
business rules, fields, etc.) is laid out exactly to your requirements and workflow. Citations are written on
either laptops or handheld devices, uploaded to a central server and further processed for integration in
the RMS and court systems according to the client -defined workflow process. The information that
resides on the central eCitation server is provided for reporting and analytical purposes.
With the Brazos solution, a customer's various departments can have separate configurations, log -ins and
business rules (on our hosted system or a local installation) while retaining the electronic import
capabilities and data sharing that the client wants.
All of this flexibility facilitates growth and expansion as the client moves through future implementation
phases. With MaeKIT, we can extend nearly any application to the mobile environment and easily
disseminate it out to the devices, and individual departments can operate as connected to each another
or autonomously as the customer wishes.
Server Environment
Brazos allows customers to either install the entire application within their own environment or leverage
our hosted servers and eliminate any server hardware/software requirements. If a customer elects for a
local installation, all of the scaability/performance/ security that is built into our hosted model is
5/31/19
4
00 "° tyler
*i�o♦o City of Renton, WA
ier:hnolL*ies Parking Citation System RFP
provided within the local network. If a customer prefers the hosted model, all of the hardware/software,
uptime maintenance, and DRA functions become the responsibility of Tyler.
We currently process over 8.1 million citations peryear on our hosted server.
Architecture
The diagram on the following page shows the high-level architecture of a typical Brazos solution
implementation. All interfaces, data feeds, etc., will be established using XML or whatever format the
customer dictates during the kickoff process.
-
--------------------------------------
-
"AW 5 6ovCloud
Brazos Hosted Server ;
Availability Zones
' A B C
' Active ' `1'' ` M.
I '
1 t (SAKI! . 1 1 I S 1 1
r we 5lNH DL ' ' legacy Wen ' i We0�02 , 1
I IMultl-AZ) , I Server (Muhl-AZI r 1MulIFA2) ' 1
Timed Ops/
Ir
ADSS aServerl �' ' On -Demand
r Co :
j 1 ADS SOL Server • 11 ADS SQL Server , I Whrlows Svcs/ I 1
11RoductionNOWMUM-AZ IS1.P AZ DB OptNMzer 1
t 1 (ynde AZ) 1 r
I it 11 1
1 EIlmcSesrU I I I r DesncSesrch I
Amazon S3
1
Load ;
� Balancing---------------------------------------
;
Other Existing Systems
8 a
Court RMS
8
Other
NCIC/State Returns
Cradle A
AirCard irCard
802.11 802.11
Vehicle/Person Brazos Message Switch
Wants and Warrants
I �
Existing Message Switch
Security
The Brazos solution has a number of features that ensure that data are never lost, either from the device
to the e-citation server or from thee -citation server to the receiving system(s).
ON THE DEVICE
Once an officer saves a record (citation, Field Investigation or any other record), that information is
backed up to a non-volatile area on each proposed device. That non-volatile area contains all information
that has been saved along with the files needed to re -install the application. This means that not only are
the data secure, but also that once power is reapplied to the device, the application will reload
5/31/19
Other Existing Systems
8 a
Court RMS
8
Other
NCIC/State Returns
Cradle A
AirCard irCard
802.11 802.11
Vehicle/Person Brazos Message Switch
Wants and Warrants
I �
Existing Message Switch
Security
The Brazos solution has a number of features that ensure that data are never lost, either from the device
to the e-citation server or from thee -citation server to the receiving system(s).
ON THE DEVICE
Once an officer saves a record (citation, Field Investigation or any other record), that information is
backed up to a non-volatile area on each proposed device. That non-volatile area contains all information
that has been saved along with the files needed to re -install the application. This means that not only are
the data secure, but also that once power is reapplied to the device, the application will reload
5/31/19
s
a'• tyler
City of Renton, WA
' Parking Citation System RFP
automatically without the need for IT intervention. We have never lost a record that was saved on the
device. One of our clients left a ticket writer on the roof of a patrol car and lost the device in a field. They
did not find the ticket writer for two months (during the rainiest season on record for the Dallas area).
When the ticket writer was found by a maintenance worker, it was cleaned off and placed in the cradle.
After the device was recharged, the software automatically reloaded, and five tickets were pushed off of
that device.
IN TRANSIT
When the data are synced, two layers of technology ensure proper delivery. The Brazos solution provides
the first safeguard for the information. The solution works on a request/confirm model where all
information is sent, validated and confirmed before a transmission is considered complete. All data
transmissions receive a valid and authenticated confirmation message before the information is removed
from the mobile device. This method guarantees that all information is received and complete, even if a
connection is lost during the sync process. We have never lost a record in transit from any mobile device
back to the eCitation server.
ON THE SERVER
The Brazos eCitation server serves as a middleware product for electronically moving information from
the mobile devices to the receiving system(s). It also serves as a robust reporting mechanism for any
record captured from the mobile device. As such, the only mission -critical disaster recovery needs for this
box are the continued processing of records not yet sent to the receiving system(s) and the continued
process of citations that are being written on the street.
Once confirmation of the successful receipt of a record from the receiving system(s) is received by the e-
citation server, the Brazos solution can mark any and all records with the current status and the date that
status was received. The Brazos solution also allows the customer to re -download any citation record that
was rejected after modifications are made to resolve the conflict. While this is a "soft" safeguard to
pushing the information to the other system(s), it is important to note that the customer will have a
complete system to resolve issues and resubmit records to any and all system(s).
With these two layers of technology to guarantee data delivery, an outage of the e-citation server will not
cause a data loss situation. In the case of the e-citation server being unavailable, the records remain
either on the device or in the queue to be processed when the server comes back online.
AUTOMATED BATTERY RECOVERYTM
Battery loss is inevitable when deploying and using handheld devices, and battery backup is a critical
aspect of a successful backup and recovery plan. Handheld devices are not like PCs; they do not have hard
drives, so when the battery goes so does all of the installed software and data. Upon restoration of the
battery, the unit reverts to the original factory -shipped state.
How and if the device recovers from loss of battery is critical, and Brazos Automated Battery Recovery
(ABR) provides a strong recovery strategy that is as simple as inserting a charged battery. Upon battery
restoration, ABR kicks in, and the unit completely reinstalls all Brazos software and recovers all data as of
the last time the software was cleanly exited. No phone calls are needed, no software needs to be
reinstalled and no data is lost.
5/31/19 4
e
••::a, tyl+er
LOGIN REQUIREMENTS
City of Renton, WA
Parking Citation System RFP
Brazos requires a valid login to both the website and the Brazos software. The users are each assigned a
role(s) that defines what they have access to, what they can add/change/delete/view, etc., and the user
profiles are completely controlled by the customer. The users can also be assigned to a "group" with
certain profiles and security access defined.
We also allow for LDAP integration for the website, which allows the agency to manage roles within the
existing Microsoft Active Directory implementation.
ENCRYPTION
All data transferred to and from the devices are performed over a TLS 1.2 connection via webservices.
We can also utilize installed certificates on client machines, but most customers do not elect this route
due to potential maintenance issues. This includes downloads, uploads, software distribution and error
reporting. All communications are compressed and then encrypted via AES.
Data at rest is encrypted using AES-256.
WEB SECURITY
Since we utilize the hosted model for a significant number of customers, we have implemented industry
best -practices for server hardening and the security measures required for security. These include
intrusion detection, antivirus, turning off all unneeded ports, complete form and user authentication, etc.
Data Entry Methods
Brazos allows for the entry of citation data through a number of different methods including swiping of a
mag stripe, scanning QR and VIN barcodes, scanning registration stickers, keyboard, touch -screen, video,
audio, photo, and fingerprint capture. All of the rules surrounding the data entry, editing, reporting, and
printing are defined and controlled by each agency via BuildlT.
The data entry screens are easy to navigate because our system has been designed by the officers
themselves. Every aspect of the solution is configured to the customer's exact specifications. Our goal is
to make the process as efficient, effective, and safe for the officers as possible.
Interfaces
The Brazos solution was built on the idea that we would always be interfacing with other systems, and we
have built an import/export wizard that allows new interfaces to be implemented very easily. The Brazos
solution can access Open Database Connectivity (ODBC)-compliant databases, XML-based Application
Programming Interfaces (APIs) and file -based import/export methods for moving data to and from other
applications, including legacy systems. For this project, the citation records will be uploaded to the
eCitation server and can then be transmitted to the Washington State AOC and Renton Municipal Court
Journal CMS as dictated by the City.
We will match any file format (XML, flat file, CSV, etc.) utilized by the system we are interfacing with. WE
also will match any transport method (FTP, file drop, API, web services, and/or direct database injection)
that is required for the interface. We have implemented all of these file types and transport methods in
the past for both pushing data to and receiving data from other systems.
5/31/19
0
tyler
o�
City of Renton, WA
Parking Citation System RFP
To date we have interfaced with more than 40 different RMS, CAD, and court systems across the country.
We also run vehicle and person returns via our own Brazos Message Switch and third -party message
switches.
Reporting
Brazos has a robust management reporting capability. Since the citation data are stored on the e-citation
server, the reports can be generated and printed from any location/workstation with access to the
Internet and the proper security access to the customer's internal network. The customer determines all
user access levels. Via BuildIT, the administrator can manage all aspects of the devices — users, access
levels, reporting and automated software download. Users granted the necessary access level can run
reports from any computer connected to the Internet by logging into the eCitation server.
Any photo, video, audio clip, scanned document, etc., can be added to the system and associated with a
particular citation number (with the proper security access and workflow approval as defined by the
customer). Types of multimedia captured within a citation are dictated by functionality included within
the mobile hardware device.
Each and every report on the eCitation server allows for optional report parameters and sorting
capabilities. For example, the Citation Detail report (which prints the citation exactly as the defendant
saw it) can be run for all citations or scoped on any number of the following parameters: Beginning Date,
End Date, Officer, Stop Results, Citation Number or whether or not Officer Notes were entered. We have
a "hot spot" report that can be configured to be scoped by area, district, date/time, etc. If a parameter is
left blank then all records are assumed.
All reports can be exported to the following formats: HTML, PDF, Excel, TIFF, Web Archive, CSV and XML
file. Zooming on the report provides larger text. When printing the report, users are prompted to select
any printer on the network as with any standard Microsoft Office product.
ADHOC REPORTING
Tyler's Brazos Adhoc Reporting tool allows our customers to perform true adhoc reporting. If the
customer wishes to perform true adhoc reporting using its own existing adhoc reporting tool, Tyler will
provide a copy of the database which would be downloaded to another server (new or existing) so as to
not negatively impact the production response time.
DASHBOARD
Brazos includes a configurable dashboard upon which authorized users can select what they would and
would not like to see, including open items, ticket management, etc.
MAPPING
Brazos utilizes both ESRI and Google Maps for locator services and mapping. Using exposed locator
services and mapping providers from the agency's own ESRI implementation, Brazos will allow the users
to query which records should be displayed on the maps. Of course, all of this information can also be
used for true adhoc reporting and report creation in multiple visual displays (i.e. charts, graphs, etc.).
Brazos uses Cognos BI for all adhoc reporting and user -defined reporting.
5/31/19
s
•°�° tyler City of Renton, WA
0 Parking Citation System RFP
Following is an example of a "hot spot" report that can be configured to be scoped by area, district,
date/time, etc. Command staff can use this information to manage or redeploy patrol when necessary.
AUDIT REPORTS
Brazos includes a workflow/review/approval process which will be configured to exactly meet the needs
and requirements of the customer as described earlier. The customer controls who can make changes to
the system, citation records, etc. Timestamps and signatures on approvals, voids, etc. are required as
dictated by the customer.
Brazos records all entries, edits, deletions as well as user logins, and failed login attempts. We also
provide standard audit reports so that the customer can see at any time where every ticket number in
their jurisdiction resides. If customer would like to capture additional information such as record creation,
submission for review, approval, rejection/change request, deletion, etc., and provide a notes field in an
audit report, this is configured in BuildIT as well. We have implemented this audit functionality with
many of our existing customers.
Training
Training is an underestimated aspect of this project at most agencies and is a primary cause for
failure. The goal for our training program is that the officers will be able to fill out the electronic citation
long -hand (i.e., no DL swipe, VIN decode, or any other aid) and have it printed in less than four minutes.
The training class also teaches first level troubleshooting techniques for when things don't go absolutely
perfect —the officer can still be fully operational. It has been our experience that identifying and training a
handful of key officers who we think will adapt to the technology quickly and can in turn teach the rest of
the officers during the full deployment of the solution works best. Therefore, throughout our 820
implementations, we have utilized a Train -the -Trainer approach to training users on our software. We
provide these pilot officers with all of the tools that they need to train the remaining officers.
The Train -the -Trainer class is approximately two days long.
TRAINING MATERIALS
The Brazos Training Package includes training materials to allow agency trainers to conduct future
eCitation training and all documentation for the "Train -the -Trainer" program. The Tyler -written training
materials are also available to users through the Brazos Web Portal.
Support and Maintenance
Tyler prides itself on exceptional customer service and support after the sale. Our Toll -Free Brazos
Support Center Hotline is available 24x7x365. Using our web -based technology we offer the most
5/31/19
9
�•;:�a tyler
City of Renton, WA
Parking Citation System RFP
comprehensive maintenance program in the industry. As long as the customer stays current with the
annual maintenance contract, all of the following will be provided FOR NO ADDITIONAL CHARGE.
The maintenance agreement will automatically renew for the number of licenses, servers, and
interfaces in place at the time of renewal unless cancelled by the customer.
TECHNICAL SUPPORT
Tyler's Brazos provides two levels of technical support, via phone and email, to ensure that all issues
are handled in an expedient manner.
Support Services. During the term of the Agreement, Tyler will provide the support services to
maintain the Covered Software in good working order, keeping it free from material defects so that
the Covered Software shall function properly and in accordance with the accepted level of
performance as set forth in the License Agreement. The Support Center Hotline is available 24x7x365.
Remedial Support. During the term of the Agreement, Brazos will provide support for those
experiencing an error, defect, malfunction, or nonconformity in the Covered Software.
Upon receipt by Tyler of notice from Licensee through the Support Center Hotline of an error, defect,
malfunction, or nonconformity in the Covered Software, Tyler shall respond as provided below:
'M
Severity 1. Produces an emergency situation in
Tyler will provide a response by a qualified member
which the Covered Software is inoperable,
of its staff to begin to diagnose and to correct a
produces incorrect results, or fails
Severity 1 problem as soon as reasonably possible,
catastrophically.
but in any event a response via telephone will be
provided within one (1) hour. Tyler will continue to
provide best efforts to resolve Severity 1 problems
in less than forty-eight (4.8) hours. The resolution
will be delivered to Licensee as a work -around or as
an emergency software fix. If Tyler delivers an
acceptable work -around, the severity classification
will drop to a Severity 2.
Severity 2. Produces a detrimental situation in
Tyler will provide a response by a qualified member
which performance (throughput or response) of
of its staff to begin to diagnose and to correct a
the Covered Software degrades substantially
Severity 2 problem as soon as reasonable possible,
under reasonable loads, such that there is a
but in any event a response via telephone will be
severe impact on use; the Covered Software is
provided within four (4) hours. Tyler will exercise
usable but materially incomplete; one or more
best efforts to resolve Severity 2 problems within
mainline functions or commands is inoperable;
five (5) days. The resolution will be delivered to
or the use is otherwise significantly impacted.
Licensee in the same format as Severity 1 problems.
If Tyler delivers an acceptable work -around for a
Severity 2 problem, the severity classification will
drop to a Severity 3.
Severity 3. Produces an inconvenient situation in
Tyler will exercise best efforts to resolve Severity 3
which the Covered Software is usable but does
problems in the next maintenance release.
not provide a function in the most convenient or
expeditious manner, and the user suffers little or
5/31/19 8
S
••::•a tyler
City of Renton, WA
Parking Citation System RFP
no significant impact.
Severity 4: Produces a noticeable situation in
Tyler will provide, as agreed by the parties, a fix or
which the use is affected in some way which is
fixes for Severity 4 problems in future maintenance
reasonably correctable by a documentation
releases.
change or by a future, regular release from
Tyler.
UPDATES AND UPGRADES
Using our web -based technology we offer the most comprehensive maintenance program in the industry.
The maintenance agreement will automatically renew on an annual basis unless cancelled by the
customer. As long as the customer stays current with the annual maintenance contract, we will make any
change to any part of the solution (including updates requested by the Courts or the Legislature) at NO
ADDITIONAL CHARGE. Our'No Change Order' policy will ensure that our customers will continue to have
a relevant and superior solution for many, many years and will save thousands of dollars in the future.
Part of our strategy for providing outstanding support is keeping all of our customers on the current
version of software. Any time we release major or minor updates to the software, that software is
updated to the server and automatically downloaded to all devices (with no IT intervention). We also
have the ability to remotely update the operating system if needed but will be kept up to date FOR NO
ADDITIONAL CHARGE. If for any reason a customer decides not to receive these upgrades, Tyler will
support up to two versions back. If the software becomes older than two versions, there may be an
additional cost to 'catch up' the software if the automatic updating process cannot run unattended. We
typically provide minor releases at least once per month with major releases once per quarter.
The maintenance fee is waived in year 1 and begins in year 2.
5/31/19
Project Management Philosophy and Schedule
Tyler is committed to delivering a successful and referenceable electronic citation project to our customers. Our
implementation approach has been highly successful, and we feel that the steps outlined below provide the best method
to minimize risks and ensure a successful project. The key is to involve the customer in all phases of developing and
implementing software specifically for them, to meet their specific needs. Our average time to full deployment for a tier 2
or 3 agency from contract signature is 120 days. In cases where agencies and interfacing vendor systems have been
extremely responsive regarding configuration and deliverables, the time to deploy has been 90 days or less.
This includes: full customization for the customer, electronic interfaces into the Court and RMS systems, customized
reporting, installation, training, and the end -to -end operation of the entire solution.
NEEDS ASSESSMENT AND KICK OFF
To ensure that our customer's needs are addressed, Brazos will conduct a thorough needs assessment that captures
project as well as project owner information for all principals related to the project. Interviews with each principal
involved are conducted to identify both existing processes and new processes that result from implementation of this
system. From these interviews, a complete current and future project understanding is transferred from the customer to
Tyler from which Tyler can provide recommendations and solutions.
During the needs assessment phase, a highly specific Work Order is collaboratively created that explicitly identifies the
detailed operation, requirements of the entire system, roles and responsibilities for Tyler and the customer, along with a
detailed project plan of deliverables for all parties. The customer is given the opportunity to approve this Work Order to
ensure complete understanding of the entire system. The Work Order combines the requirements gathered along with
the proposal requirements to comprise a Statement of Work, which guides the rest of the process.
This two-day process would begin immediately following award of the contract and would produce the work
order/requirements document for the project.
SETUP AND CONFIGURATION
O Order ticket writer hardware and any software necessary
O Order new server hardware (if necessary)
O Order the interfaces with Court and/or RMS vendor(s)
O Receive the interface downloads from the Court and/or RMS software
O Offense codes
O Lookup values
O Officer information
O Streets and locations
O Load all lookup values into the database
O Lay out the ticket writer interface
O Lay out the defendant receipts
O Verify with customer the layout of receipt and verify legalese
O Create sample citations and send those samples to software vendors (if they require verification)
O Receive hardware order and install devices
O The average duration for this is two to three weeks
O The two largest risk factors are hardware availability and court or RIMS software vendor responsiveness.
PRODUCT INSTALL AND VERIFICATION
O Install software on devices
O Install the server software
O Install and verify RDBMS and reporting services
O Verify successful operation of server components
O Install and verify operation of mobile devices from the PD
O Show the screens and defendant receipts to PD and courts for feedback
O The typical duration is two days
O The largest risk factor is having the servers setup with latest OS and all applicable software/network settings are
cmmnlPtP.
BEGIN PILOT
O Train the pilot officers on system operation
O Continue making improvements and incorporating changes to ticket writers
O The defendant receipt has been approved and complete
O Complete the Citation Detail report to look like the defendant's receipt
O Spend at least a day or two having the officer write 'warnings' in the field
O Verify the data flow to the court and RMS systems
O Verify each field for applicable interfaces
O This phase is complete when we have the entire process complete and the officers are practicing with the
technology
O The typical duration is one week
O This largest risk factor for the project is that most of the major portions of this project must be complete. The
officers must begin the pilot with the software as close to complete as possible. There can be no false starts at this
point.
OPERATIONAL PILOT
O Closely monitor the data moving to and from the court and RMS systems
O Monitor the officers' output as well as any requests they have for improvement
O Start finalizing the documentation and verify it with the officers
O Begin planning the full training plan with the pilot officers to maximize the effectiveness of the program
O Verify citation output from the pilot officers to ensure the effectiveness of the training
O This phase can last from a month to a few months depending upon the success of the project and the feedback
from the pilot officers and PD administration.
Phase
Task
Attp&y
MmPeriptilor,
I Task
I Tt"
cx%met
DeUvgrables
Duration
Duration
1
For FnuW-~ Qrojerlsi: proem below would be rephimud In similar manw
1
Contract Award
TBD
JONT ;J)
2
Contrac[Signature
-BD
.4,-ENC+
3
Contract Processed by Tyler
'BD
4
Tyler Project Manager Assigned
9 Doys
9d
5
Welcome Aboard Call
1 Day
-fd
Pro ect Team ntroduced
`
Current Citation Documentation
-Y -P,(T
Reques_ed
'
Current Citation Documenta-;ion
�s.GENL,
Current Cita_ion
Provided
Documeniatior
6
Kick-0ff'Project
2,v
3W
J
Dfficial' fork Plan
KicKo=f Conference Call
1
Idemif� eCitati r- System (ECSI
.
J
Requirements
z
Gather requ rernents'r�rn all
J
pro�ec; oy:ners
3
Bu'Id official' or!c Plar,
J
4
'v'e-`y'ldork Plan,,,., th -vendors
J
`w' ork Plan to be sigred
off by Aeency
7
Sign -off of Work Plan by AGENCY
3 Days
3.5,1:
Ai ENC
8
Order hardware
-BD
9
ECS Requirements Due
-BD
3.5ar:
LGENCY
ECS Requirements Docs
(from KicKom
--
ECS Reouirernents Format
_
_
10
ed
Approved
_W
4.5v1
11
&gild Scheduled
3d
5tv
12
Setup Canfiguration of ECS [a€1-site)
Sw
aw
1
Se --up and Configure mobile
scftwsre
2
Setup and Configure all interfaces
IterfaceDocumentatior
3
Layout the citaEianprir,:aaU
Sa mWe Layouts fo
Approval
,,,
Install mobil_ software onto
AGENCY bard•a'vare 4olf-site)
_
5
Tes3ol;atic;•i sin; AGENCY
hardware
T
6
;.reate sample interface files `or
AS EN.( system(='
13
Create ATP Plan
1 w
51W
1
Bijlf l ATP F sn
T
Approve ATP Pian
AGENCY
24
Tyler ECS Te i ing (QiA)
TB D
g
1
Test Laptops and connectivity SCE
i�rr•�=+r
T
^
s
Tes: ad interface_ for server
T
3
Tess wet citation entry screen
T
4
Test wet: -based reporting
T
5
Certifv ECS teased upon A—i r
_
is
ChvsitieECS Testing
TBD
9:,
1
Test! aptnps End cc^inectivivi Ca
server
2
Test a"i mterfaces for server
�
5
tiertify ECS based upon AT'e
16
AgmKy Re ALw
2w
11w.
1
Identif-y New/P-Tvised Requirements
AGENCY
2
Res&ve tlewiRe ued Requirements
T
3
Tes Updateq ECS
T
4
Certify ECS based' upon A s -
17
Sd
1
Day 1: Train � ticket seems: in
Orissrcom
Day Z: Field-bMa_a ECS -training with
Clfficers ITrair the trained
Day 3 System A'drsirustrator
Trainana
-
Int-oduction ta-ZuppartTeam Celi
5
Addieiona4 on-sita training
3 d
b
Appro% ai for Go-ilive
AGENCY
�ient sign_ off on Sc-
live
GO-LIWE
18
Post-lmpleara"caden Phase
1
I_5ues repzirted/New RequeSta
submitted ahrougt Suppc Team
AuEhlCY
Post-Irrpterr__ntation---=-Bo,C_11
Solution Plan and a cmeiine is;- any
3
remalning items delivered to client
T
Solution Plan 3t
byProject M3nagsr
Tirrel ne
ens iranzitioned to Rail -ferns
4
Support
i9
Fin af Aoceptame f rtferns um task
=d
's3.5ry
T
C!:ient signs off on
15)
project
MD
End of Project
a4ww
0ebrief of abl prgiect
orimopals
Functional Requirements
Ref # Requirement Tvoe Cede CemmPnt
Client Software
F-1
Ability to issue Citations, Warnings and Abandoned Vehicle
R
3
Notices.
F-2
Citation Data fields:
R
3
Every aspect of the project (tasks, screens, print jobs, business rules,
Agency (always "RENTON POLICE DEPARTMENT")
fields, etc.) is laid out exactly to your requirements and workflow.
Date/Time (automatically current date/time)
Location
Issue No. (automatically next number)
Issue Date (automatically current date)
Issue Place (always "RENTON, WA")
Infraction:
Violation code, description, and fine
Amount Due (calculation)
Date Due (calculation)
Vehicle:
License No.
VIN
Registration State
Registration Expiration
Vehicle Make
Vehicle Model
Vehicle Year
Vehicle Style
Vehicle Color
Permit number
Officer Remarks
- Officer Notes
Officer number, name (based on login)
F-3
Abandoned Vehicle Data fields:
R
3
Agency (always "RENTON POLICE DEPARTMENT")
Date/Time (automatically current date/time)
Location
Issue No. (automatically next number)
Issue Date (automatically current date)
Vehicle:
License No.
VIN
Registration State
Registration Expiration
Vehicle Make
Vehicle Model
Vehicle Year
Vehicle Style
Vehicle Color
Odometer Reading
Officer Remarks
-Officer Notes
Officer number, name (based on login)
Date Letter was Mailed
F-4
Ability to manually enter data in fields.
R
3
F-S
Ability to override data in fields with defaulted or imported
R
3
date.
F-6
Populate the following fields with Optical Character
0
2
This is accomplished via the proposed interface between Brazos and
Recognition (OCR) data from.scan/picture:
the AutoVu LPR system. Brazos does not have latent OCR capabilities
License Plate
at this time.
VIN
F-7
Ability to have at least two violations per citation.
R
3
F-8
Ability to have at least three violations per citation.
0
3
F-9
Must show Fine amount per violation.
R
3
F-10
Must show total amount due for all violations.
R
3
F-11
Must be able to add multiple Officer remarks.
R
3
F-12-1
Must be able to add freeform Officer remarks.
R
3
F-13
Must be able to select prewritten Officer remarks with the
ability to edit them.
F-14
Must be able to attach one or more photo.
R
F-15
Must be able to easily select photo(s) to include/attach.
R 3
R
R
3
3
R 3
R 3
F-22 jActive Directory integration for Single Sign -On (preferred) 1 0
F-23 Ability to void a citation
F-24 Ability to query records by one or more of the following:
Date range
Location
Officer
Record type
Issue number range
F-25 Query result to include counts R
F-26 Requiring record history/audit trail to include date/time and R
user of the following record activity:
Uploaded from handheld
Exported
F-27 Requesting history/audit trail to include date/time and user of O
the following record activity:
Transmitted to the Court
Printed from Back office
F-28 Record history/audit trail easily viewed and accessible through R
the BackOffice software.
F-29 Time should automatically change for Day Light Savings O
Administrative
F-30 List changes should be pushed to handhelds when made. R
(examples of list: violations, officer remarks, makes, models,
color...
F-31 1User account maintenance (usernames, permissions...) I R
3 1 1
3 Brazos supports single sign -on to other mobile systems using LDAP
integration for all server components and laptops. We have also
found that LDAP integration is not practical for handheld devices due
to the disconnected nature of their login process. Typically we
provide the user management for all handhelds.
BackOffice Software
0 3
R 3
3
3
i
In
3 Changes can be uploaded to the server via our web -based
configuration tool BuildIT. Once the changes are processed according
to the agency -defined workflow, they are automatically pushed out
to the handhelds upon their next sync.
3 The agency's administrator maintains all user security profiles via
BuiIdIT.
F-32 Ability to customize Abandoned Vehicle Letters R 3
F-33 Ability to print Abandoned Vehicle Letters by date range with R 3
specified sort order
Security
F-34 Ability to create different permission level groups/templates. R 3 JAll security is defined and controlled by the agency.
F-35 Changes to permission templates must automatically reflect in R 3
all users assigned to group/template.
Media
F-36 Ability to customize citation print design to meet Police and R 3
Court requirements.
F-37 Ability to customize warning print design to meet Police R 3
requirements.
F-38
Ability to customize the abandon vehicle notice print design to
R
3
meet Police requirements.
F-39
Pre-printed citation stock with Renton header and footer on
O
0
In our experience with over 820 customers, we have observed that
the Front and instructional information on the back.
most agencies prefer to use single -sided paper rather than using pre-
printed stock. This is primarily because the legalese that
accompanies a citation changes over time, and when it does, any pre-
printed stock is wasted. Therefore we have included Brother's
thermal paper for this project.
The layout of the printed citation is defined and controlled by the
City. We can almost exactly recreate the layout of the City's existing
parking citation layout using BuildIT. Each type of form created can
have its own layout.
Data Transfer
F-40
Handheld data needs to sync to the backend software from
R
3
the field.
F-41
Handheld data needs to sync to the backend software
R
3
The frequency of the data sync is defined by the customer.
throughout the day. (Not just at end of day.)
Equipment/Hardware
F-42
Citation handheld includes a camera with flash.
R
3
F-43
Citation handheld with a touch screen including touch screen
R
3
keyboard.
F-44
Printer must me mobile. Either included as part of the
R
3
Tyler proposes the Brother RuggedJet RJ4230 mobile Bluetooth
handheld, or worn on officer with something such as a belt,
printer for this project.
clip or shoulder strap.
F-45
Handheld should be small and light enough to be held with
R
3
The Brother RJ4230 weighs less than 2 pounds.
one hand.
F-46
Handheld charging in car.
0
3
A vehicle charger is included in the proposal.
Integrations
F-47
Proposed solution shall have a one-way integration with
R
3
Interface included in proposal.
AutoVu (LPR). Citations must populate with the following data
from AutoVu (LPR):
License Plate Number
Pictures
F-48
AutoVu (LPR) Integration - Citations should populate with the
O
3
following data from AutoVu (LPR):
GPS Location
First read date/time and second read date/time
F-49
Interface with Washington State, or other system, to pull in
0
3
Interface included in proposal.
the following based on license plate number:
Registration State
Registration Expiration
Vehicle Make
-Vehicle Model
Vehicle Year
Vehicle Style
- Vehicle Color
F-50
The following citation information must be sent to the
R
3
Interface included in proposal.
Washington Court Data Exchange Vehicle Related Violations
(VRV) system. Warnings and Abandoned Notices will not be
sent over:
Citation information
Citation image
Officer notes (not included on the citation)
Photos
Cost
Item Cost
Software and Hardware
Brazos eParking Licenses (3 Devices x $850) $ 2,550
Module: Abandoned Vehicle (1 x $3,250) $ 3,250
Handheld Device & Accessories
TC75EK-2MB22AB-US / Zebra EVM, TC75X, w/GMS (3 x $1424) $ 4,272
Z1AE-TC75XX-5C00 / Zebra EVM, Warranty, TC75, 5 year (3 x $505) $ 1,515
CRD-TC7X-CVCD1-01 / Zebra EVM, TC75, Vehicle Cradle -charge only (3 x $138) $ 414
CHG-AUTO-CLA1-01 / Zebra EVM, TC7X, Auto Charger for Vehicle Cradle (3 x $63) $ 189
CHG-AUTO-HWIREl-01 / Zebra EVM, TC7X, Vehicle Power Cable for Vehicle Cradle (3 x $81) $ 243
Printer & Accessories
RJ4230BL / Brother, Printer, Rugged Jet RJ4230B-L (3 x $664)
$ 1,992
207601-001 / Brother, Warranty, Mobile, 1 year (3 x $26)
$ 78
PA-CR-002 / Brother, Acc-Printer, RJ4200 Series, Docking/Mounting Station (3 x $164)
$ 492
LB3690 / Brother, Rugged Jet, Vehicle Adapter -Cigarette Plug (3 x $20)
$ 60
LB3834 / Brother, Pocketjet, Rugged Jet, AC Charger (3 x $42)
$ 126
LBX064 / Brother, Acc-Printer, RJ4200, Shoulder Strap w/metal swivel clips and rubber shoulder pad (3 x $20)
$ 60
LB3601 / Brother, USB Cable, 4 ft. (3 x $10)
$ 30
RDM02U5 / Brother, Rugged Jet, Paper, Thermal, premium, 36 rolls per case (2 x $133)
$ 266
Software and Hardware Subtotal
$ 15,537
Setup and Implementation
System Installation and Setup
$ 10,000
Configuration
$ -
Project Management Services
$ 2,000
Implementation Planning and Assistance
$ -
Training
$ 2,000
Travel
$ -
Setup and Implementation Subtotal
$ 14,000
Integrations
Integration with LPR System (AutoVu by Genetec)
$ 3,250
Washington State ACC Export/Integration
$ 3,250
Renton Municipal Court Journal CMS
$ 3,250
Integrations Subtotal
$ 9,750
Maintenance/Hosting and Support
Maintenance and Support -Year 1 (Included in License Costs)
$ -
Maintenance and Support -Year 2
$ 4,584
Maintenance and Support - Year 3
$ 4,584
Maintenance and Support -Year 4
$ 4,584
Maintenance and Support - Year 5
$ 4,584
Maintenance and Support Subtotal
$ 18,336
Custom Work
N/A
Custom Work Subtotal $ -
Other
Integration with Renton PD's NW RMS System (If requested - No cost due to "Tyler Alliance") $ -
PROPOSALTOTAL
Other Subtotal $ -
GRAND TOTAL $ 57,623
Hourly Rates
Training $ 125
Project Management $ 125
Programmer/Analyst $ 125
Technical Support Analyst $ 125
Payment Schedule Narrative
Tyler will invoice Client for the License Fees upon delivery of the software. Maintenance and Hosting Fees will be invoiced upon one (1) year
from the effective date and annually thereafter on the anniversary of that date. The first year's maintenance and Hosting Fees are waived.
All payment terms are net thirty (30) days.
Please refer to the accompanying file ParkingCiteSystem_2019_TylerTechnologies_LicenseAgreement.pdf for additional details.
THIS PROPOSAL IS VALID FOR 90 DAYS.
Client Name:
Contact Name:
Title:
Phone Number:
Email Address:
Website:
Type of Service Provided:
Length of Time Using Proposed Solution:
Client Name:
Contact Name:
Title:
Phone Number:
Email Address:
Website:
Type of Service Provided:
Length of Time Using Proposed Solution
Client Name:
Contact Name:
Title:
Phone Number:
Email Address:
Website:
Type of Service Provided:
Length of Time Using Proposed Solution
Client References
Client 1
Mercer Island Police Department
Jeff Magnan
Commander
206-275-7917
jeff.magnan@mercergov.org
http://www.mercergov.org/Sectionlndex.asp?SectionlD=84
eParking
1 Year
Client 2
City of Austin
Lyndon Meris
Parking Manager
512-974-1497
lyndon.meris@austintexas.gov
http://www.austintexas.gov/
eParking, eCitations, Field Interview, Criminal Trespass
4 Years
Client 3
City of Fort Worth
Peter Elliott
Parking Manager
817-392-7977
peter.elliott@fortworthtexas.gov
http://fortworthtexas.gov/
eParking, eCitations, Field Interview, Criminal Trespass
1 Year