Full Text
AGREEMENT FOR PROFESSIONAL ENGINEERING SERVICES RELATED TO IMPLEMENTATION OF THE CITY OF MOSCOW PAVEMENT MANAGEMENT SYSTEM THIS AGREEMENT FOR PROFESSIONAL ENGINEERING SERVICES RELATED TO IMPLEMENTATION OF THE CITY OF MOSCOW PAVEMENT MANAGEMENT SYSTEM (hereinafter "Agreement"), is made and entered into this ~ day of A-u~ VI 0 , 2013, by and between the City of Moscow, Idaho, a municipal corporation of the S~te of Idaho, 206 East Third Street, Moscow, Idaho, 83843 (hereinafter "CITY"), and MDS Technologies, Inc., 350 S. Northwest Highway, Suite 300, Park Ridge, Illinois, 60068 (hereinafter "ENGINEER"). WITNESSETH: WHEREAS, CITY desires to implement a pavement management system as a tool to assist CITY with the task of managing CITY' s pavements, to include a complete inventory of all existing pavements, an evaluation of their condition, and most cost effective maintenance and preservation treatments (hereinafter "PROJECT"); and WHEREAS, CITY has selected the above-referenced ENGINEER to complete the Scope of Work identified herein; and WHEREAS, ENGINEER has prepared the Scope of Work which is incorporated into this Agreement; and WHEREAS, CITY wishes ENGINEER to complete the Scope of Work pursuant to this Agreement; NOW, THEREFORE, be it agreed that for and in consideration of the mutual covenants and promises between the parties hereto, that: SECTION I: SCOPE OF WORK ENGINEER Responsibilities ENGINEER shall be responsible for defining road segments, collecting all necessary field data, assessing existing pavement conditions, uploading collected data to CITY' s Carte graph PavementView Plus Software application, and training of CITY staff in the use of the software as fully described in Exhibit Detailed Scope of Work and Fee Schedule. A. Define Road Segments ENGINEER will define CITY's road network as a series of road segments m Pavement View. RECEIVED JUL 1 9 2013 PROFESSIONAL SERVICES AGREEMENT- MDS TECHNOLOGIES, INC. City of Moscow PAGE 1OF16 ---PAGE BREAK--- Several fields need to be populated in PavementView in order to properly define each road segment and allow a numeric condition score to be calculated from the pavement inspection data. • Street Name, From Street, To Street Fields The Street Name, From Street, and To Street fields will be used to define road segments in PavementView. • Segment ID Field PavementView requires each segment to have a unique Segment ID. The Segment ID is an alphanumeric string that can be any combination of numbers, letters, and allowable special characters. ENGINEER will collaborate with CITY to assign Segment IDs so that segments along a street will be listed in the sequence that they occur in the field when the database is sorted by Segment ID. B. Segment Length, Paved Width, Surface Type Data Segment length and paved width data is required to calculate the paved area of each segment. Paved area, in turn, is required to calculate a condition score for each segment. The length of each road segment will be acquired from CITY's GIS pavement centerline data. CITY also has paved width data available in GIS which is thought to be accurate to the nearest foot. As this is sufficiently accurate for pavement management purposes, ENGINEER will use this data to populate the PavementView database and calculate the area of each segment. Surface type data (e.g. asphaltic concrete [AC], Portland Cement Concrete [PCC], gravel, etc.) is acquired as part of the pavement inspection process and will also be entered into the PavementView database. C. Field Data Collection ENGINEER will assess the condition of approximately eighty three (83) centerline miles of CITY streets using a vehicle based approach to capture pavement inventory and condition data. The approach consists of high resolution digital cameras tied to positioning data provided by Global Positioning Systems (GPS). By orienting cameras at various angles, large quantities of pavement related data can be captured safely as the vehicle travels the roads at normal speeds. This approach does not involve sampling as the entire surface area is evaluated. D. Pavement Condition Assessment Pavement condition data is acquired through analysis of the digital imagery captured with the data collection vehicle. Both the forward-looking streetscape view and the downward- looking detailed pavement view are used to assess the severity and extent of any distresses that occur. Because each frame is tied to positioning data acquired from GPS, each image pair can be easily tied to a road segment. • Assessing the Severity and Extent of Pavement Distresses Using software tools built for this purpose, ENGINEER will mark the location, severity, and extent of the distresses along each segment. PROFESSIONAL SERVICES AGREEMENT- MDS TECHNOLOGIES, INC. PAGE20F 16 ---PAGE BREAK--- Pavement Condition scores will be calculated for each segment after the inspection data is loaded into CITY's PavementView database. In PavementView, pavement condition scores will be related as the Distress Index (DI). These scores will range from one hundred (excellent) to zero (failed) (100 - E. Upload Data to Pavement View Database The road segment data and inspection data described above will be uploaded to CITY' s, PavementView database. ENGINEER will use the Cartegraph Import/Export Utility to upload this data. ENGINEER will perform this task either from ENGINEER's office through a remote connection to a CITY computer with PavementView installed, or on- site prior to providing training to CITY staff. F. Training for CITY Staff ENGINEER will provide two types of training: PavementView user training and pavement evaluation training. 1. PavementView User Training ENGINEER will provide PavementView user training so that CITY staff will be able to use PavementView effectively. This training will be tailored to the needs of CITY. ENGINEER will provide a one day training session. Training will include the following: a. An overview of the user interface; b. Locating a segment in the database; c. Viewing/Modifying/ Adding data for an existing segment; d. Viewing/Modifying/ Adding inspection data; e. Viewing/Modifying/ Adding work history data; f. Sorting and Filtering data; g. Selecting/Viewing Reports; and h. Other items as required. 2. Pavement Evaluation Training ENGINEER will provide training so that CITY staff can perform their own inspections and load the new inspection data into PavementView. This training will be provided over one day and will include: a. A classroom overview of the DI model, including a review of the different types of distresses used in the model and an overview as to how Distress Index scores are calculated; b. Identifying appropriate sample(s) to evaluate; c. Evaluating and recording the type, severity, and extent of distresses in the field; d. Entering the inspection data into PavementView; and e. Calculating new Distress Index scores. CITY staff will be trained to inspect both AC and PCC surfaced pavements. CITY staff will be responsible to provide their own transportation to/from the pavement evaluation sites. PROFESSIONAL SERVICES AGREEMENT- MDS TECHNOLOGIES, INC. PAGE3OF16 ---PAGE BREAK--- SECTION II: CITY Responsibilities CITY staff will be asked to: 1. Provide a GIS pavement centerline file showing the road segments to be included in the PROJECT. 2. Provide GIS ortho-photography (if available). 3. Attend a PROJECT Meeting prior to the start of the field work. 4. Allow remote access to a CITY computer with PavementView installed. 5. Allow ENGINEER to park the data collection vehicle in a secure area of the public works yard and allow access to this area during non-working hours. SECTION III: PROJECT Schedule ENGINEER shall complete the PROJECT within a three month time frame from receipt of notice to proceed. The Fieldwork Task is the critical path item for this PROJECT because several other Tasks cannot be initiated and/or completed until the fieldwork is complete. Fieldwork shall be initiated within three weeks of notice to proceed. The duration of the fieldwork is expected to be less than one week. 1. CITY shall provide to ENGINEER, in relationship to the PROJECT, all necessary documents, permits, permissions, and authorities to complete the PROJECT as described. 2. CITY shall sign off on final documents, after approval by CITY Public Works Director. SECTION IV: Independent Contractor The contracting parties warrant by their signature that no employer/employee relationship is established between ENGINEER and CITY by the terms of this Agreement. It is understood by the parties hereto that ENGINEER is an independent contractor and as such neither it nor its employees, if any, are employees of CITY for purposes of tax, retirement system, or social security (FICA) withholding. SECTION V: Fees and Conditions for Engineering Services 1. Payment for all services described in this Agreement is provided in accordance with the cost described in the following Section 11.B.2. 2. The cost for engineering services for PROJECT as described in Section I, Scope of Work, is a lump sum fee of Thirty Thousand, One Hundred Dollars ($30,100) with payment based on Exhibit Scope of Work, which shall include all fixed fees (profit), overhead, and direct costs. 3. Bills submitted to CITY by ENGINEER shall list individual performing work and description of work performed. Bills shall be submitted on a basis to CITY Engineer for approval and payment. 4. Payment is due upon receipt ofENGINEER's statement(s). PROFESSIONAL SERVICES AGREEMENT- MDS TECHNOLOGIES, INC. PAGE40F 16 ---PAGE BREAK--- 5. Payment of the not-to-exceed amount of Thirty Thousand, One Hundred Dollars ($30,100) 6. CITY and ENGINEER may mutually agree to re-allocate task funding, providing the "not to exceed price" described in Section Il.B.2. is unchanged. SECTION VI: Termination of Agreement This Agreement may be terminated by ENGINEER upon thirty (30) days written notice, should CITY fail to substantially perform in accordance with its terms through no fault of ENGINEER. CITY may terminate this Agreement with thirty (30) days notice without cause and without further liability to ENGINEER except as designated by this section. In the event of termination, ENGINEER shall be paid for services performed to termination date, including direct expense and including a percentage of the fixed fee based upon the work completed. All working Drawings shall become the property of, and shall be surrendered to, CITY. SECTION VII: Extent of Agreement This Agreement may be amended only by written instrument signed by both parties hereto. SECTION VIII: Data of Record CITY shall make available to ENGINEER all technical data of record in CITY's possession, including maps, surveys, borings and other information described in Section I. B. to ENGINEER supporting this PROJECT. SECTION IX: Compensation ENGINEER shall be compensated for work performed pursuant to this Agreement as described on page 8, section 5 of Exhibit attached hereto. SECTION X: Termination of PROJECT If any portion of PROJECT covered by this Agreement shall be suspended, abated, abandoned or terminated, CITY shall pay ENGINEER for the services rendered to the date of such suspended, abated, abandoned or terminated work; the payment to be based, insofar as possible, on the amounts established in this Agreement or, where the Agreement cannot be applied, the payment shall be based upon a reasonable estimate as mutually agreed upon between the two parties as to the percentage of the work completed. SECTION XI: Insurance ENGINEER's Additional Insurance ENGINEER shall maintain Automobile Insurance and Statutory Workmen's Compensation Insurance coverage, Employer's Liability, and Comprehensive General Liability Insurance coverage. The Comprehensive General Liability Insurance shall have a minimum limit of Five Hundred Thousand Dollars ($500,000) per claim and One Million Dollars ($1,000,000) PROFESSIONAL SERVICES AGREEMENT- MDS TECHNOLOGIES, INC. PAGE50F 16 ---PAGE BREAK--- aggregate, and ENGINEER shall cause CITY to be named as an additional insured under said policy. SECTION XII: Indemnification ENGINEER agrees, to the fullest extent permitted by law, to indemnify and hold harmless CITY against damages, liabilities and costs arising from the negligent acts of ENGINEER in the performance of professional services under this Agreement, to the extent that ENGINEER is responsible for such damages, liabilities and costs on a comparative basis of fault and responsibility between ENGINEER and CITY. ENGINEER shall not be obligated to indemnify CITY for CITY' s sole negligence. SECTION XIII: Jurisdiction and Venue It is agreed that this Agreement shall be construed under and governed by the laws of the State of Idaho. In the event of litigation concerning it, it is agreed that proper venue shall be the District Court of the Second Judicial District of the State ofldaho, in and for the County of Latah. SECTION XIV: Costs and Attorney Fees In the event either party incurs legal expenses to enforce the terms and conditions of this Agreement, the prevailing party is entitled to recover reasonable attorney's fees and other costs and expenses, whether the same are incurred with or without suit. SECTION XV: No Assignment ENGINEER shall not assign any of the rights or duties of this Agreement without prior written consent of CITY. ENGINEER binds itself, its partners, successors, assigns and legal representatives to the other parties to this Agreement and to the partner, successors, assigns and legal representatives of such other parties with respect to all covenants of this Agreement. SECTION XVI: Modification and Assignability of Agreement This Agreement contains the entire agreement between the parties concerning PROJECT, and no statements, promises, or inducements made by either party, or agents of either party, are valid or binding unless contained herein. This Agreement may not be enlarged, modified, or altered except upon written agreement signed by the parties hereto. ENGINEER may not subcontract or assign its rights (including the right to compensation) or duties arising hereunder without the prior written consent and express authorization of CITY. Any such subcontractor or assignee shall be bound by all of the terms and conditions of this Agreement as if named specifically herein. SECTION XVII: CITY'S Representatives CITY designates the City Engineer to act in behalf of CITY. The City Engineer shall examine the documents of the work as necessary, and shall render decisions related thereto in a timely manner so as to avoid unreasonable delays. PROFESSIONAL SERVICES AGREEMENT-MOS TECHNOLOGIES, INC. PAGE60F 16 ---PAGE BREAK--- SECTION XVIII: Conflict of Interest ENGINEER covenants that they presently have no interest and will not acquire any interest, direct or indirect, in PROJECT which would conflict in any manner or degree with the performance of services hereunder. ENGINEER further covenants that, in performing this Agreement, they will employ no person who has any such interest. SECTION XIX: Ownership and Publication of Materials. All reports, information, data and other materials prepared by ENGINEER pursuant to this Agreement shall be the property of CITY, which shall have the exclusive and unrestricted authority to release, publish, or otherwise use them, in whole or in part. All such materials developed under this Agreement shall not be subject to copyright or patent in the United States or in any other country without the prior written approval and express authorization of CITY. SECTION XX: Non-discrimination. ENGINEER shall not discriminate against any employee or applicant for employment on the basis of race, color, religion, gender, pregnancy, national origin, ancestry, age, marital status, veteran status, disability, sexual orientation, genetic information, or any other basis prohibited by local, state, or federal law. IN WITNESS WHEREOF, the parties hereto have caused this Agreement to be executed as of the date indicated above. ENGINEER CITY Tre · Principal DATED this\~ day of JtJv'( 2013. PROFESSIONAL SERVICES AGREEMENT- MDS TECHNOLOGIES, INC. PAGE 7 OF 16 ---PAGE BREAK--- ACKNOWLEDGMENT STATE OF ILLINOIS ) ) SS. COUNTY OF COOK ) On this 1111" day of 2013, before me, a Notary Public in and for said State, appeared Trevor T. Triffo, known to me to be the person named above and acknowledged that he executed the foregoing document as a duly authorized representative for MDS ~ Technologies, Inc. SCOTT BOERMA OFFICIAL SEAL Notary Public, State of Illinois My Commission Expires December 31, 2013 Notary Public for the State of Illinois Residing at ~ ~ . <:rDU/.J'fr A-Vi£ My commission expires / i.J ft 3 PROFESSIONAL SERVICES AGREEMENT- MDS TECHNOLOGIES, INC. PAGE80F 16 ---PAGE BREAK--- EXHIBIT DETAILED SCOPE OF WORK FEE SCHEDULE 1. PROJECT REQUIREMENTS The CITY of Moscow, Idaho (hereinafter "CITY") wants to implement a pavement management System as a tool to assist CITY staff with the task of managing the CITY's pavements. CITY has purchased and installed Cartegraph's PavementView Plus software application for this purpose (hereinafter "System"). CITY wants a complete inventory of the CITY's pavements defined within PavementView. Pavement condition data, acquired from pavement inspections, must also be entered into the System. CITY staff must receive training on how to use and maintain the System. A Work Plan designed to achieve the CITY's objectives is detailed below. 2. WORKPLAN MDST has created a draft Work Plan that is comprised of a series of logical Tasks. The following Tasks are discussed in more detail below: Define Road Segments Acquire Length, Width, and Surface Type Data Field Data Collection Pavement Condition Assessment Upload Data to PavementView Training MDST understands that this draft Work Plan is subject to modification upon review by CITY staff. 2.1 DEFINE ROAD SEGMENTS The first step in the project is to identify the roads that CITY wants to include in PavementView Plus. Typically, this would include all CITY-maintained roads. It could also include CITY-maintained parking lots. In some cases our clients have included non-CITY maintained roads that they were expecting to annex in the foreseeable future. Roads inside CITY limits that are maintained by other entities (e.g. State, county, and private roads) are usually not included in the System. This data is often available from the pavement centerline layer of our clients' GIS system. If this is not available, this data can be obtained from hard copy maps or other sources available from CITY. MDS TECHNOLOGIES, INC. EXHIBIT PAVEMENT MANAGEMENT SYSTEMS - RIGHT-OF-WAY ASSET MANAGEMENT SYSTEMS - GIS PAGE90F 16 ---PAGE BREAK--- MDST will define CITY's road network as a series of road segments in PavementView. Each road segment should be homogeneous in terms of pavement type, cross-section, construction history, traffic, and condition. Roads are typically segmented on a block-to-block basis because these factors can change frequently on these types of roads. Sometimes, further subdivision is necessary to account for cases in which conditions change in mid-block. Another factor to consider when creating road segments is that the size of each segment should be such that it represents a practical rehabilitation project (i.e. not too large or too small). Several fields need to be populated in PavementView in order to properly define each road segment and allow a numeric condition score to be calculated from the pavement inspection data. These fields are: Street Name From Street To Street Segment ID Street Name, From Street, To Street Fields The Street Name, From Street, and To Street fields are the key fields used to define road segments in PavementView. Each segment has a Street Name and From/To Termini descriptors. The From/To Termini descriptors are usually the names of intersecting streets, but can also be non-street names such "CITY Limit" or "Cul-de-Sac". It is good practice to enforce desired street naming format and abbreviation conventions when assigning Street Names. For example, "North Main Street" could also be formatted as Main St." or "Main St. When selecting the desired format, consideration should be given to existing conventions in GIS or other systems. MDST will assist CITY staff with this as necessary. Sources for the street names include the CITY's GIS, other CITY systems/databases, hard copy maps, and/or field observations. Often, the pavement centerline file from our clients' GIS provides the best source for this information. Segment ID Field PavementView requires each segment to have a unique Segment ID. The Segment ID is an alphanumeric string that can be any combination of numbers, letters, and allowable special characters. MDST has found that it is good practice to assign Segment IDs so that segments along a street will be listed in the sequence that they occur in the field when the database is sorted by Segment ID. MDST will collaborate with CITY staff and present some options regarding the structure/naming convention of the Segment ID field. MDS TECHNOLOGIES, INC. EXHIBIT PAVEMENT MANAGEMENT SYSTEMS - RIGHT-OF-WAY ASSET MANAGEMENT SYSTEMS - GIS PAGE lOOF 16 ---PAGE BREAK--- 2.2 SEGMENT LENGTH, PAVED WIDTH, SURFACE TYPE DATA Segment length and paved width data is required to calculate the paved area of each segment. Paved area, in tum, is required to calculate a condition score for each segment. The length of each road segment can be acquired from CITY's GIS pavement centerline data. CITY also has paved width data available in GIS which is thought to be accurate to the nearest foot. As this is sufficiently accurate for pavement management purposes, we propose to use this data to populate the PavementView database and calculate the area of each segment. Surface type data (e.g. asphaltic concrete [AC], Portland Cement Concrete [PCC], gravel, etc.) is acquired as part of the pavement inspection process and will also be entered into the Pavement View database. 2.3 FIELD DATA COLLECTION CITY wants to assess the condition of its road network. This amounts to approximately eighty three (83) centerline miles of CITY streets according to CITY staff. Accurate and consistent pavement condition data is crucial to successful implementation of a pavement management system. Acquisition of this data in a timely and cost effective manner is a major implementation issue. To address this issue, MDST uses a vehicle based approach to capture pavement inventory and condition data quickly, accurately, and cost-effectively. Our approach consists of high resolution digital cameras tied to positioning data provided by Global Positioning Systems (GPS). By orienting cameras at various angles, large quantities of pavement related data can be captured safely as the vehicle travels the roads at normal speeds. A two camera configuration is typically used for pavement condition surveys. MDST uses industrial grade cameras that are capable of outputting images up to four ( 4) Megapixels in size. Images are typically captured at approximately ten foot (10') intervals. Each frame is written to on-board, high-capacity hard disk drives in A VI or JPG format. Both cameras are mounted to the roof of the data collection vehicle. One camera is configured to provide forward-looking pavement oriented digital imagery of the streetscape. This view provides pavement attribute data (e.g. paved width, number of lanes, surface type, etc.). The second camera is mounted at the rear of the vehicle and is configured to provide detailed imagery of the pavement surface. This approach does not involve sampling as the entire surface area is evaluated. 2.4 PAVEMENT CONDITION ASSESSMENT Pavement condition data is acquired through analysis of the digital imagery captured with the data collection vehicle. Both the forward-looking streetscape view and the downward- looking detailed pavement view are used to assess the severity and extent of any distresses that occur. A sample image pair is shown below. Because each frame is tied to positioning data acquired from GPS, each image pair can be easily tied to a road segment. MDS TECHNOLOGIES, INC. EXHIBIT PAVEMENT MANAGEMENT SYSTEMS • RIGHT-OF· WAY ASSET MANAGEMENT SYSTEMS - GIS PAGE 11OF16 ---PAGE BREAK--- Assessing the Severity and Extent of Pavement Distresses An experienced pavement inspector performs a 'virtual drive' along a road segment by stepping through the image pairs one frame at a time. Since the image pairs are captured at approximately ten foot (10') intervals, the entire area of a pavement segment can be assessed. The inspector marks the location, severity, and extent of the distresses along each segment using software tools built for this purpose. PavementView Plus uses the ASTM D6433-11 method to quantify pavement distress. This method was originally developed by the US Army Corps of Engineers. In this model, the severity of a distress is related to the width of cracking for cracking-type distresses and the degree of deviation from the plane of the original surface for distortion-type distresses. For asphalt surfaced pavements, the extent of distress is determined by area (e.g. alligator cracking), length (e.g. longitudinal cracking), or occurrence (e.g. potholes) depending on the type of distress encountered. For PCC surfaced pavements, extent is determined based on the number of slabs affected by a distress. 11vt; ff • Qo f • 8i' flll 11 fi d:J •lil I The following distresses are evaluated on pavements with an asphalt surface: Alligator Cracking Bleeding Block Cracking Bumps and Sags Corrugation MDS TECHNOLOGIES, INC. EXHIBIT PAVEMENT MANAGEMENT SYSTEMS - RIGHT-OF-WAY AsSET MANAGEMENT SYSTEMS - GIS - x PAGE 120F 16 ---PAGE BREAK--- Depression Edge Cracking Joint Reflection Cracking Lane/Shoulder Drop Off Longitudinal & Transverse Cracking Patching Polished Aggregate Potholes Railroad Crossing Rutting Shoving Slippage Cracking Swelling Weathering/Raveling The following distresses are evaluated on pavements with a Portland Cement Concrete surface: Blowup/Buckling Comer Break Divided Slab Cracking Faulting Joint Seal Damage Lane/Shoulder Drop Off Linear Cracking Large Patching Small Patching Polished Aggregate Popouts Pumping Punchout Railroad Crossing Scaling/Map Cracking/Crazing Shrinkage Cracks Comer Spalling Joint Spalling MOS TECHNOLOGIES, INC. EXHIBIT PAVEMENT MANAGEMENT SYSTEMS - RIGHT-OF-WAY ASSET MANAGEMENT SYSTEMS - GIS PAGE 13OF16 ---PAGE BREAK--- Calculating Pavement Condition Scores Pavement Condition scores will be calculated for each segment after the inspection data is loaded into CITY's PavementView database. In PavementView, pavement condition scores are referred to as the Distress Index (DI). These scores range from one hundred (excellent) to zero (failed) (100 - 2.5 UPLOAD DATA TO PA VEMENTVIEW DAT ABASE The road segment data and inspection data described above will be uploaded to CITY' s PavementView database. MDST will use the Cartegraph Import/Export Utility to upload this data. MDST can perform this task either from our office through a remote connection to a CITY computer with PavementView installed, or on-site prior to providing training to CITY staff. 2.6 TRAINING FOR CITY STAFF CITY needs to be able to use and maintain the PavementView System going forward at the conclusion of this Project. MDST proposes to provide two types of training: PavementView user training and pavement evaluation training. Pavement View User Training MDST will provide PavementView user training so that CITY staff will be able to use PavementView effectively. This training will be tailored to the needs of CITY. MDST proposes to provide a one day training session. Training typically includes: An overview of the user interface; Locating an segment in the database; Viewing/Modifying/ Adding data for an existing segment; Viewing/Modifying/ Adding inspection data; Viewing/Modifying/ Adding work history data; Sorting and Filtering data; Selecting/Viewing Reports; Other items as required. Additional PavementView user training can be provided at additional cost. Usually this is best done in a second session after CITY staff has had the opportunity to use and master the knowledge they gained in the first session. Pavement Evaluation Training Pavement inspections provide information about the condition of the road network at a point in time. As time goes on, conditions in the field change and re-inspection becomes necessary so that CITY is aware of any developing issues and the data in the PavementView MDS TECHNOLOGIES, INC. EXHIBIT PAVEMENT MANAGEMENT SYSTEMS - RIGHT-OF-WAY ASSET MANAGEMENT SYSTEMS - GIS PAGE 140F 16 ---PAGE BREAK--- System accurately reflects the condition in the field. MDST will provide training so that CITY staff can perform their own inspections and load the new inspection data into PavementView. This training would be provided over one day and would include: A classroom overview of the DI model, including a review of the different types of distresses used in the model and an overview as to how DI scores are calculated; Identifying appropriate sample( s) to evaluate; Evaluating and recording the type, severity, and extent of distresses in the field; Entering the inspection data into PavementView; and, · Calculating new DI scores. CITY staff will be trained to inspect both AC and PCC surfaced pavements (if CITY maintains both types of pavements). CITY staff will be responsible to provide their own transportation to/from the pavement evaluation sites. 3. REQUIREMENTS OF CITY STAFF The requirements for CITY staff are minimal for this Project. CITY staff will be asked to: Provide a GIS pavement centerline file showing the road segments to be included in the Project; Provide GIS ortho-photography (if available); Attend a Project Meeting prior to the start of the field work; Allow remote access to a CITY computer with PavementView installed; and, Optionally, allow us to park the data collection vehicle in a secure area of the public works yard and allow access to this area during non-working hours. 4. MDST can complete the project within a three month time frame from receipt of notice to proceed. The Fieldwork Task is the critical path item for this Project because several other Tasks cannot be initiated and/or completed until the fieldwork is complete. Fieldwork can be initiated within two weeks of notice to proceed. The duration of the fieldwork is expected to be less than one ( 1) week. 5. FEE SCHEDULE MDST's lump sum fee to provide these services is shown below. MDST will submit invoices to CITY on a cycle. Invoiced amounts will be pro-rated based on percent complete by Task. Payment terms are Net Thirty (30) days. This proposal is valid for ninety (90) days. MDS TECHNOLOGIES, INC. EXHIBIT PAVEMENT MANAGEMENT SYSTEMS - RIGHT-OF-WAY ASSET MANAGEMENT SYSTEMS - GIS PAGE 15OF16 ---PAGE BREAK--- PROJECT FEE SCHEDULE1 TASK FEE Define Road Segments $ 4,125 Length, Width, and Surface Type Data $ 1,250 Field Data Collection $ 8,950 Pavement Condition Assessment $ 9,100 !Upload Data to PavementView $ 1,200 !Office Training $ 3,300 Pavement Evaluation Training2 $ 2,175 TOTAL: $30,100 1• 2. PavementView is installed on the CITY's computer network and connected to a database. PavementView database is empty-we are working with a "clean slate". Approximately eighty three (83) centerline miles of pavements are to be included in the System. MDST asswnes the Pavement Evaluation training will be done in conjunction with the User Training. If no, additional fees to cover travel time and expenses will apply. MDS TECHNOLOGIES, INC. EXHIBIT PAVEMENT MANAGEMENT SYSTEMS - RIGHT-OF-WAY ASSET MANAGEMENT SYSTEMS - GIS PAGE 160F 16