US20160321061A1 - System and approach to manage versioning of field devices in a multi-site enterprise - Google Patents
System and approach to manage versioning of field devices in a multi-site enterprise Download PDFInfo
- Publication number
- US20160321061A1 US20160321061A1 US15/207,294 US201615207294A US2016321061A1 US 20160321061 A1 US20160321061 A1 US 20160321061A1 US 201615207294 A US201615207294 A US 201615207294A US 2016321061 A1 US2016321061 A1 US 2016321061A1
- Authority
- US
- United States
- Prior art keywords
- new version
- firmware
- version firmware
- field devices
- versioning
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Abandoned
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/65—Updates
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/65—Updates
- G06F8/654—Updates using techniques specially adapted for alterable solid state memories, e.g. for EEPROM or flash memories
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
- G06F8/71—Version control; Configuration management
Definitions
- the present disclosure pertains to management of devices and particularly to versioning the devices. More particularly, the disclosure pertains to management and versioning the devices in a multi-site environment.
- the disclosure reveals an energy management and control system that may manage versioning firmware for devices.
- the system may be structured in a hierarchy of enterprise, site and field levels, with one or more computing platforms at the various levels.
- An enterprise supervisor may detect and obtain new version firmware for the devices at the field level.
- the new version firmware may be transferred from the supervisor to one or more site controllers.
- the one or more site controllers may transfer the new version firmware to eligible field devices.
- the devices may report to their respective site controllers a status of a transfer of the new version firmware.
- the site controllers may report to the supervisor the status of the transfer. Detection of new version firmware may be automatic. Transfer of the new version firmware to virtually all of the eligible devices may be automatic.
- FIG. 1 is a diagram of an energy management and control system hierarchy
- FIG. 2 is a diagram of a relationship between an enterprise supervisor and site-level controllers
- FIG. 3 is a diagram of a field device versioning process flow
- FIG. 4 is a diagram of another field device versioning process flow.
- the present system and approach may incorporate one or more processors, computers, controllers, user interfaces, wireless and/or wire connections, and/or the like, wherever desired.
- An energy management and control system may be a three-tier hierarchy with enterprise, site and field levels.
- Computing platforms computers/controllers
- applications specific to the functionality required at that level.
- the EMCS may consist of numerous devices, each of which performs a specific function. These devices might be, for example, simple input/output modules (IOMs), electronic thermostats (ETMs) that control rooftop heating, ventilation and air conditioning (HVAC) units, lighting control units (LCUs) that manage a building's interior and exterior lights, and/or other kinds of devices. Additionally, each controller type may be comprised of various models; ETM-1, ETM-2 and ETM-3 might be models of ETMs that are differentiated by unique features and/or functions.
- IOMs simple input/output modules
- ETMs electronic thermostats
- HVAC rooftop heating, ventilation and air conditioning
- LCUs lighting control units
- each controller type may be comprised of various models
- ETM-1, ETM-2 and ETM-3 might be models of ETMs that are differentiated by unique features and/or functions.
- Each field device in an EMCS may contain a program (or firmware) which controls that device's functionality.
- Virtually all controllers of a particular model, ETM-1s for example, may execute the same version of firmware.
- new firmware versions may be transferred to each controller. Placing another version of firmware in place of firmware in a controller or that of a field device may be regarded as “versioning”.
- field device versioning may be a manual process. One may manually connect to each site and initiate a firmware update for each field device needing a new version. When a particular model of controller needs to have its firmware updated, the effort of versioning may be complex, costly and time-consuming.
- an EMCS might consist of a few or several dozen controllers. While a small footprint building may have only ten ETMs, and a few IOMs and LCUs, a larger building may have thirty ETMs, and a dozen IOMs and LCUs.
- controllers that should be managed may greatly increase.
- a single site may have only ten to thirty ETM-1 controllers; however, an enterprise with hundreds of sites may need to manage thousands of ETM-1s. If the enterprise has over a thousand sites, the controller count may be in the tens of thousands.
- the present system and approach may manage the task of deploying firmware versions to controllers in a multi-site enterprise.
- the issues of time, cost and complexity may be addressed by distributing and automating the tasks associated with version management across the enterprise hierarchy.
- the enterprise supervisor, controller or computer may provide a versioning service which manages the field device versioning process. It may provide a user interface for the versioning service which allows a user to configure, manage and monitor the versioning process. It may provide a query mechanism to determine the field device inventory of each site.
- the enterprise may have a capability to automatically detect when a firmware file containing a new version of the program for a particular model of field device is placed on the enterprise and may initiate the file transfer process.
- the enterprise may transfer a firmware file to each site at which at least one compatible device model is installed.
- the enterprise may receive updates from each site about the progress/status of the transfer process.
- the site controller may respond to an enterprise query for the site controller's field device inventory.
- the site controller may receive a firmware file from the enterprise.
- the site controller may automatically initiate and manage the process of transferring a firmware file to each compatible field device.
- the site controller may report the progress/status of the transfer process to the enterprise.
- the field device may receive a firmware file from the site controller.
- the field device may report the progress/status of the transfer process to the site controller.
- the enterprise level may be a centralized application which manages and monitors the control system at multiple, remote sites.
- a site may have one or more site controllers which manage, control, and monitor one or more networks of field devices.
- the field device may typically be designed to control a piece of EMCS equipment. Other uses may include control of indoor and outdoor lights, control of signage, and more.
- the present system and approach may have enhanced functionality at each level of the EMCS.
- the enterprise may have a versioning service added to an enterprise application. This service may coordinate virtually all activities related to versioning of field devices.
- the service may provide a user interface which allows the user to configure the service's behavior and monitor versioning activities.
- a query mechanism may interrogate each site in the enterprise to obtain a field device inventory from each site controller. This inventory may then be available to the user interface allowing the user to view and manage the installed base of field devices.
- the user may modify versioning behavior at the enterprise, site, site controller, or field device level; for instance, enabling the services ability to automatically detect the presence of a new firmware file and initiate the file transfer process, enabling or disabling the automatic firmware upgrade functionality of one or more specific sites, site controllers, and/or field device types.
- a firmware file may be saved to a specific subdirectory on the computer's file system. Based on the configuration of the versioning service, the enterprise application may monitor that subdirectory for the presence of a new file. When a new file is detected, the enterprise application may initiate the file transfer process. Alternately, the file transfer process may be initiated manually through the application's user interface.
- the firmware file may be parsed to determine the target field device model. Each site in the enterprise may then be scanned, depending on the site-specific configuration, to locate sites at which the particular field device is installed. When a qualifying site is found, the firmware file may be transferred to the appropriate site controller. This transfer process may begin with the enterprise application notifying the site controller with a “start of file transfer” message. Once the site controller acknowledges the message, the enterprise application may transfer the file according to the enterprise-to-site communications protocol.
- the enterprise application may execute a monitoring process which receives progress/status updates from the site controllers as the firmware file is being received and the field devices are being updated.
- the monitoring process may maintain a user interface which displays the current progress and/or status of the firmware upgrade activities.
- the versioning service may maintain a history of upgrade activity for each field device.
- the site controller may prepare a location on its local file store (or comparable storage medium) to save the incoming file.
- the site controller may receive the file according to an enterprise-to-site communications protocol and save the file.
- the site controller may update the enterprise application with progress and/or status information.
- the site controller may parse the firmware file to determine the target field device model. The site controller may then scan its device network or networks to locate compatible field devices. When a qualifying field device is found, the site controller may flag that device as needing a firmware upgrade.
- the site controller may use a polling mechanism to schedule communications with its one or more networks of field devices. As each device gets a turn, the polling task may check if the device has been flagged for a firmware upgrade. Following the site controller-to-field device communications protocol, the firmware file may be transmitted to the field device. During the upgrade process, the site controller may receive progress and/or status updates from the field device and communicate those updates to the enterprise application.
- the device may prepare, according to its device specification, for a firmware upgrade.
- the device may receive and process the new program according to its device specification; these details may incorporate where and/or how the new version is saved during the upgrade and the mechanism for replacing the current application with the new version. As the firmware upgrade process occurs, the device may update the site controller with progress/status information.
- FIG. 1 is a diagram of the energy management and control system hierarchy with example sites.
- An enterprise supervisor 12 may be connected with a number (n) of sites 13 , 14 and 15 . Although three sites are shown, there may be more or fewer sites.
- Site 13 may have one or more site-level controllers or site supervisors 16 , connected with enterprise supervisor 12 , and one or more field devices 17 connected with a site controller 16 .
- site 13 , 14 , and 15 may be in San Francisco, San Antonio and Cleveland, respectively.
- Sites 14 and 15 may have the same structure and items as site 13 .
- FIG. 2 is a block diagram of enterprise supervisor 12 and its site-level controllers 16 .
- the blocks within the block representing enterprise supervisor 12 may indicate a versioning service 40 , an enterprise data model, a web server, alarm management, history management and batch services. There may be additional blocks indicating other items relative to enterprise supervisor 12 .
- a block representing each site level controller 16 may contain blocks indicating a versioning service 50 , site data model, a web server, alarm management, history management, and device control and demand response strategies. There may be additional blocks indicating other items relative to site level controller 16 .
- FIG. 3 is a diagram 30 representing an example of a field device versioning process flow along with components of the energy management and control system.
- Enterprise supervisor 12 and site controller 16 may incorporate a versioning service 40 and 50 , respectively.
- Components of versioning service 40 of supervisor 12 may incorporate a versioning service user interface 21 , a query engine 22 , a versioning job processor 23 and a file transfer engine 24 .
- Components of versioning service 50 of site controller 16 may incorporate a query engine 32 , a versioning job processor 33 , a file transfer engine 34 and a file transfer manager 35 .
- Site controller 16 may also incorporate a communication engine 36 .
- An enterprise manager 41 may provide direction and information to user interface 21 .
- manager 41 may load a new version firmware file via a user interface.
- the firmware is an example file.
- Another file or information may be loaded.
- Manager 41 may configure and initiate a version deployment job.
- Supervisor 12 may query a site 13 , 14 or 15 for a device 17 inventory.
- site 13 may be considered as an example.
- the query may be via a connection 38 between query engines 22 and 32 .
- Versioning job processor 23 of supervisor 12 may initiate a firmware file transfer from supervisor 12 to site 13 via a connection 39 between job processor 23 and file transfer engine 24 .
- Versioning service 40 of supervisor 12 may update the versioning service 50 of site 13 with versioning job details along a connection 42 between versioning job processor 23 of supervisor 12 and versioning job processor 33 of site controller 16 .
- the firmware file may be transferred from supervisor 12 to site 13 via a connection 43 between file transfer engine 24 and file transfer engine 34 .
- Site 13 may receive the firmware file at file transfer engine 34 and save the firmware file to a local file store.
- Site 13 may update supervisor 12 with firmware file transfer status via connection 43 .
- Versioning job processor 33 at site 13 may update file transfer manager 35 with needed transfer tasks via a connection 44 between versioning job processor 33 and file transfer manager 35 .
- File transfer manager 35 may interact with file transfer engine 34 via a connection 45 to download the firmware file to the appropriate devices 17 via a connection 47 from a communication engine 36 .
- Communication engine 36 may incorporate protocol stacks, encode/decode logic, and so forth.
- the one or more field devices 17 may receive the firmware file and report a status to site controller 16 via connection 47 between communication engine 36 and the one or more field devices 17 .
- File transfer manager 35 may update versioning job processor 33 of site 13 via connection 44 with a current status of the firmware file transfer operations.
- Versioning service 50 of site 13 may update versioning service 40 of supervisor 12 with a versioning job status via connection 42 between versioning job processor 33 and versioning job processor 23 .
- Job processor 23 of supervisor 12 may update a versioning history log with the versioning job status.
- Enterprise manager 41 may monitor progress and status of the deployment job of the firmware file via the versioning service user interface 21 of supervisor 12 .
- FIG. 4 is a diagram 60 representing another example of a field device versioning process flow along with components of the energy management and control system.
- Diagram 60 may differ from diagram 30 of FIG. 3 relative to a flow process. The components may be similar or the same among the diagrams.
- enterprise manager 41 may configure an “automated job” of versioning service 40 of supervisor 12 via user interface 21 .
- Manager 41 may specify the enterprise, site, site controller and field device behavior also via interface 21 .
- Manager 41 may enable an “auto-detect” of a firmware file.
- Supervisor 12 may query site 13 for a field device 17 inventory via query engines 22 and 32 with connection 38 .
- Manager 41 may load a new version firmware file via interface 21 .
- Versioning service 40 of supervisor 12 may auto-detect a new firmware file and launch a versioning job. From here on, the flow process and structure of diagram 60 may appear similar to that of diagram 30 .
- an energy management and control system may incorporate a supervisor controller having a first versioning service component, one or more site controllers, having a second versioning service component, connected to the supervisor controller, and one or more field devices, having firmware, connected to the one or more site controllers.
- the first versioning service component may have a configuration that enables automatic detection by the supervisor controller of new version firmware.
- a query may be made by the first versioning service component to the second versioning service component for an inventory of the one or more field devices to determine which field devices, if any, are appropriate for receipt of the new version firmware.
- the first versioning service component may launch a versioning job process and transfer the new version firmware to the second versioning service component to continue the versioning job process.
- the versioning job process may incorporate installing the new version firmware in the one or more field devices determined as appropriate for receipt of the new version firmware.
- the first versioning component may incorporate a user interface.
- a user may provide, via the user interface, the configuration to the first versioning service component that enables automatic detection by the supervisor controller of the new version firmware.
- a field device appropriate for receipt of the new version firmware may have a present version firmware which is upgradeable or replaceable with the new version firmware.
- the field device, appropriate for receipt of the new version firmware may report to a site controller a status of a transfer of the new version firmware.
- a site controller may report a status of transfer operations of the new version firmware to the first versioning service component so that a user can monitor the status and progress of the transfer operations via the user interface.
- the job process may automatically continue until virtually all of the one or more field devices determined as appropriate for receipt of the new version firmware, have been installed with the new version firmware unless interrupted by a user via a user interface to the system.
- An energy management and control system having a mechanism for versioning firmware of field devices may incorporate an enterprise supervisor, one or more site controllers connected to the enterprise supervisor, and one or more field devices connected to the one or more site controllers.
- the one or more field devices may incorporate firmware that controls an operation of the one or more field devices, respectively.
- the enterprise supervisor may detect new version firmware for one or more field devices.
- the enterprise supervisor may query the one or more site controllers for an inventory of appropriate field devices qualified to receive the new version firmware.
- the enterprise supervisor may transfer the new version firmware to the one or more site controllers.
- the new version firmware may be transferred by the one or more site controllers to virtually all of the appropriate field devices.
- a transfer of the new version firmware may replace or upgrade the firmware in the appropriate field devices.
- the enterprise supervisor may incorporate a versioning service that detects the new version firmware.
- the versioning service may provide information about receipt and transfer of new version software to a versioning history log.
- the one or more site controllers may update the enterprise supervisor with a status of a transfer of the new version firmware.
- the new version firmware may then be automatically transferred to the appropriate field devices.
- An energy management and control system may incorporate a supervisor having a first versioning service component, at least one site controller, connected to the supervisor, having a second versioning service component, and one or more field devices connected to the at least one site controller.
- the first versioning service component may be loaded with new version firmware.
- the new version firmware may be transferred by the first versioning service component to the second versioning service component.
- the second versioning service component may transfer the new version firmware to replace or upgrade firmware in the one or more field devices.
- the first versioning service component may incorporate a user interface, a first query engine, a first file transfer engine, and a first versioning job processor connected to the first file transfer engine.
- the second versioning service component may incorporate a second query engine connected to the first query engine, a second file transfer engine connected to the first file transfer engine, a second versioning job processor connected to the first versioning job processor, and a file transfer manager connected to the second versioning job processor and the second file transfer engine.
- the second file transfer engine may receive the new version firmware and save the new version firmware to a file store.
- the file transfer manager may download the new version firmware from the second file transfer engine and/or the file store, and download the new version firmware to an appropriate field device or field devices of the one or more field devices.
- the second versioning job processor may update the file transfer manager about transfer tasks.
- the second query engine may respond to one or more queries from the first query engine regarding an inventory of the one or more field devices to determine the appropriate field device or field devices.
- An appropriate field device may be a device that has a present version firmware that is replaceable or upgradeable with the new version firmware.
- the file transfer manager may further update the second versioning job processor with a current status of transfer operations of the new version firmware to the appropriate field device or field devices.
- the site controller may incorporate a communication engine that receives the new version firmware from the second transfer engine and transfers the new version firmware to the appropriate field device or field devices.
- the one or more field devices may report a new version firmware status to the site controller via the communication engine.
- the one or more field devices may incorporate input/output modules, electronic thermostats, and/or lighting control units.
- the one or more field devices may incorporate one or more model types.
- Firmware for one model type may be different than firmware for another model type.
- the new version firmware may be an acceptable version for firmware of just one model type of field devices.
- a user interface may permit a user to load the new version firmware, configure and initiate a deployment job for the new version firmware, and monitor the deployment job.
- the first versioning job processor may initiate a transfer of the new version firmware from the supervisor to the at least one site controller, and update a history log of a versioning job status.
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Computer Security & Cryptography (AREA)
- Stored Programmes (AREA)
Abstract
An energy management and control system that may manage versioning firmware for devices. The system may be structured in a hierarchy of enterprise, site and field levels, with one or more computing platforms at the various levels. An enterprise supervisor may detect and obtain new version firmware for the devices at the field level. The new version firmware may be transferred from the supervisor to one or more site controllers. The one or more site controllers may transfer the new version firmware to eligible field devices. The devices may report to their respective site controllers a status of a transfer of the new version hardware. The site controllers may report to the supervisor the status of the transfer. Detection of new version firmware may be automatic. Transfer of the new version firmware to virtually all of the eligible devices may be automatic.
Description
- This present application is a Continuation of U.S. patent application Ser. No. 13/689,551, filed Nov. 29, 2012. U.S. patent application Ser. No. 13/689,551, filed Nov. 29, 2012, is hereby incorporated by reference.
- The present disclosure pertains to management of devices and particularly to versioning the devices. More particularly, the disclosure pertains to management and versioning the devices in a multi-site environment.
- The disclosure reveals an energy management and control system that may manage versioning firmware for devices. The system may be structured in a hierarchy of enterprise, site and field levels, with one or more computing platforms at the various levels. An enterprise supervisor may detect and obtain new version firmware for the devices at the field level. The new version firmware may be transferred from the supervisor to one or more site controllers. The one or more site controllers may transfer the new version firmware to eligible field devices. The devices may report to their respective site controllers a status of a transfer of the new version firmware. The site controllers may report to the supervisor the status of the transfer. Detection of new version firmware may be automatic. Transfer of the new version firmware to virtually all of the eligible devices may be automatic.
-
FIG. 1 is a diagram of an energy management and control system hierarchy; -
FIG. 2 is a diagram of a relationship between an enterprise supervisor and site-level controllers; -
FIG. 3 is a diagram of a field device versioning process flow; and -
FIG. 4 is a diagram of another field device versioning process flow. - The present system and approach, as described herein and/or shown in the Figures, may incorporate one or more processors, computers, controllers, user interfaces, wireless and/or wire connections, and/or the like, wherever desired.
- An energy management and control system (EMCS) may be a three-tier hierarchy with enterprise, site and field levels. Computing platforms (computers/controllers) at each level may execute applications specific to the functionality required at that level.
- At the field level, the EMCS may consist of numerous devices, each of which performs a specific function. These devices might be, for example, simple input/output modules (IOMs), electronic thermostats (ETMs) that control rooftop heating, ventilation and air conditioning (HVAC) units, lighting control units (LCUs) that manage a building's interior and exterior lights, and/or other kinds of devices. Additionally, each controller type may be comprised of various models; ETM-1, ETM-2 and ETM-3 might be models of ETMs that are differentiated by unique features and/or functions.
- Each field device in an EMCS may contain a program (or firmware) which controls that device's functionality. Virtually all controllers of a particular model, ETM-1s for example, may execute the same version of firmware. As new features and functions are developed, or as bugs are fixed, new firmware versions may be transferred to each controller. Placing another version of firmware in place of firmware in a controller or that of a field device may be regarded as “versioning”.
- In the related art, field device versioning may be a manual process. One may manually connect to each site and initiate a firmware update for each field device needing a new version. When a particular model of controller needs to have its firmware updated, the effort of versioning may be complex, costly and time-consuming.
- Depending on a building's size, an EMCS might consist of a few or several dozen controllers. While a small footprint building may have only ten ETMs, and a few IOMs and LCUs, a larger building may have thirty ETMs, and a dozen IOMs and LCUs.
- As the scale of a multi-site enterprise increases, the number of controllers that should be managed may greatly increase. A single site may have only ten to thirty ETM-1 controllers; however, an enterprise with hundreds of sites may need to manage thousands of ETM-1s. If the enterprise has over a thousand sites, the controller count may be in the tens of thousands.
- The present system and approach may manage the task of deploying firmware versions to controllers in a multi-site enterprise. The issues of time, cost and complexity may be addressed by distributing and automating the tasks associated with version management across the enterprise hierarchy.
- The tasks, or responsibilities, at the various levels of the hierarchy may be noted in the following. The enterprise supervisor, controller or computer (enterprise) may provide a versioning service which manages the field device versioning process. It may provide a user interface for the versioning service which allows a user to configure, manage and monitor the versioning process. It may provide a query mechanism to determine the field device inventory of each site. The enterprise may have a capability to automatically detect when a firmware file containing a new version of the program for a particular model of field device is placed on the enterprise and may initiate the file transfer process. The enterprise may transfer a firmware file to each site at which at least one compatible device model is installed. The enterprise may receive updates from each site about the progress/status of the transfer process.
- The site controller may respond to an enterprise query for the site controller's field device inventory. The site controller may receive a firmware file from the enterprise. The site controller may automatically initiate and manage the process of transferring a firmware file to each compatible field device. The site controller may report the progress/status of the transfer process to the enterprise.
- The field device may receive a firmware file from the site controller. The field device may report the progress/status of the transfer process to the site controller.
- The enterprise level may be a centralized application which manages and monitors the control system at multiple, remote sites. A site may have one or more site controllers which manage, control, and monitor one or more networks of field devices. The field device may typically be designed to control a piece of EMCS equipment. Other uses may include control of indoor and outdoor lights, control of signage, and more.
- The present system and approach may have enhanced functionality at each level of the EMCS. The enterprise may have a versioning service added to an enterprise application. This service may coordinate virtually all activities related to versioning of field devices. The service may provide a user interface which allows the user to configure the service's behavior and monitor versioning activities. A query mechanism may interrogate each site in the enterprise to obtain a field device inventory from each site controller. This inventory may then be available to the user interface allowing the user to view and manage the installed base of field devices. The user may modify versioning behavior at the enterprise, site, site controller, or field device level; for instance, enabling the services ability to automatically detect the presence of a new firmware file and initiate the file transfer process, enabling or disabling the automatic firmware upgrade functionality of one or more specific sites, site controllers, and/or field device types.
- A firmware file (firmware) may be saved to a specific subdirectory on the computer's file system. Based on the configuration of the versioning service, the enterprise application may monitor that subdirectory for the presence of a new file. When a new file is detected, the enterprise application may initiate the file transfer process. Alternately, the file transfer process may be initiated manually through the application's user interface.
- The firmware file may be parsed to determine the target field device model. Each site in the enterprise may then be scanned, depending on the site-specific configuration, to locate sites at which the particular field device is installed. When a qualifying site is found, the firmware file may be transferred to the appropriate site controller. This transfer process may begin with the enterprise application notifying the site controller with a “start of file transfer” message. Once the site controller acknowledges the message, the enterprise application may transfer the file according to the enterprise-to-site communications protocol.
- The enterprise application may execute a monitoring process which receives progress/status updates from the site controllers as the firmware file is being received and the field devices are being updated. The monitoring process may maintain a user interface which displays the current progress and/or status of the firmware upgrade activities.
- In conjunction with the field device inventory, the versioning service may maintain a history of upgrade activity for each field device. When the site controller receives a “start of file transfer” message from the enterprise application, the site controller may prepare a location on its local file store (or comparable storage medium) to save the incoming file. The site controller may receive the file according to an enterprise-to-site communications protocol and save the file. As the file is received, the site controller may update the enterprise application with progress and/or status information.
- At the end of the file transfer, the site controller may parse the firmware file to determine the target field device model. The site controller may then scan its device network or networks to locate compatible field devices. When a qualifying field device is found, the site controller may flag that device as needing a firmware upgrade.
- The site controller may use a polling mechanism to schedule communications with its one or more networks of field devices. As each device gets a turn, the polling task may check if the device has been flagged for a firmware upgrade. Following the site controller-to-field device communications protocol, the firmware file may be transmitted to the field device. During the upgrade process, the site controller may receive progress and/or status updates from the field device and communicate those updates to the enterprise application.
- When a field device receives a “start of firmware upgrade” message from the site controller, the device may prepare, according to its device specification, for a firmware upgrade.
- The device may receive and process the new program according to its device specification; these details may incorporate where and/or how the new version is saved during the upgrade and the mechanism for replacing the current application with the new version. As the firmware upgrade process occurs, the device may update the site controller with progress/status information.
-
FIG. 1 is a diagram of the energy management and control system hierarchy with example sites. Anenterprise supervisor 12 may be connected with a number (n) ofsites Site 13 may have one or more site-level controllers orsite supervisors 16, connected withenterprise supervisor 12, and one ormore field devices 17 connected with asite controller 16. As examples,site Sites 14 and 15 may have the same structure and items assite 13. -
FIG. 2 is a block diagram ofenterprise supervisor 12 and its site-level controllers 16. The blocks within the block representingenterprise supervisor 12 may indicate aversioning service 40, an enterprise data model, a web server, alarm management, history management and batch services. There may be additional blocks indicating other items relative toenterprise supervisor 12. - A block representing each
site level controller 16 may contain blocks indicating aversioning service 50, site data model, a web server, alarm management, history management, and device control and demand response strategies. There may be additional blocks indicating other items relative tosite level controller 16. -
FIG. 3 is a diagram 30 representing an example of a field device versioning process flow along with components of the energy management and control system.Enterprise supervisor 12 andsite controller 16 may incorporate aversioning service versioning service 40 ofsupervisor 12 may incorporate a versioningservice user interface 21, aquery engine 22, aversioning job processor 23 and afile transfer engine 24. - Components of
versioning service 50 ofsite controller 16 may incorporate aquery engine 32, aversioning job processor 33, afile transfer engine 34 and afile transfer manager 35.Site controller 16 may also incorporate acommunication engine 36. - An
enterprise manager 41 may provide direction and information touser interface 21. For instance,manager 41 may load a new version firmware file via a user interface. The firmware is an example file. Another file or information may be loaded.Manager 41 may configure and initiate a version deployment job.Supervisor 12 may query asite device 17 inventory. For illustrative purposes,site 13 may be considered as an example. The query may be via aconnection 38 betweenquery engines job processor 23 ofsupervisor 12 may initiate a firmware file transfer fromsupervisor 12 tosite 13 via a connection 39 betweenjob processor 23 andfile transfer engine 24.Versioning service 40 ofsupervisor 12 may update theversioning service 50 ofsite 13 with versioning job details along aconnection 42 betweenversioning job processor 23 ofsupervisor 12 andversioning job processor 33 ofsite controller 16. The firmware file may be transferred fromsupervisor 12 tosite 13 via aconnection 43 betweenfile transfer engine 24 andfile transfer engine 34.Site 13 may receive the firmware file atfile transfer engine 34 and save the firmware file to a local file store.Site 13 may updatesupervisor 12 with firmware file transfer status viaconnection 43. - Versioning
job processor 33 atsite 13 may updatefile transfer manager 35 with needed transfer tasks via aconnection 44 betweenversioning job processor 33 andfile transfer manager 35.File transfer manager 35 may interact withfile transfer engine 34 via a connection 45 to download the firmware file to theappropriate devices 17 via aconnection 47 from acommunication engine 36.Communication engine 36 may incorporate protocol stacks, encode/decode logic, and so forth. The one ormore field devices 17 may receive the firmware file and report a status tosite controller 16 viaconnection 47 betweencommunication engine 36 and the one ormore field devices 17. -
File transfer manager 35 may updateversioning job processor 33 ofsite 13 viaconnection 44 with a current status of the firmware file transfer operations.Versioning service 50 ofsite 13 may updateversioning service 40 ofsupervisor 12 with a versioning job status viaconnection 42 betweenversioning job processor 33 andversioning job processor 23.Job processor 23 ofsupervisor 12 may update a versioning history log with the versioning job status.Enterprise manager 41 may monitor progress and status of the deployment job of the firmware file via the versioningservice user interface 21 ofsupervisor 12. -
FIG. 4 is a diagram 60 representing another example of a field device versioning process flow along with components of the energy management and control system. Diagram 60 may differ from diagram 30 ofFIG. 3 relative to a flow process. The components may be similar or the same among the diagrams. To start,enterprise manager 41 may configure an “automated job” ofversioning service 40 ofsupervisor 12 viauser interface 21.Manager 41 may specify the enterprise, site, site controller and field device behavior also viainterface 21.Manager 41 may enable an “auto-detect” of a firmware file.Supervisor 12 may querysite 13 for afield device 17 inventory viaquery engines connection 38.Manager 41 may load a new version firmware file viainterface 21.Versioning service 40 ofsupervisor 12 may auto-detect a new firmware file and launch a versioning job. From here on, the flow process and structure of diagram 60 may appear similar to that of diagram 30. - To recap, an energy management and control system may incorporate a supervisor controller having a first versioning service component, one or more site controllers, having a second versioning service component, connected to the supervisor controller, and one or more field devices, having firmware, connected to the one or more site controllers. The first versioning service component may have a configuration that enables automatic detection by the supervisor controller of new version firmware. A query may be made by the first versioning service component to the second versioning service component for an inventory of the one or more field devices to determine which field devices, if any, are appropriate for receipt of the new version firmware. The first versioning service component may launch a versioning job process and transfer the new version firmware to the second versioning service component to continue the versioning job process. The versioning job process may incorporate installing the new version firmware in the one or more field devices determined as appropriate for receipt of the new version firmware.
- The first versioning component may incorporate a user interface. A user may provide, via the user interface, the configuration to the first versioning service component that enables automatic detection by the supervisor controller of the new version firmware.
- A field device appropriate for receipt of the new version firmware may have a present version firmware which is upgradeable or replaceable with the new version firmware. The field device, appropriate for receipt of the new version firmware, may report to a site controller a status of a transfer of the new version firmware.
- A site controller may report a status of transfer operations of the new version firmware to the first versioning service component so that a user can monitor the status and progress of the transfer operations via the user interface.
- When the first versioning service component launches the versioning job process and transfers the new version firmware to the second versioning service component to continue the versioning job process, the job process may automatically continue until virtually all of the one or more field devices determined as appropriate for receipt of the new version firmware, have been installed with the new version firmware unless interrupted by a user via a user interface to the system.
- An energy management and control system having a mechanism for versioning firmware of field devices, may incorporate an enterprise supervisor, one or more site controllers connected to the enterprise supervisor, and one or more field devices connected to the one or more site controllers. The one or more field devices may incorporate firmware that controls an operation of the one or more field devices, respectively.
- The enterprise supervisor may detect new version firmware for one or more field devices. The enterprise supervisor may query the one or more site controllers for an inventory of appropriate field devices qualified to receive the new version firmware. Upon a launch initiated by a user, the enterprise supervisor may transfer the new version firmware to the one or more site controllers. The new version firmware may be transferred by the one or more site controllers to virtually all of the appropriate field devices. A transfer of the new version firmware may replace or upgrade the firmware in the appropriate field devices.
- The enterprise supervisor may incorporate a versioning service that detects the new version firmware. The versioning service may provide information about receipt and transfer of new version software to a versioning history log.
- The one or more site controllers may update the enterprise supervisor with a status of a transfer of the new version firmware.
- Upon transfer the new version firmware to the one or more site controllers, the new version firmware may then be automatically transferred to the appropriate field devices.
- An energy management and control system may incorporate a supervisor having a first versioning service component, at least one site controller, connected to the supervisor, having a second versioning service component, and one or more field devices connected to the at least one site controller.
- The first versioning service component may be loaded with new version firmware. The new version firmware may be transferred by the first versioning service component to the second versioning service component. The second versioning service component may transfer the new version firmware to replace or upgrade firmware in the one or more field devices.
- The first versioning service component may incorporate a user interface, a first query engine, a first file transfer engine, and a first versioning job processor connected to the first file transfer engine.
- The second versioning service component may incorporate a second query engine connected to the first query engine, a second file transfer engine connected to the first file transfer engine, a second versioning job processor connected to the first versioning job processor, and a file transfer manager connected to the second versioning job processor and the second file transfer engine.
- The second file transfer engine may receive the new version firmware and save the new version firmware to a file store. The file transfer manager may download the new version firmware from the second file transfer engine and/or the file store, and download the new version firmware to an appropriate field device or field devices of the one or more field devices. The second versioning job processor may update the file transfer manager about transfer tasks.
- The second query engine may respond to one or more queries from the first query engine regarding an inventory of the one or more field devices to determine the appropriate field device or field devices. An appropriate field device may be a device that has a present version firmware that is replaceable or upgradeable with the new version firmware.
- The file transfer manager may further update the second versioning job processor with a current status of transfer operations of the new version firmware to the appropriate field device or field devices.
- The site controller may incorporate a communication engine that receives the new version firmware from the second transfer engine and transfers the new version firmware to the appropriate field device or field devices. The one or more field devices may report a new version firmware status to the site controller via the communication engine.
- The one or more field devices may incorporate input/output modules, electronic thermostats, and/or lighting control units. The one or more field devices may incorporate one or more model types. Firmware for one model type may be different than firmware for another model type. The new version firmware may be an acceptable version for firmware of just one model type of field devices.
- A user interface may permit a user to load the new version firmware, configure and initiate a deployment job for the new version firmware, and monitor the deployment job. The first versioning job processor may initiate a transfer of the new version firmware from the supervisor to the at least one site controller, and update a history log of a versioning job status.
- In the present specification, some of the matter may be of a hypothetical or prophetic nature although stated in another manner or tense.
- Although the present system and/or approach has been described with respect to at least one illustrative example, many variations and modifications will become apparent to those skilled in the art upon reading the specification. It is therefore the intention that the appended claims be interpreted as broadly as possible in view of the related art to include all such variations and modifications.
Claims (20)
1. An energy management and control system comprising:
a supervisor controller;
one or more site controllers connected to the supervisor controller; and
one or more field devices, each having firmware, connected to at least one of the one or more site controllers; and
wherein:
the supervisor controller is configured to automatically initiate and manage transfer of a new version firmware to the one or more compatible field devices;
the supervisor controller is configured to transfer the new version firmware to the one or more site controllers; and
the one or more site controllers are configured to automatically initiate and manage transfer of the new version firmware to the one or more field devices.
2. The system of claim 1 , wherein the supervisor controller is configured to query the one or more site controllers for an inventor of the one or more field devices to determine which field devices, if any, are appropriate for receipt of the new version firmware.
3. The system of claim 2 , wherein a field device appropriate for receipt of the new version firmware has a present version firmware which is upgradeable or replaceable with the new version firmware.
4. The system of claim 2 , wherein the field device, appropriate for receipt of the new version firmware, reports to a site controller a status of a transfer of the new version firmware.
5. The system of claim 2 , wherein a site controller reports a status of transfer operations of the new version firmware to the supervisor controller so that a user can monitor the status and progress of the transfer operations via the user interface.
6. The system of claim 1 , wherein the one or more site controllers are located at one or more locations removed from the supervisor controller.
7. The system of claim 2 , wherein the site controller is configured to transfer the new version firmware to the one or more site controllers until virtually all of the one or more field devices determined as appropriate for receipt of the new version firmware, have been installed with the new version firmware unless interrupted by a user via a user interface to the system.
8. The system of claim 1 , wherein a user interface permits a user to load the new version firmware, configure and initiate a deployment job for the new version firmware, and monitor the deployment job.
9. An energy management and control system, comprising:
an enterprise supervisor controller including a user interface, the user interface configured to allow a user to configure and monitor a versioning process;
one or more site controllers connected to the enterprise supervisor, the one or more site controller positioned at a remote location from the enterprise supervisor; and
one or more field devices connected to the one or more site controllers; and
wherein:
the one or more field devices comprise firmware that controls an operation of the one or more field devices, respectively;
the enterprise supervisor controller is configured to automatically detect new version firmware for the one or more field devices;
the enterprise supervisor controller is configured to transfer the new version firmware to the one or more site controllers upon user initiation; and
the new version firmware is transferred by the one or more site controllers to virtually all of the appropriate field devices.
10. The system of claim 9 , wherein a transfer of the new version firmware replaces or upgrades the firmware in the appropriate field devices.
11. The system of claim 9 , wherein the enterprise supervisor controller queries the one or more site controllers for an inventory of appropriate field devices qualified to receive the new version firmware.
12. The system of claim 9 , wherein the one or more site controllers update the enterprise supervisor controller with a status of a transfer of the new version firmware.
13. The system of claim 9 , wherein upon transfer of the new version firmware to the one or more site controllers from the enterprise supervisor controller, the new version firmware is then automatically transferred to the appropriate field devices.
14. An energy management and control system comprising:
an enterprise supervisor having a first versioning service component;
at least one site controller connected to the enterprise supervisor, the at least one site controller having a second versioning service component; and
one or more field devices connected to the at least one site controller; and
wherein:
when the first versioning service component detects new version firmware, the first versioning service component configured to automatically initiate and manage transfer of the new version firmware to the second versioning service component; and
the second versioning service component transfers the new version firmware to replace or upgrade firmware in the one or more field devices and updates the enterprise supervisor with a status of a transfer of the new version firmware.
15. The system of claim 14 , wherein the first versioning service is configured to provide information about receipt and transfer of new version software to a versioning history log.
16. The system of claim 14 , wherein the first versioning service component comprises:
a user interface;
a first query engine;
a first file transfer engine; and
a first versioning job processor connected to the first file transfer engine.
17. The system of claim 16 , wherein the second versioning service component comprises:
a second query engine connected to the first query engine;
a second file transfer engine connected to the first file transfer engine;
a second versioning job processor connected to the first versioning job processor; and
a file transfer manager connected to the second versioning job processor and the second file transfer engine.
18. The system of claim 14 , wherein a query is made by the first versioning service component to the second versioning service component for an inventory of the one or more field devices to determine which field devices, if any, are appropriate for receipt of the new version firmware.
19. The system of claim 14 , wherein:
the one or more field devices comprise input/output modules, electronic thermostats, and/or lighting control units;
the one or more field devices comprise one or more model types;
firmware for one model type can be different than firmware for another model type; and
the new version firmware can be an acceptable version for firmware of just one model type of field devices.
20. The system of claim 14 , wherein a user interface permits a user to load the new version firmware, configure and initiate a deployment job for the new version firmware, and monitor the deployment job.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US15/207,294 US20160321061A1 (en) | 2012-11-29 | 2016-07-11 | System and approach to manage versioning of field devices in a multi-site enterprise |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US13/689,551 US9389850B2 (en) | 2012-11-29 | 2012-11-29 | System and approach to manage versioning of field devices in a multi-site enterprise |
US15/207,294 US20160321061A1 (en) | 2012-11-29 | 2016-07-11 | System and approach to manage versioning of field devices in a multi-site enterprise |
Related Parent Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US13/689,551 Continuation US9389850B2 (en) | 2012-11-29 | 2012-11-29 | System and approach to manage versioning of field devices in a multi-site enterprise |
Publications (1)
Publication Number | Publication Date |
---|---|
US20160321061A1 true US20160321061A1 (en) | 2016-11-03 |
Family
ID=50774488
Family Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US13/689,551 Active 2033-08-01 US9389850B2 (en) | 2012-11-29 | 2012-11-29 | System and approach to manage versioning of field devices in a multi-site enterprise |
US15/207,294 Abandoned US20160321061A1 (en) | 2012-11-29 | 2016-07-11 | System and approach to manage versioning of field devices in a multi-site enterprise |
Family Applications Before (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US13/689,551 Active 2033-08-01 US9389850B2 (en) | 2012-11-29 | 2012-11-29 | System and approach to manage versioning of field devices in a multi-site enterprise |
Country Status (1)
Country | Link |
---|---|
US (2) | US9389850B2 (en) |
Cited By (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US10430175B2 (en) | 2016-11-01 | 2019-10-01 | Johnson Controls Technology Company | Thermostat with software update features |
US10747527B2 (en) | 2016-11-01 | 2020-08-18 | Johnson Controls Technology Company | Multi-zone system with software update features |
Families Citing this family (24)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20110093493A1 (en) | 2008-10-28 | 2011-04-21 | Honeywell International Inc. | Building management system site categories |
US9818073B2 (en) | 2009-07-17 | 2017-11-14 | Honeywell International Inc. | Demand response management system |
US9124535B2 (en) | 2009-07-17 | 2015-09-01 | Honeywell International Inc. | System for using attributes to deploy demand response resources |
US8782190B2 (en) | 2009-07-17 | 2014-07-15 | Honeywell International, Inc. | Demand response management system |
US9153001B2 (en) | 2011-01-28 | 2015-10-06 | Honeywell International Inc. | Approach for managing distribution of automated demand response events in a multi-site enterprise |
US20140081704A1 (en) | 2012-09-15 | 2014-03-20 | Honeywell International Inc. | Decision support system based on energy markets |
US9529349B2 (en) | 2012-10-22 | 2016-12-27 | Honeywell International Inc. | Supervisor user management system |
US9389850B2 (en) | 2012-11-29 | 2016-07-12 | Honeywell International Inc. | System and approach to manage versioning of field devices in a multi-site enterprise |
US9989937B2 (en) | 2013-07-11 | 2018-06-05 | Honeywell International Inc. | Predicting responses of resources to demand response signals and having comfortable demand responses |
US10346931B2 (en) | 2013-07-11 | 2019-07-09 | Honeywell International Inc. | Arrangement for communicating demand response resource incentives |
US9691076B2 (en) | 2013-07-11 | 2017-06-27 | Honeywell International Inc. | Demand response system having a participation predictor |
US9507686B2 (en) | 2013-12-20 | 2016-11-29 | Netapp, Inc. | System, method, and computer program product for monitoring health of computer system assets |
US9891905B2 (en) * | 2014-02-10 | 2018-02-13 | General Electric Company | Utility meter intelligent firmware update system and method |
US9665078B2 (en) | 2014-03-25 | 2017-05-30 | Honeywell International Inc. | System for propagating messages for purposes of demand response |
DE102014004754A1 (en) * | 2014-04-01 | 2015-10-01 | Abb Technology Ag | Method and device for managing and configuring field devices of an automation system |
JP6281413B2 (en) * | 2014-05-28 | 2018-02-21 | 富士通株式会社 | Firmware update device, storage control device, and program |
US10185551B2 (en) * | 2014-07-02 | 2019-01-22 | Hewlett-Packard Development Company, L.P. | Firmware update |
US9933762B2 (en) * | 2014-07-09 | 2018-04-03 | Honeywell International Inc. | Multisite version and upgrade management system |
DE102014118546A1 (en) | 2014-12-12 | 2016-06-16 | Schneider Electric Automation Gmbh | Procedure for updating firmware of devices |
US9535685B1 (en) * | 2015-03-24 | 2017-01-03 | EMC IP Holding Company LLC | Smartly identifying a version of a software application for installation |
US10209689B2 (en) | 2015-09-23 | 2019-02-19 | Honeywell International Inc. | Supervisor history service import manager |
US10362104B2 (en) | 2015-09-23 | 2019-07-23 | Honeywell International Inc. | Data manager |
US10541556B2 (en) | 2017-04-27 | 2020-01-21 | Honeywell International Inc. | System and approach to integrate and manage diverse demand response specifications for multi-site enterprises |
US10986002B1 (en) * | 2017-11-03 | 2021-04-20 | EMC IP Holding Company LLC | Centralizing enterprise-specific information across cloud-based systems |
Citations (7)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2001090829A2 (en) * | 2000-05-24 | 2001-11-29 | Schneider Automation Inc. | System for remote configuration monitoring of an industrial control system |
US20030217357A1 (en) * | 2002-05-14 | 2003-11-20 | Parry Travis J. | Monitoring firmware |
US20040254013A1 (en) * | 1999-10-06 | 2004-12-16 | Igt | Download procedures for peripheral devices |
US20080046878A1 (en) * | 2006-08-18 | 2008-02-21 | Control4 Corporation | Systems and methods for updating a site |
US20100228854A1 (en) * | 2009-03-09 | 2010-09-09 | At&T Mobility Ii Llc | Network operation management |
US20130205288A1 (en) * | 2010-08-30 | 2013-08-08 | Tridonic Gmbh & Co. Kg | Parallel Programming and Updating of Lighting Bus Subscribers |
US8594850B1 (en) * | 2012-09-30 | 2013-11-26 | Nest Labs, Inc. | Updating control software on a network-connected HVAC controller |
Family Cites Families (193)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US4110827A (en) | 1976-10-29 | 1978-08-29 | Honeywell Inc. | Load cycling with space temperature feedback |
US4130874A (en) | 1977-06-13 | 1978-12-19 | Westinghouse Electric Corp. | Load management terminal having plural selectable address formats for a power line communication system |
US4153936A (en) | 1977-09-26 | 1979-05-08 | Reliance Electric Company | Energy management system |
US4419667A (en) | 1979-07-02 | 1983-12-06 | Sangamo Weston, Inc. | System for controlling power distribution to customer loads |
DE3689263T2 (en) | 1985-11-25 | 1994-04-28 | Alcatel Nv | TELEMETRY END STATION. |
US5341142A (en) | 1987-07-24 | 1994-08-23 | Northrop Grumman Corporation | Target acquisition and tracking system |
US4937760A (en) | 1988-09-19 | 1990-06-26 | International Business Machines Corporation | Method for sharing common values implicitly among communicating generative objects |
US5500561A (en) | 1991-01-08 | 1996-03-19 | Wilhelm; William G. | Customer side power management system and method |
CA2116168A1 (en) | 1993-03-02 | 1994-09-03 | Gregory Cmar | Process for identifying patterns of electric energy consumption and demand in a facility, predicting and verifying the effects of proposed changes, and implementing such changes in the facility to conserve energy |
US5598349A (en) | 1994-10-25 | 1997-01-28 | Honeywell Inc. | Responding to pricing signals from a power supplier using mixed add/shed and profile setback delta schemes |
US6574581B1 (en) | 1994-10-25 | 2003-06-03 | Honeywell International Inc. | Profile based method for deriving a temperature setpoint using a ‘delta’ based on cross-indexing a received price-point level signal |
CA2162200A1 (en) | 1994-11-23 | 1996-05-24 | Gagan Lal Choudhury | Efficiently providing multiple grades of service with protection against overloads in shared resources |
US5572438A (en) | 1995-01-05 | 1996-11-05 | Teco Energy Management Services | Engery management and building automation system |
US5822553A (en) | 1996-03-13 | 1998-10-13 | Diamond Multimedia Systems, Inc. | Multiple parallel digital data stream channel controller architecture |
US5892758A (en) | 1996-07-11 | 1999-04-06 | Qualcomm Incorporated | Concentrated subscriber wireless remote telemetry system |
US5886995A (en) | 1996-09-05 | 1999-03-23 | Hughes Electronics Corporation | Dynamic mapping of broadcast resources |
JP3821537B2 (en) | 1997-05-20 | 2006-09-13 | 富士通株式会社 | Data communication system |
US7010700B1 (en) | 1997-10-31 | 2006-03-07 | Cisco Technology, Inc. | Data scanning network security technique |
US6209018B1 (en) | 1997-11-13 | 2001-03-27 | Sun Microsystems, Inc. | Service framework for a distributed object network system |
US6026375A (en) | 1997-12-05 | 2000-02-15 | Nortel Networks Corporation | Method and apparatus for processing orders from customers in a mobile environment |
US6195367B1 (en) | 1997-12-31 | 2001-02-27 | Nortel Networks Limited | Architectural arrangement for bandwidth management in large central offices |
US6289384B1 (en) | 1998-06-05 | 2001-09-11 | I2 Technologies, Inc. | System and method for event notification through a firewall |
US6252950B1 (en) | 1998-09-30 | 2001-06-26 | Lucent Technologies Inc. | Predictive bursty real-time traffic control for telecommunications switching systems |
US6446136B1 (en) | 1998-12-31 | 2002-09-03 | Computer Associates Think, Inc. | System and method for dynamic correlation of events |
US6366926B1 (en) | 1998-12-31 | 2002-04-02 | Computer Associates Think, Inc. | Method and apparatus for the dynamic filtering and routing of events |
ES2207501T3 (en) | 1999-02-08 | 2004-06-01 | United Parcel Service Of America, Inc. | SYSTEM AND METHODS FOR SENDING PACKAGES THROUGH THE INTERNET. |
US6529723B1 (en) | 1999-07-06 | 2003-03-04 | Televoke, Inc. | Automated user notification system |
US7844687B1 (en) | 1999-10-06 | 2010-11-30 | Gelvin David C | Method for internetworked hybrid wireless integrated network sensors (WINS) |
US6535817B1 (en) | 1999-11-10 | 2003-03-18 | The Florida State Research Foundation | Methods, systems and computer program products for generating weather forecasts from a multi-model superensemble |
AUPQ539700A0 (en) | 2000-02-02 | 2000-02-24 | Worldlingo.Com Pty Ltd | Translation ordering system |
AU2001263311A1 (en) | 2000-05-19 | 2001-12-03 | Enron Broadband Services, Inc. | Globally accessible computer network-based broadband communication system with user-controllable quality of information delivery and flow priority |
DE10024407C2 (en) | 2000-05-19 | 2003-12-04 | Driam Anlagenbau Gmbh | Device for coating granules and cores |
US6519509B1 (en) | 2000-06-22 | 2003-02-11 | Stonewater Software, Inc. | System and method for monitoring and controlling energy distribution |
US7069309B1 (en) | 2000-10-19 | 2006-06-27 | Cisco Technology, Inc. | Apparatus and methods for requesting an event notification over a network |
WO2002056662A1 (en) | 2001-01-10 | 2002-07-18 | Matsushita Electric Industrial Co., Ltd. | Component mounter, service supplier, and service supplying method |
US20030016237A1 (en) | 2001-03-08 | 2003-01-23 | Neil Hickey | System for and method of emulating a database system |
US6865685B2 (en) | 2001-03-20 | 2005-03-08 | American Power Conversion | Power supply event notification system for sending an electronic notification to multiple destinations |
GB0110153D0 (en) | 2001-04-25 | 2001-06-20 | Isis Innovation | Improvements in or relating to forecasting |
US7027400B2 (en) | 2001-06-26 | 2006-04-11 | Flarion Technologies, Inc. | Messages and control methods for controlling resource allocation and flow admission control in a mobile communications system |
US7039532B2 (en) | 2001-06-28 | 2006-05-02 | Hunter Robert R | Method and apparatus for reading and controlling utility consumption |
US20030033230A1 (en) | 2001-08-06 | 2003-02-13 | Mccall John E. | Method and system for presenting customized advisory information |
US7260616B1 (en) | 2001-08-13 | 2007-08-21 | Sprint Communications Company L.P. | Communication hub with automatic device registration |
AU2002322930A1 (en) | 2001-08-24 | 2003-03-10 | March Networks Corporation | Remote health-monitoring system and method |
US8489063B2 (en) | 2001-10-24 | 2013-07-16 | Sipco, Llc | Systems and methods for providing emergency messages to a mobile device |
US7401086B2 (en) | 2001-11-21 | 2008-07-15 | Enterasys Networks, Inc. | Translating configuration files among network devices |
US20050095228A1 (en) | 2001-12-07 | 2005-05-05 | Fraser John K. | Methods of using regenerative cells in the treatment of peripheral vascular disease and related disorders |
US7585670B2 (en) | 2001-12-07 | 2009-09-08 | Cytori Therapeutics, Inc. | Automated methods for isolating and using clinically safe adipose derived regenerative cells |
US8321302B2 (en) | 2002-01-23 | 2012-11-27 | Sensormatic Electronics, LLC | Inventory management system |
US6985087B2 (en) | 2002-03-15 | 2006-01-10 | Qualcomm Inc. | Method and apparatus for wireless remote telemetry using ad-hoc networks |
US7424268B2 (en) | 2002-04-22 | 2008-09-09 | Cisco Technology, Inc. | System and method for management of a shared frequency band |
EP1501582A4 (en) | 2002-04-24 | 2009-03-25 | Interpore Orthopaedics Inc | Blood separation and concentration system |
US7318414B2 (en) | 2002-05-10 | 2008-01-15 | Tmc Company | Constant-speed multi-pressure fuel injection system for improved dynamic range in internal combustion engine |
CA2388895C (en) | 2002-06-04 | 2008-11-18 | Global Sensor Systems Inc. | A billing system and method for determining transportation charges for packages |
GB0213073D0 (en) | 2002-06-07 | 2002-07-17 | Hewlett Packard Co | Method of maintaining availability of requested network resources |
US20040034484A1 (en) | 2002-06-24 | 2004-02-19 | Solomita Michael V. | Demand-response energy management system |
US6566926B1 (en) | 2002-06-25 | 2003-05-20 | Intel Corporation | Hysteretic self-biased amplifier |
EP1385277B1 (en) | 2002-07-22 | 2005-06-08 | Agilent Technologies, Inc. - a Delaware corporation - | Transmission of supervisory data in an optical communication system |
US20040203649A1 (en) | 2002-07-22 | 2004-10-14 | Cashiola James P. | System and method for rating communications services provisioned on demand in converging telecommunications networks |
US20070222295A1 (en) | 2002-09-05 | 2007-09-27 | Paul Wareham | System and method for power load management |
US7337237B2 (en) | 2002-10-16 | 2008-02-26 | International Business Machines Corporation | Mechanism to provide callback capabilities for unreachable network clients |
US7333880B2 (en) | 2002-12-09 | 2008-02-19 | Enernoc, Inc. | Aggregation of distributed energy resources |
US20040137897A1 (en) | 2003-05-06 | 2004-07-15 | Joe Teixeira | Flow-through using an automated main distribution frame |
US20050027636A1 (en) | 2003-07-29 | 2005-02-03 | Joel Gilbert | Method and apparatus for trading energy commitments |
US7702424B2 (en) | 2003-08-20 | 2010-04-20 | Cannon Technologies, Inc. | Utility load control management communications protocol |
CA2537910C (en) | 2003-09-05 | 2012-11-06 | Itron, Inc. | Synchronizing and controlling software downloads, such as for utility meter-reading data collection and processing |
US8234876B2 (en) | 2003-10-15 | 2012-08-07 | Ice Energy, Inc. | Utility managed virtual power plant utilizing aggregated thermal energy storage |
US20050172304A1 (en) | 2003-11-28 | 2005-08-04 | David Tavares | Event management system |
US7310722B2 (en) | 2003-12-18 | 2007-12-18 | Nvidia Corporation | Across-thread out of order instruction dispatch in a multithreaded graphics processor |
US7707039B2 (en) | 2004-02-15 | 2010-04-27 | Exbiblio B.V. | Automatic modification of web pages |
US20050194456A1 (en) | 2004-03-02 | 2005-09-08 | Tessier Patrick C. | Wireless controller with gateway |
US20050229220A1 (en) | 2004-04-06 | 2005-10-13 | William Fisher | System and method for interactive video services |
GB0410724D0 (en) | 2004-05-13 | 2004-06-16 | Watkins Daniel R | Authorisation system |
US7787494B1 (en) | 2004-12-07 | 2010-08-31 | Nortel Networks Limited | Method and apparatus for assigning and allocating network resources to packet-based virtual private networks |
US7183910B2 (en) | 2004-12-17 | 2007-02-27 | International Business Machines Corporation | Tiered on-demand location-based service and infrastructure |
EP1679867A1 (en) | 2005-01-06 | 2006-07-12 | Orange SA | Customisation of VoiceXML Application |
WO2006076259A2 (en) | 2005-01-10 | 2006-07-20 | Nicholas Pasquale | Distributed energy storage for reducing power demand |
US8183995B2 (en) | 2005-03-08 | 2012-05-22 | Jackson Kit Wang | Systems and methods for modifying power usage |
US7472301B2 (en) | 2005-05-27 | 2008-12-30 | Codman Neuro Sciences Sárl | Circuitry for optimization of power consumption in a system employing multiple electronic components, one of which is always powered on |
WO2007014146A2 (en) | 2005-07-22 | 2007-02-01 | Cannon Technologies, Inc. | Load shedding control for cycled or variable load appliances |
US20070055999A1 (en) | 2005-09-07 | 2007-03-08 | Looptv | Method and system for initiating, controlling and managing a content-on-demand session via phone, mobile communication or internet based services |
KR20130036332A (en) | 2005-11-17 | 2013-04-11 | 실버 스프링 네트웍스, 인코포레이티드 | Method and system for providing a network protocol for utility services |
EP1987482A4 (en) | 2006-02-21 | 2011-04-20 | Dynamic Intelligence Inc | Transportation scheduling system |
US7392115B2 (en) | 2006-03-01 | 2008-06-24 | Honeywell International Inc. | Characterization of utility demand using utility demand footprint |
ITMI20060599A1 (en) | 2006-03-30 | 2007-09-30 | Eldor Corp Spa | METHOD AND DEVICES FOR THE CONTROL OF THE AIR-COMBUSTIBILR REPORT OF AN INTERNAL COMBUSTION ENGINE |
US8327024B2 (en) | 2006-04-29 | 2012-12-04 | 724 Solutions Software, Inc. | System and method for SMS/IP interoperability |
US8373547B2 (en) | 2006-05-25 | 2013-02-12 | Nev Electronics Llc | Method and apparatus for using power-line phase-cut signaling to change energy usage |
WO2008007160A2 (en) * | 2006-07-11 | 2008-01-17 | Abb Research Ltd. | A life cycle management system for intelligent electronic devices |
US8799639B2 (en) | 2006-07-25 | 2014-08-05 | Intuit Inc. | Method and apparatus for converting authentication-tokens to facilitate interactions between applications |
CA2661999A1 (en) | 2006-08-31 | 2008-03-06 | Itron, Inc. | Orchestration manager |
US20080074285A1 (en) | 2006-08-31 | 2008-03-27 | Guthrie Kevin D | Interface between meter and application (IMA) |
US7873441B2 (en) | 2006-09-25 | 2011-01-18 | Andreas Joanni Synesiou | System for execution of a load operating plan for load control |
US20080114638A1 (en) | 2006-11-10 | 2008-05-15 | Inspection Management Systems, Inc. | Parameter-based appointment scheduling system and method |
US20080167931A1 (en) | 2007-01-04 | 2008-07-10 | Richard Allen Gerstemeier | Community resource management systems and methods |
US20080177678A1 (en) | 2007-01-24 | 2008-07-24 | Paul Di Martini | Method of communicating between a utility and its customer locations |
US20080183307A1 (en) | 2007-01-26 | 2008-07-31 | Autani Corporation | Upgradeable Automation Devices, Systems, Architectures, and Methods |
US20080255760A1 (en) | 2007-04-16 | 2008-10-16 | Honeywell International, Inc. | Forecasting system |
US8406937B2 (en) | 2008-03-27 | 2013-03-26 | Orion Energy Systems, Inc. | System and method for reducing peak and off-peak electricity demand by monitoring, controlling and metering high intensity fluorescent lighting in a facility |
US8091794B2 (en) | 2007-06-28 | 2012-01-10 | Honeywell International Inc. | Thermostat with usage history |
US7954726B2 (en) | 2007-06-28 | 2011-06-07 | Honeywell International Inc. | Thermostat with utility messaging |
US7845576B2 (en) | 2007-06-28 | 2010-12-07 | Honeywell International Inc. | Thermostat with fixed segment display having both fixed segment icons and a variable text display capacity |
CN101689058A (en) | 2007-06-28 | 2010-03-31 | 霍尼韦尔国际公司 | Has the thermostat that on display, transmits message capability |
WO2009020606A1 (en) | 2007-08-09 | 2009-02-12 | Honeywell International Inc. | System to manage demand driven load control |
US7565227B2 (en) | 2007-08-15 | 2009-07-21 | Constellation Energy Group, Inc. | Multi-building control for demand response power usage control |
US8676273B1 (en) | 2007-08-24 | 2014-03-18 | Iwao Fujisaki | Communication device |
US7715951B2 (en) | 2007-08-28 | 2010-05-11 | Consert, Inc. | System and method for managing consumption of power supplied by an electric utility |
US8700187B2 (en) | 2007-08-28 | 2014-04-15 | Consert Inc. | Method and apparatus for actively managing consumption of electric power supplied by one or more electric utilities |
WO2009027617A1 (en) | 2007-08-28 | 2009-03-05 | John Stanton | A utility metering system incorporating a private/public radio network |
US7886166B2 (en) | 2007-09-13 | 2011-02-08 | Gridpoint, Inc. | User interface for demand side energy management |
US8140279B2 (en) | 2007-09-24 | 2012-03-20 | Budderfly Ventures, Llc | Computer based energy management |
US8073558B2 (en) | 2007-10-05 | 2011-12-06 | Honeywell International Inc | Critical resource notification system and interface device |
US7941528B2 (en) | 2007-10-11 | 2011-05-10 | At&T Intellectual Property I, L.P. | Methods, systems and computer program products for providing a multimedia applications gateway |
US8639214B1 (en) | 2007-10-26 | 2014-01-28 | Iwao Fujisaki | Communication device |
WO2009085610A2 (en) | 2007-12-19 | 2009-07-09 | Aclara Power-Line Systems Inc. | Achieving energy demand response using price signals and a load control transponder |
US8330762B2 (en) | 2007-12-19 | 2012-12-11 | Advanced Micro Devices, Inc. | Efficient video decoding migration for multiple graphics processor systems |
US20090187499A1 (en) | 2008-01-21 | 2009-07-23 | David Mulder | System, Method and Computer Program Product for Providing Demand Response Functionality |
KR100960503B1 (en) | 2008-02-05 | 2010-06-01 | 엘에스산전 주식회사 | Electronic smart meter enabling demand response and method for demand response |
US8312299B2 (en) | 2008-03-28 | 2012-11-13 | Packet Digital | Method and apparatus for dynamic power management control using serial bus management protocols |
US20090249090A1 (en) | 2008-03-28 | 2009-10-01 | Schmitz Michael J | Method and apparatus for dynamic power management control using parallel bus management protocols |
US7958229B2 (en) | 2008-03-31 | 2011-06-07 | Verizon Patent And Licensing Inc. | Method and system for energy efficient routing and network services |
WO2009129232A1 (en) | 2008-04-14 | 2009-10-22 | Digital Lumens Incorporated | Modular lighting systems |
US20090271255A1 (en) | 2008-04-24 | 2009-10-29 | Microsoft Corporation | Commerce and advertisement based on explicit consumer's value cost proposition |
MY152237A (en) | 2008-05-09 | 2014-09-15 | Accenture Global Services Ltd | Method and system for managing a power grid |
US20130035992A1 (en) | 2008-05-27 | 2013-02-07 | Kaspar Llc | Method and system for the more efficient utilization and conservation of energy and water resources |
US20100076835A1 (en) | 2008-05-27 | 2010-03-25 | Lawrence Silverman | Variable incentive and virtual market system |
US20100114340A1 (en) | 2008-06-02 | 2010-05-06 | Charles Huizenga | Automatic provisioning of wireless control systems |
KR20090126104A (en) | 2008-06-03 | 2009-12-08 | 서울대학교산학협력단 | Method and system for demand response of electric power |
US20090313083A1 (en) | 2008-06-13 | 2009-12-17 | Honeywell International Inc. | Renewable energy calculator |
US8600571B2 (en) | 2008-06-19 | 2013-12-03 | Honeywell International Inc. | Energy optimization system |
US8143811B2 (en) | 2008-06-25 | 2012-03-27 | Lumetric, Inc. | Lighting control system and method |
US8260468B2 (en) | 2008-06-25 | 2012-09-04 | Versify Solutions, Inc. | Aggregator, monitor, and manager of distributed demand response |
US20100057480A1 (en) | 2008-08-27 | 2010-03-04 | David Arfin | Energy Services |
GB0816721D0 (en) | 2008-09-13 | 2008-10-22 | Daniel Simon R | Systems,devices and methods for electricity provision,usage monitoring,analysis and enabling improvements in efficiency |
WO2010042200A1 (en) | 2008-10-08 | 2010-04-15 | Rey Montalvo | Method and system for fully automated energy curtailment |
US8291243B2 (en) | 2008-10-24 | 2012-10-16 | International Business Machines Corporation | Adaptive computing responsive to environmental conditions |
US8850347B2 (en) | 2010-09-30 | 2014-09-30 | Honeywell International Inc. | User interface list control system |
US20110093493A1 (en) | 2008-10-28 | 2011-04-21 | Honeywell International Inc. | Building management system site categories |
KR101022574B1 (en) | 2008-10-28 | 2011-03-16 | 한국전력공사 | Day-Ahead Load Reduction System Based on Customer Baseline Load |
US20100106543A1 (en) | 2008-10-28 | 2010-04-29 | Honeywell International Inc. | Building management configuration system |
US8260469B2 (en) | 2008-11-04 | 2012-09-04 | Green Energy Corporation | Distributed hybrid renewable energy power plant and methods, systems, and comptuer readable media for controlling a distributed hybrid renewable energy power plant |
US8868925B2 (en) | 2008-12-09 | 2014-10-21 | Nvidia Corporation | Method and apparatus for the secure processing of confidential content within a virtual machine of a processor |
US8295989B2 (en) | 2009-02-03 | 2012-10-23 | ETM Electromatic, Inc. | Local power tracking for dynamic power management in weather-sensitive power systems |
US7778738B2 (en) | 2009-02-11 | 2010-08-17 | Accenture Global Services Gmbh | Method and system for reducing feeder circuit loss using demand response |
US20110040666A1 (en) | 2009-08-17 | 2011-02-17 | Jason Crabtree | Dynamic pricing system and method for complex energy securities |
US8352094B2 (en) | 2009-03-17 | 2013-01-08 | Palo Alto Research Center Incorporated | Technique for aggregating loads with time-varying operating cycles |
US8321950B2 (en) | 2009-03-20 | 2012-11-27 | Cisco Technology, Inc. | Delivering secure IPTV services to PC platforms |
US9406036B2 (en) | 2009-04-24 | 2016-08-02 | Rockwell Automation Technologies, Inc. | Discrete energy assignments for manufacturing specifications |
CA2761416C (en) | 2009-05-08 | 2021-01-19 | Accenture Global Services Limited | Building energy consumption analysis system |
US20100138363A1 (en) | 2009-06-12 | 2010-06-03 | Microsoft Corporation | Smart grid price response service for dynamically balancing energy supply and demand |
US8600556B2 (en) | 2009-06-22 | 2013-12-03 | Johnson Controls Technology Company | Smart building manager |
US9137050B2 (en) | 2009-07-17 | 2015-09-15 | Honeywell International Inc. | Demand response system incorporating a graphical processing unit |
US8671191B2 (en) | 2009-07-17 | 2014-03-11 | Honeywell International Inc. | Installation system for demand response resources |
US8782190B2 (en) | 2009-07-17 | 2014-07-15 | Honeywell International, Inc. | Demand response management system |
US8667132B2 (en) | 2009-07-17 | 2014-03-04 | Honeywell International Inc. | Arrangement for communication about and management of a resource using a mobile device |
US8572230B2 (en) | 2009-07-17 | 2013-10-29 | Honeywell International Inc. | System for using attributes to deploy demand response resources |
US8671167B2 (en) | 2009-07-17 | 2014-03-11 | Honeywell International Inc. | System for providing demand response services |
US8676953B2 (en) | 2009-07-17 | 2014-03-18 | Honeywell International Inc. | Use of aggregated groups for managing demand response resources |
US8626344B2 (en) | 2009-08-21 | 2014-01-07 | Allure Energy, Inc. | Energy management system and method |
US8620634B2 (en) | 2009-07-24 | 2013-12-31 | Honeywell International Inc. | Energy resource allocation including renewable energy sources |
US20110046805A1 (en) | 2009-08-18 | 2011-02-24 | Honeywell International Inc. | Context-aware smart home energy manager |
US8305380B2 (en) | 2009-09-09 | 2012-11-06 | Advanced Micro Devices, Inc. | Managing resources to facilitate altering the number of active processors |
US20110113068A1 (en) | 2009-11-12 | 2011-05-12 | Xinfang Zhao | System and method for managing multiple user registrations |
EP2508999A4 (en) | 2009-11-30 | 2014-03-05 | Panasonic Corp | Portable communication apparatus, communication method, integrated circuit, and program |
US20110231320A1 (en) | 2009-12-22 | 2011-09-22 | Irving Gary W | Energy management systems and methods |
US8738190B2 (en) | 2010-01-08 | 2014-05-27 | Rockwell Automation Technologies, Inc. | Industrial control energy object |
US8543247B2 (en) | 2010-01-08 | 2013-09-24 | International Business Machines Corporation | Power profile management method and system |
EP2531969A4 (en) | 2010-02-01 | 2013-12-04 | Jumptap Inc | Integrated advertising system |
US9847644B2 (en) | 2010-02-09 | 2017-12-19 | Open Access Technology International, Inc. | Systems and methods for demand response and distributed energy resource management |
US20110196539A1 (en) | 2010-02-10 | 2011-08-11 | Honeywell International Inc. | Multi-site controller batch update system |
US20110202293A1 (en) * | 2010-02-15 | 2011-08-18 | General Electric Company | Diagnostics using sub-metering device |
US8386086B2 (en) | 2010-04-26 | 2013-02-26 | Accenture Global Services Limited | Methods and systems for analyzing energy usage |
US20120136496A1 (en) | 2010-11-30 | 2012-05-31 | General Electric Company | System and method for estimating demand response in electric power systems |
WO2012082173A1 (en) | 2010-12-17 | 2012-06-21 | Abb Research Ltd. | Systems and methods for predicting customer compliance with demand response requests |
US8626354B2 (en) | 2011-01-28 | 2014-01-07 | Honeywell International Inc. | Approach for normalizing automated demand response events in energy management control systems |
US9153001B2 (en) | 2011-01-28 | 2015-10-06 | Honeywell International Inc. | Approach for managing distribution of automated demand response events in a multi-site enterprise |
US8630744B2 (en) | 2011-01-28 | 2014-01-14 | Honeywell International Inc. | Management and monitoring of automated demand response in a multi-site enterprise |
US20120245968A1 (en) | 2011-03-21 | 2012-09-27 | Honeywell International Inc. | Building system control and equipment fault and degradation monetization and prioritization |
US20130041852A1 (en) | 2011-08-12 | 2013-02-14 | Qualcomm Incorporated | Customizable dynamic resource regulating devices and methods |
US8689020B2 (en) | 2011-08-16 | 2014-04-01 | General Electric Company | Method, system and computer program product for scheduling demand events |
JP6277129B2 (en) | 2011-09-16 | 2018-02-07 | オートグリッド インコーポレイテッド | A system that optimizes demand response events and facilitates management |
US20130079931A1 (en) | 2011-09-26 | 2013-03-28 | Mohan Wanchoo | Method and system to monitor and control energy |
US8879483B2 (en) | 2011-10-17 | 2014-11-04 | International Business Machines Corporation | Multi-device monitoring and control using intelligent device channel sharing |
US20130144451A1 (en) | 2011-10-25 | 2013-06-06 | San Diego State University Research Foundation | Residential and commercial energy management system |
US20130123996A1 (en) | 2011-11-14 | 2013-05-16 | Gilberto Augusto Matos | Method and system for improving the effectiveness of planned power consumption demand response events |
US8417391B1 (en) | 2011-12-15 | 2013-04-09 | Restore Nv | Automated demand response energy management system |
US20120101653A1 (en) | 2011-12-28 | 2012-04-26 | Bao Tran | Systems and methods for reducing energy usage, |
US20120109399A1 (en) | 2012-01-01 | 2012-05-03 | Bao Tran | Energy resource conservation systems and methods |
US8849715B2 (en) | 2012-10-24 | 2014-09-30 | Causam Energy, Inc. | System, method, and apparatus for settlement for participation in an electric power grid |
US20140122181A1 (en) | 2012-09-15 | 2014-05-01 | Honeywell International Inc. | Demand response load forecaster |
US9389850B2 (en) | 2012-11-29 | 2016-07-12 | Honeywell International Inc. | System and approach to manage versioning of field devices in a multi-site enterprise |
US9807099B2 (en) | 2013-03-15 | 2017-10-31 | Google Inc. | Utility portals for managing demand-response events |
US20140278687A1 (en) | 2013-03-15 | 2014-09-18 | Gridglo Llc | System and Method for Optimizing A Demand Response Event |
US9595070B2 (en) | 2013-03-15 | 2017-03-14 | Google Inc. | Systems, apparatus and methods for managing demand-response programs and events |
US9691076B2 (en) | 2013-07-11 | 2017-06-27 | Honeywell International Inc. | Demand response system having a participation predictor |
-
2012
- 2012-11-29 US US13/689,551 patent/US9389850B2/en active Active
-
2016
- 2016-07-11 US US15/207,294 patent/US20160321061A1/en not_active Abandoned
Patent Citations (7)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20040254013A1 (en) * | 1999-10-06 | 2004-12-16 | Igt | Download procedures for peripheral devices |
WO2001090829A2 (en) * | 2000-05-24 | 2001-11-29 | Schneider Automation Inc. | System for remote configuration monitoring of an industrial control system |
US20030217357A1 (en) * | 2002-05-14 | 2003-11-20 | Parry Travis J. | Monitoring firmware |
US20080046878A1 (en) * | 2006-08-18 | 2008-02-21 | Control4 Corporation | Systems and methods for updating a site |
US20100228854A1 (en) * | 2009-03-09 | 2010-09-09 | At&T Mobility Ii Llc | Network operation management |
US20130205288A1 (en) * | 2010-08-30 | 2013-08-08 | Tridonic Gmbh & Co. Kg | Parallel Programming and Updating of Lighting Bus Subscribers |
US8594850B1 (en) * | 2012-09-30 | 2013-11-26 | Nest Labs, Inc. | Updating control software on a network-connected HVAC controller |
Cited By (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US10430175B2 (en) | 2016-11-01 | 2019-10-01 | Johnson Controls Technology Company | Thermostat with software update features |
US10747527B2 (en) | 2016-11-01 | 2020-08-18 | Johnson Controls Technology Company | Multi-zone system with software update features |
Also Published As
Publication number | Publication date |
---|---|
US20140149973A1 (en) | 2014-05-29 |
US9389850B2 (en) | 2016-07-12 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US9389850B2 (en) | System and approach to manage versioning of field devices in a multi-site enterprise | |
CN101411123B (en) | Method, system and computer program for the centralized system management on endpoints of a distributed data processing system | |
CN102622298B (en) | Software testing system and method | |
CN109471789B (en) | Multi-device management method and device for testing, server and storage medium | |
CN100378670C (en) | Apparatus and method for updating I/O capability of a logically-partitioned computer system | |
CN101346714B (en) | Method for guaranteeing content image execution | |
CN105827446A (en) | Intelligent traffic API gateway and intelligent traffic service system | |
CN107357571B (en) | Maintenance method and system for equipment component program | |
US20170039501A1 (en) | Workflow management apparatus, workflow management method, and workflow management program | |
CN104360952A (en) | Software test system and software test method | |
US9170579B1 (en) | System, method and computer program product for monitoring and controlling industrial energy equipment | |
CN101478422B (en) | Self negotiation method and system for software version | |
JP2022509321A (en) | Cluster management methods, equipment, and systems | |
KR20150112537A (en) | Electronic control unit software coding system and method | |
CN101471820B (en) | Test method for substrate management controller | |
CN110912728B (en) | Operating system patch batch automatic update management method and system | |
CN104461559A (en) | Method for communication between browser and mobile terminal and browser device | |
CN103685405A (en) | Network service system and firmware updating method | |
CN107135120B (en) | Automatic test method and device for HPC cluster | |
CN112035579A (en) | Graph management method, data storage method, data query method, device and storage medium | |
CN115344292A (en) | Firmware automatic upgrading method and device, electronic equipment and readable storage medium | |
CN102004649A (en) | Method and equipment for updating software | |
CN113553163A (en) | Scheduler-based Jenkins application deployment method and device | |
CN102193850A (en) | Time updating system of multi-mainboard server | |
Cejka et al. | Application Lifecycle Management for Industrial IoT Devices in Smart Grid Use Cases. |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
STPP | Information on status: patent application and granting procedure in general |
Free format text: NON FINAL ACTION MAILED |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: RESPONSE TO NON-FINAL OFFICE ACTION ENTERED AND FORWARDED TO EXAMINER |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: NON FINAL ACTION MAILED |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: RESPONSE TO NON-FINAL OFFICE ACTION ENTERED AND FORWARDED TO EXAMINER |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: FINAL REJECTION MAILED |
|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION |