1

Town of Bloomfield

Date: April 25, 2019 To: All Prospective Respondents Subject: Request for Proposals (RFP) No 1092: GIS ENGINEERING SERVICES The Town of Bloomfield invites you to submit a proposal based on the requirements of the enclosed RFP. The RFP and any addenda can be found on the Town of Bloomfield website, www.bloomfieldct.org, as well as the State of CT Dept. of Administrative Services website, http://www.biznet.ct.gov/SCP_Search/Default.aspx?AccLast=2 . The information contained herein outlines the intent and scope of the project; the guidelines governing the submission and evaluation of all proposals; and IRS Form W-9, Request for Taxpayer Identification Number and Certification must be completed and submitted with your proposal. We ask that your proposal conform to our format request as closely as possible. The Town may accept proposals that take exception to any requirement in the RFP. Any exception or alternative must be clearly delineated in a separate attachment to the proposal submitted. The RFP and the proposal submitted by successful respondent will be made part of the resultant contract with the Town. All proposals must be received in the office of the Purchasing and Risk Manager by 1:00 P.M May 20, 2019 Town Hall hours are 9:00 a.m. – 5:00 p.m. Monday through Friday. One Original (clearly identified as such) and five (5) copies plus a thumb drive with a read only copy of the proposal shall be submitted to the attention of

Purchasing and Risk Manager Town of Bloomfield

2nd Floor 800 Bloomfield Avenue

Bloomfield CT 06002 The Package submitted containing proposals shall be sealed, bearing on the outside the firm's name and address and plainly marked "RFP 1092; GIS ENGINEERING SERVICES” The Town of Bloomfield looks forward to receiving your response.

2

Town of Bloomfield

TOWN OF BLOOMFIELD

REQUEST FOR PROPOSALS #1092

GIS ENGINEERING SERVICES

1. INTENT AND PURPOSE

1.1 Introduction and Purpose

1.1.1 The Town of Bloomfield is seeking a qualified professional GIS vendor to create and populate new cadastral GIS datasets, to deed level or better accuracy, in support of the Town Assessor’s Computer Aided Mass Appraisal (CAMA) system, Assessor’s tax mapping, and other Town uses of GIS cadastral data, and in association with an ongoing property revaluation effort.

1.1.2 The datasets created and populated would replace the Town’s existing corresponding datasets, or be a new dataset for the Town.

1.1.3 The anticipated datasets to be created and populated as part of this project are:

1.1.4 Parcel polygons (replace existing).

1.1.5 Parcel points (new dataset).

1.1.6 Street rights of way (new dataset with existing centerline dataset as reference).

1.1.7 Paper streets (as part of an Easement dataset) (new dataset).

1.1.8 Map labels (new dataset with some existing data as reference).

1.1.9 Record lot distance labels (new dataset).

1.1.10 Remainder of Easement dataset (Town option – price provided as part of RFP response.) (new dataset with some existing linework for reference.)

2. BACKGROUND

2.1 Cadastral Statistics (approximate) 2.1.1 Town land area: 26.45 square miles.

2.1.2 CAMA land parcels: 7200 records.

2.1.3 CAMA Common Interest Community (“CIC”) (aka condos): 1350 records.

2.1.4 Roadway distance: 165 miles.

3

Town of Bloomfield

2.1.5 State roadway distance: 28 miles.

3.3.1 Easement bounding lines currently captured: 1600 (have not been converted to polygons.)

2.2 The Town of Bloomfield uses the CAMA system from Vision Government Solutions. Vision is also the prime vendor for the current revaluation effort.

2.3 Town’s current GIS parcel dataset:

2.3.1 Created by MDC in 1990’s from the hard copy tax maps.

2.3.2 Schematically, the physical polygon relationship within the dataset is relatively accurate. From positional accuracy and topological standpoints, there are numerous deficiencies.

2.3.3 The current GIS to CAMA record [correct] match rate is estimated to be

between 90% and 95%.

2.4 Streets data

2.4.1 The Town does not currently have a polygon dataset of street rights of way.

2.4.2 The Town does have a streets centerline dataset that includes attribute data for the street name, ownership [of the right of way], street classification, and acceptance information (if known).

3. AVAILABLE DATA

3.4 Data to be provided by Town to the successful respondent

3.4.1 Town boundary.

3.4.2 Current GIS parcel layer.

3.4.3 Digital parcel boundaries from survey for 300+ lots.

3.4.4 Scans of all of the maps (stored as maps) in the Town Land Records (Town

Clerk’s office).

3.4.5 Railroad rights of way maps (scans)

3.4.5.1 1916 valuation maps updated through 1971.

3.4.5.2 9 additional updated right of way maps.

3.4.6 CTDOT maps (scans)

3.4.6.1 57 right of way maps covering most/all of state roads in town.

3.4.6.2 20 or so other DOT maps.

3.3.6 Sketches of unit locations within condominium buildings.

4

Town of Bloomfield

3.5 Data available (for research or copy) in Town offices

3.5.1 Electronic land record documents from 1985 to present.

3.5.2 Electronic land record index from 1967 – 2982. (No typo – there is a gap.)

3.5.3 Various paper land record documents, indexes, and meeting minutes in Town

Clerk vault.

3.5.4 Paper maps of non-residential site plans in Land Use office.

3.5.5 Paper versions of individual residential lot plot plans in Land Use office.

3.5.6 Various maps showing Town rights of way (which may include as-built maps) in Land Use office.

3.5.7 A file containing many easement documents granted to the Town from an earlier [layperson] land records search.

3.5.8 2015 Topographic and planimetric data (compiled by MDC) 4. SUBMISSION AND DEADLINE

4.1 All proposals must be received in the office of the Purchasing and Risk Manager by 1:00 p.m., May 20, 2019. One original (clearly identified as such) and five (5) copies of the proposal, plus a read only copy on a thumb drive shall be submitted to the attention of the Purchasing and Risk Manager at:

Town of Bloomfield Town Hall, 2nd Floor

800 Bloomfield Avenue Bloomfield, CT 06002

4.2 Package containing proposals must be sealed, bearing on the outside the Consultant’s

name and address and plainly marked "RFP 1092; GIS ENGINEERING SERVICES”.

4.3 Questions about this Request For Proposal and submission requirements must be submitted to and received by email or via fax, to the Purchasing and Risk Manager at nhaynes@bloomfieldct.org or 860-243-2913 by 4:00 PM Friday, May 10, 2019.

4.4 Written clarifications or interpretations, as well as any changes or amendments to this

RFP, will be issued by Addenda not later than 4 PM on May 14, 2019. Only information issued by formal written Addenda will be binding. Oral and other clarifications or interpretations will be without legal effect. Addenda will be posted only on the Town’s website as well as the State DAS website.

4.5 Respondents are required to limit their contact with the Town regarding this RFP to the

persons named herein. 4.6 The Town may accept proposals which take exception to any requirements in this RFP, or

which offer any alternative to a requirement herein. Any exception or alternative must be clearly delineated and cannot materially affect the substance of this RFP.

5

Town of Bloomfield

5. SPECIAL INSTRUCTIONS

5.1 Firms responding to this Request for Proposal are hereby notified that all proposals submitted and information contained therein and attached thereto will not become public information until the Town has awarded a contract to the successful respondent.

5.2 Firms responding to this Request For Proposal, and their sub-consultants, must have

sufficient staff and expertise to complete the required services. Respondents must agree that all personnel assigned to this project are qualified for this type of work.

6. SCOPE OF SERVICES

6.1 General

6.1.1 Create and populate cadastral datasets as specified herein.

6.1.2 The intent is for the polygon features to be to an accuracy of metes and bounds legal property description or better to the extent available.

6.1.3 Attributes to be associated with each cadastral feature, as categorized by the applicable

dataset, are tentatively specified in Exhibit A. The vendor shall create the appropriate dataset tables (or other structure) as appropriate.

6.1.4 Items identified as [option] represent tasks for which a separate price is requested

which may or may not be included in the final engagement at the option of the Town.

6.1.5 The Town recognizes, and expects, that the successful respondent will have more expertise in the provided services than Town staff. Town staff has prepared the details of this scope of services based on their understanding of the matter. The Town desires to take advantage of the expertise of the successful respondent and will be open to input/suggestions regarding ways to streamline or improve the process and final product.

6.1.6 The datasets may be created in any appropriate format, subject to review by the Town.

The datasets must be delivered to the Town in a format that allows the Town to appropriately load the data into a [non ESRI geodatabase] PostgreSQL/PostGIS database. The delivery format will be agreed to by the parties prior to commencing the creation work.

6.1.7 The datasets shall be created and delivered using the EPSG code 2234 (NAD 83

Connecticut State Plane) coordinate reference system in U.S. feet (1 foot = 0.304800609601219 meter).

6.2 Data creation – polygons/polylines

6.2.1 Applicable to creation of parcel, street, and easement polygons and polylines.

6.2.2 Available data is summarized in section 3.

6

Town of Bloomfield

6.2.3 Polygon features are to be built from underlying polylines; the polylines are to be stored in their own separate dataset to be part of the deliverables to the Town.

6.2.4 The final data creation algorithm will be developed with the successful vendor based on

the available data, their experience, and the purposes and specifications set forth in this RFP; however, below is provided the basic building blocks in prioritized order as the Town currently views them:

6.2.3.1 Digital subdivision/survey maps.

6.2.3.2 Record (i.e. from Land Records) subdivision/rights of way/[appropriate] survey maps as can be accurately anchored.

6.2.3.3 CTDOT, railroad, and Town rights of way maps located as best available.

6.2.3.4 Record subdivision/[appropriate] survey maps located as best available.

6.2.3.5 Deed descriptions.

6.2.3.6 Compiled survey maps and other credible map information.

6.2.3.7 Historical tax maps.

6.3 Land parcels datasets (polygons and polylines)

6.3.1 A polygon feature is to be developed for each active parcel record in the CAMA system that corresponds to an actual parcel of land (including “condo main parcels” and for any non-street right of way land areas for which there is not a corresponding CAMA parcel record. (Note that each paper street represents a land parcel that must be captured; and most paper streets are not currently represented by a record in the CAMA system. A paper street typically is a proposed street shown on a subdivision map that has never been accepted as a public road, and/or has not been improved as a private road. As the deeds for adjacent lots typically use the edge of the paper street as their boundary, it is not uncommon that the ownership of a paper street will still remain with the original subdivider – or the successors thereof.)

6.3.2 The vendor shall keep a digital list of parcels identified through its research that are not

currently included in the CAMA system, identifying them by a means, and recording such information about the same, as agreed to by the Assessor, and shall, at intervals acceptable to the Assessor, provide such list to the Assessor for creation of such records in the CAMA system by the Assessor. (Note that the pid and gid attributes must be created by the CAMA system to allow for the link to the GIS data.)

6.3.3 The vendor shall populate the gid (GIS identifier) attribute for each created parcel

polygon as corresponds to the appropriate CAMA parcel record. The existing GIS parcel dataset will be of assistance for this task. However, it is known that there are errors in the existing links. The vendor is to verify each link for each parcel polygon created in the new dataset.

6.3.4 The vendor shall populate the parcel source attribute for each created parcel polygon.

7

Town of Bloomfield

6.3.5 The vendor shall populate two attributes to capture new map and lot designations for each parcel. The process for determining the map and lot designations will be agreed to by the parties.

6.3.6 The vendor shall populate the metadata and common attributes (see Exhibit A) for each

created polygon. 6.3.7 The vendor shall establish a deed history for each parcel sufficient to fully describe the

parcel boundaries and ownership. The vendor shall keep a digital list of any parcel deed history information where such information in the existing CAMA database is missing or incorrect; or acknowledge that the current CAMA information is correct and sufficient. The vendor shall provide this list to the Assessor at the end of the project, or at other intervals agreed upon.

6.3.8 The parties shall agree upon reasonable parameters for the limitation of the amount of

deed research for any given parcel as may be associated with establishing parcel boundaries by deed and/or deed history.

6.4 Parcel points dataset

6.4.1 The vendor shall create a point feature representing each active parcel record in the

CAMA database; this includes both actual land parcels and CIC parcels.

6.4.2 The parcel point for each parcel shall be located as follows:

6.4.2.1 For land parcels with a main building, at the approximate centroid of the building.

6.4.2.2 For land parcels without buildings, near the center of the primary street frontage at a distance off of the street right of way line approximately equal to other point locations along the same frontage.

6.4.2.3 For condo main parcels, similar to parcels without buildings, except that the point

shall not be located within the footprint of any building.

6.4.2.4 For CIC parcels, at a location within the appropriate building footprint, or as otherwise agreed to by the parties.

6.4.3 The vendor shall populate the pid (parcel identifier) attribute for each parcel point

created as corresponds to the appropriate CAMA parcel record.

6.4.4 The vendor shall populate the address number and address street attributes for each parcel point created. This information may be pulled from the CAMA system.

6.4.5 The vendor shall populate the parcel type attribute for each parcel point created. 6.4.6 The vendor shall establish a deed history for each parcel sufficient to fully describe the

parcel boundaries and ownership. The vendor shall keep a digital list of any parcel deed history information where such information in the existing CAMA database is missing or incorrect; or acknowledge that the current CAMA information is correct and sufficient.

8

Town of Bloomfield

The vendor shall provide this list to the Assessor at the end of the project, or at other intervals agreed upon.

6.5 [option] Street right of way dataset (polygons)

6.5.1 The vendor shall create a right of way polygon for each active (i.e. is accepted or has

improvements serving more than 3 properties) public and private street right of way.

6.5.2 The street centerline dataset that is provided to the vendor will include a classification attribute for each street. The Town will provide the vendor with a priority list for these classifications. At intersections, the higher priority street polygon will include the intersection area; the lower priority street will be broken to edge match the higher priority street. The parties will agree upon a procedure for dealing with the intersection of streets of equal classification.

6.5.3 The vendor shall populate the sys id field, which is a unique identifier for each item. 6.5.4 The vendor shall populate the owner field. This represents the party who owns (or is

responsible for the maintenance of) the subject roadway improvements. 6.5.5 The vendor shall populate the metadata and common attributes (see Appendix A) for

each polygon created as may be applicable.

6.6 Easement dataset (polygons)

6.6.1 The vendor shall create a polygon feature for each known significant easement (whether made known to the vendor by the Town or encountered by the vendor as part of its map and deed research for the project.)

6.6.2 Significant easements include:

6.6.2.1 Conservation/open space easements.

6.6.2.2 Easements to the Metropolitan District Commission (MDC), typically for water or sanitary sewer facilities.

6.6.2.3 Drainage easements to the Town or State of Connecticut.

6.6.2.4 Utility easements for transmission or other facilities serving multiple properties. (This would typically not include easements that run adjacent and parallel to a streetline, easements serving a single property, or easements for small accessory facilities such as guy wires, switch gear, transformers, etc.)

6.6.2.5 Major access easements. This would typically include access easements serving multiple properties or buildings, or where significant improvements exist, or paper streets that are not their own separate parcel.

6.7 Labels dataset (ESRI Annotation)

9

Town of Bloomfield

6.7.1 This dataset contains label points (ESRI annotation features) with attribute information

defining labels for tax maps. The subject tax maps will be on a grid supplied by the Town for plotting at 24” x 36” at a scale of 1” = 200’. The vendor shall crate label points at a number and at locations as appropriate for such plots. Labels shall be created for street names (including paper streets), watercourse names, easements, town line labels, parks and other points of interest, etc.

6.7.2 The vendor shall populate the text [for the label], rotation, scale min, and scale max

attributes for each label. The rotation attribute designates the appropriate rotation for the label in degrees, with “0” being horizontal. The global values for scale min and scale max will be agreed to by the parties.

6.8 Record distance labels dataset (ESRI annotation)

6.8.1 This dataset contains label points (ESSRI annotation features) for record distance (from

deed or map) labels along lot lines and easements. The parties will agree on how to handle situations where more than one distance is applicable to a given line.

6.8.2 The text and rotation attributes shall be populated in the same manner as for the labels

dataset above.

6.9 Quality Assurance/Quality Control

6.9.1 Topological integrity: While the Town does not desire the delivered polygon data to be topologically intelligent, it is expected to be of the highest topological integrity. Coincident lines will be coincident; there shall be no gaps or overlaps. Polygon lines shall not loop back on themselves, or contain overshoots or undershoots. Where non-coincident vertices of adjacent polygons are near each other, their relationship shall be correct. And other industry standard topological integrity measures shall apply. The vendor shall run a topological test on all polygon datasets prior to delivery, and all discrepancies shall be resolved.

6.9.2 Parcel match rate: The correct parcel record match rate (for both the polygon and point

datasets) between the cadastral features and the corresponding CAMA records shall be a minimum of 98%.

6.9.3 The area coverage and street name and owner attribute values for the street right of

way dataset are expected to be 100% correct. 6.9.4 The label point and record distance point text values shall be a minimum of 98% correct;

and the rotation values shall be a minimum of 95% appropriate. 6.9.5 Other attribute data shall be a minimum of 95% correct, as related to the source data.

6.9.6 Polylines and polygon edges shall be within 2.5 feet of their actual locations, with a 95% accuracy.

10

Town of Bloomfield

6.9.7 All curvilinear line features shall be true circular curves (i.e. shall not be faceted/densified.)

6.9.8 The dataset structures (e.g. table structure) shall be correct. 6.9.9 The vendor shall conduct regular internal QA/QC audits of the progressing work

appropriate to the scope of the work and the timing of deliverables. The frequency and scope of these audits shall be agreed to by the parties.

6.9.10 Pilot project: The vendor shall perform a pilot project on a representative area of town

agreed to by the parties that is in the range of ½ to full size of one 24” x 36” at 1” = 200’ scale map grid. A significant portion of the pilot area can include digital subdivision data; however, there shall be a representative number of parcels and rights of way that need to be created by other means. The deliverables of the pilot project shall be representative of those for the full project. The vendor is not authorized to proceed with any work outside of the pilot project area until written authorization for the same is received from the Town. Such written authorization may be issued is parts. Any work that the vendor may undertake out of compliance with the foregoing is at the vendor’s own sole risk.

6.9.11 The parties shall meet prior to the vendor beginning work to finalize the vendor’s

approach and to agree on the various parameters, specifications, and other matters per this scope of services.

6.9.12 The parties shall meet once or more in association with the evaluation of the pilot

project to discuss its success and make adjustments as may be necessary to such parameters, specifications, and other matters.

6.9.13 The Town may conduct its own QA/QC evaluation of any deliverable or other work

product as deemed fit thereby prior to final acceptance of any of the same. Interim acceptance of any interim deliverable or other work product shall be evidence that the Town has performed a reasonable cursory QA/QC evaluation of the same. The Town reserves the right, however, to compel the vendor to address/correct, prior to final acceptance, any deficiencies or defects in the same that either significantly affect the quality or integrity of the final product, or would not have been evident in a reasonable cursory QA/QC evaluation of the same.

6.10 Deliverables

6.10.1 The nature and content of deliverables for the project shall be as specified in this scope

of services, as otherwise is reasonable and appropriate to such tasks per industry standards, and as agreed to by the parties at the pre-startup meeting.

6.10.2 As this project is being conducted in conjunction with the Town’s revaluation effort, and will be occurring simultaneously to some degree, the Town may and will be requiring interim deliveries of portions of the parcel polygon and parcel point datasets as they are completed. Further information on such interim deliveries is included in the Project Schedule portion of this RFP; and final details will be agreed to at the pre-startup meeting.

11

Town of Bloomfield

7. TIMEFRAMES

The anticipated RFP schedule is as follows:

RFP Issued 4/25/19 Proposals Due 5/20/19 Proposal Review Completed 5/28/19 Interview respondents Week of 6/7/19 Finalize selection 6/14/19 Commencement of Services 7/1/19

8. CONTRACT PERIOD The contract period is anticipated to be from date of execution through the completion of the

services. 9. CONTRACT MANAGEMENT

9.1 Any contract or purchase order resulting from this RFP will be managed by the Town Assessor unless otherwise specified.

9.2 The selected respondent will assign one qualified individual, who will be the firm's day-

to-day contact person and who will be responsible for directing and coordinating the activities of the firm's personnel in all aspects of the project.

10. EVALUATION AND AWARD 10.1 Selection Criteria The following criteria will be used, without limitation, in evaluating proposals and

determining the most responsive Consultant: 10.1a The Consultant’s technical understanding of the scope of services and proposed

professional services as evidenced by the proposal submitted. 10.1b The background and experience of the Consultant in providing similar services

(especially to other municipalities) as well as the specific background, education, qualifications and relevant experience of key personnel to be assigned to this contract.

10.1c Proposed fees and costs, although the Town is not bound to select the Consultant

who proposes the lowest fees. The Town reserves the right to negotiate fees with the selected Consultant.

Proposals in response to this RFP will be reviewed against the criteria listed above, and

recommendation for award will be made in accordance with standard purchasing procedures.

10.2 Selection Procedures

12

Town of Bloomfield

The Town intends to enter into a contract with the most responsible Consulting Firm whose proposal is determined to be in the best interest of the Town.

10.2a The Town reserves the right to reject any or all proposals or parts thereof for any

reason, to negotiate changes to proposal terms, to waive minor inconsistencies with the RFP, and to negotiate a contract with the successful respondent.

10.2b It is anticipated that several of the respondents whom the Town determines to

have submitted the most responsive proposals will be invited to interview and make a detailed presentation before the Town.

10.2c The Town shall, after a thorough review of the proposals received, and after

conclusion of the interview process, will award the contract to the respondent whom the Town deems best qualified to perform the services required under this contract. The Town reserves the right to award the contract on the basis of the written proposal alone, should it be in its best interests to do so.

11. PROPOSALS The Town will not be liable for costs incurred in the preparation of the response to this RFP or in

connection with any presentation before the Town. Proposals submitted must be bound, paginated, indexed and numbered consecutively. The original proposal must be clearly marked as such. Consultants shall submit as their proposal the following:

11.1 Letter of Transmittal: A letter of transmittal addressed to The Purchasing and Risk

Manager, which includes a statement by the respondent accepting all terms and conditions and requirements contained in this RFP. The letter should also include a brief discussion of the Consultant’s background, experience, and ability to perform this contract in accordance with the Scope of Services. Also to be included, is a listing of clients for whom similar services were performed.

11.2 Detailed Proposal, which includes the following sections: 11.2a Project Understanding: Provide a written discussion in sufficient detail to

demonstrate the Consultant’s understanding of the scope and the professional services required.

11.2b Experience: Provide a detailed written summary of the Firm's history and

experience and capability in providing the services required. 11.2c Staff Plan: Identify key personnel whom the firm will assign to perform services

under this contract. Indicate their background, experience and areas and levels of responsibility. Provide the resumes of all key personnel.

11.2d Service Plan: Provide a detailed, itemized plan of proposed services. 11.2e Services Expected of the Town: Define the nature and scope of all services to be

provided by the Town.

13

Town of Bloomfield

11.2f References: Firms must provide a minimum of three references, sufficiently detailed to include names, titles, addresses and telephone numbers as to allow the Town to contact these references. References are preferred from those projects listed in the proposal.

11.3 Fee Proposal: Consultants are required to submit a fee proposal which includes the

following: 11.3a A detailed fixed sum fee, excluding the items identified as “options” (Section

1.1.10, 6.35 and item 1.10 in Exhibit A). Please provide a separate fee for each option.

11.3b The Town reserves the right to negotiate the fees or rates and payment schedules

with the successful Consultant. All Proposals must be signed by the firm's authorized official. The proposal must also provide

name, title, address, and telephone numbers for 1) the individual with authority to negotiate and contractually bind the firm, and 2) for those who may be contacted for the purpose of clarifying any information provided therein.

12. GENERAL REQUIREMENTS 12.1 Insurance: The selected Consultant shall be required to furnish proof of the following insurance coverage

within ten (10) days of receipt of Notice of Selection. Insurance shall be issued by an insurance company licensed to conduct business in the State of Connecticut with a Best’s Key Rating of A-, VIII or better. Any and all exceptions must be approved by the Town Manager. Insurance coverage shall remain in full force for the duration of the Contract term including any and all extensions or renewal thereof. Each insurance certificate shall contain a (30) day notice of cancellation. All renewal certificates shall be furnished at least thirty (30) days prior to policy expiration.

Minimum Limits General Liability Each Occurrence $1,000,000 Products/Completed Operations Aggregate $2,000,000 General Aggregate $2,000,000 Auto Liability Combined Single Limit $1,000,000 Worker’s Compensation WC Statutory Limits Employer’s Liability EL each accident $100,000 EL disease policy $500,000 Disease accident limit $100,000 Umbrella Each Occurrence $1,000,000

12.1a The Town of Bloomfield and Bloomfield Board of Education are included as Additional

Insureds, ATIMA under the Commercial General Liability and Employer’s Liability Insurance Policies. THE UNDERLINED WORDING MUST BE SHOWN IN THE SPACE PROVIDED FOR “COMMENTS” ON THE ACORD INSURANCE CERTIFICATE. Coverage is to be provided on a primary, noncontributory basis. Waiver of subrogation to be provided.

14

Town of Bloomfield

12.1b Each insurance coverage named above shall provide not less than a 30-day notice of

cancellation to the Town. All policies shall be on the occurrence form. Any and all exceptions shall be reviewed by the Town Manager.

12.1c Cancellation or other termination of insurance policies required by this Agreement

without immediate replacement thereof may be considered a default in the terms and conditions of this Agreement. The Consultant agrees that such default may be cured by procurement of insurance on behalf of Consultant, by the Town, at the Consultant’s expense, at Town’s option.

12.2 Hold Harmless Agreement: The Consultant, its agents and assigns shall indemnify and hold harmless the Town of Bloomfield

and the Bloomfield Board of Education, including but not limited to, its elected officials, its officers, and agents, ("the Town") from any and all claims made against the Town, including but not limited to, damages, awards, costs and reasonable attorney’s fees, to the extent any such claim directly and proximately results from the wrongful, willful or negligent performance of services by the Consultant during the Consultant’s performance of this Agreement or any other Agreements of the Consultant entered into by reason thereof. The Town agrees to give the Consultant prompt notice of any such claim and absent a conflict of interest, an opportunity to control the defense thereof.

As a municipal agency of the State of Connecticut, the Town will NOT defend, indemnify, or hold harmless the successful proposer.

12.3 Conditions Consultants responding to this RFP will be expected to adhere to the following conditions in an

agreement with the Town and must make a positive statement to that effect in its proposal submitted:

12.3a Agree that the Consultant has sufficient personnel to assure service continuity

and project completion and agree to maintain adequate qualified personnel for the full duration of the contract.

12.3b Agree that all work produced under this agreement will become property of the

Town of Bloomfield.

12.3c Agree to provide the insurance coverage herein specified for the full duration of the contract's term, including any and all extensions.

12.3d Agree to accept and follow management direction from the Town and specifically,

the individuals named herein or their duly authorized designee(s).. 12.3e Agree to conform to all applicable laws and ordinances and policies of the Federal

Government, State of Connecticut and Town of Bloomfield. 12.3f Agree that if the Town cannot in good faith negotiate a written contract within a

reasonable time with a selected Consultant, the Town may unilaterally cancel its selection of that Consultant.

12.3g Agree that periodic payments to the Consultant will be made as agreed upon in

the signed contract.

15

Town of Bloomfield

12.3h Agree that if services are not performed in a timely manner so as to meet the

Town’s stated time frame, the Town may withhold payment, or portions of payment.

12.3i Agree that the Town reserves the right to terminate the contract at any time. In

the event of contract termination, the Consultant shall be entitled to payment for approved services rendered after the execution of the contract and prior to receipt of notice of termination. However, if the Consultant has damaged the Town, said payment may be withheld until the Town determines whether or not by how much said payment should be reduced.

12.3j Agree that the contract between the Town and the Consultant shall be governed

by and construed in accordance with the laws of the State of Connecticut and the ordinances of the Town of Bloomfield.

12.3k Agree that no conflict of interest exists. Identify the nature of any potential

conflict of interest that firm might exist when providing services to the Town under this RFP. Discuss fully any conflicts of interest, actual or perceived, which might arise in connection with the performance of the proposed agreement. If conflicts do or might exist, describe how they would be resolved.

13. ANTI COLLUSION STATEMENT

Proposers and their employees, officers, advisers, agents or sub-contractors must not engage in any collusive bidding or other anti-competitive conduct, or any other similar conduct, in relation to: a. the preparation or submission of Proposals; b. the clarification of Proposals; and c. the conduct and content of negotiations, including final contract negotiations, in respect of this RFP or procurement process, or any other procurement process being conducted by the Town in respect of any of its requirements.

14. TAXPAYER'S IDENTIFICATION NUMBER

Each Consultant, whether an individual, proprietor, partnership or a non-profit corporation or organization must obtain, complete and include, with the proposal submitted, an Internal Revenue Service Form W-9, "Request for Taxpayer Identification Number and Certification".

15. ADDITIONAL INFORMATION AND REVISIONS TO PROPOSALS Information may be provided to potential respondents for the purpose of clarification to assure

full understanding of, and responsiveness to the Request for Proposal requirements. Prospective respondents shall be afforded fair and equal treatment with respect to access to additional information and revision of proposals. No additions or changes to the original proposal will be allowed after submittal.

16

Town of Bloomfield

EXHIBIT A

RFP #1092; GIS ENGINEERING SERVICES

DATASET ATTRIBUITES

1. Dataset Attributes (creation order TBD)

1.6. Polygon datasets - metadata

1.6.1. edit_date

1.6.2. edit_by

1.6.3. e_reason

1.6.4. e_comment

1.6.5. gen_comment

1.6.6. flag (an integer field for data manipulation; default value = 0)

1.7. Polygon data sets – common attributes

1.7.1. source_type (e.g. deed, subdivision, site plan, digital, gis, tax map, composite)

1.7.2. source_location (e.g. land records, land use, owner)

1.7.3. source_document (e.g. book/page, map number, etc.)

1.7.4. source_doc_type (e.g. warranty deed, quit claim deed, easement grant, etc.)

1.7.5. survey_accuracy

1.7.6. create_method

1.7.7. As there will likely be occasions where a parcel (or other polygon entity) is defined

through the combination of more than one document, (creating a many-to-one

relationship), Town staff envisions the use of a spreadsheet to capture these attributes

during creation, with the subject data being migrated to the database in the later stages

of the project.

1.8. Land parcels (polygons) (does not include individual common interest community parcel

records)

1.8.1. gid (gis id from CAMA)

1.8.2. parcel_type (e.g. fee simple, condo main, etc.)

1.8.3. map/lot designation (newly created as part of project)

1.8.4. deed history (this is a separate digital list for future incorporation into the CAMA system.

This is a redundant subset to 1.7.3 above.)

1.8.5. Up to 40 attributes to be imported/updated from CAMA (set up attribute field in table)

17

Town of Bloomfield

1.9. Parcel points (e.g. address points; includes common interest community parcel records)

1.9.1. pid (parcel id from CAMA)

1.9.2. address_number (text field – populated from CAMA)

1.9.3. address_street (from CAMA)

1.9.4. parcel_type (land or CIC)

1.10. [option] Street right of way (public and private)

1.10.1. sys_id (unique id text field)

1.10.2. street_name

1.10.3. owner (e.g. Bloomfield, State of CT, association, other municipality, other private)

1.10.4. land_owner (e.g. Bloomfield, State of CT, association, n_d [adjacent properties

presumed])

1.10.5. acceptance_by (to be populated by Town in base proposal)

1.10.6. acceptance_date (to be populated by Town in base proposal)

1.11. Easement (includes paper streets)

1.11.1. sys_id (unique id text field)

1.11.2. purpose (e.g. access, drainage, sanitary sewer, water service, utility)

1.11.3. owner (essentially same as for street rights of way, except list pids for private owners)

1.12. Annotation

1.12.1. text

1.12.2. rotation

1.12.3. scale_min

1.12.4. scale_max

1.13. Record distance annotation)

1.13.1. [distance] text (from deed or map)

1.13.2. rotation