11.07.2015 Views

12th International Symposium on District Heating and Cooling

12th International Symposium on District Heating and Cooling

12th International Symposium on District Heating and Cooling

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

The <str<strong>on</strong>g>12th</str<strong>on</strong>g> <str<strong>on</strong>g>Internati<strong>on</strong>al</str<strong>on</strong>g> <str<strong>on</strong>g>Symposium</str<strong>on</strong>g> <strong>on</strong> <strong>District</strong> <strong>Heating</strong> <strong>and</strong> <strong>Cooling</strong>,September 5 th to September 7 th , 2010, Tallinn, Est<strong>on</strong>iaEnergy <strong>and</strong> heat load usage was primarily evaluated bystudying the dynamic differences between the forward<strong>and</strong> return temperature of the radiator system inrelati<strong>on</strong> to the flow. These readings were then verifiedby specificati<strong>on</strong>s from the district heating providerregarding energy c<strong>on</strong>sumpti<strong>on</strong> <strong>and</strong> momentary heatload usage.Using this set-up we scheduled different types oftemporary heat load reducti<strong>on</strong>s <strong>and</strong> studied theireffects <strong>on</strong> the measured data. During this study westudied three primary types of temporary heat loadreducti<strong>on</strong>s:system performs a c<strong>on</strong>trolled heat load recovery inorder to avoid unwanted heat load peaks after thereducti<strong>on</strong>.The same values are shown for a l<strong>on</strong>g heat loadreducti<strong>on</strong> in Figure 2. The heat load reducti<strong>on</strong> startsslightly before the 600 minute mark <strong>and</strong> c<strong>on</strong>tinues forseveral hours until about the 900 minute mark. Afterthat the c<strong>on</strong>trol system performs a c<strong>on</strong>trolled recoveryin order to return to the original operati<strong>on</strong>al state.L<strong>on</strong>g – Four to eight hours of c<strong>on</strong>tinuous heatload reducti<strong>on</strong> with different intensityShort – Up to <strong>on</strong>e hour l<strong>on</strong>g heat loadreducti<strong>on</strong>s with different intensityRecurring – Several short subsequent heatload reducti<strong>on</strong>s with short pauses in betweenWhen we studied the different types of heat loadreducti<strong>on</strong>s we took care in allowing the buildingsthermal process to return to its original state betweeneach reducti<strong>on</strong> so that the reducti<strong>on</strong>s would notinfluence each other. This was d<strong>on</strong>e in between eachreducti<strong>on</strong> except in those cases when then purposewas to explicitly study the interacti<strong>on</strong> betweensubsequent heat load reducti<strong>on</strong>s.EXPERIMENTAL METHODFigure 2: dT in radiator circuit with l<strong>on</strong>g heat loadreducti<strong>on</strong>Figure 3 shows the same values for a series ofrecurring heat loads.Figure 1 shows the temperature difference between theforward <strong>and</strong> return temperature in the radiator circuitduring a short heat load reducti<strong>on</strong>.Figure 1: dT in radiator circuit with short heat loadreducti<strong>on</strong>The heat load reducti<strong>on</strong> starts at about 60 minutes <strong>and</strong>c<strong>on</strong>tinues until the 120 minute mark. Between the 120minute mark <strong>and</strong> about the 160 mark the c<strong>on</strong>trol246Figure 3: dT in radiator circuit with recurring heat loadreducti<strong>on</strong>Each of the heat load reducti<strong>on</strong>s in Figure 3 is <strong>on</strong>e hourl<strong>on</strong>g intersected by <strong>on</strong>e hour l<strong>on</strong>g recovery periods.The first reducti<strong>on</strong> starts at the 60 minute mark <strong>and</strong>c<strong>on</strong>tinues until the 120 minute mark.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!