HomeMy WebLinkAbout241034 MINER MINER - CONTRACT - RFP - P916 GIS RELATED APPLICATION DEVELOPMENTa
PROFESSIONAL SERVICES AGREEMENT
THIS AGREEMENT made and entered into the day and year set forth below, by and
between THE CITY OF FORT COLLINS, COLORADO, a Municipal Corporation, hereinafter referred
to as the "City" and Miner & Miner, Consulting Engineers, Inc. hereinafter referred to as
"Professional".
WITNESSETH:
In consideration of the mutual covenants and obligations herein expressed, it is agreed by
and between the parties hereto as follows:
1. Scope of Services. The Professional agrees to provide services in accordance with
the scope of services attached hereto as Exhibit "A", consisting of nine (9) pages, and incorporated
herein by this reference.
2. Time of Commencement and Completion of Services. The services to be performed
pursuant to this Agreement shall be initiated within one -hundred -twenty (120) days following
execution of this Agreement. Services shall be completed no later than September 30, 2004. Time
is of the essence. Any extensions of the time limit set forth above must be agreed upon in writing by
the parties hereto.
3. Early Termination by City. Notwithstanding -the time periods contained herein, the
City may terminate this Agreement at any time without cause by providing written notice of
termination to the Professional. Such notice shall be delivered at least fifteen (15) days prior to the
termination date contained in said notice unless otherwise agreed in writing by the parties.
All notices provided under this Agreement shall be effective when mailed, postage prepaid and sent
to the following addresses:
PSA 05/01
1
1.1.3.4 Define Parcel QA Process
In this task, the M&M PM and the City will define how the Parcel
information from the CAD tiles will be QAed in the geodatabase.
Deliverables: On -Site requirements gathering of Parcel QA process
(M&M, City)
1.1.3.5 Define Topology QA Process
In this task, the M&M PM and the City will define how the topology
of the Parcels from the CAD files will be QAed in the geodatabase.
Deliverables: On -Site requirements gathering of topology QA process
(M&M, City)
1.1.3.6 Document Functional Requirements
In this task, the M&M PM will gather all of the requirements gathered
into the Parcel Maintenance fools requirements document.
Deliverables: Parcel Maintenance Tools requirements document
(M&M)
1.1.3.7 Review Functional Requirements Document
In this task, the City will review the requirements document and
provide comments back to M&M on them.
Deliverables: Comments on the Parcel Maintenance Tools
requirements document (City)
1.1.3.8 Revise Functional Requirements Document
In this task, the M&M PM will revise the requirements document
based upon the comments received from the City.
Deliverables: Revised Parcel Maintenance Tools requirements
document (M&M)
1.1.3.9 Deliver Functional Requirements Document
This Milestone marks the end of the Design Phase of the Project. This
milestone is reached with the delivery of the revised Parcel
Maintenance Tools requirements document to the City.
1.2 Prototype Phase
This series of tasks will produce a set of Parcel Maintenance Tools that closely adhere to
the requirements specification defined in the Design Phase. These tools will be
demonstrated to the City on -site. Comments from the City will be incorporated into the
requirements document after the demonstration.
1.2.1 Prepare Development Environment
This task allows both the City and M&M to prepare the development environment
in which the tools will be built. M&M will build and test the tools using the
City's GIS data ensuring that upon delivery the tools will work as specified in the
requirements document.
1.2.1.1 Package Data for Delivery
In this task, the City will prepare all necessary data to develop the
Parcel Maintenance Tools into a package and deliver the package to
M&M.
Deliverables: Deliver data to M&M (City)
1.2.1.2 Load Data into Development Environment
In this task, an M&M Database Analyst will load all data delivered
from the City into the development environment.
Deliverables: Development environment ready for use at M&M
(M&M)
1.2.2 Develop Prototype Tools
During this series of tasks M&M will develop the prototype tools for loading
parcel data into the Geodatabase and performing QA on the resulting features.
1.2.2.1 DWG/DXF to Geodatabase Import
This set of tools will process the CAD file and import the various
layers into the Geodatabase as defined in the requirements document.
Parcel data will be loaded into the Parcel Framework and TaxParcel
polygon feature classes, Boundary and Easement line feature classes,
and City -defined annotation classes. Address data will be loaded into
the Address and Subaddress point feature classes, the Street line
feature class, and the address range tables.
Deliverable: Prototype DWG/DXF to Geodatabase import tool
(M&M)
1.2.2.2 Address QA Tools
This set of tools will allow the City to perform QA checks on the data
that was imported into the Address dataset in the geodatabase as
defined in the requirements document.
Deliverable: Prototype Address QA tool (M&M)
1.2.2.3 Parcel QA Tools
This set of tools will allow the City to perform QA checks on the data
that was imported into the Parcel dataset in the geodatabase as defined
in the requirements document.
I Deliverable: Prototvpe Parcel OA tool (M&M) I
1.2.2.4 Topology QA Tools
This set of tools will allow the City to perform QA checks on the
topology of the data that was imported into the Parcel dataset in the
geodatabase as defined in the requirements document.
Deliverable: Prototype Topology QA tool (M&M)
1.2.3 Prototype Demonstration
M&M will travel to the City and demonstrate the tools to City staff. The
demonstration will clearly outline how the tools meet the functional and business
requirements and allow the City to provide feedback on the development effort.
Optionally, the City may travel to M&M for the demonstration.
Deliverable: Demonstration of Prototype Parcel Maintenance Tools (M&M)
Conference Facilities (including digital projector) (City)
1.2.4 Review Parcel Maintenance Tools Requirements Document
The City will review the Parcel Maintenance Tools requirements document after
the demonstration of the prototype tools. This review will be accomplished with
the M&M Project Manager, allowing for the City to provide feedback on the
prototype tools and refine the requirements as necessary.
Deliverable: Review of Requirements Document (M&M, City)
Conference Facilities (including digital projector) (City)
1.2.5 Revise Parcel Maintenance Tools Requirements Document
In this task, the M&M Project Manager will update the requirements document to
reflect the results of the requirements review meetine.
Deliverable: Revised Requirements Document (M&M)
1.2.6 Deliver Final Parcel Maintenance Tools Requirements Document
This milestone marks the completion of the Prototype Phase. The Milestone
occurs when the revised parcel maintenance tools requirements document is
delivered to the City.
1.3 Develop and Deploy Phase
This series of tasks will produce the final Parcel Maintenance Tools adhering to the
revised requirements specification from the Prototype Phase. These tools will be fully
tested and documented at M&M during the factory acceptance tests (FAT). Final
acceptance of the tools by the City will occur after the tools have passed site acceptance
testing (SAT) at the City.
1.3.1 Develop Final Tools
During this series of tasks the City and M&M will development a series of test
plans to ensure the Parcel Maintenance Tools meet all required functionality.
1.3.1.1 Develop Test Plans based on Requirements Document
Using the Functional Requirements document as a guide, the City will
develop a series of test plans that will be used to test the Parcel
Maintenance tools. These plans will be used in the factory acceptance
testing and the site acceptance testing. Once the tools pass these tests
at the city, both parties will consider the tools acceptable.
Deliverable: Draft Test Plans (City)
1.3.1.2 Review Test Plans
M&M will review and provide feedback on the test plans. This review
will ensure that the test plans are focused on the specific functionality
of the Parcel Maintenance tools, while not disabling other GIS
functions.
Deliverable: Comments on Test Plans (M&M)
1.3.1.3 Revise Test Plans
The City will incorporate comments from M&M into the final version
of the test plans and provide them to M&M.
Deliverable: Revised Test Plans (City)
1.3.1.4 Deliver Final Test Plans
This Milestone marks the completion of the test plan development.
The milestone is reached when the City delivers the final test plans for
the Parcel Maintenance tools to M&M.
Deliverable: Final Test Plans (City)
1.3.2 Develop Final Tools
During this series of tasks M&M will finish the development and documentation
of the Parcel Maintenance Tools for loading parcel data into the Geodatabase and
performing QA on the resulting features.
1.3.2.1 DWG/DXF to Geodatabase Import
This set of tools will process the CAD file and import the various
layers into the geodatabase as defined in the requirements document.
Deliverable: Final DWG/DXF to Geodatabase import tool (M&M)
1.3.2.2 Address QA Tools
This set of tools will allow the City to perform QA checks on the data
that was imported into the Address dataset in the geodatabase as
defined in the requirements document.
I Deliverable: Final Address OA tool (M&M) I
1.3.2.3 Parcel QA Tools
This set of tools will allow the City to perform QA checks on the data
that was imported into the Parcel dataset in the geodatabase as defined
in the requirements document.
Deliverable: Final Parcel OA tool (M&M)
1.3.2.4 Topology QA Tools
This set of tools will allow the City to perform QA checks on the
topology of the data that was imported into the Parcel dataset in the
geodatabase as defined in the requirements document.
I Deliverable: Final Tonoloav OA tool (M&M) I
1.3.3 Factory Acceptance Testing
M&M will perform Factory Acceptance Testing (FAT) on all tools developed.
This testing will be performed according to a set of documented test plans, agreed
to by both the City and M&M. M&M will resolve issues as they appear during
the FAT.
Deliverable: Factory Acceptance Testing (performed at M&M) (M&M)
Documentation of Test Results (M&M)
1.3.4 On -Site Acceptance Testing
M&M will support the City in the performance of Site Acceptance Testing (SAT)
on all tools developed. This testing will be performed according to the
documented test plans, agreed to by both the City and M&M. M&M will resolve
issues as they a ear during the SAT.
Deliverable: Support Site Acceptance Testing (performed at the City) (M&M)
Documentation of Test Results (City)
1.3.5 User Training
This training will be done through a user workshop setting in support of the on -
site acceptance testing. An M&M Analyst will work with City employees to
ensure -that the City has a through understanding of the tool functionality and how
to make use of that functionality.
Deliverable: One day of an M&M Analyst on -site working with City employees
in a workshop setting (M&M)
1.4 Final Delivery Complete
This Milestone marks the completion of the Project. The Milestone occurs when the
rollout task is completed.
1.5 Acceptance
1.5.1 Deliverable Review.
All deliverables submitted to the Client shall be reviewed and checked within
two weeks of delivery. The Contractor shall be notified in writing of any
pending delays in the review periods. Should Client fail to notify Contractor in
writing within two weeks, these deliverables shall be deemed accepted.
1.5.2 Compliance.
All reviews will be performed on the basis of work correctness and compliance
with the contract. The Client reserves the right to return for correction within
these approximate review periods any and all products that are in error or have
not been prepared within the scope of work; unless otherwise notified in writing,
these corrections will be incorporated in another work task submittal.
1.5.3 Classification of Deliverables.
After initial review, deliverables will be classified as follows:
1.5.3.1 Deliverable Accepted
Shall be defined as a deliverable conforming to the Statement of Work
or meeting specifications, with no more than minor and/or isolated
exceptions or nonconformities, in which case the Client will take
responsibility for correction and will so inform the Contractor.
1.5.3.2 Deliverable Accepted With Rework
That is, essentially to specification, but having a significant number of
isolated exceptions, and accepted pending re-editing and correction by
the Contractor. The Contractor shall re-edit the work for indicated errors
and resubmit within 30 days. The Client will rerun its acceptance checks
for the classes of errors detected in the initial check and will reclassify
the deliverables as whether ACCEPTED or REJECTED.
1.5.3.3 Deliverable Rejected
Shall be defined as a deliverable failing to conform to the Statement of
Work or to meet specification, in ways that indicate that major
improvements in performance and/or procedure are needed to avoid
recurrence. The Contractor shall rework the deliverable generally,
including all quality checks, and resubmit to the Client within 30 days, at
which time the Client will rerun its acceptance check and reclassify the
work.
1.5.3.4 Client Delays
Client must exercise due diligence and shall ensure that factors beyond
the control of the Contractor, such as Client delays and failure to fulfill
Client responsibilities, will not interfere with Contractor's ability to
complete the services. Client shall notify Contractor of any such factors
that may cause delays in the completion of tasks or changes to the scope
of work, and both parties will mutually determine required modifications
to this Agreement.
1.5.3.5 Final Acceptance and Certification
At the conclusion of project acceptance, Contractor will request that
Client sign an acceptance certificate. Client production use of any given
application prior to receipt of an acceptance certificate shall constitute
acceptance on part of the Client. Production use shall be defined as the
use of the application in an environment that includes Client's system of
record database. Once final acceptance is given on any deliverable, any
further modifications required of Contractor for that accepted deliverable
shall result in a change in scope. Changes to scope must be agreed to in
writing by both parties.
Optional Tasks
1.6 Formal End User Training
This set of tasks allows for the creation of end -user training material, review & revision
of the material with the City, and training of the users.
1.6.1 Develop Custom Training Material
In this task an M&M Trainer will review the tools built and create a series of
lectures and exercises designed to teach the end -user how to load parcel data into
the aeodatabase.
Deliverable: Training materials for the Parcel Maintenance Tools (M&M)
1.6.2 Review Material with the City
In this task an M&M Trainer will review the lectures and exercises with City
personnel and receive comments back on it. The M&M Trainer will modify the
training material based upon mutually agreed upon alterations.
Deliverable: Review of training materials (M&M, City)
Final training materials for the Parcel Maintenance Tools (M&M)
1.6.3 User Training Class
In this task an M&M Trainer will lead a series of lectures and exercises with City
personnel, training them in the use of the Parcel Maintenance Tools.
Deliverable: User training class (M&M, City)
Conference Facilities (with a digital projector) (City)
10
OwM1e
NMnbw
Task Name
OuWbn
CAet
,kate
08 4!ffi SR ISO ISMSI&MI S130 I 6f8 I Bn3 1 620 1 (17 1 714 7n1 7nO 7MS
8f1 8I8
t
1
Parom Malrwll eTools
6"el"s
et R coo"
Li1iM CIu of R COW"
L$[aY aRCow"
LWaI qy dRCaNbu
ofR Cow"
�yof R Comm
,Chy Of PtComm
LliiM of R CaWwe
,CRy of Rcoukm
pM,t2lY of R Coons
PM,ChYor R Coda :.
Ps4.CRY of R Crain
PM
gRComm
PM
of Ft Comm
M OaMF-ss An*jg
-
PMy4Px.J
PS1�9112 .
Assyrt,N6Y PMp91ij
YPM.M6M Anoly$t,Chy of R COWM
at RComo
PM
: - 5
dR Caubm
PM
of p Caonw
6f22
A"Wasm PM(16Yi
2
1.1
Osmgn Pfiam(Phw 1)
Tftp
$ XWW
3
,.1.1
PmJW Kickoff Mes"
025 days
SWOD
1.1.2
PAview Ourrom Precwd s
i dry
St,S80.OD
1,12.1
Review CWWA DWGIDXF Fromm
0,12 aye
$16320
1,122
fyaview OWG+D% OA Proces9e80.13dap
$176,W
1,12.2
ReviewOWGN%F to Coverage Oran025
d"s
00
Ko4
1A.2.4
ReviewAdit= QA Pracoea
0.18dap
$176.80
/.12b
Revew P✓PoW OA Pfoom
0.12 days
18320
1.12.6
Review Topoobgy QA Pr S
025ap
$$MOD
1.1.3
Defkro Armi66 Prwcess
A75 days
S2,7aRAD
12
/ 1.8.1
OBflne DW FQ0. Proo9aeea
028 dye
$34000
13
1.13.2
Da61e DXF to Goodatatm proves f
0.25 d0a
smoo
14
1./.32
D4*w Addraae OAProoe-
0.25ays
$340.OD
15
1.IA41
Deem PrOW QA PronsS
025 days
$w OD
16
1.1.3.5
Do**TopoolbW QA Ptoasss
025 drys
$340A0
17
1.1.3A
DaawnWd Fwr lwim Ragt* metos
, day
t,380.00
13
11.3.7
�..1.1.3
Review FW4'WW F`WgW nenb Doc
3dep
$0,00
13
8
Modify FwlcomMl Regl4 ~ts Doff
0.5 dlyS
$SW..OD
20
1.1.30
Defier FumOmet—F'amems Om
0 days
50.00
7.2
Rafatype Phae(Phwse 2)
26 days
325,790,00
22
t21
Pr4Pwr 1 Doveupwmrd EaWonnmd
Sdap
S1,2WA0
23
12.1 i
Package Dau far Oe6ery
8 ap
-waD
24
12,1.2
toad data W Dsyslapmem Erwkow
t ay
$I,molf
25
122
Dwaiep Proeoeype Teals
16 dqa
SZ45"OO
25
1.22.1
OvyCdDXF la GeodN�e Import
S dys
S AWIN0
2/
1222
3daye
28
122$
PAVOW CQAProasa
PMce1 QA Process
Sap
$4,5WAU
S4,SOOAO
20
—1224
..�..—. Topology QA Pro
4 dip
$OAOD00
3D
1.2.3,
._
Pwtatype Demm�Ma W -
QB dye
$12KOD
M
124
Peview Pameiw Mnwro Tows Paqu
�
3dsp
$O.OD
32
1.2.5
— Modify Parcel Tools Bmp* n
0.5 do"
sm.00
Sa
1.2.8
Delver Fvml Parcq kAekoermrics Tode Re
0 ap
SOeb
34
"1
DevtlopOwDept" Phaae(p1Ye3)
tA$dwp
$22.i4RDD
35
ISt
Dewlap Teat Puna
t5 dap
S600O
36
13.1A
Teal Plan W6ed an Repukf
3dep
SOOD
37
1.3t.2
PAVIDW Tact Kam
O.Sdtys
5680.00
36
1.3.1.3
AWN Tom Raps
I day
$0.00
30
1.31.4
Drawer RAW TOM pma
O day5
$0.0D
40
142
Oewup F%M TOou
t0d4yw
51$,N0,D0
1
1,3.2.1
OWGtDXFb GoodaUbm kllpatt
Sapwpm
Pmjy Parcel mwnwwm_v2
Date, M12129M
Task maesbww + Exa mf Tamd
�d .... • 1. • � , . • , . • Slmtnary mlastorm
PropreEB Project $tmmty ^ Dm&*
Pop 1
io
a.m
1.32
Takr-o
CA2 Pa
p,rpyyr
2dap
caM
,720
4ma
U2 Sa we 62a sm
:
-
SIM SM 6mAwryr,7176 72m d9
MAM �1�1
M pwtVAJ
AaaMt,M6M PM[/67y
A"MVA,M6MPM .:
dR COWAVAA NAnMIW
UM AwMW.CLLy of R COMM
- `7/12
TnNw,MaMY R�2s%7
Trrssr,C6yd RCo6ba,
MMa TnYw.C6yd R COMM_
3
13
W Po
2 dNya
f2.728.OD
44
1.32A
Tapoloq Qh Pr62vae
3 *0
f4XZOD
46
1.3-3
Far 1 Ac W,m Te6Wp
2daya
$A40.o0
46
1.3.4
Aooplarrf8 T4aNrp
2dM
f2.3W.aD
d7
1.9.6
Vser Tmkig
day
/,ia0.00
1.4
FkW oef ery CarnPWe
—Oda"
iom
49
50
1S
qw Ml T-w-
6
R4 .A0
61
141
Famm Z" Um Trow"
6 dpa
sli; :66
52
fb,1.1
OBVB♦OAQr6W--r-k"M.W4.1
4dM*
f8 .00
53
iS.12
RVAM MMnn* wft CNy
1dq
660W
54
13,t.3
User TnkdW CYu
1day
Ty
Proiecl: Parch Makae -Q
D9*: Mw /2Qa03
Task
SON
....
Progress
NMUMrr
st"Mmy
Pfo}aol
+
a-m"
EdMW Tashi
^ E dww mka `
om*w
Pape 2
Professional:
City:
With Copy to:
Miner & Miner
City of Fort Collins
City of Fort Collins
4701 Royal Vista Circle
Attn: City Clerk
Attn: Marcus Bodig
Fort Collins, CO 80522
PO Box 580
PO Box 580
Fort Collins, CO 80522
Fort Collins, CO 80522
In the event of any such early termination by the City, the Professional shall be paid for services
rendered prior to the date of termination, subject only to the satisfactory performance of the
Professional's obligations under this Agreement. Such payment shall be the Professional's sole right
and remedy for such termination.
4. Desican, Project Indemnity and Insurance Responsibility. The Professional shall be
responsible for the professional quality, technical accuracy, timely completion and the coordination
of all services rendered by the Professional, including but not limited to designs, plans, reports,
specifications, and drawings and shall, without additional compensation, promptly remedy and
correct any errors, omissions, or other deficiencies. The Professional shall indemnify, save and hold
harmless the City, its officers and employees in accordance with Colorado law, from all damages
whatsoever claimed by third parties against the City; and for the City's costs and reasonable
attorneys fees, arising directly or indirectly out of the Professional's negligent performance of any of
the services furnished under this Agreement. The Professional shall maintain commercial general
liability insurance in the amount of $500,000 combined single limits, and errors and omissions
insurance in the amount of N/A .
5. Compensation. In consideration of the services to be performed pursuant to this
Agreement, the City agrees to pay Professional on a time and reimbursable direct cost basis
according to Exhibit "B", consisting of two (2) pages, and incorporated herein by this reference;
with maximum compensation (for both Professional's time and reimbursable direct costs) not to
exceed Sixty -Four Thousand Four Hundred Dollars ($64,400). Monthly partial payments based
PSA 05/01
2
EXHIBIT "C"
SPECIAL PROVISIONS: INTELLECTURAL PROPERTY RIGHTS
a. Each party reserves the right to use, for any purpose, any programming tools, skills, and
techniques previously acquired, developed or used in the performance of the services described
herein. Nothing in this Agreement shall be construed as restraining either party, their employees,
or agents in the use of the techniques and skills of computer programming and design which
may be utilized or acquired in the course of performance of this Agreement.
b. Professional and City, subject to the terms of this Agreement, agree to joint ownership of
Deliverables. The City further agrees not to market, or sell said Deliverables or prevent
Professional from marketing and selling said product. The City reserves the right to share
Deliverables, at no cost to others, with public agencies within Larimer County.
C. The City shall not make, sell, translate, export, license, sublicense, localize, use with any
time-sharing or for service bureau arrangements, or transmit to any person outside of
Professionals internal business organization the Deliverables.
d. Any patentable or unpatentable discoveries, ideas, including methods, techniques, know-
how, concepts, or products (Invention); or any works fixed in any medium of expression,
including copyright and mask work rights (Works of Authorship); or any other intellectual
property created by Professional during the course of the Services and provision of Deliverables
shall be the sole and exclusive property of Professional.
e. Except as set forth in Section a. above, no direct or indirect ownership interest or license
rights in Inventions, Works of Authorship or other intellectual property including software or
patents are granted or created by implication in this Agreement.
f. Professional may perform the same or similar Services for others, including providing the
same or similar conclusions and recommendations, provided that the City's Confidential
Information is not disclosed.
upon the Professional's billings and itemized statements of reimbursable direct costs are
permissible. The amounts of all such partial payments shall be based upon the Professional's
City -verified progress in completing the services to be performed pursuant hereto and upon the
City's approval of the Professional's reimbursable direct costs. Final payment shall be made
following acceptance of the work by the City. Optional Tasks must be authorized by the City
Representative before proceeding.
6. City Representative. The City will designate, prior to commencement of work, its
project representative who shall make, within the scope of his or her authority, all necessary and
proper decisions with reference to the project. All requests for contract interpretations, change
orders, and other clarification or instruction shall be directed to the City Representative.
7. Monthly Report. Commencing thirty (30) days after the date of execution of this
Agreement and every thirty (30) days thereafter, Professional is required to provide the City
Representative with a written report of the status of the work with respect to the Scope of Services,
Work Schedule, and other material information. Failure to provide any required monthly report may,
at the option of the City, suspend the processing of any partial payment request.
8. Independent Contractor. The services to be performed by Professional are those of
an independent contractor and not of an employee of the City of Fort Collins. The City shall not be
responsible for withholding any portion of Professional's compensation hereunderfor the payment of
FICA, Workers' Compensation, other taxes or benefits or for any other purpose.
9. Personal Services. It is understood that the City enters into this Agreement based on
the special abilities of the Professional and that this Agreement shall be considered as an
agreement for personal services. Accordingly, the Professional shall neither assign any
responsibilities nor delegate any duties arising under this Agreement without the prior written
consent of the City.
PSA 05/01
3
10. Acceptance Not Waiver. The City's approval of drawings, designs, plans,
specifications, reports, and incidental work or materials furnished hereunder shall not in any way
relieve the Professional of responsibility for the quality or technical accuracy of the work. The City's
approval or acceptance of, or payment for, any of the services shall not be construed to operate as a
waiver of any rights or benefits provided to the City under this Agreement.
11. Default. Each and every term and condition hereof shall be deemed to be a material
element of this Agreement. In the event either party should fail or refuse to perform according to the
terms of this agreement, such party may be declared in default.
12. Remedies. In the event a party has been declared in default, such defaulting party
shall be allowed a period of ten (10) days within which to cure said default. In the event the default
remains uncorrected, the party declaring default may elect to (a) terminate the Agreement and seek
damages; (b) treat the Agreement as continuing and require specific performance; or (c) avail
himself of any other remedy at law or equity. If the non -defaulting party commences legal or
equitable actions against the defaulting party, the defaulting party shall be liable to the
non -defaulting party for the non -defaulting parry's reasonable attorney fees and costs incurred
because of the default.
13. Binding Effect. This writing, together with the exhibits hereto, constitutes the entire
agreement between the parties and shall be binding upon said parties, their officers, employees,
agents and assigns and shall inure to the benefit of the respective survivors, heirs, personal
representatives, successors and assigns of said parties.
14. Law/Severability. The laws of the State of Colorado shall govern the construction,
interpretation, execution and enforcement of this Agreement. In the event any provision of this
Agreement shall be held invalid or unenforceable by any court of competent jurisdiction, such
holding shall not invalidate or render unenforceable any other provision of this Agreement.
PSA 05/01
4
15. Special Provisions. Special provisions or conditions relating to the services to be
performed pursuant to this Agreement are set forth in Exhibit "C", consisting of one (1) page,
attached hereto and incorporated herein by this reference.
THE CITY O FORT COLLINS, COLORADO
By:
John IV. Fischbach
City Manager
By: IS O
es B. O'Neill II, CPPO, FNIGP
Director Purchasing & Risk Management
DATE: / I l Lfcl q
l �
I
CVZle rk
`'APPROVE
F M:
AMPIMMUdy Attorney
Inc.
By:
Title: "
C 0 R A tZ fTZEIIRESIDENT OR VI E PRESIDENT
Date
ATTEST: 1/A1 /1
v
Corpooke Secretary Ll
PSA 05/01
(Corporate Sealj!r �N
.4
I JZ
5
EXHIBIT "A"
Project Scope
The goal of the Parcel Maintenance Tools project (the Project) is to provide the City with the
necessary tools to move parcel data from CAD based files into Geodatabase's Parcel and Address
feature classes.
The Project consists of three phases. In the Design Phase M&M and the City will review the
current, `As -Is' procedures for loading CAD data into the GIS. Once this is complete, the
requirements for a new, `To -Be' process in the ArcGIS 8 environment will be defined. This
process will cover both the data loading and QA processes necessary to ensure correct attribute
and topology information. It will not necessarily be the case that the `To -Be' solution follows the
exact same steps as the `As -Is' procedures. M&M will work with the City to identify how the
data loading process can be streamlined to improve efficiency and data quality. For example,
given the functionality provided in the ArcGIS 8 environment it may be possible to migrate data
directly from AutoCAD drawing (DWG) files to GeoDatabase feature classes rather than
converting the drawings to DXFs, then migrating the DXF file data.
In the Prototype Phase, M&M will work from the functional requirements defined in the Design
Phase to build prototype tools that meet the City's needs. These tools will be demonstrated to the
City in a daylong review session. The City will have time to provide feedback to help clarify the
requirements of the tools at this time. These clarifications will be incorporated into the
requirements document.
In the Develop and Deploy Phase, M&M will work from the revised functional requirements
document to finalize the Parcel Maintenance tools. Once completed and fully tested at M&M,
the tools will be delivered to the City. The City will then perform their Site Acceptance Tests,
with support from M&M. After the tools pass testing, they will be installed and a daylong user
training session will be held in a lecture and exercise format, giving the City employees the
knowledge to properly maintain the Parcel data.
The Project will take an AutoCAD DWG or DXF file and update the Geodatabase components. The
tools will be written to run on the windows operating system and it will be written in a modular
fashion to allow for individual modules to be updated or replaced. The tools will be written using
ESRI Are Objects and will integrate with ArcMap.
At a minimum, the parcel Geodatabase components that will need to be updated are:
• Parcel framework polygon feature classes
• Boundary are feature class
• Tax parcel polygon feature class, as modified. Tax parcel polygon feature class will have
a unique id assigned automatically. Tables related to it will also have their unique id's
assigned automatically.
• Several annotations will be incorporated into the Geodatabase including feature linked
Geodatabase annotation.
• Easements will be incorporated as an arc feature class
At a minimum, the address Geodatabase components that will need to be updated are:
• Address point feature class
• Subaddress point feature class
• Street arc feature class
• Address range tables, and name tables
• Several annotations will be incorporated into the Geodatabase
• Address and subaddress point feature classes will have a unique id assigned
automatically.
The tools developed must have QC processes to ensure that the same standard of data quality that
now exists is maintained. Input data must be checked to determine that it is correct and all there and
it also must check that the final data has no errors and that it will integrate into the existing dataset.
Items Outside of Project Scope
To clarify the scope of the Project, this section provides a list of items that are not included in the
scope of this Project. M&M would require a Change Order to this Agreement for any work to be
performed in regards to these issues.
1. Database Modeling and Database Updates
The City has stated that the standard ESRI Parcel and Address data models will be used for
the storage of Parcel and Address information. It is assumed that any changes to be made to
these standard models will be performed by the City. These changes include, but are not
limited to, feature class additions and subtractions, field additions and subtractions, domain
value changes, relationship additions and subtractions, annotation feature class additions and
subtractions, and topology rules.
Additionally, assistance in the migration of existing data into these data models is excluded
from this scope of work.
2. Topology rules and Topology issues with existing data
Since M&M is not involved with any aspect of the data conversion, it is outside the scope of
work for this project to participate in any review of or corrections to existing topology issues.
It is expected that the City will have all necessary topology rules defined when the
geodatabase is delivered to M&M to create the development environment
Project Tasks
1.1 Design Phase
The initial phase for the Project will involve a series of tasks to flesh out and document
the functional requirements of the Parcel Maintenance Tools.
1.1.1 Project Kickoff Meeting
M&M will hold a two hour Project Kickoff Meeting on -site at the City. The team
will review, discuss, and make sure all participants fully understand the goals and
methodology for the project. We will also review the project plan to review the
tasks, responsibilities, and dependencies. The team will then cover the
administrative framework for managing the project. We will establish
communication processes, business processes (for example, configuration control
and access control), and change control processes.
Deliverable: Project Kickoff Meeting (M&M, City), Conference facilities
(including a digital projector) (City)
1.1.2 Review Current Procedures
In order to fully understand the current process of loading data into the Librarian
parcel and address layers, a series of tasks to review this process will be held. The
goal of these tasks is to get a complete understanding of the business requirements
and functional requirements of the Project.
1.1.2.1 Review Current DWG/DXF Format
In this task, the M&M PM and the City will review the current
requirements the City has in place for the delivery of CAD files of
parcel data.
Deliverables: On -Site review of Current DWG/DXF Format (M&M,
City)
1.1.2.2 Review DWG/DXF QA Processes
In this task, the M&M PM and the City will review the current
requirements the City has in place for QA of CAD files of parcel data
Deliverables: On -Site review of DWG/DXF QA Process (M&M,
City)
1.1.2.3 Review DWG/DXF to Coverage Process
In this task, the M&M PM and the City will review the current
requirements the City has in place for the conversion of the DXF files
into the Librarian laver.
Deliverables: On -Site review of conversion process (M&M C;tv)
1.1.2.4 Review Address QA Process
In this task, the M&M PM and the City will review the current
requirements the City has in place for the QA of Address information.
Deliverables: On -Site review of Address QA process (M&M, City)
1.1.2.5 Review Parcel QA Process
In this task, the M&M PM and the City will review the current
requirements the City has in place for the QA of Parcel data.
Deliverables: On -Site review of Parcel OA process (M&M_ C
1.1.2.6 Review Topology QA Process
In this task, the M&M PM and the City will review the current
requirements the City has in place for the QA topology within the
Parcel laver.
Deliverables: On -Site review of topology QA process (M&M, City)
1.1.3 Define ArcGIS 8 Process
With a firm understanding of the current process and the business drivers behind
them, the next step is to define how those business requirements will be met with
the Parcel Maintenance Tools.
1.1.3.1 Define DWG/DXF QA Processes
In this task, the M&M PM and the City will define how the CAD files
of parcel data will be processed before loading into the geodatabase.
Deliverables: On -Site requirements gathering of DXF QA process
(M&M, City)
1.1.3.2 Define DWG/DXF to Geodatabase Process
In this task, the M&M PM and the City will define how the CAD files
of parcel data will be loaded into the geodatabase, including which
DWG/DXF layers are associated with feature classes in the
geodatabase.
Deliverables: On -Site requirements gathering of DWG/DXF to
geodatabase process (M&M, City)
1.1.3.3 Define Address QA Process
In this task, the M&M PM and the City will define how the Address
information from the CAD tiles will be QAed in the geodatabase.
Deliverables: On -Site requirements gathering of Address QA process
(M&M, City)