top 2 pitfalls in laying out a poe lighting and automation
TRANSCRIPT
Top 2 Pitfalls in Laying out a PoE Lighting and Automation System
NOT FULLY VETTING THE DESIGNPitfall #1
Design is a closed loop!Most processes never close the loop and stop at criteria
Validity feedback from:• AHJs, code officials (define “why”)• End User (define “what”)• Installer (defines “when” and “how much”)
Objectivity feedback from:• Members of BICSI, CABA, et.al.• Outside consultants (ex Luis Suau, Sinclair)• Manufacturers (ex PoE Texas)
Things that need vetting Budget Lighting Specs Energy code requirements Level of construction
New Substantial retrofit (removing walls, ceilings) Light retrofit (keeping walls, reuse wires)
Owner Objectives “Cool factor” desired – ex. touch screen tablet control vs 4 button wall switches
How to handle change requests Pre CO (certificate of occupancy) Post CO (when tenants are in space)
How different systems will interact Will occupancy events after hours send email notifications or just turn on a light Will people counters just collect data or will they proactively notify the HVAC system? Security camera activity – turn on lights, email someone or log to a file
Redundancy & resilience UPS and power outage scenarios Dashboard and analytic requirements Do all the parts work together High voltage requirements, indoor, outdoor differences Schematic level of completeness
Walk through the DesignSame as a physical walk through…Itemize and highlight all the components to ensure installers are set for success.
Compartmentalize & Layer Information
• Naming schema – make sure you define it – Ex F100_2_03AC for <Room Number>_<OutputWire>_<MACAddress>
• Establish list of what is in each room– Define groups in Room. Ex group of lights, group of sensors, group of shades etc– Define groups of groups!– Establish what affects what. Wall switches affect lights, temp request, service request etc– Define Energy code compliance behaviors– Define User preferences (ex wall switch is toggle on/off, press and hold dim or step bright/dim (+/- 20% per
push)• Establish Fidelity of control. Each fixture individually controllable or is it circuit based control• Create fixture schedule that has power requirements of each fixture
– ensure no brown out scenarios• Verify (test) all components work together – do a trial if needed
Room Group
Group
Room
Input
Device
Building
Input
Device
Group
GroupGroup
DESIGN DONT’S• DON’T assume parts work together
– Get trusted personal testimony or test them yourself
• DON’T let the process “flow” drop information– Explicit and clear installation– Tight feedback loop on what
gets installed relative to what was specified
• NEVER underestimate the power of denial
Network MapMust show link from:Fixture Control NodeControl Node Port on SwitchSwitch IP address on Subnet
Why?- Remote diagnostics- Power per port- Detection of Brown outs
Create a project Google SheetInformation portal between design and installation forces
Handoff to commissioning agent with agreed upon information
Add Fixture Schedule Sheet
Lookup to the fixture schedule so that if fixture changes, network design
adapts
FAILURE TO COMMUNICATEPitfall #2
• AHJ’s and code officials– Full submittal before project starts –
approved by local officials and AHJ (ie no surprises later)
• Installers and project managers– Pre-Con meeting to train in detail
how to wire and how to document as you go.
– DAILY stand-up meetings• Owner
– Understand requirements– Manage expectations
Communication - Who and What
THREE HIGH ROI TOOLS FOR INSTALLATION PROCESS
Maximize the number of these< 1% failure rate
Minimize the number of these>40% failure rate
<RoomNumber>_<WireNumber>_<MACAddress>
Daily Standup
Label EVERY fixture (and make sure it stays on)
Finding and climbing ladders takes time & $$
Case Study 1Installer did not pre-authorize equipment being used
AHJ started “failing” things that were not within scope of their initial purview (ex 24V LED exit signs connected to UPS)
Used inferior equipment to get certification and needed 25% more material to get to same load capacity
Case Study 2Installer did not train crew on information tracking
They had to go back to each fixture 2-3 times to get info
Delayed exit by weeks
Ran up against the penalty timeline
Case Study 3No Project Management
No Timeline / project schedule established
Crisis (aka looming $$$ penalty). Send in 20 people on the weekend and pay overtime
“How do we wire this”?-”Not sure, No one told me - I think this way”
“Cool, thanks”….“What do you mean those are NOT the current set of plans????”….“What do you mean we only ordered 93, we need 147!”- “Ok, well let's use a substitute that we can get online here by
tomorrow
Thank You for Your Time
Where Do We Go from Here?Evaluate Your Project Needs to Create a
Fitted SolutionDemonstrate the System Capabilities