<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Jim Butler on Medium]]></title>
        <description><![CDATA[Stories by Jim Butler on Medium]]></description>
        <link>https://medium.com/@jimbutlerma?source=rss-c5fe3c4d1b58------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*L-scSLaG5sJoHNCQbjhGog.jpeg</url>
            <title>Stories by Jim Butler on Medium</title>
            <link>https://medium.com/@jimbutlerma?source=rss-c5fe3c4d1b58------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 16:42:24 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@jimbutlerma/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Protecting BAS from Cybersecurity Threats]]></title>
            <link>https://medium.com/new-deal/protecting-bas-from-cybersecurity-threats-3c5ab0f6d822?source=rss-c5fe3c4d1b58------2</link>
            <guid isPermaLink="false">https://medium.com/p/3c5ab0f6d822</guid>
            <category><![CDATA[nist-framework]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[ndsummit]]></category>
            <category><![CDATA[facility-it]]></category>
            <category><![CDATA[building-automation]]></category>
            <dc:creator><![CDATA[Jim Butler]]></dc:creator>
            <pubDate>Thu, 23 Jan 2020 22:38:50 GMT</pubDate>
            <atom:updated>2020-01-23T22:38:50.178Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FXTdG_aCbZ_L2bm76CfcTA.png" /></figure><p>This article is one of a series of articles that have been published to coincide with the <a href="https://newdeal.blog/cybersecurity-summit-2020-2500e4a28024">New Deal Cybersecurity Summit at AHR Expo 2020 in Orlando</a>.</p><p>For an overview of the relevance of the NIST Cybersecurity Framework to BAS, and links to other articles, read this story: “<a href="https://newdeal.blog/nist-cybersecurity-framework-and-bas-832ddda58ad">NIST Cybersecurity Framework and BAS</a>”.</p><h3>Why do we need to protect building automation systems?</h3><p>Buildings are critical infrastructure, and building automation systems (BAS) have a key role in ensuring that commercial and industrial buildings can be used for their intended purposes. BAS systems are evolving; for example, TCP/IP and Ethernet communication are increasingly being used within BAS systems, and BAS systems increasingly share IT-managed network infrastructure with other systems. A consequence of this evolution is that BAS systems are facing new and increasing cybersecurity threats.</p><p>Here are some of the types of attacks that BAS systems could face today:</p><ol><li>Ransomware. This is a popular way for cybercriminals to profit from their hacking, and BAS systems might be seen as vulnerable.</li><li>Lateral attacks. Poorly protected BAS systems can be a stepping stone to facilitate attacks against other systems to which they are connected. One example of a lateral attack is described in <a href="https://www.casino.org/news/hackers-stole-las-vegas-casino-high-roller-database-via-its-fish-tank/">this news article</a> about how hackers apparently stole valuable data from a casino by first attacking a network-connected device in a fish tank.</li><li>Denial of service. BAS devices are potentially vulnerable to such attacks and compromised BAS devices could be used in botnets to carry out such attacks.</li></ol><p>Protecting BAS systems from cyberattacks is the joint responsibility of building owners, building managers, IT networking and cybersecurity personnel, BAS integrators, and BAS manufacturers. In order to work together effectively, we should use a common playbook. One such playbook that is in widespread use in IT is the NIST Cybersecurity Framework.</p><h3>Leveraging the NIST Cybersecurity Framework</h3><p>The <a href="https://www.nist.gov/cyberframework">NIST Cybersecurity Framework version 1.1</a> defines a structured approach for managing and reducing cybersecurity risk in critical infrastructure, and <a href="https://newdeal.blog/nist-cybersecurity-framework-and-bas-832ddda58ad">we can apply the Framework to BAS systems</a>.</p><p>The following table shows the five functions of the Framework (Identify, Protect, Detect, Respond and Recover). Each function has a corresponding set of outcomes/actions, which are referred to as categories; for example, Asset Management is a category within the Identify function.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BjmxtoUxQsZYjcOS7DE0ww.png" /></figure><p>The Protect function of the Framework is where we can look for guidance about protecting BAS systems. But before we go about developing a strategy for protecting assets in a particular system, we need to identify the BAS assets and determine the most critical risks to those assets. These activities fall into the Identify function of the NIST framework, which is discussed in the article “<a href="https://newdeal.blog/b774e3911aa6">Understanding NIST’s Identify Function</a>”.</p><p>In the table shown above, the Protect column lists several categories of desirable outcomes and activities that go into protecting a system.</p><p><strong>Identity Management and Access Control:</strong> Access to BAS assets should be limited to authorized users, processes, and devices. This includes all manner of access, including physical access and remote access. Managing credentials used for authentication (e.g. usernames and their corresponding passwords) is an integral part of this activity.</p><p><strong>Awareness and Training:</strong> All BAS users and other stakeholders should receive cybersecurity awareness education and role-appropriate training about their cybersecurity responsibilities.</p><p><strong>Data Security:</strong> The three primary goals are maintaining the confidentiality of sensitive data, the integrity of data, and the availability of data necessary for building operation. Data stored within BAS devices should be protected, as well as data transmitted on a communication channel (e.g. a network).</p><p><strong>Information Protection Processes and Procedures: </strong>This includes baseline BAS system and device configurations that reflect good cybersecurity practices, procedures for conducting backups of important data, and incident response and recovery plans.</p><p><strong>Maintenance: </strong>When maintenance of BAS assets is required, it should be done using approved tools. All BAS maintenance should be logged. Remote maintenance requires prior approval and must be done in a way that prevents unauthorized access.</p><p><strong>Protective Technology:</strong> Technical security solutions should be managed in such a way as to ensure that BAS systems are secure and resilient. Such solutions include audit logging and network security controls.</p><p>The degree to which an organization implements the Protection recommendations in the Framework should be determined by the organization based on its assessment of the expected costs and potential benefits of implementation.</p><h3>How does BACnet/SC protect BAS systems?</h3><p>BACnet/SC, which was officially added to the BACnet standard (ANSI/ASHRAE Standard 135) in November 2019, is a new communication technology for use on TCP/IP networks that are built upon widely used network protocols (TCP, TLS, and WebSocket). BACnet/SC requires peer authentication of devices and encryption of all network traffic.</p><p>In terms of the NIST Cybersecurity Framework, BACnet/SC contributes to Identity Management and Access Control by requiring devices to be authenticated and by limiting BACnet/SC network access to authorized devices. As well, BACnet/SC contributes to Data Security by using a reliable transport protocol and encryption.</p><p><a href="https://newdeal.blog/cybersecurity-summit-2020-2500e4a28024"><strong>Learn more about BAS cybersecurity from the panel of experts at the New Deal Cybersecurity Summit on February 4, 2020.</strong></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3c5ab0f6d822" width="1" height="1" alt=""><hr><p><a href="https://medium.com/new-deal/protecting-bas-from-cybersecurity-threats-3c5ab0f6d822">Protecting BAS from Cybersecurity Threats</a> was originally published in <a href="https://medium.com/new-deal">A New Deal for Buildings</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What Your Building Isn’t Telling You]]></title>
            <link>https://medium.com/new-deal/what-your-building-isnt-telling-you-36cecdf0cd71?source=rss-c5fe3c4d1b58------2</link>
            <guid isPermaLink="false">https://medium.com/p/36cecdf0cd71</guid>
            <category><![CDATA[hvac]]></category>
            <category><![CDATA[automation]]></category>
            <category><![CDATA[building]]></category>
            <category><![CDATA[energy]]></category>
            <category><![CDATA[sensors]]></category>
            <dc:creator><![CDATA[Jim Butler]]></dc:creator>
            <pubDate>Mon, 26 Feb 2018 18:11:32 GMT</pubDate>
            <atom:updated>2018-02-26T22:45:00.929Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8hSxraSHs8X1yaF4H9cTEA.png" /></figure><p>In our analytical services business, we frequently find significant problems in commercial and industrial building HVAC systems that have probably gone unnoticed for some time. Many of these problems have resulted in wasted energy and other problems that can affect system reliability, performance and efficiency.</p><p>When we point out a problem, building managers sometimes tell us: “There haven’t been any comfort complaints or alarms, so we didn’t know that anything was wrong.” HVAC controllers are designed to compensate for varying input conditions and are somewhat tolerant of faults in other parts of the HVAC system, so building occupants may not notice that anything is amiss until a problem becomes acute.</p><p>But why don’t building automation systems inform the building operators about common faults? In fact, building automation systems are capable of reporting certain simple fault conditions to building operators or building occupants, but these systems are generally unable to detect or diagnose many important faults that are more complex. Why is this the case? There are two primary reasons:</p><p>1. It is common for installed building automation systems to have insufficient sensors to reliably detect or diagnose many important faults.</p><p>2. Detecting relatively complex fault conditions typically requires custom automation system programming, which is generally limited to the implementation of customer-specified sequences of operation.</p><p>#1 is an important problem in the HVAC industry, and often results from the “minimize first cost” objective on many projects. To illustrate this problem, let’s look at one algorithm frequently implemented in HVAC analytics software. This algorithm is used to detect a leaking heating valve in a built-up air handling unit, a relatively common problem that can result in wasted energy and reduced air handler cooling capacity. The heating valve controls the flow of hot water into the heating coil. If the heating valve has been commanded to be fully closed by air handling unit’s controller, then a significant air temperature increase as air flows across the heating coil indicates that the valve is probably not fully closed, allowing hot water to flow through the coil when it not needed or desired.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0-GURaHkthaHqLA7eZeJzA.png" /><figcaption>Simplified diagram of heating &amp; cooling elements in an AHU (Air Handling Unit)</figcaption></figure><p>An algorithm that can detect this problem typically uses data from an air temperature sensor immediately prior to the heating coil and a temperature sensor immediately after the heating coil in the supply air stream, as well as the commanded position of the heating valve. However, if one of the air temperature sensors is missing (most likely the sensor between the heating coil and the cooling coil), then it will be more difficult to detect a leaking heating valve without a physical inspection. Why would one of the air temperature sensors be missing? Sensors that are <em>not required</em> to control the discharge air temperature and pressure may be omitted so as to reduce the initial cost of the air handler. Such cost cutting can be expensive in the long run because problems such as leaking valves can result in a substantial amount of wasted energy before they are eventually discovered and repaired.</p><p>But even if the necessary sensors are in place, reason #2 comes into play: building automation systems are not programmed to detect many important types of faults or to determine the root cause of those faults. To address the need for better system performance analysis, several companies (including my employer, Cimetrics) have developed HVAC analytics software that can perform the fault detection, diagnosis and performance analysis that few building automation systems can do, and the results can be eye-opening to building owners and facility managers.</p><p>Thanks in part to pressure from customers and regulators, manufacturers of HVAC equipment are gradually adding improved fault detection into their products. Studies performed over the past two decades in the United States have clearly demonstrated that air conditioning equipment often have significant problems that can be profitably addressed by appropriate maintenance. The energy savings that can be realized by repairing common problems in air conditioning equipment led the California Energy Commission to require that new air-cooled unitary air conditioning equipment with a capacity of 54,000 Btu per hour or greater sold in California be able to detect and report common economizer faults.</p><p>What I hope that you will take away from this article is the following: <strong>If we improve the transparency of building systems, building owners and facility managers will be able obtain information that will help them to make better decisions about how to operate and maintain those systems. </strong>Before making the decision to reduce project first cost by eliminating sensors from a new building automation system, building owners should discuss the benefits of those sensors for fault detection and problem diagnosis with their consulting engineer.</p><p>Here are two related articles from the New Deal blog:</p><p><a href="https://newdeal.blog/using-data-to-improve-facility-operations-78bb1d1b0580">Using Data to Improve Facility Operations</a>, by John Petze.</p><p><a href="https://newdeal.blog/the-new-deal-building-blocks-395c891fa6dc">Building Blocks for the New Deal</a>, by Jim Lee.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=36cecdf0cd71" width="1" height="1" alt=""><hr><p><a href="https://medium.com/new-deal/what-your-building-isnt-telling-you-36cecdf0cd71">What Your Building Isn’t Telling You</a> was originally published in <a href="https://medium.com/new-deal">A New Deal for Buildings</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[BACnet — A Foundation for Building Analytics]]></title>
            <link>https://medium.com/new-deal/bacnet-a-foundation-for-building-analytics-16ee91d9aaa3?source=rss-c5fe3c4d1b58------2</link>
            <guid isPermaLink="false">https://medium.com/p/16ee91d9aaa3</guid>
            <category><![CDATA[building]]></category>
            <category><![CDATA[analytics]]></category>
            <category><![CDATA[iot]]></category>
            <dc:creator><![CDATA[Jim Butler]]></dc:creator>
            <pubDate>Fri, 30 Jun 2017 14:02:17 GMT</pubDate>
            <atom:updated>2017-06-30T14:02:17.385Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cAMVR_5iMtydrMmKLMnwrA.png" /></figure><p>Since its approval as an ANSI/ASHRAE standard in 1995 and as an ISO standard in 2003, BACnet has become the most common network protocol in modern building automation systems. Although BACnet was not originally designed to enable analytics, it has a number of features that have facilitated the implementation of analytics applications, not the least of which is that BACnet offers a standard method for third-party analytics applications to access data in building systems. However, this article focuses on other features of BACnet that help building owners to implement analytics in their facilities.</p><p>John Petze’s recent article <a href="https://newdeal.blog/introduction-to-project-haystack-3dce54f90b1d">Introduction to Project Haystack</a> described two activities that are a starting point for the implementation of analytics in a building system:</p><p>1. Understanding the meaning of your data</p><p>2. Documenting your understanding using semantic tags</p><p>The good news is that BACnet has capabilities that can help you to understand the data present in a building automation system and then to document the data points within your automation systems in an open fashion.</p><h3>A Brief Review of BACnet Objects and Services</h3><p>Data in BACnet-compliant devices are contained in BACnet objects. As an example, a BACnet Analog Input object represents a physical analog input in a building automation device. Each BACnet object contains a number of properties, each of which contains data or metadata. In the case of a BACnet Analog Input object, the value associated with the physical analog input is stored in the Present_Value property, and properties such as Object_Name, Engineering_Units, and Status_Flags contain metadata. Each BACnet object type (such as Analog Input) has several properties that are required to be present in every object of that type and other properties that are optionally present in an object of that type.</p><p>BACnet objects are accessed using BACnet services, which you could think of as APIs that trigger the transmission of messages on the network. Fundamental BACnet services include Read Property, used to read the value of a property of a BACnet object, and Write Property, used to modify the value of a property of a BACnet object.</p><h3>Semantic Tags in BACnet Objects</h3><p>Yes, BACnet objects can contain semantic tags! This feature was added to BACnet in 2016. Each BACnet object may contain a new BACnet property which contains a list of tags, each tag consisting of a character string and, in some cases, a value associated the character string. Tags will be assigned by the product manufacturer, the controls contractor, and/or the facilities engineering and maintenance staff.</p><p>Here is an example of a set of tags that could be attached to a BACnet object that represents the value read from an air temperature sensor: “sensor”, “air”, “temperature”, “measuredValue”, and “status”. By combining tags in this manner, it will be possible for analytical applications to answer questions such as the following: “Which room air temperature sensors were reading a value greater than 75 degrees F at any time from 8 a.m. until 6 p.m. yesterday?”</p><p>A common misconception is that BACnet will only support BACnet-specific semantic tags. The reality is that BACnet objects can contain almost any semantic tags that can be represented as character strings, including Haystack tags. In fact, ASHRAE has not yet defined any semantic tags in a published standard. It seems likely that many BAS manufacturers and software vendors will define their own proprietary tag sets which will be used in combination with tag sets defined by industry groups.</p><h3>Are we there yet?</h3><p>Just as BACnet provides functionality that enables open communication within and between automation systems, metadata that enable analytics can be made easily accessible to third-party applications using BACnet. With a better understanding of the value of well designed metadata, building owners will be able to make decisions that will allow them to use the growing number of analytical services and tools that can unlock additional value from their building systems.</p><p>BACnet has been successfully applied in building control applications for two decades. Now that there is also a solid foundation for analytics within BACnet, it is time for industry to leverage this foundation to enable the widespread deployment of rich analytical applications.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=16ee91d9aaa3" width="1" height="1" alt=""><hr><p><a href="https://medium.com/new-deal/bacnet-a-foundation-for-building-analytics-16ee91d9aaa3">BACnet — A Foundation for Building Analytics</a> was originally published in <a href="https://medium.com/new-deal">A New Deal for Buildings</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>