EP3652595B1 - Procédé et système pour surveiller une installation de la technologie d'automatisation - Google Patents

Procédé et système pour surveiller une installation de la technologie d'automatisation Download PDF

Info

Publication number
EP3652595B1
EP3652595B1 EP18732770.5A EP18732770A EP3652595B1 EP 3652595 B1 EP3652595 B1 EP 3652595B1 EP 18732770 A EP18732770 A EP 18732770A EP 3652595 B1 EP3652595 B1 EP 3652595B1
Authority
EP
European Patent Office
Prior art keywords
data
database
conversion unit
field device
data conversion
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.)
Active
Application number
EP18732770.5A
Other languages
German (de)
English (en)
Other versions
EP3652595A1 (fr
Inventor
Michael Mayer
Axel PÖSCHMANN
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.)
Endress and Hauser Process Solutions AG
Original Assignee
Endress and Hauser Process Solutions 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 Endress and Hauser Process Solutions AG filed Critical Endress and Hauser Process Solutions AG
Publication of EP3652595A1 publication Critical patent/EP3652595A1/fr
Application granted granted Critical
Publication of EP3652595B1 publication Critical patent/EP3652595B1/fr
Active legal-status Critical Current
Anticipated expiration legal-status Critical

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
    • G05B19/00—Programme-control systems
    • G05B19/02—Programme-control systems electric
    • G05B19/04—Programme control other than numerical control, i.e. in sequence controllers or logic controllers
    • G05B19/042—Programme control other than numerical control, i.e. in sequence controllers or logic controllers using digital processors
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/23—Updating
    • G06F16/2358—Change logging, detection, and notification
    • 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
    • G05B19/00—Programme-control systems
    • G05B19/02—Programme-control systems electric
    • G05B19/04—Programme control other than numerical control, i.e. in sequence controllers or logic controllers
    • G05B19/042—Programme control other than numerical control, i.e. in sequence controllers or logic controllers using digital processors
    • G05B19/0428—Safety, monitoring
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/23—Updating
    • G06F16/2365—Ensuring data consistency and integrity
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/24—Querying
    • G06F16/245—Query processing
    • G06F16/2455—Query execution
    • G06F16/24564—Applying rules; Deductive queries
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/25—Integrating or interfacing systems involving database management systems
    • G06F16/258—Data format conversion from or to a database
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/27—Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
    • G06F16/273—Asynchronous replication or reconciliation
    • 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
    • G05B2219/00—Program-control systems
    • G05B2219/20—Pc systems
    • G05B2219/25—Pc structure of the system
    • G05B2219/25204—Translate between different communication protocols
    • 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
    • G05B2219/00—Program-control systems
    • G05B2219/20—Pc systems
    • G05B2219/25—Pc structure of the system
    • G05B2219/25428—Field device
    • 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
    • G05B2219/00—Program-control systems
    • G05B2219/30—Nc systems
    • G05B2219/31—From computer integrated manufacturing till monitoring
    • G05B2219/31348—Gateway

Definitions

  • the invention comprises a method for monitoring an automation technology system in which at least one field device is used. Furthermore, the invention includes a data conversion unit for carrying out the method according to the invention.
  • Field devices that are used in industrial plants are already known from the prior art. Field devices are often used in automation technology as well as in production automation. In principle, all devices that are used close to the process and that supply or process process-relevant information are referred to as field devices. Thus, field devices are used to record and/or influence process variables. Measuring devices or sensors are used to record process variables. These are used, for example, for pressure and temperature measurement, conductivity measurement, flow measurement, pH measurement, level measurement, etc. and record the corresponding process variables pressure, temperature, conductivity, pH value, level, flow rate, etc. Actuators are used to influence process variables. These are, for example, pumps or valves that can influence the flow of a liquid in a pipe or the fill level in a container. In addition to the measuring devices and actuators mentioned above, field devices also include remote I/Os, wireless adapters or devices in general that are arranged at the field level.
  • field devices are usually connected to higher-level units via communication networks such as fieldbuses ( Profibus® , Foundation® Fieldbus , HART® , etc.).
  • the higher-level units are control units, such as a PLC (programmable logic controller) or a PLC (programmable logic controller).
  • the higher-level units are used, among other things, for process control and for commissioning the field devices.
  • the measured values recorded by the field devices, in particular by sensors are transmitted via the respective bus system to one (or optionally several) higher-level unit(s), which further process the measured values and forward them to the control center of the plant.
  • the control station is used for process visualization, process monitoring and process control via the higher-level units.
  • data transmission from the higher-level unit via the bus system to the field devices is also required, in particular for configuring and parameterizing field devices and for controlling actuators.
  • operating programs are required to operate the field devices; Emerson Delta V) are integrated.
  • operating is understood to mean, among other things, parameterization of the field device, updating of the field device and/or querying and visualizing process data and/or diagnostic data of the field device.
  • the data generated by the field devices is often collected directly from the field using so-called data conversion units, which are referred to as “edge devices” or “cloud gateways”, for example, and automatically transmitted to a central cloud-enabled database on which an application is located.
  • This application which among other things offers functions for visualization and further processing of the data stored in the database, can be accessed by a user via the Internet.
  • the data collected is transmitted to various databases by the data conversion units. These are mostly the databases of the respective manufacturer of a data conversion unit. A data exchange between the different databases is therefore often not possible or desirable. Therefore, there are many different implementations on the market - synergy effects are very difficult or impossible to achieve.
  • the DE 10 2014 119515 A1 comprises a method which describes a field device with an implemented first server (C1) and an internal database.
  • An operator can connect to the first server via an operating unit.
  • the first server connects to a second server.
  • the operator's retrieval commands are thus tunnelled through the field device to the second server, so that the data can be loaded from the second server onto the operator control device.
  • the DE 10 2005 051580 A1 discloses a communication module which is designed to acquire data from a field device via a first interface, convert it and transmit it to a cloud-enabled database.
  • the EP 2 660 667 A2 discloses a cloud gateway which, among other things, has a transformation component and can be connected to a cloud-enabled database.
  • the invention is based on the object of presenting a method which allows consistent management of data from a number of cloud-enabled databases which are not compatible with one another.
  • the object is achieved by a method according to claim 1.
  • the great advantage of the method according to the invention is that data can be transmitted from the first database to the second database, even though the databases have different data configurations.
  • the second database does not have to be specially configured here, since the data conversion unit communicates like a conventional edge device located in a plant.
  • the second database can therefore be used to access data from a field device, even though the second database itself is not connected to the field device.
  • a database within the meaning of the invention is understood to be “cloud-capable” if it can be contacted by a user via the Internet. It can be provided here that the database has an application, for example for visualizing field device-specific data that is stored in the database, or for configuring the database, for example for defining and selecting devices, within the meaning of the invention, data conversion units that the database Provide data that stores them.
  • a user can access the database application via the Internet from his device, for example a PC or a mobile device.
  • the field device-related data are collected by means of a second data conversion unit, which is located in particular in the system, are transmitted to the first database and are stored in the first database.
  • This data conversion unit usually has to be selected in the application located on the first database so that its data is stored on the first database.
  • the method according to the invention can thus be used bidirectionally.
  • the first data conversion unit must be selected or registered both in the first and in the second database.
  • the second database is brought into communication with a field device of a second process automation system and at least part of the data retrieved from the first database is used to operate the field device.
  • operating is understood to mean, among other things, parameterization of the field device, updating of the field device and/or querying and visualizing process data and/or diagnostic data of the field device.
  • the method therefore allows, for example, a field device to be parameterized with data originating from the first database.
  • the data located on the first and second databases are synchronized by means of the data conversion unit, in particular at recurring, defined time intervals, so that after the conclusion of a synchronization process, the databases have an essentially identical database . This increases the ease of use for a user. If he uses several databases, he only has to access a single one in order to be able to access his entire database. It is also ensured that the database is up-to-date.
  • the first data conversion unit is designed to retrieve at least part of the data contained in the first database and actively all changes to the data contained in the second database and/or not yet in the second database to transfer the data contained to the second database.
  • the data transmission is thereby actively driven by the data conversion unit, in that it pushes the data into the second database.
  • the second database therefore does not actively call up data via the data conversion unit, but receives the data automatically.
  • the first data conversion unit is implemented and executable as an application on the first database or the second database.
  • this data conversion unit must be selected in the application located on the first database so that its collected data is stored on the first database. It is not apparent to the database that this is a virtual data conversion unit.
  • the first data conversion unit is configured as a physical data conversion unit.
  • “Physical” means that the data conversion unit is a manageable device that has at least one electronic module, with the help of which the data is retrieved from the first database, converted and transmitted to the second database.
  • the first data conversion unit has a first interface and n further interfaces, the first interface being able to be connected to at least one first database via a first communication network and the nth interface being connected via a nth communication network can be connected to at least one nth database, where n ⁇ 2.
  • the method according to the invention can be carried out using the data conversion unit with each of the databases, so that the second database transmits at least part of the respective database from each of the databases gets.
  • a field device FG is arranged in a plant A of the process automation. This field device FG is used to acquire a physical measured variable and to convert the acquired measured variable into a measured value. Examples of such field devices FG have already been mentioned in the introductory part of the description.
  • the field device FG is connected via a communication interface to a field bus, not shown here, via which it transmits the measured values generated to the control room of the installation A.
  • the field device FG is connected to a data conversion unit, referred to here as the second data conversion unit DE 2 . The connection to the data conversion unit takes place either via a separate communication interface of the field device FG or via the fieldbus.
  • the second data conversion unit DE2 is in particular an edge device or a cloud gateway.
  • the second data conversion unit DE2 collects data from the field device FG at regular time intervals. This can be the measured values generated, but also diagnostic messages, parameter settings and/or identification data.
  • the collected field device-related data are transmitted to a first database DB1 via the Internet or a private network.
  • the connection is wired, for example, or wireless, for example via a mobile data connection such as GSM, UMTS, LTE, or the like.
  • the second data conversion unit DE2 In order for the data to be stored in the first database DB1, the second data conversion unit DE2 must be registered in the first database DB1. This is done using an application that runs on the first database DB1. To do this, a user BN accesses the application of the first database DB1 via the Internet or a private network.
  • the transmitted data are then stored in the first database DB1.
  • the storage takes place on the basis of a first data configuration.
  • a data configuration defines the file format of the stored data, or its semantics and/or rules for organizing and/or storing the data in the first database DB1.
  • the user BN can then access the data, for example by connecting to the application of the first database DB1.
  • the user BN can have a large number of other installation parts and field devices. Under certain circumstances, these use a different type of fieldbus which is not compatible with the second data conversion unit DE2, or cannot be connected to the second data conversion unit DE2 in some other way, for example due to the geographical location, so that further data conversion units are required. If these additional data conversion units are from a different manufacturer, the data collected from them is stored, among other things, in databases other than the first database DB1, which other databases may not allow data exchange. The user BN therefore needs to collect the databases of all his field devices in a single database.
  • the exemplary embodiment shown is used to transfer data stored on the first database DB1 to a second database DB2 using the method according to the invention.
  • the second database DB2 has a second data configuration that is not compatible with the first data configuration.
  • Further field devices, not shown here, can be connected to the second database DB2, for example by means of further data conversion units, or directly, with their data being stored in the second database.
  • a virtual data conversion unit referred to here as the first data conversion unit DE1
  • the first database DB1 This is designed as a software application and runs in the application of the first database DB2, which the user BN can access.
  • the first data conversion unit DE1 is registered in the second database DB2 as described above.
  • the first data conversion unit DE1 now collects data from the first database DB1.
  • the first data conversion unit DE knows the first data configuration of the first database DB1.
  • the collected data is then converted into the format of the second data configuration and transmitted from the first data conversion unit DE1 to the second database DB2, which then stores the data.
  • the transmission takes place via the Internet or via a private network.
  • the data is stored as if it had been collected directly from the field by a data conversion unit, since the second database DB2 cannot see from which source a data conversion unit obtains its respective data.
  • the user BN can then access the data of the field device FG using the application of the second database DB2. It can also be provided that, in the event that the second database DB2 is connected to a further field device, this further field device with the data of the field device FG is parameterized if they are used, for example, in a similar measuring point. Data from different parts of the plant can therefore be exchanged and used with one another in a simple manner.
  • the method according to the invention also allows the reverse route, so that data is collected from the second database DB2 and transmitted to the first database DB1. It can also be provided that the first and the second database DB1, DB2 are synchronized by means of the first data conversion unit DE1.
  • the method according to the invention also makes it possible to collect the data from a large number of databases DB1, DB3, . . . , DBn in one database DB2. 2 shows this use case.
  • the first data conversion unit DE1 is in the form of a physical device. This has a large number of communication interfaces IF1, IF2, IF3, ..., IFn, which via a corresponding communication network KN1, KN2, KN3, ..., KNn with the individual databases DB1, DB2, DB3, ..., DBn are connected.
  • a single communication network is used, for example the Internet, via which the first data conversion unit DE1 can contact the databases DB1, DB2, DB3, . . . DBn.
  • the communication interfaces IF1, IF2, IF3, . . . , IFn are configured as communication interfaces on the software side.
  • the first data conversion unit DE1 is able to understand each data configuration used by the databases DB1, DB2, DB3, . . . DBn and to convert data into another format used by the data configurations.
  • first data conversion unit DE1 can also be designed as a virtual data conversion unit in this application example. It is also possible that those in the below 1 described embodiment mentioned first data conversion unit DE1 can be designed as a physical device.

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Databases & Information Systems (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Data Mining & Analysis (AREA)
  • General Engineering & Computer Science (AREA)
  • Automation & Control Theory (AREA)
  • Computing Systems (AREA)
  • Computational Linguistics (AREA)
  • Computer Security & Cryptography (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)

Claims (8)

  1. Procédé destiné à la surveillance d'une installation (A) de la technique d'automatisation, installation dans laquelle est utilisé au moins un appareil de terrain (FG),
    procédé pour lequel une première base de données (DB1) compatible avec le cloud présente une première configuration de données et contient des données relatives à l'appareil de terrain, comprenant des valeurs mesurées, des valeurs de paramètres, des données d'identification et/ou un état de diagnostic de l'appareil de terrain (FG), les données relatives à l'appareil de terrain étant collectées au moyen d'une deuxième unité de conversion de données (DE2), transmises à la première base de données (DB1) et mémorisées dans la première base de données (DB1),
    une deuxième base de données (DB2) compatible avec le cloud présentant une deuxième configuration de données incompatible avec la première configuration de données,
    la deuxième base de données (DB2) étant mise en liaison de communication avec un deuxième appareil de terrain d'une deuxième installation de la technique d'automatisation, et
    la première et la deuxième configuration de données définissant le format de fichier des données, ou leur sémantique et/ou des règles pour l'organisation et/ou le stockage des données dans la première ou deuxième base de données (DB1, DB2) respective, lequel procédé comprend les étapes suivantes :
    - Récupération d'au moins une partie des données contenues dans la première base de données (DB1) au moyen d'une première unité de conversion de données (DE1) ;
    - Conversion des données récupérées dans un format conforme à la deuxième configuration de données ;
    - Transmission des données converties à la deuxième base de données (DB2) au moyen de la première unité de conversion de données (DE1) ;
    - Stockage des données converties dans la deuxième base de données (DB2) ;
    - Accès aux données du deuxième appareil de terrain au moyen d'une application de la deuxième base de données (DB2) ; et
    - Commande du deuxième appareil de terrain de la deuxième installation au moyen d'au moins une partie des données récupérées dans la première base de données (DB1), la commande comprenant une mise à jour du deuxième appareil de terrain, et/ou une interrogation et une visualisation de données de process et/ou de données de diagnostic du deuxième appareil de terrain.
  2. Procédé selon la revendication 1, comprenant en outre les étapes suivantes :
    - Récupération, au moyen de la première unité de conversion de données (DE1), au moins d'une partie des données contenues dans la deuxième base de données (DB2) et non contenues, ou en partie, dans la première base de données (DB1) ;
    - Conversion des données récupérées dans un format compatible avec la première configuration de données ; et
    - Stockage des données converties dans la première base de données (DB1).
  3. Procédé selon la revendication 1,
    pour lequel les données se trouvant sur la première et la deuxième base de données (DB1, DB2) sont synchronisées au moyen de la première unité de conversion de données (DE1), de telle sorte qu'à l'issue d'une opération de synchronisation, les bases de données (DB1) disposent d'un ensemble de données sensiblement identique.
  4. Système conçu pour la réalisation d'un procédé selon au moins l'une des revendications 1 à 3, lequel système comprend une première base de données (DB1) compatible avec le cloud, une deuxième base de données (DB2) compatible avec le cloud, une première unité de conversion de données (DE1) et une deuxième unité de conversion de données.
  5. Système selon la revendication 4, pour lequel la première unité de conversion de données (DE1) est configurée pour récupérer au moins une partie des données contenues dans la première base de données (DB1) et pour transférer activement vers la deuxième base de données (DB2) toutes les modifications concernant les données contenues dans la deuxième base de données (DB2) et/ou les données non encore contenues dans la deuxième base de données (DB2).
  6. Système selon la revendication 4 ou 5, pour lequel la première unité de conversion de données (DE1) est implémentée et peut être exécutée en tant qu'application sur la première base de données (DB1) ou la deuxième base de données (DB2).
  7. Système selon la revendication 4 ou 5, pour lequel la première unité de conversion de données (DE1) est conçue comme une unité de conversion de données physique.
  8. Système selon la revendication 7, pour lequel la première unité de conversion de données (DE1) comprend une première interface (IF1) et n autres interfaces (IF2, IF3, ..., IFn), la première interface (IF1) pouvant être connectée à au moins une première base de données (DB1) par l'intermédiaire d'un premier réseau de communication (KN1) et la énième interface (IF2, IF3, ..., IFn) pouvant être connectée à au moins une énième base de données (DB2, DB3, ..., DBn) par l'intermédiaire d'un énième réseau de communication (KN1, KN2, ..., KN3), n étant ≥ 2.
EP18732770.5A 2017-07-11 2018-06-20 Procédé et système pour surveiller une installation de la technologie d'automatisation Active EP3652595B1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
DE102017115517.1A DE102017115517A1 (de) 2017-07-11 2017-07-11 Verfahren und Datenumsetzungseinheit zum Überwachen einer Anlage der Automatisierungstechnik
PCT/EP2018/066381 WO2019011603A1 (fr) 2017-07-11 2018-06-20 Procédé et unité de conversion de données pour surveiller une installation de la technologie d'automatisation

Publications (2)

Publication Number Publication Date
EP3652595A1 EP3652595A1 (fr) 2020-05-20
EP3652595B1 true EP3652595B1 (fr) 2022-03-16

Family

ID=62684831

Family Applications (1)

Application Number Title Priority Date Filing Date
EP18732770.5A Active EP3652595B1 (fr) 2017-07-11 2018-06-20 Procédé et système pour surveiller une installation de la technologie d'automatisation

Country Status (4)

Country Link
US (1) US11514018B2 (fr)
EP (1) EP3652595B1 (fr)
DE (1) DE102017115517A1 (fr)
WO (1) WO2019011603A1 (fr)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
DE102020200453A1 (de) * 2020-01-15 2021-07-15 Wago Verwaltungsgesellschaft Mbh Multi-Cloud-Industriecontroller
CN111506642A (zh) * 2020-06-12 2020-08-07 夸克云智科技(深圳)有限公司 一种基于基础数据类型的数据转换方法

Family Cites Families (29)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO1998014852A1 (fr) * 1996-10-04 1998-04-09 Fisher Controls International, Inc. Interface accessible entre reseau et systeme de commande de processus
AU5025600A (en) * 1999-05-17 2000-12-05 Foxboro Company, The Process control configuration system with parameterized objects
US20060206806A1 (en) * 2004-11-04 2006-09-14 Motorola, Inc. Text summarization
US9208480B2 (en) * 2004-11-05 2015-12-08 Rdm Corporation Mobile deposit system for digital image and transaction management
US8308075B2 (en) * 2005-04-19 2012-11-13 Kamterter Products, Llc Systems for the control and use of fluids and particles
US8739059B2 (en) * 2005-05-16 2014-05-27 Xcira, Inc. System for generating inspection reports for inspected items
DE102005051580A1 (de) 2005-10-27 2007-05-03 Vega Grieshaber Kg Datenbankinterface für Feldgerät
US9418263B2 (en) * 2005-12-09 2016-08-16 Tego, Inc. Operating systems for an RFID tag
CA2701997A1 (fr) * 2007-11-07 2009-11-12 Edsa Micro Corporation Systemes et procedes pour une prevision et une prediction en temps reel de pics electriques et une gestion de l'energie, de la sante, de la fiabilite et de la performance de systemes d'energie electrique sur la base d'un reseau neuronal adaptatif artificiel
WO2009108328A1 (fr) * 2008-02-25 2009-09-03 Invensys Systems, Inc. Système et procédé pour générer une base de données de systèmes de commandes et des graphiques à partir de descriptions intermédiaires par schéma
US20110270723A1 (en) * 2010-04-30 2011-11-03 Agco Corporation Dynamically triggered application configuration
US20120072317A1 (en) * 2010-09-20 2012-03-22 Agco Corporation Billing management system for agricultural services access
US8478908B2 (en) * 2010-10-25 2013-07-02 Moxa Inc. Fieldbus gateway using virtual serial filedbus port and data transmission method thereof
US20130201316A1 (en) * 2012-01-09 2013-08-08 May Patents Ltd. System and method for server based control
EP2660667B1 (fr) 2012-05-04 2021-11-10 Rockwell Automation Technologies, Inc. Passerelle de nuage pour systèmes d'information et de commande d'automatisation industrielle
CA2799055A1 (fr) * 2012-12-14 2014-06-14 Caledon Computer Systems Inc. Appareil configure pour faciliter des transactions financieres securisees
US9305044B2 (en) * 2013-07-18 2016-04-05 Bank Of America, N.A. System and method for modelling data
KR20150099891A (ko) * 2014-02-23 2015-09-02 삼성전자주식회사 데이터 변환 처리 방법 및 이를 지원하는 전자 장치
US10208947B2 (en) * 2014-03-26 2019-02-19 Rockwell Automation Technologies, Inc. Cloud-level analytics for boiler networks
WO2016100545A1 (fr) * 2014-12-16 2016-06-23 Noderprime, Inc. Serveurs informatiques pour la gestion d'un centre de données
DE102014119515A1 (de) 2014-12-23 2016-06-23 Endress + Hauser Wetzer Gmbh + Co Kg Verfahren zum Betreiben eines Feldgerätes sowie Anordnung umfassend ein Feldgerät
US11042131B2 (en) * 2015-03-16 2021-06-22 Rockwell Automation Technologies, Inc. Backup of an industrial automation plant in the cloud
US10432754B2 (en) * 2015-09-16 2019-10-01 Profire Energy, Inc Safety networking protocol and method
US10187471B2 (en) * 2016-10-28 2019-01-22 Johnson Controls Technology Company Thermostat with direction display
US20170351226A1 (en) * 2016-06-01 2017-12-07 Rockwell Automation Technologies, Inc. Industrial machine diagnosis and maintenance using a cloud platform
WO2017210917A1 (fr) * 2016-06-10 2017-12-14 Honeywell International Inc. Mécanisme de test intégré pour des systèmes de commande et d'automatisation de processus industriel
US10318570B2 (en) * 2016-08-18 2019-06-11 Rockwell Automation Technologies, Inc. Multimodal search input for an industrial search platform
US10545492B2 (en) * 2016-09-26 2020-01-28 Rockwell Automation Technologies, Inc. Selective online and offline access to searchable industrial automation data
US11042362B2 (en) * 2019-09-26 2021-06-22 Rockwell Automation Technologies, Inc. Industrial programming development with a trained analytic model

Also Published As

Publication number Publication date
WO2019011603A1 (fr) 2019-01-17
US11514018B2 (en) 2022-11-29
EP3652595A1 (fr) 2020-05-20
US20200394174A1 (en) 2020-12-17
DE102017115517A1 (de) 2019-01-17

Similar Documents

Publication Publication Date Title
EP3612900B1 (fr) Procédé permettant de surveiller une installation technique d'automatisation
DE102010029952B4 (de) Verfahren zum Integrieren von zumindest einem Feldgerät in ein Netzwerk der Automatisierungstechnik
EP1525518B9 (fr) Procede d'actualisation de descriptions d'appareils pour des appareils de terrain employes dans l'automatisation de processus
DE102009045386A1 (de) Verfahren zum Betreiben eines Feldbus-Interface
EP3616365B1 (fr) Procédé permettant de faire fonctionner un appareil de terrain
DE102011007384A1 (de) Verfahren zur Offline-Konfiguration eines Feldgeräts
WO2009074544A1 (fr) Procédé pour faire fonctionner un système présentant un appareil de terrain et un système de commande
DE102016124350A1 (de) Verfahren und System zum Überwachen einer Anlage der Prozessautomatisierung
EP1797484A1 (fr) Application de bus de terrain comprenant plusieurs appareils de terrain
WO2017182201A1 (fr) Procédé de surveillance de l'état d'une installation pour l'automatisation de processus
EP3652595B1 (fr) Procédé et système pour surveiller une installation de la technologie d'automatisation
DE102009046041A1 (de) Anordnung zur Bedienung von Feldgeräten in der Automatisierungstechnik mittels eines Konfigurier-/Managementsystems
EP3861413B1 (fr) Procédé pour établir une communication de réseau par opc ua
EP3821306B1 (fr) Procédé de paramétrage d'un système de capteurs
EP3616011B1 (fr) Dispositif et procédé de surveillance d'un système d'automatisation
DE102010040054A1 (de) Verfahren zur Sicherstellung der korrekten Funktionsweise einer Automatisierungsanlage
WO2011042258A2 (fr) Procédé pour faire fonctionner une interface de bus de terrain
WO2016102194A1 (fr) Dispositif et procédé de fonctionnement d'un appareil de terrain pourvu d'un serveur web
EP4004664B1 (fr) Procédé pour vérifier l'inventaire des appareils de terrain enregistrés dans un système de gestion des actifs
DE102017123224A1 (de) Verfahren zum Etablieren einer Netzwerkkommunikation mittels OPC UA
DE102006062477A1 (de) Verfahren zum Betreiben eines nach dem Blockmodell arbeitenden Feldgerätes für ein verteiltes Automatisierungssystem
DE102021133959A1 (de) Verfahren zum Austausch eines Feldgeräts mit einem Ersatzfeldgerät in einer Messstelle einer Anlage der Automatisierungstechnik
DE102022133650A1 (de) System und Verfahren zum Zugriff einer Bedieneinheit auf zumindest ein Feldgerät
WO2009083426A2 (fr) Appareil de terrain, système d'automatisation et procédé permettant d'extraire des paramètres de profil de cet appareil

Legal Events

Date Code Title Description
STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: UNKNOWN

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

Free format text: STATUS: THE INTERNATIONAL PUBLICATION HAS BEEN MADE

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

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

Free format text: STATUS: REQUEST FOR EXAMINATION WAS MADE

17P Request for examination filed

Effective date: 20191210

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

DAV Request for validation of the european patent (deleted)
DAX Request for extension of the european patent (deleted)
STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: EXAMINATION IS IN PROGRESS

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

Free format text: STATUS: EXAMINATION IS IN PROGRESS

17Q First examination report despatched

Effective date: 20201223

GRAP Despatch of communication of intention to grant a patent

Free format text: ORIGINAL CODE: EPIDOSNIGR1

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

Free format text: STATUS: GRANT OF PATENT IS INTENDED

INTG Intention to grant announced

Effective date: 20211027

GRAS Grant fee paid

Free format text: ORIGINAL CODE: EPIDOSNIGR3

GRAA (expected) grant

Free format text: ORIGINAL CODE: 0009210

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

Free format text: STATUS: THE PATENT HAS BEEN GRANTED

AK Designated contracting states

Kind code of ref document: B1

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

REG Reference to a national code

Ref country code: GB

Ref legal event code: FG4D

Free format text: NOT ENGLISH

REG Reference to a national code

Ref country code: CH

Ref legal event code: EP

Ref country code: DE

Ref legal event code: R096

Ref document number: 502018009113

Country of ref document: DE

REG Reference to a national code

Ref country code: IE

Ref legal event code: FG4D

Free format text: LANGUAGE OF EP DOCUMENT: GERMAN

REG Reference to a national code

Ref country code: AT

Ref legal event code: REF

Ref document number: 1476334

Country of ref document: AT

Kind code of ref document: T

Effective date: 20220415

REG Reference to a national code

Ref country code: NL

Ref legal event code: FP

REG Reference to a national code

Ref country code: LT

Ref legal event code: MG9D

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: SE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20220316

Ref country code: RS

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20220316

Ref country code: NO

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20220616

Ref country code: LT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20220316

Ref country code: HR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20220316

Ref country code: BG

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20220616

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: LV

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20220316

Ref country code: GR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20220617

Ref country code: FI

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20220316

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: SM

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20220316

Ref country code: SK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20220316

Ref country code: RO

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20220316

Ref country code: PT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20220718

Ref country code: ES

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20220316

Ref country code: EE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20220316

Ref country code: CZ

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20220316

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: PL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20220316

Ref country code: IS

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20220716

Ref country code: AL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20220316

REG Reference to a national code

Ref country code: DE

Ref legal event code: R097

Ref document number: 502018009113

Country of ref document: DE

PLBE No opposition filed within time limit

Free format text: ORIGINAL CODE: 0009261

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

Free format text: STATUS: NO OPPOSITION FILED WITHIN TIME LIMIT

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: MC

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20220316

Ref country code: DK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20220316

REG Reference to a national code

Ref country code: CH

Ref legal event code: PL

REG Reference to a national code

Ref country code: BE

Ref legal event code: MM

Effective date: 20220630

26N No opposition filed

Effective date: 20221219

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: SI

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20220316

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: LU

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20220620

Ref country code: LI

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20220630

Ref country code: IE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20220620

Ref country code: CH

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20220630

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: BE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20220630

P01 Opt-out of the competence of the unified patent court (upc) registered

Effective date: 20230601

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: NL

Payment date: 20230620

Year of fee payment: 6

Ref country code: FR

Payment date: 20230628

Year of fee payment: 6

Ref country code: DE

Payment date: 20230620

Year of fee payment: 6

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: IT

Payment date: 20230623

Year of fee payment: 6

Ref country code: GB

Payment date: 20230622

Year of fee payment: 6

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: MK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20220316

Ref country code: CY

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20220316

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: HU

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT; INVALID AB INITIO

Effective date: 20180620