US20160337203A1 - System and approach for remote room controller and device diagnostics and health monitoring - Google Patents
System and approach for remote room controller and device diagnostics and health monitoring Download PDFInfo
- Publication number
- US20160337203A1 US20160337203A1 US14/709,333 US201514709333A US2016337203A1 US 20160337203 A1 US20160337203 A1 US 20160337203A1 US 201514709333 A US201514709333 A US 201514709333A US 2016337203 A1 US2016337203 A1 US 2016337203A1
- Authority
- US
- United States
- Prior art keywords
- health
- page
- remote room
- room controller
- controllers
- 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
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/22—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks comprising specially adapted graphical user interfaces [GUI]
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/01—Input arrangements or combined input and output arrangements for interaction between user and computer
- G06F3/048—Interaction techniques based on graphical user interfaces [GUI]
- G06F3/0481—Interaction techniques based on graphical user interfaces [GUI] based on specific properties of the displayed interaction object or a metaphor-based environment, e.g. interaction with desktop elements like windows or icons, or assisted by a cursor's changing behaviour or appearance
- G06F3/0482—Interaction with lists of selectable items, e.g. menus
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/01—Input arrangements or combined input and output arrangements for interaction between user and computer
- G06F3/048—Interaction techniques based on graphical user interfaces [GUI]
- G06F3/0481—Interaction techniques based on graphical user interfaces [GUI] based on specific properties of the displayed interaction object or a metaphor-based environment, e.g. interaction with desktop elements like windows or icons, or assisted by a cursor's changing behaviour or appearance
- G06F3/0483—Interaction with page-structured environments, e.g. book metaphor
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/01—Input arrangements or combined input and output arrangements for interaction between user and computer
- G06F3/048—Interaction techniques based on graphical user interfaces [GUI]
- G06F3/0484—Interaction techniques based on graphical user interfaces [GUI] for the control of specific functions or operations, e.g. selecting or manipulating an object, an image or a displayed text element, setting a parameter value or selecting a range
- G06F3/04842—Selection of displayed objects or displayed text elements
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/04—Network management architectures or arrangements
- H04L41/044—Network management architectures or arrangements comprising hierarchical management structures
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/06—Management of faults, events, alarms or notifications
- H04L41/0695—Management of faults, events, alarms or notifications the faulty arrangement being the maintenance, administration or management system
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L43/00—Arrangements for monitoring or testing data switching networks
- H04L43/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
- H04L43/0805—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability
- H04L43/0817—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability by checking functioning
Definitions
- the present disclosure pertains to controllers, and particularly to monitoring of controllers.
- a master room controller may be used to open a system health page or a diagnostic page for other controllers.
- a system health page may provide an overview of virtually all of the other room controllers.
- a tool of the present system may be used to trouble shoot issues remotely at another room controller in lieu of doing a visit to the respective room controller.
- a user may navigate from the system health page to virtually any place on the room controller to diagnose issues. The navigation may be done by hyper linking from the system health page.
- the healthy controllers may be hidden from the page so that the unhealthy systems can be viewed in one shot.
- FIG. 1 is a diagram of an illustrative example of a system for remote room controller and device health monitoring
- FIG. 2 is a diagram of an approach for obtaining health and diagnostics of room controllers, networks and devices;
- FIG. 3 is a diagram of a system health summary screen
- FIG. 4 is a diagram of a summary of conditions for an application control engine health, network status and device status
- FIG. 5 is diagram of a screen shot certain properties of an application control engine
- FIG. 5 a is a diagram of thresholds related to the application control engine
- FIG. 6 is a diagram showing a diagnostics page
- FIG. 7 is a diagram of device tab that may display virtually all devices connected to a network and with error and alarm status.
- the present system and approach may incorporate one or more processors, computers, controllers, user interfaces, wireless and/or wire connections, and/or the like, in an implementation described and/or shown herein.
- This description may provide one or more illustrative and specific examples or ways of implementing the present system and approach. There may be numerous other examples or ways of implementing the system and approach.
- a TridiumTM NiagaraTM AX Framework may be a base software application to develop a remote room controller diagnostics page and a tool for troubleshooting the devices. Further, the present system and approach may have a tool that may be used to troubleshoot issues remotely and thus a technician may be required to visit a customer site to troubleshoot any issues of a device.
- FIG. 1 is a diagram 71 of an example layout of a system for remote controller and device health monitoring.
- a master room controller 72 may be connected to one or more remote room controllers 73 , 74 and 75 .
- a connection between controller 72 and controllers 73 - 75 may be via a web 76 , a direct wire connection 77 or a wireless connection.
- Master room controller 72 may have a user interface 78 that is integral to controller 72 or apart from controller 72 .
- User interface 78 may have a display 79 and keyboard 81 and so forth. Display 79 could be a touch screen for selection, response and input.
- Several screens of pages may be shown on display 79 . The screens may incorporate an at-a-glance page 82 , a system health page 83 , a diagnostics page 84 , a troubleshooting page 85 , and other pages 86 , as desired.
- a system health summary screen 31 revealed in a diagram of FIG. 3 may be a web page to provide an “at-a-glance” overview of system-wide health status.
- the system health summary screen 31 may indicate the health of each room controller. Examples of controllers noted may be MIT RMC Bldg 1 and MIT RMC Bldg 2 .
- MIT RMC Bldg 1 may be noted in FIGS. 3 and 5-7 .
- the present disclosure may help for instance, a Phoenix ControlsTM technician to remotely check, for example, the following items: 1) a status of JACETM (Java application control engine); 2) a status of Lon Networks in the JACE; 3) a status of devices in the one or more LonTM networks; 4) a hyperlink of the JACE to allow a user to navigate to a detailed diagnostics screen of the JACE; and 5) mode error and alarm conditions.
- JACETM Java application control engine
- Lon Networks in the JACE a status of Lon Networks in the JACE
- mode error and alarm conditions may help for instance, a Phoenix ControlsTM technician to remotely check, for example, the following items: 1) a status of JACETM (Java application control engine); 2) a status of Lon Networks in the JACE; 3) a status of devices in the one
- a PhoenixTM technician may launch a system health page directly from a Phoenix workbench room controller.
- This controller may be a master room controller.
- a master room controller may be a master of all other room controllers, which has a direct connection to other room controllers.
- Each of the room controllers may have a unique IP address assigned to it which can let a user open a system health page or a diagnostics page.
- the system health page may provide an overview of virtually all room controllers for that Phoenix job as shown in a screen shot in a diagram 31 of FIG. 3 .
- each room controller may be running in a simulated unique port. If the room controller has a dual LAN card, both of the card details may be displayed.
- the categories 32 of information in screen 31 may be a room controller, location, primary LAN with IP address and DHCP (dynamic host configuration protocol), a secondary LAN with IP address and DHCP, JACE health, LON status with LON 1 and LON 2 , and device status.
- Example indicators 33 may be either green (Gn), red (R) or gray (Gy).
- FIG. 2 is a diagram of an example 10 of the present approach.
- a start at symbol 11 may proceed to one of several approaches which in the present case may be to launch a system health page on an RMC from a workbench at symbol 12 , or to enter the via the system health URL in a web browser at symbol 13 .
- a login page at symbol 14 may appear for entry of a user name and password.
- one may press an enter button or click on a login button at symbol 15 .
- a result may be indicated at symbol 16 , which may be login failed or of login success.
- a login failed may have the user return to the login page at symbol 14 or quit the attempt.
- system health page containing room controllers with overall health indicators like RMC/RMI health, LON health and device health and containing a link to a diagnostic page for each RMC in the table. Then the link for diagnostics may be clicked.
- a logic page may appear at symbol 18 and a user name and password can be entered according to symbol 19 . There may be a login failed or a login success. A login failed may have the user return to the logic page at symbol 18 or quit the attempt.
- symbol 20 There may be a diagnostics page for selected RMC with detailed RMC/RMI health, low health and device health as represented by symbols 21 , 22 and 23 , respectively.
- Symbol 21 may indicate a display detailed RMC/RMI health containing CPU usage, memory usage, heap usage, and resource details.
- Symbol 22 may indicate a display of details about the LON network.
- Symbol 23 may indicate a display of devices connected to LON networks with a health indication and additional details of a selected device with alarm and error details.
- FIG. 4 is a diagram of a summary 35 of conditions.
- JACE health 37 a green indication may show a healthy status.
- a red indication may show that something is wrong or that one or more of the conditions exceeded a threshold.
- Chart 36 at the top of the diagram of FIG. 4 is shown in a diagram of FIG. 5 a .
- a gray indication may show that a connection has not been established.
- a green indication may indicate a LON status to be healthy.
- a red indication may indicate something to be wrong.
- a condition may be revealed with a status mask of “FAULT
- green indication may reveal a status to be healthy. Red may indicate something to be wrong. A condition may be revealed with a status mask of “FAULT
- a user may navigate from the system health to any component on the room controller to diagnose the issues. This may be done by hyper linking from the system health page. Also, it may provide the flexibility to hide healthy systems (i.e., no errors or alarms in JACE health, LON status, and device status), so that one can view unhealthy systems in a shot.
- a polling interval may be set which can poll based on the interval (e.g., 5 minutes) set in a Phoenix workbench.
- a screen shot in a diagram 41 of FIG. 5 may show that the memory usage (marked in red ⁇ 2999.7) of indicator 42 may have exceeded a threshold defined, i.e., 80 percent in the present example, according to indicator 43 in a diagram 36 of FIG. 5 a .
- the JACE health may display virtually all of the parameters of the room controller like CPU usage, alarm resources, component count, engine queue actions, engine life time, queue timers, heap usage, some of which are noted by indications 44 , 45 , 46 , 47 and 48 , respectively, and so forth. Alarms may be generated because of low available files, low disk space, low heap, low memory, and RAM also shown on a dashboard.
- FIG. 6 is a diagram 51 showing a diagnostics page.
- JACE health tab 52 may show various parameters related to health of the component.
- a LON (Lon) health tab 53 may display virtually all the Lon related parameters such as health, alarm, fail time, status, and so forth.
- a device tab for an instance of a hood, may display virtually all of the Lon devices connected to the Lon network and its error and alarm status as shown in a diagram 61 of FIG. 7 .
- An error value may be read from “nvoPhxStatus/nvoAppStatus” of a Niagara property and an alarm may be read from “nvoAlarmStatus”.
- a system for remote room controller monitoring may incorporate one or more remote room controllers, a master room controller connected to the one or more remote room controllers, and a user interface connected to the master room controller.
- the user interface may be used to obtain an at-a-glance overview of system-wide issues to provide an at-a-glance overview of a system-wide health status of the one or more remote room controllers.
- the user interface may be used to obtain a diagnostics page corresponding to a selected remote room controller.
- the user interface may be used to pull up a tool to remotely troubleshoot issues of the selected remote room controller in accordance with issues indicated in the diagnostics page corresponding to the selected remote room controller.
- the user interface may be used to go to a website to get the at-a-glance overview of system-wide issues and go to the website to troubleshoot any issues as indicated in the at-a-glance overview of system-wide issues in the one or more remote room controllers.
- the system health summary screen may reveal the at-a-glance overview of system-wide issues to indicate health of each remote room controller for helping a technician to remotely check one or more health items of each remote room controller.
- the one or more health items may be selected from a group consisting of a status of an application control engine, a status of one or more networks in the application control engine, a status of devices in the one or more networks, and a hyperlink of the application control engine to allow a user to navigate to a diagnostics screen of the application control engine, mode, errors, and/or alarm conditions.
- the system may be launched from a health page for a remote room controller from a workbench at the master room controller.
- the health page may incorporate one or more remote room controllers with overall health indicators remote room controller health, network health, and/or device health.
- the system health page may incorporate a link to a diagnostics page for each remote room controller in a table. Upon clicking the link, the diagnostics page for selected remote room controller health, network health and/or a device health may come up on the display.
- the remote room controller health on the diagnostics page revealed on the display may incorporate one or more details selected from a group consisting of central processing unit usage, memory usage, heap usage and/or resources.
- the display may show a list of devices connected to one or more networks having a health indicator and details of one or more devices on the list with alarm and error details.
- the display may show details of the one or more networks.
- the mode, error and alarm details for a device may be highlighted with an indicator for showing a first, second or third color.
- the first color may indicate that something is wrong and one or more of the conditions exceed a threshold.
- the second color may indicate that a connection has not been established.
- the third color may indicate a healthy condition.
- An approach for health monitoring and diagnosis may incorporate developing a diagnostics page for one or more remote room controllers, clicking on a link to obtain for one or more remote room controllers the diagnostics page on a display of a processor, developing a tool for troubleshooting an issue with a device of the one or more remote room controllers, and entering into a system to get to a health page incorporating one or more remote room controllers having overall health indicators.
- the diagnostics page may show the remote room controllers having overall health indicators.
- the overall health indicators may reveal a health of one or more items of a group consisting of remote room controllers, networks, and devices.
- the diagnostics page may be for a selected remote room controller.
- the diagnostics page may incorporate details of remote room controller health, network health and/or device health for a selected remote room controller.
- Details of the remote room controller health may incorporate one or more items of a group consisting of central computing unit usage, memory usage, heap usage and/or resource details.
- a list of devices may be connected to one or more networks with a health indicator and additional details of a selected device with mode, alarm and/or error details displayed.
- a system having monitoring and diagnostics may incorporate one or more remote room controllers, a master room controller connected to the one or more remote room controllers, and a display with an input mechanism connected to the master room controller.
- the master room controller may incorporate an application to develop a remote room controller health page and a diagnostic page, and a tool to remotely troubleshoot issues based on the diagnostics page of a device at a remote room controller.
- the display may show a screen that provides a system-wide health status of the one or more remote controllers.
- Each of the one or more remote room controllers may incorporate one or more items selected from a group consisting of an application control engine, networks connected to and in the application control engine, and a hyperlink of the application control engine to allow a user to navigate to a detailed diagnostics screen of the application control engine, modes, errors, and/or alarm conditions.
- a user may remotely check one or more items of a group consisting of the application control engine, networks in the application control engine, and the hyperlink of the application control engine of the application control engine to allow a user to navigate to the detailed diagnostics screen of the application control engine, modes, errors, and/or alarm conditions.
- Each of the one or more remote room controllers may have a unique internet protocol (IP) address.
- IP internet protocol
- a user can use an internet protocol address at the master room controller to open a system health page or a diagnostics page for a remote room controller having the internet protocol address. The user may troubleshoot a device having a property issue spotted with the diagnostics page.
Abstract
Description
- The present disclosure pertains to controllers, and particularly to monitoring of controllers.
- The disclosure reveals a system and approach for remote health monitoring and diagnostics of room controllers, networks and devices. A master room controller may be used to open a system health page or a diagnostic page for other controllers. A system health page may provide an overview of virtually all of the other room controllers. A tool of the present system may be used to trouble shoot issues remotely at another room controller in lieu of doing a visit to the respective room controller. A user may navigate from the system health page to virtually any place on the room controller to diagnose issues. The navigation may be done by hyper linking from the system health page. The healthy controllers may be hidden from the page so that the unhealthy systems can be viewed in one shot.
-
FIG. 1 is a diagram of an illustrative example of a system for remote room controller and device health monitoring; -
FIG. 2 is a diagram of an approach for obtaining health and diagnostics of room controllers, networks and devices; -
FIG. 3 is a diagram of a system health summary screen; -
FIG. 4 is a diagram of a summary of conditions for an application control engine health, network status and device status; -
FIG. 5 is diagram of a screen shot certain properties of an application control engine; -
FIG. 5a is a diagram of thresholds related to the application control engine; -
FIG. 6 is a diagram showing a diagnostics page; and -
FIG. 7 is a diagram of device tab that may display virtually all devices connected to a network and with error and alarm status. - The present system and approach may incorporate one or more processors, computers, controllers, user interfaces, wireless and/or wire connections, and/or the like, in an implementation described and/or shown herein.
- This description may provide one or more illustrative and specific examples or ways of implementing the present system and approach. There may be numerous other examples or ways of implementing the system and approach.
- A Tridium™ Niagara™ AX Framework may be a base software application to develop a remote room controller diagnostics page and a tool for troubleshooting the devices. Further, the present system and approach may have a tool that may be used to troubleshoot issues remotely and thus a technician may be required to visit a customer site to troubleshoot any issues of a device.
-
FIG. 1 is a diagram 71 of an example layout of a system for remote controller and device health monitoring. Amaster room controller 72 may be connected to one or moreremote room controllers controller 72 and controllers 73-75 may be via aweb 76, adirect wire connection 77 or a wireless connection.Master room controller 72 may have auser interface 78 that is integral to controller 72 or apart fromcontroller 72.User interface 78 may have adisplay 79 andkeyboard 81 and so forth.Display 79 could be a touch screen for selection, response and input. Several screens of pages may be shown ondisplay 79. The screens may incorporate an at-a-glancepage 82, asystem health page 83, adiagnostics page 84, atroubleshooting page 85, andother pages 86, as desired. - A system
health summary screen 31 revealed in a diagram ofFIG. 3 may be a web page to provide an “at-a-glance” overview of system-wide health status. The systemhealth summary screen 31 may indicate the health of each room controller. Examples of controllers noted may be MIT RMC Bldg 1 and MIT RMC Bldg 2. MIT RMC Bldg 1 may be noted inFIGS. 3 and 5-7 . - The present disclosure, such as a system health summary screen to indicate the health of each room controller, may help for instance, a Phoenix Controls™ technician to remotely check, for example, the following items: 1) a status of JACE™ (Java application control engine); 2) a status of Lon Networks in the JACE; 3) a status of devices in the one or more Lon™ networks; 4) a hyperlink of the JACE to allow a user to navigate to a detailed diagnostics screen of the JACE; and 5) mode error and alarm conditions.
- A Phoenix™ technician may launch a system health page directly from a Phoenix workbench room controller. This controller may be a master room controller. A master room controller may be a master of all other room controllers, which has a direct connection to other room controllers. Each of the room controllers may have a unique IP address assigned to it which can let a user open a system health page or a diagnostics page.
- The system health page may provide an overview of virtually all room controllers for that Phoenix job as shown in a screen shot in a diagram 31 of
FIG. 3 . For an offline job, each room controller may be running in a simulated unique port. If the room controller has a dual LAN card, both of the card details may be displayed. - The categories 32 of information in
screen 31 may be a room controller, location, primary LAN with IP address and DHCP (dynamic host configuration protocol), a secondary LAN with IP address and DHCP, JACE health, LON status withLON 1 andLON 2, and device status.Example indicators 33 may be either green (Gn), red (R) or gray (Gy). -
FIG. 2 is a diagram of an example 10 of the present approach. A start at symbol 11 may proceed to one of several approaches which in the present case may be to launch a system health page on an RMC from a workbench atsymbol 12, or to enter the via the system health URL in a web browser atsymbol 13. From eithersymbol symbol 14 may appear for entry of a user name and password. Then, one may press an enter button or click on a login button at symbol 15. A result may be indicated atsymbol 16, which may be login failed or of login success. A login failed may have the user return to the login page atsymbol 14 or quit the attempt. - With login success to
symbol 17, there may be a system health page containing room controllers with overall health indicators like RMC/RMI health, LON health and device health and containing a link to a diagnostic page for each RMC in the table. Then the link for diagnostics may be clicked. - A logic page may appear at
symbol 18 and a user name and password can be entered according tosymbol 19. There may be a login failed or a login success. A login failed may have the user return to the logic page atsymbol 18 or quit the attempt. - With login success, one may go to
symbol 20. There may be a diagnostics page for selected RMC with detailed RMC/RMI health, low health and device health as represented bysymbols 21, 22 and 23, respectively. Symbol 21 may indicate a display detailed RMC/RMI health containing CPU usage, memory usage, heap usage, and resource details.Symbol 22 may indicate a display of details about the LON network. Symbol 23 may indicate a display of devices connected to LON networks with a health indication and additional details of a selected device with alarm and error details. Upon review of one or more of the instances of information as revealed in the symbols, one may end the inquiry atsymbol 24. -
FIG. 4 is a diagram of asummary 35 of conditions. As toJACE health 37, a green indication may show a healthy status. A red indication may show that something is wrong or that one or more of the conditions exceeded a threshold.Chart 36 at the top of the diagram ofFIG. 4 is shown in a diagram ofFIG. 5a . A gray indication may show that a connection has not been established. - As to
LON status 38, a green indication may indicate a LON status to be healthy. A red indication may indicate something to be wrong. A condition may be revealed with a status mask of “FAULT|DOWN|STALE|NULL”. If any of the bits in the mask is set in any of the Lon networks, then it may be marked as red. Gray may indicate a connection not to be established. - As to
device status 39, green indication may reveal a status to be healthy. Red may indicate something to be wrong. A condition may be revealed with a status mask of “FAULT|DOWN|STALE|NULL”. If any of the bits in the mask is set in any of the LON devices, then it may be marked as red. A gray indication may indicate a connection not established. - A user may navigate from the system health to any component on the room controller to diagnose the issues. This may be done by hyper linking from the system health page. Also, it may provide the flexibility to hide healthy systems (i.e., no errors or alarms in JACE health, LON status, and device status), so that one can view unhealthy systems in a shot. A polling interval may be set which can poll based on the interval (e.g., 5 minutes) set in a Phoenix workbench.
- A screen shot in a diagram 41 of
FIG. 5 may show that the memory usage (marked in red −2999.7) ofindicator 42 may have exceeded a threshold defined, i.e., 80 percent in the present example, according to indicator 43 in a diagram 36 ofFIG. 5a . The JACE health may display virtually all of the parameters of the room controller like CPU usage, alarm resources, component count, engine queue actions, engine life time, queue timers, heap usage, some of which are noted byindications -
FIG. 6 is a diagram 51 showing a diagnostics page.JACE health tab 52 may show various parameters related to health of the component. A LON (Lon)health tab 53 may display virtually all the Lon related parameters such as health, alarm, fail time, status, and so forth. A device tab, for an instance of a hood, may display virtually all of the Lon devices connected to the Lon network and its error and alarm status as shown in a diagram 61 ofFIG. 7 . An error value may be read from “nvoPhxStatus/nvoAppStatus” of a Niagara property and an alarm may be read from “nvoAlarmStatus”. - To recap, a system for remote room controller monitoring, may incorporate one or more remote room controllers, a master room controller connected to the one or more remote room controllers, and a user interface connected to the master room controller. The user interface may be used to obtain an at-a-glance overview of system-wide issues to provide an at-a-glance overview of a system-wide health status of the one or more remote room controllers. The user interface may be used to obtain a diagnostics page corresponding to a selected remote room controller. The user interface may be used to pull up a tool to remotely troubleshoot issues of the selected remote room controller in accordance with issues indicated in the diagnostics page corresponding to the selected remote room controller.
- The user interface may be used to go to a website to get the at-a-glance overview of system-wide issues and go to the website to troubleshoot any issues as indicated in the at-a-glance overview of system-wide issues in the one or more remote room controllers.
- The system health summary screen may reveal the at-a-glance overview of system-wide issues to indicate health of each remote room controller for helping a technician to remotely check one or more health items of each remote room controller.
- The one or more health items may be selected from a group consisting of a status of an application control engine, a status of one or more networks in the application control engine, a status of devices in the one or more networks, and a hyperlink of the application control engine to allow a user to navigate to a diagnostics screen of the application control engine, mode, errors, and/or alarm conditions.
- The system may be launched from a health page for a remote room controller from a workbench at the master room controller.
- The health page may incorporate one or more remote room controllers with overall health indicators remote room controller health, network health, and/or device health. The system health page may incorporate a link to a diagnostics page for each remote room controller in a table. Upon clicking the link, the diagnostics page for selected remote room controller health, network health and/or a device health may come up on the display.
- The remote room controller health on the diagnostics page revealed on the display may incorporate one or more details selected from a group consisting of central processing unit usage, memory usage, heap usage and/or resources.
- The display may show a list of devices connected to one or more networks having a health indicator and details of one or more devices on the list with alarm and error details.
- The display may show details of the one or more networks.
- The mode, error and alarm details for a device may be highlighted with an indicator for showing a first, second or third color. The first color may indicate that something is wrong and one or more of the conditions exceed a threshold. The second color may indicate that a connection has not been established. The third color may indicate a healthy condition.
- An approach for health monitoring and diagnosis, may incorporate developing a diagnostics page for one or more remote room controllers, clicking on a link to obtain for one or more remote room controllers the diagnostics page on a display of a processor, developing a tool for troubleshooting an issue with a device of the one or more remote room controllers, and entering into a system to get to a health page incorporating one or more remote room controllers having overall health indicators. The diagnostics page may show the remote room controllers having overall health indicators.
- The overall health indicators may reveal a health of one or more items of a group consisting of remote room controllers, networks, and devices.
- The diagnostics page may be for a selected remote room controller. The diagnostics page may incorporate details of remote room controller health, network health and/or device health for a selected remote room controller.
- Details of the remote room controller health may incorporate one or more items of a group consisting of central computing unit usage, memory usage, heap usage and/or resource details.
- A list of devices may be connected to one or more networks with a health indicator and additional details of a selected device with mode, alarm and/or error details displayed.
- A system having monitoring and diagnostics may incorporate one or more remote room controllers, a master room controller connected to the one or more remote room controllers, and a display with an input mechanism connected to the master room controller.
- The master room controller may incorporate an application to develop a remote room controller health page and a diagnostic page, and a tool to remotely troubleshoot issues based on the diagnostics page of a device at a remote room controller.
- The display may show a screen that provides a system-wide health status of the one or more remote controllers.
- Each of the one or more remote room controllers may incorporate one or more items selected from a group consisting of an application control engine, networks connected to and in the application control engine, and a hyperlink of the application control engine to allow a user to navigate to a detailed diagnostics screen of the application control engine, modes, errors, and/or alarm conditions.
- A user may remotely check one or more items of a group consisting of the application control engine, networks in the application control engine, and the hyperlink of the application control engine of the application control engine to allow a user to navigate to the detailed diagnostics screen of the application control engine, modes, errors, and/or alarm conditions.
- Each of the one or more remote room controllers may have a unique internet protocol (IP) address. A user can use an internet protocol address at the master room controller to open a system health page or a diagnostics page for a remote room controller having the internet protocol address. The user may troubleshoot a device having a property issue spotted with the diagnostics page. Any publication or patent document noted herein is incorporated by reference to the same extent as if each individual publication or patent was specifically and individually indicated to be incorporated by reference.
- 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 (22)
Priority Applications (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US14/709,333 US20160337203A1 (en) | 2015-05-11 | 2015-05-11 | System and approach for remote room controller and device diagnostics and health monitoring |
US17/396,339 US11973664B2 (en) | 2021-08-06 | System and approach for remote room controller and device diagnostics and health monitoring |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US14/709,333 US20160337203A1 (en) | 2015-05-11 | 2015-05-11 | System and approach for remote room controller and device diagnostics and health monitoring |
Related Child Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US17/396,339 Continuation US11973664B2 (en) | 2021-08-06 | System and approach for remote room controller and device diagnostics and health monitoring |
Publications (1)
Publication Number | Publication Date |
---|---|
US20160337203A1 true US20160337203A1 (en) | 2016-11-17 |
Family
ID=57277262
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US14/709,333 Abandoned US20160337203A1 (en) | 2015-05-11 | 2015-05-11 | System and approach for remote room controller and device diagnostics and health monitoring |
Country Status (1)
Country | Link |
---|---|
US (1) | US20160337203A1 (en) |
Citations (9)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5400246A (en) * | 1989-05-09 | 1995-03-21 | Ansan Industries, Ltd. | Peripheral data acquisition, monitor, and adaptive control system via personal computer |
US6097995A (en) * | 1994-11-30 | 2000-08-01 | Chemmist Limited Partnership | Hazardous materials and waste reduction management system |
US20040098148A1 (en) * | 2002-11-14 | 2004-05-20 | Retlich Kevin A. | Industrial control and monitoring method and system |
US20060010009A1 (en) * | 2004-07-07 | 2006-01-12 | Fangman William L | Medication card and system |
US7145457B2 (en) * | 2002-04-18 | 2006-12-05 | Computer Associates Think, Inc. | Integrated visualization of security information for an individual |
US20070219645A1 (en) * | 2006-03-17 | 2007-09-20 | Honeywell International Inc. | Building management system |
US20070239351A1 (en) * | 2006-04-11 | 2007-10-11 | Invensys Systems, Inc. | System management user interface providing user access to status information for process control system equipment including displayed propagated status in a navigation pane |
US20110029102A1 (en) * | 2009-07-31 | 2011-02-03 | Fisher-Rosemount Systems, Inc. | Graphical View Sidebar for a Process Control System |
US9693734B2 (en) * | 2011-07-05 | 2017-07-04 | Saudi Arabian Oil Company | Systems for monitoring and improving biometric health of employees |
-
2015
- 2015-05-11 US US14/709,333 patent/US20160337203A1/en not_active Abandoned
Patent Citations (9)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5400246A (en) * | 1989-05-09 | 1995-03-21 | Ansan Industries, Ltd. | Peripheral data acquisition, monitor, and adaptive control system via personal computer |
US6097995A (en) * | 1994-11-30 | 2000-08-01 | Chemmist Limited Partnership | Hazardous materials and waste reduction management system |
US7145457B2 (en) * | 2002-04-18 | 2006-12-05 | Computer Associates Think, Inc. | Integrated visualization of security information for an individual |
US20040098148A1 (en) * | 2002-11-14 | 2004-05-20 | Retlich Kevin A. | Industrial control and monitoring method and system |
US20060010009A1 (en) * | 2004-07-07 | 2006-01-12 | Fangman William L | Medication card and system |
US20070219645A1 (en) * | 2006-03-17 | 2007-09-20 | Honeywell International Inc. | Building management system |
US20070239351A1 (en) * | 2006-04-11 | 2007-10-11 | Invensys Systems, Inc. | System management user interface providing user access to status information for process control system equipment including displayed propagated status in a navigation pane |
US20110029102A1 (en) * | 2009-07-31 | 2011-02-03 | Fisher-Rosemount Systems, Inc. | Graphical View Sidebar for a Process Control System |
US9693734B2 (en) * | 2011-07-05 | 2017-07-04 | Saudi Arabian Oil Company | Systems for monitoring and improving biometric health of employees |
Also Published As
Publication number | Publication date |
---|---|
US20210367859A1 (en) | 2021-11-25 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US8504991B2 (en) | Cross-browser testing of a web application | |
US7340649B2 (en) | System and method for determining fault isolation in an enterprise computing system | |
US11231944B2 (en) | Alerting, diagnosing, and transmitting computer issues to a technical resource in response to a dedicated physical button or trigger | |
AU2005331434B2 (en) | Monitoring simulating device, method, and program | |
US6865731B2 (en) | Method and computer program product for testing application program software | |
US9595141B2 (en) | Diagnostic device for motor vehicles and diagnostic method | |
JP2018112829A (en) | Cloud service control device, cloud service control system, cloud service control method, cloud service control program and recording medium | |
JP2007102506A (en) | Fault diagnostic system, image forming device and fault diagnostic method | |
US20210367859A1 (en) | System and approach for remote room controller and device diagnostics and health monitoring | |
US11973664B2 (en) | System and approach for remote room controller and device diagnostics and health monitoring | |
CN101795204A (en) | Remote hardware detection system and method | |
US11334060B2 (en) | Alert-enabled passive application integration | |
JP7038629B2 (en) | Equipment condition monitoring device and program | |
JP4257364B2 (en) | COMMUNICATION ERROR INFORMATION OUTPUT PROGRAM, COMMUNICATION ERROR INFORMATION OUTPUT METHOD, AND COMMUNICATION ERROR INFORMATION OUTPUT DEVICE | |
EP3511835A1 (en) | Management of software bugs in a data processing system | |
JP5115025B2 (en) | Fault diagnosis system and fault diagnosis program | |
US20210103785A1 (en) | Method and system for displaying equipment fault code diagnostic information | |
CA3118098C (en) | Alerting, diagnosing, and transmitting computer issues to a technical resource in response to a dedicated physical button or trigger | |
US20180276107A1 (en) | Method for message-processing | |
JP5224759B2 (en) | Test formula creation support system, test formula creation support method, and test formula creation support program | |
WO2019117852A1 (en) | System and method for semantics assisted asset onboarding for industrial digital services | |
JP7286439B2 (en) | Supervisory control system, information processing device, information processing method, and computer program | |
JP2014089540A (en) | Plant control system, plant analysis device, plant analysis method and plant analysis program | |
JP7094078B2 (en) | Simulation equipment and programs | |
JP6798181B2 (en) | Failure resolution support server device and system and program |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: HONEYWELL INTERNATIONAL INC., NEW JERSEY Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:NAIR, AJAY;PARAVASTU, UPENDER;BARRETTE, JAMES;AND OTHERS;SIGNING DATES FROM 20150505 TO 20150507;REEL/FRAME:038548/0718 |
|
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: FINAL REJECTION MAILED |
|
STCV | Information on status: appeal procedure |
Free format text: NOTICE OF APPEAL FILED |
|
STCV | Information on status: appeal procedure |
Free format text: APPEAL BRIEF (OR SUPPLEMENTAL BRIEF) ENTERED AND FORWARDED TO EXAMINER |
|
STCV | Information on status: appeal procedure |
Free format text: EXAMINER'S ANSWER TO APPEAL BRIEF MAILED |
|
STCV | Information on status: appeal procedure |
Free format text: ON APPEAL -- AWAITING DECISION BY THE BOARD OF APPEALS |
|
STCV | Information on status: appeal procedure |
Free format text: BOARD OF APPEALS DECISION RENDERED |
|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- AFTER EXAMINER'S ANSWER OR BOARD OF APPEALS DECISION |