If COVID-19 taught facilities managers and building engineers anything, it’s the importance of proper design and maintenance of air and water systems for stopping the spread of pathogens. But aside from Coronavirus, there are other deadly bugs we need to control if we are to create healthy environments for building occupants. Legionnaires’ disease is one of them.
What is Legionnaires’ disease?
Legionnaires’ disease is a serious respiratory illness caused by the bacterium Legionella pneumophila. It is typically contracted by inhaling small droplets of water that contain the bacteria and can occur when water vapor or mist from a contaminated source is inhaled into the lungs. Facility water and cooling systems can become a source of Legionella bacteria if they are not properly designed, installed, and maintained.
Outbreaks are common with facilities like hotels, vacation rentals, medical facilities and cruise ships. Public hot tubs, for example, present ideal conditions for Legionella pneumophila and are common sources for outbreaks. About 1 in 10 people who contract Legionnaires’ disease will die due to complications from the illness. In health care facilities, the mortality rate jumps to 1 in 4, according to the CDC.
Controlling the Spread
To minimize the risk of Legionnaires’ disease growing within water or cooling systems, it is important to follow best practices for the design, installation, and maintenance of these systems.
Water Cooler System Design. Design water and cooling systems to minimize the risk of Legionella growth and proliferation. This includes using materials that are resistant to corrosion and scale formation, as well as designing the system to allow for proper water flow and circulation.
Regular Maintenance. Regularly clean and maintain water and cooling systems to prevent the buildup of Legionella bacteria. This includes flushing the system to remove any sediment or debris and using water treatment chemicals to kill bacteria and prevent the growth of biofilm.
Temperature Control. Maintain your water and cooling systems at a temperature too high for Legionella bacteria to grow. This typically means keeping the water temperature preferably above 124°F (51°C), and below 68°F (20°C). (Source: CDC)
Control Your pH Levels. Legionella bacteria thrive in water with a pH between 6.0 and 8.5. To prevent the growth of these bacteria, it is important to maintain the pH of the water in the system outside this range. Studies show that a pH of 9.6 prevents the bacteria’s growth in cooling towers. (Source: Water Research).
Disinfection. Regularly disinfect water and cooling systems to kill any Legionella bacteria that may be present. This can be done using chemicals such as chlorine or monochloramine or by using UV light to kill the bacteria.
Risk Assessment. It is important to regularly assess the risk of Legionella growth in water and cooling systems. Implement appropriate control measures as needed. This may include regularly testing the water for the presence of Legionella bacteria and implementing additional measures such as water treatment or increased cleaning.
In addition to these measures, it is important to educate employees and building occupants about the risks of Legionnaires’ disease and how to prevent it. This may include providing information about the signs and symptoms of the disease and reminding people to wash their hands frequently to reduce the risk of infection.
Overall, the key to preventing Legionnaires’ disease from water and cooling systems is to properly design, install, and maintain these systems. By following these best practices, you can significantly reduce the risk of this serious and potentially life-threatening illness.
Remote work has presented challenges for both workers and their companies. Challenges include adopting flexible schedules and conducting video interviews. However, managing a team of remote workers can be a challenge, but it can also be a rewarding experience for both the employer and employees. With the right strategies in place, it is possible to effectively manage and support a team of remote workers. Here are some tips for managing remote workers:
1. Clearly Communicate Expectations
It’s important to make sure that remote workers know what is expected of them and how their role fits into the overall goals of the company. Regular meetings and clear, concise communication are best for providing expectations. When explaining your anticipations, whether verbally or written, use simple language, short instructions, and concrete examples. Anticipate potential problems and emphasize actions that are acceptable and ones that aren’t. So as not to appear negative, maybe include a few anticipated positives too.
2. Set Regular Check-ins
Scheduling regular check-ins with remote workers can help to ensure that they are on track with their work and address any concerns they may have. They also make up for the emotional gap left from the absence of face-to-face communication. The non-verbal cues we get from personal interactions are critical to building trust, empathy, and understanding, even in a professional relationship. Regular check-ins help make up for this deficient.
3. Keep Meetings Short
Employees can’t maximize remote work benefits if they spend too much time in lengthy online meetings. They might as well be at the office. Set a start and stop time and stick to it. One easy way to do this is to set a timer on your phone or your Windows Clock app. Better yet, use the free version of Zoom conference calling, which limits a call to forty minutes. The service will pop up a reminder that your meeting is about to end so you can wrap up your discussion. Also, use a meeting agenda with bullet points to keep the meeting on track.
4. Shift to a Results-based Appraisal
Your employees’ workflows will inevitably change with remote work. It’s just the nature of remote work for more time to be spent on other things like family responsibilities during “normal” work hours. Besides, the whole appeal of remote work is that workers can have a healthier work-life balance. So, shift your appraisal from the “correct” process, to goals and results. Dedicated, honest workers will find the shortest distance from A to B in their new workflow. Let them find their way. Ask yourself “Are they delivering results?” If the answer is “Yes”, then base your appraisal more on that fact rather than how unorthodox or non-traditional the approach to the work may seem.
5. Provide support
It is important to make sure that remote workers have the resources and support they need to be successful in their role. This can include access to training and development opportunities, as well as any necessary equipment or software. Create virtual “happy hours” or other informal events to build relationships.
6. React to Signs of Stress
Change is hard. Adjusting to a new workflow is a major change for employees. New problems crop up, along with opportunities. The stress may be overwhelming at time. Be sensitive to signs of over-work or excessive stress. Stressed workers may seem more argumentative, report more sick time, or complain more. Identify signs quickly so you can make changes. Check in regularly and facilitate an honest and open dialogue so workers aren’t afraid to tell you about problems.
Conclusion
In addition to these tips, there are a few best practices that can help to ensure the success of a remote team. For one, it is important to establish a process for tracking and managing work. This can include using project management software or creating clear, actionable to-do lists to ensure that work is completed efficiently and effectively.
Also, it’s critical to provide regular feedback to remote workers. This can help to keep them motivated and engaged, as well as provide opportunities for growth and development.
Managing a team of remote workers can be a challenge, but with the right strategies in place, it’s easy to ensure success for workers and the company. By following these tips, employers can create a positive and productive work environment for their remote team members.
Although often overlooked by building managers and engineers, data schemas are essential to the efficient building management, data analysis and system automation. That’s because schemas are the building blocks of effective database management. Without them, you foreclose your property’s potential to save energy, adopt tech, and compile valuable operational data that make your buildings run at more efficiently and at lower costs. But what are schemas and how do they work?
Database Schema Basics
Databases of all kinds must be organized in pre-determined ways. Otherwise, it’s impossible to store and retrieve data in any workable sense. Think of a schema as a naming standard “language” for how you write, store, and retrieve the information about your building—from the status of its assets to the historical data around energy use.
Just like any language, schemas have rules and conventions. Language has rules around naming things (e.g., noun, verb, etc.) and grammar (subject + verb + director object). If we don’t follow the rules, communication turns into confusion or completely breaks down. In the same way, database schema standards outline how things are stored, what they’re called, and how they’re related (i.e., relational database).
Schemas deal in metadata or “data about data”. For example, books have metadata in the form of their title, author, publisher, or call number. In the same way, buildings have data about their assets, such as asset name, location, site, or type.
For managers and engineers, schemas make recording and managing your asset database easier by ensuring your library is mapped, tagged and organized in a way that’s easily understood by machines and software. So, these standards are intended for both building owners and developers, ensuring both parties are speaking the same language.
Too often, managers and engineers use schemas customized to their site or ad hoc naming conventions that get lost when buildings change and people move on. Such informality creates confusion over time, but maintaining a standard schema ensures your software, BMS and assets can always communicate effectively.
Like advanced schemas, pictures are worth a thousand words.
Basic vs Advanced Schema
Some schemas are basic, recording only a few pieces of metadata (e.g., asset name, location, serial number). Other schemas are complex, recording many pieces of data. The more complex your schema, the more descriptive it is, and a more description means a “deeper” more powerful database, just as a long sentence is more descriptive than a short one. For example, consider the following two sentences:
“The dog fetched.”
“The black Labrador fetched the yellow tennis ball from its toy box.”
What are the major differences between these two sentences, and (more important) what can we do with the second sentence that we can’t do with the first?
For one, Sentence 2 contains more descriptive words (“black Labrador” “yellow” “toy box”), so we have a better understanding of the context. Second, the shorter sentence lacks an object. We know the dog fetched, but we don’t know what it fetched. The second sentence tells us—it’s the ball. In the longer sentence, we’re even given information about the situation (i.e., the Lab has a toy box). More importantly, Sentence 2 creates a relationship between the subject and the object. We can say, therefore, that the longer sentence is “relational” in that it describes how one thing (the dog) is related to another (the ball), which is related to another thing (the toy box).
These same differences exist between informal and standardised schemas. Longer, more descriptive schemas provide more context and meaning around a building asset. They’re also relational, in that they describe how one asset (e.g., temperature sensor) is related to another (e.g., AHU). Consider these two naming schemas for a temperature sensor housed on Level 9 of a hospital.
Examples of basic and advanced standard schemas
While the basic schema lists only the location (LV09) and asset name (TempS), the advanced schema extends the description to include the building, system, asset type, point type, specific location, and the device class. With these added details, we now have a relational description of the sensor. For example, we know it is part of the mechanical (M) system and part of an AHU. Therefore, we can say Schema 2 is part of a relational database, and that it gives us a greater understanding of the asset and its place in the system.
Overall, Schema 2 gives us more context and meaning than Schema 1, and we can use this information to learn more about how our buildings operate. Once we extend this schema strategy to our entire building, we have a powerful way to analyze its contents and functional efficiency.
Schema Benefits
There are many benefits to adopting and maintaining a standard database schema. Here are a few of the most important.
Software Deployment
Standard schemas create a common lexicon and database structure for software developers to use. Adopting a standard naming schema makes software deployment and management much simpler. Developers and building systems benefit from a common, predictable set of rules and naming conventions. Such standards make software development and deployment easier and cheaper because both stakeholders are working from a shared data structure. The developer can simply bolt their software package to your system, and everything works out-of-the-box.
Advanced Queries and Dynamic Lists
Conventional BMS pages are static. Their queries are hard-baked, with pre-built graphics that deliver data around points such as fault detection, temperatures, run speeds and statuses. They are “static” in that their queries never change. Your BMS will only “ask” specific questions about your system. They may be important questions, but they are, to be sure, limited. Contrary to their appearances, however, buildings aren’t static with respect to the data they produce, and managers and engineers often need to run queries and generate dynamic lists that exist outside the BMS purview. Using a relational, standardised schema allows this limitless flexibility.
For example, say you suspected one of your AHUs was starting to fail. You could run a query that identified all room temperature sensors that have been reading above 21 degrees for the last 24-hours for that specific AHU. If your schema is relational, it understands which specific sensors to target. You could then upload the data to a dynamic page to help troubleshoot performance issues. Dynamic lists like these can improve predictive failure and shorten downtimes.
Boilers in a mechanical room.
Asset Replacement
With a standard relational schema, you can identify an asset’s effect on the system and impact to service. For example, a standard schema can show you the effects to other systems when you plan to replace a failed actuator. Before work begins, you can ask questions like: “Will replacing the actuator stop chilled water to the whole building or just the data center?” or “How will the replacement affect Tenant X, Y and Z?” Such insights give you and your service engineers the right information for estimating costs, cutting downtime, and ensuring better tenant outcomes.
Updating Building Data
Buildings go through many evolutions in their life cycle, and these changes affect your asset database. Standard relational schemas make updating metadata much easier and more accurate. Recording changes only requires updating one specific piece of data, like a room number or new part. After that, your system automatically adjusts names and relationships, both upstream and downstream. Standard schemas cut the time and costs of updating asset databases.
Popular Schema Standards
Today’s most popular standard schemas differ in their approach, but all attempt to standardise asset description and storage to aid interoperability and software deployment. Project Haystack is a tag-based schema focusing on streamlining operation between smart devices within buildings, homes, factories, and cities. The Brick Ontology standardises both asset labels and connections, allowing the user to create a relational database.
Conclusion
It’s difficult to make big data work for you without first putting it into a standard structure. Schemas are that structure—they’re the digital architecture of your building systems. By building your asset database with standard schema, you’re ensuring your building, tenants and occupants benefit from future invocations such as advanced analytics, AI, machine learning, and cloud computing. These are the future of building operations and facilities management. Once all buildings graduate to smart status, they’ll be connected to everything, and proptech will help managers do everything from calculating asset depreciation to managing carbon emissions.
You stride through a bustling conference hall, alive with excited chats and enthusiastic handshakes. In your pocket, a stack of freshly printed business cards. In your head, a well-rehearsed elevator pitch. You’re confident and poised, ready to network.
As you cruise, you notice only small groups engaged in salesy banter. You spot someone in a corner alone. Dang it, they’re on their phone. Then someone walks by you…maybe…nope, they’re headed to the bathroom. Soon a quiet panic sets in. You find no openings. You feel isolated, alone within the crowd. The clusters of exhibitors, speakers and attendees appear as guarded fortresses, impervious to any networking siege. The walls grow higher. That quiet panic is now a raucous party of self-doubt and insecurity. You bolt to a shadowy corner of the room. Finding a safe harbor, you whip out your phone and pretend to scroll.
Anyone who’s ever attended an expo or tradeshow is familiar with this situation. It’s a universal experience, and one that betrays a paradox: humans are built for social interaction but find it incredibly hard to meet new people. However, introductions aren’t an irrational phobia. Meeting new people is full of unknowns. As children, we’re taught “Don’t talk to strangers”, only to grow up and realize it’s essential to doing business, making friends, and finding mates.
Introductions require an excuse to command someone’s attention. Icebreakers are simply excuses we’ve deemed “acceptable” for presuming someone wants to talk to us. We all know when someone crosses a line, and it’s this fear of transgression that, in large part, fuels our own anxiety towards meeting new people. We don’t want to be the person who interrupts, shares too much or comes off as “creepy”. But with preparation and practice, you can learn how to construct and deploy effective convo starters to super charge your next networking event. Here are 5 icebreaker tips to increase your networking success at your next tradeshow.
1. Choose Universal Topics
Effective icebreakers reflect common experiences. That’s why many people use sports or the weather to form a fast connection. But convo starters don’t have to reflect the human experience. In fact, they can be too broad. Something like “How ‘bout this weather?” would probably seem too general for a group gathered specifically to do business (unless that business is meteorology).
Instead, make your topics universally specific to the situation. With respect to an expo or tradeshow, a more specific “universal” topic would be something that many (but only) show attendees experienced. (“Did you enjoy the awards dinner last night?”). Other examples include:
“Who do you work for?”
“What industry are you in?”
“Can you recommend any good sessions to attend?”
“What’s your favorite part of the show so far?”
“Have you been to the Expo before?”
“Did you see X Company’s demonstration?”
Memorize four to six of these icebreakers and have them ready to go. You’ll discover more as the show goes on and be able to fine tune them to the situation.
Pro Tip: Eat lunch in the commons area of the tradeshow venue. Many will congregate here, and lunch is a perfect opportunity to socialize.
2. Keep Questions Person-Centered and Open-Ended
People enjoy talking about themselves, so your icebreakers should focus on the person or group. The example open questions above are person-centric, while not overstepping the line of being “too personal”. If you tell a story or anecdote, it should serve the purposes of the group and add value to the group’s discussion, not show how smart you are.
In general, you’ll get further with questions that elicit personal opinions (“What’s your favorite part of the show so far?”) rather than simple facts (“Who do you work for?”). That’s because opinions leave more room for commentary.
In general, design your questions to be open-ended. For example: “Who do you work for?” will get you less information than “Is your company exhibiting at the Show this year?” Even subtle changes in how you phrase the same question can have big impacts. Consider these two questions:
“Is this your first time at the Expo?”
“Have you been to the Expo before?”
While both are asking the same basic question, you will likely get two different answers. While # 1 may get you a simple “yes” or “no” response, the answer to # 2 will usually be longer and more in-depth. That’s because the addition of the phrase “before” references a past event. The reference unconsciously prompts the listener to be more descriptive or to tell a story of past events. The longer you can keep the convo started, the better your chances at making a deeper connection.
3. Learn to Infiltrate Small Groups
It’s difficult joining small groups where people are already engaged in conversations. Many of us feel injecting ourselves into the group is too intrusive or creepy. Much of this exclusionary vibe comes from the fact that people in groups tend to stand in a circular formation. The shape itself creates a boundary that seems to warn, “Do not enter.” However, the standard circular formation is a practical construction that ensures everyone inside can make eye contact. So, ironically, the circle is actually an attempt at inclusion. We do well to remember this fact, whether we are on the inside or outside.
Here are a few hacks for breaking into a group circle:
Start a convo with a group member, preferable one who seems bored. Then slowly work your way into the circle, or start a new one.
Look for a group with an odd number of people. It ensures there’s at least one person available for a chat.
Get in early. Locate a group that’s just starting to form.
At an after part event, wait for a drink server to come by for deliveries or to pick up empties. This usually breaks the circle momentarily. Use the opportunity to gain closer proximity.
Listen and wait until you can add something valuable and relevant. Make sure it’s substantial, but not too domineering. Short comments are easily acknowledged then ignored.
Smile and appear generally upbeat and approachable yourself.
Address the group. Deploy an interesting anecdote, ask an open-ended question, or relate a personal story. Anything interesting, educational or relevant will be well received.
Keep in mind, some groups are simply more “open” and sociable. The more familiar the members are with one another, the more they tend to keep things tight. To identify closed groups, look for body language signals. Friends or colleagues will tend to stand closer to one another, forming a tighter circle. These can be difficult to break. Other groups may be in a serious conversation and aren’t interested in being “social”. Look for signals like serious looks, crossed arms, or direct face-to-face discussions. Such closed groups should be obvious. Approach with caution.
4. Flattery is Your Friend
Flattery gets you everywhere when it comes to meeting people. Everyone is instantly receptive to praise, so flattery is an easy win for icebreakers. Most folks who are “famous” in your industry come to conferences expecting a bit of approbation—so, give it to them! You’re likely not annoying them, especially if they’re alone. In these cases, it’s acceptable to begin with a comment about yourself (“I enjoy reading your blog articles on smart building tech.”) In this case, you’re leading with an “I” statement, which may seem to shift the focus off the other person, but the compliment is actually putting all the attention on them.
5. Introduce Yourself Online Before the Tradeshow
There are plenty of to-dos on the pre-show checklist, from identifying your target audience to following groups on social media. But make sure online preliminary introductions is one task you check off. Connect with people on LinkedIn, Facebook and Instagram. Like their pages and follow their accounts. It’s easier to “meet” someone in person if they’ve already “accepted” you with a connect request. So, use that digital handshake to your advantage.
Also, use your online accounts to announce you’ll be attending. Ask if anyone else is planning on going. Post to your trade groups and connections list. Follow up with offers to meet for coffee or lunch. You’ll likely make new connections. Announcing your plans to attend is an effective way to show your enthusiasm and openness to networking, and it will make real-life introductions much easier.
Conclusion
Like any skill, conference networking takes practice. There’s no substitute for hard work. Experience will hone your skills at picking up on body language signals, tone of voice, and group dynamics. You’ll fine tune your anecdotes, perfect your presentation. With these skills, you can identify better networking prospects and command the room.
In this article in our BACnet Basics Series, we look at Device Profiles, why they’re important and how they’re created. We’ve also included a real world example that illustrates how to use device profiles to accurately specify your own projects.
What are Device Profiles?
As we saw in BACnet Basics: What are BIBBs?, device functions come in five basic categories, each containing specific capabilities. For example, the category Data Sharing (DS) includes capabilities like Read Properties (RP), Write Properties (WP) or Change of Value (COV). If we combined all these services into a minimum collection of capabilities, we would be creating a device profile.
As an analogy, think of the profile “Automobile”. Every machine that claims to be an “automobile” needs the functions of Acceleration (A), Deceleration (D) and Maneuverability (M). Of course, there can be automobiles that do much more, but every “automobile” must, at minimum, perform these three functions (A,D,M).
Definition: BACnet device profiles define the minimum set of BACnet Interoperability Building Blocks (BIBBs) supported by a device claiming that profile. When a device claims a specific profile, you know that it contains a preset of specified functions and services. Profiles are handy because they provide a short-hand method for describing a device and its interoperability capabilities. Device profiles are organized into Groups and Families
Device Groups
Device Groups are general categories of device functions. There are four Group types:
Operator Interface—Covers the minimum capabilities for workstations and other user interface devices. Devices normally support A-side (Client) functionality.
Controller Device—Covers anything from programmable building controllers to smart sensors. Devices normally support B-side (Server) functionality, but more advanced supervisory controllers also include A-side (Client) functionality.
Control Station—Covers lighting control stations that are smaller client devices that support specific user controls such as manual light switches.
Basic Device—Covers all “miscellaneous” family functionality. Usually included alongside other device profiles.
Device Families
Each Profile Group contains various Families within it. Families cover profiles for various, supported building systems like Lighting, Life Safety, and General Purpose. For example, the Controller Device Group contains profiles for the following Family types:
(Example) Controller Family
General Purpose—General purpose controllers usually for HVAC and lighting.
Access Control—Access control controllers such as an access control panel
Lighting—Lighting controllers such as supervisory lighting controller
Life Safety—Life safety controllers such as a fire detection panel.
Elevator—Elevator controllers
Let’s zoom into the General Purpose profile family within the Controller Device Group and see what BIBBs it contains.
Building Controller (B-BC) —Field programmable and configurable supervisory controllers in HVAC and general purpose application.
Advanced Application Controller (B-AAC)—Controllers that run advanced HVAC or general purpose control applications.
Application Specific Controller (B-ASC)—Controllers that run specific HVAC or general purpose control applications.
Smart Sensor (B-SS)—Small sensors that provide sensor values to other devices.
BACnet device profile Families are organized in a container hierarchy. As you move up in complexity, you increase the minimum amount of BIBBS required. Like nesting dolls, each profile contains all the minimum profiles from the previous ones.
For example, the above General Purpose BACnet profiles increase in complexity as you move up from Smart Sensor to Building Controller. All BIBBS included in a Smart Sensor profile are always included in a Smart Actuator profile, and all the BIBBs included in those two profiles are always included in an Application Specific Controller, and so on.
Although higher level BACnet profiles contain more BIBBs, it’s not the number of profiles that matters. Each profile requires a minimum number and type of profiles. So, even if a device contains or exceeds the minimum number of BIBBs, it doesn’t guarantee it will meet the standard. It must contain the minimum number of the correct BIBBs to meet the profile standard.
Specifying Device Profiles: Boardroom Example
Let’s use the Device Profile Quick Reference Guide to see an example of how to choose the device profiles for a real-world project. Read the following scenario:
You want to outfit a medium-sized boardroom equipped with a control panel with a built-in controller. The panel will control the room’s temperature and lighting. You also need manual lighting controls near the door.
To determine the device profiles needed for the project, we can start by listing the functionality we need. We will need HVAC controls for temperature. For lighting, we will need controls for both the panel and a manual user control switch on the wall. Therefore, we will need functionality from the Controller Group and Control Station Group.
Next, we can determine what Families we need within each group.
For the Controller Group, we need:
General PurposeFamily for HVAC
Lighting Family for panel control lighting
Access ControlFamily for access
For the Control Station Group, we need:
Lighting Family for manual switch lighting control
Finally, we can choose specific profiles to fulfill our HVAC and lighting functionality.
HVAC Profiles
In the Reference Guide, we see the following profiles for the General Purpose Controller Family:
B-BC: The building controller is intended for field programmable and configurable supervisory controllers in HVAC and general purpose applications.
B-AAC: The advanced application controller is intended for controllers that run advanced HVAC or general purpose control applications. It does not require being configurable through BACnet.
B-ASC: The application specific controller is intended for controllers that run specific HVAC or general purpose control applications. It does not require being configurable through BACnet.
B-SA: The smart actuator is intended for small actuator devices that allow being commanded.
B-SS: The smart sensor is intended for small sensor devices that provide sensor values to other devices.
We can ignore the last two profiles, because we need neither actuators (B-SA) or sensors (B-SS) for the project. We can also eliminate the Building Controller (B-BC) profile because it does not require supervisory control. Depending on our HVAC needs, we could choose either the Advanced Application (B-AAC) or the Application Specific (B-ASC) profile.
Lighting Profiles
In the Reference Guide, we see the following profiles for the Lighting Controller Family:
B-LS: The lighting supervisory controller is intended for controllers in lighting applications that can command and operate subordinate lighting controllers, in particular through group write commanding.
B-LD: The lighting device is intended for lighting controllers that control individual lights or groups of lights. Normally used as leaf nodes in lighting group setups.
We would choose the B-LD profile if the panel only controls one group of lights. However, if the lighting is more complex, we might opt for the B-LS with supervisory controls.
Control Station Profiles
Because the room also requires manual user lighting controls, we need a profile from the Control Station Family. In the Reference Guide, we see the following profiles:
B-ALCS: The advanced lighting control station is intended for sophisticated control stations that support user view, control and limited configuration of lighting functionality. Provides full commanding support of lighting objects and group operations for them.
B-LCS: The lighting control station is intended for control stations that support simple control of lighting functionality and limited status indication. Provides limited support of commanding lighting objects.
The simpler B-LCS would work for this project. But, again, depending on the complexity of the room’s lighting, we might choose the more complex profile.
Conclusion
Through the Boardroom Example above, we can see how BACnet profiles make project specifications easier and more accurate. Standards and profiles support an accurate procurement process, requiring less change orders and adjustments. Defining capabilities also creates an outcomes-based workflow so that buildings function the way owners and tenants need them to.
