allow for preprogramming demand response/demand reduction events with at least three degrees of severity. out” the lighting control system must allow any zone to “Opting – out” of a manual or automated demand response event. “opt Manual overrides the following devices or methods may be used to – manually control any zone or combination of zones [include those that are required on a project and delete the others]: Types/methods of manual override: Wallbox switches/dimmers. Preset selector panels (for example, used in a conference room to dim all zones to predetermined levels by pushing a single button for each scene). Touch screens. Smartphone apps. Software-based control. Input from a BMS (for example to turn all luminaires to full on in an emergency situation other than during loss of normal power). for override behavior variables can be set in the system “Logic” – software to control the behavior of manual override devices or methods. [Based on descriptions below, if specific behaviors are required in your project, make sure to describe them here.] Control profiles: Control system software shall allow for creation of that contain “profiles” variables for controlling the behavior of luminaires. Control profiles may be activated automatically by creating blocks of time in the schedule during which a specific profile is in effect. The software shall also allow for creation of a when a specific control profile is active unless a separate “default” – scheduled event is created that overrides the default control profile. These variables include (but are not limited to): Occupancy sensor input whether or not occupancy/vacancy – sensors are used, time delays upon sensing occupancy or vacancy before lights turn on or off (or dim), sensitivity, transition times between states, etc. Daylight harvesting high and low setpoints to create a deadband – for dimming or switching fixtures in response to available daylight,
allow for preprogramming demand response/demand reduction events with at least three degrees of severity. “Opting out” – the lighting control system must allow any zone to “opt out” of a manual or automated demand response event. Manual overrides – the following devices or methods may be used to manually control any zone or combination of zones [include those that are required on a project and delete the others]: Types/methods of manual override: Wallbox switches/dimmers. Preset selector panels (for example, used in a conference room to dim all zones to predetermined levels by pushing a single button for each scene). Touch screens. Smartphone apps. Software-based control. Input from a BMS (for example to turn all luminaires to full on in an emergency situation other than during loss of normal power). “Logic” for override behavior – variables can be set in the system software to control the behavior of manual override devices or methods. [Based on descriptions below, if specific behaviors are required in your project, make sure to describe them here.] Control profiles: Control system software shall allow for creation of “profiles” that contain variables for controlling the behavior of luminaires. Control profiles may be activated automatically by creating blocks of time in the schedule during which a specific profile is in effect. The software shall also allow for creation of a “default” – when a specific control profile is active unless a separate scheduled event is created that overrides the default control profile. These variables include (but are not limited to): Occupancy sensor input – whether or not occupancy/vacancy sensors are used, time delays upon sensing occupancy or vacancy before lights turn on or off (or dim), sensitivity, transition times between states, etc. Daylight harvesting – high and low setpoints to create a deadband for dimming or switching fixtures in response to available daylight,
NYC-Lighting-Controls-Spec-AppB.docx