Intelligent Lighting Networks
1.1. The following specifications detail the minimum performance and related criteria for
the digital lighting control system to be provided by the lighting control manufacturer.
Workstation-specific lighting controls associated with BI-DIRECTIONAL
"workstation-specific" pendant luminaries specifically associated with a single
workstation, comprised of a task-lighting component controllable by the occupant of
that workstation and an ambient lighting component controlled on a space-wide basis.
1.2. System commissioning, training, and trouble-shooting."System Description and
1.2.1. The Lighting Control and Automation System, as defined under this section,
cover the following equipment: digitally addressable ballasts, 0-10v ballasts,
and 3-wire ballasts. The 0-10v or 3-wire ballasts must be used with interfaces
that allow integration with the digital control system and the Building
Automation System (BAS) in accordance with the GSA Intelligent Building
1.2.2. Lighting control programming, operating, and monitoring software packages
shall communicate initially with the BAS, or have the ability to communicate in
the future with a BAS using protocols in accordance with the GSA Smart
Building Technology Standard. The lighting network shall enable the intelligent
networking of all lamps and lighting control components using a single,
globally recognized, open standards communications protocol.
1.2.3. The lighting network technology must be able to allow the commissioning,
control and management of any lamp used internally, externally and for safety
from the iBMS web based convergent platform.
1.2.4. The lighting network must allow for the widest choice of lamp type and
manufacturer to be used.
1.2.5. The offered lighting network solution must possess all or as many of the
following features as possible:
126.96.36.199. All lighting fixtures and equipment shall be intelligent “Digital
Addressable Lighting Interface”. DALI is the US recognized NEMA
243 or European DALI-AG. This is the international standard that
guarantees the exchangeability of dimmable ballasts from different
Intelligent Lighting Control Monday, 29 June 2009 Page 1 of 18
manufacturers. This gives planners, luminary manufacturers, building
owners, installers and end-users the security of supply from many
sources. The DALI-interface has been described in the fluorescent
lamp ballast standard IEC 60929 under Annex E.
2. DALI AND Niagara AX™
2.1. The DALI control system shall be native to the standard Niagara AX™ software
platform that supports all of the protocols listed under the Network Area Controller
(NAC), either self-contained or resident in the BAS, such as the eLighting™
connectivity and driver for standard Niagara AX™ platform devices.
2.2. The controls platform shall in no way be deployed using a proprietary piece of software
or gear that cannot be purchased from multiple DALI sources. Support shall be directly
to DALI from other protocols without the use of gateways where the objects can share
information between building systems.
2.2.1. Simple wiring of control lines (no group formation, no polarity).
2.2.2. Control of individual units (individual addressing) or groups (group addressing)
2.2.3. A simultaneous control of all units is possible at any time (built-in initial
operation function) through broadcast addressing.
2.2.4. No interference of data communication is to be expected due to the simple data
2.2.5. Control device status messages (lamp fault), (report options: all / by group / by
2.2.6. Automatic search of control devices and simple formation of groups through
2.2.7. Automatic and simultaneous dimming of all units when selecting a scene.
2.2.8. Logarithmic dimming behavior – matching the eye’s sensitivity.
2.2.9. System with assigned intelligence (every unit contains, amongst other things,
the following data: individual address, group assignment, lighting scene values,
188.8.131.52. Operational tolerances of lamps can be stored as default.
184.108.40.206. Values (i.e. maximum values can be set for the purpose of energy
Intelligent Lighting Control Monday, 29 June 2009 Page 2 of 18
220.127.116.11. Fading: adjustment of dimming speed.
18.104.22.168. Identification of unit type.
22.214.171.124. Options for emergency lighting can be chosen (selection of specific
ballasts, dimming level).
126.96.36.199. No need to switch on/off the external relay for the mains voltage (this
is done by internal electronic components).
188.8.131.52. Lower system cost and more functions compared to 1–10V systems.
2.3. DALI has been defined for:
2.3.1. A maximum of 64 single units (individual addresses).
2.3.2. A maximum of 16 groups (group addresses).
2.3.3. A maximum of 16 scenes (scene light values).
2.4. The intelligence of the system has not been centralized for the purpose of defining the
DALI-interface for control devices.
2.5. This means that many of the set points and lighting values are stored within the
2.5.1. Individual addresses
2.5.2. Group assignments
2.5.3. Light scene values
2.5.4. Fading times
2.5.5. Emergency lighting level (System Failure Level)
2.5.6. Power On Level
2.5.7. DALI closes the gap between conventional 1–10V interfaces and complex
lighting control systems. These are the features that make DALI stand out as the
ideal platform for an intelligent and flexible lighting management in modern
3. INTELLIGENT LIGHTING COMMISSIONING, CONTROLS AND MANAGEMENT
Intelligent Lighting Control Monday, 29 June 2009 Page 3 of 18
3.1. All commissioning, control and management of the intelligent lighting and control
devices shall be via a single web based software tool that seamlessly integrates onto the
web based iBMS convergent technology platform.
3.2. Such a solution must:
3.2.1. Be based upon Open and De Facto standards, seamlessly and directly allowing
the open standards lighting network to be integrated onto the web based iBMS
convergent technology platform. Be able to be operated by existing trained staff
familiar with the web based iBMS convergent technology platform. Provide
direct and seamless connectivity to the above lighting system standard into the
chosen web based iBMS convergent technology platform via the web based
iBMS convergent platforms RS485 serial port.
3.2.2. Provide a minimum DALI lighting channel of 64 devices per channel on a
single RS232 serial port.
3.2.3. Allow lighting channels to be distributed across multiple web based iBMS
3.2.4. Be able to interface to any intelligent DALI ballast via the lighting network
global open standards protocol.
3.2.5. Shall as a minimum provide:
184.108.40.206. A single web based commissioning, control and management
environment for the lighting networks.
220.127.116.11. Remote connectivity for the purpose of support, maintenance,
monitoring and management via the web based iBMS convergent
18.104.22.168. The following lighting control functions:
22.214.171.124.1. Constant Light control/ Daylight management
126.96.36.199.2. Automatic presence and or absence
188.8.131.52.3. Meeting room function
184.108.40.206.4. Corridor hold
220.127.116.11.5. Switch and switch dimming
18.104.22.168.6. Manual override
Intelligent Lighting Control Monday, 29 June 2009 Page 4 of 18
22.214.171.124.7. Enable and disable
126.96.36.199.8. Be capable of support worldwide
188.8.131.52.9. Be capable of support by non lighting controls specialists
4. LIGHTING CONTROL AND MONITORING SYSTEM (LCMS)
4.1. Healthy / Faulty status of NAC / Software
4.2. Healthy / Faulty status of the LCMS components
4.3. ON / OFF / AUTO commands
4.4. LCMS alarms
5. SYSTEM REQUIREMENTS
5.1. The EIS shall provide the interface between the LAN or WAN and the HVAC and
other ELVs systems, and provide global supervisory control functions over the control
devices connected to the systems. It shall be capable of executing application control
programs to provide:
5.1.3. Alarm monitoring and routing
5.1.4. Time synchronization
5.1.5. Integration of Lon Works, DALI, BACnet and Modbus controller and standard
5.1.6. Network management functions for all Lon Works and DALI based devices
5.2. The EIS shall support standard web browser access via the Intranet/Internet. It shall
support a minimum of 32 simultaneous users.
6. HVAC CONTROLLERS
6.1. Healthy / Faulty Status of the HVAC components
6.2. Temperature, humidity, pressure, On / Off status
6.3. ON / OFF / AUTO commands
Intelligent Lighting Control Monday, 29 June 2009 Page 5 of 18
6.4. Set temperature
6.5. Other standard commands, statuses and alarms
7. OPEN, INTEROPERABLE, INTEGRATED ARCHITECTURES
7.1. The EIS software shall employ object-oriented technology (OOT) for representation of
all data and control devices within the system.
7.2. In addition, adherence to industry standards including ANSI /ASHRAE™ Standard
135-2001, BACnet and LonMark to assure interoperability between all system
components is required.
7.3. For each LonWorks device that does not have LonMark certification, the device
supplier must provide an XIF file and a resource file for the device.
7.4. For each BACnet device, the device supplier must provide a PICS document showing
the installed device’s compliance level.
7.5. Minimum compliance is level 3; with the ability to support data read and write
functionality. Physical connection of BACnet devices shall be via Ethernet (BACnet
Ethernet/IP,) and/or RS-485 (BACnet MSTP) as specified.
8. NETWORK AREA CONTROLLER (NAC)
8.1. NETWORK AREA CONTROLLER (NAC)
8.1.1. The EIS contractor shall supply one or more Network Area Controllers (NAC)
as part of this contract.
8.1.2. Number of area controllers required is dependent on the type and quantity of
devices specified in the ELV sub systems. It is the responsibility of the EIS
contractor to coordinate with the consultant/contractor to determine the quantity
and type of devices.
8.1.3. The Network Area Controller (NAC) shall provide the interface between the
LAN or WAN and the field control devices, and provide global supervisory
control functions over the control devices connected to the NAC. It shall be
capable of executing application control programs to provide:
184.108.40.206. Alarm monitoring and routing
Intelligent Lighting Control Monday, 29 June 2009 Page 6 of 18
220.127.116.11. Time synchronization
18.104.22.168. Integration of LonWorks, BACnet, DALI and Modbus controller data.
8.2. Network management functions for all LonWorks and BACnet based devices. The
NAC must provide the following hardware features as a minimum:
8.2.1. The embedded server shall run on the QNX RTOS platform. It shall support
multiple independent applications such as building automation and access
control on the same platform.
8.2.2. The server shall support multiple protocols, such as but not limited to,
LonWorks, DALI, BACnet (IP & MSTP), Modbus (TCP & RTU), EIB, SNMP
and web services (XML/Soap). Wired Ethernet as well as edge cellular
networks shall be fully supported.
8.3.1. QNX operating system with a 440Epx PowerPC processor @667 MHz.
8.3.2. Supports a remote 10” (800 x 600) touch screen display (RD-700-10) utilizing a
max. 10’single interface cable (power for the display provided through the
8.3.3. Supports external keyboard/mouse (USB) when using optional display
8.3.4. Din rail mounted or direct panel mount.
8.3.5. Standard memory is 512MB fields upgradeable to 1 GB
8.3.6. Standard 1GB on board flash for data storage
8.3.7. One on board RS-232 port and one RS-485/power port- 2 option slots available
8.3.8. 15VDC power input from din rail mounted power supply.
8.3.9. On board battery backup.
8.3.10. Built in recharging and monitoring support for an external 12V sealed lead-acid
8.3.11. Supports BACnet, TCP/IP, MSTP, LON, DALI, Modbus TCP, Modbus RTU,
EIB, ObixUL-916, CE, CSA rated0-50 degrees C, 0-90% RH non condensing
Intelligent Lighting Control Monday, 29 June 2009 Page 7 of 18
8.4. The NAC shall support standard web browser access via the Intranet/Internet. It shall
support a minimum of 32 simultaneous users.
8.5. Event alarm notification and actions
8.5.1. The NAC shall provide alarm recognition, routing, management, and analysis to
supplement distributed capabilities of equipment or application specific
8.5.2. The NAC shall be able to route any alarm condition to any defined user location
whether connected to a local network or remote via dial-up telephone
connection, or wide-area network.
8.5.3. Alarm generation shall be selectable for annunciation type and
acknowledgement requirements including but limited to:
22.214.171.124. To alarm
126.96.36.199. Return to normal
188.8.131.52. To fault
8.6. Provide for the creation of a minimum of fifteen alarm classes for the purpose of
routing types and or classes of alarms, i.e.: security, HVAC, Fire, etc.
8.7. Provide timed (schedule) routing of alarms by class, object, group, or node.
8.8. Provide alarm generation from binary object “runtime” and/or event counts for
equipment maintenance. The user shall be able to reset runtime or event count values
with appropriate password control.
8.9. Control equipment and network failures shall be treated as alarms and annunciated.
8.10. Alarms shall be annunciated in any of the following manners as defined by the user:
8.10.1. Screen message text.
8.10.2. Email of the complete alarm message to multiple recipients. Provide the ability
to route and email.
8.11. Alarms based on:
8.11.1. Day of week
8.11.2. Time of day
Intelligent Lighting Control Monday, 29 June 2009 Page 8 of 18
8.11.4. Graphic with flashing alarm object(s)
8.11.5. Printed message, routed directly to a dedicated alarm printer NAC
8.12. The following shall be recorded by the NAC for each alarm (at a minimum):
8.12.1. Time and date
8.12.2. Location (building, floor, zone, office number, etc.)
8.12.3. Equipment (air handler #, access way, etc.)
8.12.4. Acknowledge time, date, and user who issued acknowledgement.
8.12.5. Alarm actions may be initiated by user defined programmable objects created
for that purpose.
8.12.6. Defined users shall be given proper access to acknowledge any alarm, or
specific types or classes of alarms defined by the user.
8.12.7. An error log to record invalid property changes or commands shall be provided
and available for review by the user.
9. DATA COLLECTION AND STORAGE
9.1. The NAC shall have the ability to collect data for any property of any object and store
this data for future use.
9.2. The data collection shall be performed by log objects, resident in the NAC that shall
have, at a minimum, the following configurable properties:
9.2.1. Designating the log as interval or deviation.
9.2.2. For interval logs, the object shall be configured for time of day, day of week and
the sample collection interval.
9.2.3. For deviation logs, the object shall be configured for the deviation of a variable
to a fixed value.
9.2.4. This value, when reached, will initiate logging of the object.
9.2.5. For all logs, provide the ability to set the maximum number of data stores for
the log and to set whether the log will stop collecting when full, or rollover the
data on a first-in, first-out basis.
Intelligent Lighting Control Monday, 29 June 2009 Page 9 of 18
9.2.6. Each log shall have the ability to have its data cleared on a time-based event or
by a user-defined event or action.
9.2.7. All log data shall be stored in a relational database in the NAC and the data
shall be accessed from a server (if the system is so configured) or a standard
9.3. All log data shall be available to the user in the following data formats:
9.3.3. Plain Text
9.3.4. Comma or tab separated values
9.4. Systems that do not provide log data in HTML and XML formats at a minimum shall
not be acceptable.
9.5. The NAC shall have the ability to archive its log data either locally (to itself), or
remotely to a server or other NAC on the network. Provide the ability to configure the
following archiving properties, at a minimum:
9.5.1. Archive on time of day.
9.5.2. Archive on user-defined number of data stores in the log (buffer size).
9.5.3. Archive when log has reached its user-defined capacity of data stores.
9.5.4. Provide ability to clear logs once archived.
9.6. AUDIT LOG
9.6.1. Provide and maintain an audit log that tracks all activities performed on the
NAC. Provide the ability to specify a buffer size for the log and the ability to
archive log based on time or when the log has reached its user-defined buffer
size. Provide the ability to archive the log locally (to the NAC), to another NAC
on the network, or to a server.
9.6.2. For each log entry, provide the following data:
184.108.40.206. Time and date
220.127.116.11. User ID
Intelligent Lighting Control Monday, 29 June 2009 Page 10 of 18
18.104.22.168. Change or activity: i.e., change set point, add or delete objects,
22.214.171.124. Multiprotocol Support
126.96.36.199. Database backup and storage
9.7. The NAC shall have the ability to automatically backup its database to the BMS server.
The database shall be backed up based on a user-defined time interval.
9.8. Copies of the current database and, at the most recently saved database shall be stored
in the NAC. The age of the most recently saved database is dependent on the user-
defined database save interval.
9.9. The NAC database shall be stored, at a minimum, in XML format to allow for user
viewing and editing, if desired. Other formats are acceptable as well, as long as XML
format is supported.
9.10. NAC – Interface Software
9.10.1. The GUI shall employ browser-like functionality for ease of navigation. It shall
include a tree view (similar to Windows Explorer) for quick viewing of, and
access to, the hierarchical structure of the database. In addition, menu-pull
downs, and toolbars shall employ buttons, commands and navigation to permit
the operator to perform tasks with a minimum knowledge of the HVAC control
system and basic computing skills. These shall include, but are not limited to,
forward/backward buttons, home button, and a context sensitive locator line
(similar to a URL line), that displays the location and the selected object
9.10.2. Real-time displays. The GUI, shall at a minimum, support the following
graphical features and functions:
9.10.3. Graphic screens shall be developed using any drawing package capable of
generating a GIF, BMP, PNG or JPG file format. Use of proprietary graphic file
formats shall not be acceptable. In addition to, or in lieu of a graphic
background, the GUI shall support the use of scanned pictures.
9.10.4. Graphic screens shall have the capability to contain objects for text, real-time
values, animation, color spectrum objects, logs, graphs, HTML or XML
document links, schedule objects, hyperlinks to other URL’s, and links to other
9.10.5. Graphics shall support layering and each graphic object shall be configurable
for assignment to a layer. A minimum of six layers shall be supported.
Intelligent Lighting Control Monday, 29 June 2009 Page 11 of 18
9.10.6. Modifying common application objects, such as schedules, calendars, and set
points shall be accomplished in a graphical manner.
9.10.7. Schedule times will be adjusted using a graphical slider, without requiring any
keyboard entry from the operator.
9.10.8. Holidays shall be set by using a graphical calendar without requiring any
keyboard entry from the operator.
9.11. Commands to start and stop binary objects shall be done by right-clicking the selected
object and selecting the appropriate command from the pop-up menu or on single click
on the selected object. No entry of text shall be required.
9.12. Adjustments to analog objects, such as set points, shall be done by right-clicking the
selected object and using a graphical slider to adjust the value or on single click on
selected up and down objects. No entry of text shall be required.
9.13. System configuration. At a minimum, the GUI shall permit the operator to perform the
following tasks, with proper password access:
9.13.1. Create, delete or modify control strategies.
9.13.2. Add/delete objects to the system.
9.13.3. Tune control loops through the adjustment of control loop parameters.
9.13.4. Enable or disable control strategies
9.13.5. Generate hard copy records or control strategies on a printer.
9.13.6. Select points to be alarm able and define the alarm state.
9.13.7. Select points to be trended over a period of time and initiate the recording of
9.13.8. Online help. Provide a context sensitive, on-line help system to assist the
operator in operation and editing of the system. On-line help shall be available
for all applications and shall provide the relevant data for that particular screen.
Additional help information shall be available through the use of hypertext. All
system documentation and help files shall be in HTML format.
9.14. Security. Each operator shall be required to log on to that system with a user name and
password in order to view, edit, add, or delete data. System security shall be selectable
for each operator. The system administrator shall have the ability to set passwords and
security levels for all other operators.
Intelligent Lighting Control Monday, 29 June 2009 Page 12 of 18
9.15. Each operator password shall be able to restrict the operators’ access for viewing and/or
changing each system application, full screen editor, and object. Each operator shall
automatically be logged off of the system if no keyboard or mouse activity is detected.
This auto log-off time shall be set per operator password. All system security data shall
be stored in an encrypted format.
9.16. System diagnostics. The system shall automatically monitor the operation of all
workstations, printers, modems, network connections, building management panels,
and controllers. The failure of any device shall be annunciated to the operator.
9.17. Alarm console
9.17.1. The system will be provided with a dedicated alarm window or console. This
window will notify the operator of an alarm condition, and allow the operator to
view details of the alarm and acknowledge the alarm. The use of the alarm
console can be enabled or disabled by the system administrator.
9.17.2. When the alarm console is enabled, a separate alarm notification window will
supercede all other windows on the desktop and shall not be capable of being
minimized or closed by the operator.
9.17.3. This window will notify the operator of new alarms and un-acknowledged
alarms. Alarm notification windows or banners that can be minimized or closed
by the operator shall not be acceptable.
9.17.4. The Alarm console should have the provision of accessing relevant information
and graphical user interfaces with the use of hyperlinks.
10. WEB BROWSER CLIENTS
10.1. The system shall be capable of supporting an unlimited number of clients using a
standard Web browser such as Internet Explorer™, Netscape Navigator™ or Firefox.
Systems requiring additional software (to enable a standard web browser) to be resident
on the client machine, or manufacture-specific browsers shall not be acceptable.
10.2. The web browser software shall run on any operating system and system configuration
that is supported by the web browser. Systems that require specific machine
requirements in terms of processor speed, memory, etc., in order to allow the web
browser to function with the BMS, shall not be acceptable.
10.3. The web browser shall provide the same view of the system, in terms of graphics,
schedules, calendars, logs, etc., and provide the same interface methodology as is
provided by the Graphical User Interface.
Intelligent Lighting Control Monday, 29 June 2009 Page 13 of 18
10.4. Systems that require different views or that require different means of interacting with
objects such as schedules, or logs, shall not be permitted.
10.5. The web browser client shall support at a minimum, the following functions:
10.5.1. User log-on identification and password shall be required. If an unauthorized
user attempts access, a blank web page shall be displayed. Security using Java
authentication and encryption techniques to prevent unauthorized access shall
10.5.2. Graphical screens developed for the GUI shall be the same screens used for the
web browser client. Any animated graphical objects supported by the GUI shall
be supported by the web browser interface.
10.5.3. HTML programming shall not be required to display system graphics or data on
a Web page.
10.5.4. HTML editing of the web page shall be allowed if the user desires a specific
look or format.
10.5.5. Storage of the graphical screens shall be in the Network Area Controller (NAC)
or on the BMS operator workstation, without requiring any graphics to be stored
on the client machine. Systems that require graphics storage on each client are
10.5.6. Real-time values displayed on a web page shall update automatically without
requiring a manual “refresh” of the web page.
10.5.7. Users shall have administrator-defined access privileges. Depending on the
access privileges assigned, the user shall be able to perform the following:
10.5.7.1. Modify common application objects, such as schedules, calendars, and
set points in a graphical manner. Schedule times will be adjusted using
a graphical slider, without requiring any keyboard entry from the
operator. Holidays shall be set by using a graphical calendar, without
requiring any keyboard entry from the operator.
10.5.7.2. Commands to start and stop binary objects shall be done by right-
clicking the selected object and selecting the appropriate command
from the pop-up menu or on single click on the selected object. No
entry of text shall be required.
10.5.7.3. View logs and charts
10.5.7.4. View and acknowledge alarms
Intelligent Lighting Control Monday, 29 June 2009 Page 14 of 18
10.5.7.5. Setup and execute SQL queries on log and archive information
10.5.8 The system shall provide the capability to specify a user’s (as determined by the
log-on useridentification) home page. Provide the ability to limit a specific user
to just their defined homepage. From the home page, links to other views, or
pages in the system shall be possible, ifallowed by the system administrator.
10.5.9 Graphic screens on the web Browser client shall support hypertext links to other
locations on the Internet or on Intranet sites, by specifying the Uniform
Resource Locator (URL) for the desired link.
11. SYSTEM PROGRAMMING
11.1 The Graphical User Interface software (GUI) shall provide the ability to perform
system programming and graphic display engineering as part of a complete software
package. Access to the programming functions and features of the GUI shall be through
password access as assigned by the system administrator. Text based programming is
11.2 A library of control, application, and graphic objects shall be provided to enable the
creation of all applications and user interface screens. Applications are to be created by
selecting the desired control objects from the library, dragging or pasting them on the
screen, and linking them together using a built in graphical connection tool. Completed
applications may be stored in the library for future use. Graphical User Interface
screens shall be created in the same fashion. Data for the user displays is obtained by
graphically linking the user display objects to the application objects to provide “real-
time” data updates. Any real-time data value or object property may be connected to
display its current value on a user display. Systems requiring separate software tools or
processes to create applications and user interface displays shall not be acceptable.
11.3 Programming Methods
11.3.1 Provide the capability to copy objects from the supplied libraries, or from a
user-defined library to the user’s application. Objects shall be linked by a
graphical linking scheme by dragging a link from one object to another. Object
links will support one-to-one, many-to-one, or one-to-many relationships.
Linked objects shall maintain their connections to other objects regardless of
where they are positioned on the page and shall show link identification for
links to objects on other pages for easy identification. Links will vary in color
depending on the type of link; i.e., internal, external, hardware, etc.
11.3.2 Configuration of each object will be done through the object’s property sheet
using fill-in the blank fields, list boxes, and selection buttons. Use of custom
programming, scripting language, or a manufacturer-specific procedural
language for configuration will not be accepted.
Intelligent Lighting Control Monday, 29 June 2009 Page 15 of 18
11.3.3 The software shall provide the ability to view the logic in a monitor mode.
When online, the monitor mode shall provide the ability to view the logic in real
time for easy diagnosis of the logic execution. When off-line (debug), the
monitor mode shall allow the user to set values to inputs and monitor the logic
for diagnosing execution before it is applied to the system. Network Area
Controller – Specification Page 7. Network Area Controller – Specification
11.3.4 All programming shall be done in real-time. Systems requiring the uploading,
editing and downloading of database objects shall not be allowed.
11.3.5 The system shall support object duplication within a customer’s database. An
application, once configured, can be copied and pasted for easy re-use and
duplication. All links, other than to the hardware, shall be maintained during
12. LonWorks NETWORK MANAGEMENT
12.1. The Graphical User Interface software (GUI) shall provide a complete set of integrated
LonWorks network management tools for working with LonWorks networks. These
tools shall manage a database for all LonWorks devices by type and revision, and shall
provide a software mechanism for identifying each device on the network. These tools
shall also be capable of defining network data connections between LonWorks devices,
known as “binding”. Systems requiring the use of third party LonWorks network
management tools shall not be accepted.
12.2. Network management shall include the following services: device identification, device
installation, device configuration, device diagnostics, device maintenance and network
12.3. The network configuration tool shall also provide diagnostics to identify devices on the
network, to reset devices, and to view health and status counters within devices.
12.4. These tools shall provide the ability to “learn” an existing LonWorks network,
regardless of what network management tool(s) were used to install the existing
network, so that existing LonWorks devices and newly added devices are part of a
single network management database.
12.5. The network management database shall be resident in the Network Area Controller
(NAC), ensuring that anyone with proper authorization has access to the network
management database at all times. Systems employing network management databases
that are not resident, at all times, within the control system, shall not be accepted.
13. DALI NETWORK MANAGEMENT
Intelligent Lighting Control Monday, 29 June 2009 Page 16 of 18
13.1. The Graphical User Interface software (GUI) shall provide a complete set of integrated
DALI network management tools for working with DALI networks. These tools shall
manage a database for all DALI devices by type and revision, and shall provide a
software mechanism for identifying each device on the network. These tools shall also
be capable of addressing and grouping DALI. Systems requiring the use of third party
DALI network management tools shall not be accepted.
13.2. Network management shall include the following services: device addressing, device
identification, device installation, device configuration, device diagnostics and device
13.3. The network configuration tool shall also provide diagnostics to identify devices on the
network, to reset devices, and to view health and status of devices.
13.4. These tools shall provide the ability to “discover” an existing DALI network, regardless
of what network management tool(s) were used to install the existing network, so that
existing DALI devices and newly added devices are part of a single network
management database. Network Area Controller – Specification Page 9
13.5. The network management database shall be resident in the Network Area Controller
(NAC), ensuring that anyone with proper authorization has access to the network
management database at all times. Systems employing network management databases
that are not resident, at all times, within the control system, shall not be accepted.
14. OBJECT LIBRARIES
14.1. A standard library of objects shall be included for development and setup of application
logic, user interface displays, system services, and communication networks.
14.2. The objects in this library shall be capable of being copied and pasted into the user’s
database and shall be organized according to their function. In addition, the user shall
have the capability to group objects created in their application and store the new
instances of these objects in a user-defined library.
14.3. In addition to the standard libraries specified here, the supplier of the system shall
maintain an on-line accessible (over the Internet) library, available to all registered
users to provide new or updated objects and applications as they are developed.
14.4. All control objects shall conform to the control objects specified in the BACnet
14.5. The library shall include applications or objects for the following functions, at a
14.5.1. Scheduling object. The schedule must conform to the schedule object as defined
in the BACnet specification, providing 7-day plus holiday & temporary
Intelligent Lighting Control Monday, 29 June 2009 Page 17 of 18
scheduling features and a minimum of 10 on/off events per day. Data entry to be
by graphical sliders to speed creation and selection of on-off events.
14.5.2. Calendar Object. . The calendar must conform to the calendar object as defined
in the BACnet specification, providing 12-month calendar features to allow for
holiday or special event data entry. Data entry to be by graphical “point-and-
click” selection. This object must be “linkable” to any or all scheduling objects
for effective event control.
Intelligent Lighting Control Monday, 29 June 2009 Page 18 of 18