My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
HDR Engineering Inc 7/9/2019
>
Contracts
>
6 Years Then Destroy
>
2021
>
HDR Engineering Inc 7/9/2019
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
7/23/2019 9:48:05 AM
Creation date
7/23/2019 9:47:45 AM
Metadata
Fields
Template:
Contracts
Contractor's Name
HDR Engineering Inc
Approval Date
7/9/2019
Council Approval Date
7/3/2019
End Date
6/30/2021
Department
Public Works
Department Project Manager
Souheil Nasr
Subject / Project Title
Update Comprehensive Water Plan
Public Works WO Number
UP3718
Tracking Number
0001899
Total Compensation
$760,233.00
Contract Type
Agreement
Contract Subtype
Professional Services
Retention Period
6 Years Then Destroy
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
69
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).
View images
View plain text
F)R <br /> 3. Add average day demand and customer class information to City-provided GIS layer of <br /> meters. <br /> 4. Select model nodes that will be used as demand nodes within the model (excluding nodes <br /> on transmission lines, node near facilities, etc.). <br /> 5. Using InfoWater's demand allocation tool, assign demands to demand nodes within the <br /> model. Customer class demands will remain separated at each node to allow different <br /> diurnal curves to different customer classes for future model use. <br /> 6. Adjust total demand by pressure zone area according to demand forecasts. <br /> 7. Allocate future demands by planning area boundaries and/or land use. <br /> 8. Non-revenue demands (fire flow, leakage, etc.)will be equally distributed among model <br /> nodes. <br /> 9. Select model nodes that will be used as fire flow nodes within the model (excluding nodes in <br /> areas lacking hydrants or on transmission lines). Using adjacent land use/zone information, <br /> assign an appropriate fire flow goal based on customer class fire flow requirements. <br /> 10. Add fire flow goals for specific users with large fire flow requirements (assumed to be no <br /> more than 10 locations). <br /> 11. Add junctions, piping, and other infrastructure to model for areas of future development to be <br /> considered for future scenario model runs(these would be inactive for model runs reflecting <br /> the current condition). <br /> Model Calibration <br /> 1. Provide brief technical memorandum that outlines the plan for field testing and identifies data <br /> needed to complete a steady state calibration using fire flow tests. The technical <br /> memorandum will provide direction for City staff to conduct field data collection including: <br /> a. Selection of sites for hydrant tests, <br /> b. Selection of sites to place recording pressure gauges (if available)for hydrant tests, <br /> c. SCADA information to collect to develop boundary conditions, and <br /> d. Forms to record data during hydrant field testing. <br /> HDR will work with City staff to determine appropriate locations for hydrant tests. It is <br /> assumed that up to 35 tests would be completed. <br /> 2. The technical memorandum will also provide direction on data needs that need to be <br /> collected within the system during the period of calibration field testing. SCADA or other <br /> suitable information for each of the following facilities(as available)will need to be collected <br /> electronically (as possible) at 15-minutes (or finer if available)for a minimum duration of one <br /> week for hydrant testing (or longer if field testing takes more than one week's time to perform <br /> hydrant tests): <br /> a. Reservoir levels <br /> b. Pump station flows and/or pump on/off levels <br /> Everett Comprehensive Water Plan June 12, 2019 <br /> Exhibit A—Scope of Services Page 19 of 30 <br />
The URL can be used to link to this page
Your browser does not support the video tag.