non res lighting subcommittee n.
Skip this Video
Loading SlideShow in 5 Seconds..
Non-Res Lighting Subcommittee PowerPoint Presentation
Download Presentation
Non-Res Lighting Subcommittee

Non-Res Lighting Subcommittee

114 Vues Download Presentation
Télécharger la présentation

Non-Res Lighting Subcommittee

- - - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript

  1. Non-Res Lighting Subcommittee Retrofit Lighting Standard Protocol Review 10/23/13

  2. What has happened since March? • Incorporated comments from March subcommittee meeting into protocol • Further revised protocol and interview guide to use consistent language • Split protocols into “retrofit” and “LPA required” instead of “pre-conditions” and ”current practice” • In reality, retrofits could have both baselines present • Waiting to develop provisional data collection section until remainder of protocol is reviewed

  3. Key Definitions Space Use Type (SUT) • For retrofits, SUT is used to define a space inside/outside the building with a specific use and occupancy hours of use (HOUocc) • SUT is linked to LPA requirements for installations governed by code System • Combination of fixtures associated with a single control type within each SUT • Takes into account individual controls effects on different fixtures • (Ex. daylight sensors vs. manual switch in same space) • Many fixtures within a SUT can be considered a single system if they have the same control types (i.e. multiple occ sensors in open office) • Lighting calculator would require line item entry of fixtures and controls, (i.e. a system) with a SUT and HOUocc for each system Project • Sum of all SUT’s and their systems is considered the project • HVAC IF based on primary equipment used to condition entire project

  4. SUT SUT SUT SUT SYSTEM* SUT SYSTEM SYSTEM SYSTEM SUT PROJECT *If HOUocc are the same for all fixtures/controls. Systems cannot cross a SUT.

  5. Example Space Data Collection • Baseline data collection • Identify a SUT based on HOUocc and use of the space • Identify each system within a SUT • A system is associated with a particular control type • These systems all occur within the same SUT therefore HOUoccshould be the same • Note: Systems cannot cross SUT • Eventually determine controlled HOU for each system • Apply CSF and results of site interview Gathered by interview

  6. Example Space Data Collection • Determine baseline power of each system • CSF is used to apply an adjustment to HOUocc for each system • Interview answers used to roll up to annual savings Calculator does this based on inputs

  7. Example Space Data Collection • Efficient Case Data Collection & Consumption • Utilize same SUT boundaries when applicable • Note: Major change in SUTs means retrofit protocol N/A • Same method as baseline for fixture count, quantity, etc. for each control type within a system • Calculator can determine savings allocation • Controls savings vs. wattage reduction savings

  8. Where things will get tricky • Some controls affect both wattage and HOU • Ex. Combo daylight/occ sensor • Would need to define consumption and HOU at each power level • Can we do so accurately with an interview guide? • HOU required for each space (SUT) • Some programs do this for whole building only • Plan to use interview guide to test whole building occupancy schedule to individual SUT schedules for possible simplification in the future

  9. Interview Guide • Need to link answers from interview guide to savings calculation components • i.e. if practitioner asks a question, the answer needs to be used for something • Limit interview guide to only questions that are needed to inform HOU-related estimates • Includes space HOU and controls-related HOU • Ex. combo daylight/occ sensor HOU reduction

  10. Interview Guide • Need to determine if the guide asks the correct questions to get answers needed for savings estimation • Can we remove some? Or refine them to get at a more reliable answer? • Understand that programs might use their own interview guide to streamline process in field. • i.e. Developing an electronic guide would allow for flexibility with many SUTs

  11. Provisional Data Needs – Next step • Need to collect provisional data to prove the Simplest Reliable Method is reliable compared to a best practice approach • We don’t appear to have reliable data on: • HOU estimates • Controls Savings Fractions • Fixture wattages? • Recent data suggests manufacturer rating may not be reliable • Large number of possibilities given various control types and SUTs • 150+ possibilities just using current list of options

  12. Comparison of Methods Need to collect provisionally * Prior best practice was to use manufacturer’s default lamp/fixture rating