System and method for monitoring of fire alarm systems
4 claims: 3 independent, 1 dependent
- 1System (1) zur Überwachung von Brandmeldeanlagen (2, 3, 4), aufweisend:- eine Mehrzahl von Brandmeldeanlagen (2, 3, 4), wobei jede Brandmeldeanlage (2, 3, 4) aufweist: • eine Brandmeldezentrale (5, 6, 7), • eine Mehrzahl von mit der Brandmeldezentrale (5, 6, 7) verbundene Brandmeldesensoren (8-16), • eine Alarmmeldeeinheit (17, 18, 19) zur Meldung eines Alarms an eine Leitstelle (20), und • mindestens einen Datenspeicher (21, 22, 23) mit Komponentendaten;sowie - eine Zentraleinheit (24), wobei die Zentraleinheit (24) aufweist: • eine Erfassungseinheit (25) zur Erfassung der Komponentendaten der Brandmeldeanlagen (2, 3, 4), • eine Anzeigeeinheit (26) zur Anzeige der Komponentendaten, und • eine Überprüfungseinheit (27) zur Überprüfung der Übereinstimmung der Komponentendaten mit Referenzdaten;dadurch gekennzeichnet, dass : - die Zentraleinheit (24) ferner eine Warneinheit (28) zur Ausgabe einer Warnung in Abhängigkeit von der durch die Überprüfungseinheit (27) durchgeführten Überprüfung aufweist, und - die Komponentendaten als Informationen über die jeweilige Brandmeldezentrale (5, 6, 7) und/oder die jeweiligen Brandmeldesensoren (8-16), nämlich als Statusinformationen und/oder Wartungsinformationen, ausgebildet sind.
- 2System nach Anspruch 1, wobei in den Brandmeldeanlagen (2, 3, 4) jeweils eine Mehrzahl von Datenspeichern (21, 22, 23), insbesondere in der jeweiligen Brandmeldezentrale (5, 6, 7) und in mindestens einem der jeweiligen Brandmeldesensoren (8-16), ausgebildet ist.
- 3System nach einem der vorhergehenden Ansprüche, wobei die jeweilige Brandmeldezentrale (5, 6, 7) der Brandmeldeanlagen (2, 3, 4) über eine Datenverbindung mit der Zentraleinheit (24) verbunden ist.
- 4Verfahren zur Überwachung einer Mehrzahl von Brandmeldeanlagen (2, 3, 4), wobei jede Brandmeldeanlage (2, 3, 4) aufweist:eine Brandmeldezentrale (5, 6, 7), eine Mehrzahl von mit der Brandmeldezentrale (5, 6, 7) verbundene Brandmeldesensoren (8-16), eine Alarmmeldeeinheit (17, 18, 19) zur Meldung eines Alarms an eine Leitstelle (20), und mindestens einen Datenspeicher (21, 22, 23) mit Komponentendaten, wobei das Verfahren folgende Verfahrensschritte aufweist: - Erfassen der Komponentendaten der Brandmeldeanlagen (2, 3, 4) in einer Zentraleinheit (24), wobei die Komponentendaten als Informationen über die jeweilige Brandmeldezentrale (5, 6, 7) und/oder die jeweiligen Brandmeldesensoren (8-16), nämlich als Statusinformationen und/oder Wartungsinformationen, ausgebildet sind;- Anzeigen der Komponentendaten durch eine Anzeigeeinheit (26) der Zentraleinheit (24);- Überprüfen der Übereinstimmung der Komponentendaten mit Referenzdaten;und - Ausgeben einer Warnung durch eine Warneinheit (28) der Zentraleinheit (24) in Abhängigkeit vom Ergebnis der durchgeführten Überprüfung.
Independent claims4
26 paragraphs in 1 section, as filed
0001The invention relates to a system and a method for monitoring fire alarm systems. Central monitoring of fire alarm systems is in the<patcit id="pcit0001" dnum="WO2015107449A"><text>WO 2015/107449</text></patcit> described.
0002The invention is based on the object of offering a system for monitoring fire alarm systems, which enables simple and uncomplicated monitoring of a plurality of fire alarm systems. A further object of the invention is to offer a simple and uncomplicated method for monitoring fire alarm systems.
0003This object is achieved by a system for monitoring fire alarm systems with the features of claim 1 or by a method for monitoring a plurality of fire alarm systems with the features of claim 7. Advantageous embodiments are described in the subclaims.
0004According to the invention, the system for monitoring fire alarm systems has a plurality of fire alarm systems and a central unit. Each of the fire alarm systems has a fire alarm center, a plurality of fire alarm sensors connected to the fire alarm center, an alarm alarm unit for reporting an alarm to a control center, and at least one data memory with component data. The central unit has a recording unit for recording the component data of the fire alarm systems and a display unit for displaying the component data.
0005In this way, the component data of the individual fire alarm systems are displayed centrally (in one place) by the central unit. It is not necessary to call up the component data locally from each of the plurality of fire alarm systems. This reduces the monitoring effort. For example, an operator of several fire alarm systems (e.g. Operator of an infrastructure project, regional authority, ...) get a central overview of all connected fire alarm systems, even if the individual fire alarm systems are spatially separated from each other. This simplifies monitoring.
0006Here, the component data are in particular designed as information (data) about the respective fire alarm center and / or the respective fire alarm sensors. In particular, it can be status information (current status, status of individual components, error messages) and / or maintenance information (maintenance intervals, time of next maintenance, time of last maintenance). In this way, the operator receives a central overview of the respective status of the decentralized components of a plurality of different fire alarm systems.
0007In an advantageous embodiment, the central unit also has a checking unit for checking the correspondence of the component data with reference data. In this way, it can be determined centrally whether some of the component data differ from target values or whether they correspond to specified reference data. In a particularly advantageous embodiment, the central unit also has a warning unit for outputting a warning as a function of the check carried out by the checking unit. This warning can in particular be an optical and / or acoustic warning signal or the output of an electronic warning signal. In this way, the responsible persons are made aware that certain component data deviate from reference data. Based on this warning, further actions can then be carried out (e.g. triggering maintenance if the maintenance interval is exceeded, on-site inspection if an error is reported).
0008In an advantageous embodiment, a plurality of data memories is formed in each of the fire alarm systems, in particular in the respective fire alarm center and in at least one of the respective fire alarm sensors. In this way, component data from a large number of components of a fire alarm system (namely central fire alarm and fire alarm sensors) can be monitored centrally.
0009In a particularly advantageous manner, the respective fire alarm center of the fire alarm systems is connected to the central unit via a data connection. This leads to a reliable data transmission of the component data.
0010Advantageously, parts of the central unit are designed in a local server or in the form of an IT infrastructure ("cloud") that is dynamically adapted to requirements and made available via a network.
0011In an advantageous embodiment, the component data are at least partially protected with selective access rights. In this way, data misuse or data manipulation by unauthorized persons can be prevented.
0012The method according to the invention for monitoring a plurality of fire alarm systems, each fire alarm system having a fire alarm center, a plurality of fire alarm sensors connected to the fire alarm center, an alarm reporting unit for reporting an alarm to a control center and at least one data memory with component data, has the following process steps: (1) Acquisition of the component data of the fire alarm systems in a central unit; and (2) displaying the component data by a display unit of the central processing unit.
0013In this way, the component data of the individual fire alarm systems are displayed centrally. This makes it easier to monitor multiple fire alarm systems.
0014The invention is defined by the appended claims and is explained further in the drawing using an exemplary embodiment.<dl id="dl0001" compact="compact"><dt>Fig. 1</dt><dd>shows a block diagram of a system for monitoring fire alarm systems.</dd></dl>
0015This in <figref idref="f0001">Fig. 1</figref> System 1 shown schematically for monitoring fire alarm systems has a plurality of fire alarm systems 2, 3, 4. In<figref idref="f0001">Fig. 1</figref> only three fire alarm systems 2, 3, 4 are shown here. The system 1 can, however, also comprise fewer (at least two) or more fire alarm systems. The fire alarm systems 2, 3, 4 are decentralized (ie at different locations). Each of the fire alarm systems 2, 3, 4 has at least one fire alarm center (BMZ). The fire alarm center of the fire alarm system 2 is here in<figref idref="f0001">Fig. 1</figref> with "BMZ 1" (reference number 5). The fire alarm center of the fire alarm system 3 is correspondingly designated with “BMZ 2” (reference number 6) and the fire alarm center of the fire alarm system 4 with “BMZ 3” (reference number 7).
0016Each of the fire alarm systems 2, 3, 4 has a plurality of fire alarm sensors 8 to 16 in addition to the respective fire alarm center 5, 6, 7. The fire alarm sensors 8, 9, 10 are assigned to the fire alarm system 2 and are connected to the "BMZ 1" via data connections. In a similar way, the fire alarm sensors 11, 12, 13 are part of the fire alarm system 3 and are connected to the "BMZ 2" via data connections. The fire alarm sensors 14, 15, 16 are part of the fire alarm system 4 and are connected to the "BMZ 3" via data links. For each of the fire alarm systems, three fire alarm sensors were shown. In reality, however, each of the fire alarm systems has a large number of fire alarm sensors.
0017Each fire alarm center 5, 6, 7 has an alarm signaling unit 17, 18, 19. The alarm reporting unit 17, 18, 19 detects an alarm from one of the respectively associated fire alarm sensors 8 to 16 and forwards this via communication lines, in particular directly to a control center 20 (in particular a fire brigade control center).
0018Furthermore, each fire alarm center has a data memory 21, 22, 23. Component data of the respective fire alarm system 2, 3, 4 are stored in the data memory 21, 22, 23. These are electronic data that represent information about the respective fire alarm center and / or the respective fire alarm sensors. In particular, this concerns status information (current status, status of individual components, error messages) and maintenance information (maintenance intervals, time of next maintenance, time of last maintenance) of the respective fire alarm control panel or the respective fire alarm sensors of the fire alarm system 2, 3, 4.
0019The system 1 also has a central unit 24. This central unit 24 is connected to the fire alarm systems 2, 3, 4 - more precisely to the respective fire alarm center 5, 6, 7 - by separate data connections (independent of the communication lines of the control center 20 and in particular without a connection to the alarm reporting units 17, 18 and 19). The central unit 24 has a detection unit 25, a display unit 26, a checking unit 27 and a warning unit 28.
0020The acquisition unit 25 is designed to acquire the component data stored in the data memories 21, 22, 23 (e.g. by reading out the data memories 21, 22, 23) and to hold them centrally in the central unit 24 (e.g. by storing in a, in <figref idref="f0001">Fig. 1</figref> data memory of the central unit 24, not shown).
0021The display unit 26 is designed to display the component data acquired and held by the acquisition unit 25 (for example on a screen).
0022The checking unit 27 is designed to check whether individual component data with reference data that are stored in the central unit 24, for example in the in <figref idref="f0001">Fig. 1</figref> not shown data memory are stored, match or differ from these reference data.
0023The warning unit 28 is designed to output a warning (in particular an optical and / or acoustic warning signal) if the checking unit has determined a deviation of certain component data from the reference data.
0024In the system 1, the component data of the individual fire alarm systems 2, 3, 4 are thus displayed centrally (at one location) by the display unit 26 of the central unit 24. It is not necessary to view the component data in a decentralized manner for each of the plurality of fire alarm systems 2, 3, 4. This reduces the monitoring effort. The checking unit 27 can be used to determine centrally whether individual component data differ from setpoint values or match the given reference data. By means of the warning unit 28, the persons responsible are made aware that certain component data deviate from reference data.
0025In the in <figref idref="f0001">Fig. 1</figref> The illustrated embodiment, the data memory 21, 22, 23 of the fire alarm system 2, 3, 4 is arranged in the respective fire alarm center 5, 6, 7. This data memory 21, 22, 23 can also contain information about the fire alarm sensors 8 to 16 connected to the fire alarm center 5, 6, 7. However, it is also possible that in some or all of the fire alarm sensors 8 to 16 separate (additional) data memories are formed in which the component data of the respective fire alarm sensors 8 to 16 are stored.
REFERENCE LIST
0026<dl id="dl0002" compact="compact"><dt>1</dt><dd>System for monitoring fire alarm systems</dd><dt>2, 3, 4</dt><dd>Fire alarm system</dd><dt>5, 6, 7</dt><dd>Fire alarm center (BMZ)</dd><dt>8 - 16</dt><dd>Fire alarm sensor</dd><dt>17, 18, 19</dt><dd>Alarm reporting unit</dd><dt>20</dt><dd>Control center</dd><dt>21, 22, 23</dt><dd>Data storage</dd><dt>24</dt><dd>Central unit</dd><dt>25</dt><dd>Registration unit</dd><dt>26</dt><dd>Display unit</dd><dt>27</dt><dd>Verification unit</dd><dt>28</dt><dd>Warning unit</dd></dl>
1 sheet
Sheet 1
Every citation, both ways
| Document | Relation | Office | Cited during |
|---|---|---|---|
| EP4462400A1 | Cited by | European Patent Office (EPO) | Search report |
| EP1845499A2 | Cites | European Patent Office (EPO) | Filed by opponent |
| US2007139183A1 | Cites | United States of America | Filed by opponent |
| US2008262816A1 | Cites | United States of America | Filed by opponent |
| US2008262816A1 | Cites | United States of America | Filed by opponent |
| US2008262816A1 | Cites | United States of America | Filed by opponent |
| US2008309486A1 | Cites | United States of America | Filed by opponent |
| WO2011109622A2 | Cites | World Intellectual Property Organization (WIPO) | Filed by opponent |
| WO2011128100A1 | Cites | World Intellectual Property Organization (WIPO) | Filed by opponent |
| US2013321161A1 | Cites | United States of America | Filed by opponent |
| US2013321161A1 | Cites | United States of America | Filed by opponent |
| US2013321161A1 | Cites | United States of America | Filed by opponent |
| WO2014044675A1 | Cites | World Intellectual Property Organization (WIPO) | Filed by opponent |
| WO2014044675A1 | Cites | World Intellectual Property Organization (WIPO) | Filed by opponent |
| WO2014044818A1 | Cites | World Intellectual Property Organization (WIPO) | Filed by opponent |
| WO2014044818A1 | Cites | World Intellectual Property Organization (WIPO) | Filed by opponent |
| WO2014044818A1 | Cites | World Intellectual Property Organization (WIPO) | Filed by opponent |
| WO2015048894A1 | Cites | World Intellectual Property Organization (WIPO) | Filed by opponent |
| WO2015048894A1 | Cites | World Intellectual Property Organization (WIPO) | Filed by opponent |
| US2015097664A1 | Cites | United States of America | Filed by opponent |
| US2015097664A1 | Cites | United States of America | Filed by opponent |
| WO2015107449A1 | Cites | World Intellectual Property Organization (WIPO) | Filed by opponent |
| WO2015107449A1 | Cites | World Intellectual Property Organization (WIPO) | Filed by opponent |
| AT501215B1 | Cites | Austria | Filed by opponent |
| US5686896A | Cites | United States of America | Filed by opponent |
| US5686896A | Cites | United States of America | Filed by opponent |
| US6078050A | Cites | United States of America | Filed by opponent |
| US6989756B2 | Cites | United States of America | Filed by opponent |
| US6989756B2 | Cites | United States of America | Filed by opponent |
| US8836467B1 | Cites | United States of America | Filed by opponent |
| US8836467B1 | Cites | United States of America | Filed by opponent |
| WO2014044818A1 | Cites | World Intellectual Property Organization (WIPO) | – |
| WO2015107449A1 | Cites | World Intellectual Property Organization (WIPO) | – |
| US2008262816A1 | Cites | United States of America | – |
| US2013321161A1 | Cites | United States of America | – |
| MULLER R., HUPPI S.: "Fire Tablet plus, Mobiles Service interface zu Siemens Brandmeldeanlagen Bachelorarbeit", HSR, HOCHSCHULE FUR TECHNIK, 2011, pages 1 - 102, XP055841334 | Non-patent | – | Filed by opponent |
| Stellungnahme der Patentinhaberin im Prufungsverfahren | Non-patent | – | Filed by opponent |
| Brandmelderzentrale Serie BC216 Handbuch Teil A | Non-patent | – | Filed by opponent |
| Brandmelderzentrale Serie BC216 Handbuch Teil C | Non-patent | – | Filed by opponent |
| ALVIS 3.2 New Features | Non-patent | – | Filed by opponent |
| Handbuch ADM Melder fur Vorgangersystem LBC1000 | Non-patent | – | Filed by opponent |
| Vortrag REACT | Non-patent | – | Filed by opponent |
| Tagesordnung zur Sitzung des FA Brandmeldetechnik am 14. 10.2015 | Non-patent | – | Filed by opponent |
| Protokoll + Teilnehmerliste zur Sitzung des FA Brandmeldetechnik am 14.10 | Non-patent | – | Filed by opponent |
| Produktinformation SMS2-1 | Non-patent | – | Filed by opponent |
| Katalog Brandmeldetechnik 2007/2008 | Non-patent | – | Filed by opponent |
| SMS/ E-Mail -Sendermodul SMS2-1 Beschreibung | Non-patent | – | Filed by opponent |
| Einsatzleitsystem ALVIS 3.0 | Non-patent | – | Filed by opponent |
| Integral remote : Femzugriff auf Brandmeldezentralen | Non-patent | – | Filed by opponent |
| Produktbeschreibung Esser remote access (September 2014) | Non-patent | – | Filed by opponent |
| Produktbeschreibung Siemens Sinteso FS20 (Mai 2015) | Non-patent | – | Filed by opponent |
| ANONYMOUS: "Sinteso FS20-Zentralen – klares Konzept, effiziente Bedienung", SIEMENS, 1 January 2015 (2015-01-01), pages 1 - 16, XP055844000 | Non-patent | – | Filed by opponent |
| ANONYMOUS: "FC2020-CZ, FC2020-CC", SIEMENS, 1 January 2014 (2014-01-01), pages 1 - 10, XP055844003, Retrieved from the Internet <URL:https://ch.bt-pip.com/uploads/master/product/documents/fc2020cc_fc2020cc_023_02_de.pdf> [retrieved on 20210923] | Non-patent | – | Filed by opponent |
| KÖNINGS OLIVER: "BMACLOUD für Errichter erstellen sie ihre Prüfplan online und bei der Wartung füllen Sie diese per App aus", BMACLOUD, 1 January 2014 (2014-01-01), pages 1 - 11, XP055844008 | Non-patent | – | Filed by opponent |
| ANONYMOUS: "Brandmeldeanlagen - Teil 2: Brandmelderzentralen; Deutsche Fassung DIN EN 54-2:1997", DEUTSCH NORM, 1 January 1997 (1997-01-01), pages 1 - 27, XP055844012 | Non-patent | – | Filed by opponent |
| ANONYMOUS: "Brandmeldeanlagen - Teil 2: Brandmelderzentralen; Deutsche Fassung DIN EN 54-2:1997/A1", DEUTSCHE NORM, 1 January 2006 (2006-01-01), pages 1 - 42, XP055844015 | Non-patent | – | Filed by opponent |
| ANONYMOUS: "Messe-Highlight Aplis Aplis", RE GRAPH GRAPHISCHE INFOSYSTEME, GEORG THIEME VERLAG KG, STUTTGART · NEW YORK, 1 September 2014 (2014-09-01), Stuttgart · New York, pages 1 - 2, XP055844020, Retrieved from the Internet <URL:https://www.regraph.de/news_files/Highlights.pdf> [retrieved on 20210923], DOI: 10.1055/s-0034-1393880 | Non-patent | – | Filed by opponent |
2 members in 1 office; this record represents the family
Priority claims2
| Document | Office | Kind | Date |
|---|---|---|---|
| 15201952 | European Patent Office (EPO) | A | |
| EP20150201952 | – | – | – |
Members2
| Document | Office | Kind | |
|---|---|---|---|
| EP3185228A1 | European Patent Office (EPO) | A1 | |
| EP3185228B1This record | European Patent Office (EPO) | B1 |
89 legal events, as 10 offices reported them to INPADOC
Over the term
Point at a mark for the eventEvents
| Event | Code | Office | |
|---|---|---|---|
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Revocation of the patentMA03 | MA03 | AT | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Patent revokedRevoked27W | 27W | EP | |
| Gb: patent revoked under art. 102 of the ep convention designating the uk as contracting stateRevokedGBPR | GBPR | EP | |
| Revoked following oppositionRevokedMGE | MGE | FI | |
| Lapse because of not paying annual feesLapsedMM01 | MM01 | AT | |
| Lapsed because of non-payment of the annual feeLapsedMM | MM | NL | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Patent ceasedCeasedPL | PL | CH | |
| Patent revokedRevokedORIGINAL CODE: 0009271RDAG | RDAG | EP | |
| Information on the status of an ep patent application or granted ep patentGrantedSTATUS: PATENT REVOKEDSTAA | STAA | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Epo's revocation decision now finalR064 | R064 | DE | |
| Patent revoked by epoRevokedR103 | R103 | DE | |
| Communication despatched that patent is revokedRevokedORIGINAL CODE: EPIDOSNREV1RDAF | RDAF | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Opposition filedOpposition26 | 26 | EP | |
| Opposition filedOpposition26 | 26 | EP | |
| Opposition filedOpposition26 | 26 | EP | |
| Opposition filedOpposition26 | 26 | EP | |
| Opposition filedOpposition26 | 26 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Notice of opposition and request to file observation + time limit sentOppositionORIGINAL CODE: EPIDOSNOBS2PLAX | PLAX | EP | |
| Opposition filedOppositionORIGINAL CODE: 0009260PLBI | PLBI | EP | |
| Lapsed because of non-payment of the annual feeLapsedMM | MM | BE | |
| Opposition filedOppositionORIGINAL CODE: 0009260PLBI | PLBI | EP | |
| Opposition filed against patentOppositionR026 | R026 | DE | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Patent ceasedCeasedPL | PL | CH | |
| Invalidation of extension of european patentsMG9D | MG9D | LT | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Annual fee paid to national office [announced via postgrant information from national office to epo]GrantedPGFP | PGFP | EP | |
| Annual fee paid to national office [announced via postgrant information from national office to epo]GrantedPGFP | PGFP | EP | |
| Annual fee paid to national office [announced via postgrant information from national office to epo]GrantedPGFP | PGFP | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Annual fee paid to national office [announced via postgrant information from national office to epo]GrantedPGFP | PGFP | EP | |
| Annual fee paid to national office [announced via postgrant information from national office to epo]GrantedPGFP | PGFP | EP | |
| Translation for ep filed (entry of ep into country)FP | FP | NL | |
| European patents granted designating irelandGrantedLANGUAGE OF EP DOCUMENT: GERMANFG4D | FG4D | IE | |
| Dpma publication of mentioned ep patent grantGrantedR096 | R096 | DE | |
| European patent takes effect as a national patent in ch/liEP | EP | CH | |
| Reference to at number (ep patent validated in austria)REF | REF | AT | |
| Designated contracting statesAK | AK | EP | |
| European patent grantedGrantedNOT ENGLISHFG4D | FG4D | GB | |
| (expected) grantORIGINAL CODE: 0009210GRAA | GRAA | EP | |
| Information on the status of an ep patent application or granted ep patentGrantedSTATUS: THE PATENT HAS BEEN GRANTEDSTAA | STAA | EP | |
| Grant fee paidORIGINAL CODE: EPIDOSNIGR3GRAS | GRAS | EP | |
| Intention to grant announcedINTG | INTG | EP | |
| Information on inventor provided before grant (corrected)RIN1 | RIN1 | EP | |
| Despatch of communication of intention to grant a patentORIGINAL CODE: EPIDOSNIGR1GRAP | GRAP | EP | |
| Information on the status of an ep patent application or granted ep patentGrantedSTATUS: GRANT OF PATENT IS INTENDEDSTAA | STAA | EP | |
| Request for examination filed17P | 17P | EP | |
| Designated contracting states (corrected)RBV | RBV | EP | |
| Information on the status of an ep patent application or granted ep patentGrantedSTATUS: REQUEST FOR EXAMINATION WAS MADESTAA | STAA | EP | |
| Designated contracting statesAK | AK | EP | |
| Request for extension of the european patentAX | AX | EP | |
| Public reference made under article 153(3) epc to a published international application that has entered the european phaseORIGINAL CODE: 0009012PUAI | PUAI | EP | |
| Information on the status of an ep patent application or granted ep patentGrantedSTATUS: THE APPLICATION HAS BEEN PUBLISHEDSTAA | STAA | EP |
Numbers
- Publication
- 3185228
- Publication, DOCDB
- 3185228
- Publication, EPODOC
- EP3185228
- Application
- 152019527
- Application, DOCDB
- 15201952
- Application, EPODOC
- EP20150201952
Titles3
- German
- SYSTEM UND VERFAHREN ZUR ÜBERWACHUNG VON BRANDMELDEANLAGEN
- English
- SYSTEM AND METHOD FOR MONITORING OF FIRE ALARM SYSTEMS
- French
- SYSTEME ET PROCEDE DE SURVEILLANCE D'INSTALLATIONS DE DETECTION D'INCENDIE
Classification
- CPC, 1
- G08B29/145
- IPC, 1
- G08B29 14
Designated states38
- Contracting states, 38
- Albania
- Austria
- Belgium
- Bulgaria
- Switzerland
- Cyprus
- Czechia
- Germany
- Denmark
- Estonia
- Spain
- Finland
- France
- United Kingdom
- Greece
- Croatia
- Hungary
- Ireland
- Iceland
- Italy
- Liechtenstein
- Lithuania
- Luxembourg
- Latvia
and 14 moreShow fewer
- Monaco
- North Macedonia
- Malta
- Netherlands (Kingdom of the)
- Norway
- Poland
- Portugal
- Romania
- Serbia
- Sweden
- Slovenia
- Slovakia
- San Marino
- Türkiye
