HomeMy WebLinkAboutCity of Mia. agreement' City of Miami Municipal Software Corp.
MARCH, 29, 2004 APPLICATION SOFTWARE IMPLEMENTATION AGREEMENT
AGREEMENT
Between
CITY OF MIAMI
and
MUNICIPAL SOFTWARE CORPORTION
March 29, 2004
Page i
City of Miami Municipal Software Corp.
MARCH, 29, 2004 APPLICATION SOFTWARE IMPLEMENTATION AGREEMENT
TABLE OF CONTENTS
PREAMBLE 1
SECTION I: DEFINITIONS 2
A. DEFINITION OF TERMS 2
SECTION II: SCOPE AND TERM OF AGREEMENT 3
A. SCOPE OF AGREEMENT 3
B. TERM OF AGREEMENT 4
SECTION III: MUNICIPAL'S RESPONSIBILITY 4
SECTION IV: CITY'S RESPONSIBILITY 5
SECTION V: SUPPORT SERVICES 6
A. SCOPE OF SUPPORT SERVICES 6
B. ON -GOING SUPPORT FOR LICENSED APPLICATION SOFTWARE 8
C. SYSTEM SUPPORT SERVICES 8
D. DATA CONVERSION 8
E. TRAINING 9
F. IMPLEMENTATION SUPPORT SERVICES 9
G. OTHER THIRD -PARTY SOFTWARE 9
SECTION VI: MODIFICATION OF SCOPE 10
SECTION VII: INSTALLATION, DELIVERY, AND TESTING 11
A. INSTALLATION AND DELIVERY 11
B. ACCEPTANCE TESTING 11
C. RELIABILITY TESTING 12
Page ii
City of Miami Municipal Software Corp.
MARCH, 29, 2004 APPLICATION SOFTWARE IMPLEMENTATION AGREEMENT
SECTION VIII: ACCEPTANCE PROCESS 12
A. ACCEPTANCE PROCEDURE 12
B. PAYMENT SCHEDULE 14
SECTION IX: APPLICABLE TAXES 15
SECTION X: WARRANTY OF PERFORMANCE 15
A. COMPLIANCE WITH STATE AND FEDERAL AUDIT REQUIREMENTS 15
B. WARRANTY OF PERFORMANCE 15
C. LIQUIDATED DAMAGES 16
D. CORRECTION OF ERRORS UNDER THE WARRANTY 17
E. ORAL REPRESENTATIONS 17
F. PROGRESS REPORTS 17
G. TERMINATION 17
SESSION XI: LIABILITY, INDEMNIFICATION AND DEFAULT 18
A. LIABILITY, INDEMNIFICATION AND DEFAULT 18
B. BANKRUPTCY/SUPPORT CESSATION 18
C. INSURANCE 18
D. LIMITATION OF LIABILITY 19
SESSION XII: GENERAL PROVISIONS 19
A. ASSIGNMENT 19
B. GOVERNING LAW 19
C. COSTS AND ATTORNEYS FEES 20
D. MEDIATION 20
E. ARBITRATION 20
Page iii
City of Miami Municipal Software Corp.
MARCH, 29, 2004 APPLICATION SOFTWARE IMPLEMENTATION AGREEMENT
F. ENTIRE AGREEMENT(S)/AMENDMENTS 20
G. CONSTRUCTION 21
H. SERVICE OF NOTICE 21
SIGNATURES: 21
Page iv
City of Miami
MARCH, 29, 2004
Municipal Software Corp.
APPLICATION SOFTWARE IMPLEMENTATION AGREEMENT
PREAMBLE
This Agreement entered into this 19th day of March 2004 on behalf of the City of Miami, a
Florida Municipal corporation duly organized under the laws of the State of Florida, located at:
Miami Riverside Center,
444 S.W. 2nd
Miami, Florida 33130
hereinafter referred to as `CITY' and Municipal Software Corporation, a British Columbia,
Corporation, authorized to sell in the State of Florida, and having its principal office located at:
4464 Markham Street, Suite 1101
Victoria, British Columbia
V8Z 7X8
hereinafter referred to as `VENDOR;'
RECITALS:
WHEREAS, the CITY has established the need for computer application software,
implementation services, training, text support, and maintenance ("Services") as set forth in the
Requirements Traceability Matrix ("RTM") attached hereto as Exhibit A; and
WHEREAS, in response to said RTM, VENDOR submitted a Final Proposal ("Proposal") dated
March 12, 2004, attached hereto as Exhibit B to provide Services; and
WHEREAS, a similar project in scope and nature was competitively tendered at the City of San
Mateo, California and, after reviewing the Agreement pricing and terms and conditions for San
Mateo, the CITY has negotiated the pricing, terms and conditions established in the Agreement
that the VENDOR has entered into with San Mateo; and
WHEREAS, after careful evaluation the CITY has determined that, due to its background and
expertise, VENDOR is qualified to provide the aforesaid application software and services, and
the CITY is desirous of entering into a Agreement with VENDOR desires to provide said
application software and services to the CITY; and
WHEREAS, the Miami City Commission, by Resolution No. , adopted
, ("Resolution"), approved the acquisition of computer application software and
services awarded under the City of San Mateo Agreement.
NOW, THEREFORE, in consideration of the foregoing and of the mutual covenants set forth
herein, VENDOR agrees to sell, and provide to the City the Services as defined hereunder, under
Page 1
' City of Miami
MARCH, 29, 2004 APPLICATION SOFTWARE IMPLEMENTATION AGREEMENT
Municipal Software Corp.
the terms and conditions of the City of San Mateo Agreement, which is hereby incorporated into
and made a part of this Agreement, modified as follows.
SECTION I; DEFINITIONS
A. DEFINITION OF TERMS
It is the CITY's understanding that, a word in an agreement means what the agreement says
it means, within the limits of common usage.
For purposes of this Agreement, the following are defined terms:
Acceptance means the acceptance of the Application Software and Implementation
Services in accordance with the procedures and processes of this Agreement by both
VENDOR and the CITY.
Application Software is the software and Third Party Software owned or marketed by
VENDOR as set out in the Final Proposal.
Change Control Document means the formal printed paper prepared by the VENDOR
outlining specific changes, additions or deletions to the Implementation Services to be
completed.
Documentation means the formal printed paper or electronic technical and user manuals
supplied by VENDOR or its licensors for the Application Software.
Enhancements means updates, upgrades and other enhancements to the Software which
are generally released to the public by VENDOR after the execution date of this
Agreement.
Implement means that the Application Software has been installed and all agreed upon
modifications, conversions and training have been completed and the Application Software
is made operational, all in accordance with the terms of this Agreement.
Installation Activities means any and all software configuration activities, software
loading, software testing, etc., whether performed at the CITY's site or at VENDOR's site.
Primary Vendor means VENDOR who will provide the Application Software listed in the
Exhibit A of this Agreement.
Product means the Application Software and related documentation, including manuals,
and any other information confidential to VENDOR or its licensors.
Scope Document means the formal printed paper prepared by VENDOR, which outlines
findings and recommendations on how to proceed through the project.
System Configuration means the hardware, server, workstations, peripherals, cabling,
networks, and other communications devices related to the physical installation.
Software means the compiled object code version of the latest version of VENDOR's
application software known as "CityView" and any enhancements and related
documentation, excluding maintenance diagnostics.
Page 2
City of Miami
MARCH, 29, 2004
Municipal Software Corp.
APPLICATION SOFTWARE IMPLEMENTATION AGREEMENT
Third Party Software means any software (and related documentation) not developed by
VENDOR but purchased by the CITY from other provider under this project.
Training means dedicated professional education about all Application Software listed in
this Agreement. Training may consist of both structured classroom training and individual
operator training and assistance.
SECTION II: SCOPE AND TERM OF AGREEMENT
A. SCOPE OF AGREEMENT
The CITY hereby retains VENDOR to implement the Application Software (as shown in Exhibit
A attached hereto and made a part hereof) in a project comprised of the following:
1. Infrastructure Review
2. Subject Matter Expert Training
3. Business Process Review and Data Collection
4. Functional Scope Documents Produced
5. Application Prototype Development
6. User Review and Change Control Document Produced
7. Refinements
8. Data Conversion
9. Installation Services and Testing
10. Training (Final Change Control Document may be produced)
11. Final Acceptance
Once VENDOR provides the CITY with the required Detailed Functional Scope Documents, work
may not proceed to the next task until the Scope Documents has been agreed to in writing by the
CITY, and formal authorization must then be provided in writing to VENDOR by the CITY in
order to proceed to each of the following phases of the project, all as outlined in Section VIII, A.
Acceptance Procedure below. As each of the Scope Document and Change Control Document(s)
is completed and agreed to by the CITY, it becomes part of this Agreement.
The CITY has agreed upon the following implementation deliverables:
1. Detailed Functional Scope Documents (will be attached as Exhibit to this Agreement
once completed)
2. Change Control Document(s) (will be attached as Exhibit to this Agreement once
completed)
3. A maximum of 45 CityView forms/reports (to be developed and refined by VENDOR)
for the implementation of Phase 1
4. Data Conversions
Page 3
'City of Miami Municipal Software Corp.
MARCH, 29, 2004 APPLICATION SOFTWARE IMPLEMENTATION AGREEMENT
5. 3rd Party Application Integrations (only GIS at this time) note: we are waiting for
confirmation of 3rd party applications to be integrated
6. End User Training and Testing
7. Final System Acceptance and Sign -off
8. Go Live
VENDOR shall perform all of the aforementioned Installation Services (will be attached as Exhibit
to this Agreement once completed) in accordance with the terms of the Final Proposal, except as
may otherwise be agreed to in writing by the CITY.
B. TERM OF AGREEMENT
The term of this Agreement shall commence as of the date of the execution of this Agreement and
shall end upon completion by VENDOR of the Installation Services (as evidence by a Letter of
Completion signed by both parties), unless this Agreement is earlier terminated by the CITY
pursuant to the terms of this Agreement. During the term, VENDOR will provide the Installation
Services and any other services agreed to in writing by the parties. Any amendments or
modifications shall be executed in writing and signed by duly authorized representatives of both
parties. VENDOR shall complete the Installation Services in accordance with the delivery
schedule detailed in the Project Schedule (will be attached as Exhibit to this Agreement once
completed), as may be modified by the Scope Document and Change Control Document(s). The
Application Software is being licensed to the CITY, and ongoing maintenance and support of the
Application Software will be provided by VENDOR, in accordance with the terms of the Support
Services detailed in Section V, Support Services below. In the event of any conflicts between the
terms contained in this Agreement and the RTM or Proposal, the applicable terms of this
Agreement shall control.
The CITY reserves the right to implement the Land Use Certificate System, Code Enforcement
and Land Management in a phased implementation, and VENDOR agrees to guarantee the pricing
as shown in EXHIBIT A for a period of 2 years from the date of this Agreement. For the purpose
of this Agreement EXHIBIT A refers to 2 separate phases. Phase 1 includes for the Land Use
Certification System and Code Enforcement as 2 separate projects running concurrently yet
independent of one another. Phase 2 includes for the implementation of Land Management. If the
CITY determines to divide Phase 2 into multiple phases, VENDOR reserves the right to re -define
the estimates for implementation services based on the CITY's revised requirements but using the
per unit costs guaranteed for 2 years from the date of this Agreement.
SECTION III: VENDOR'S RESPONSIBILITY
VENDOR represents that it will furnish to the CITY a complete, fully operational Application
Software Systems as detailed in Scope Document and Change Control Document, and that the
Application Software shall be free from programming errors materially detrimental to the
operation of the system in accordance with the Documentation. This representation of VENDOR
shall survive for a period of one (1) year after the termination of this Agreement based on the
consideration provided by the City.
Page 4
City of Miami Municipal Software Corp.
MARCH, 29, 2004 APPLICATION SOFTWARE IMPLEMENTATION AGREEMENT
VENDOR agrees to be the primary vendor for all Application Software purchased from
VENDOR. VENDOR will acquire, deliver, install and certify (in the letter of Completion) the
proper operation of the Application Software on a turnkey basis. This includes:
1. Acting as single point of contact for Application Software installation, third party
software integration, Training and Software support issues, for all activities detailed in
the Installation Services.
2. Provide Application Software system support and maintenance on the Software
provided by VENDOR as per the VENDOR and the CITY shall protect the work sites
and work from damage and shall make good all entry to same occurring before the
completion of the work to be performed under this Agreement.
3. All on -site work shall be scheduled in advance by VENDOR and the CITY and shall be
approved by the CITY's Project Manager.
4. VENDOR and the CITY shall comply with all applicable statutes, laws, ordinances,
rules and regulations relating to the performance of their respective work hereunder. If
any portion of this Agreement is at variance therewith, VENDOR and the CITY shall
promptly notify the other party upon discovering same and the responsible party shall
immediately bring the matter up to specification.
5. VENDOR shall secure at its own cost and expense, and be responsible for any and all
payment of all income taxes, social security, state disability insurance compensation,
unemployment compensation and other payroll deductions for VENDOR and its
officers, agents and employees and all business licensed, in connection with the project
and/or the services to be performed hereunder.
6. VENDOR agrees that title to all materials prepared hereunder, including, without
limitation, all original drawings, designs, reports, both field and office notices,
calculations, computer code, language, data or programs, maps, memoranda, letters and
other documents, shall belong to CITY, and VENDOR shall turn these materials over
to CITY upon expiration or termination of this Agreement or upon project completion,
whichever shall occur first. These materials may be used by CITY as it sees fit.
7. VENDOR shall be responsible for full compliance with the immigration and
naturalization laws of the United States and shall, in particular, comply with the
provision of the United States Code regarding employment verification.
8. Out-of-pocket expenses incurred by VENDOR for travel related, supplies, and other
expenses shall be paid by VENDOR.
SECTION IV: CITY'S RESPONSIBILITY
The CITY shall fully cooperate with and assist VENDOR in the performance of its responsibilities
under this Agreement. As part of the CITY's responsibilities, it will designate a qualified staff
member who will be the CITY's Project Manager, and who will have authority to act for the CITY
and provide VENDOR with necessary information and data concerning CITY's operations and
activities.
Page 5
City of Miami Municipal Software Corp.
MARCH, 29, 2004 APPLICATION SOFTWARE IMPLEMENTATION AGREEMENT
The CITY will provide appropriate resources to participate in all business analysis phases, process
mapping, business rule definition and creation of acceptance criteria. During the business process
review and data gathering phase, the CITY may, subject to its written approval, be assigned
additional tasks which may become additional responsibility of both the CITY and VENDOR to
complete.
Failure on the part of the CITY to complete assigned tasks within mutually agreed schedule will
constitute a delay beyond the control of VENDOR and subsequent schedules may be affected and
adjusted accordingly.
Significant delay on the part of the CITY may cause VENDOR to incur costs not foreseen at the
creation of this Agreement; provided, however, that the CITY shall not be liable for any additional
costs incurred by VENDOR due to such delay unless the CITY has failed to diligently commence
curing such delay within fifteen (15) days after receiving written notice from VENDOR detailing
the nature of the delay.
SECTION V: SUPPORT SERVICES
A. SCOPE OF SUPPORT SERVICES
VENDOR shall maintain CITY's Licensed Application Software so that they operate in
conformity with materials as set forth in the VENDOR'S Proposal, the RTM, Scope
Document and Change Control Document including all future updated or enhanced
versions.
VENDOR shall use best efforts to correct reproducible material errors or malfunctions after
notification by CITY, supply technical bulletins, updated user guides and other Licensed
Materials as they are released by VENDOR, and supply CITY with Updates to the
Licensed Application Software within 30 days of their announced release.
VENDOR shall render support and services during Normal Working Hours (5:30AM to
5:30PM PST/PDT, Monday through Friday, excluding federal holidays and the day
following Thanksgiving) for the following:
1. Telephone Support - Calls for assistance related to operation of the Licensed
Application Software, reporting of a potential error condition or abnormal termination
of a program, or request for minor assistance related to the Licensed Application
Software;
2. Support Enhancements - Selected Enhancements, the nature and type of which shall be
determined solely by VENDOR. Such provision shall not preclude VENDOR from
providing other Enhancements of the Licensed Application Software to the CITY free
of charge.
3. Software Warranty — Since CITY is obtaining Software Support from VENDOR, and
such Software Support is in effect without interruption from inception of this
Agreement, VENDOR will warrant the Licensed Application Software to be free of
errors for the life of this Agreement.
Page 6
.City of Miami Municipal Software Corp.
MARCH, 29, 2004 APPLICATION SOFTWARE IMPLEMENTATION AGREEMENT
4. Error Correction - Any substantive, replicable problem, which causes interruptions to
the CITY's business operations, and is caused by incorrect operation of the computer
code of the Licensed Application Software or an incorrect statement or diagram in
Licensed Documentation that produces incorrect results or causes incorrect actions to
occur that CITY identifies and documents to VENDOR will be corrected by VENDOR
with either a software modification or addition that, when made or added to the
Licensed Application Software, establishes material conformity of the Licensed
Application Software to the Licensed Documentation, or a procedure or routine that,
when observed in the regular operation of the Licensed Application Software,
eliminates the practical adverse effect on Licensee of such non -conformity. The terms
and conditions for reporting and resolution for such errors are as follows:
• For any reproducible program error or malfunction of the Licensed Application
Software designated by CITY as "Critical" and reported by CITY during normal
support hours, VENDOR will begin a technical review of the problem and respond
by phone to CITY within two (2) working hours after receipt of such notification.
VENDOR shall work diligently to correct the error or malfunction and provide a
daily status briefing to the CITY as to the disposition of the problem, which will be
accessible by phone or access to VENDOR'S web site.
• For other reproducible program errors or malfunction of the Licensed Application
Software reported by CITY during normal support hours, VENDOR will use its
best efforts to assign a technician to the problem and provide status reports on
progress to resolution via web -based system. Problems of normal priority will be
automatically escalated to a higher priority if no action is taken within four (4)
business hours. Problems of lower priority (as designated by CITY) will not be
automatically escalated.
• If problems reported by CITY as Critical are determined to be caused by abuse,
misuse, or unauthorized modifications, and the proper use had been covered in a
VENDOR provided training session, VENDOR may charge CITY for the
documented technician hours of work on the problem at the then current technician
rates.
• If CITY feels that a critical problem is not being handled in a timely fashion,
notification of an escalation of the problem should be sent to the following four (4)
people, in addition to Technical Support:
a. President and CEO (Robert Bennett)
b. Vice President, Client Services (Troy Kusy)
c. Manager, Product Development (Sue Leuchter)
d. Manager, Technical Support (Robin Gwynne)
• Failure of VENDOR to initiate a review of a Critical problem and provide daily
status briefings once VENDOR has received escalated notification may result in a
penalty. It is understood and agreed that continued functioning of the system is
essential to the CITY's business operations and that it will be impossible to
Page 7
' City of Miami Municipal Software Corp.
MARCH, 29, 2004 APPLICATION SOFTWARE IMPLEMENTATION AGREEMENT
determine the actual damage which the CITY will sustain in the event of, and by
reason of, delayed technical support. It is agreed, therefore, VENDOR may pay to
CITY the sum of ten percent of the annual maintenance fee for each calendar day
delay in critical technical support response or each calendar week delay in routine
technical support response as liquidated damages, each time frame being measured
from the date of escalated notification. This payment will be in the form of a check
payable to the CITY or credit against current or future invoices, at CITY's option.
• It is agreed and understood that minor variations in the above parameters may occur
from time to time and that such variance does not necessarily entitle the other party
to the remedy stated. However, if such variance is significant (i.e. more than eight
working hour response) or there is a consistent pattern of three or more minor
abuses, the offended party will be entitled to the remedies stated herein.
5. Maintenance Modifications — When any errors in the Licensed Application Software
are identified by CITY or other licensed user of VENDOR'S Licensed Application
Software, VENDOR will make modifications or revisions to the Licensed Application
Software or Licensed Documentation that correct these errors and promptly distribute
thoroughly tested patches, updates, or new versions of the Licensed Application
Software along with detailed instructions as to how to apply the modifications to the
installed version of the Licensed Application Software.
B. ON -GOING SUPPORT FOR LICENSED APPLICATION SOFTWARE
VENDOR shall provide continuing on -going support services necessary to repair
Application Software systematic program bugs or identified logic and operational problems
and to keep the licensed Application Software compatible with then -current supported
versions of all (third party operating systems, database engines, and utilities) software
implemented in this project.
C. SYSTEM SUPPORT SERVICES
In addition to training services, VENDOR will provide system support services which shall
include, but not be limited to, cooperating with CITY staff in configuring CITY acquired
hardware and System Software as defined in Vendor's RFP response to support the
VENDOR's Licensed Application Software, setting up tables and parameters for CITY's
unique installation, preparing backup scripts to back up the databases for the applications,
and training CITY's technical staff how to perform these tasks as well as diagnostic
troubleshooting techniques for the VENDOR Licensed Application Software.
D. DATA CONVERSION
VENDOR shall be responsible for conversion of CITY's current data in machine-readable
form, if any, to the format required by the Licensed Application Software. CITY shall
provide all requested data for conversion using formats specified by VENDOR. In the
event that the CITY is unable to provide requested data in the format specified, VENDOR
Page 8
City of Miami
MARCH,29,2004
Municipal Software Corp.
APPLICATION SOFTWARE IMPLEMENTATION AGREEMENT
may request a Change Control Document to assist CITY in transforming the requested data
to the prescribed format.
E. TRAINING
VENDOR shall provide all training as specified in the Agreement directly to the various
user -groups for the Application Software at CITY's facilities. Additional training at CITY
request will be available at VENDOR'S then current rates (for similar agencies and similar
services). Trainers shall be experienced and knowledgeable in the specific VENDOR
Application Software they are teaching and familiar with the procedures in similar
VENDOR environments to the CITY. Furthermore, VENDOR shall provide a
comprehensive course outline for each training session at least two weeks prior to the start
of the session showing the course outline, who should attend, expected outcomes. In
addition, CITY may request modifications or enhancements to the specific course outlines
up to one week prior to the start of a session pursuant to the related Business Process tasks
associated with the Application Software. VENDOR will make reasonable effort to
accommodate such changes. VENDOR will provide necessary training materials and have
session outlines and agendas for all training sessions, provided to CITY at least five days in
advance of the scheduled sessions. VENDOR will provide each student with training
manuals specific to the courses offered.
CITY may request a replacement trainer if, in the opinion of CITY there is evidence that
the trainer initially scheduled has been ineffective in conducting specific training sessions.
If VENDOR has been notified that a particular training session was ineffective because of
the qualifications or techniques of the trainer and uses the same trainer in a subsequent
session which also turns out to be ineffective, CITY will be entitled to withhold payment
for the subsequent session until a makeup session with a qualified trainer can be completed.
The training dates may be modified only by mutual agreement after the schedule is
developed of the CITY and VENDOR. In the event that the CITY cancels scheduled
training dates (excluding events beyond CITY's reasonable control), with less than two
weeks notice to VENDOR, VENDOR shall be compensated for all documented out-of-
pocket expenses incurred for said training.
F. IMPLEMENTATION SUPPORT SERVICES
The scope and sequence of the final implementation schedule will be determined by mutual
agreement at the project initiation kickoff meeting to be scheduled as soon as practical
following the execution of this Agreement. As the final implementation schedule is
completed and agreed to by the CITY and VENDOR, it becomes part of this Agreement.
G. OTHER THIRD -PARTY SOFTWARE
In addition to VENDOR developed and supplied application software, certain specific
software have been proposed that are supplied by third -party vendors acting as sub-
contractors to VENDOR. It is understood that the CITY may enter into an agreement for
the purchase of this software independently, but that the interface and integration of the
Page 9
City of Miami Municipal Software Corp.
MARCH, 29, 2004 APPLICATION SOFTWARE IMPLEMENTATION AGREEMENT
third party vendor software with VENDOR application software is essential to this
Agreement.
H. ACCESS TO PROGRAM SOURCE CODE
Vendor acknowledges that it has entered into an agreement (hereinafter called the "Escrow
Agreement") with Jones Emery Hargreaves Swan, Barristers and Solicitors, having an
office at Suite 1212 —1175 Douglas Street in the City of Victoria, in the Province of British
Columbia. A copy of the Escrow Agreement is attached hereto as Schedule D. Said
Escrow Agreement provides that a licensee may gain access to program source code for
purpose of maintaining and supporting their program license all as provided in the Escrow
Agreement.
VENDOR agrees that for so long as the Agreement is in effect it will deposit and
periodically update, at VENDOR's sole cost, a copy of the current version of the program
source code for all programs for which the licensee holds license as described in Schedule
A attached hereto in Escrow.
Vendor further agrees that for so long as this Agreement is in effect it will take no steps or
actions which would have the effect of modifying or eliminating the Escrow Agreement
without first having received written permission from the Licensee to do so.
SECTION VI: MODIFICATION OF SCOPE
Services specified in Change Control Document may be agreed to between the CITY and
VENDOR. Such services may include special studies; database conversion; data conversion;
implementation planning, and procedures; installation evaluation; technical and user training; and
specification preparation. CITY shall request such changes in writing on a VENDOR -developed,
CITY -approved form and shall specify:
1. Nature of work to be performed;
2. Date on which assignment is to begin;
3. Length of assignment, including due date and Cost; and
4. Individual who will coordinate for CITY and VENDOR.
VENDOR shall use its best efforts to provide a quotation for each service request and will provide
a written quote within ten (10) working days following receipt by the VENDOR of the CITY's
request. Acceptance by CITY of VENDOR quotation for each service request is subject to
compliance with CITY's then existing purchasing ordinances and policies. Upon acceptance by
CITY and VENDOR, such request shall be called "additional work assignment".
Each additional work assignment shall be governed by the terms and conditions of the Agreement,
the terms and conditions of the additional work assignment, and by such supplementary written
amendments of the Agreement or the work assignment as may be, from time to time, executed
between the parties.
Page 10
City of Miami Municipal Software Corp.
MARCH, 29, 2004 APPLICATION SOFTWARE IMPLEMENTATION AGREEMENT
In the event of a conflict between the terms and conditions of the Agreement and the terms and
conditions of any additional work assignment, the terms and conditions of the work assignment
shall govern.
No oral request for modification of services shall be binding on either party.
Further, the VENDOR agrees that its responsibilities under the Agreement will not be assigned or
licensed by VENDOR without the prior written consent of the CITY.
VENDOR is willing to provide modifications of service at the same rates outlined in the Final
Scope Document and Change Control Document included as Exhibits in this Agreement for a
period of two years from the date after the project goes live. After two years has lapsed, rates for
service will be based upon VENDOR then current rates (for similar agencies and similar services).
VENDOR shall have the right to decline to perform work associated with a service request if in
VENDOR'S sole opinion, VENDOR believes that the product resulting from said service request
will not result in an appropriate addition to the System or if VENDOR does not have sufficient
resources to properly complete the service request. If VENDOR elects not to perform work
contained in a service request, VENDOR will notify CITY within ten (10) working days.
SECTION VII: INSTALLATION, DELIVERY, AND TESTING
A. INSTALLATION AND DELIVERY
Delivery of the Licensed Application Software and test data shall be complete when
Application Software are loaded onto the CITY's hardware environment and is fully
operational for testing purposes and appropriately labeled media and documentation is
presented to the CITY as a complete system backup of the application software and data.
The documentation shall include, but is not limited to, instructions as to how to completely
re -install the contents of the media onto the hardware proposed. The initial delivery will
include a fully functional test database, not necessarily with CITY converted data, which
the CITY can use as a test -environment for experimentation and technical review.
B. ACCEPTANCE TESTING
Once the hardware and Application/Utility Software has been delivered, installed, and
configured, and VENDOR has converted any relevant CITY data and trained the
designated CITY resources to operate the basic components of the proposed Licensed
Application Software, the Testing Period can begin. During the Testing Period, CITY will
test all delivered software by executing any or all of the features contained in the feature
responses in Scope Document and Change Control Document.
During this time, VENDOR will provide access (at no additional charge) to a qualified
technician either on -site or via telephone and dial -in modem/Internet connection to assist
CITY in the testing of the applications. Failure by the CITY to report any failures within
30 business days of the start of Testing shall mean tacit acceptance and will be treated as if
the CITY has accepted the Application Software in its entirety.
Page 11
City of Miami Municipal Software Corp.
MARCH, 29, 2004 APPLICATION SOFTWARE IMPLEMENTATION AGREEMENT
If any part of the Application Software and integrated subsystems should fail (i,e. not
perform according to the function and feature of the Scope Document and Change Control
Document), CITY may designate that portion as a Project for delivery at a later date or
apply other remedies as specified in Section V, Acceptance Process.
C. RELIABILITY TESTING
Once the Licensed Application Software and Projects have passed the Acceptance Tests,
the implementation into productive use will begin. This includes training of all users and
final conversion of all relevant data. Once VENDOR has designated a system is available
for productive use (in writing), a 30-business day Reliability Test will begin. During this
period all of the data, workstations, software, and peripherals must be available to all
designated users at least 99.9 % of the time. This will be determined by summing across
all workstations the ratios calculated by dividing downtime by expected available time for
each workstation and limiting the downtime to no more than 0.001 (0.1%). For example, a
standard desktop workstation might be available for 10 hours during the day, and the
servers that CityView runs on would probably be required for 24 hours per day. If you had
50 workstations and 2 servers, the calculation over the 30-day Reliability Test would be:
(50 * 10 + 24 * 2) * .001 * 30 = 16.44 hours. Problems caused by the CITY's network or
computer hardware shall not be included.
Functional performance of the overall system will be measured, in a mutually agreed to
benchmark, such that during this period any user will experience the same or better
performance as demonstrated in VENDOR presentations.
SECTION VIII: ACCEPTANCE PROCESS
Acceptance of the development and implementation of the Application Software for the CITY will
be obtained throughout the scope of the project. Various stages of the process will be outlined in a
Scope Document developed by VENDOR in co-operation with the CITY.
A. ACCEPTANCE PROCEDURE:
1. VENDOR will provide the CITY with a Scope Document to be developed after initial
on -site review with the CITY. Such Scope Document will outline the Implementation
Services to be provided to complete further phases of the project. The Scope
Document must have the signature of the CITY's Project Manager and VENDOR prior
to any further work being commenced thereunder.
2. Upon acceptance of the Scope Document, VENDOR will complete the required tasks
and conduct an on -site user review of the prototyped application software. Resulting
from the on -site user review, VENDOR will provide the CITY with a Change Control
Document. Such Change Control Document will describe any and all changes to the
Implementation Services and whether such changes are Additional work assignment (as
described in Section 4 of the Final Proposal). Additional Work Assignment is to be
Page 12
'City of Miami Municipal Software Corp.
MARCH, 29, 2004 APPLICATION SOFTWARE IMPLEMENTATION AGREEMENT
costed by VENDOR and approved in writing by the CITY's Project Manager prior to
being started.
3. Upon acceptance of the Change Control Document, VENDOR will complete the
Implementation Services listed in the Change Control Document.
4. VENDOR will provide training to the CITY in accordance with the Scope Document.
5. VENDOR will provide the Application Software to the CITY (along with the Web
application, Data Conversion, Third Party Software integrations, and all technical and
user documentation relating to all Application Software and the Third Party software
integration.
6. Delivery of the Licensed Application Software and test data shall be complete when
Application Software (along with the Web application, Third Party Software
integrations) are loaded onto the CITY's hardware environment and is fully operational
for testing purposes and appropriately labeled media and documentation is presented to
the CITY as a complete system backup of the application software and data. The
documentation shall include, but is not limited to, instructions as to how to completely
re -install the contents of the media onto the hardware proposed. The initial delivery
will include a fully functional test database, not necessarily with CITY converted data,
which the CITY can use as a test -environment for experimentation and technical
review.
7. If any part of the Application Software and third party software integration test should
fail (i.e. not perform according to the Scope and Change Control Document(s), CITY
may require the following:
• VENDOR shall be giving the opportunity to extend the Acceptance testing period
for up to thirty (30) business days during which to bring such irregularities into
compliance. If after such time the performance irregularity is not remedied to the
CITY's sole satisfaction, the CITY may terminate the Agreement with a refund of
any License Fees paid to that point, or
• At the CITY's sole option, relegate the non -compliant component as a Project to be
completed at a mutually agreeable date. As a bond to ensure timely completion of a
Project so -designated, VENDOR shall provide a cashier's check for the non-
compliant, incomplete, unacceptable, or non -delivered items in the amount equal to
or greater than the value of the non -delivered items. This value of this bond shall
be determined as a reasonable pro rata portion of relative value of the overall
functionality of the module without the non -compliant feature(s). The maximum
bond value shall not exceed $75,000. Specifications for the delivery and
acceptance for each such item will be the same as the acceptance provisions stated
above and shall include appropriate due dates. CITY may then close the initial
Acceptance Period for items delivered and functioning in accordance with their
specifications, pay for accepted items only, and open new testing periods for non -
delivered items backed by guarantees of performance in the form of cashier's
checks. The CITY shall then retain the cashier's checks, until the items are
delivered and accepted and have passed a 30-day Reliability Test. As each item is
Page 13
City of Miami Municipal Software Corp.
MARCH, 29, 2004 APPLICATION SOFTWARE IMPLEMENTATION AGREEMENT
accepted, the cashier's check will be returned and payment for the item processed.
If the agreed upon delivery dates are not met, or the item fails the acceptance
provisions, the CITY may cash the cashier's check and find an alternate solution.
This procedure shall continue until all undelivered items are delivered and accepted
or all cashiers' checks returned or retained. Final Reliability Testing will not be
complete until all such Projects are delivered and accepted by the CITY.
• The CITY shall have the right to terminate the Agreement, upon written notice
effective immediately, at any time during the Acceptance period.
• In the event the VENDOR is rejected during the Acceptance period, the CITY will
agree to pay only those delivered and accepted phase of the project cost as specified
in the payment schedule.
8. VENDOR will submit a signed letter of Completion to the CITY detailing and
certifying that VENDOR has delivered and configured the Application Software
proposed with converted CITY data and that the Application Software performs at a
functional level consistent with what was documented in the Scope Document, Change
Control Document and completion of each phase of the project comprising the
Implementation Services. The letter must have the signature of the CITY's Project
Manager and VENDOR and will provide for acceptance by the CITY of completion of
each phase.
9. VENDOR shall not be authorized to perform any Implementation Services relating to
any subsequent phase of the project, and shall not be entitled to any payment therefore,
until such time as the CITY confirms and accepts VENDOR'S completion of the then -
current phase of the project.
B. PAYMENT SCHEDULE
Payment will be authorized and processed by the CITY according to the Payment Schedule
which is attached hereto and incorporated into this Agreement.
1. Reflective of a need to meet a staged requirement that the CITY has identified for the
licensing of their software products, and in consideration of the discounts and other
terms and conditions contained within this Agreement, VENDOR agrees to waive its
standard "full initial payment" condition with the following licensing arrangement:
• On or by [Agreement Date], the CITY will issue a purchase order for 10 licenses of
CityView at a price of $82,894(32% of the license total);
• On or by [Agreement Date plus 1 month], the CITY will purchase an additional 15
licenses of CityView along with the related Web and third -party components at a
price of $106,207 (41% of the license total);
• On or by [Agreement Date plus 2 months], the City will purchase the remaining
CityView licensing less a holdback of 10% at a price of $44,099 (17% of the
license total); and,
• The 10% holdback on licensing costs ($25,843) will be paid upon successful
completion of the project, not to exceed 12 consecutive months of productive use.
Page 14
City of Miami
MARCH, 29, 2004
Municipal Software Corp,
APPLICATION SOFTWARE IMPLEMENTATION AGREEMENT
2. Annual Software Maintenance fee will be invoiced annually and due on the anniversary
date commencing one (1) year from the date of this Agreement. This is not dependent
on project go -live.
3. Subject Matter Expert training fee will be invoiced upon successful completion of the
training.
4. Infrastructure Review and Recommendations fee will be invoiced upon CITY receipts
of the detailed Infrastructure Review Document.
5. Data Collection and Project Scope Document fee will be invoiced upon CITY receipts
and approval of the detailed Scope Document.
6. Form/Report Prototype fee and User Review fee will be pay for as follows:
• 20 % upon CITY receipts and approval of the Scope Document;
• 20 % upon CITY receipts of the Prototype Application Software;
• 10 % upon CITY receipts and approval of Change Control Document;
• 10 % upon successful deployment of Web applications;
• 10 % upon successful completion of all third party software integration;
• 10 % upon successful completion of the data conversion;
• 10 % upon successful completion of the Reliability Test by the CITY;
• 10 % upon successful go live.
7. Upon completion of the designated tasks and presentation to the CITY of an itemized
invoice showing the specific tasks completed and the resources involved in each.
8. Installation services and training will be invoiced upon successful completion of the
designated tasks and presentation to the CITY of an itemized invoice showing the
specific tasks completed and the resources involved in each.
SECTION IX: APPLICABLE TAXES
Taxes based upon net income or any other tax normally paid by VENDOR shall be the sole
responsibility of the VENDOR. The onus is on the CITY to self assess any sales taxes on
the Licenses and services identified in this Agreement and to remit on their own behalf to
the appropriate taxing jurisdiction. Taxes based upon net income or any other tax normally
paid by VENDOR shall be the sole responsibility of the VENDOR.
SECTION X: WARRANTY OF PERFORMANCE
A. COMPLIANCE WITH STATE AND FEDERAL AUDIT REQUIREMENTS
As long as CITY maintains continuous support for the Application Software included
herein, VENDOR shall ensure that all application software will comply with any and all
then current State and Federal audit requirements, such that CITY will not be liable for
program flaws which may violate any such requirements.
B. WARRANTY OF PERFORMANCE
As long as CITY maintains continuous support for the Application Software included
herein, VENDOR shall warrant for a period equal to the term of the Agreement,
Page 15
City of Miami Municipal Software Corp.
MARCH, 29, 2004 APPLICATION SOFTWARE IMPLEMENTATION AGREEMENT
commencing with the CITY's acceptance of the Licensed Application Software, that the
Licensed Application Software will perform in accordance with its specifications as set
forth in the Licensed Materials, if properly used in the operating environment specified in
Scope Document and Change Control document. VENDOR warrants that all components
are interoperable and the configuration is complete and suitable for the purpose specified
by the CITY in the Scope and Change Control Documents. VENDOR"S warranty of
performance shall be based on the specifications, terms and conditions contained in the
Agreement as a whole, including Pricing Proposal, Scope Document, Change Control
Document and the RTM.
C. LIQUIDATED DAMAGES
Time is of the essence in the Agreement. It is the understanding of the parties hereto that
because damages from delay are difficult, if not impossible, to predict in Application
Software installations, VENDOR agrees to pay the CITY five hundred dollars ($500.00)
per working day as reasonable charges for each working day that the Systems are not
operational sixty (60) calendar days after the specified dates in the Project Schedule (to be
mutually agreed), in the event that the delays are primarily caused by the actions or
inactions of the VENDOR. In the event that the delays are primarily caused by the actions
or inactions of the CITY, the CITY agrees to pay the VENDOR according to the same
terms and conditions. This amount shall apply to all reliability/go live due dates
established in the final Agreement unless waived by the CITY at its sole option in the event
that the VENDOR is the primary cause of delay, or waived by the VENDOR in the event
that the CITY is the primary cause of delay. The Project Schedule (to be mutually agreed)
may be modified only by mutual agreement of the CITY and VENDOR. In no event shall
the total damages exceed $25,000.
CITY and VENDOR are not responsible for failure to fulfill their obligation under the
Agreement due to causes beyond their reasonable control without the fault or negligence of
such party. In the event that failure to meet the established deadline(s) is outside the
control of both parties, the deadline(s) will be extended to mutually agreeable date(s) as
soon as possible. Such dates shall be attached, as amendment(s), to the final Agreement.
CITY and VENDOR shall mutually and reasonably agree on which causes are out of the
VENDOR's control.
In the event that the VENDOR is the primary cause of delay, liquidated damages may be
deducted from unpaid Fees as identified. If delays cause the Liquidated Damages period to
begin, the daily amount shall accrue and accumulate for the period of time required for
VENDOR to deliver and install remedies to the non-functioning Application Systems. At
this point, the Acceptance procedures defined herein will resume. In lieu of liquidated
damages, at the CITY's sole option, VENDOR may provide Project Bonds or cashier's
checks for each of the non -compliant, incomplete, unacceptable, or non -delivered items,
with appropriate specifications and due dates. CITY may then close the initial testing and
acceptance period for items delivered and functioning in accordance with their
specifications, pay for accepted items only, and open new testing periods for non -delivered
items backed by Project Bonds. CITY may then retain the Project Bond if the agreed upon
delivery dates are not met. Should VENDOR meet the delivery dates, CITY will test the
Page 16
City of Miami Municipal Software Corp.
MARCH, 29, 2004 APPLICATION SOFTWARE IMPLEMENTATION AGREEMENT
delivered items for another thirty (30) calendar days and accept these items if they are
compliant with their specifications and return the Project Bond for those items and pay the
agreed upon price. This procedure can continue until all Project bonds are satisfied.
In the event that the CITY is the primary cause of delay, the daily amount shall accrue and
accumulate for the period of time required for CITY to provide the necessary remedy. At
this point, an invoice will be issued to the CITY for the period of delay, and VENDOR and
CITY will agree to a mutually acceptable revised timetable.
D. CORRECTION OF ERRORS UNDER THE WARRANTY
At no charge to the CITY, VENDOR will promptly correct technical errors or in the
Licensed Application Software according to the terms of this Agreement so that the
Licensed Application Software will perform as described in the Scope Document, Change
Control Document and VENDOR's RFP response proposal.
E. ORAL REPRESENTATIONS
No CITY or VENDOR employee has the authority to bind either party to any oral
representation or warranty.
F. PROGRESS REPORTS
VENDOR will design a progress report form that itemizes the activities accomplished to
date, the activities planned and any problems which have occurred or are anticipated from
the point of Agreement signing until Final Acceptance. The forms' design and adequacy
will be subject to CITY approval. Progress reports will be prepared bi-weekly prior to
Acceptance and weekly thereafter by VENDOR and either mailed or e-mailed to the
CITY's Project Manager. Progress reports will be discontinued when the CITY, in its sole
judgment, deems the project to be complete and in conformance with the Scope Document
and VENDOR's Proposal and any subsequently agreed upon necessary modifications, and
deems VENDOR's commitments to be completed.
G. TERMINATION
VENDOR shall have the right to terminate this Agreement if CITY fails to pay charges due
within forty-five (45) days of notice and demand. VENDOR shall thereafter reinstate
services under this Agreement only upon payment of all past due charges plus any
additional late fees (as defined as 1 % per month on uncontested invoices). City shall have
the right to terminate should VENDOR's product fail to perform as represented and if said
failure(s) are not corrected within reasonable period as determined by CITY.
In the event VENDOR ceases to provide maintenance and support for the Licensed
Application Software (including any VENDOR -supplied updates) for reasons other than
CITY's failure to pay maintenance fees, a current copy of the Source Code as defined in
Section V, clause H with complete system documentation will be provided to CITY in
order to ensure continued maintenance.
Page 17
City of Miami Municipal Software Corp.
MARCH, 29, 2004 APPLICATION SOFTWARE IMPLEMENTATION AGREEMENT
SESSION XI: LIABILITY, INDEMNIFICATION AND DEFAULT
A. LIABILITY, INDEMNIFICATION AND DEFAULT
CITY shall in no event be liable to VENDOR or other person claiming damages as a result
of the CITY's use of the Licensed Application Software and Materials in conformity of this
Agreement, whether direct or indirect, special or general, consequential, or incidental or
arising from loss of profits; provided that this provision shall not apply to any claim,
demand, loss or action alleging that any modifications made by Licensee to the Licensed
Application Software and Materials infringe any third -party rights in the United States
respecting copyright, trade secret, or patent.
VENDOR shall indemnify, defend, and hold harmless from any demands, claims or suits
by a third party for loss, damages, expenses, liability, legal costs, and attorney's fees arising
out of allegations that the CITY's use of the Licensed Application Software and Materials
in conformity with this Agreement infringe any third -party rights in the United States
respecting copyright, trade secret, or patent.
After the successful completion of the acceptance period, any material failure by CITY or
VENDOR to comply with any term or condition under this Agreement shall entitle the
other party to give the party in default written notice requiring it to make good such
default. Failure to make good such notified default within thirty (30) calendar days of such
notice shall constitute breach of Agreement by the defaulting party and grounds for
termination of this Agreement.
B. BANKRUPTCY/SUPPORT CESSATION
The term "default" as used in this Agreement shall include the institution of proceedings by
or against VENDOR under federal or state bankruptcy laws and assignment or receivership
for the benefit of creditors. CITY rights to a complete and documented copy of all related
Source Code corresponding to the then current released version of the System/Utility
Software (for internal use and not for resale) shall precede any bankruptcy proceedings and
stand before any trustee's claims for the benefit of creditors. In the event that VENDOR
ceases to provide support for the System/Utility Software for reasons other than CITY's
failure to pay maintenance fees, the CITY shall have the same rights as if VENDOR had
declared bankruptcy.
C. INSURANCE
VENDOR, at its own cost and expense, shall purchase and maintain during the life of this
Agreement a comprehensive liability policy that shall protect VENDOR from claims for
property damage and injuries to persons, including accidental death, and name the CITY as
an additional insured under said policy in not less than the following amounts:
• General Liability including personal injury and property damage in the amount of
S1,000,000.
Page 18
• City of Miami
MARCH, 29, 2004
Municipal Software Corp.
APPLICATION SOFTWARE IMPLEMENTATION AGREEMENT
• Automobile Liability, all automobiles, in the amount of $1,000,000 for combined
single limit.
In addition, CITY shall be named as additional insured on such policies and shall be
notified by the insurance carrier of any change in or cancellation of coverage. VENDOR
further agrees during the life of this Agreement to maintain, at VENDOR expense, all
necessary insurance for its employees, including, but not limited to, Workman's
Compensation, disability, and unemployment insurance.
VENDOR shall furnish a certificate of insurance countersigned by an authorized agent of
the insurance carrier on a form of the insurance carrier setting forth the general provisions
of the insurance coverage. The countersigned certificate shall name the CITY as an
additional insured under the policy. The certificate shall contain a statement of obligation
on the part of the insurance carrier to notify CITY of any material change, cancellation or
termination of the coverage at least thirty (30) calendar clays in advance of the effective
date of any such material change. The certificate shall be furnished by VENDOR to CITY
prior to execution of this Agreement by CITY.
D. LIMITATION OF LIABILITY
VENDOR's liability for direct damages to CITY or others resulting from the performance
of Services under this Agreement shall not exceed the amount of the total of Licensed
Application Software and Materials charges paid to VENDOR under this Agreement and
all related agreements, and the total fees paid for training or other related payments paid to
VENDOR.
SESSION XII: GENERAL PROVISIONS
A. ASSIGNMENT
This Agreement may be assigned by VENDOR to another person or organization that
acquires all or substantially all of the assets of VENDOR as long as all contractual
provisions and responsibilities are assumed by the acquiring person or organization and the
CITY's approval is obtained which will not be unreasonably withheld. Any other assign-
ment by VENDOR shall be made only with the prior written consent of CITY which
consent shall not be unreasonably withheld provided that in the event of such assignment
the proposed assignee has agreed to be fully responsible for VENDOR obligations under
this Agreement.
B. GOVERNING LAW
This Agreement shall be governed by and construed in accordance with the laws of the
state of Florida and any and all disputes or legal actions shall be venued in Miami -Dade
County or the nearest jurisdiction to the City of Miami.
Page 19
City of Miami
MARCH, 29, 2004
Municipal Software Corp.
APPLICATION SOFTWARE IMPLEMENTATION AGREEMENT
C. COSTS AND ATTORNEYS FEES
Attorney fees in an amount not exceeding $85 per hour per attorney, and in total amount
not exceeding $5,000, shall be recoverable as costs (by the filing of a cost bill) by the
prevailing party in any action or actions to enforce the provisions of this Agreement. The
above $5,000 limit is the total of attorneys fees recoverable whether in the trial court,
appellate court, alternative dispute resolution processes, including but not limited to
conciliation, mediation, and arbitration, or otherwise, and regardless of the number of
attorneys, trials, appeals, or actions. It is the intent of this Agreement that neither party
shall have to pay the other more than $5,000 for attorney's fees arising out of an action, or
actions to enforce the provisions of this Agreement.
D. MEDIATION
Should any dispute arise out of this Agreement, any party may request that it be submitted
to mediation. The parties shall meet in mediation within 30 days of a request. The
mediator shall be agreed to by the mediating parties; in the absence of an agreement, the
parties shall each submit one name from mediators listed by either the American
Arbitration Association, the Florida Dispute Resolution Center, or other agreed -upon
service. The mediator shall be selected by a "blindfolded" process.
The cost of mediation shall be borne equally by the parties. Neither party shall be deemed
the prevailing party. No party shall be permitted to file a legal action without first meeting
in mediation and making a good faith attempt to reach a mediated settlement. The
mediation process, once commenced by a meeting with the mediator, shall last until an
agreement is reached by the parties but not more than 60 days, unless the maximum time is
extended by the parties.
E. ARBITRATION
After mediation above, and upon agreement of the parties, any dispute or claim arising out
of or relating to this Agreement may be settled by arbitration in accordance with the
Construction Industry Rules of the American Arbitration Association, and judgment upon
the award rendered by the arbitrators may be entered in any court having jurisdiction
thereof. The costs of arbitration shall be borne equally by the parties.
F. ENTIRE AGREEMENT/AMENDMENTS
This Agreement constitutes the entire understanding of the parties with respect to the
matter contained herein. There are no promises, covenants or undertakings other than those
expressly set forth herein.
This Agreement may not be amended except by writing signed by authorized
representatives of CITY and VENDOR and approved by the CITY's Manager.
If any of the provisions of the Agreement are declared to be invalid, such provisions shall
be severed from the Agreement and the other provisions hereof shall remain in full force
and effect.
Page 20
JVV L 11.11Vtaa
iXVUG1 L DG1ll1GLL
City of Miami Municipal Software Corp.
MARCH, 29, 2004 APPLICATION SOFTWARE IMPLEMENTATION AGREEMENT
G. CONSTRUCTION
A term or condition of the Agreement can be waived only by written consent of both
parties.
Title and paragraph headings contained in the Agreement are for convenient reference and
do not constitute part of the Agreement and shall not affect the interpretation of the
Agreement.
This Agreement shall be binding upon and inure to the benefit of the parties to the
Agreement and their respective successors and assigns.
H. SERVICE OF NOTICE
Any notice required or permitted to be sent under the Agreement shall be delivered by hand
or mailed by registered mail, return receipt requested, to the addresses of the parties first set
forth below.
VENDOR: Municipal Software Corporation
Robert Bennett, President and CEO
4464 Markham Street, Suite 1101
Victoria, BC
V8Z 7X8
CITY: City of Miami
Joe Arriola, City Manager
Miami Riverside Center - 444 S.W. 2nd Ave,
Miami, FL 33130
SIGNATURES:
IN WITNESS WHEREOF, the parties have executed this Agreement as of the
day, month and year first above written.
CITY OF MIAMI Municipal Software Corporation
Joe Arriola
City Manager
Robert Bennett
President and CEO
Page 21
City of Miami
MARCH, 29, 2004
Municipal Software Corp.
APPLICATION SOFTWARE IMPLEMENTATION AGREEMENT
ATTEST:
Priscilla A. Thompson
City Clerk
APPROVED AS TO FORM: APPROVED AS TO INSURANCE
CORRECTNESS:
Alejandro Vilarello Dania Carrillo
City Attorney Risk Management Administrator
Page 22
RTM
htb(+FC
Actex
Code Enforcement Requirement Traceability Matrix
March 24, 2004
Prepared by: Christie Mory and Reviewed by Conrad Salazar
Response prepared by: Municipal Software Corporation
Overview:
Code Enforcement needs a system to replace their existing method of entering, tracking and closing violations in the current
Complaint Tracking System. Detailed program activities were documented in anticipation of use with another vendor application.
This documentation is provided as an attachment to this Code Enforcement RTM. In Phase I implementation of Code Enforcement
the following capabilities are needed:
• Enter violation information and create work orders_ Information can come directly into the Code Enforcement department or
be handled at 13 NET offices by the NET clerks
• Work orders become a REQUEST and are entered by Inspectors and NET clerks
• The inspector will need to schedule and inspect the violation and determine whether it should become a CASE or remain a
REQUEST and close.
• The inspector will record the results of the inspection and if a CASE is opened then various predefined activities occur which
include notices, letters and a series of time events
• Inspection results need to be logged, and rescheduled
• Tickets, letters, notices need to be output by the system.
Note: It is important to note that where we have responded that the item is configurable as required, there is no custom
source code programming. Configuration is completed using the tools provided in CityView.
1
1.1
The System shall allow the Code Enforcers
and NET clerks to create a new or modify
and existing form or template to log the
Yes
CityView 82.1
Configurable as required
and proposed.
included as
proposed
1.2
The System shall allow the users to define
Yes
CityView 8.2.1
Configurable as required
and proposed.
included as
proposed
1.3
The System shall be able to track and
register initial complaints to include but not
be limited to:
Date complaint received _
Date inspector assigned
First inspection Date
Request Type: REQUEST or CASE
Violation location
Yes
CityView 8.2.1
Configurable as required
and proposed.
included as
proposed
1.4
The System shall be able to assign a unique
number of each complaint received and the
Yes
CityView 82.1
Configurable as required
and proposed.
included as
proposed
1.5
The System shall be able to provide violation
Yes
CityView 8.2.1
Configurable as required
and proposed.
included as
proposed
1.6
The System shall be able to conduct inquiry
to include, but not limited to open cases from
Building and Zoning in one screen. (ie.
Yes
CityView 8.2.1
Configurable as required
and proposed.
included as
proposed
1.7
The System shall allow user access by
address or folio number using a GIS parcel
interface which displays graphical
representation of the property
Yes
CityView 8.2.1
Configurable as required
and proposed.
included as
proposed
1.8
The System shall be capable of determining
if there is a duplicate complaint on a
particular property
Yes
CityView 8.2.1
A user must discern
whether a 2nd complaint
is a duplicate or a
different complaint.
included as
proposed
2
1.9
2.1
If there is not a duplicate the system shall
prompt the user if they want to add a new
case.
The System must be able to automatically
determine the priority based on the type of
case reported.
Yes
Yes
CityView 8.2.1
Chew 8.2.1
Configurable as required
and proposed.
Configurable as required
and proposed_
included as
proposed
induded as
proposed
2.2
The System shall be capable of entering the
complaint as a REQUEST. then changing
the complaint type to a CASE if the inspector
determines that it is a CASE after an initial
'
Yes
CityView 8.2.1
Configurable as required
and proposed.
included as
proposed
.. Ion.
3.1
The System shall allow one or more
inspectors to be automatically assigned
based on geographic area or specific type of
case.
Yes
CityView 8.2.1
Configurable as required
and proposed.
induded as
proposed
3.2
The System shall be able to automatically
set up inspection schedule and tickler for
inspectors assigned
Yes
CityView 8.2.1
Configurable as required
and proposed.
included as
proposed
3.3
The System shall allow an inspectors case
load to remain with him, even though he may
move to another territory.
Yes
CityView 8.2.1
Configurable as required
and proposed.
Inspectors can be
assigned work based on
their territory at the time
of the assignment, and
transferring of a case to
another inspector after
he transfers would be a
supervisors decision.
So by default, the case
would stay with the
'•
included as
proposed
o final ins.:-.,. .
4.1
The System shall allow inspectors to access
the system for property history and code
information history via their handheld device,
Yes
CityView 8.2.1
Configurable as required
and proposed, assuming
the standard CityView
mini -browser interface.
included as
proposed
4.2
The System shall allow the inspector to enter
inspection results, comments and tag
property for violation via their handheld
device, laptop or ipad.
Yes
CityView 8.2.1
Configurable as required
and proposed, assuming
the standard Chew
mini -browser interface. .
included as
proposed
4.3
The System must be able to provide
Yes
CityView 8.2.1
Configurable as required
included as
3
4.4
4.5
4.6
4.7
4.8
r 4.9
4.10
4.11
4.12
5.1
5.2
5.3
5.4
attachment of photos, images of final plat
drawings, documents to parcel database
records.
The System shall track the dates of
inspections.
The System shall provide an area of
inspector comments and tie to the case
number, notices sent and violation location.
The System shall be able to automate the
naming of images using a file name and
picture sequence structures. Example: If
case 3455 the picture shall be named 3455-1
The System shall store the images on a
database not on the work station.
The System shall interface with Motorola 311
system to include receiving and sending
automated information from Code
Enforcement: Future: January 2005
The System shall be capable of allowing
inspectors to open rages that have been
previously carried over from previously
assigned areas the inspector has worked.
The System shall be capable of requesting
and/or assigning to an individual inspector
cases that are of same activity types.
The System must provide attachment of
photos, images of final plat drawings,
documents to parcel database records.
The System must provide for multiple street
name aliases and related valid street
numbers.
The System shall automatically generate
letters and notices.
The System shall be able to allow images to
be imbedded into letters and documents.
The System shall be able to perform
calculations and then print the amount on
letters and notices.
The System shall be able to track but not be
limited to:
Abatement fees
Yes
Yes
Yes
Yes
No
Yes
Yes
Yes
Yes
Yes
Yes
Yes
CityView 8.2.1
CityView 8.2.1
CityView 8.2.1
CityView 8.2.1
CityView 8.2.1
CityView 8.2.1
CityView 8.2.1
CityView 8.2.1
CityView 8.2.1
CityView 8.2.1
CityView 8.2.1
CityView 8.2.1
and proposed.
Configurable as required
and proposed.
Configurable as required
and proposed.
Configurable as required
and proposed, using
CityVievws built-in auto -
number -sequencing
function.
The images are stored
on a file server, under
the control of the
CityView Server.
Quoted as a separate
line item.
Configurable as required
and proposed.
Configurable as required
and proposed.
Configurable as required
and proposed.
Configurable as required
and proposed.
Configurable as required
and proposed.
Configurable as required
and proposed.
Configurable as required
and proposed.
proposed
included as
proposed
included as
proposed
included as
proposed
included as
Proposed
included as
proposed
included as
proposed
included as
proposed
included as
proposed
included as
proposed
included as
proposed
included as
proposed
Yes
CityView 8.2.1
Configurable as required
and proposed.
included as
proposed
4
5.5
5.6
5.7
5.8
5.9
5.10
5.11
5.12
5.13
5.14
Abatement fee due dates
Fee due dates
Administration fees
The System shalt be able to track multiple
abatement, violation and notices by issues
dates, amounts and dates letters sent.
The System shall provide tickler for
inspection due dates and notification if
deadlines have passed.
The System shall be able to automatically
generate the letter based on user defined
rules.
The System shall be able to track the dates,
status and history of all inspection by
property address.
Yes
Yes
Yes
Chew 8.2.1
CityView 8.2.1
CityView 8.2.1
Configurable as required
and proposed.
Configurable as required
and proposed. A user
must dick a form button
to invoke this query.
Alternatively reports "to
do lists' can be used, if
Chew s Outlook
functionality is being
used, reminders and
notifications are a
function of Outlook
Configurable as required
and proposed.
included as
proposed
included as
proposed
included as
proposed
The System must be able to calculate related
fees based on the fee table or schedule
The System must be able to automatically
generate warning or citation letters based on
user defined roles.
The System must be able to track multiple
citation occurrences.
The System must allow manual entry of the
citation fees.
The System shall provide tracking capability
to track the dates and CIC hearing
comments and decisions.
The System must provide the capability to
track the date of the meeting, agenda and
comments.
Yes
Yes
Yes
CityVew 8.2.1
CityView 8.2.1
CityVew 8.2.1
Configurable as required
and proposed.
Configurable as required
and proposed.
Configurable as required
and proposed.
included as
proposed
included as
proposed
included as
proposed
Yes
Yes
Yes
CityView 8.2.1
CityVew 8.2.1
CityVew 8.2.1
Configurable as required
and proposed.
Configurable as required
and proposed.
Configurable as required
and proposed.
included as
proposed
included as
proposed
included as
proposed
Yes
Cityvew 8.2.1
Configurable as required
and proposed.
included as
proposed
5
LUCS Requirements Traceability Matrix
March 2004
Responses prepared by: Municipal Software Corporation
Note: It is important to note that where we have responded that the item is configurable as required, there is no custom source code
programming. Configuration is completed using the tools provided in CityView.
1.1
1.2
1.3
1.5
1.6
1.9
1.10
The System shall allow user access by
address or folio number using a GIS parcel
zoning interface which displays graphical
re • resentation of the . ro .
The System shall validated the address or
folio number u.on ent
Deleted: Process Re. uirement
If the address or folio exists system shall
return Summary Details about the property in
include folio number, property address,
property owner, property owner mailing
address street, : , state, and . ostal zi . .
Deleted: Du • ficate to 1.1
If the address or folio exists the system shall
retum Zoning Information which contains
primary zone district designation and existing
land use.
Deleted: Arnbi • uous
tf the address or folio exists the system shall
display the primary zone district designation
and when selected, the specified primary
zone districts "Use" allowed which may be up
to X number of Uses.
If the address or folio does not exist the
System shall retum a list of five properties
that are in close proximity to the address
entered.
The System shall show the fire zones and
districts from a GIS layer for a particular
TO . - address.
Deleted: Du • Iicate of 1.9
Yes
Yes
Yes
Yes
Yes
No
Yes
CityView v8.2.1
CityView v8.2.1
CityView v8.2.1
CityView v8.2.1
CityView v8.2.1
CityView v8.2.1
CityView v8.2.1
Configurable as required, to suit your
specific GIS needs.
Configurable as required and proposed.
Configurable as required and proposed.
Confi. urabie as re • uired and • ro • osed.
Configurable as required and proposed.
The number of Uses is configurable as
required. There are no system -
imposed limits to this number.
This is normally a 2-step process. (1)
Find an exact match, else (2) Find
proximity matches. If the expectation is
that this would be 2 steps, then we do
su • • ort this r- • uirement out of the box.
Configurable as required and proposed.
provided fire zones are a GIS layer.
1
1.12
The System shall be able to provide a history
of CU use and existing code enforcement
cases (violations/liens).
Yes
CityView v8.2.1
Configurable as required and proposed.
Since CE would be implemented so
shortly after LUCS, we would not
interface to your existing CE system.
Interfacing to our internal CE module is
supported `out -of -the -box"_ It is
assumed that the CE implementation
would include conversion of historical
data.
1.13
The. System shall not allow any editing while
making inquires on address or folio land
Yes
CityView v82.1
Configurable as required and proposed,
by user privileges, or by a query form
distinct from the update form.
1.14
The System shall show the flood zone from a
GIS layer for a particular property address.
Yes
CityView v8.2.1
Configurable as required and proposed,
provided that Hood zones are a GIS
layer.
1.15
The System shall show the voting districts
from a GIS layer for reporting purposes.
Yes
CityView v8.2.1
Configurable as required and proposed,
provided that voting districts are a GIS
layer.
1.16
2.1
The System shall have the capability to
recognize address abbreviations or address
similarities. For example: Street versus St.
The System shall allow the Clerk
to pre -populate the CU application
with data from the GIS interface to
eliminate manual data entry.
Information includes the following:
Property Owner Name
Property Owner Mailing
Address (street, city, state
and zip code)
Property Owner Telephone
(include area code)
Property Owner E-Mail
Property Owner Fax Number (optional)
Yes
Yes
CityView v8.2.1
CityView v8.2.1
Searches are typically based on
scrubbed data, configured to your
street -naming standards, with a
separate field for street -type. Users
typically qualify a street name with a
street -type selected from a drop -down
list box of valid street -types. Therefore,
this requirement is met in a different
wa than what is - . uested here.
Configurable as required and proposed.
2
2.2
The System shall allow the Clerk
to populate the CU application with
Property information from the GIS
interface to include the following:
Property Folio Number
Property Address (street, city,
state and zip code)
Zoning Designation
Other Designations
Net Area/Code Compliance
District (need fields)
Special Conditions
Special Permits
Yes
CityView v8.2.1
Configurable as required and proposed.
2.3
The System shall allow a new address to be
entered as long as it links to an existing
address or folio.
Yes
CityView v8.2.1
1t is recommended that new addresses
are downloaded from GIS, if that's the
master database. However, new
addresses can be entered as specified. •
2.4
The System shall query the clerk for a unit
number if none is entered; if there is no unit
number the system shall enforce the clerk to
enter "none" or some similar value.
Yes
CityView v8.2.1
Configurable as required and proposed.
2.5
Deleted: Duplicate to 1.10
2.6
The System shall have the capability of
recognizing address aliases.
Yes
CityView v8.2.1
Configurable as required and proposed.
The default can be set to "none", or can
be left blank and set to "must fill".
2.7
3.1
The System shall have the capability of
re•..nizin. multiple addresses . -r .. met.
The System shall provide a user interface to
select information from Zoning Compliancy
Use table-
Yes
Yes
CityView v8.2.1
CityView v8.2.1
Configurable as required and proposed.
Configurable as required and proposed.
3.2
The System shall allow the Zoning
Compliancy Use data to be created, edited
and deleted as well as the changes tracked.
Yes
CityView v8.2.1
Configurable as required and proposed.
3.3
The System shall populate the CU
application screen with the District Use
Type Use (USE) from the Zoning
Compliancy Use table.
Yes
CityView v8.2.1
Configurable as required and proposed.
3.4
The System shall allow one District Use
Type Use (USE) from the Zoning
Compliancy Use table to be entered for each
CU entered into the System.
Yes
CityView v8.2.1
Configurable as required and proposed.
3.5
The System shall assign a unique USE
IDENTIFIER number for each CU entered
into the System.
Yes
CityView v8.2.1
3.6
The System shall allow the Clerk to select
CONDITIONS from the Zoning Compliancy
Use table with a text area to enter reference
information.
Yes
CityView v8.2.1
Configurable as required and proposed.
3.7
The System shall allow the Clerk to select
Yes
CityView v8.2.1
Configurable as required and proposed.
3
3.8
4.1
4.2
4.3
4.4
4.5
4.6
4.7
4.8
4.9
4.10
FEATURES of the CU from the Zoning
Compliancy Use table.
Moved to 4.12
Deleted: Duplicate of 12
Moved to 1.16
Deleted
The System shall generate the current DATE
of application.
Moved: To 9.16 non-functional rqmt.
Deleted: Redundant to 6.3 and 6.5
The System shall allow the Clerk
to enter the CU APPLICATION
TYPE to include:
New Use
Existing Use (New Ownership,
Expansion, Modification)
Deleted: Ambiguous
The System shall display the
STATUS of the NEW CU
Application, otherwise the CU
record shall have one of the
following status on the record
depending on the workflow
Suspended (Critical Problem)
Pending (Class 1 or Class 2)
Approved (Final Approval)
Rejected (Inspections not ok)
Revoked (Legal problems)
In Process (Paid)
Expired (No action)
Deleted: Duplicate of 4.7
Yes
Yes
Yes
CityView v8.2.1
CityView v8.2.1
CityView v8.2.1
4
Configurable as required and proposed.
Configurable as required and proposed.
4.11
The System shall allow the Clerk
to enter the following information
from the Applicant for a new CU.
Registered Agent andlor
Applicant Name
Business Name
Business Address
Business Mailing Address
Applicant Telephone Number
Emergency Phone Number
Cell Phone Number
Applicant E-Mail Address
Applicant Facsimile Number )
Property Owner's Authorization Proof
(Y/N)
Square Footage
Units in Business
Seats in Business
Comments
Restrictions
Payment Exempt (yes/no)
Yes
CityView v82.1
Configurable as required and proposed.
4.12
The System shall have the capability of
searchin. for an existi • CU record.
Yes
CityView v8.2.1
Configurable as required and proposed.
5.1
The System shall allow a record to
be put into a pending state if an
applicant has to apply for a Class
1 or Class 2 Permit.
Yes
CityView v8.2.1
Configurable as required and proposed_
52
The System shall allow a Class 1
or Class 2 Permits be entered into
the system.
Yes
CityView v8.2.1
Configurable as required and proposed.
5
5.3
The System shall allow the Clerk
to enter the following information
about the Class 1 permit:
Application Type
Nature of Application
Applicant Name
Applicant Address
Contact Phone Number
Receipt Number (of CU?)
NET Area
Zoning Designation
Date Submitted
Address of Business
Square Footage
Fair market value
Proof of Certified Mail Receipts
(YIN)
Legal description of property
(YIN)
Site plan (Y/N)
Parking landscaping (YIN)
Yes
CityView v8.2.1
Configurable as required and proposed.
5.4
The System shall calculate the fee
s based on pre -established fee
fables for Class 1 and Class 2
Special Permits.
Yes
CityView v8.2.1
Configurable as required and proposed.
5.5
The System shall be capable of allowing the
Clerk to enter the amount and how payment
was received with cash, check or credit.
Yes
CityView v8.2.1
Configurable as required and proposed.
5.6
The System shall generate a hardcopy
receipt in the amount paid to be given to the
Applicant.
Yes
CityView v8.2.1
Configurable as required and proposed.
5.7
The System shall assign a unique number to
the documents (inspection package) and
print one hardcopy for attachment to the
package.
Yes
CityView v8.2.1
Configurable as required and proposed.
5.8
The System shall track the package unique
number as apart of the Class 1 or Class 2
Permit record.
Yes
CityView v8.2.1
Configurable as required and proposed.
5.9
The System shall have the
capability to allow the Service Aide
to schedule an inspection with
NET inspectors.
Yes
CityView v8.2.1
Configurable as required and proposed.
6
5.10
The System shall allow the
inspector to enter his inspection
results to include:
Name
Date of Inspection:
Results
Approved
Denied — Non Needed
Incomplete Submittal
Pending Zoning Review
Pending Net Review
Yes
CityView v8.2.1
Configurable as required and proposed.
5.11
The System shall send notification
to the Zoning Administrator of
Approval and Service Clerk (to
notify the Applicant)
Yes
CityView v8.2.1
Configurable as required and proposed.
5.12
The System shall allow the Zoning
Administrators to enter approval
and assign a Class 1 Special
Permit Number.
Yes
CityView v8.2.1
Configurable as required and proposed.
5.13
The System shall generate a
hardcopy Class 1 or Class 2
Yes
CityView v8.2.1
Configurable as required and proposed.
5.14
The System shall allow the Clerk
to enter whether a Hold Harmless
Affidavit with signed and notarized.
Yes
CityView v8.2.1
Configurable as required and proposed.
5.15
The System shall allow the Zoning
Inspector access to the Class 1
record to enter approval in the
Zoning section of the Building
Yes
CityView v8.2.1
Configurable as required and proposed.
5.16
The System shall allow the
Planning Department to record
final approval for Class 1 permits
Yes
CityView v82.1
Configurable as required and proposed.
5.17
The System shall permit the Class
II Coordinator to enter the Class 2
permit information.
Yes
CityView v8.2.1
Configurable as required and proposed.
5.18
The System shall calculate a
special fee for urban Development
or Historic Preservation Board
Yes
CityView v8.2.1
Configurable as required and proposed_
5.19
The System shall send notification
to the NET offices that the Class 2
Yes
CityView v8.2.1
Configurable as required and proposed.
5.20
The System shall allow the NET
Zoning inspector to record the
Yes
CityView v8.2.1
Configurable as required and proposed.
5.21
The System shalt send notification
to the Net Administrator the results
from the NET Zoning Inspector
review.
Yes
CityView v8.2.1
Configurable as required and proposed_
7
5.22
5.23
5.24
5.25
5.26
5.27
5.28
5.29
5.30
6.1
6.2
6.3
6.4
6.5
The System shall send notification
to the Class 11 Coordinator the
package is ready for review after
the NET Administrators review.
The System shall allow the
decision to be entered as either,
Approved, Denied, Issue Intended
Decision, or Final Decision with
reasons and required changes.
The System shall be capable of
determining when 15 days appeal
has expired if a Hold Harmless
Affidavit has been submitted or
Neighbors appeal.
The System shall be capable of
freezing a Class 2 permit while the
Appeal Process takesplace.
The System shall produce a final
Class 1 or 2 permit with an
effective date.
The System shall have the ability
to modify a Class 2 Special Permit
after its been issued.
Yes
Yes
Yes
Yes
Yes
CityView v8.2.1
CityView v8.2.1
CityView v8.2.1
CttyVew v8.2.1
CityView v8.2.1
Configurable as re
Configurable as r
Configurable as re
Configurable as re
Configurable as re
The System shall have the ability
to issue a modified Class 2 Special
Permit.
The System shall have the
following status: New, Modified
and Expired
Yes
Yes
CityView v8.2.1
CityView v8.2.1
Configurable as r
by user
Configurable as re
The System shall have the
capability to expire a Class 2
Special Permit after a pre -defined
eriod of time.
The System shall calculate the amount due
from the applicant based on fee schedules
determined by the City.
The System shall be capable of allowing the
Clerk to enter the amount and how payment
was received with cash, check or credit.
The System shall generate a hardcopy
receipt in the amount paid.
The System shall generate a hardcopy CU
application with all of the information entered
by the Clerk as well as a list of disciplines
that will need to inspect the property.
The System shall interface the financial
GEMS system.
Yes
Yes
Yes
Yes
Yes
No
Chew v8.2.1
CityView v8.2.1
CityView v8.2.1
CityView v8.2.1
CityView v8.2.1
CityView v8.2.1
CityView v8.2.1
Configurable as r
Configurable as re
Configurable as re
Configurable as re
Configurable as req
Configurable as req
8
A custom interface
we have included
the propo
quired and proposed.
quired and proposed.
quired and proposed.
luired and proposed.
luired and proposed.
quired, constrained
privileges.
luired and proposed.
luired and proposed.
luired and proposed.
uired and proposed.
uired and proposed.
uired and proposed.
uired and proposed.
must be written and
3 budget amount in
;al for this.
6.6
6.7
6.8
6.9
7.1
72
7.3
7.4
7.5
7.6
7.7
7.8
7.9
Yes
Yes
CityView v8.2.1
CityView v8.2.1
Configurable as required and proposed.
Configurable as required and proposed.
The System shall generate an inspection
notification to be sent to Building, Electrical,
Plumbing, Mechanical, Fire and Zoning
depending on the USE of the CU.
The System shall allow the system to change
the status to pending then after review
recalculate payment based on changes
found upon inspection. (ex: change in use,
characteristics, or square footage)
Moved to 8.6
The System shall generate a CU
application with information to be
filled out upon inspection to
include the following Fire
information
Fire Usage Code
Fire Property Class
Distribution Code
Night Inspection (Yes/No)
Structure (Yes/No)
Occupancy Load
Building (Fire) Protection
(1,2,3,4)
Corridor (I/E
The System shall have the capability to
schedule an inspection at the NET for the
inspectors at the Code Enforcement
department.
The System shall allow inspectors to track
and schedule inspections.
Deleted
Deleted: Redundant to 6.7
If an inspection fails and the problem is
critical, the System shall send email or report
notification to other disciplines not to inspect
until problem has been resolved and send
critical failure to Zoning to revoke or suspect
CU application until resolution.
Deleted: Redundant to 6.6
The System shall have the capability to allow
inspectors document their inspection results
in an automated manner.
The System shall allow only CU Records
with a "Paid" status to be scheduled an
inspection.
Yes
Yes
Yes
CityView v8.2.1
CityView v8.2.1
Configurable as required and proposed.
Configurable as required and proposed.
Configurable as required and proposed.
Yes
CityView v82.1
Configurable as required and proposed.
The System shall allow the CU Record to be
placed in an Approved state only when all
Yes
Yes
Yes
CityView v8.2.1
CityView v8.2.1
CityView v8.2.1
9
Configurable as required and proposed.
Configurable as required and proposed.
Configurable as required and proposed.
aF
:ct
of
ri
is
is
a
ie
of
sl
ie
Ir
It
0
rf
c
ip
itl
a
nri
a
d
it
fE
7.10
7.11
7.12
7.13
7.14
7.15
7.16
7.17
7.18
7.19
7.20
disciplines have completed and approved
inspections and ail fees are paid. The System shall allow Business Rules to be _
entered and applied to when an inspection
can be scheduled. For example: Fire
cannot perform inspection until 3 days after
CU application. Scheduling inspections too
early causes re -inspections.
The System shall have the capability to
periodically check for inspection status of in
process" and "not scheduled' and notify the
appropriate discipline the inspection needs to
occur.
The System shall have the capability to sort
a group of inspection notification by
discipline, and inspector assigned districts,
and assign a group of CUs for inspections.
The System shall send a email or report
notification to the inspector within that
discipline to schedule an inspection
Yes
Yes
CityView v8.2.1
CityView v8.2.1
Configurable as required and proposed.
Configurable as required and proposed.
The System shall have unlimited inspections
history records for each inspection discipline_
The System shall have for each inspection
record, the capability to allow the Inspectors
to add or modify Inspection Data to include,
Inspection Requested Date, Inspection
Performed Date, Time, Approval or
Disapproval, Reason, Conditions,
Restrictions, Comments, Initials, Results,
and Approval date.
The System shall have the capability to
reject a CU application and notify zoning to
review based on an inspection result that the
approved use is different from the use the
inspector saw.
The System shall allow the inspector to
update a CU record with Fire Usage Codes,
Property Class, square foot/units/seats,
distribution code, night inspection, shell,
building protection, corridor, occupancy load,
Fire Usage Code and Property Class
according to Fire FOL
Deleted: Redundant to 7.13
The System shall have the capability to send
email notifications of inspection requests as
a group by a specific time.
The System shall have the capability to
generate a report of inspection requests that
are sorted based on pre -defined supervisor
groups, districts or nets.
Yes
Yes
Yes
Yes
Yes
Yes
CityView v8.2.1
CityView v8.2.1
CityView v8.2.1
CityView v8.2.1
CityView v8.2.1
CityView v8.2.1
Configurable as required and proposed.
Configurable as required and proposed.
Configurable as required and proposed.
Configurable as required and proposed.
Configurable as required and proposed.
Configurable as required and proposed.
Yes
Yes
CityView v8.2.1
CityView v8.2.1
10
Configurable as required and proposed.
Configurable as required and proposed.
7.21
The System shall have the capability to
create an automatic re -inspection or referral
to another discipline.
Yes
CityView v8.2.1
•
Configurable according to your precise
business rules_
7.22
The System shall have the capability to
extend the period of time the re -inspection
must be completed for a particular set of
days (30-60-90).
Yes
CityView v8.2.1
Configurable as required and proposed.
723
The System shall allow the inspectors to
create a new inspection with and without
reschedutinq capabilities.
Yes
CityView v8.2.1
Configurable as required and proposed.
7.24
The System shall notify the Health
department of a pending inspection via email
and/or reporting.
Yes
CityView v8.2.1
Configurable as required and proposed.
7.25
The System shall provide the capability to
identify the source of the request to schedule
an inspection (phone, email, over counter
etc).
Yes
CityView v8.2.1
Configurable as required and proposed.
7.26
The System shall allow for inspections to be
cancelled.
Yes
CityView v8.2.1
Configurable as required and proposed.
7.27
Deleted: Redundant to 7.16
7.28
8.1
The System shall have inspection status to
be as follows_ Suspended, Pending, Hold,
Re'ected and • • • roved
The System shall send email notification to
the Zoning Administrator that the CU is
complete.
Yes
Yes
CityView v8.2.1
CityView v82.1
Configurable as required and proposed.
Configurable as required and proposed.
82
The System shall allow the Zoning
Administrator to enter an approval to the CU.
Yes
CityView v8.2.1
Configurable as required and proposed.
8.3
The System shall allow an approved CU
notification be sent to Zoning and Planning to
mail the CU or have picked up.
Yes
CityView v8.2.1
Configurable as required and proposed.
8.4
The System shall interface with ARCV
(Accounts Receivable) to place renewal
information into the system.
Yes
CityView v8.2.1
Configurable as required and proposed.
8.5
Deleted: Interface to ARPS wilt be manual
8.6
9.1
The System shall generate a CU Number
that contains the first two digits of the current
ear.
System shall provide the capability to
reverse an entry once entered.
Yes
Yes
CityView v8.2.1
CityView v82.1
Configurable as required and proposed.
Configurable as required and proposed,
constrained by audit trail and user
privileges.
9.2
The System shall have the capability to
expire a record based on a pre -determined
period of inactivity.
Yes
CityView v8.2.1
Configurable as required and proposed.
9.3
The System shall have the capability to be
able to re -activate a CU.
Yes
CityView v8.2.1
Configurable as required and proposed.
9.4
The System shall not allow a change to the
Yes 1
CityView v8.2.1
The audit trail for inspection results
11
9.5
9.6
9.7
9.8
9.9
9.10
9.11
9.12
9.13
9.14
9.15
9.16
9.17
9.18
9.19
9.20
history of the inspection results.
The System shall allow Supervisors to
change specific information in a record that
an inspector cannoL
System shall be compatible with MRC, NET
and Code Enforcement technical
infrastructure.
Deleted - Duplicate
Yes
CityView v82.1
A detailed Infrastructure
Review will be
conducted as part of the
proposal
The System shall have validation, error
messages and edits built into the system to
preserve the integrity of the data.
System shall provide reporting capabilities
System shall have error processing routines
if input is invalid or missing
System shall have a login screen and user
defined roles
System shall have required fields and
validations of values put into the system
System shall have pre -defined log off
capability if there is a period of no usage
time.
Deleted
Yes
Yes
Yes
CityView v8.2.1
CityView v8.2.1
CityView v8.2.1
Yes
Chew v8.2.1
Yes
Yes and No
CityView v8.2.1
CityView v8.2.1
System shall provide query capabilities
The System shall maintain a history of
"STATUS" changes, what and by whom.
The System shall be able to provide single
sign -on capability
The System shall be able to prevent un-
authorized access and update.
The System shall provide online help or
tutorial sessions
Yes
Yes
Yes
CityView v8.2.1
CityView v8.2.1
CityView v8.2.1
Yes
CityView v8.2.1
The System shall allow the Clerk to save the
incomplete application for later use within a
predefined period of time.
Yes and No
- Yes
CityView v8.2.1
p
H
CityView v8.2.1
12
listory is not alterable within CityView.
Configurable
Configurable
Configurable
Configurable
Cfigurable
created
;onfigurable as required and proposed,
constrained by user privileges.
as required and proposed.
onfigurable as required and
proposed.
onfigurabie as required and proposed.
as required and proposed.
onfigurable as required and proposed.
The default is 20 minutes for Web
Forms, configurable on the IIS. Not
supported on workstation.
as required and
proposed.
as required and proposed.
mfigurable as required and proposed.
on as required and proposed.
:ityview help files are supported — not
tutorials. The help files are not
customized to reflect your specific
business process; they only explain
how to use the generic CityView
rocess, however custom help can be
and attached to the CityView
elp options that reflect your business
processes.
mfigurable as required and proposed.