Scope of Work and Deliverables

Scope of Work and Deliverables 1. PROJECT IDENTIFICATION: 1.1 DESCRIPTION 1.1.1 Project Purpose • Inspect, locate, digital video and cleaning of obstr...
Author: Lesley Maxwell
1 downloads 0 Views 97KB Size
Scope of Work and Deliverables 1. PROJECT IDENTIFICATION: 1.1 DESCRIPTION 1.1.1 Project Purpose • Inspect, locate, digital video and cleaning of obstructed or dirty storm sewer system features on I-494 from I-394 to I-94 in Minnetonka, Plymouth and Maple Grove See attachments for specific details. • Global Position System (GPS) location of all newly identified storm sewer infrastructure features identified on the MAP. • Hydraulic Cleaning – Conduct cleaning of obstructed or dirty storm sewer infrastructure per the guidelines established within this document. • Provide updated MAP, digital video, and load all new and existing feature inspection/GPS information into HYDINFRA Database. • Information on condition of hydraulic infrastructure will be used by MnDOT for scoping purposes 2. SCOPE OF WORK 2.1 GENERAL 2.1.1 Contractor will perform all work activities in accordance with applicable State standards, and any other standards as outlined by the State’s Project Manager. 2.1.2 Contractor will provide all necessary equipment and personnel to complete the work in a timely manner, and in accordance with applicable State standards. 2.1.3 Contractor will obtain all necessary permits, provide necessary fees and coordinate work activities with all applicable land owners, land users, and regulatory agencies. 2.1.4 Contractor will be responsible for gaining access to the storm sewer infrastructure system (remove cover and grates) as identified on the MAP. 2.1.5 Contractor will notify the state within 48-hours of the discovery of damaged / broken road surface structures (catch basin, manhole covers, culverts, pipes) and / or other storm sewer features that have the potential to affect the road surface. 2.1.6 If the Contractor or any of the Contractor’s sub–contractor’s / affiliates cause damage to or degrade the existing infrastructure or roadway it will be the Contractor’s responsibility for all repairs and expense to restore the site to at least an pre-existing condition as defined by the State’s Project Manager. 2.2 HEALTH AND SAFETY 2.2.1 Contractor will ensure all personnel involved in the work comply with the requirements of all applicable local, State, and federal health and safety requirements for all parts of the work and especially for work in confined spaces. 2.2.2 Contractor will provide traffic control to provide work zone safety and coordinate with appropriate departments/agencies. 2.2.2.1 Contractor will coordinate all lane closures with State’s Dispatch and any other appropriate agencies. Traffic control and lane closures will be conducted in accordance with the Minnesota Manual of Uniform Traffic Control Devices as indicated on the pages of the Minnesota Department of Transportation (MnDOT) Lane Closure Manual. Improper lane closures will be deemed non-acceptable work for which Contractor will not be paid. 2.2.2.2 Contractor will minimize any traffic disruption. Storm sewer system feature inspection and location activities will not result in the introduction of water, any storm sewer system feature materials/debris, or any other items to any driving surface, especially during cold and/or freezing conditions. Contractor will be responsible for removing any work-related materials from the driving surface and

Page 1 of 5

Scope of Work and Deliverables returning the driving surface to its pre-work conditions prior to opening the affected lanes to traffic. 2.3

OUTPUT PRODUCTS (DELIVERABLES) 2.3.1 The State’s Project Manager will define the storm sewer infrastructure system project limits to be investigated and documented, herein referred to as the “MAP” (See Exhibit B). The Contractor will use the MAP(s) to locate intended features. 2.3.1.1 The State will label/number all known features on the MAP. All newly identified or non-labeled features will be labeled by the contractor. All labels should be labeled in concert with known features if possible. (Example; known feature ID 1000, discovered feature ID 1000a, another discovered feature ID 1000b). 2.3.2 All other storm sewer infrastructure features not identified on the MAP will follow the procedures outlined below. 2.3.2.1 All storm sewer infrastructure additions or changes will be identified on the MAP herein referred to as “MAP EDITS” 2.3.2.2 MAP EDITS will be clearly hand-drawn on the MAP, and will reference and include the approximate location, temporary identification number, flow direction, feature type, feature size, and feature length (if appropriate and other descriptive information as deemed appropriate by the field personnel). 2.3.2.3 MAP EDITS will be consistent on all MAP pages; inconsistencies will be returned for correction and may not be accepted by the State’s Project Manager. 2.3.2.4 MAP EDITS include; structures found in the field within MnDOT right-of-way or project boundary that are not shown on the MAP. 2.3.2.5 The Contractor will perform GPS (Global Position System) locations on all MAP EDITS. 2.3.2.6 Features requiring MAP EDITS will be televised or captured with digital photography (All pipes, culverts, catch basins, manholes, aprons, etc). MAP EDITS will be cleaned as necessary to televise and assess the storm sewer features. 2.3.2.7 MAP EDITS and other storm sewer infrastructure features identified by the State’s Project Manager will be inspected by using the appropriate HYDINFRA Inventory / Inspection Data Form (See exhibit B). 2.3.2.8 The Contractor will submit the MAP EDITS to the State. 2.3.3 Contractor will televise and record all storm sewer infrastructure system features (pipes, culverts, manholes, catch basins, drop inlets, etc.) within the project limits as define on the MAP. 2.3.3.1 Video product will be recorded in digital format (MPEG-1 or MPEG-4). 2.3.3.2 Video files will contain only one feature per MPEG file (example; one pipe, one catch basin, or one structure = 3 MPEG files). 2.3.3.3 Pipe features are segmented from one feature to the next (Example: apron – pipe – apron or catch basin – pipe – catch basin or apron – pipe – catch basin). MPEG files for the above examples would include one for each feature; hence 9 MPEG files would be generated. 2.3.3.4 Contractor will deliver all video MPEG files on a compact disk (CD) or temporary external database to the State’s Project Manager. 2.3.3.4.1 MPEG files structure will be delivered to the State by categorizing files with the appropriate MAP pages (example; MPEG files for MAP page 1 will have a file created that only includes those files associated with MAP page 1 and any overlapping storm sewer feature found on following MAP page. 2.3.3.4.2 MPEG text files (.txt files) will be removed before submitting files to the State.

Page 2 of 5

Scope of Work and Deliverables 2.3.4

2.3.5

2.3.6

2.3.7.

2.4

Contractor will complete the HYDINFRA Inspection Forms for newly identified features and specified existing features (See Exhibit B for example of Forms). Inspections will rate all features in accordance to the HYDINFRA methodologies or follow guidance of the State’s Project Manager. 2.3.4.1 The Contractor will upload the HYDINFRA information to the HYDINFRA web site at least two weeks prior to the contract expiration date and provide the State an electronic format copy (CD or external hard drive) 2.3.4.2 Contractor is responsible for insuring that the most up to date HYDINFRA Forms are incorporated into GPS equipment or other data collection methodologies. The Contractor will collect GPS (Global Position System) locations for all newly identified storm sewer infrastructure features on the MAP EDITS. Storm sewer features may include the following; manholes, catch basins, grit chambers, structural pollution control devices, pipes, aprons, and culverts. All pipes will be loaded into HYDINFRA using the TPF_Pipeand Insp record type of the published format where Longitude/Latitude’ UTM X / UTM Y are the location of the upstream end of the pipe and Pipe Latitude 2/Pipe Longitude 2/Pipe Northing 2/Pipe Easting 2 are the location of the downstream end of the pipe, and the other data that is included in the GPS HYDINFRA Arc Pad Forms and other required data is entered into the published format as described in the hyd-csb.xls spreadsheet at http://www.dot.state.mn.us/bridge/hydraulics/hydinfra/geopakandalternatedata.html Summary of Final Output Products (DELIVERABLES) Contractor will provide output products listed below on or prior to the work expiration date: • The MAP with all the MAP EDITS – deliverable due November 22, 2013 • GPS rover files with all newly identified or modified MAP EDIT features and original MAP features if appropriate - deliverable due November 22h, 2013 • CD’s or external hard drive with appropriate MPEG video files and digital photos - deliverable due November 22, 2013 • Verification that all uploaded information has been accepted or approved by the Hydinfra database – deliverable due November 27 , 2013 • Documentation of proper disposal of all materials / sediment generated during cleaning activities – November 27, 2013 if deemed appropriate

VIDEO INSPECTION & INVENTORY INSPECTION INSTRUCTIONS: 2.4.1 The appropriate HYDINFRA Form will be completed by the Contractor for all newly identified or specifically identified storm sewer infrastructure features on the MAP EDITS. 2.4.2 Video inspections will be conducted using remote controlled, self-propelled video cameras of appropriate size and functionality to assess all areas of each feature, and to provide color video. Video will be in digital video format (MPEG-1 or MPEG-4). 2.4.3 Televising will be carried out at a slow rate of speed and provide good lighting sufficient to illuminate the entire circumference of the feature up to 20 feet ahead of the feature. Video inspections which are collected too fast to identify problem areas will be rejected and deemed non-acceptable by the State’s Project Manager for which the Contractor will not be paid. 2.4.4 Video inspection will include televising of the entire feature; completing a 360 degree pan of broken, separated, or otherwise damaged joint, crack, or defect encountered in any feature. 2.4.5 Pipe failures or deficiencies, including broken segments, separated, damaged joints, cracks or defects encountered in any pipe features will be segmentally identified for all pipe inspections. Segmental identification will show the entire length of the pipe feature and the

Page 3 of 5

Scope of Work and Deliverables location of the failures or deficiencies and the linear distance from the beginning of inspection (unit in feet). 2.4.6 Video inspection of non-linear features will pan the entire inner circumference of manholes, catch basins, and drop inlets from top-to-bottom. 2.4.7 During televising if that camera encounters a pipe bottom that is broken (non-existent or rusted out, CMP pipes) and not traversable, then said pipe will be televised from the other end of the pipe if possible. 2.4.8 Video inspections will provide a “still shot” or a digital photo for individual non-linear features; aprons, manholes, catch basins, and drop inlets, etc. 2.4.9 Contractor will provide text documentation regarding beginning point, ending point, approximate bearing if appropriate, structure diameter, material, length, height, and defects. 2.4.10 After the first full week of televising, the Contractor will submit the video inspection products on CD’s or external database, completed database forms and a copy of edited map for the State’s Project Managers review.

2.5 GPS INSTRUCTIONS 2.6.1. Contractor will collect individual GPS points for specified storm sewer infrastructure features identified on the MAP and will collect GPS for all MAP EDITS features. 2.6.2. The GPS rover files will be recorded in UTM’s, Zone 15 North, NAD 1983 (conus), MLS (mean sea level), with coordinate units set to meters. 2.6.3. GPS rover files will be collected as Field Data Files (*.ssf), then 3D post-processed as a Corrected File (*.cor). 2.6.4. GPS accuracy will be at a minimum sub meter grade, data that is not sub meter quality may be rejected. 2.6.5. The Contractor will provide both the raw rover files (*.ssf) and the corrected rover files (*.cor). and the exported (*.hif) or (*.cvs) files if appropriate. 2.6.6. GPS locator will be a Registered Land Surveyor or have received training in use of Hydinfra data dictionary from appropriate MnDOT personnel. 2.6 SCHEDULE AND COMMUNICATION 2.6.1 Before the awarded Contractor can begin work the Contractor will hold a meeting and provide a schedule to the State’s Project Manager. 2.6.2 Contractor will not suspend work without prior State approval. Workdays lost due to inclement weather and/or snow removal will not be added to the completion date of the project. 2.6.3 Work stoppages beyond the control of the Contractor will not result in penalty to the Contractor. However, said stoppages will not result in extension of the completion date of the project. 2.6.4 Appropriate personnel from State and Contractor will be required to attend status meetings as determined by the State’s Project Manager. 2.7 DEFINITIONS: 2.7.1 Storm sewer system features include all storm drainage pipes, culverts, manholes, catch basins, drop inlets, aprons, structural pollution control devices etc., used to convey storm water within the project limits.

2.8 HYDRAULIC CLEANING INSTRUCTIONS – OPTIONAL TASK AT DIRECTION OF PROJECT MANAGER

Page 4 of 5

Scope of Work and Deliverables 2.8.1

2.8.2

2.8.3

2.8.4

2.8.5

2.8.6 2.8.7

Contractor will identify storm sewer infrastructure features which require cleaning, and provide a list and justification for cleaning (video CD’s or digital photographs) to the State’s Project Manager before cleaning (other that spot debris removal). Cleaning may be necessary if enough sediment / debris exists within the feature to prevent an accurate overall assessment of the feature or limits the ability of the camera to inspect the entire feature. Spot removal of obstructions or debris accumulations is expected and will be performed by the Contractor without prior State’s approval or notice. Cleaning of pipe features less than 24 inches in diameter may occur without pre-approval by the State Project Manager if four inches or more material exists within the pipe for the majority of their length. Cleaning of pipes that are 24 inches or greater may occur without pre-approval by the State Project Manager if six inches or more of material exists within the pipe for the majority of their length. Metal pipes within the project corridor will require cleaning if sediment within a pipe does not allow the televising to accurately assess the bottom of the pipe for the majority of the length. Cleaning of all pipes less than 24 inches in diameter will require approval from the State’s Project manager if the pipe is ≥50% full of sediment / debris for the majority of their length. Cleaning of all pipes 24 inches or greater will require approval from the State’s Project Manager if the pipe is ≥33% full of sediment / debris for the majority of their length. State’s Project Manager may require additional storm sewer system feature cleaning as necessary, based on review of video inspections. Contractor will dispose of materials according to all Minnesota Pollution Control Standards and will document such disposal for the States review. The State’s Project Manager may identify site(s) to dispose of such material; otherwise contractor will be responsible for identifying and dumping at an approved location. 2.8.7.1 Spoil materials and debris will not be deposited within MnDOT right-of-way. 2.8.7.2 No hazardous material is anticipated to be encountered in the vicinity of the project. 2.8.7.3 If hazardous material is encountered, Contractor is to suspend work immediately in the vicinity of the hazardous material, notify the State’s Project Manager, and quarantine equipment which has come in contact with the hazardous material. 2.8.7.4 The State’s Project Manager will determine the course of action to be followed. Costs of identifying, handling, and disposal of hazardous material will be considered extra services and outside the scope of this project.

THE BALANCE OF PAGE IS INTENTIONALLY LEFT BLANK

Page 5 of 5