OEC Module C – Lighting Controls Implementation

From eLADwiki
Revision as of 11:33, 25 January 2011 by Jgaines (Talk | contribs)

Jump to: navigation, search


Schematic Design Phases

Control Design Intent Narrative
  • Plain language description of how the system is intended to operate, for use by design team and owner to promote dialogue and establish goals of the system.
  • Objectives are discussed by space type and evolve throughout project design phases. Narrative will eventually ensure that all trades, disciplines, users and O&M staff understand the intended operation of the system.
  • eLAD to show examples or templates.
- Expected daylight levels and variation
- Expected operation of blinds or shading devices
- How the controls respond to daylight during normal operation
- How the controls respond to operation of blinds
- How the controls respond to daylight during testing/ calibration
- How the controls respond to daylight during emergency
- What overrides are available to the users and O&M staff
- How the daylighting controls are combined with the other lighting controls
- How the O&M Staff will receive and deal with user demands

Establishing Initial Control Zoning
  • Should tailor project for flexibility and maximum savings
  • eLAD to show options and different approaches

Design Development
  • Approach several manufacturers with Narrative. How would they meet it? Discuss pros and cons of each.

Construction Drawings and Specifications

Overall Objectives
  • Be tight in the specs and drawings so that control objectives are met, a high level of Q&A is ensured before trades leave the building site/ building is occupied, and criteria are provided to qualify equipment and products for an intended purpose.
  • eLAD to include examples of translating a narrative into a product spec, problem sets for typical spaces with control approaches (linking to elements of the Controls Design Module), and compatibility matrix.
- Construction Documents – Zoning to show on electrical drawings. Electrical Engineer provides panel schedules and emergency interface.
- Provide generic performance specifications for individual components. Should address features and capability: e.g. sensitivity of sensors, FOV of sensors, features for adjusting, control algorithm, fade rate, delay, dead band.
- Standards, warranty: e.g. UL, 5 years etc.
- Compatibility at the integrated systems level (e.g., EMCS, HVAC & façade systems)
- Compatibility at level of component of a heterogeneous system related to networking communications protocols, power/ voltage, ballast > controller > sensor interoperability.
- Plug and play systems, proprietary systems, physical connections, wireless, mixed-bag-of-nuts approach.
  • Specs should include requirements to clearly establish the roles and responsibilities of members of the project team during installation.
- Requirement for a “primary” manufacturer or an “integrator” to take responsibility for total function and compatibility
- Include Intent Narrative and require written statement of compliance with specs and narrative
- Submittal Requirements to specify what the contractor will submit for approval at each stage of construction
- Installation Requirements to specify means and methods for installation
- Requirements for labeling of all manual controls, and clear labeling of electrical panels, control panels, and remote ballasts
- Calibration Requirements to specify by whom, when and how the calibration will be done
- Requirements for additional time from manufacturer’s field technician during final calibration and commissioning
- M&V Requirements to specify how system will be verified prior to close of contract and to establish a method of proof for meeting specification, along with ensuring that the M&V systems needed to maintain performance over the life of the building are included in the scope: database, archiving, storage & retrieval.
- Requirements for video taped training session, documentation of final settings, re-commissioning of system
- Training Requirements to specify the level of training for operators (facility managers, building engineer) needed prior to hand-off to properly operate, adjust, and maintain the system over the life of the bldg.


  • Costing & feedback at pre-bid meetings with bid contractors before project is bid on (Formulation of how product/ equipment is delivered)
  • Bid package goes out (informational meetings, RFIs, to wring out uncertainties in the specifications, clarifications)
  • Bid negotiations, approve contractor


  • Pre-construction - review contractor’s plans, schedule, sequence, how trades come through
  • Pre-installation - review contractor submittals for equipment, accept substitutions, approve final locations of sensors
  • Installation - ensure that procedures and requirements outlined in specs are followed by project team
    • Submittal of products for approval per submittal requirements
    • Ask for as-built control zone drawings if different from CDs
    • Installation of equipment per installation requirements
    • Calibration and testing of equipment per calibration requirements
    • Training of personnel per training requirements
    • M&V - verify before final sign-off of contract


  • User / occupant manual: To explain design intent to achieve buy-in. Provide instructions for operating specific equipment.
    • When should this manual be written?
    • What should it contain?
    • Who should write it?
  • Complaint guide: How to respond to occupant complaints that may be due to qualitative issues.
  • Operating and Maintenance Manual (provide electronic copy): Compilation of all information relevant to operation of lighting system
  • All equipment user manuals, trouble-shooting guides, and shop drawings
  • As-built equipment schedules for re-ordering
  • List of Reps and distributors
  • As-built drawings for hidden equipment, such as different ballasts, power packs, etc.
  • Intent Narrative
  • Final commissioning calibration settings and schedule for re-commissioning
  • Recommended cleaning and re-lamping schedules
Personal tools