AIA/CES Provider Number: 50111167

COURSE EE115: INTEGRATION AND BUILDING AUTOMATION

Course Number: 115

AUTHOR: C. WEBSTER MARSH, HLB LIGHTING DESIGN

 

 

EDUCATION CREDIT

At the end of this course, participants will be able to complete an online exam, with a passing grade of 70+% to qualify for CEU and LEU (NCQLP)

credit and 80+% for LU/HSW hours (AIA/CES). Upon a passing grade, you will be able to download a Certificate of Completion for each type of

credits. For LC certification maintenance (LEUs), credits are self-reported. For AIA /CES, the Lighting Controls Association will report credit earned

for this course to AIA CES.

NO ENDORSEMENT BY ACCREDITING ORGANIZATIONS

This course is registered with AIA CES for continuing professional education. As such, it does not include content that may be deemed or construed

to be an approval or endorsement by this organization of any material of construction or any method or manner of handling, using, distributing, or

dealing in any material or product.

 

COPYRIGHT

This presentation is protected by US and International copyright laws.  Reproduction, distribution, display and use of the presentation without written

permission of the Lighting Controls Association is prohibited.

DISCLAIMER

The information contained in this course has been obtained from sources believed to be reliable. Damages arising from errors, omissions or damages

as a result of the use or misuse of the data or information contained in this course are not the responsibility of the Lighting Controls Association,

National Electrical Manufacturers Association, ZING Communications, Inc. or their employees or members. All information contained in this course is

published for professionals seeking information about the subjects contained therein. It is not the intent of this course provide professional services

such as design, engineering or consulting. If these services are sought, they should be rendered by properly trained, registered, regulated and

insured professionals.

 

 

INTRODUCTION

Today’s lighting control systems work alongside and may need to communicate with many other systems such as audio/visual (A/V), mechanical air

handling (HVAC), life/safety, or computer networking (ITS). There are many reasons for this communication, such as using the same occupancy

sensor or sharing a single touchscreen in a conference room. Whether the design is simple or complex, integration ensures that communication

between multiple systems works. Integration services are necessary when multiple systems must communicate.

When the majority of systems in a building communicate with and trigger each other, this is referred to as a building automation system (BAS), which

can present intricate designs. Sometimes, the lighting control design may be the integral piece to an entire building’s automation system and

coordinating these complex designs may be the responsibility of the lighting controls designer. The successful designer will be able to identify the

intent of building automation, know how to integrate a lighting control system with other systems, and provide a comprehensive sequence of

operations.

The many puzzle pieces of building automation

 

INTRODUCTION

EE115: Integration and Building Automation defines today’s integration, how BAS are designed, and considerations for specifying integration and a

BAS. While not required, it is recommended you complete the following Education Express courses prior to this one:

EE 102: Switching Control

EE 105. Lighting Control System Design

EE 302: Intelligent Lighting Control

EE 305. Lighting Control Protocols

 

 

LEARNING OBJECTIVES

By the end of this course, you will be able to:

Discuss integration and BAS needs with clients

Design lighting control solutions with an understanding of what Integration and a BAS is

Identify projects that need an MSI consultant

Coordinate a lighting controls system that integrates with a BAS

Specify projects that use a BAS or integrator

 

 

INTRODUCTION TO BUILDING AUTOMATION

Also known as building management systems (BMS), BAS provide connectivity between any systems that automate a building’s functionality. They

coordinate all the functions using a sequence of operations (SOO) that is programmed into a central computer and identifies the various devices,

zones, or functions throughout the building. The BAS can therefore coordinate automatic operations so that manual control is rarely, if ever, required

by the occupants of the building.

Image courtesy of the U.S. Government Accountability Office

 

 

INTRODUCTION TO BUILDING AUTOMATION

Imagine you walk into a secured building after hours. You start by waving a badge at a door to unlock it, and before you open the door the lights

automatically turn ON for you. As you proceed from the lobby to the elevators, you hear the gentle whir of the air vents and notice that the space is at

a comfortable temperature. When you reach the elevators, a touchscreen lights up asking you to type in which floor you would like to go to. You touch

the button for floor 21 and an arrow indicates in which direction your elevator will arrive. A light over the elevator door turns ON indicating that the

elevator has arrived.

In just these few moments, you have interacted with countless systems throughout the building, using sensors and integrated processors that follow a

specific sequence of operations.

Image courtesy of Leviton

 

 

INTRODUCTION TO BUILDING AUTOMATION

The first system you interacted with was the security system that scanned your badge. This system was integrated with the lighting control system

and triggered the lighting to turn ON in the lobby. The security system also signaled the HVAC system to adjust the temperature in the lobby and turn

ON the vents. The elevator touchscreen has a proximity sensor to turn the screen ON when someone is near and is also integrated with the elevator

control system to identify each elevator cab and its location, which triggered direction arrows and indicator lights.

Many of these systems can function independently of each other but connecting them together with a central computer provides a seamless

experience. While this kind of automation requires an incredible level of coordination, design, and integration, the benefits of this design are

incomparable, and we’ve only scratched the surface of what building automation can do.

Image courtesy of Leviton

 

 

MARKET DRIVERS

The most common driver for building automation design is commercial building energy codes. Additionally, net-zero design, which is a design with a

net energy consumption of zero achieved through energy efficiency and renewable energy production, is growing in popularity throughout the United

States.

Another driver is data collection. Lighting is ubiquitous in buildings and is paired with some form of sensing technology. When using these sensors to

collect data, one can analyze building utilization. Additionally, if the system is networked with wireless connectivity, it can be used for asset

management and can track inventory such as laptops or bags within the building.

Finally, a growing trend is to provide security-related features. If the entire building can communicate, a lockdown of say a school building can be

implemented with a button push that would also call the police. Additionally, with motion sensors, police can monitor movement throughout the

building and be better informed before acting.

These are just a few examples of why building automation is growing in importance in building design.

   

 

BAS AND LIGHTING CONTROL SYSTEMS

Lighting control systems have had the ability to integrate with BAS for many years, yet only

recently has integration gained in popularity. As a result, lighting control manufacturers have had to

develop hardware and services to connect their systems to a BAS, but there are also manufacturers that

provide a complete BAS with lighting control included. In the United States, complete BAS designs often

are in the form of a proprietary system and may require the system and luminaires be provided by a

single manufacturer, thus limiting the options available to the designer.

When working on a project that has a BAS, the lighting controls designer should identify the needs of the

BAS and whether their system should be connected to it. Lighting controls often should connect if the

BAS will reduce and monitor energy use. While controlled LED lighting is low in energy consumption, it

can represent a significant number of the devices, including occupancy and daylight sensors that can be

used by the BAS.

 

 

WHAT IS INTEGRATION?

The term

integration

covers a wide array of people and tasks, and these definitions can vary among design professionals. As

of the publishing of this course, the industry’s definition is still in development, but there are a few things

that are certain about integration:

1. Integration bridges the gap between anything unrelated such as systems, designs, and manufacturers.

2. Integration can provide custom features to any controls system.

3. Integration can be a part of a project’s energy compliance requirements.

4. Integration is often required for projects with open protocols such as DMX.

5. Integration is essential for any project with a comprehensive BAS.

6. Integration can be designed prior to bidding or construction, but only recently has a role emerged specific to designing the integration.

 

 

WHY SPECIFY INTEGRATION?

A good lighting control system can operate independently but sharing devices and sensors with a BAS allows for more robust features and may

reduce the total number of devices. In applications such as conference rooms with media walls, A/V and lighting are often are expected to work

together. In this case, a single touchscreen is often used to control lighting and A/V.

Connecting multiple systems is not always as intuitive, however, and may involve trial and error during installation and commissioning, particularly

with complex applications. Because of this, it is often desirable to engage a specialist called an Integrator to take ownership of the connections

between systems and oversee the installation.

Image courtesy of Worldwide Market Reports

 

 

THREE TYPES OF INTEGRATORS

Specifying integration ensures that the project is priced accurately, and that the contractor has the support they need to complete the project with

minimal issues. Whether one is specified or not, it is likely that an integrator will be brought on to the project by the contractor. If one is not specified,

however, a contractor may get underbid by another that didn’t include one, resulting in integration being provided by a less-skilled professional with

associated risks.

While there are many integrators, we will focus on three major types:

1. Multisystem integration consultants (MSI Consultants)

2. Lighting control systems integrators (LCSI)

3. Manufacturer-provided integrators (MPI)

Depending on the project’s needs, each of these integrators offers distinct advantages and disadvantages. It is important to understand their roles

and responsibilities so that the project is designed, bid, and installed correctly.

 

 

MULTISYSTEM INTEGRATION CONSULTANTS (MSI)

MSI consultants are a relatively new player in the industry. These are consultants that help create the

bid documents for a project by overseeing all its integration points. In small integration designs, this

scope may be covered by the lighting control designer or the manufacturer’s representative, but in larger

projects involving BAS design, this scope should be assigned to a dedicated paid team member who will

be able to coordinate with all disciplines that will need integration.

Depending on the project, the MSI consultant may also be able to serve as the next type of integrator,

the lighting control systems integrator.

 

 

LIGHTING CONTROL SYSTEMS INTEGRATOR (LCSI)

LCSIs are third-party integrators who often provide the control devices. They oversee and train

contractors to ensure correct installation. After installation, the LCSI starts up, programs, and

commissions the system and trains the owner. LCSIs can work as an MSI consultant by attending

coordination meetings and providing drawings, but many LCSIs will not do this work for free unless the

project has a single-name specification, which guarantees them the work. This is frequently how

design/build projects work, but in design/bid/build projects the MSI consultant will often be an

independent group from the LCSI to eliminate conflicts of interest.

Additionally, LCSIs may also be product distributors and may be referred to as a lighting control systems

integrator and distributor (LCSID). This is an important distinction, because some LCSIDs typically only

work on projects where they supply the equipment. If the project is large and complex enough, the design may require multiple LCSIDs to provide the

equipment.

The successful lighting controls designer should always consider specifying an LCSI when DMX is specified, when an open and a proprietary

protocol are used together, whenever multiple manufacturers must interoperate within the lighting control system, or when a custom user interface or

application programming interface (API) are required.

 

 

MANUFACTURER PROVIDED INTEGRATOR (MPI)

Also known as factory-certified technicians, MPIs are often provided on projects that only have one

manufacturer responsible for the control or automation system but may also be provided on other

projects. MPIs work to ensure that the manufacturer’s products work as intended but will not work on

equipment provided by another manufacturer. On projects with multiple manufacturers, there may be

multiple MPIs, and coordinating them may be challenging if their systems need to interoperate.

Selecting between an MPI and an LCSI is not an easy decision and comes down to intent. Will the

integrator be expected to do custom work? Will the system have equipment from multiple manufacturers

that must be interoperable? Will the lighting be complex with a lot of programming? If yes to any of

these, then an LCSI should be considered over an MPI.

 

 

THREE KINDS OF LIGHTING CONTROLS INTEGRATION

In addition to the many kinds of integrators, there are many types of integrations. Again, we will only focus on three major types:

1. Local device integration

2. Multisystem integration

3. Building automation integration

All three types describe when unrelated devices, systems, or user interfaces need to be tied together, but the complexity of the design is what will

dictate the type of integration to prepare for.

 

 

LOCAL DEVICE INTEGRATION

Local device integration refers to integration that is done from one device to another with limited shared

control. This is often done via an interface and a commonly shared protocol such as RS232, a protocol

common in interfacing and integration. In the case of RS232 integration design, the code is meaningless

to each device until assigned to a function. The programmers are responsible for assigning this

information in both devices so that a shared language is developed.

Let’s look at how this works in an example. A lighting control designer and A/V consultant design two

different systems that use different communication protocols, but the A/V system will have a

touchscreen that needs to control the lighting. To accomplish this, each system is provided with an

RS232 interface. The interfaces are then connected to each other via RS232 cabling. An LCSI programs

each system so that the touchscreen can trigger presets on the lighting control system via the RS232

protocol.

 

 

MULTISYSTEM INTEGRATION

Multisystem integration refers to integration used to control or monitor many systems from a central or

distributed control system. It’s used when multiple control manufacturers are involved and often requires

an agreed-upon protocol for communication. A good multisystem protocol can communicate with

individual devices and control them without the need for local device integration.

Let’s look at another example. A high-rise office building has color-changing lighting on the exterior that

needs to be controlled by the interior white lighting control system. The lighting designer has also

specified a variety of DMX-controlled color-changing luminaires from different manufacturers. The

lighting control system uses a DMX control signal to each luminaire and the interior lighting uses 0-10V

signal to dim. An LCSI programs the control system so that it can control the exterior color-changing

lighting and the interior white lighting together. The LCSI also provides a user interface that allows the

owner to have control over both systems. The owner can select any color for the exterior lighting while at

the same time dim the interior lighting.

 

 

BUILDING AUTOMATION INTEGRATION

Building automation integration is integration that is used to control or monitor an entire building from a

central networked control system. Unlike multisystem integration, building automation typically entails a

higher level of design. While a multisystem design may require systems to communicate with each

other, building automation integration requires those systems to provide automatic triggers for each

other and a central server to monitor these triggers and provide priority and sequencing to each. This is

the essential integration required for a BAS.

Additionally, there are new BAS protocols, such as BACnet Secure Connect, which can provide an

easier end-user experience with larger and more complex systems integration.

 

 

BUILDING AUTOMATION INTEGRATION

Here are two examples. In the first, we have a building with integrated life/safety and lighting control

systems. During an emergency, the life/safety system activates and triggers the egress lighting to turn

ON to full output, while also signaling the building’s audio system to use any speakers in the building to

announce emergency status and procedures.

In another example, we have a high-rise office building with at least one tenant per floor. The owner

provides lighting and HVAC to each tenant but wants to minimize energy waste, and so it monitors

energy use via a BACnet server that oversees all lighting and HVAC devices. The lighting control

system interoperates using Bluetooth and reports to a BACnet interface, which translates between the

protocol so it can control the lighting. Reports are generated showing relative consumption between

these systems and the tenants. Programming at the BACnet server allows the operator to adjust the

sequencing to maximize energy cost savings.

 

 

DESIGNING A BAS

Designing a BAS and designing a lighting control system share similar steps, with the key element being

to identify its intent. BAS is well suited to reducing energy use, but the owner may also want to mine

occupant data and monitor assets. Every requested feature should be documented to inform design and

specification choices. Below are relevant questions to ask.

1. What is the intent of the BAS?

2. How is each system expected to function in the BAS?

3. Where will the central controls server be installed?

4. What is the central controls protocol?

5. How will lighting devices and luminaires interact with the central controls server? 1. Will the lighting control devices that provide triggers to other systems?

2. Will the lighting control devices need to directly control other devices?

6. What kinds of gateways or interfaces will the central controls server provide?

7. Who is responsible for specifying the BAS?

8. Will there be a custom graphical user interface (GUI) or API used and if so, who will provide it?

 

 

SPECIFYING THE BAS

While it’s uncommon for the lighting control designer to specify the BAS—often, it’s done by the mechanical engineer—it may occur, and when it

does, a good deal of coordination is required to support the intent.

The first step is to schedule a coordination meeting with all disciplines involved in the BAS, no matter how small their involvement may be. This

meeting will be used to answer the questions on the previous page and help carve out scope—who will specify what control devices, triggers,

programming, and commissioning. The group should then review each space with the intent to create a sequence of operations (SOO), a document

used to identify devices and triggers in a BAS (and in a lighting control system).

After the SOO is produced, identify a manufacturer or open protocol that will satisfy its requirements. Meet with manufacturers and their

representatives to discuss the project’s needs and review products and services. While it’s not the BAS designer’s responsibility to specify everything,

it is their responsibility to ensure all disciplines can connect to the BAS.

 

 

SPECIFYING: DOCUMENTATION

The SOO is one of many documents the lighting controls designer will create to support a project, but there are two major categories of

documentation: drawings and specifications.

Drawings are used to document the graphical and pictorial portions of the contract documents. These documents show the location and dimensions

of the project design and can be referred to as the “Sheets,” “Drawings,” “Layouts,” “Elevations,” or “Plans.”

Specifications are written requirements for devices and workmanship for the project. These documents support the drawings and cover information

that may not be able to be communicated on the drawings. Specifications can be referred to as the “Specs,” “Project Manual,” “Prescriptive

Specifications,” or “Legal Documents.” The drawings are still legal contractual documents, but the specifications often use very deliberate legal

language.

The SOO may be provided in either category but is frequently shown in the drawings as a graphical matrix.

 

 

SPECIFYING: DIVISIONS AND TRADES

Image courtesy of the Construction Specifications Institute

When providing a specification in North America, it is common to use CSI’s MasterFormat® to number

and organize each specification document. Lighting controls are covered under Division 26, the

Electrical Division, but BAS may be specified under multiple divisions, including:

Division 21 – Fire Suppression

Division 22 – Plumbing

Division 23 – HVAC

Division 25 – Integrated Automation

Division 26 – Electrical

Division 27 – Communications

Division 28 – Electronic Safety and Security

If the lighting controls are specified with the BAS design in a division other than 26, identify the new division and number in a location where the

electrical contractor will look so that it is clearly communicated which contractor is responsible for that scope.

 

 

SPECIFYING: SYSTEM INTERFACES

As mentioned earlier, systems may make use of system interfaces to communicate with each other by

taking in one protocol and converting it to another. System interfaces can be simplistic—providing a

simple method of controls such as ON/OFF or 0-10V—but they can also be very dynamic, coordinating

functions and triggers with multiple connected systems.

The most common system interface used on a BAS is known as a field controller. These interfaces act

as a central point of contact for various devices and can provide multiple types of protocols and methods

of control. Some lighting controls manufacturers are beginning to provide field controllers as a part of

their distributed or networked lighting control systems, but it is still uncommon to see them in a lighting

control system.

 

 

SPECIFYING: GRAPHICAL USER INTERFACE (GUI) AND APPLICATION PROGRAMMING INTERFACE (API)

Another common interface on a BAS is a graphical user interface (GUI). A GUI is used on a computer or

touchscreen to gain a visual display of the controls to receive updates (e.g., device status) and to assign

functionality to devices or groups of devices. GUIs can be provided by the manufacturer with standard

features, or custom GUIs can be created.

An LCSI is often included on a project if a custom GUI is being provided for the controls. Custom GUIs

often require additional system interfaces and/or a custom API. Some software applications, services, or

websites have an API to offer a specialized way for users to interact with that application instead of a

more traditional method. A user interface with an API has elevated capabilities over the control system,

but the design may be limited by the cost and time required for programming. LCSIs may be able to

provide a custom GUI and API, but not all do this, so it is important if the project needs these to specify

an LCSI that has this capability.

Image courtesy of Johnson Controls

 

 

SPECIFYING: INSTALLATION OF A BAS

The installation or “construction administration” phase of the project is when the physical integration work is performed. This includes everything from

purchasing equipment to training the owner.

A good BAS design specification will describe what is expected to happen during the installation, including a breakdown of scope per each discipline,

and may even identify different disciplines for the same device but at different stages. For instance, the electrical contractor may install all the low-

voltage devices and wiring, but then the integrator may terminate the wiring into the devices and program them. Since a BAS involves many

disciplines, identifying who will provide what and when is critical to avoid missing parts or services. It is the BAS designer’s responsibility to identify

the scope of each discipline and may do so using various methods. A common method is via a scope matrix, which is a diagram that indicates who is

responsible for what.

Image courtesy of BuildingIQ

 

 

LOOKING FORWARD: POWER OVER ETHERNET (PoE)

Image courtesy of the National Electrical Manufacturers Association

At the time of this course’s publication, power over Ethernet (PoE) is an emerging technology that

provides many benefits to a BAS. By combining data and power within one cable (CAT5 or CAT6),

specification and installation becomes simplified. PoE designs by nature are finding a home in Division

27 – Communications, as most of the same equipment used for the building’s computer network is used

on a PoE system. Putting the BAS into Division 27 provides a clear route to fully networking the building

and so there is a lot of promise with this technology.

 

 

LOOKING FORWARD: INTERNET OF THINGS (IoT)

The Internet of Things (IoT) is another emerging technology that holds significant promise. The technology enables any object to be connected to the

internet. This capability is still in its infancy, but we are seeing it bring newer and more creative features to a BAS, such as improved environment

control, asset tracking, and space occupancy utilization, to name a few.

 

 

WRAPPING IT UP

For better or worse, integration and BAS are intrinsically tied together, and it’s hard to speak about one without the other. While a BAS can be

installed without a qualified integrator involved, there is a greater risk to the project if an integrator is omitted, as integration typically must occur

regardless.

An integrator oversees the project and makes sure that all the separate systems and disciplines are connected correctly so that a BAS can effectively

communicate throughout. The BAS oversees the various systems that it is connected to and follows a SOO designed to provide an automatic and

seamless experience throughout the building. The SOO should be the guiding document created at the beginning of the BAS design.

It is the BAS designer’s responsibility to make sure that the SOO is complete, and all documentation delineates the scope per the appropriate

discipline. While the BAS may be specified under different divisions and disciplines, it should be clear who is responsible for what. The successful

BAS designer will have many coordination meetings confirming function and design with every discipline connecting to the BAS.

The successful lighting control designer will be able to identify the intent of building automation, know how to integrate a lighting control system with

other unrelated systems, and provide a comprehensive SOO. A BAS may take time and effort to design, but the improved quality of life with a BAS is

hard to ignore and more owners are reaping the benefits of BAS design work. It is the lighting control designer’s responsibility to be an effective

design team member and prepare to step in as the BAS designer, if necessary.

 

 

YOU’RE FINISHED

You have completed the Education Express course EE115: Integration and Building Automation. Please take a moment to provide feedback about

your experience with this course. You may also take the Comprehension Test to test your learning and to qualify for credit towards your education

goals.

EE115: Integration and Building Automation Comprehension Test