Abstract: An approach for control of users relative to access to controllers of a site in a hierarchy of controllers and building equipment. When a user of a customer has established a read write connection to a site controller, the customer does not necessarily want any subsequent user to establish a read write connection to the site controller or another controller within the same site and also make changes, for example, to settings of building equipment. Thus, a subsequent user may be allowed a read only connection and just be able to view building equipment information. When the first user has disconnected either intentionally or by inactivity, the site controller may be cleared allowing a subsequent user to obtain a read write connection. If the first user is inactive but fails to disconnect from the controller, an auto log-off provision may disconnect the user after a specified period of inactivity.

Abstract: An approach for control of users relative to access to controllers of a site in a hierarchy of controllers and building equipment. When a user of a customer has established a read write connection to a site controller, the customer does not necessarily want any subsequent user to establish a read write connection to the site controller or another controller within the same site and also make changes, for example, to settings of building equipment. Thus, a subsequent user may be allowed a read only connection and just be able to view building equipment information. When the first user has disconnected either intentionally or by inactivity, the site controller may be cleared allowing a subsequent user to obtain a read write connection. If the first user is inactive but fails to disconnect from the controller, an auto log-off provision may disconnect the user after a specified period of inactivity.

Abstract: An approach for control of users relative to access to controllers of a site in a hierarchy of controllers and building equipment. When a user of a customer has established a read write connection to a site controller, the customer does not necessarily want any subsequent user to establish a read write connection to the site controller or another controller within the same site and also make changes, for example, to settings of building equipment. Thus, a subsequent user may be allowed a read only connection and just be able to view building equipment information. When the first user has disconnected either intentionally or by inactivity, the site controller may be cleared allowing a subsequent user to obtain a read write connection. If the first user is inactive but fails to disconnect from the controller, an auto log-off provision may disconnect the user after a specified period of inactivity.

Abstract: An approach for managing distribution of automated demand response events in a multi-site enterprise. Event distribution may be controlled by an auto demand response gateway. At an enterprise level, the gateway may be implemented as a supervisor service and configured to connect with an auto demand response system. At a site level, event distribution may be managed in several ways. One is that the auto demand response service may be configured to utilize a gateway connection. The auto demand response service's client settings may be modified to select the site's energy management and command system supervisor as a host station. Another way of managing event distribution may incorporate adding auto demand response gateway functionality to the auto demand response service. When the gateway functionality is enabled, the auto demand response service may route events to other energy management and command system site controllers within a facility.

Abstract: An approach for control of users relative to access to controllers of a site in a hierarchy of controllers and building equipment. When a user of a customer has established a read write connection to a site controller, the customer does not necessarily want any subsequent user to establish a read write connection to the site controller or another controller within the same site and also make changes, for example, to settings of building equipment. Thus, a subsequent user may be allowed a read only connection and just be able to view building equipment information. When the first user has disconnected either intentionally or by inactivity, the site controller may be cleared allowing a subsequent user to obtain a read write connection. If the first user is inactive but fails to disconnect from the controller, an auto log-off provision may disconnect the user after a specified period of inactivity.

Abstract: An approach for management and monitoring of auto demand response in a multi-site enterprise. It may provide awareness of upcoming demand response events, monitoring actual responses to demand response events, analysis of energy management and command system performance, an ability to opt-out of a demand response event, and management and control of the demand response strategy. At the enterprise level, an auto demand response supervisor may add management and monitoring functionality. Added capabilities may incorporate message exchanging with the site-level auto demand response service, support for user interfaces that allow event monitoring and enable management actions such as opting-out of an event. At the site level, functionality may be an extension to the auto demand response service.

Abstract: An approach for normalizing automated demand response events in energy management and control systems. The normalizing may be of events having disparate communication protocols and data formats. There may be a processing engine for each unique protocol or data format. When event data are received, they may be normalized into a standard format which can be utilized by an energy management and control system to initiate a pre-programmed demand response strategy. In other words, using an auto demand response service with its normalized event information, standard response strategies may be developed. The auto demand response service and standard strategies may then be deployed across an entire multi-site enterprise regardless of the auto demand response service provider servicing a particular site. There appears no need to modify the demand response strategy because the auto demand response service may handle a transformation of the auto demand response system's event data.

Abstract: An approach for normalizing automated demand response events in energy management and control systems. The normalizing may be of events having disparate communication protocols and data formats. There may be a processing engine for each unique protocol or data format. When event data are received, they may be normalized into a standard format which can be utilized by an energy management and control system to initiate a pre-programmed demand response strategy. In other words, using an auto demand response service with its normalized event information, standard response strategies may be developed. The auto demand response service and standard strategies may then be deployed across an entire multi-site enterprise regardless of the auto demand response service provider servicing a particular site. There appears no need to modify the demand response strategy because the auto demand response service may handle a transformation of the auto demand response system's event data.

Abstract: An approach for management and monitoring of auto demand response in a multi-site enterprise. It may provide awareness of upcoming demand response events, monitoring actual responses to demand response events, analysis of energy management and command system performance, an ability to opt-out of a demand response event, and management and control of the demand response strategy. At the enterprise level, an auto demand response supervisor may add management and monitoring functionality. Added capabilities may incorporate message exchanging with the site-level auto demand response service, support for user interfaces that allow event monitoring and enable management actions such as opting-out of an event. At the site level, functionality may be an extension to the auto demand response service.

Abstract: An approach for managing distribution of automated demand response events in a multi-site enterprise. Event distribution may be controlled by an auto demand response gateway. At an enterprise level, the gateway may be implemented as a supervisor service and configured to connect with an auto demand response system. At a site level, event distribution may be managed in several ways. One is that the auto demand response service may be configured to utilize a gateway connection. The auto demand response service's client settings may be modified to select the site's energy management and command system supervisor as a host station. Another way of managing event distribution may incorporate adding auto demand response gateway functionality to the auto demand response service. When the gateway functionality is enabled, the auto demand response service may route events to other energy management and command system site controllers within a facility.