# US 2018/0025618 A1 · Multi alarm remote monitoring system > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 2018/0025618 A1 - Document ID: US20180025618A1 - Status: Published application - Kind: A1 - Application number: 15/539,296 - Filed: 2015-12-29 - Published: 2018-01-25 - Earliest claimed: 2014-12-29 - Assignees: Sprue Safety Products Ltd. - Applicants: Sprue Safety Products Ltd. - Inventors: Nicholas Rutter; Chris Bolger; Peter Brigham - Web page: https://patentgrep.com/patent/US20180025618A1 ## CPC - G08B 25/006: {Alarm destination chosen according to type of event, e.g. in case of fire phone the fire service, in case of medical emergency phone the ambulance} - G08B 25/14: Central alarm receiver or annunciator arrangements - G08B 31/00: Predictive alarm systems characterised by extrapolation or other computation using updated historic data - G08B 21/0423: {detecting deviation from an expected pattern of behaviour or schedule} - G08B 25/08: using communication transmission lines {(G08B13/19658, G08B21/0286, G08B25/016 take precedence)} - G08B 29/02: Monitoring continuously signalling or alarm systems - G08B: SIGNALLING SYSTEMS, e.g. PERSONAL CALLING SYSTEMS; ORDER TELEGRAPHS; ALARM SYSTEMS ## Abstract A remote alarm monitoring system (10) for recording and processing alarm event data. The alarm system (10) comprises one or more alarm devices (12) in connection with an interface (14), wherein the interface (14) is configured to receive alarm event data; a server (18) in communication with the interface (14), wherein the server (18) is configured to receive and process alarm event data from the interface (14); and one or more networked client devices (22) in communication with the server (18), wherein the server (18) is configured to transmit a message to the networked client device (22), said message based upon the processed alarm event data. ## Claims ### Claim at position 1 1-14. (canceled) ### Claim 15 A remote alarm monitoring system for recording and processing alarm event data, the alarm system comprising: at least one alarm device in connection with an interface, wherein the interface is configured to receive alarm event data; a server in communication with the interface, wherein the server is configured to receive and process alarm event data from the interface; and at least one networked client device in communication with the server, wherein the server is configured to transmit a message to the networked client device, said message based upon the processed alarm event data. ### Claim 16 (depends on 15) The alarm system according to claim 15, wherein the processed alarm event data is based on an analysis of at least one of the pattern and the frequency of alarm events and an assessment of a level of risk based on the analysis results. ### Claim 17 (depends on 15) The alarm system according to claim 15, wherein the processed alarm event data is based on an analysis of the type of alarm events and an assessment of a level of risk based on the analysis results. ### Claim 18 (depends on 15) The alarm system according to claim 15, wherein each of the at least one alarm devices is configured to store alarm event data, the alarm event data including activation of an alarm, test procedures on the alarm or a malfunction of the alarm for transmission to the server. ### Claim 19 (depends on 16) The alarm system according to claim 16, wherein the analysis of at least one of the pattern and the frequency of alarm events takes into account non-hazardous alarm events. ### Claim 20 A server for processing alarm event data, the server configured to: receive alarm event data from an alarm installation via an interface; analyse at least one of the pattern, the frequency and the type of alarm events; compare the analysed data with pre-determined criteria; and transmit a message to networked client device based on results of the comparison. ### Claim 21 (depends on 20) The server according to claim 20, wherein the step of comparing the analysed alarm event data with the pre-determined criteria results in a risk-level specific to the installation. ### Claim 22 (depends on 20) The server according to claim 20, wherein the pre-determined criteria includes stored historical data specific to the associated installation. ### Claim 23 (depends on 21) The server according to claim 21, wherein the pre-determined criteria includes ongoing analysis of at least one of the pattern, the frequency, and the type of the alarm event data of the associated installation. ### Claim 24 (depends on 20) The server according to claim 20, wherein in analysing at least one of the pattern and the frequency of alarm events, the server takes into account at least one of the number and the type of non-hazardous alarm events. ### Claim 25 A method for remotely monitoring alarms, comprising the steps of: receiving alarm event data at an interface from at least one alarm device; transferring alarm event data from the interface to a server; processing the alarm event data; and transmitting a message to at least one networked client device based on the processed alarm event data. ### Claim 26 (depends on 25) The method according to claim 25, wherein the step of processing the alarm event data comprises: analysing at least one of the pattern, the frequency and the type of alarm events; assessing the level of risk based on the analysis results. ### Claim 27 (depends on 26) The method according to claim 26, further comprising the step of: storing alarm event data locally at the at least one alarm device for transmission to the server. ### Claim 28 (depends on 26) The method according to claim 26, wherein the step of analysing at least one of the pattern and the frequency of alarm events takes into account at least one of the number and the type of non-hazardous alarm events.