My WebLink
|
Help
|
About
|
Sign Out
Home
8I Consent 2013 0122
CityHall
>
City Clerk
>
City Council
>
Agenda Packets
>
2013
>
Packet 2013 0122
>
8I Consent 2013 0122
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
2/7/2013 12:53:18 PM
Creation date
1/16/2013 2:39:25 PM
Metadata
Fields
Template:
CM City Clerk-City Council
CM City Clerk-City Council - Document Type
Staff Report
Document Date (6)
1/22/2013
Retention
PERM
Document Relationships
_CC Agenda 2013 0122 CSAmended+RG
(Reference)
Path:
\City Clerk\City Council\Agenda Packets\2013\Packet 2013 0122
Reso 2013-005
(Reference)
Path:
\City Clerk\City Council\Resolutions\2013
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
31
PDF
Print
Pages to print
Enter page numbers and/or page ranges separated by commas. For example, 1,3,5-12.
After downloading, print the document using a PDF reader (e.g. Adobe Reader).
Download electronic document
View images
View plain text
<br />Consulting Services Agreement between <br />City of San Leandro and RMC Water and Environment—Exhibit A Page 3 of 9 <br />Task 3 – Flow Monitoring <br />Flow monitoring is necessary to quantify dry and wet weather flows in the system and to calibrate the sewer <br />system hydraulic model. A flow monitoring plan and site reconnaissance was conducted under a previous <br />contract. This task involves the following activities: <br /> <br />After the City’s approval of the final flow-monitoring plan and traffic control plans, RMC (or their sub <br />consultant) will install, calibrate and maintain the flow meters for up to 2 months during the rainy season <br />and remove the flow meters at the end of this monitoring period. In addition, 3 recording rain gauges will <br />also be installed to capture rainfall data during the flow monitoring period. RMC will review flow monitoring <br />site reports to confirm final flow meter locations and will review the flow monitoring data every two to three <br />weeks during the flow monitoring periods to check data quality and consistency. RMC will provide final <br />electronic data files (15-minute data) at the conclusion of the monitoring. <br /> <br />Task 3 Deliverables: <br /> Flow monitoring data for each site including depth, velocity, flow rate, and rainfall in MS Excel <br />format <br /> <br />Task 3 Assumptions: <br /> 21 area-velocity flow meters and 3 rain gauges will be installed for a period of up to two months <br />during the 2012/13 wet weather season. <br /> Flow meters will be installed during late January or early February 2013. <br /> City will provide any required encroachment permit(s) for work in City streets. <br /> <br />Task 3 Schedule: <br /> Flow monitoring data shall be submitted by June 30, 2013. <br /> <br />Task 4 – Hydraulic Model Development <br />Under this task, RMC will develop and calibrate a hydraulic model of the collection system. RMC will use <br />its own software licenses for the modeling work; however, all model files developed and generated as part <br />of the project will be provided to the City at project conclusion. RMC will use InfoWorks CS, a fully dynamic <br />hydraulic modeling program from Innovyze, for this work. <br /> <br />Subtask 4.1 Develop Model Network <br />This subtask includes the following activities: <br /> Develop and Validate Model Network. Using data from the City’s GIS and asset inventory <br />database, RMC will develop a hydraulic model of the sewer system. Available sewer record <br />drawings and data from the City’s previous Hydra model (as documented in the Appendix to the <br />City’s 1993 Master Plan report) and H2OMap SWMM model of the Transit Oriented Development <br />(TOD) area (if available from the City) will be used to supplement the data in GIS and existing <br />databases. The modeled sewer network will include, at a minimum, all sewers 10 inches and <br />larger (i.e., the “trunk network”) and critical smaller diameter pipes, including those that serve areas <br />of significant size, are known or suspected by City staff to have capacity problems, or serve areas <br />of potential future growth or redevelopment. Less critical smaller-diameter pipelines will not be <br />included in the initial model but could be added in the future as need ed. The model will also include <br />any pump stations located within the trunk network. Following the construction of the model <br />database, a QA/QC process called “model validation,” will be used to verify the data before
The URL can be used to link to this page
Your browser does not support the video tag.