EP2533118A1 - Système de gestion d'alarmes installé sur un site pour la gestion des composants source d'alarme - Google Patents

Système de gestion d'alarmes installé sur un site pour la gestion des composants source d'alarme Download PDF

Info

Publication number
EP2533118A1
EP2533118A1 EP11169544A EP11169544A EP2533118A1 EP 2533118 A1 EP2533118 A1 EP 2533118A1 EP 11169544 A EP11169544 A EP 11169544A EP 11169544 A EP11169544 A EP 11169544A EP 2533118 A1 EP2533118 A1 EP 2533118A1
Authority
EP
European Patent Office
Prior art keywords
alarm
component
service
source
asc
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Withdrawn
Application number
EP11169544A
Other languages
German (de)
English (en)
Inventor
Thomas Gehrke
Gianluca Mazzimini
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Siemens AG
Original Assignee
Siemens AG
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Siemens AG filed Critical Siemens AG
Priority to EP11169544A priority Critical patent/EP2533118A1/fr
Publication of EP2533118A1 publication Critical patent/EP2533118A1/fr
Withdrawn legal-status Critical Current

Links

Images

Classifications

    • G—PHYSICS
    • G05—CONTROLLING; REGULATING
    • G05B—CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
    • G05B23/00—Testing or monitoring of control systems or parts thereof
    • G05B23/02—Electric testing or monitoring
    • G05B23/0205—Electric testing or monitoring by means of a monitoring system capable of detecting and responding to faults
    • G05B23/0208—Electric testing or monitoring by means of a monitoring system capable of detecting and responding to faults characterized by the configuration of the monitoring system
    • G05B23/0216—Human interface functionality, e.g. monitoring system providing help to the user in the selection of tests or in its configuration

Definitions

  • the invention relates to an alarm management system installed on a site for managing alarm source components.
  • One important aspect in the field of building technologies and other business domains is a reliable and fast detection of events occurring in various parts of a site.
  • the events differ in their cause and importance and are detected by a variety of sensors and devices, each type of sensor being designed for a special event type. Examples of events are: fire, smoke, intrusion, water leak. Therefore, a variety of types of detector objects exist, like fire detectors, motion detectors, etc.
  • a wide-spread solution to monitor the events is by installing cameras throughout the site, such that especially sensitive environments, like high-security access points, can be surveyed. Data, like still images or live video transmitted from the cameras are collected into a central surveillance entity like a management station, where they are monitored in real time and recorded for backup purposes.
  • a problem related to this solution is the complexity of such systems, especially systems covering large sites, thus requiring a high amount of cameras and detection objects. All surveyed areas can hardly be monitored at once, thus, in many cases, views of the surveyed areas are shown sequentially on monitoring means. This fact introduces delays between subsequent views of a same surveyed area resulting in a late reaction to an event which occurred in that area.
  • the alarm service is a core component in building technology management systems.
  • An platform used for this management task would like to be used by a business unit that wants to build a product for managing either simply and complex systems including the alarm management.
  • the alarm management might be very different (e.g. fire alarm noticed by a smoke detector in a danger management system requires a different treatment compared to light fault detected by train's car in a transportation system).
  • an alarm management system installed on a site for managing alarm source components, comprising:
  • This system provides an alarm service business logic component that is able to handle the pluggable alarm state machine components.
  • a standard alarm state machine component for handling most of the alarm source notification can be provided accompanied by one or more customized alarm state machine components for handling distinct type of alarms (distinct alarm types).
  • Such components can be implemented and plugged by just adjusting the alarm service configuration file without the need of changing the existing code of the alarm service business logic component.
  • a preferred embodiment of the present invention will provide an interface of the alarm state machines providing at least one method for:
  • the alarm service business logic component takes advantage of operating procedures for treating the alarm events by means of a predefined workflow, including which part of a treatment users are expected to do, and when they are supposed to do it. Therefore, the system further comprises an operating procedure business logic component that manages at least one operating procedure which enables an arbitrary combination of the alarm management of different alarm source components. Therefore, the operating procedure enables interconnection/meshing of alarm services that would be loosely coupled without the design of the operating procedure business logic. Thereby, services are brought together that have an intentional logical/ functional relationship among each other. In order to suffice on the demand of flexibility within the system, a preferred embodiment of the present invention provides for the operation of the operating procedure business logic component by pluggable operating procedure state machine components.
  • the alarm management system has to fulfil the need for aggregating alarms and for managing the communication of the alarm source notifications throughout the communication nodes in the alarm management system. Therefore, a further preferred embodiment of the present invention is realized when the alarm service business logic component comprises an alarm hierarchy service; said alarm hierarchy service being enabled to aggregate alarm source notifications and to generate summery alarms by using directed acyclic graph topologies. Therefore, it is further advantageous when the alarm service hierarchy supports the supply of alarm state machines which determine the aggregation of the alarm source notifications and the propagation thereof within the alarm service business logic component. The collection, the aggregation and the propagation of the alarm source notifications can therefore be changed in a simple way just by modifying/replacing the pluggable alarm hierarchy state machine component. A default plug-in can be provided though custom ones can be easily added by the final user/business unit.
  • the alarm hierarchy service is further able to handle a bundle of hierarchies which means multiple hierarchies can be managed simultaneously.
  • a further preferred embodiment of the present invention will decouple the alarm source component and the alarm service business logic component by designing the alarm service configuration file in a way that it is further adjustable to comprise the configuration file of the alarm source components.
  • the alarm source components are configured in the alarm service business logic component thereby enabling to add and/or remove an alarm source component by downloading an amended configuration file of the alarm source components without restarting the service or the entire system.
  • Figure 1 shows schematically the architecture of an alarm management system AMS comprising an alarm consumer/client AC, an alarm service AS and at least one alarm producer AP.
  • the alarm consumer AC is the client that subscribes to the alarm service AS.
  • the alarm consumer AC comprises an alarm consumer business logic AC_BL and an alarm consumer interface ACI that substantially is the interface for interacting with the alarm service AS.
  • the alarm consumer business logic AC_BL comprises all the software routines that are required to receive and represent alarm notifications to the extent both authorized and desired.
  • the alarm consumer is typically executed on a personal computer, laptop, PDA, mobile display, mobile phone and the like.
  • the alarm producer AP comprises an alarm source component ASC, such as a smoke detector, intrusion detector, motion detector, gas sensor, humidity detector or the like, and a respective alarm source interface ASI for the communication with the alarm service AS.
  • ASC alarm source component
  • ASI alarm source interface
  • the alarm service AS comprises as core components an alarm service business logic AS_BL, at least one alarm state machine component ASM with an respective alarm state machine plug-in ASM_PI where the alarm state machine components can be plugged in, and a managed object component MOC.
  • the alarm service business logic AS_BL is a software routine that handles any type of alarm source notification and the processing thereof.
  • the alarm service business logic AS_BL is further able to handle the pluggable alarm state machine components ASM.
  • the alarm service business logic AS_BL processes incoming alarm source notifications (COSA) form the alarm source components ASC and the outgoing alarm notifications (COA) to the alarm consumer/client AC. It further processes any incoming operation request which is a command or an operation from the alarm consumer/client AC and the outgoing operation requests to the alarm source components ASC. Besides these tasks, the alarm service business logic AS_BL is responsible for invoking the pertinent alarm state machine ASM when changes in the alarm occur.
  • COSA incoming alarm source notifications
  • COA outgoing alarm notifications
  • the alarm state machine component ASM is the pluggable component that can be used to control the alarm lifecycle.
  • a reference alarm state machine is provided to the alarm service AS, but an arbitrary and optional number of customized alarm state machines can be added. Since the alarm state machine components ASM are implemented as plug-ins to assure the adaptability of the alarm service AS to different user's concepts and needs. Its representation is stateless since all the information of interest in the alarm state machine is stored in alarm instances.
  • the alarm state machine components ASM receive all the alarm related information from the alarm service business logic AS_BL as input parameters and operates with them according to the state diagram changing their value if required by the ASM-specific alarm related rules. An alarm state machine then delivers this value back to the alarm service business logic AS_BL which stores the values in the managed object component MOC.
  • the managed object component MOC is used as a data repository for managing both the alarm type information and the alarm object instance information (alarm objects generated at runtime).
  • the managed object component MOC further comprises alarm related information generated by the alarm source components ASC und represented by an alarm service object extension (ASOE) which represent themselves static and dynamic attribute of an alarm source notification. It further acts as a dispatcher for notifying changes in the alarm objects.
  • ASOE alarm service object extension
  • the alarm state machine component ASM is made pluggable by means of the configuration of the alarm management system AMS and the configuration of the alarm service AS therein.
  • the alarm service types can be changed that are linked to the alarm state machines during runtime.
  • an alarm object is created, such an alarm is associated to the proper alarm state machine component ASM by means of the alarm type the alarm refers to.
  • the interface of the alarm state machine components provides methods for:
  • FIG. 2 schematically show in the schema of a MS Windows® page an example of the alarm service configuration file ASCF, hereinafter referred to as system configuration file.
  • the system configuration file comprises three distinct alarm state machine components: DefaultStateMachine, FnFStateMachine and SBTStateMachine.
  • DefaultStateMachine DefaultStateMachine
  • FnFStateMachine FnFStateMachine
  • SBTStateMachine Using the respective development studio, it is possible to add new alarm state machine components, and remove and/or modify existing alarm state machine components ASM.
  • the displayed mask gives a self-explaning structure of the configuration options for the alarm state machine component as well as for any other state machine that will be mentioned below.
  • the present example shows a default alarm state machine but other alarm state machine component can be configured in a customizable way, such as the FnFStateMachine or the SBTStateMachine.
  • Each alarm state machine instance must have a distinct name, but all of them shall provide the IA
  • the present invention provides the following advantages to the final users of the alarm service AS.
  • the final user has a quick and clean way for supporting a new alarm type that requires a specific management.
  • the new alarm management system AMS allows for a varied alarm handling approach through an unique alarm service (AS) and one or more flexible, inter-changeable and pluggable alarm state machine components ASM.
  • AS unique alarm service
  • ASM flexible, inter-changeable and pluggable alarm state machine components
  • FIG. 3 now provides a schematic overview on the architecture of the above-mentioned operating procedure service OPS which combines workflow techniques with SOA techniques.
  • the operating procedure OP enables interconnecting/meshing of arbitrary services, such as the alarm service AS, that would be otherwise only loosely coupled with it. This feature allows to bring together services that have a logical/functional relationship with each other.
  • the operating procedure service OPS has a similar architecture like the alarm management system AMS of Figure 1 or in other words, the distinct services, such as the alarm service AS, are created in the environment of the provided operating procedure service OPS.
  • different services can use the same hardware components such as the MOC as repository.
  • An Operating Procedure instance is associated with, for instance, an alarm through its alarm type, and can be engineered specifying the number of operating instructions that compose the alarm service procedure, the execution order, the operating instruction execution type and other attributes that control its behaviour.
  • OP consumers typically alarm service consumer AC
  • Operating Procedure Business Logic OP BL Operating Procedure is a mandatory com-ponent that is used to manage workflows for assisted alarm treatment which is defined as a sequence of treatment and inspection steps, each representing one task that the user has to perform or the system automatically executes to treat an alarm.
  • the operating procedure business logic support multiple steps (as plug-ins) .
  • Operating Procedure RSI The role-specific Operating procedure interface is a mandatory component which is used to handle operating pro-cedure notifications and the corre-sponding subscription sessions to the client. The clients can also send com-mands that control the operating proce-dure executions by means of this inter-face.
  • Operating Procedure plug-in The Operating Procedure state machine is a mandatory component which is in charge of handling the operating proce-dure instance states.
  • the operating procedure step is an op-tional component which is in charge of executing a specific step of the oper-ating procedure workflow, for instance view a map, send an SMS or e-mail, dis-play CCTV video, and so forth. These components are implemented as plug-ins to ensure the adaptability of the Oper-ating Procedure to different final user concepts.
  • Managed Object Com-ponent The MOC mandatory component manages OP objects like OP types, OP step types, and OP instances created at runtime. MOC persistency An optional component that persists managed objects.
  • the role-specific Alarm Source inter-face is a mandatory component which is used for creating alarms related to un-expected behaviour on OP execution.
  • Activation RSI The role-specific Activation Interface is a mandatory component which is used to activate a specific version of a configuration (of an alarm service, for example).
  • Configuration RSI-D The Alarm Source uses the mandatory Configuration delegate interface which gets access to its runtime configura-tion data from the local C&A service. The configuration data are cached lo-cally in the service through the C&A controller.
  • C&A controller The C&A controller (CAC) is a mandatory component which manages all activities regarding the changes of a service con-figuration inside a service itself.
  • MOC XML Importer creates new trans-action, imports new configuration data into MOC, commits and close transac-tions.
  • FIG 4 schematically illustrates the architecture of an Alarm hierarchy Service AHS that is constructed similar to the architecture of the Operating Procedure Service OPC and the alarm service AS.
  • the alarm hierarchy service AHS is an important, but optional, feature with the alarm service AS and makes allowance for the aggregation of alarm information (i.e. simple COA alarm notification coming from the Alarm Service AS) and the generation of summary alarms (i.e. summary COSA alarm source notification going to the Alarm Service AS) by using directed acyclic graph topologies as illustrated in Figure 5 .
  • the alarm hierarchy service AHS supports the capability to supply pluggable components to the alarm hierarchy business logic which decides how alarm information is aggregated and disseminated at each node.
  • the alarm hierarchy service AHS implements a virtual alarm service in charge of collecting different alarms on different hierarchy levels by subscribing to the respective alarms generated by alarm service instances; thereby acting as an agent delivering a collection of aggregated alarms transparently to the alarm service clients AC.
  • the present alarm hierarchy service AHS offers the following advantages to the final users.
  • the collection, aggregation and propagation of the alarm instances can be changed in an easy way by modifying/replacing the pluggable alarm hierarchy state machine.
  • the alarm service AS and the operating procedure service OP a default plug-in for the alarm hierarchy state machine is provided though custom ones can be easily added by the final user.
  • the alarm hierarchy service AHS is able to handle a bunch of hierarchies which means multiple hierarchies can be managed the same time by an appropriate design of the alarm hierarchy state machines. Further, the performances of the alarm service AS are not affected by any alarm hierarchy elaboration since the entire process takes place in a distinct service.
  • Fig. 5 shows an exemplary handling of summary alarms.
  • Summary alarms are generated using alarm hierarchies.
  • Alarm hierarchies are maintained in a specific Alarm Hierarchy Component. This component is connected to the Alarm Service as an alarm client, i.e. the Alarm Hierarchy Component subscribes to the alarms and receives the corresponding alarm events from the Alarm Service.
  • the Alarm Hierarchy Component contains one or several alarm hierarchies.
  • An alarm hierarchy consists of a directed acyclic graph of alarm hierarchy objects (AHOs).
  • AHO 3 represents the alarm at the lowest levels in the hierarchies
  • the AHOs of each level the of the alarm hierarchy are connected to the next upper level by logical relationsships (e.g. the boolean operators "and", "or” or "xor"). In accordance with these relationships, the alarm is propagated through the different levels of the hierarchies.
  • the AHO can raise a summary alarm that is sent to the Alarm Service.
  • the Alarm Hierarchy Component is also an alarm source.
  • the example in Fig. 5 shows that an alarm is received by the Alarm Hierarchy Component and mapped to AHO 3. Then the alarm is propagated in accordance with the relationships between the AHOs to AhoO 5 and then to AHO 6.
  • AHO 6 is configured to send a summary alarm the Alarm Service.
  • the different alarm hierarchies in the Alarm Hierarchy Component are configurable.

Landscapes

  • Engineering & Computer Science (AREA)
  • Human Computer Interaction (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Automation & Control Theory (AREA)
  • Alarm Systems (AREA)
EP11169544A 2011-06-10 2011-06-10 Système de gestion d'alarmes installé sur un site pour la gestion des composants source d'alarme Withdrawn EP2533118A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
EP11169544A EP2533118A1 (fr) 2011-06-10 2011-06-10 Système de gestion d'alarmes installé sur un site pour la gestion des composants source d'alarme

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
EP11169544A EP2533118A1 (fr) 2011-06-10 2011-06-10 Système de gestion d'alarmes installé sur un site pour la gestion des composants source d'alarme

Publications (1)

Publication Number Publication Date
EP2533118A1 true EP2533118A1 (fr) 2012-12-12

Family

ID=44484916

Family Applications (1)

Application Number Title Priority Date Filing Date
EP11169544A Withdrawn EP2533118A1 (fr) 2011-06-10 2011-06-10 Système de gestion d'alarmes installé sur un site pour la gestion des composants source d'alarme

Country Status (1)

Country Link
EP (1) EP2533118A1 (fr)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
DE102019111854A1 (de) * 2019-05-07 2020-11-12 Minimax Viking Research & Development Gmbh Konfigurationssystem und Computerprogrammprodukt zur Konfiguration einer Zentrale
CN112829956A (zh) * 2021-01-14 2021-05-25 中国商用飞机有限责任公司 目标可配置的机组告警系统及用于其的配置方法

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5768119A (en) * 1996-04-12 1998-06-16 Fisher-Rosemount Systems, Inc. Process control system including alarm priority adjustment
WO2007024622A2 (fr) * 2005-08-22 2007-03-01 American Standard International, Inc. Gestion de donnees de systeme de controle automatique de batiments
EP1813999A1 (fr) * 2006-01-24 2007-08-01 Yokogawa Electric Corporation Dispositif et procédé pour le traitement d'informations d'alarmes
US20080255681A1 (en) * 2007-04-10 2008-10-16 Cindy Alsup Scott Methods and apparatus to manage process plant alarms
US20090278680A1 (en) * 2006-12-21 2009-11-12 Abb Technology Ag Method and device for optimizing the alarm configuration

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5768119A (en) * 1996-04-12 1998-06-16 Fisher-Rosemount Systems, Inc. Process control system including alarm priority adjustment
WO2007024622A2 (fr) * 2005-08-22 2007-03-01 American Standard International, Inc. Gestion de donnees de systeme de controle automatique de batiments
EP1813999A1 (fr) * 2006-01-24 2007-08-01 Yokogawa Electric Corporation Dispositif et procédé pour le traitement d'informations d'alarmes
US20090278680A1 (en) * 2006-12-21 2009-11-12 Abb Technology Ag Method and device for optimizing the alarm configuration
US20080255681A1 (en) * 2007-04-10 2008-10-16 Cindy Alsup Scott Methods and apparatus to manage process plant alarms

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
DE102019111854A1 (de) * 2019-05-07 2020-11-12 Minimax Viking Research & Development Gmbh Konfigurationssystem und Computerprogrammprodukt zur Konfiguration einer Zentrale
WO2020225311A1 (fr) 2019-05-07 2020-11-12 Minimax Viking Research & Development Gmbh Système de configuration et produit de programme informatique pour la configuration d'une centrale
US11790763B2 (en) 2019-05-07 2023-10-17 Minimax Viking Research & Development Gmbh Configuration system and computer program product for configuration of a control center
CN112829956A (zh) * 2021-01-14 2021-05-25 中国商用飞机有限责任公司 目标可配置的机组告警系统及用于其的配置方法
CN112829956B (zh) * 2021-01-14 2023-03-14 中国商用飞机有限责任公司 目标可配置的机组告警系统及用于其的配置方法

Similar Documents

Publication Publication Date Title
CN108353034B (zh) 用于数据中心基础设施监测的方法、系统和存储介质
US20210117895A1 (en) Systems and Methods for Cross-Platform Scheduling and Workload Automation
CN105593835B (zh) 通过主云服务管理器管理多个二级云
US8499250B2 (en) Apparatus and methods for interacting with multiple information forms across multiple types of computing devices
US6115646A (en) Dynamic and generic process automation system
US8285838B2 (en) Hierarchical management of realtime edge processor
CN104737517A (zh) 基于ldap的多客户云内身份管理系统
KR100437746B1 (ko) 원격의 호스트 시스템 상에서 실행되는 작업을 로컬의 워크스테이션에서 모니터링하는 방법 및 분산 컴퓨터 시스템과 컴퓨터 판독가능한 기록 매체
US20060277313A1 (en) System and method of data brokering
US10892970B2 (en) Centralized, scalable, resource monitoring system
AU2019203092B2 (en) System and method for deploying a distributed component-based application
Bromuri et al. Distributed agent environments in the ambient event calculus
US20070028174A1 (en) Grid processing dynamic screensaver
EP2533118A1 (fr) Système de gestion d'alarmes installé sur un site pour la gestion des composants source d'alarme
Patiniotakis et al. Assessing flexibility in event-driven process adaptation
Teimoury et al. Automation of the supply chain performance measurement based on multi-agent system
US9059992B2 (en) Distributed mobile enterprise application platform
Joshi Digital Twin Solution Architecture
Preventis et al. CLONE: collaborative ontology editor as a service in the cloud
Szwed et al. Business processes in a distributed surveillance system integrated through workflow
CN110609734A (zh) 定时任务调度的方法和装置
CN116468388A (zh) 一种流程混合编排系统
CN117785197A (zh) 积分商城软件的运维方法、装置、设备及存储介质
Mazurkevych Development of web application for uptime status monitoring
CN115344404A (zh) 事件处理方法、存储介质及电子装置

Legal Events

Date Code Title Description
PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

AX Request for extension of the european patent

Extension state: BA ME

RAP1 Party data changed (applicant data changed or rights of an application transferred)

Owner name: SIEMENS AKTIENGESELLSCHAFT

17P Request for examination filed

Effective date: 20130521

RIC1 Information provided on ipc code assigned before grant

Ipc: G05B 23/02 20060101AFI20130819BHEP

GRAP Despatch of communication of intention to grant a patent

Free format text: ORIGINAL CODE: EPIDOSNIGR1

INTG Intention to grant announced

Effective date: 20140108

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE APPLICATION IS DEEMED TO BE WITHDRAWN

18D Application deemed to be withdrawn

Effective date: 20140520