Professional Documents
Culture Documents
Gomes Samaras Lighting Controls SOO NCBC 2016 2016-05-10
Gomes Samaras Lighting Controls SOO NCBC 2016 2016-05-10
2
Learning Objectives
• At the end of this session you will be able to:
1. Make intelligent comments in the design review that would
improve the energy efficiency and the quality of bids
2. Review a lighting controls sequence of operation with
confidence
3. Recognize when lighting control sequences require
manufacturer-specific sequences instead of generic
sequences that can be used across many projects and know
where to go to find that information in manufacturer literature
4. Identify maintainability issues for lighting controls in design
review, just like mechanical equipment
3
What We’ll Cover
• Perspective
• Lighting Control Basics
• Components
• Systems
• Design
• Reviews
• Sequences of operation
• Productive comments
• Maintainability
• Constructability challenges
• Trends
4
Perspective: How we got here
5
Perspective: IRL
HOT POTATOES….
6
Perspective: IRL
HOT POTATOES….
7
Perspective: The CxP’s role
8
The Designer(s)
What is their thought process?
• Lighting Consultant:
Often Partial scope (Front of House/Public spaces only)
Design Services to 100%DD or 50%CD level
Not fully engaged for Construction/Bid Set
• Architect:
Creates base plans
Often selects decorative lights/scones (if not included in lighting
designer’s package)
Makes changes
• Electrical Engineer:
Often responsible for BoH areas
Has to pull together the latest base plans/designs from the
Architect/Lighting Consultant
Responsible for Circuiting
Documents the controls in the Permit/Bid Set
9
The Designer(s)
What’s Missing???
• Lighting Consultant:
Not responsible for complete system
Not involved during construction when design is refined
Not responsible for circuiting (thus controls/details)
• Architect:
Makes changes to base plans (forgets to share with team)
Doesn’t address control intent
Did I mention? ...Makes changes
• Electrical Engineer:
Is often not involved in the OAC meetings where users discuss
operational needs.
Often defaults to the Manufacturer’s recommendations
Often defaults to the code requirements (code minimum)
Struggles with documentation with multiple named specs
10
Basic Components
• Occupancy sensors
• Daylighting
• Timeclocks, Janitor Overrides, Scene Controllers
11
Occupancy Sensors
• Types:
• PIR (Passive InfraRed)
• Ultrasonic
• Microphonic
• Dual Technology
• Trigger/Retrigger
Occupancy/Vacancy
• Delay to Off (Dwell)
• Coverage range
• Location
Photocells/Daylight Sensors
• Types
– Open loop
– Closed loop
– Combo
– skylight
• Technology
– Affects placement
• Coverage range
– Closed vs open loop
• Mounting location
– Not too high
– Not obstructed
– No hot spots
21st NCBC Conference
Timeclocks, Janitor Overrides, Scene Control
• Shown on drawings?
• Timeclock
• Hours of operation
• Sweeps
• Zones
• Janitor Override
• Dwell
• Retrigger?
• Scene Control
• Labels
• Zones
• Sequence
14
Lighting Control Systems
What are we dealing with?
Networked /
Integrated Intelligent
Efficiency
Standalone
Complexity
15
Lighting Control Systems
What are we dealing with?
• Standalone
• Doesn’t talk to anyone but itself
• Usually single function
• Local programming
• Local Integration
• Multiple devices / inputs
• Local programming
• Local control
• Additional inputs
• Networked / Intelligent
• Wired or Wireless
• Addressable
• Intelligent Fixtures
16
Lighting Control Systems
Standalone
17
Lighting Control Systems
• Standalone
• Doesn’t talk to anyone but itself
• Usually single function
• Local programming
• Local Integration
• Multiple devices / inputs
• Local programming
• Local control
• Additional inputs
• Networked / Intelligent
• Wired or Wireless
• Addressable
• Intelligent Fixtures
18
Lighting Control Systems
Local Integration
19
Lighting Control Systems
• Standalone
• Doesn’t talk to anyone but itself
• Usually single function
• Local programming
• Local Integration
• Multiple devices / inputs
• Local programming
• Local control
• Additional inputs
• Networked / Intelligent
• Wired or Wireless
• Addressable
• Intelligent Fixtures
20
Networked Lighting Control Systems
21
Networked / Intelligent Lighting Control Diagram
Addressable
22
Networked / Intelligent Lighting Control Diagram
Wired -OR- Wireless
23
Beyond the Perspective and Basics
Implementation
24
Owner’s Project Requirements (OPR)
• Design assumptions
• Basic control strategies
• Timeclocks, janitor overrides
• Occupancy control
• Integrate with HVAC?
• Daylighting
• Demand response
• Outdoor lighting
• Manual dimming
• Which spaces?
• Task tuning
• Manufacturer
• Standalone or Networked?
26
Design Review
• Encourage sole-source
• Parallels with HVAC Controls
• Encourage SOOs
• Lay it out for them
• Invest in a go-to explanation
• Can the product do what the SOO asks?
• Examples
• daylighting control + continuous dimming and non-
dimming ballasts
• ADR with standalone system
• Bathrooms set on vacancy mode
27
Reviewing the Lighting Controls
Don’t Be Caught in a Dark Bathroom with Your Pants Down
• Lighting controls legend • Fixture schedule
• Symbols should differ for • Lamp type
model type
• Ballast/driver type
• Hallway occ sensor vs
• Specs
office occ sensor
• Sensors
• Occ Sensor application
• Control system
• Ultrasonic or Dual
Technology Sensors in • Standalone or
spaces with barriers Networked?
• Coverage pattern
matches application &
area
• Daylighting
• Fixtures can do dimming
• Number of photocells
match control type
• Demand Response
• Disaggregated zones
• Dimming
• Timeclock
• Hours of operation
• Zones controlled
• Overrides
• Locations
• Zones
• Time delay 29
Creating and Reviewing Sequences of Operation (SoO)
Do you want to
build a …
…a system?
…a platform?
30
General Process
Inputs General Design Intent or Modifications: 1 Modifications: 2 Modifications: 3
Strategy during normal
Operation
Photo-sensor /
Daylighting
Occupancy
Sensing
Tuning
Personal
Controls
31
General Process
Inputs General Design Intent or Modifications: 1 Modifications: 2 Modifications: 3
Strategy during normal
Operation
Photo-sensor / Automatically balance
Daylighting available daylight using
dimmable electric lighting
to provide 50FC at +30” at
all occupied times
Occupancy Reduce Light levels in
Sensing corridors, stairwells, &
unoccupied spaces during
time of vacancy
32
General Process
Inputs General Design Intent or Modifications: 1 Modifications: 2 Modifications: 3
Strategy during normal After hours / ADR ADR – Alt.
Operation Weekends
Photo-sensor / Automatically balance No Mod. Reduce set point
Daylighting available daylight using to 20FC
dimmable electric lighting
to provide 50FC at +30” at
all occupied times
Occupancy Reduce Light levels in Turn light off in Turn light off in Reduce timeout
Sensing corridors, stairwells, & corridors, corridors, intervals
unoccupied spaces during stairwells and stairwells and
time of vacancy unoccupied unoccupied
spaces when spaces when
vacant vacant
Tuning Reduce light levels on area No Mod. Reduce light
basis to correct for over- levels even
lighting further
Personal Light levels are selected No Mod. Light levels
Controls based on local user prevented from
preference exceeding set
level
33
Sequence of Operations Structure
• Components
• OS, PC, BMS, Time of Day
• Their role
• Fixture-integrated
• Standalone
• Information flow:
• Input
• Associated Output
• Communication protocol
• Wired
• Wireless
• BACNet, ZigBee,
other…
34
SoO’s come in numerous forms
• Narrative/Descriptive: Pros/Cons
• Tables or Operational forms: Pros/Cons
• Graphic: Pros/Cons
• Details with Notes (Pictorial): Pros/Cons
• Manufacturer Checklist: Pros/Cons
35
Example SoO: Narrative/Descriptive
36
Example SoO: Tables / Operational Form
37
Example SoO: Graphic
38
Example SoO: Details / Pictorial
39
Example SoO: Pictorial / Narrative
40
Example SoO: Pictorial / Narrative
41
Example SoO: Mfr’s Check Lists…
42
Example SoO: Mfr’s Check Lists…
43
Manufacturer-Specific Requirements
The case for sole-source
44
Do your homework
45
Anatomy of a productive comment
Prevent drama
46
Implementable comments
• What do we see?
• What’s wrong?
• Significance?
• How to Fix it?
• What do we
recommend?
47
Recommendations that aren’t controversial
• Be respectful I demand
• It’s not about you – respect and I’m
it’s about the project gonna talk down
• Establish a positive tone to everyone until
• Avoid Authoritarian tone I get it!
• Best: “We
recommend…”
• Bad: “In our
opinion…”
• Provide an example –
make it easy for them
48
Example Design Statement
What
Description we
of Issue see Dwg Recommended Changes
The mechanical drawings indicate M6.3 Coordinate with the mechanical engineer
that occupancy sensors will be used E5.1 and make it clear that the lighting control
in the mechanical control sequences. system will need to support the HVAC
It is not clear on the electrical control system.
drawings that the WattStopper What’sAccording to WattStopper, you can either:
system will support the exchange of
this information to the HVAC wrong1. Add an LMRL-100 to each room,
which has a contact closure that can
controls. relay occupancy status to the HVAC
Bringing this point from the lighting control system.
control system to the BMS will be a
Significance
significant effort (i.e. time and money
2. If a Segment Manager is used on the
project, it’s possible to export a table
for the contractor) and would require of room status to the HVAC control
a fair amount of coordination with the system over BACnet/IP, but the two
lighting control vendor (more time & control systems must be on the same
money). If the contractor misses it network.
and then has to do the work they
didn’t budget for (but is contractually Clarify which option will be used and
obligated to), there is a chance that make it clear in the mechanical and
the quality of workmanship will be electrical drawings which will be used.
deficient and the system may not
work reliably. Recommendation
49
Maintainability (don’t buy cheap stuff)
• GUESSWORK
• Impossible sequences
• “Performance
specification”
• New technologies
• New codes
51
Trends…. Smart Lighting
•DESIGN
Challenges of the designer
What key elements does a good SOO need to have?
How does the contractor interpret the SOO at bid time?
Rapidly evolving marketplace with highly proprietary equipment
•CONSTRUCTION
Channels the SOO goes through
How does the contractor interpret the SOO during construction?
Process (Is this setup/programming?)
•COMMISSIONING
How is it (SOO, OPR, specs, or other?) interpreted/enforced by the Cx agent?
Issues often encountered:
•Specified products can’t do what the SOO asks for.
•Lighting designed by one consultant, circuiting (and/or controls) designed by another.
•Moves/Adds Changes very costly with some mfrs. as only a service tech can do them.
•Specified system is too complex for the user to maintain themselves.
4a. Specified system is more expensive than project SOO requires.
•Design continues to evolve when the SOO doesn’t get revised.
•Electrical should follow what HVAC has been doing for decades. Consider the following: (THIS IS ABSOLUTELY AWESOME)
HVAC LIGHTING/ELECTRICAL
One consultant designing HVAC and Often two consultants
associated Controls
SOO standard deliverable/spec item No standard
Designed with the Client’s ability to Designed to the Consultant’s
maintain standard/opinion
Controls Sub-contractor specializing in Left to Electrical Sub (who knows switchgear
HVAC controls better)
54