UK quantum spec - lights only.doc - Dimmers And Lighting ...



Networked Lighting Control System Specification

The #Project Name# shall have a lighting control and energy management system that provides total light management by combining where required, lighting controls, automated window shades, digital ballasts and LED drivers, and sensors together under one software, service and support umbrella.

The control system must be processor-based and can be connected to the building network or a dedicated network for the control system. Only a single point of connection is needed on the control system network for total communication to the entire system. The customer should be able to extract the programming database from the system if and when required.

With the appropriate security credentials, the control system should be capable of being managed from anywhere and from any device using a HTML5 compatible browser (including Internet Explorer, Chrome, and Safari) connected to the building’s secure network.

The control system should provide actionable data from lights, shades and sensors via an easy to understand web-based application to enable the #Project Name# to maximize occupant comfort, save energy, improve operational efficiency and maximize space utilization.

The automated window shading system must be integrated with the lighting control and energy management system without the need for additional interfaces. The lighting plus shading system must optimize the penetration of direct sunlight, maximize view, provide diffused daylight and optimize electric light energy use.

The control system should support addressable DALI-2 for light fixtures and BACnet/IP for Building Management System (BMS) integration without the need for additional gateways.

Wireless switches shall be compatible with metal plates without degradation of RF performance and the switches shall be provided with customized engraving

The control system should not be reliant on an internet connection or cloud services, and performance should not be degraded when offline.

Lighting Control System Functions and Features

1. Presence Detectors

a. Smart passive infrared with adaptive threshold technology that detects fine-motion without the need to change the sensor's sensitivity threshold.

b. Programmable to operate as an occupancy sensor or a vacancy sensor (manual-on and automatic-off).

c. Area occupancy settings including level that lights turn on to when area is occupied, and level that lights turn off to when area is unoccupied can be changed in real-time from a web based facility management software.

d. Occupancy sensors should be capable of controlling any area under the lighting control system irrespective of where the sensor is physically located.

e. BACnet integrator can Enable/Disable occupancy sensors, add occupancy sensor time out without using additional interfaces.

f. BACnet integrator can monitor area occupancy status and energy savings due to Occupancy sensors without using additional interfaces.

2. Daylight sensors

a. Automatically dim lights based on photocell measurement.

b. Partially shielded for accurate detection of available daylight to prevent fixture lighting and horizontal light component from skewing sensor detection.

c. Provide linear response from 20 to 1600 lux.

d. Facility management software can be used to Enable/disable daylight sensors, tune gain levels and monitor history of daylight sensor operation for quick and easy troubleshooting.

e. BACnet integrator can Enable/Disable daylight sensors and set daylight levels without using additional interfaces.

f. BACnet integrator can monitor daylight levels without using additional interfaces.

3. Wireless communication for sensors and remotes

a. Minimize interference, ensure reliability and indoor performance by operating in a wireless spectrum with limited in-band interference.

b. Bands allowing continuous transmissions (e.g. 2.4 GHz, 900 MHz) should not be used for system critical functions.

c. Wireless messages should be transmitted via a fixed network (point to point) to ensure quick system reaction (less than 300ms latency) and easy troubleshooting (if necessary). The system should not create a Mesh network.

d. Wireless sensors and remotes have a minimum of 10 year battery life by design.

e. Lighting system identifies end of life for sensors and provides notification via software.

4. Load controllers

a. Should be capable of controlling DALI-2, EcoSystem, Leading and Trailing edge phase dimming, 0-10V, DMX and switched fixtures

b. DALI-2 load controllers should be certified by the Digital Illumination Interface Alliance (DiiA) and be listed on DiiA’s online database.

c. Phase dimming controllers should be capable of automatically select forward or reverse phase dimming based on the light source.

d. Phase dimming controllers should be capable of having a zero watt minimum load

e. Load controllers seamlessly integrate with motorized window shades, control stations, sensors and the building lighting system without additional interfaces.

f. White Tuning should be done using two digital inputs, one for colour temperature and one for intensity

i. Change colour temperature dynamically while maintaining the intensity

ii. Local user control

iii. Timeclock events

iv. Daylight linking

5. Lighting management software

a. System software license and hardware must be designed, tested, manufactured, and warranted by a single manufacturer.

b. Software for system programming, control and monitoring must have a graphical floor plan view based on customized CAD based drawing of the building for easy navigation.

c. Programming software should allow customized conditional programming and timeclocks.

d. Control and monitoring can be done on an individual fixture or zone level.

6. Tools for facility management

a. User interface should provide an intuitive dashboard to quickly allow access to the different functions of the system, from a campus view all the way down to a single fixture

i. Access to alarms and alerts

ii. Energy usage

iii. Floor plan interface

iv. Schedules, including emergency testing and monitoring

v. Space utilization

b. Space utilization monitoring

i. System provides information on when and for how long spaces are occupied for one or more areas over a period of time.

ii. Data is presented in a simple, accessible format using graphs and bar charts.

iii. Space utilization data can be monitored/accessed via BACnet.

iv. Create customized reports.

v. Export space utilization data in CSV format.

vi. Space utilization data can be monitored/accessed via BACnet.

c. Energy reporting:-

i. Software calculates energy used by individual lights.

ii. Software shows a comparison of energy used over a period of time for one or more areas.

iii. Show energy usage in W/sq.m

iv. Show energy savings for any area broken down by strategy (tuning, occupancy sensing, timeclock etc.)

v. Create customized reports.

vi. Export energy usage data in CSV format.

vii. Power data can be monitored/accessed via BACnet.

d. System health monitoring

i. Activity Report: Show what activity has taken place over a period of time for one or more areas. Activity includes occupant activities (e.g. wall controls being pressed), building manager operation (e.g. controlling/changing areas using the control and monitor tool), and device failures (e.g. keypads or ballasts that are not responding).

ii. Lamp Failure Report: Shows which areas are currently reporting lamp failures.

iii. Shade Level Report: Shows the shade level for any shade group in the system over any historical 24 hour period.

iv. Sensor Level Report: Shows the light level in footcandles of any photosensor in the system.

v. Alert Activity Report: Capable of generating historical reports of all alert activity within the system.

vi. Wireless sensor battery status reporting

vii. Automatically generates alerts in the software and via email for:

1. Failed equipment (drivers, control gear, sensors etc.)

2. Lamp outage using advanced digital dimming ballasts

3. Low battery conditions in battery-operated sensors and controls; alert cleared when battery is replaced.

4. Luminaires with lamp operating hours in excess of designated time.

5. A load shed event; alert generated for beginning and end of trigger.

6. Energy usage higher than designated threshold target.

7. Potential light level condition discrepancies (daylight sensors not agreeing with expected lighting status).

8. Potential sensor failures (Radio Window sensors that have not seen a change in light level).

viii. Configure and monitor tests for self-contained DALI emergency units.

e. Automated Emergency Lighting Testing and Monitoring

i. System is capable of scheduling emergency lighting testing by area to minimize disruption

ii. The system allows the user to schedule and perform Functional Tests and Duration Tests for all DALI Emergency devices that are part of the system.

1. Functional Tests to occur Weekly, Bi-Weekly or Monthly, or triggered manually at any time.

iii. Scheduling can be managed on a calendar view, where all events can be seen as to avoid any potential disruptions.

iv. Emergency devices can be grouped and tested independently.

v. The system will report the following information regarding the DALI Emergency devices:

1. Date of last Function Test for each Emergency Group.

2. Date of last Duration Test for each Emergency Group.

3. If Duration Test or Function Test is past due for each Emergency Group

4. If any problem was identified during a Function Test or Duration Test for each DALI Emergency device.

f. Access to areas and features can be restricted based on login credentials.

g. Allows mobile control and programming of the light and shading system via native applications for Apple iPad and Windows 10 tablets/PCs.

7. Control stations

a. All stations should be capable of light and shade control.

b. Wireless remotes for zone and scene control - capable of operating in a wireless spectrum where continuous transmission is not permitted.

c. Faceplates should have concealed mounting hardware.

d. Multi-scene wired controls must utilize RS485 wiring for low-voltage communication

e. Buttons to depress and provide tactile feedback of a successful button push. Controls utilizing capacitive or resistive touch technology are not acceptable.

f. Buttons are backlit for easy identification.

8. The lighting control system must be BACnet Testing Laboratories (BTL) listed.

9. Startup and services:

a. Manufacturer’s representative should perform a prewire Visit to coordinate site conditions, sequence of operations, project timelines, sensors and drawings.

b. Manufacturer should offer System & Network Integration consultation or similar to coordinate sequence of operations between building systems.

c. Manufacturer takes responsibility for sensor layout and fine-tuning calibration before and after project turnover via optional service plans.

d. Manufacturer must deliver commissioning support services for energy standards and codes, including system verification documentation for LEED and onsite system verification testing and demonstration.

e. Manufacturer must deliver System Diagnostic Services onsite and remotely.

f. Manufacturer must offer 10 year service contracts with 24-hour guaranteed response time and yearly scheduled preventive maintenance visits.

g. Manufacturer should offer an 8 year limited warranty for all products.

................
................

In order to avoid copyright disputes, this page is only a partial summary.

Google Online Preview   Download