HomeMy WebLinkAbout2015-02-24; City Council; 21869; Agreement Geographic Information System Redesign ModificationCITY OF CARLSBAD - AGENDA BILL
AB# 21.869
DATE 2/24/15
DEPT. ASD/IT
APPROVAL OF AN AGREEMENT FOR $130,000 FOR
GEOGRAPHIC INFORMATION SYSTEM (GIS) DATABASE
REDESIGN AND MODIFICATION
DEPT. DIRECTOR QtA.
CITY ATTY
CITY MGR.
RECOMMENDED ACTION:
Adopt City Council Resolution No. 2015-048 approving the agreement with Environmental Systems
Research Institute, Inc. (Esri), a California Corporation, to convert the city's existing geographic
information system (GIS) database to an industry standard local government information model.
ITEM EXPLANATION:
Since 1991, the city has developed, maintained and utilized a collection of geographic data that reside in
a database for the city's GIS needs. Over time, this database has grown in size and complexity, but not in
its level of industry-standard organization. As the city moves to an integrated and enterprise-wide
information technology environment, the data stored in the GIS needs to be available in a more standard
arrangement so it can be easily linked to these enterprise applications. Additionally, the city's GIS
software vendor is making available to all its clients ready-to-use mapping templates designed to easily
connect to this standard database design.
When complete, the new GIS database structure will enable more efficient maintenance procedures,
provide enhanced capabilities for the city to deploy effective web mapping applications for city staff and
citizens, and more effectively link to existing and planned enterprise information systems.
FISCAL IMPACT:
The total cost for this agreement is $130,000, and is currently budgeted in the Innovation Fund.
ENVIRONMENTAL IMPACT:
Pursuant to Public Resources Code section 21065, this action does not constitute a "project" within the
meaning of CEQA in that it has no potential to cause either a direct physical change in the environment,
or a reasonably foreseeable indirect physical change in the environment, and therefore does not require
environmental review.
EXHIBITS:
1. Resolution No. 2015-048 approving the agreement for GIS consulting services with
Environmental Systems Research Institute, Inc., a California corporation, to migrate the city's GIS
database to an industry standard database structure.
2. Agreement and Scope of Work with Environmental Systems Research Institute, Inc. (Esri).
DEPARTMENT CONTACT: Karl von Schlieder 760-602-2434 karl.vonschlieder@carlsbadca.gov
FOR CLERK USE.
COUNCIL ACTION: APPROVED CONTINUED TO DATE SPECIFIC •
DENIED • CONTINUED TO DATE UNKNOWN •
CONTINUED • RETURNED TO STAFF •
WITHDRAWN • OTHER - SEE MINUTES •
AMENDED • REPORT RECEIVED •
EXHIBIT
1 RESOLUTION NO. 2015-048
2
3
A RESOLUTION OF THE CITY COUNCIL OF THE CITY OF CARLSBAD,
CALIFORNIA, APPROVING AN AGREEMENT FOR $130,000 FOR
PROFESSIONAL CONSULTING SERVICES WITH ENVIRONMENTAL
4 SYSTEMS RESEARCH INSTITUTE, INC. (Esri), A CALIFORNIA
CORPORATION, FOR GEOGRAPHIC INFORMATION SYSTEM (GIS)
5 DATABASE REDESIGN AND MODIFICATION
14
15
16
27
28
WHEREAS, the City of Carlsbad requires a redesigned geographic information system
(GIS) database that is well organized and documented according to best industry practices, and,
WHEREAS, Esri will perform the work to assess the current GIS database structure and
6
7
8
9
JQ contents, develop a plan to migrate the current GIS database to an industry-standard structure,
11 and migrate the data to the new structure, and test for accuracy; and,
^2 WHEREAS, the new GIS database will enable more efficient maintenance procedures,
13
provide enhanced capabilities for the city to deploy many effective web mapping applications
for city staff and citizens, to be accessed via desktop, tablet and mobile devices, and more
effectively link to existing and planned enterprise information systems; and
17 WHEREAS, funds sufficient to pay for the agreement between the city and Esri are
18 available via the city's Innovation Fund.
NOW, THEREFORE, BE IT RESOLVED by the City Council of the City of Carlsbad, California
20
as follows:
21
That the above recitations are true and correct.
22
22 2. That the City Council awards contract in an amount not to exceed $130,000 to Esri
24 for GIS redesign and modification services.
25 3. That the Mayor of the City of Carlsbad is authorized to execute the agreement
26 with Esri on behalf of the City of Carlsbad.
///
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
PASSED, APPROVED AND ADOPTED at a Regular Meeting ofthe City Council ofthe City
of Carlsbad on the 24*^ day of February, 2015, by the following vote to wit:
AYES:
NOES:
Council Members Hall, Blackburn, Schumacher, Wood, Packard.
None.
ABSENT: None.
MATT HALL, Mayor
ATTEST:
ShiELLEY COLLINS,Y^ssistant City Clerk
AGREEMENT FOR FIXED PRICE DATABASE SCHEMA MIGRATION SERVICES
ENVIRONMENTAL SYSTEMS RESEARCH INSTITUTE, INC.
THIS AGREEMENT is made and entered into as of the e^^-f^ day of
P^JjoV'UOjrrj , 20/^, by and between the CITY OF CARLSBAD, a municipal corporation,
("City"), and ENVIRONMENTAL SYSTEMS RESEARCH INSTITUTE, INC., a California corporation,
("Contractor").
RECITALS
A. City requires the professional services of a Geographic Information Systems (GIS)
consulting firm that is experienced in GIS database schema migration and modification services.
B. Contractor has the necessary experience in providing professional services and advice
related to migrating existing GIS databases to a local government information model.
C. Contractor has submitted a proposal to City and has affirmed its willingness and ability to
perform such work.
NOW, THEREFORE, in consideration of these recitals and the mutual covenants contained herein.
City and Contractor agree as follows:
1. DEFINITIONS
i. "Commercial Off-the-Shelf Software" or "COTS Software" means all or any portion of Contractor's
proprietary software technology accessed or downloaded from an authorized Contractor website or
delivered on any media in any format, including backups, updates, service packs, patches, hot fixes,
or permitted merged copies, available under license to the general public.
ii. "Custom Software" means all or any portion of the computer software code, components, dynamic
link libraries (DLLs), and programs delivered on any media provided in source, object, or executable
code format(s), inclusive of backups, updates, or merged copies permitted or supplied hereunder,
exclusive of Commercial Off-the-Shelf Software, or COTS Software.
iii. "Services" means Custom Software or Technical Data specified for delivery or use by the City under
this firm fixed price Agreement as specified in Exhibit A Scope of Services.
iv. "Map Data" means any digital dataset(s) including geographic, vector data coordinates, raster, or
associated tabular attributes supplied by either party for use in the performance of this Agreement,
which must be separately licensed from the vendor.
V. "Technical Data" means, without limitation, all technical materials including formula, compilations,
software code or programs, methods, techniques, know-how, technical assistance, processes, algorithms,
designs, data dictionaries and models, schematics, user documentation, training documentation,
specifications, drawings, flowcharts, briefings, test or quality control procedures, or other similar
information supplied or disclosed by Contractor under this Agreement. Technical Data does not include
Esri Agreement No. 2015C65
COTS Software, COTS data, or COTS documentation, which must be separately licensed by the City under
Contractor's commercial Software license, or Map Data.
2. SCOPE OF WORK
City retains Contractor to perform, and Contractor agrees to render, those services (the "Services") that
are defined in attached Exhibit "A", which is incorporated by this reference in accordance with this
Agreement's terms and conditions.
3. STANDARD OF PERFORMANCE AND LIMITED WARRANTY
3.1 While performing the Services, Contractor will exercise the reasonable professional care and skill
customarily exercised by reputable members of Contractor's profession practicing in the Metropolitan
Southern California Area, and will use reasonable diligence and best judgment while exercising its
professional skill and expertise.
3.2 Limited Warranty. Contractor warrants that for a period of ninety (90) days after acceptance of
Services that the unmodified Service will substantially conform, in a manner consistent with the
professional and technical standards ofthe software industry, with the applicable written
specifications that are included in, or delivered by Contractor pursuant to, the corresponding
Scope of Services.
3.3 Disclaimer of Warranties
WITH THE EXCEPTION OF THE LIMITED WARRANTY SET FORTH IN SECTION 3.2. OF THIS ARTICLE,
CONTRACTOR DISCLAIMS, AND THIS AGREEMENT EXPRESSLY EXCLUDES, ALL OTHER
OBLIGATIONS TO CORRECT OR REPLACE SERVICES AND OTHER WARRANTIES, EXPRESS OR
IMPLIED, ORAL OR WRITTEN, INCLUDING, WITHOUT UMITATION, (i) ANY WARRANTY THAT
SERVICES ARE ERROR-FREE, FAULT-TOLERANT, OR FAIL-SAFE; WILL OPERATE WITHOUT
INTERRUPTION; ARE COMPATIBLE WITH ALL EQUIPMENT AND SOFTWARE CONFIGURATIONS;
OR THAT ALL NONCONFORMITIES CAN OR WILL BE CORRECTED; (ii) ANY WARRANTY THAT THE
SERVICES ARE DESIGNED, MANUFACTURED, OR INTENDED FOR USE IN ENVIRONMENTS OR
APPLICATIONS THAT MAY LEAD TO DEATH, PERSONAL INJURY, OR PHYSICAL PROPERTY
DAMAGE OR ENVIRONMENTAL DAMAGE (ANY SUCH USE BY CITY SHALL BE AT CITY'S OWN RISK
AND COST); (iii) ANY AND ALL WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR
PURPOSE, NONINTERFERENCE, SYSTEM INTEGRATION, AND NONINFRINGEMENT OF
INTELLECTUAL PROPERTY RIGHTS.
3.3 Map Data Disclaimer. CONTRACTOR DOES NOT WARRANT IN ANY WAY THE MAP DATA,
WHETHER SUPPLIED BY CITY OR CONTRACTOR, OR THE VENDORS OF EITHER OF THEM. IF
SUPPLIED BY CONTRACTOR OR ITS VENDORS, CONTRACTOR BELIEVES SUCH MAP DATA IS
REUABLE, BUT IT MAY NOT BE FREE OF NONCONFORMITIES, DEFECTS, ERRORS, OR OMISSIONS;
BE AVAILABLE WITHOUT INTERRUPTION; BE CORRECTED IF ERRORS ARE DISCOVERED; OR MEET
CITY'S NEEDS OR EXPECTATIONS. CONTRACTOR IS NOT INVITING REUANCE ON MAP DATA, AND
CITY SHOULD ALWAYS VERIFY ACTUAL DATA FROM DOCUMENTS OF RECORD, FIELD
MEASUREMENT, OR OBSERVATION.
Esri Agreement No. 2015C65
4. TERM
The term of this Agreement will be effective for a period of one year from the date first above written.
The City Manager may amend the Agreement to extend it for one additional one year period or parts
thereof. Extensions will be based upon a satisfactory review of Contractor's performance. City needs, and
appropriation of funds by the City Council. The parties will prepare a written amendment indicating the
effective date and length ofthe extended Agreement.
5. COMPENSATION: FIXED PRICE
The total fee payable for the Services to be performed during the initial Agreement term will not exceed
one hundred-thirty-thousand dollars ($130,000). No other compensation for the Services will be allowed
except for items covered by subsequent amendments to this Agreement. The City reserves the right to
withhold a ten percent (10%) retention until City has accepted the work and/or Services specified in
Exhibit "A".
Incremental payments should be made as outlined in attached Exhibit "B".
Contractor shall prepare and submit invoices for tasks completed and accepted by the city as outlined in
Exhibit "B". Upon completion and acceptance ofall tasks under this Agreement, any unpaid balance of
the total Agreement value is due.
City shall pay each invoice no later than thirty (30) days after receipt thereof. Payment shall be made to
the Contractor address identified on original Contractor invoices.
6. STATUS OF CONTRACTOR
Contractor will perform the Services in Contractor's own way as an independent contractor and in pursuit
of Contractor's independent calling, and not as an employee of City. Contractor will be under control of
City only as to the result to be accomplished, but will consult with City as necessary. The persons used by
Contractor to provide services under this Agreement will not be considered employees of City for any
purposes.
The payment made to Contractor pursuant to the Agreement will be the full and complete compensation
to which Contractor is entitled. City will not make any federal or state tax withholdings on behalf of
Contractor or its agents, employees or subcontractors. City will not be required to pay any workers'
compensation insurance or unemployment contributions on behalf of Contractor or its employees or
subcontractors. Contractor agrees to indemnify City within thirty (30) days for any tax, retirement
contribution, social security, overtime payment, unemployment payment or workers' compensation
payment which City may be required to make on behalf of Contractor or any agent, employee, or
subcontractor of Contractor for work done under this Agreement. At the City's election. City may deduct
the indemnification amount from any balance owing to Contractor.
7. SUBCONTRACTING
Contractor will not subcontract any portion of the Services without prior written approval of City. If
Contractor subcontracts any of the Services, Contractor will be fully responsible to City for the acts and
omissions of Contractor's subcontractor and of the persons either directly or indirectly employed by the
subcontractor, as Contractor is for the acts and omissions of persons directly employed by Contractor.
Nothing contained in this Agreement will create any contractual relationship between any subcontractor
Esri Agreement No. 2015C65
of Contractor and City. Contractor will be responsible for payment of subcontractors. Contractor will bind
every subcontractor and every subcontractor of a subcontractor by the terms of this Agreement
applicable to Contractor's work unless specifically noted to the contrary in the subcontract and approved
in writing by City.
8. OTHER CONTRACTORS
The City reserves the right to employ other Contractors in connection with the Services.
9. INDEMNIFICATION
Contractor will indemnify and hold harmless the City and its officers, officials, and employees(collectively
the "Indemnified Parties") from and against all claims, damages, losses, liabilities, judgments and
settlements, including all reasonable costs, expenses and attorney's fees arising out of any action or claim
for bodily injury, death or property damage (except for databases not subject to a reasonable backup
program) brought against any of the Indemnified Parties to the extent arising from any negligence, act or
omission or willful misconduct by Contractor, any subcontractor, or their respective directors, officers,
employees or agents.
10. INSURANCE
Contractor will obtain and maintain for the duration of the Agreement and any and all amendments,
insurance against claims for injuries to persons or damage to property which may arise out of or in
connection with performance of the services by Contractor or Contractor's agents, representatives,
employees or subcontractors. The insurance will be obtained from an insurance carrier admitted and
authorized to do business in the State of California. The insurance carrier is required to have a current
Best's Key Rating of not less than "A-:VM". OR with a surplus line insurer on the State of California's List of
Eligible Surplus Line Insurers (LESLI) with a rating in the latest Best's Key Rating Guide of at least "A:X".
10.1 CoveraRes and Limits.
Contractor will maintain the types of coverages and minimum limits indicated below, unless Risk Manager
or City Manager approves a lower amount. City, its officers, agents and employees make no
representation that the limits of the insurance specified to be carried by Contractor pursuant to this
Agreement are adequate to protect Contractor. If Contractor believes that any required insurance
coverage is inadequate. Contractor will obtain such additional insurance coverage, as Contractor deems
adequate, at Contractor's sole expense.
10.1.1 Commercial General Liabilitv Insurance. $1,000,000 combined single-limit per
occurrence for bodily injury, personal injury and property damage. If the submitted policies contain
aggregate limits, general aggregate limits will apply separately to the work under this Agreement or the
general aggregate will be twice the required per occurrence limit.
10.1.2 Automobile Liabilitv. (If the use of an automobile is involved for Contractor's work
for City). $1,000,000 combined single-limit per accident for bodily injury and property damage.
Esri Agreement No. 2015C65
10.1.3 Workers' Compensation and Emplover's Liabilitv. Workers' Compensation limits
as required by the California Labor Code. Workers' Compensation will not be required if Contractor has
no employees and provides, to City's satisfaction, a declaration stating this.
10.1.4 Professional Liability. Errors and omissions liability appropriate to Contractor's
profession with limits of not less than $1,000,000 per claim. Coverage must be maintained for a period of
two years following the date of completion ofthe work.
I I If box is checked. Professional Liability
City's Initials Contractor's Initials Insurance requirement is waived.
10.2. Additional Provisions. Contractor will ensure that the policies of insurance required under this
Agreement contain, or are endorsed to contain, the following provisions:
10.2.1 The City will be named as an additional insured on Commercial General Liability
blanket endorsement, which shall provide primary coverage to the City.
10.2.2 Contractor will obtain occurrence coverage, excluding Professional Liability,
which will be written as claims-made coverage.
10.2.3 City will receive prompt notice of cancellation or nonrenewal of for the
Comprehensive General Liability, Automobile Liability, Professional Liability, and/or Workers
Compensation/Employers Liability policies, provided that no such notice is required if Contractor buys a
replacement policy that ensures continuous coverage and otherwise complies with the requirements of
this paragraph.
10.3 Providing Certificates of Insurance and Endorsements. Prior to City's execution of this
Agreement, Contractor will furnish certificates of insurance and endorsements to City.
10.4 Failure to Maintain Coverage. If Contractor fails to maintain any of these insurance coverages,
then City will have the option to purchase replacement insurance or pay the premiums that are due on
existing policies in order to maintain the required coverages. Contractor is responsible for any payments
made by City to obtain or maintain insurance and City may collect these payments from Contractor or
deduct the amount paid from any sums due Contractor under this Agreement.
11. BUSINESS LICENSE
Contractor will obtain and maintain a City of Carlsbad Business License for the term of the Agreement, as
may be amended from time-to-time.
12. ACCOUNTING RECORDS
Contractor will maintain complete and accurate records with respect to direct costs incurred in the
performance of this Agreement. All records will be clearly identifiable. Contractor will allow a
representative of City during mutually agreed upon normal business hours at Contractor's Redlands, CA
headquarters to examine such records (excluding proprietary information, proprietary processes, profit,
overhead, general and administrative costs of the Contractor). Contractor will allow inspection of all such
records for a period of three (3) years from the date of final payment under this Agreement.
Esri Agreement No. 2015C65
13. OWNERSHIP OF DOCUMENTS
Contractor or its licensors own and retain all right, title, and interest in the Services. This Agreement
does not transfer ownership rights of any description in the Services to City or any third party. Subject to
the terms and conditions set forth in this Agreement and effective upon the transfer, by any means, of
the Services to the City, Contractor hereby grants to the City a nonexclusive, worldwide license in the
Services to use, modify, and reproduce the Services in connection with the City's authorized use of COTS
Software. The license grant in the immediately preceding sentence does not apply to Map Data, which
the City must separately and directly license from the vendor.
City shall retain any patent, copyright, or trademark or proprietary notices on all items licensed under this
Agreement and shall take other necessary steps to protect Contractor's or its licensor's intellectual
property rights.
14. ACCEPTANCE
Services shall be categorized as follows:
i. "SERVICE ACCEPTED" means a service conforming to applicable Scope of Services with no more
than minor nonconformities. City shall complete its acceptance review within ten (10) working
days of receiving each Service.
ii. "SERVICE ACCEPTED WITH REWORK" means a service substantially conforming to applicable
Scope of Services, but having a significant number of identified nonconformities and accepted
subject to rework by Contractor. Contractor shall rework the Service for the identified
nonconformities and resubmit it within thirty (30) days. City will rerun its acceptance review for
the nonconformities detected in the initial review within ten (10) working days of such
resubmission and will reclassify the service as either SERVICE ACCEPTED or SERVICE REJECTED.
iii. " SERVICE REJECTED" means a Service that fails to substantially conform to applicable Scope of
Services. Contractor shall rework the Service and resubmit it to City within thirty (30) days, at
which time City shall have ten (10) working days to rerun its acceptance review and reclassify
the service as either SERVICE ACCEPTED or SERVICE REJECTED.
City agrees it shall not use any Service in its business operations before acceptance as described in i. or
ii. If Contractor does not receive within ten (10) working days after delivery written notice that the
Service is "ACCEPTED WITH REWORK" or "REJECTED" in accordance with ii. or iii., or if City uses the
Service in its business operations, the Service shall be deemed, as of the first to occur of either of these
events, to have been accepted.
15. LIMITATION OF LIABILITY
A. Disclaimer of Certain Types of Liability. CONTRACTOR AND ITS LICENSORS WILL NOT BE LIABLE TO
CITY FOR COSTS OF PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOST PROFITS; LOST
SALES; BUSINESS EXPENDITURES; INVESTMENTS; BUSINESS COMMITMENTS; LOSS OF ANY
GOODWILL; OR ANY INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES ARISING OUT
OF OR RELATED TO THIS AGREEMENT OR USE OF THE SERVICES, HOWEVER CAUSED, ON ANY
Esri Agreement No. 2015C65
THEORY OF UABILITY, WHETHER OR NOT CONTRACTOR OR ITS LICENSORS HAVE BEEN ADVISED OF
THE POSSIBILITY OF SUCH DAMAGE. THESE LIMITATIONS SHALL APPLY NOTWITHSTANDING ANY
FAILURE OF ESSENTIAL PURPOSE OF ANY LIMITED REMEDY.
B. General Limitation of Liability. IN NO EVENT WILL CONTRACTOR'S TOTAL CUMULATIVE LIABILITY
ARISING OUT OF OR RELATED TO THIS AGREEMENT OR USE OF THE SERVICES FROM ALL CAUSES OF
ACTION OF ANY KIND, INCLUDING, BUT NOT LIMITED TO, CONTRACT, TORT (INCLUDING
NEGLIGENCE), STRICT LIABILITY, BREACH OF WARRANTY, MISREPRESENTATION, OR OTHERWISE,
EXCEED THE AMOUNTS PAID TO CONTRACTOR BY CITY FOR THE SERVICES FROM WHICH THE
LIABILITY DIRECTLY AROSE.
C. Applicability of Disclaimers and Limitations. City agrees that the limitations of liability and
disclaimers set forth in this Agreement will apply regardless of whether City has accepted the
Services, or any other product or service delivered by Contractor. The parties agree that Contractor
has set its prices and entered into this Agreement in reliance upon the disclaimers and limitations
set forth herein, that the same reflect an allocation of risk between the parties (including the risk
that a contract remedy may fail of its essential purpose or cause consequential loss), and that the
same form an essential basis ofthe bargain between the parties.
16. EXPORT CONTROL REGULATIONS
City must comply with all applicable laws and regulations ofthe United States including, without
limitation, its export control laws. City expressly acknowledges and agrees that City shall not export,
reexport, transfer, or release COTS Software or Services in whole or in part, to (i) any US embargoed
country (including to a resident of any US embargoed country); (ii) any person on the US Treasury
Department's List of Specially Designated Nationals; (iii) any person or entity on the US Commerce
Department's Lists of Parties of Concern; or (iv) any person or entity where such export, reexport, or
provision violates any US export control laws or regulations including, but not limited to, the terms of
any export license or licensing provision and any amendments and supplemental additions to US export
laws as they may occur from time to time.
17. CONFIDENTIALITY
1. Contractor Confidential Information
Unless otherwise agreed in writing, and subject to the California Public Records Act, the Services
are Contractor confidential and the City shall preserve and protect their confidentiality. Insofar
as its rights may be legally restricted, the City agrees not to reverse engineer or decompile
Services delivered only in object code, executable code, or formats subject to similar or greater
means of access control (collectively, "Secure Formats"). For Services delivered in source code
or other human-readable formats, the City shall have met its obligations under this Article if its
disclosure of Services is limited to Services in Secure Formats, provided that the means for
reverse engineering, decompiling, or disassembling such Services is withheld from such
disclosure, and the person or entity in receipt of such Services similarly agrees not to perform
such acts or allow others to do so.
Esri Agreement No. 2015C65
Except as provided in the preceding paragraph, the City shall not disclose the Services to
employees or third parties without the advanced written consent of Contractor. However, the
City may, without such consent, make such disclosures to employees as are reasonably required
for the City's authorized use ofthe COTS Software, provided that such disclosure is strictly
limited to the portions ofthe Services needed for that purpose.
Before disclosing all or any portion ofthe Services to employees or third parties as permitted in
the preceding paragraph, the City shall inform such employees or third parties ofthe obligations
in this Article and obtain their agreement to be bound by them.
2. City Confidential Information
Contractor acknowledges that by reason of its relationship to the City hereunder. Contractor
may have access to certain information and materials concerning the City's business plans,
clients, technology, and products that are confidential and of substantial value, and said value
would be impaired if such information were disclosed to third parties. Contractor agrees that it
shall not use in any way for its own account or the account of any third party, nor disclose to any
third party, any identified confidential information revealed to it in writing or orally. Contractor
will protect the confidential information as they protect their own, using no less than a
reasonable standard of care.
3. Exclusions to Confidentiality
Neither party shall have any obligation to protect any part of Confidential Information, as
described in subsections 1. and 2. herein, that it can prove: (i) was in its possession before
receipt from the disclosing party; (ii) is or becomes a matter of public knowledge through no
fault ofthe recipient; (iii) is rightfully disclosed by a third party without a duty of confidentiality;
(iv) is disclosed by discloser to a third party without a duty of confidentiality; (v) is
independently developed by a party; or (vi) is required to be disclosed by operation of law.
18. TAXES
Values specified in this Agreement are exclusive of state, local, and other taxes or charges (including,
without limitation, custom duties, tariffs, and value-added taxes, but excluding income taxes payable by
Contractor). In the event such taxes or charges become applicable to Services, City shall pay any such
taxes upon receipt of written notice that they are due.
19. FORCE MAJEURE
If the performance of this Agreement, or any obligation except the making of payments, is prevented,
restricted, or interfered with by reason of fire, flood, earthquake, explosion, or other casualty or
accident; strikes or labor disputes; inability to procure or obtain delivery of parts, supplies, or power;
war, terrorist act, cyberattack, or other violence; any law, order, proclamation, regulation, ordinance,
demand, or requirement of any governmental agency; or any act or condition whatsoever beyond the
reasonable control ofthe affected party, the party so affected, upon giving prompt notice to the other
Esri Agreement No. 2015C65
party, shall be excused from such performance to the extent of such prevention, restriction, or
interference.
20. RESTRICTIONS ON SOLICITATION
City shall not solicit for hire any Contractor employee who is associated with efforts called for under this
Agreement during the term of this Agreement and for a period of one (1) year thereafter. The foregoing
shall in no way restrict City from publicly advertising positions for hire in newspapers, professional
magazines, or Internet postings.
21. CHANGES TO SCOPE OF SERVICES
City may, at anytime, request changes to the Scope of Services. If the parties agree to such changes and
such changes cause an increase or decrease in the cost or time required to provide Services, an
equitable adjustment in the price or schedule, or both, shall be made, and this Agreement shall be
modified accordingly in writing and signed by both parties.
22. PATENTS AND INVENTIONS
During the performance of this Agreement, the parties anticipate that inventions, innovations, and
improvements ("Inventions") relating to the subject matter of this Agreement may be conceived solely
or jointly by principals, employees, consultants, or independent contractors (hereinafter called
"Inventors") ofthe parties hereto.
The parties agree that, as of the effective date of this Agreement, Contractor or its licensors own all
intellectual property rights in the COTS Software. During the term of this Agreement, City shall promptly
notify Contractor if City becomes aware of any known or suspected infringement or violation of these
rights.
Each party shall retain title to any Inventions made or conceived solely by its Inventors during the term
of this Agreement, including, but not limited to, such Inventions that Contractor's Inventors solely make
or conceive while providing technical assistance pursuant to this Agreement. The parties shall jointly
own any Inventions made or conceived jointly by Inventors from both parties.
Where only one party has title to an Invention, that party, at its sole discretion, shall have the right, but
not the obligation, at its expense to (i) decide on whether or not to seek or maintain, or to continue to
seek or maintain, patent protection in any country on such Invention; (ii) decide the extent and scope of
such protection; and (iii) protect and enforce in any country any patents issued on such Invention.
Except as provided in the next paragraph, where an Invention is jointly owned, each party shall share
equally the costs of acquiring protection for the Invention and furnish the other joint owner with
assistance reasonably required for acquiring protection.
The acquisition or maintenance of protection shall not be abandoned by a joint owner (the "Assigning
Owner") without giving the other joint owner (the "Beneficial Owner") an opportunity to intervene and
acquire or maintain protection at the Beneficial Owner's expense. The Assigning Owner electing not to
acquire or maintain protection on any Inventions in any country or countries shall assign such of its
rights in such Inventions to the Beneficial Owner as is necessary to enable the Beneficial Owner to
protect such Inventions in such country or countries at its expense and for its exclusive benefit. In such
Esri Agreement No. 2015C65
event, the Assigning Owner shall make available to the Beneficial Owner the Assigning Owner's
Inventors and shall otherwise cooperate with the Beneficial Owner in orderto assist the Beneficial
Owner in protecting such Inventions. The Beneficial Owner shall reimburse the Assigning Owner for all
reasonable out-of-pocket expenses incurred in rendering such assistance. If any such Inventions are so
protected by the Beneficial Owner, then the Assigning Owner shall have a license with respect to the
subject matter of such protected Inventions in such country or countries.
All Inventions made by Inventors during performance of tasks defined by the Scope of Services during
the term of this Agreement will be presumed, absent clear and convincing evidence to the contrary, to
have resulted from the Inventors' activities under the Scope of Services.
Neither party may license, transfer, sell, or otherwise alienate or encumber its interest in jointly owned
Inventions without the written consent ofthe other party, which shall not be unreasonably withheld by
either party. However, either party may transfer such Inventions to its Affiliates for their internal use
only. "Affiliate" shall mean the parent or subsidiary companies of a party or subsidiary companies to a
party's parent provided there is more than fifty percent (50%) ownership ofthe subsidiary by the parent
or party.
23. NOTICES
The name ofthe persons who are authorized to give written notices or to receive written notice on behalf
of City and on behalf of Contractor under this Agreement.
For Citv For Contractor
Name Karl von Schlieder Name John Perry
Contracts Manager - Esri Professional
Title GIS Manager Title Services Division
Department Information Technology Address 380 New York Street
City of Carlsbad Redlands, CA 92373
Address 1635 Faraday Ave Phone No. (909)793-2853
Carlsbad CA 92008-7314 Email jperry@esri.com
Contracts Manager
Phone No. (760)602-2434 Copy Tel: (909) 793-2853, ext. 2248
Each party will notify the other immediately of any changes of address that would require any notice or
delivery to be directed to another address.
24. CONFLICT OF INTEREST
City will evaluate Contractor's duties pursuant to this Agreement to determine whether disclosure under
the Political Reform Act and City's Conflict of Interest Code is required of Contractor or any of
Contractor's employees, agents, or subcontractors. Should it be determined that disclosure is required.
Esri Agreement No. 2015C65 10
Contractor or Contractor's affected employees, agents, or subcontractors will complete and file with the
City Clerk those schedules specified by City and contained in the Statement of Economic Interests Form
700.
Contractor, for Contractor and on behalf of Contractor's agents, employees, subcontractors and
consultants confirms that to the best of its current knowledge, by execution of this Agreement, that
they have no interest, present or contemplated, in the projects affected by this Agreement. Contractor
further confirms that to the best of its current knowledge, neither Contractor, nor Contractor's agents,
employees, subcontractors and consultants have any ancillary real property, business interests or
income that will be affected by this Agreement or, alternatively, that Contractor will file with the City an
affidavit disclosing this interest.
25. GENERAL COMPLIANCE WITH LAWS
Contractor will keep fully informed of federal, state and local laws and ordinances and regulations which
in any manner affect those employed by Contractor, or in any way affect the performance ofthe Services
by Contractor. Contractor will at all times observe and comply with these laws, ordinances, and
regulations and will be responsible for the compliance of Contractor's services with all applicable laws,
ordinances and regulations.
Contractor will be aware of the requirements of the Immigration Reform and Control Act of 1986 and will
comply with those requirements, including, but not limited to, verifying the eligibility for employment of
all agents, employees, subcontractors and consultants whose services are required by this Agreement.
26. DISCRIMINATION AND HARASSMENT PROHIBITED
Contractor will comply with all applicable local, state and federal laws and regulations prohibiting
discrimination and harassment.
27. DISPUTE RESOLUTION
If a dispute should arise regarding the performance of the Services the following procedure will be used
to resolve any questions of fact or interpretation not otherwise settled by agreement between the parties.
Representatives of Contractor or City will reduce such questions, and their respective views, to writing. A
copy of such documented dispute will be forwarded to both parties involved along with recommended
methods of resolution, which would be of benefit to both parties. The representative receiving the letter
will reply to the letter along with a recommended method of resolution within ten (10) business days. If
the resolution thus obtained is unsatisfactory to the aggrieved party, a letter outlining the disputes will
be forwarded to the City Manager. The City Manager will consider the facts and solutions recommended
by each party and may then opt to direct a solution to the problem. In such cases, the action ofthe City
Manager will be binding upon the parties involved, although nothing in this procedure will prohibit the
parties from seeking remedies available to them at law.
28. TERMINATION
City shall have the right, in addition and without prejudice to any other rights or remedies, to
terminate this Agreement for any material breach of this Agreement by Contractor that is not
cured within fifteen (15) days of receipt by Contractor of a notice specifying the breach and
Esri Agreement No. 2015C65 11
requiring its cure. City may also terminate this Agreement immediately upon written notice to
Contractor in the event that one or more ofthe following occur:
i. Contractor becomes insolvent, ceases to pay its debts in the ordinary course of business,
is unable to pay its debts as they become due, or makes an assignment for the benefit of
creditors;
ii. A trustee or receiver is appointed for any or all of Contractor's assets;
iii. Any bankruptcy or insolvency proceeding under any federal or state bankruptcy or
insolvency code, or similar law, whether voluntary or involuntary, is commenced by or
against Contractor.
Contractor may terminate this Agreement immediately upon written notice to City in the event
that one or more ofthe following occur:
Insolvency of City
i. City becomes insolvent, ceases to pay its debts in the ordinary course of business, is
unable to pay its debts as they become due, or makes an assignment for the benefit of
creditors;
ii. A trustee or receiver is appointed for any or all of City's assets;
iii. Any bankruptcy or insolvency proceeding under any federal or state bankruptcy or
insolvency code, or similar law, whether voluntary or involuntary, is commenced by or
against City.
Default or Breach by City
iv. City defaults under this Agreement three (3) or more times within any six (6)-month
period, regardless ofwhether such defaults are cured;
V. City engages in the unauthorized use of the COTS Software;
vi. City engages in the unauthorized use, reproduction, or disclosure of Services;
vii. City breaches any provision of this Agreement and there is no possibility of cure;
viii. City fails to pay after ten (10) days' written notice the amounts due to Contractor
pursuant to the compensation section of this Agreement.
Obligations upon Termination
i. In the event of termination by Contractor pursuant to Subsections iv-viii of Contractor's
termination rights pursuant to this Section, the due dates of all invoices for amounts owed by
City to Contractor shall be accelerated automatically so that such amounts become due and
payable on the effective date ofthe termination, regardless ofthe payment term provisions set
forth in this Agreement.
ii. Upon termination of this Agreement, the parties shall have no further obligations pursuant to its
terms, except that Sections titled Definitions, Patents and Inventions, Confidentiality,
Esri Agreement No. 2015C65 12
Compensation, Disclaimer of Warranty, Limitation of Liability, Export Control Regulations,
Termination, restrictions on Solicitation and Taxes shall survive termination. Unless City has
materially breached its obligations under this Agreement, Sections titled Ownership of
Documents, and Limited Warranty shall also survive termination. Except where specifically stated
otherwise, any current or future cause of action or claim of one party because of any breach or
default ofthe other party and any accrued license rights shall survive to the degree necessary to
permit the complete fulfillment or discharge of the cause of action.
Either party upon tendering thirty (30) days written notice to the other party may terminate this
Agreement. In this event and upon request of City, Contractor will assemble the work product and put it
in order for proper filing and closing and deliver it to City. Contractor will be paid for work performed to
the termination date; however, the total will not exceed the lump sum fee payable under this Agreement.
City will make the final determination as to the portions of tasks completed and the compensation to be
made.
29. COVENANTS AGAINST CONTINGENT FEES
Contractor warrants that Contractor has not employed or retained any company or person, other than a
bona fide employee working for Contractor, to solicit or secure this Agreement, and that Contractor has
not paid or agreed to pay any company or person, other than a bona fide employee, any fee, commission,
percentage, brokerage fee, gift, or any other consideration contingent upon, or resulting from, the award
or making of this Agreement.
30. CLAIMS AND LAWSUITS
30.1 By signing this Agreement, Contractor agrees that any Agreement claim submitted to City must
be asserted as part ofthe Agreement process as set forth in section 30.2 of this Agreement. Contractor
acknowledges that if a false claim is submitted to City, it may be considered fraud and Contractor may be
subject to criminal prosecution. Contractor acknowledges that California Government Code sections
12650 et seq.. the False Claims Act applies to this Agreement and, provides for civil penalties where a
person knowingly submits a false claim to a public entity. These provisions include false claims made with
deliberate ignorance ofthe false information or in reckless disregard ofthe truth or falsity of information.
If City seeks to recover penalties pursuant to the False Claims Act, it is entitled to recover its litigation
costs, including attorney's fees. Contractor acknowledges that the filing of a false claim may subject
Contractor to an administrative debarment proceeding as the result of which Contractor may be
prevented to act as a Contractor on any public work or improvement for a period of up to five (5) years.
Contractor acknowledges debarment by another jurisdiction is grounds for City to terminate this
Agreement.
30.2 If a dispute should arise regarding the performance ofthe Services the following procedure will
be used to resolve any questions of fact or interpretation not otherwise settled by agreement between
the parties. Representatives of Contractor or City will reduce such questions, and their respective views,
to writing. A copy of such documented dispute will be forwarded to both parties involved along with
recommended methods of resolution, which would be of benefit to both parties. The representative
receiving the letter will reply to the letter along with a recommended method of resolution within ten
(10) business days. If the resolution thus obtained is unsatisfactory to the aggrieved party, a letter
outlining the disputes will be forwarded to the City Manager. The City Manager will consider the facts
and solutions recommended by each party and may then opt to direct a solution to the problem. In such
Esri Agreement No. 2015C65 13
cases, the action ofthe City Manager will be binding upon the parties involved, although nothing in this
procedure will prohibit the parties from seeking remedies available to them at law.
31. JURISDICTION
This Agreement shall be governed by and construed in accordance with the laws of the State of California
without reference to conflict of laws principles.
32. SUCCESSORS AND ASSIGNS
It is mutually understood and agreed that this Agreement will be binding upon City and Contractor and
their respective successors. Neither this Agreement or any part of it nor any monies due or to become
due under it may be assigned by either party without the prior consent ofthe other party, which shall not
be unreasonably withheld.
33. ENTIRE AGREEMENT
This Agreement, together with any other written document referred to or contemplated by it, along with
the purchase order for this Agreement and its provisions, embody the entire Agreement and
understanding between the parties relating to the subject matter of it. In case of conflict, the terms of the
Agreement supersede the purchase order. Neither this Agreement nor any of its provisions may be
amended, modified, waived or discharged except in a writing signed by both parties.
W
W
W
34. AUTHORITY
The individuals executing this Agreement and the instruments referenced in it on behalf of Contractor
each represent and warrant that they have the legal power, right and actual authority to bind Contractor
to the terms and conditions of this Agreement.
CONTRACTOR/ ENVIRONMENTAL SYSTEMS CITY OF CARLSBAD, a municipal corporation of
RESEARCH INSTITUTE, INC. the State of California
By: By:
• Mayor >
Matt Hall
Alejandra Merino
Wsnager, Intemational Contrails
(print name/title)
Esri Agreement No. 2015C65 14
ATTEST:
By:
(sign here) BARBARA EN
City Clerk
(print name/title)
If required by City, proper notarial acknowledgment of execution by contractor must be attached. If a
corporation. Agreement must be signed by one corporate officer from each ofthe following two groups.
Group A
Chairman,
President, or
Vice-President
Group B
Secretary,
Assistant Secretary,
CFO or Assistant Treasurer
otherwise, the corporation must attach a resolution certified by the secretary or assistant secretary under
corporate seal empowering the officer(s) signing to bind the corporation.
APPROVED AS TO FORM:
CEUA-ArBse^y^^^g^cTEy Attorney
Assistant City Attorney
Esri Agreement No. 2015C65 15
EXHIBIT "A"
SCOPE OF SERVICES
Task 1 Migrate the Current City GIS Database to Esri's LGIM Schema
The goal of this task is to migrate the City's current geodatabase to a LGIM geodatabase. This
migration will be accomplished by conducting a data mapping workshop to map feature classes
and attributes in the current geodatabase to the LGIM; tailoring the model for attributes and
feature classes not in the main LGIM but needed by the City; creating migration scripts, running
the scripts to migrate the data, assessing the quality of conversion; and finally delivering the
migration scripts and source code.
Task 1.1 Conduct Data Mapping Between Source and Target Database
Task 1.1.1 Project Kickoff
Esri will conduct a remote Project Kickoff meeting via a three hour webcast which will cover the
following topics:
Introduce the team members and identification of project roles
Review project tasks
Review contract scope of work, project schedule, and deliverables
Finalize project resources and responsibilities
Finalize project communication process
Finalize mechanism for risk management and issue tracking
Finalize progress reporting mechanism
Esri will prepare and submit a draft project kickoff meeting agenda to the City for review five business
days prior to the start ofthe meeting. Esri will review the draft kickoff meeting agenda with the City and
will incorporate updates, as mutually agreed. This document will then be used to produce the final
kickoff meeting agenda.
The Esri project manager will coordinate with the City project manager to schedule the Project Kickoff
meeting and other logistics, including attendance of participants.
After reviewing the project plan and schedule with the City, Esri will make the changes as
mutually agreed upon and conduct another two hour webcast to review the final schedule. Esri
will then submit the final project schedule to the City. The City will provide Esri with written
acceptance of the final project schedule within two business days of receipt. Once the City
accepts the final project schedule, the tasks below will be started.
Esri Deliverables:
• Draft and final project kickoff meeting agenda.
Esri Agreement No. 2015C65 16
• Lead a three-hour remote project kickoff meeting.
• Lead a two-hour webcast to review the final schedule.
• Draft and Final project schedule.
City Responsibilities:
• Ensure appropriate City Core Team members participate in three hour project kickoff
meeting.
• Ensure appropriate City Core Team members participate in two hour project schedule
final review meeting.
• Provide Esri with written acceptance ofthe final schedule agenda within two business
days of receipt.
Task 1.1.2 Data Mapping Workshop
Esri will travel to the City's offices in Carlsbad, CA to conduct a three day workshop with the
City's GIS and IT staff to map feature classes and attribute data to the LGIM and document the
mapping with a mapping matrix in an Excel spreadsheet format. The City will provide Esri with
a copy of the current geodatabase prior to the start of the project. Esri will review it prior to
conducting the workshop.
During the workshop, Esri will review the feature classes and attributes that are related to the
LGIM and assess and document the data needed to drive the functions of the following ArcGIS
applications and maps for:
Local government basemaps
Infrastructure maps and applications
Public safety maps and applications
Planning and development maps and applications
Facilities maps and applications
Address maintenance maps and applications
Public works maps and applications
Esri will also review and document the data requirements of key applications and internal
databases that will consume GIS data or interact with GIS data from the LGIM schema. As part
of this review, detailed process and workflow mapping ofthe following systems will be
analyzed. The following are the current applications at the City that will consume GIS data from
the LGIM schema:
• Public works asset data inventory contained in a number of datasets
o With data entry class extensions, subtypes, and relationship classes
Esri Agreement No. 2015C65 17
Integrated community development system
o Now Energov but was Accela PERMITS PLUS
Public works work order and asset management system
o Infor Public Sector 8.2.3 (formerly Hansen)
Facilities maps and applications
Address maintenance maps and applications
Public works maps and applications
Esri Deliverables:
• Three-day on-site Data Mapping Workshop.
City Responsibilities:
• Communicate project needs and priorities to the Esri consultant.
• Provide appropriate management and technical staff to participate in the on-site
workshop activities.
• Provide to Esri all required information on business processes, GIS applications, GIS
services, data sources, workflows, and geodatabases while Esri is on-site.
• Identify and schedule the appropriate City staff to attend the Data Mapping Workshop.
• Provide a conference room equipped with an SVGA LCD projector. This conference room
should be large enough to host the workshop activities.
Task 1.1.3 Data Mapping Design
Based upon the results ofthe Data Mapping Workshop, Esri will prepare a Data Mapping Matrix
which will include the following:
• Feature classes and attributes in the current geodatabase mapped to the LGIM
• Document any attribute data mapped for another database to the LGIM
• Additional feature classes and attributes added to the LGIM based upon the workshop
findings
• Documented changes to LGIM domains
• Documented changes to:
o Subtypes
o Datatypes
o Relationship classes
Esri will prepare a Draft Data Mapping Matrix and submit it to the City for review and comment.
Following receipt, the City will have three business days to review the draft and provide Esri with
consolidated, written comments that have been reviewed and approved by the City project manager.
Esri Agreement No. 2015C65 18
Upon receipt of the City's comments, Esri will conduct a two-hour webcast to review the draft Data
Mapping Matrix, including the City's comments. Esri will incorporate changes, as mutually agreed, and
deliver a final version ofthe Data Mapping Matrix. The City is responsible for providing Esri with written
acceptance ofthe final Data Mapping Matrix within two business days of receipt.
Esri Deliverables:
• Draft Data Mapping Matrix.
• Conduct two-hour webcast to review the draft Data Mapping Matrix.
• Final Data Mapping Matrix.
City Responsibilities:
• Address follow-up questions as required by Esri.
• Review the draft Data Mapping Matrix and provide Esri with consolidated written
comments within three business days of receipt.
• Participate in two-hour webcast to review the draft Data Mapping Matrix.
• Provide Esri with written acceptance ofthe final Data Mapping Matrix within two
business days of receipt.
Task 1.2 Migrate Data to the LGIM Schema
Task 1.2.1 Test Environment Installation/Configuration
Esri will establish a test environment at Esri offices in Redlands, California and remotely assist
the City in setting up a development/test environment at the City's offices in Carlsbad,
California. These test environments will support the creation and testing of extraction,
transformation, and loading (ETL) scripts, data migration scripts ifapplicable, data reviewer
scripts, and any additional quality assurance/quality check (QA/QC) scripts (if applicable). The
purpose of the test environment at Esri is to provide a controlled environment that mimics the
City's test and production environment as closely as possible to test the functionality of the
scripts before testing them in the City's test environment.
Task 1.2.2 ETL Development and Migration
Based on the accepted Data Mapping Matrix, Esri will create the data migration ETL scripts. Esri
will then run the scripts in its test environment to load data into the LGIM schema from the
current GIS and any other City database that was identified as a source of attribute data in the
accepted Data Mapping Matrix.
Esri Agreement No. 2015C65 19
Esri will conduct webcast Development Review Meetings during this task to elicit comments
and inform the City on the status ofthe task. The frequency ofthe webcast Review Meetings
will be mutually agreed upon by Esri and the City.
Esri Deliverables:
• Development Review Meeting(s) with the City as mutually agreed upon.
• Migrated data resident in Esri's test environment
City Responsibilities:
• Ensure appropriate resources are available to participate in Development Review
Webcasts as mutually agreed upon.
Assunjptions:
• If there isn't a development environment at the City, then the City's test environment
will be used as an initial development environment and then will be reinstalled using the
Deployment Plan for UAT in Task 1.4.
Task 1.3 Assess Conversion Quality and Generate Reports
Esri will assess the quality and accuracy ofthe conversion, and generate reports on resulting
inventory data gaps, e.g. empty LGIM feature classes/fields, native Carlsbad data migrated "as-
is", and other discrepancies in the LGIM version ofthe database resulting from the migration.
Esri has implemented numerous LGIM conversions and has found that the best results occur
when the following tasks are done as part ofthe LGIM migration project:
Test Plan
Deployment Plan
Internal Acceptance Testing (IAT)
User Acceptance Testing (UAT)
Implementation
Task 1.3.1 Test Plan
Esri will initiate development of the Test Plan including Test Scripts upon completion of the
deliverables specified in Task 1.1.3.
Esri will prepare a Test Plan that will identify procedures, types of testing, and test strategy to
be used for acceptance ofthe migration ofthe City's geodatabase to its configured LGIM
schema during the IAT and UAT tasks described below. The Test Plan will include Test Scripts
and identify the criteria that the City will use to determine acceptance ofthe configured LGIM
schema. The Test Plan will include the following content:
Esri Agreement No. 2015C65 20
Schedule of testing activities
The types of test or testing cycles that will be completed prior to and during UAT, and
their location
Testing logistics for Esri internal testing activities and those conducted during UAT
Specifications for the testing environment(s) that will be used
Roles and responsibilities during testing
Test reporting
User acceptance criteria
Corrective action procedures
The Test Scripts within the Test Plan will include:
• £/st of Test Scripts—This is a listing of the tests that will be executed to verify that the
migrated LGIM meets the City's acceptance criteria
• Content of each test scr/pt—Instructions of how to conduct the test, including
information such as specific sequence of steps, environment, variables, and pre/post
conditions
Esri will deliver a draft Test Plan to the City. Following receipt, the City will have three business days to
review the draft and provide Esri with consolidated, written comments that have been reviewed and
approved by the City's project manager. Upon receipt ofthe City's comments, Esri will conduct a two-
hour webcast to review the draft Test Plan, including the City's comments. Esri will incorporate changes,
as mutually agreed, and deliver a final version. The City is responsible for providing Esri with written
acceptance ofthe final Test Plan within two business days of receipt.
Note: Written acceptance of the Test Plan by the City is a pre-condition for Esri to proceed with IAT and
UAT
Esri Deliverables:
• Draft Test Plan.
• Two-hour webcast to review the draft Test Plan.
• Final Test Plan.
City Responsibilities:
• Ensure that appropriate management and technical staff participate in the Test Plan
review webcast.
• Review the draft Test Plan document and provide Esri with consolidated written
comments within three business days of receipt.
• Provide Esri with written acceptance ofthe final Test Plan document within two
business days of receipt.
Esri Agreement No. 2015C65 21
Task 1.3.2 Internal Acceptance Testing (IAT)
IAT can be initiated once the ETL scripts are functionally complete and meets IAT test entry criteria as
specified in the accepted Test Plan. The objective of IAT is to confirm that the LGIM migration complies
with the accepted Test Plan prior to delivering the migrated data to the City for UAT. IAT will implement
the same procedures that the City will use during UAT in an environment that replicates the City's
environment as closely as possible.
Esri will conduct IAT at Esri offices in Redlands, California. The test scripts contained in the accepted
Test Plan will form the basis ofwhether the migrated LGIM passes the IAT process.
During IAT, Esri's test team will log defects in Esri's defect tracking system. Esri will review defect
reports and identify those that require defect fixes for resolution. Where appropriate, defect fixes will
be made and regression tested during IAT.
At the conclusion of IAT, Esri will compile an IAT test report documenting the results ofthe IAT. The IAT
test results report includes:
• Summary of the testing approach
• Recommendation on readiness to proceed with UAT
• Test results, including pass/fail decision for Test Scripts, and list of defects
Esri will conduct a two hour IAT review meeting, via webcast, with the City to review the IAT test results
report, including the readiness ofthe migrated data for UAT in the City's test/quality assurance
environment.
Once the data has been migrated to LGIM, has been reviewed and reports generated, Esri will create
and deliver a release package to the City for deployment in the City's Test/Quality Assurance
environment for UAT. The release package will include:
• Data migrated to LGIM
• Quality control reports
• ETL Scripts
• QA/QC scripts
• Release notes
• Installation instructions
IAT will be deemed complete when all IAT test scripts have been executed and defect thresholds in the
acceptance criteria as defined in the accepted Test Plan have not been exceeded.
£sr/ Deliverables:
• Data migrated to LGIM
• IAT test results report.
Esri Agreement No. 2015C65 22
• Remote two hour IAT review meeting, via webcast, with the City.
• Release package that will be used for UAT.
City Responsibilities
• Participate in the IAT review meeting via webcast.
Task 1.4 Deliver Extracting, Loading, and Transforming (ETL) Scripts
Esri will deliver for installation on the City's system the migrated data, QA/QC scripts and the
ETL tools used in the migration. This will be done in the Test/Quality Assurance (OA)
environment for the UAT and in production for implementation once UAT has been accepted.
Task 1.4.1 User Acceptance Testing (UAT)
The objective of UAT is for the City to test the LGIM migration and ETL scripts to confirm that it meets
the acceptance criteria as defined in the accepted Test Plan.
To initiate UAT, Esri will travel to the City's office in Carlsbad, California for a period of four consecutive
business days. The migrated LGIM database, ETL software (Data Interoperability extension for ArcGIS
for Desktop), QA/QC software (Data Reviewer extension for ArcGIS for Desktop), ETL Scripts, and QA/QC
scripts will be installed/loaded into the City's test/QA system under direction of Esri to prepare the
environment for UAT.
Immediately following the UAT environment deployment, Esri will provide the City's test team with a
one-day training class on how to test the migration based on the accepted Test Plan.
Following the UAT test team training class, the City will test the LGIM migration to verify that it functions
in accordance with the accepted Test Plan. The City will record discrepancies, if any, using the defect
reporting mechanism as specified in the accepted Test Plan. UAT will be conducted over a period of
seven business days. Esri will provide two days of on-site support and five days remote support during
UAT.
During UAT, the following procedures will be used to review and validate any reported discrepancies:
1. When the test team members for the City finds a discrepancy that they believe is a migration
defect, they will verify with another team member before reporting the issue to Esri. The City
will document the steps needed to reproduce the problem using an agreed to defect reporting
template. Esri will then work to validate the discrepancy. If Esri can validate the discrepancy, it
will be recorded as a defect and classified as one of four defect severity levels (reference the
descriptions in Table 1 below).
2. If Esri cannot validate the discrepancy, the City testing team will either provide more
information or demonstrate how and where the discrepancy occurs. Based on this information,
Esri will work to further identify the source of the discrepancy. Esri may determine that the
Esri Agreement No. 2015C65 23
discrepancy is not an ETL script problem but instead a problem with data, the network, or a
misunderstanding about how the data will be converted.
3. If Esri cannot replicate a reported discrepancy, if the City test team cannot demonstrate it, or if
it is determined by Esri that the discrepancy has another cause not related to Esri-supplied
software, then Esri will notify the City's test team that the problem is not an ETL script defect
and identify the cause of the defect. If appropriate, Esri will recommend an action to take, for
example, to reload certain data into the geodatabase.
The City will send daily defect reports to Esri based on a mutually agreed-on format. Esri will use its
internal defect-tracking application to capture and prioritize defects and modifications.
During UAT, the City's testing team and Esri will hold daily defect review meetings or conference calls to
review the open defects and associated severity. At the conclusion of UAT, Esri will create a software
test report documenting the result of UAT. The Esri project manager will lead a conference call with the
City to discuss the report, including any outstanding issues/defect fixes and a plan to resolve them.
Table 1: Defect Descriptions
Severity Description
1
Critical
A Severity 1 defect means that the process does not work as defined in the accepted design specification
and the process is stopped with no workaround. The defect{s) may affect multiple users or frequently
used functions.
2
High
A Severity 2 defect is less severe than a Severity 1 defect but is the result of a significant problem(s). The
defect severely impairs the process and reduces user productivity. No workaround has been identified by
Esri. It could be a major problem that affects a limited number of users or affects functionality not
needed on a daily basis.
3
IVIedium
A Severity 3 defect means that the process has been impaired but has an Esri-recommended
workaround. The user is able to function near the expected productivity level. Internal geodatabase
structures are accurate and maintain their integrity.
4
Low
A Severity 4 defect does not have a significant impact on the process and reflects a minor problem(s).
UAT will be considered complete, and the City will be responsible for providing Esri with written
acceptance ofthe LGIM migration within three business days provided the following condition is met:
• UAT test scripts, as defined in the accepted Test Plan, for the release have been
executed with no remaining Severity 1 or Severity 2 defects.
Esri Deliverables:
• Provide one day of on-site UAT installation and preparation support.
Esri Agreement No. 2015C65 24
• Provide one day of on-site test team training.
• Provide two days of on-site support during UAT.
• Provide five days of remote support during UAT, as necessary.
• Provide up to two revised releases to the ETL migration scripts.
• Provide test results report at the conclusion of UAT.
City Responsibilities:
• Provide the hardware and meeting space required for the UAT training class.
• Provide testing staff with the appropriate pre-requisite skill set.
• Provide testing staff with a copy of the accepted Test Plan.
• Ensure system administrator, database administrator and IT support staff are available
during the UAT period as required by Esri.
• Conduct UAT based on the accepted Test Plan over a period of seven business days.
• Report defects to Esri daily.
• Provide Esri with written acceptance ofthe ETL migration scripts within three business
days if UAT is passed based on the acceptance criteria specified in the accepted Test
Plan.
Task 1.4.2 Production Environment Installation
The deployment of a completed release into the City's production environment for operational use can
be initiated after UAT is complete and the City has provided Esri with written acceptance.
Esri will travel to the City's offices in Carlsbad, CA for a period of two consecutive business days to guide
City staff in the installation and configuration ofthe following:
• Final LGIM migration data
• ETL Software
• ETL Scripts
• QA/QC software
• QA/QC scripts
The City is responsible for providing Esri with written acceptance ofthe delivered LGIM in the
production environment within two business days of completing the deployment.
Esri Deliverables:
• Final LGIM migrated data
• Assistance in Configuring the ETL migration scripts.
• Assistance in running the ETL scripts.
Esri Agreement No. 2015C65 25
• QA/QC software. Data Reviewer extension for ArcGIS for Desktop 10.1.
• Assistance in configuring the QA/QC scripts.
• Assistance in running the QA/QC scripts.
City Responsibilities:
• Provide properly configured production environment in accordance with the accepted
Deployment Plan.
• Provide access to the City's production environment as required by Esri.
• Ensure system administrator, database administrator and IT support staff are available during
this task as required by Esri.
• Provide Esri with written acceptance of the production environment installation within two
business days of completing the deployment.
Task 2 Assess Requirement, Design, and Modify Existing LGIM Datasets for Newly
Acquired Wastewater and Water (Potable/Recycled) Facility Data
The objective of this task is to extend the LGIM schemas for water and wastewater created in
Task 1 to incorporate the newly acquired wastewater and water (potable/recycled) Facility
assets based on the documented user requirements.
Task 2.1 Assess requirements for new facility assets
In this task, Esri will review the documented user requirements for the new facility assets for
wastewater and water (potable/recycled) and the current data for these assets stored in MS
Excel attribute spreadsheets by facility site number. Esri will then recommend an approach to
incorporate the new assets into the database that meet user requirements while also following
best practices in the water and wastewater industry.
Task 2.1.1 Facility Data Requirements Workshop
The City will make available to Esri a current copy ofthe MS Excel attribute spreadsheets
containing the Facility asset data and the documented user requirements at least 10 business
days before the Facility Data Requirements Workshop. Esri will review this information before
conducting an on-site Facility Data Requirements Workshop with the City. Esri will travel to the
City's offices in Carlsbad, CA to conduct a two day on-site Facility Data Requirements Workshop
with the City's GIS and IT staff to determine the best method for incorporating the data of the
new assets into the geodatabase that satisfies the requirements ofthe city users.
In the workshop, Esri will:
Esri Agreement No. 2015C65 26
• Review the user requirements for how the new assets will be queried and displayed in
desktop, web-based, and mobile applications.
• Address how the Infor/Hansen work order management system can process work
orders to the assets.
• Discuss how the new asset data and the other asset data in the LGIM can be analyzed
for long-range analytics and planning studies.
• Identify feature classes and attributes that can store the asset data to extend the City's
LGIM schema.
Esri Deliverables:
• Two-day on-site Facility Data Requirements Workshop.
City Responsibilities:
• Communicate project needs and priorities to the Esri consultant.
• Provide appropriate management and technical staff to participate in the on-site
workshop activities.
• Provide Esri with all required information on business processes, GIS applications, GIS
services, data sources, workflows, and geodatabases while Esri is on-site.
• Identify and schedule the appropriate City staff to attend the Facility Data Requirements
Workshop.
• Provide a conference room equipped with an SVGA LCD projector. This conference
room should be large enough to host the workshop activities.
• Send a current copy of the MS Excel attribute spreadsheets containing the Facility asset
data and the documented user requirements to Esri at least 10 days before the Facility
Data Requirements Workshop.
Assumpt/ons;
• A copy of the MS Excel attribute spreadsheets containing the Facility asset data and the
documented user requirements will be sent to Esri at least 10 days before the Facility
Data Requirements Workshop.
Task 2.1.2 Facility Data Requirements Design
Based upon the results ofthe Facility Data Requirements Workshop, Esri will prepare a Data
Mapping Matrix for Facility assets. The Data Mapping Matrix will be in a Microsoft Excel
spreadsheet format and include the following:
• Additional feature classes and attributes that will need to be added to the LGIM based
upon the workshop findings
• Documented changes to LGIM domains, subtypes, and relationship classes if applicable
Esri Agreement No. 2015C65 27
Esri will prepare a Draft Data Mapping Matrix and submit it to the City for review and comment.
Following receipt, the City will have three business days to review the draft and provide Esri with
consolidated, written comments that have been reviewed and approved by the City project manager.
Upon receipt of the City's comments, Esri will conduct a two-hour webcast to review the draft data
mapping matrix, including the City's comments. Esri will incorporate changes, as mutually agreed, and
deliver a final version of the Data Mapping Matrix. The City is responsible for providing Esri with written
acceptance ofthe final Data Mapping Matrix within two business days of receipt.
£sr/ Deliverables:
• Draft Data Mapping Matrix for Facility assets.
• Conduct two-hour webcast to review the draft Data Mapping Matrix for Facility assets
and City comments.
• Final Data Mapping Matrix for Facility assets.
City Responsibilities:
• Address follow-up questions as required by Esri.
• Review the draft Data Mapping Matrix and provide Esri with consolidated written
comments within three business days of receipt.
• Participate in two-hour webcast to review draft Data Mapping Matrix.
• Provide Esri with written acceptance ofthe final Data Mapping Matrix within two
business days of receipt.
Task 2.2 Modify the LGIM-Based Schema for the New Assets
The objective of this task is to create a script or scripts that will modify the LGIM-based schema
created in Task 1 to incorporate the new Facility assets in a test environment.
Task 2.2.1 Update Test Environment
Esri will update the test environment at the Esri offices in Redlands, California created in Task 1
and assist the City in updating the development/test environment at the City's offices in
Carlsbad, California by helping with the installation of the ETL software and QA/QC software.
These test environments will support the creation and testing of extraction, transformation,
and loading (ETL) scripts, data migration scripts ifapplicable, data reviewer scripts, and any
additional QA/QC scripts (if applicable). The purpose of the test environment at Esri is to
provide a controlled environment that mimics the City's test and production environment as
closely as possible to test the functionality ofthe scripts before testing them in the City's
test/quality assurance environment.
Esri Agreement No. 2015C65 28
Task 2.2.2 ETL Development and Migration
Based on the accepted Data Mapping Matrix for Facility assets, Esri will create the data loading/
ETL scripts. Esri will then run the scripts in its test environment to create the new assets in the
City's LGIM schema and to load data to it from the current Excel spreadsheets.
Esri will conduct webcast Development Review Meetings during this subtask to elicit comments
and inform the City on the status ofthe task. The frequency ofthe webcast Review Meetings
will be mutually agreed upon by Esri and the City.
Esri Deliverables:
• Development Review Meeting(s) [via webcast] with the City as mutually agreed upon.
Migrated data of Facility asset data into LGIM database in Esri's test environment
City Responsibilities:
• Ensure appropriate resources are available to participate in Development Review
Webcasts as mutually agreed upon.
• Send the most current copy of the City's geodatabase and the Microsoft Excel
spreadsheets with Facility asset data to Esri to use for internal testing on Esri's test
environment.
Assumpt/ons;
• If there isn't a development environment at the City, then the test environment at the
City will be used as an initial development environment and then will be reinstalled
using the Deployment Plan for UAT.
Task 2.3 Load the New Data to the Modified LGIM-Based Schema
The objective of this task is to load the data from the Facility asset spreadsheets to the new
feature classes created in the LGIM. The data will then be reviewed for QA/QC and go through
an IAT and UAT process before production implementation.
Task 2.3.1 Assess Conversion Quality and Generate Reports
In this task, Esri will assess the quality and accuracy ofthe conversion, and generate reports on
the resulting inventory data gaps, e.g. empty LGIM feature classes/fields, native Carlsbad data
migrated "as-is", and other discrepancies in the LGIM version ofthe database resulting from
the migration.
1. Test Plan
Esri will initiate development ofthe Test Plan including Test Scripts upon completion ofthe
deliverables specified in Task 2.1.2.
Esri Agreement No. 2015C65 29
Esri will prepare a Test Plan that will identify procedures, types of testing, and test strategy to
be used for acceptance ofthe migration ofthe City's geodatabase to its configured LGIM
schema with Facility asset data during the IAT and UAT tasks described below. The Test Plan
will include Test Scripts and identify the criteria that the City will use to determine acceptance
ofthe configured LGIM schema with Facility asset data. The Test Plan will include the following
content:
Schedule of testing activities
The types of test or testing cycles that will be completed prior to and during UAT, and
their location
Testing logistics for Esri internal testing activities and those conducted during UAT
Specifications for the testing environment(s) that will be used
Roles and responsibilities during testing
Test reporting
User acceptance criteria
Corrective action procedures
The Test Scripts within the Test Plan will include:
• List of Test Scr/pts—This is a listing of the tests that will be executed to verify that the
migrated LGIM with Facility asset data meets the City's acceptance criteria
• Content of each test scr/pt—Instructions of how to conduct the test, including
information such as specific sequence of steps, environment, variables, and pre/post
conditions
Esri will deliver the draft Test Plan to the City. Following receipt, the City will have three business days
to review the draft and provide Esri with consolidated, written comments that have been reviewed and
approved by the City's project manager. Upon receipt ofthe City's comments, Esri will conduct a two-
hour webcast to review the draft Test Plan, including the City's comments. Esri will incorporate changes,
as mutually agreed, and deliver a final version. The City is responsible for providing Esri with written
acceptance ofthe final Test Plan within two business days of receipt.
Note: Written acceptance of the Test Plan by the City is a pre-condition for Esri to proceed with IAT and
UAT.
Esri Deliverables:
• Draft Test Plan.
• Two-hour webcast to review the draft Test Plan.
• Final Test Plan.
City Responsibilities:
• Ensure that appropriate management and technical staff participate in the Test Plan
review webcast.
Esri Agreement No. 2015C65 30
• Review the draft Test Plan document and provide Esri with consolidated written
comments within three business days of receipt.
• Provide Esri with written acceptance ofthe final Test Plan document within two
business days of receipt.
2. Internal Acceptance Testing (IAT)
IAT can be initiated once the ETL scripts are functionally complete and meets IAT test entry criteria as
specified in the accepted Test Plan. The objective of IAT is to confirm that the LGIM migration complies
with the accepted Test Plan prior to delivering the migrated data of facility assets to the City for UAT.
IAT will implement the same procedures that the City will use during UAT in an environment that
replicates the City's environment as closely as possible.
Esri will conduct IAT at Esri offices in Redlands, California. The test scripts contained in the accepted
Test Plan will form the basis ofwhether the migrated LGIM passes the IAT process.
During IAT, Esri's test team will log defects in Esri's defect tracking system. Esri will review defect
reports and identify those that require defect fixes for resolution. Where appropriate, defect fixes will
be made and regression tested during IAT.
At the conclusion of IAT, Esri will compile an IAT test report documenting the results ofthe IAT. The IAT
test results report includes:
• Summary of the testing approach
• Recommendation on readiness to proceed with UAT
• Test results, including pass/fail decision for Test Scripts, and list of defects
Esri will conduct a two hour IAT review meeting, via webcast, with the City to review the IAT test results
report, including the readiness ofthe Facility asset data to LGIM migration scripts for UAT in the City's
test/quality assurance environment.
Once the ETL migration scripts are ready for UAT, Esri will create and deliver a release package to the
City for deployment in the City's Test/Quality Assurance environment for UAT. The release package will
include:
• Quality control reports
• Facility asset data migrated to the LGIM database
• ETL Scripts
• QA/QC scripts
• Release notes
• Installation instructions
IAT will be deemed complete when all IAT test scripts have been executed and defect thresholds in the
acceptance criteria as defined in the accepted Test Plan have not been exceeded.
Esri Agreement No. 2015C65 31
Esri Deliverables:
• Facility asset data migrated to LGIM
• IAT test results report.
• Remote two hour IAT review meeting, via webcast, with the City.
• Release package that will be used for UAT.
City Responsibilities
• Participate in the remote IAT review meeting.
Esri will deliver and install on the City's system the ETL tools and source code used in the
migration. This will be done in the Test/Quality Assurance (OA) environment for the UAT and in
production for implementation.
Task 2.3.2 User Acceptance Testing (UAT)
Esri will deliver and assist in the installation on the City's system the migrated data and ETL scripts used
in the migration. This will be done in the Test/Quality Assurance (QA) environment for the UAT.
The objective of UAT is for the City to test the Facility asset data to LGIM migration to confirm that it
meets the acceptance criteria as defined in the accepted Test Plan.
To initiate UAT, Esri will travel to the City's office in Carlsbad, California for a period of three consecutive
business days. Esri will assist in the installation ofthe migrated geodatabase, ETL Scripts, and QA/QC
scripts in the City's Test/QA environment and prepare the environment for UAT.
Immediately following the UAT environment deployment, Esri will provide the City's test team with a
half-day training class on how to test the migration based on the accepted Test Plan.
Following the UAT test team training class, the City will test the LGIM migration to verify that it functions
in accordance with the accepted Test Plan. The City will record discrepancies, if any, using the defect
reporting mechanism as specified in the accepted Test Plan. UAT will be conducted over a period of
three business days. Esri will provide one day of on-site support and two days of remote support during
UAT.
During UAT, the following procedures will be used to review and validate any reported discrepancies:
1. When the test team members for the City finds a discrepancy that they believe is a
migration defect, they will verify with another team member before reporting the issue
to Esri. The City will document the steps needed to reproduce the problem using an
agreed to defect reporting template. Esri will then work to validate the discrepancy. If
Esri can validate the discrepancy, it will be recorded as a defect and classified as one of
four defect severity levels (reference the descriptions in Table 2 below).
Esri Agreement No. 2015C65 32
2. If Esri cannot validate the discrepancy, the City testing team will either provide more
information or demonstrate how and where the discrepancy occurs. Based on this information,
Esri will work to further identify the source of the discrepancy. Esri may determine that the
discrepancy is not an ETL script problem but instead a problem with data, the network, or a
misunderstanding about how the data will be converted.
3. If Esri cannot replicate a reported discrepancy, if the City test team cannot demonstrate it, or if
it is determined by Esri that the discrepancy has another cause not related to Esri-supplied
application software, then Esri will notify the City's test team that the problem is not an ETL
script defect and identify the cause ofthe defect. If appropriate, Esri will recommend an action
to take, for example, to reload certain data into the geodatabase.
The City will send daily defect reports to Esri based on a mutually agreed-on format. Esri will use its
internal defect-tracking application to capture and prioritize defects and enhancements.
During UAT, the City's testing team and Esri will hold daily defect review meetings or conference calls to
review the open defects and associated severity. At the conclusion of UAT, Esri will create a software
test report documenting the result of UAT. The Esri project manager will lead a conference call with the
City to discuss the report, including any outstanding issues/defect fixes and a plan to resolve them.
Table 2: Defect Descriptions
Severity Description
1
Critical
A Severity 1 defect means that the process does not work as defined in the accepted design specification
and the process is stopped with no workaround. The defect(s) may affect multiple users or frequently
used functions.
2
High
A Severity 2 defect is less severe than a Severity 1 defect but is the result of a significant problem(s). The
defect severely impairs the process and reduces user productivity. No workaround has been identified by
Esri. It could be a major problem that affects a limited number of users or affects functionality not
needed on a daily basis.
3
Medium
A Severity 3 defect means that the process has been impaired but has an Esri-recommended
workaround. The user is able to function near the expected productivity level. Internal geodatabase
structures are accurate and maintain their integrity.
4
Low
A Severity 4 defect does not have a significant impact on the process and reflects a minor problem(s).
During UAT, Esri will fix mutually agreed to defects and issue revisions to the ETL scripts release to City.
Esri will provide workarounds for any Severity 3 and 4 defects identified.
Esri Agreement No. 2015C65 33
UAT will be considered complete, and the City will be responsible for providing Esri with written
acceptance ofthe Facility asset data to LGIM migration within three business days provided the
following condition is met:
• UAT test scripts, as defined in the accepted Test Plan, for the release have been
executed with no remaining Severity 1 or Severity 2 defects.
£sr; Deliverables:
• Provide one-half day of on-site UAT installation and preparation support.
• Provide one-half day of on-site test team training.
• Provide one day of on-site support during UAT.
• Provide two days of remote support during UAT, as necessary.
• Provide up to two revised releases to the ETL migration scripts.
• Provide test results report at the conclusion of UAT.
City Responsibilities:
• Provide the hardware and meeting space required for the UAT training class.
• Provide testing staff with the appropriate pre-requisite skill set.
• Provide testing staff with a copy of the accepted Test Plan.
• Ensure system administrator, database administrator and IT support staff are available
during the UAT period as required by Esri.
• Conduct UAT based on the accepted Test Plan over a period of three business days.
• Report defects to Esri daily.
• Provide Esri with written acceptance ofthe within three business days if UAT is passed
based on the acceptance criteria specified in the accepted Test Plan.
Assumpt/ons;
• The ETL software (Data Interoperability extension for ArcGIS for Desktop) installed in
Task 1 will be used by the ETL scripts.
• The QA/QC software (Data Reviewer extension for ArcGIS for Desktop) installed in Task
1 will be used by the QA/QC scripts.
Task 2.3.3 Production Environment Installation
The deployment of a completed release into the City's production environment for operational use can
be initiated after UAT is complete and the City has provided Esri with written acceptance. Based on
defects reported by the City, Esri will revise the migration and QA/QC scripts and perform a final Facility
assets migration. Esri will create QA/QC reports and deliver them along with the final Facility assets
migrated data to the City.
Esri Agreement No. 2015C65 34
Esri will travel to the City's offices in Carlsbad, CA for a period of one consecutive business days to assist
in the installation and configuration ofthe following:
• Final Facility assets migrated data
• ETL Scripts
• QA/QC scripts
The City is responsible for providing Esri with written acceptance ofthe migrated data in the production
environment within two business days of completing the deployment.
£sr/ Deliverables:
• Final Facility assets migrated data
• Install the ETL migration scripts.
• Install the QA/QC scripts.
The City's Responsibilities:
• Provide properly configured production environment.
• Provide access to the City's production environment as required by Esri.
• Ensure system administrator, database administrator and IT support staff are available during
this task as required by Esri.
• Provide Esri with written acceptance of the production environment installation of the migrated
data within two business days of completing the deployment.
Esri Agreement No. 2015C65 35
t
EXHIBIT "B"
PAYMENT SCHEDULE
Invoice
Event
Task Description Payment ($)
1 Project Initiation and Kickoff Meeting (Task 1.1.1) 17,000
2 Data Mapping Workshop (Task 1.1.2) 15,000
3 Delivery of Final Test Plan (Task 1.3.1) 20,000
4 Production Environment Installation (Task 1.4.2) 25,000
5 IAT Test Results Report (Task 2.3.1) 25,000
6 Production Environment Installation (Task 2.3.3) 15,000
7 Withhold for Final Acceptance (10%) 13,000
Total Agreement Amount 130,000
Esri Agreement No. 2015C65 36