Claims:CLAIMS

We Claim:
1. A system (100) for monitoring and ensuring uptime and efficiency of at least one remote device (102), the system (100) characterized in that comprising:
the remote device (102) to be monitored;
an agent system (122) in communication with the remote device (102) to perform real time monitoring of the remote device (102);
a server system (142) to receive device information of the remote device (102) from the agent system (122) and store the device information in a first database (146); wherein the device information comprises at least one of real time status information, real time notification, current state, historic data, computed trend or reports of the remote device (102);
at least one user system (152) comprising at least one anomaly correction system (162) to fetch the device information, reports, trends from the server system (142), to receive a real time status information and a real time notification from the agent system (122), to raise at least one Anomaly Correction Task (ACT) to at least one technicians with closed tracking and follow-up on the Anomaly Correction Task (ACT) to completion and capable of displaying management review dashboards and exporting reports; and
at least one network (132) connected the agent system (122), the server system (142) and the user system (152).
2. The system (100) of claim 1, wherein the server system (142) comprises the agent system (122) and directly connected to the remote device (102) through the network (132).
3. The system (100) of claim 2, wherein the remote device (102) sends the device information to the agent system (122).
4. The system (100) of claim 2, wherein the agent system (122) reads the device information from the remote device (102).
5. The system (100) of claim 1 or 2, wherein the agent system (122) comprises:
at least one device monitor (124) to monitor the remote device (102), detect a change in a status of the remote device (102) and read or receive a monitor data from the remote device (102);
at least one state analyzer (126) to analyze the state of the remote device (102) based on the historic data received from the device monitor (124);
a notifier (128) to notify a new state of the remote device (102) to one or more user systems (152); and
a data transmitter (130) to send the device information comprising the state of the remote device (102) to the server system (142).
6. The system (100) of claim 5, wherein the server system (142) comprises:
a first data receiver (144) to receive the device information from the data transmitter (130);
the first database (146) for storing the device information with the state of the remote device (102); and
at least one data provider (148) to send the device information to the user system (152).
7. The system (100) of claim 6, wherein the user system (152) comprises:
a second data receiver (154) to receive the device information from the server system (142);
the second database (160) for storing the device information;
a notification receiver (156) to receive the real time notification from the notifier (128);
a device information generator (158) capable of displaying dashboards, reports and trends of the remote device (102); and
an anomaly correction system (162) to generate an Anomaly Correction Task (ACT) ID based on the sate information of the remote device (102).
8. The system of claim 5, wherein the notifier (128) is configured to trigger the real time notification using at least one of a SMS (Short Messaging Service), emails, a Push notification or a style of Internet-based communication based on the new state of the remote device (102).
9. The system of claim 7, wherein the user system (152) is configured to provide one or more access to one or more users based on at least one role of the user.
10. A method (200) for monitoring and ensuring uptime and efficiency of remote devices (102), using system (100) of claim 1, the method characterized in that comprising:
monitoring, by the device monitor (124) of the agent system (122), the remote device (102);
generating, by the agent system (122), the device information based on the monitor data;
receiving, by the first data receiver (144) of the server system (142), the device information from the agent system (122);
storing, by the server system (142), the device information in the first database (146);
receiving, by the second data receiver (154) of the user system (152), the device information from the data provider (148) of the server system (142);
receiving, by a notification receiver (156) of the user system (152), at least one notification from the agent system (122);
raising, by the user system (152), at least one anomaly correction task (ACT) to at least one technicians based on the device information and the notification;
generating, by the anomaly correction system (162) of the user system (152), at least on Anomaly Correction Task (ACT) ID based on the anomaly correction task (ACT);
updating and notifying, by the user system (152) of at least one technician, the status of the anomaly correction task based on the task performed by the technicians in the server system (142);
receiving and verifying, by the user system (152), the status of the anomaly correction task based on the task performed by the technicians in the server system (142);and
ensuring, by the user system (152), uptime and efficiency of the remote device.
11. The method of claim 10, wherein the agent system (122) is configured to perform the following steps of:
receiving, by the device monitor (124), the device information form the remote device (102);
analyzing, by the state analyzer (126), the state of the remote device (102) based on the device information; and
notifying, by the notifier (128), the notification information to the agent system (122); or sending, by the data transmitter (130), the device information comprising the state of the remote device (102) to the server system (142).
12. The method 10, wherein the server system (142) is configured to perform the following steps:
receiving, by the first data receiver (144), the device information from the data transmitter(130);
storing, by the first database (146) for the device information with the state of the remote device (102); and
sending, by the data provider (148), the device information to the user system (152).
13. The method of claim 12, wherein the anomaly correction system (162) of the user system (152) is configured to perform the following steps of:
receiving, by the second data receiver (154), the device information from the server system (142);
receiving, by the notification receiver (156), the real time notification from the notifier;
generating, by the device information generator (158), the state information of the remote device (102) based on the device information and the real time notification; and
generating, by the Anomaly Correction system (162), the Anomaly Correction Task (ACT) ID based on the device information the state information of the remote device (102).
14. The method of claim 13, wherein the agent system (122) is configured further to perform the following steps of:
establishing a connection with the remote device (102);
checking whether the connection is established with the remote device (102);
sending a notification to the remote device (102) about the not connected status;
trying again to establish the connection with the remote device (102);
reading or receiving a current status the remote device (102) and compare the status with a previous status of the remote device (102);
checking whether any change in the current status and the previous status; and
sending notification to the user system (152) and updating a baseline with the current status in the server system (142).
15. The method of claim 14, wherein the server system (142) is configured further to perform the following steps of:
receiving the current status of the remote device (102) from the agent system (122);
checking whether any change in the current status and the previous status;
updating the second database (154) with the current status; and
providing the current status to the user system (152).
16. The method of claim 15, wherein the anomaly correction system (162) of the user system (152) is configured further to perform the following steps of:
receiving the device information from the server system (142); or receiving the notification from the agent system (122);
checking whether the notification is received from the agent system (122);
showing at least one user the notification;
allowing the user to open the notification;
showing the user with the notification; and
suggesting by the user to raise the Anomaly Correction Task (ACT) to the technician to perform correction of the remote device (102).
17. The method of claim 16, wherein the anomaly correction system (162) of the user system (152) is configured further to perform the following steps of:
assigning the Anomaly Correction Task (ACT) to the technician;
allowing the technician to accept, reject or reassign the Anomaly Correction Task (ACT);
allowing the technician to perform correction of the remote device (102), add work details and request for the closure of the Anomaly Correction Task (ACT), when the technician accepts the Anomaly Correction Task (ACT);
allowing the user to review the Anomaly Correction Task (ACT); and
allowing the user to reassign or reopen the Anomaly Correction Task (ACT).
18. The method of claim 17, wherein the anomaly correction system (162) of the user system (152) is configured further to perform the following steps of:
allowing user to view the historic data or trends of the remote device (102);
allowing the user to review the historic data or trends; and
allowing the user to review the device anomaly and decide on the replacement it upgradation of the remote device (102); or allowing the user to review Turn Around Time, Service Level Agreement and quality of the Anomaly Correction Task (ACT) and decide on penalties or improvement measures on the Anomaly Correction Task (ACT).
19. The method of claim 11, wherein the notifier (128) is configured to trigger the real time notification using at least one of a SMS (Short Messaging Service), emails, a Push notification or a style of Internet-based communication based on the new state of the remote device (102).
20. The method of claim 16, wherein the user system (152) is configured to provide one or more access to one or more users based on at least one role of the user.
, Description:FIELD OF THE INVENTION

[0001] The present disclosure relates generally to monitoring of one or more remote devices. Embodiments of the disclosure are related to a system and method for monitoring and ensuring uptime and efficiency of remote devices.

BACKGROUND OF THE INVENTION

[0002] Every enterprise, irrespective of being small or big, install and maintain lots of devices (electronic devices) to assist in operations, enhancing security and so on in office premises or branches or filed offices, collectively referred as remote devices. The intend of investing in these devices is to serve the purpose when it is needed or provide stored data at later point in time for analysis. This trend is nowadays even addressing requirements in domestic space.
[0003] Hence in becomes important to maintain devices, that is, ensuring prompt maintenance and efficiency (with respect to expectation on configuration and outcome). To achieve this, either in-house team is formed or outsourced to external team with Service Level Agreements (SLA) with clear expectation set on Turn Around Time (TAT).
[0004] Despite formulating an in-house or outsourced team, often it ends up ineffective and results in electronic device not delivering when needed, thus diluting the intend. For example, consider a retail chain or bank with about 4000 locations with multiple electronic devices (referred as remote devices) for assisting in operations or enhancing security or both, this would mean the central Information Technology (IT) team to check the entire system at each location at least once in a minute (or at large intervals depending on criticality proportional to purpose met) and reporting & assigning task to correct anomalies observed. Considering network and connectivity issues (attributing Wide Area Network used) and working hours this manual process becomes less efficient and thus timely attention from technical team for fixing also matters. Even if an anomaly is observed by IT team, lakh of well-defined systems for follow-ups and review further dilutes the accountability on correction activities.
[0005] Thus, there exists a need of system and method to monitor and correct remote devices and thereby ensuring uptime and efficiency.

BRIEF SUMMARY OF THE INVENTION

[0006] The following summary is provided to facilitate an understanding of some of the innovative features unique to the disclosed embodiment and is not intended to be a full description. A full appreciation of the various aspects of the embodiments disclosed herein can be gained by taking into consideration the entire specification, claims, drawings, and abstract as a whole.
[0007] The present disclosure relates generally to monitoring of one or more remote devices. Embodiments of the disclosure are related to a system and method for monitoring and ensuring uptime and efficiency of remote devices.
[0008] A system and method for monitoring and ensuring uptime and efficiency of at least one remote device is disclosed. An agent system performs real time monitoring of the remote device. A server system receives device information of the remote device from the agent system and store the device information in a database. A user system has an anomaly correction system to fetch the device information, reports, trends from the server system, to receive real time status information and real time notification from the agent system, to raise at least one Anomaly Correction Task (ACT) to at least one technicians with closed tracking and follow-up on the ACT to completion and capable of displaying management review dashboards and exporting reports. Optionally, the agent system can be housed inside the server system to perform monitoring activates.
[0009] In a first aspect of the present disclosure, a system for monitoring and ensuring uptime and efficiency of at least one remote device, the system characterized in that comprising: the remote device to be monitored; an agent system in communication with the remote device to perform real time monitoring of the remote device; a server system to receive device information of the remote device from the agent system and store the device information in a first database; wherein the device information comprises at least one of real time status information, real time notification, current state, historic data, computed trend or reports of the remote device; at least one user system comprising at least one anomaly correction system to fetch the device information, reports, trends from the server system, to receive real time status information and real time notification from the agent system, to raise at least one Anomaly Correction Task (ACT) to at least one technicians with closed tracking and follow-up on the Anomaly Correction Task (ACT) to completion and capable of displaying management review dashboards and exporting reports; and at least one network connected the agent system, the server system and the user system.
[0010] According to an embodiment in conjunction to the first aspect of the present disclosure, the server system comprises the agent system and directly connected to the remote device through the network.
[0011] According to an embodiment in conjunction to the first aspect of the present disclosure, the remote device sends the device information to the agent system.
[0012] According to an embodiment in conjunction to the first aspect of the present disclosure, the agent system reads the device information from the remote device.
[0013] According to an embodiment in conjunction to the first aspect of the present disclosure, the agent system comprises: at least one device monitor to monitor the remote device, detect a change in a status of the remote device and read or receive a monitor data from the remote device; at least one state analyzer to analyze the state of the remote device based on the historic data received from the device monitor; a notifier to notify a new state of the remote device to one or more user systems; and a data transmitter to send the device information comprising the state of the remote device to the server system.
[0014] According to an embodiment in conjunction to the first aspect of the present disclosure, the server system comprises: a first data receiver to receive the device information from the data transmitter; the first database for storing the device information with the state of the remote device; and at least one data provider to send the device information to the user system.
[0015] According to an embodiment in conjunction to the first aspect of the present disclosure, the user system comprises: a second data receiver to receive the device information from the server system; the second database for storing the device information; a notification receiver to receive the real time notification from the notifier; a device information generator capable of displaying dashboards, reports and trends of the remote device; and an anomaly correction system to generate an Anomaly Correction Task (ACT) ID based on the sate information of the remote device.
[0016] According to an embodiment in conjunction to the first aspect of the present disclosure, the notifier is configured to trigger the notification using at least one of a SMS (Short Messaging Service), emails, a push notification or a style of Internet-based communication based on the new state of the remote device.
[0017] According to an embodiment in conjunction to the first aspect of the present disclosure, the user system is configured to provide one or more access to one or more users based on at least one role of the user.
[0018] In a second aspect of the present disclosure, a method for monitoring and ensuring uptime and efficiency of remote devices, using system of claim 1, the method characterized in that comprising: monitoring, by the device monitor of the agent system, the remote device; generating, by the agent system, the device information based on the monitor data; receiving, by the first data receiver of the server system, the device information from the agent system; storing, by the server system, the device information in the first database; receiving, by the second data receiver of the user system, the device information from the data provider of the server system; receiving, by a notification receiver of the user system, at least one notification from the agent system; raising, by the user system, at least one anomaly correction task (ACT) to at least one technicians based on the device information and the notification; generating, by the anomaly correction system of the user system, at least on Anomaly Correction Task (ACT) ID based on the anomaly correction task (ACT); updating and notifying, by the user system of at least one technician, the status of the anomaly correction task based on the task performed by the technicians in the server system; receiving and verifying, by the user system, the status of the anomaly correction task based on the task performed by the technicians in the server system; and ensuring, by the user system, uptime and efficiency of the remote device.
[0019] According to an embodiment in conjunction to the second aspect of the present disclosure, the agent system is configured to perform the following: receiving, by the device monitor, the device information form the remote device; analyzing, by the state analyzer, the state of the remote device based on the device information; and notifying, by the notifier, the notification information to the agent system; or sending, by the data transmitter, the device information comprising the state of the remote device to the server system.

[0020] According to an embodiment in conjunction to the second aspect of the present disclosure, the server system is configured to perform the following: receiving, by the first data receiver, the device information from the data transmitter; storing, by the first database for the device information with the state of the remote device; and sending, by the data provider, the device information to the user system.
[0021] According to an embodiment in conjunction to the second aspect of the present disclosure, the anomaly correction system of the user system is configured to perform the following: receiving, by the second data receiver, the device information from the server system; receiving, by the notification receiver, the real time notification from the notifier; generating, by the device information generator, the state information of the remote device based on the device information and the real time notification; and generating, by the Anomaly Correction system, the Anomaly Correction Task (ACT) ID based on the device information the state information of the remote device.
[0022] According to an embodiment in conjunction to the second aspect of the present disclosure, the agent system is configured further to perform the following: establishing a connection with the remote device; checking whether the connection is established with the remote device; sending a notification to the remote device about the not connected status; trying again to establish the connection with the remote device; reading or receiving a current status the remote device and compare the status with a previous status of the remote device; checking whether any change in the current status and the previous status; and sending notification to the user system and updating a baseline with the current status in the server system.
[0023] According to an embodiment in conjunction to the second aspect of the present disclosure, the server system is configured further to perform the following: receiving the current status of the remote device from the agent system; checking whether any change in the current status and the previous status; updating the second database with the current status; and providing the current status to the user system.
[0024] According to an embodiment in conjunction to the second aspect of the present disclosure, the anomaly correction system of the user system is configured further to perform the following: receiving the device information from the server system; or receiving the notification from the agent system; checking whether the notification is received from the agent system; showing at least one user the notification; allowing the user to open the notification; showing the user with the notification; and suggesting by the user to raise the Anomaly Correction Task (ACT) to the technician to perform correction of the remote device.
[0025] According to an embodiment in conjunction to the second aspect of the present disclosure, the anomaly correction system of the user system is configured further to perform the following: assigning the Anomaly Correction Task (ACT) to the technician; allowing the technician to accept, reject or reassign the Anomaly Correction Task (ACT); allowing the technician to perform correction of the remote device, add work details and request for the closure of the Anomaly Correction Task (ACT), when the technician accepts the Anomaly Correction Task (ACT); allowing the user to review the Anomaly Correction Task (ACT); and allowing the user to reassign or reopen the Anomaly Correction Task (ACT).
[0026] According to an embodiment in conjunction to the second aspect of the present disclosure, the anomaly correction system of the user system is configured further to perform the following: allowing user to view the historic data or trends of the remote device; allowing the user to review the historic data or trends; and allowing the user to review the device anomaly and decide on the replacement it upgradation of the remote device; or allowing the user to review Turn Around Time, Service Level Agreement and quality of the Anomaly Correction Task (ACT) and decide on penalties or improvement measures on the Anomaly Correction Task (ACT).
[0027] According to an embodiment in conjunction to the second aspect of the present disclosure, the notifier is configured to trigger the real time notification using at least one of a SMS (Short Messaging Service), emails, a Push notification or a style of Internet-based communication based on the new state of the remote device.
[0028] According to an embodiment in conjunction to the second aspect of the present disclosure, the user system is configured to provide one or more access to one or more users based on at least one role of the user.

BRIEF DESCRIPTION OF THE FIGURES

[0029] FIG. 1 is an illustration of an example block diagram of a system for monitoring and ensuring uptime and efficiency of a remote device, in accordance with the disclosed embodiment of the invention.
[0030] FIG. 2 is an illustration of an example block diagram of a system for monitoring and ensuring uptime and efficiency of the remote device, in accordance with the alternative embodiment of the invention.
[0031] FIG. 3 is an illustration of an example block diagram of an agent system used in the system of FIG. 1 or FIG. 2, in accordance with the disclosed embodiment of the invention.
[0032] FIG. 4 is an illustration of an example block diagram of the server system used in the system of FIG. 1 or FIG. 2, in accordance with the disclosed embodiment of the invention.
[0033] FIG. 5 is an illustration of an example block diagram of the user system used in the system of FIG. 1 or FIG. 2, in accordance with the disclosed embodiment of the invention.
[0034] FIG. 6 is an illustration of an example block diagram of the server system and the agent system used in the system of FIG. 1 or FIG. 2, in accordance with the disclosed embodiment of the invention.
[0035] FIG. 7 is an illustration of an example flow diagram pertaining to the steps performed by system for monitoring and ensuring uptime and efficiency of a remote device, in accordance with the disclosed embodiment of the invention.
[0036] FIG. 8 is an illustration of an example flow diagram pertaining to the steps performed by the agent system, in accordance with the disclosed embodiment of the invention.
[0037] FIG. 9 is an illustration of an example flow diagram pertaining to the steps performed by the server system, in accordance with the disclosed embodiment of the invention.
[0038] FIG. 10 is an illustration of an example flow diagram pertaining to the steps performed by the user system, in accordance with the disclosed embodiment of the invention.
[0039] FIG. 11 is an illustration of another example flow diagram pertaining to the steps performed by the user system, in accordance with the disclosed embodiment of the invention.
[0040] FIG. 12 is an illustration of another example flow diagram pertaining to the steps performed by the user system, in accordance with the disclosed embodiment of the invention.
[0041] The summary above, as well as the following detailed description of illustrative embodiments, is better understood when read in conjunction with the appended drawings. For the purpose of illustrating the present disclosure, exemplary constructions of the disclosure are shown in the drawings. However, the disclosure is not limited to specific methods and instrumentalities disclosed herein. Moreover, those in the art will understand that the drawings are not to scale. Wherever possible, like elements have been indicated by identical numbers.

DETAILED DESCRIPTION OF ILLUSTRATIVE EMBODIMENTS

[0042] The particular configurations discussed in the following description are non-limiting examples that can be varied and are cited merely to illustrate at least one embodiment and are not intended to limit the scope thereof.
[0043] Referring to FIG. 1, an example block diagram of a system 100 for monitoring and ensuring uptime and efficiency of a remote device 102. The system 100 has one or more remote devices 102, an agent system 122, a server system 142 and one or more user systems 154. The remote device 102 represents the electronic device being monitored. Remote device 102 is not limited to any 3rd party device like DVR (Digital Video Recorder), Alarm Panel, IP(Internet Protocol) Camera, printer, UPS(Uninterruptible Power Supply) and so on, but also custom built devices known in art, that are kept in offices or factories or homes. These remote devices 102 offer wired or wireless connectivity, for example, but not limited to, via serial port, for example, RJ 45 or RJ 11, Bluetooth or Wi-Fi (Wireless Fidelity). The remote device 102 represents devices (electronic devices) to assist in operations, enhancing security and so on, in office premises or branches or filed offices.
[0044] The agent system 122 is configured to be in communication with the remote device 102 to perform real time monitoring. In one example, the agent system 122 reads configuration, status parameters and other details of remote device 102 at pre-configured intervals. In another example, pre-configured interval is set by user or is derived as a function in relation with another device status. In another example, remote device 102 sends configuration, status parameters and other details to connected agent system 122.
[0045] In one embodiment of the invention the agent system 122 comprises a device monitor 124, a state analyzer 126, a notifier 128 and a data transmitter 130. The device monitor 124 is used to monitor the remote device 102, detect a change in a status of the remote device 102 and read or receive a monitor data from the remote device 102. The state analyzer 126 can be used to analyze the state of the remote device 102 based on the historic data received from the device monitor 124. The notifier 128 can notify a new state of the remote device 102 to one or more user systems 152. The agent system 122 also has the data transmitter 130 to send the device information having the state of the remote device 102 to the server system 142.
[0046] The agent system 122 may also comprise of at least one processor, at least one memory and I/O interface. At least one processor may be implemented as one or more microprocessors, microcomputers, microcontrollers, digital signal processors, central processing units, state machines, logic circuitry, and/or any devices that manipulate signals based on operational instructions. Among other capabilities, at least one processor is configured to fetch and execute computer-readable instructions stored in the memory. The memory may include any computer-readable medium known in the art including, for example, volatile memory, such as static random access memory (SRAM) and dynamic random access memory (DRAM), and/or non-volatile memory, such as read only memory (ROM), erasable programmable ROM, flash memories, hard disks, optical disks, and magnetic tapes. The I/O interface may include a variety of software and hardware interfaces, for example, a web interface, a graphical user interface, and the like. Further, the I/O interface may enable the agent system 122 to communicate with other computing devices, such as web servers and external data servers (not shown). The I/O interface may facilitate multiple communications within a wide variety of networks and protocol types, including wired networks, for example, LAN, cable, and so on, and wireless networks, such as WLAN, cellular, or satellite. The I/O interface may include one or more ports for connecting a number of devices to one another or to the server system 142. Although the present disclosure is explained by considering that the agent system 122 is implemented on the server system 142, it may be understood that the agent system 122 may also be implemented in a variety of computing systems, such as a mainframe computer, mobile, single board computer and the like.
[0047] The in one example, the notifier 128 can trigger notifications as a SMS (Short Messaging Service). In another example, the notifier 128 can trigger notification as Emails. In one another example, the notifier 128 can trigger notification with Push technology, a style of Internet-based communication where the request for a given transaction is initiated by the publisher or central server. The notifier 128, can also offer a combination of triggering mechanisms as well. The real-time notifications allows the IT team in the user system to be informed about the status change of the remote device anytime. In one embodiment of the invention the notifier is configured to trigger the notification using at least one of a SMS (Short Messaging Service), emails, a push notification or a style of Internet-based communication based on the new state of the remote device.
[0048] The server system 142 receives the device information of the remote device 102 from the agent system 122, via the first data receiver 144 and store the device information in a first database 146. The device information is not limited to at least one of real time status information, real time notification, current state, entire configuration, historic data, computed trend or reports of the remote device.
[0049] In one embodiment of the invention, the server system 142 comprises a first data receiver 144, the first database 146 and at least one data provider 148. The first data receiver 144 is configured to receive the device information from the data transmitter 130 of the agent system 122. The device information received with the state of the remote device 102 is stored in the first database 146. The data provider 148 is used to send the device information to the user system 152.
[0050] The server system 142 may also comprise of at least one processor, at least one memory and I/O interface. At least one processor may be implemented as one or more microprocessors, microcomputers, microcontrollers, digital signal processors, central processing units, state machines, logic circuitry, and/or any devices that manipulate signals based on operational instructions. Among other capabilities, at least one processor is configured to fetch and execute computer-readable instructions stored in the memory. At least one memory may include any computer-readable medium known in the art including, for example, volatile memory, such as static random access memory (SRAM) and dynamic random access memory (DRAM), and/or non-volatile memory, such as read only memory (ROM), erasable programmable ROM, flash memories, hard disks, optical disks, and magnetic tapes. The I/O interface may include a variety of software and hardware interfaces, for example, a web interface, a graphical user interface, and the like. Further, the I/O interface may enable the server system 142 to communicate with other computing devices, such as web servers and external data servers (not shown). The I/O interface may facilitate multiple communications within a wide variety of networks and protocol types, including wired networks, for example, LAN, cable, and so on, and wireless networks, such as WLAN, cellular, or satellite. The I/O interface may include one or more ports for connecting a number of devices to one another or to the server system 142. Although the present disclosure is explained by considering that the server system 142 is implemented on the server, it may be understood that the server system 142 may also be implemented in a variety of computing systems, such as a mainframe computer, mobile, single board computer and the like.
[0051] The system 100 also has one or more user system 152 comprising at least one anomaly correction system 162 is used to fetch the device information, reports, trends from the server system 142, to receive real time status information and real time notification from the agent system 122, through second data receiver 154, to raise at least one Anomaly Correction Task (ACT) to at least one technicians with closed tracking and follow-up on the Anomaly Correction Task (ACT) to completion and capable of displaying management review dashboards and exporting reports utilizing device information generator 158 and save information in second database 160. The user system 152 can receive and display status notifications utilizing an notification receiver 156.
[0052] In one embodiment of the invention, the user system 152 has a second data receiver 154, a second database 160, the notification receiver 156, a device information generator 158 and an anomaly correction system 162. The second data receiver 154 is used to receive the device information from the server system 142 and the received device information is stored in the second database 160. The notification receiver 156 can receive the real time notification from the notifier 128 of the agent system 122. The real time notification will be based on the state change of the remote device 102 that is monitored. The device information generator 158 in the user system 152 is capable of displaying dashboards, reports and trends of the remote device 102, so that the correction task/anomaly related to the remote device 102 can be allocated to technicians.

[0053] The user system 152 may also comprise of at least one processor, at least one memory and I/O interface. At least one processor may be implemented as one or more microprocessors, microcomputers, microcontrollers, digital signal processors, central processing units, state machines, logic circuitry, and/or any devices that manipulate signals based on operational instructions. Among other capabilities, at least one processor is configured to fetch and execute computer-readable instructions stored in the memory. At least one memory may include any computer-readable medium known in the art including, for example, volatile memory, such as static random access memory (SRAM) and dynamic random access memory (DRAM), and/or non-volatile memory, such as read only memory (ROM), erasable programmable ROM, flash memories, hard disks, optical disks, and magnetic tapes. The I/O interface may include a variety of software and hardware interfaces, for example, a web interface, a graphical user interface, and the like. Further, the I/O interface may enable the user system 152 to communicate with other computing devices, such as web servers and external data servers (not shown). The I/O interface may facilitate multiple communications within a wide variety of networks and protocol types, including wired networks, for example, LAN, cable, and so on, and wireless networks, such as WLAN, cellular, or satellite. The I/O interface may include one or more ports for connecting a number of devices to one another or to the server system 142. Although the present disclosure is explained by considering that the user system 152 is implemented on the server 142, it may be understood that the user system 152 may also be implemented in a variety of computing systems, such as a mainframe computer, mobile, single board computer and the like.
[0054] The agent system 122, the server system 142 and the user system 152 are connected to a network 132.
[0055] In one embodiment of the invention, the agent system 122 can be housed inside the server system 142 and can establish direct connection to the remote device 102 through the network 132, as shown in FIG. 2.
[0056] Now referring to the FIG. 3, the agent system 122 of the system 100 comprises a device monitor 124, a state analyzer 126, a notifier 128 and a data transmitter 130. The agent system 122 monitors one or more remote devices 102 and in case of any state or status change in remote device 102, the agent system 122 will transfer the device information to the server system 142. The server system can process and transmit the same to the user system to address, in case of any anomaly in the remote device 102. The device monitor 124 is used to monitor the remote device 102, detect a change in a status of the remote device 102 and read or receive a monitor data from the remote device 102. The state analyzer 126 can be used to analyze the state of the remote device 102 based on the historic data received from the device monitor 124. The notifier 128 can notify a new state of the remote device 102 to one or more user systems 152. The agent system 122 also has the data transmitter 130 to send the device information having the state of the remote device 102 to the server system 142. The real time notification will be based on the state change of the remote device 102 that is monitored in the remote device 102. It should be noted that the terms notification, alert, real time notification or notification alter refers to same meaning, that is not limited to the device information or state change information of the remote device.
[0057] Referring to the FIG. 4, the server system 142 comprises a first data receiver 144, the first database 146 and at least one data provider 148. The server system 142 is configured to receive any configuration, state or status change in remote device 102 from the agent system, then process & store the same and can then transmit the same to the user system for reviews as well as to address, in case of any anomaly in the remote device 102. The first data receiver 144 is configured to receive the device information from the data transmitter 130 of the agent system 122. The device information received with the state of the remote device 102 is stored in the first database 146. In one embodiment of the invention the last know data or device information of the remote device is stored as a baseline in the server system 142. The data provider 148 is used to send the device information to the user system 152. It should be noted that the server system 142 stores all the information’s, for example, not limited to, at least one of real time status information, real time notification, current state, historic data, computed trend or reports of the remote device 102 to be monitored. The user system 152 can use such information from the server system 142 and accordingly allocate the tasks to the technicians to rectify both software and hardware related anomalies. The software and hardware related anomalies are not limited to hardware failures, sensor calibration tolerance, capacity of data or storage, software/firmware configuration mismatch, battery capacity, software/firmware corrections, loose connections, irregular consumption of power or consumables and so on.

[0058] The user system 152 in FIG. 5 has a second data receiver 154, a second database 160, a notification receiver 156, a device information generator 158 and an anomaly correction system 162. The user system 152 is configured to receive the device information from the server system 142. The user system 152 can have one or more users to address or correct any anomaly of the remote device 102. The second data receiver 154 is used to receive the device information from the server system 142 and the received device information is stored in the second database 160. The notification receiver 156 can receive the real time notification from the notifier 128 of the agent system 122.
[0059] The device information generator 158 in the user system 152 can display dashboards, reports and trends. In one example device information generator 158 does display of dashboards, trends and reports of remote device 102, so that device anomalies can be detected and anomaly correction task related to the remote device 102 can be allocated to technicians and further action can be taken to rectify the anomaly in the remote device 102, resulting in ensuring uptime of remote device 102. In another example device information generator 158 does display of dashboards, trends and reports of remote device 102, which can used to detect anomalies with respect to efficiency of monitored remote device 102, like but not limited to power consumption, consumable consumption, storage related etc. and further anomaly correction task can be assigned for corrective measures, resulting in ensuring efficiency of remote device 102. In another example device information generator 158 does display of dashboards, trends and reports of remote device 102, which can used to initiate decisions for remote device 102 replacement or upgrades, resulting in ensuring uptime of remote device 102. In another example device information generator 158 does display of dashboards, trends and reports of remote device 102 and associated duration and details of all anomaly correction tasks, which can used to review SLA (Service Level Agreements) and TAT (Turn Around Time) take corrective measures for improving performance of team or vendor or even vendor change, resulting in ensuring focused team in place thereby improving uptime of remote device 102.
[0060] It should be noted that the user system 152 can be operated by one or more users, for example, not limited to the administrative users, work/task allocators, technicians, review managers and so on. In one example the user system 152 offer role-based access to data, providing access restrictions based on role of user in organization. In another example, the user system 152 provides higher set of privileges to a set of users to add or remove users as well as assign restrictions to other users. In one embodiment of the invention, the user system 152 is configured to provide one or more access to one or more users based on at least one role of the user in the organization.
[0061] In one embodiment of the invention, the anomaly correction system 162 is used to generate an Anomaly Correction Task (ACT) ID based on the sate information of the remote device 102. The anomaly correction system 162 is used to fetch the device information, reports, trends from the server system 142, to receive real time status information and real time notification from the agent system 122, to raise at least one Anomaly Correction Task (ACT) to at least one technicians with closed tracking and follow-up on the Anomaly Correction Task (ACT) to completion and capable of displaying management review dashboards and exporting reports.
[0062] FIG. 6 is an illustration of an example block diagram showing the working of both the server system 142 and the agent system 122 used in the system 100 of FIG. 1 or FIG. 2, in accordance with the disclosed embodiment of the invention. The device monitor 124 of the agent system 122 is used to monitor the remote device 102, detect a change in a status of the remote device 102 and read or receive a monitor data from the remote device 102. The state analyzer 126 of the agent system 122 can be used to analyze the state of the remote device 102 based on the historic data received from the device monitor 124. The notifier 128 can notify a new state of the remote device 102 to one or more user systems 152. The agent system 122 also has the data transmitter 130 to send the device information having the state of the remote device 102 to the server system 142. Once the state and condition of the remote device are obtained, the same can be transferred to the server system 142. The first data receiver 144 of the server system 142 is configured to receive the device information from the data transmitter 130 of the agent system 122. The device information received with the state of the remote device 102 is stored in the first database 146. The server system 142 also has the data provider 148 to send the device information to the user system 152. In one embodiment of the invention, the remote device 102 that is being monitored can send the status information automatically to agent system 122 located in the server system 142. In one another embodiment of the invention, the agent system 122 can periodically read the status information from monitoring system.
[0063] Referring to FIG. 7 method 200 for monitoring and ensuring uptime and efficiency of the remote devices 102. As at step 202, the device monitor of the agent system is used to monitor the remote device. The agent system generates the device information based on the monitor data from the device monitor, as at step 204. Then, as at block 206, the first data receiver of the server system is configured receive the device information from the agent system. The server system stores the device information in the first database, as at step 208. Then, as at step 210, the second data receiver of the user system receives the device information from the server system. The user system receives at least one notification from the agent system using the notification receiver, as at step 212. Then, the user system raises for rectification or correction at least one anomaly correction task (ACT) to at least one technician based on the device information and the notification, as at step 214. Then, as at the step 216, the anomaly correction system of the user system generates at least on Anomaly Correction Task (ACT) ID based on the anomaly correction task (ACT) and information is stored in server. The technician of the user system is updated and notified with the status of the anomaly correction task and notification is raised, based on the task performed by the technicians in the server system, as at step 218. The user system receives and verifies at least one notification from the technician user system using the notification receiver, as at step 220. Subsequently verifies the ACT and confirms device correction, else raises at least one anomaly correction task to at least one technician based on device information, as at step 214. Finally, as at step 222, the user system ensures uptime and efficiency of the remote device.
[0064] Referring to FIG. 8, the agent system is configured to perform the method 300. As at step 302, the agent system establishes connection with the remote device. The remote devices to be monitored can be designated to one or more agent system, either by the user system or the agent system at the time of installation of the remote device. The agent system check whether sufficient connection to the remote device is established or not, as at step 310. In case when no connection is established with the remote device, a notification is sent to the remote device, as at step 315. When the connection to the remote device is established, the device monitor and the state analyzer of the agent system can read the states of the remote device and compare with the historical state of the remote device, as at step 320. In one embodiment of the invention, the device monitor can receive the device information form the remote device and the state analyzer is used to analyze the state of the remote device based on the device information. The state analyzer checks whether any change in the state of the remote device, as at step 325. In case of change in state of remote device, as at steps 330 and 335, the server is updated with the latest state of the remote device. In one embodiment of the invention, the notifier can notify a new state of the remote device to one or more user systems. The agent system also has the data transmitter to send the device information having the state of the remote device to the server system.
[0065] Referring to FIG. 9, the server system is configured to perform the method 400. As at step 405, the first data receiver receives the device information from the data transmitter. Then, as at step 410, the first database stores the device information with the state of the remote device. Finally, the data provider can be configured to send the device information to the user system, as at step 415. It should be noted that the baseline refers to the last know data or details of the remote device that are updated in server system when any change in the state of the remote device is identified by the agent system. The baseline is generally maintained in server system and the agent system can use the same temporarily to identify state change of the remote device. The agent system can update the baseline whenever any change in the state of the remote device is identified and the same is updated in the server system for later use.
[0066] Referring to FIG. 10, the anomaly correction system of the user system is configured to perform the method 500. As at step 505, the second data receiver receives the device information from the server system. The server system, checks whether any notification is received from the agent system, as at the step 510. When a notification alert is received from the agent system, the user of the user system is shown with the notification, as at step 515. The notification receiver can be used to receive the real time notification from the notifier of the agent system. The system checks whether, the user opens the notification or not, as at step 520. When the user opens the notification, the notification data is shown to the user, as at step 535. The user can check whether the current state of the remote device is a known state, as at step 540. If the state of the remote device is not known, then the anomaly related to the remote device need to be review and rectified. Hence the user can check, whether review of the current state of the remote device is required or not, as at step 550. Then as at step 555, in case when the needs technician for correction, the Anomaly Correction Task (ACT) ID is generated by anomaly correction system based on the device information and/or the state information of the remote device. In case, when no notification is received, as at step 510, or when user do not open the notification alert at step 520, or when the state of the data to be shown to the user is not known as at step 540 or else, when no correction of the remote device is required, then the process can be closed as at step 530.
[0067] Referring now to FIG. 11, the anomaly correction system of the user system is configured further to perform the method 600. As at step 605, the Anomaly Correction Task (ACT) is assigned to the technician. The technician can either accept or reject the task, as at step 610. The technician is allowed to perform correction of the remote device, add work details and request for the closure of the Anomaly Correction Task (ACT), when the technician accepts the Anomaly Correction Task (ACT), as at step 620. In case when the technician rejects or reassigns the request or after completing the task, the user is allowed to review the Anomaly Correction Task (ACT), as at step 625. The ACT review, at the block 625 can be accepted by the user and then the ACT can be closed as at step 630. The user can also reassign or reopen the Anomaly Correction Task (ACT), if new state of device is not acceptable or as per specification, as at step 615.
[0068] Referring now to FIG. 12, the anomaly correction system of the user system is configured further to perform the method 700. As at step 705, the user is allowed to view the historic data or trends of the remote device, by selecting appropriate tab or button on the user screen. The user can also review the historic data or trends, as at step 710. When the ACT review is selected by the user, as at step 720, 730 the user is allowed to review Turn Around Time (TAT), Service Level Agreement (SLA) and quality of the Anomaly Correction Task (ACT) and decide on penalties or improvement measures on the Anomaly Correction Task (ACT). When the device review is selected by the user, as at step 715, 725 the user is allowed to review the device anomaly and decide on the replacement it upgradation of the remote device.
[0069] It will be appreciated that variations of the above disclosed and other features and functions, or alternatives thereof, may be desirably combined into many other different systems or applications. Also, various presently unforeseen or unanticipated alternatives, modifications, variations or improvements therein may be subsequently made by those skilled in the art which are also intended to be encompassed by the following claims.
[0070] Although embodiments of the current disclosure have been described comprehensively in considerable detail to cover the possible aspects, those skilled in the art would recognize that other versions of the disclosure are also possible.