Laserfiche WebLink
i <br />llf <br />It <br />l� <br />ll' <br />« IDM will explore the nuances of the City's <br />hydraulic characteristics /sensitivity and adjust <br />model time simulations accordingly. IDM's <br />experience with hydraulically similar systems <br />indicates that the City's hydraulic model may best <br />be served using a 15- minute time interval for <br />hydraulic simulations. <br />Hydraulics, and the interaction with water assets, <br />drives system operations, and become the explaining <br />factor for system performance, including pipe breaks, <br />water quality issues, customer service issues, and <br />capital improvement projects. <br />Our team represents hydraulics and hydraulic model <br />experts, Paul Hauffen and Patrick Moore, Project <br />Manager and Hydraulics Technical Advisor, <br />respectively, are widely published in the area of <br />hydraulics and water quality, and contributing <br />members of the Engineering Modeling Applications <br />Committee. Paul will lead the Hydraulics Assessment <br />phase of this Project and evaluate critical hydraulic <br />aspects of both system operations and the hydraulic <br />model, including but not limited to: <br />• System hydraulic grade lines (HGLs) <br />• System hydraulic schematics <br />« Locations of zone boundaries <br />« Pump curves and overall efficiencies <br />• SCADA controls for <br />• Booster station and wells, <br />• Interconnects, <br />• Treatment facilities (as applicable) <br />* PRV Settings, and locations <br />• Service area topography <br />• Pipe Break History <br />IDM has analyzed hydraulically similar systems across <br />Southern California, including: <br />• City of Downey -CA <br />City of Lakewood -CA <br />• City of El Centro -CA <br />• Indio Water Authority -CA <br />• City of Brawley -CA <br />2. Implementation Plan <br />Technical Memorandum (TM) 43 — <br />0 Demand Development: Hydraulic <br />model demands, usage patterns, and <br />fire flows demands will govern the <br />direction and quantify of water flowing <br />through the City's distribution system and model. <br />Having an accurate understanding of the <br />1) distribution /allocation of water demand, and 2) the <br />typical hourly water usage, and 3) required fire flow <br />demands per land use category will allow the model <br />to predict areas of high headloss, velocity, or pressure <br />deficiencies, <br />• System Demands — current system demands will <br />be developed from geocoded consumption <br />records, water production, and Top 15 users. <br />Developed from parcel layers and billing records, <br />geocoded to nearest tributary hydraulic model <br />junctions. <br />• Calibration Period — IDM will work with the City <br />to determine the maximum day and average day <br />calibration periods. Based on this, data will be <br />requested and reconciled to base demand periods <br />and diurnal curves (hourly usage). Peaking factors <br />for average day, maximum day, and peak hour <br />(from diurnal curves, see below) will be <br />developed and applied, using historic production <br />records ( SCADA), DWR reports, consumption, and <br />other key data sources. <br />• Diurnal Curves — hourly usage patterns will be <br />developed using a 15- minute interval, and <br />applied for the 72 -hour calibration period <br />determined for maximum day and average day <br />demand conditions. Data will be extracted from <br />SCADA for 24 -hours prior, and 24- hours following, <br />the calibration period. Patterns may be <br />developed and assigned based on specific land <br />uses, by pressure zone, or to the overall system, <br />dependent on best available data. SCADA will be <br />used to generate hourly fluctuations. <br />• Top 15 Users: IDM will contact each of the Top <br />15 users for usage. IDM will individually allocate <br />usage for the Top 15 users to their respective <br />model junction to ensure they receive a user - <br />specific base demand, hourly usage, and fire flow. <br />We can be more, together, <br />9 <br />