WO2014032720A1 - Procédé d'échange de messages de données entre des outils d'étude et développement dans un système d'automatisation et dispositif correspondant - Google Patents

Procédé d'échange de messages de données entre des outils d'étude et développement dans un système d'automatisation et dispositif correspondant Download PDF

Info

Publication number
WO2014032720A1
WO2014032720A1 PCT/EP2012/066890 EP2012066890W WO2014032720A1 WO 2014032720 A1 WO2014032720 A1 WO 2014032720A1 EP 2012066890 W EP2012066890 W EP 2012066890W WO 2014032720 A1 WO2014032720 A1 WO 2014032720A1
Authority
WO
WIPO (PCT)
Prior art keywords
data messages
instant messaging
development
exchanging data
planning
Prior art date
Application number
PCT/EP2012/066890
Other languages
German (de)
English (en)
Inventor
Andreas MÜLLER
Sören BURMEISTER
Marc Holz
Original Assignee
Siemens Aktiengesellschaft
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 Aktiengesellschaft filed Critical Siemens Aktiengesellschaft
Priority to PCT/EP2012/066890 priority Critical patent/WO2014032720A1/fr
Publication of WO2014032720A1 publication Critical patent/WO2014032720A1/fr

Links

Classifications

    • GPHYSICS
    • G05CONTROLLING; REGULATING
    • G05BCONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
    • G05B19/00Programme-control systems
    • G05B19/02Programme-control systems electric
    • G05B19/04Programme control other than numerical control, i.e. in sequence controllers or logic controllers
    • G05B19/042Programme control other than numerical control, i.e. in sequence controllers or logic controllers using digital processors
    • G05B19/0426Programming the control sequence
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L51/00User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
    • H04L51/02User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail using automatic reactions or user delegation, e.g. automatic replies or chatbot-generated messages
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L51/00User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
    • H04L51/04Real-time or near real-time messaging, e.g. instant messaging [IM]
    • GPHYSICS
    • G05CONTROLLING; REGULATING
    • G05BCONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
    • G05B2219/00Program-control systems
    • G05B2219/20Pc systems
    • G05B2219/25Pc structure of the system
    • G05B2219/25222Mailbox, email, mail system

Definitions

  • the invention relates to a method for exchanging data messages between development and planning tools, a so-called engineering system or a combination of such systems in the context of an automation system.
  • Different engineering systems or components of the engineering system address various aspects of automation systems that, from the point of view of an overall system, must interact in an integrative manner and are thus always seen embedded in an overall context.
  • This is particularly evident in the environment of the so-called digital factory, which represents a comprehensive network of digital Models and methods including simulation and SD visualization. Its purpose is the holistic planning, realization, control and continuous improvement of all essential factory processes and resources in connection with the product to be manufactured in the plant.
  • the aim of the digital factory is to develop and maintain a life-cycle-comprehensive and accompanying modeling of all involved components and production sections. This, that individual engineering activities in her they must be registered environmentally-giving context and adequately treated erfor ⁇ changed.
  • WEL ches addresses a different aspect of plant engineering can, as a needed because aspect related to process subset of GELIE ⁇ ferten information.
  • Such information exchange takes place offline and usually monolithic due to the data volume to be considered.
  • Information about which measures have to be taken in the target engineering system due to the information provided by the source engineering system is not apparent in an import export. The user must interpret the information provided and act accordingly.
  • AP233 Another standard for the exchange of systems engineering is AP233, with a neutral, computer-readable data format for data exchange between individual tools.
  • workflows are used for the coordination of engineering activities, which are guidelines for when and by whom and in which dependency, whereby not all instances involved in a workflow at the same time or rather, they are a set of decentralized, asynchronous tasks coordinated by the workflow.
  • Steps can be informed and act accordingly.
  • the users must interpret the corresponding information from the workflow in order to operate the engineering systems according to the workflow.
  • PLM context Product Lifecycle Management
  • the reactive implementation of actional modifications such as the adaptation of electrical components due to changes in the plant structure, is the sole responsibility of the user himself, and the resolution of inconsistencies must be carried out by hand.
  • Engineering systems do not have the ability to respond to knowledge of modifications in other but influencing systems they receive. Therefore, for the coupling of different engineering systems all ge ⁇ wish functions including communication aspects must be individually implemented and in addition to appropriate, gegebe- coordination logic can be realized.
  • IM Instant Messaging
  • IM is a communication method in which two or more participants talk via text messages, ie exchange information. In this case, the transmission is done in the push process, so that the messages arrive directly at the receiver. It provides infrastructures and mechanisms that allow individual subscribers (via messaging clients), after dialing in an instant messaging server, messages (messages) that are either intended specifically for exactly one known other subscriber, so-called private messages, or to a to send any number of unknown other participants.
  • chat rooms virtual rooms, in which the communication participants can "meet" for a limited period of time and whose number of participants also during the system can change term, known as bots may reside as participants in turn - alone applications that are largely independent repetitive tasks abarbei ⁇ th, without having to rely on an interaction with a human user. These bots wait for incoming messages and respond with reply messages in the chat room.
  • the communication between the partners can also be provided with different security levels.
  • instant messaging offers the coupling of different servers with replication function, so that stand-alone messaging networks can be formed with redundancy. In principle, this allows any number of users to be served.
  • the first attempts to use the Instant Messaging Technolo ⁇ strategy in the field of automation technology are already known.
  • SCADA Supervisory Control and Data Acquisition
  • This data is output graphically after evaluation and then used for further control and regulation System presented, which uses the mechanisms of instant messaging for the transmission of status ⁇ changes in the automation system to dedicated display devices.
  • the (real-time / real-time) data transmission to the user interfaces via instant messaging is realized.
  • not only the data but entire interfaces are transmitted.
  • the proposed system can be used for the transmission of diagnostic and error messages to the plant operator. It is an object of the present invention to provide a simple Mög ⁇ friendliness of data exchange within an engineering system or a composite of engineering systems.
  • the exchange of data messages between at least two development and / or planning tools via a communication network to support the development of control software for an automation system, wherein the development and / or planning tools can perform actions, according to the invention is characterized in that the development ⁇ development - and / or planning tools to exchange the data messages using an instant messaging mechanism and in particular using the Instant Messaging own message types and instant messaging channels.
  • the object is further achieved by a device according to claim 17.
  • the development and / or planning tool receives and the data messages ver ⁇ sends usually by one instant messaging client that communicates with the instant messaging server.
  • API application programming interface
  • the messaging client is advantageously set by a suitable configuration with the following Configurati ⁇ onsparametern:
  • a message sent to an instant messaging channel data message is in an advantageous embodiment, if necessary, translated for the addressed development and / or Pla ⁇ planning tools, called for example by an automatic ⁇ overbased translation program, known as "bot".
  • the translation program can then also be configured appropriately with the following configuration parameters:
  • the exchanged data messages can contain the following information:
  • the development and / or planning tools include at least ⁇ :
  • the instant messaging mechanism may be realized in a further embodiment of a decentralized manner in the communication network, by a plurality of intercommunicating Instant Mes ⁇ saging server.
  • the control of the responsible for the communication instant messaging server can be done using a central directory service.
  • the method can also be used in a further embodiment for the synchronization of databases of the individual development and / or planning tools.
  • Development and / or planning tool can be realized in a ⁇ design by mechanisms of the instant messaging system.
  • an encryption of the data messages can be realized by mechanisms of the instant messaging system.
  • the XMPP "Extensible Messaging and Presence Protocol" comes close to realizing the instant messaging system.
  • the method could be used in a further embodiment for exchanging data messages with diagnostic information between parts of a diagnostic system contained in the system, as in the extended sense for determining a state of the system.
  • the invention will be described below with reference to specific embodiments. This shows:
  • FIG. 1 shows a coupling between the engineering system and the messaging client
  • FIG. 2 shows a basic system architecture with a central IMS
  • FIG. 3 shows an alternative system architecture with decentralized IMS
  • Figure 4 is a schematic representation of a communication between two engineering systems according to the invention
  • Figure 5 is an exemplary communication in a first scenario
  • FIG. 6 shows the communication according to FIG. 5 using a decentralized IMS.
  • IMSI instant messaging server
  • the individual engineering systems are extended by a simple Messaging Client MC, 12, 22, which contains functions for sending and receiving data messages and is also capable of reacting to or triggering activities in the respective Engineering System (see Figure 1, in the following figures, the ES and MC blocks are simplified drawn directly to each other).
  • This MC, 12, 22, is always identical in its basic structure and functionality and has only the concrete connection to the Engineering System 11, 21, respectively
  • Each messaging client MC 12, 22 denotes an engineering system ES (hereinafter referred to as MC-ES obtained as shown in Figure 2, an individual configuration 311 in which to ⁇ least one of the following is defined:
  • a chatroom is usually a virtual space on the Internet where you can talk / chat concept of "Chat Room” used so informations ⁇ exchanging engineering systems here using the existing technical capabilities to security, Privacy, authentication, etc. can exchange their data messages.
  • Each MC sends its data messages according to its configuration to specific chat rooms CR1, ... CRm, which are either firmly defined or can be generated dynamically if required (for example, a separate chat room can be provided for each object type in the Engineering System Model Tree).
  • Chatrooms CR act as "interpreters" for incoming data messages.
  • the bots have information about which engineering systems are involved in the IM network, how their data messages are to be translated for the other engineering systems and in which context certain data messages are to be considered.
  • Each Bot Bl, Bp receives an individual configuration 130 defining at least the following:
  • FIG. 2 shows this basic system architecture with centralized, distributed by the engineering system, distributed instant messaging system IMS.
  • IMS instant messaging system
  • MT1 - Type I messages
  • MT1 - Type I messages
  • the modified element of an ES sends a message to the instant messaging network that it has been modified in a certain way; the other participants can receive this message and in the simplest case (it is not assumed that a message can be processed by all "listeners” necessarily directly) at least knowledge about received a modification in one of the ES participating in the network.
  • Type 2 messages (“this modification means ", hereinafter referred to as MT2) are sent by bots in response to data messages MT1 received by them and received by the messaging clients-ES. They contain information about the meanings that a data message MT1 has for other IM systems involved in the IM network but does not possess ver ⁇ working, engineering systems. Symbolically, the respective bot thus sends a "translation" of an MT1 into those “languages” (MT2) that are understood by the other engineering systems.
  • the path of an action in an engineering system ESI up to its reaction in a different engineering system ES2 is thus as follows: 1.
  • the action is carried out in engineering system ESI and monitored by the messaging client 12 via the ESI API.
  • the messaging client 12 converts the observation into an MT1 and sends it to the designated chat room CR, 301, according to the configuration on the given IMS (IM network), 13. All messaging clients MCI, MC2, MC3 registered in the chat room , 12, 22, 32 receive this MT1; if you can not interpret them, ignore them. Likewise, the sending messaging client MCI, 12 ignores this echo.
  • IMS IM network
  • the message client 22 of the engineering system ES2, STEP 7, 21 receives MT2 and can interpret it. Accordingly these messaging client 12 from redeemed by the ES API entspre ⁇ -reaching actions in ES2 so that ultimately the performed in ESI modification ES2 reflected.
  • bots are provided with appropriate application logic which, when predefined workflow-specific events occur, can send the MT2s defined for this purpose and thus trigger dependent activities in other engineering systems.
  • the solution described here can also be used to synchronize the databases between several similar Engineering System instances.
  • the sent MT1 can be understood directly by all participants and the bot-supported translation to MT2 can be omitted.
  • the sent MT1 and MT2 can be encrypted and the involved engineering systems or messaging client ES authenticated.
  • the received MT2 can be presented collected system users to a engineering and prepares up as evidence ( "TO DO"). This can be messaging
  • a further advantageous application of this approach would be in ⁇ play, the integrative assignment of bots or their Ap arisingslogik directly to the respective messaging clients instead of the central-ES, IM-typical operation of the bots in chat rooms (see Figure 5).
  • Another advantage is the extension of the existing standard messaging protocol, so that transfer additional semantics in the form of message types so that incoming messages can be already classified by the aforementioned interpreters before an accurate analy ⁇ se of the transmitted data made must become. par- In this way, even more complex mapping rules of the type n: 1, l: m or generally n: m can be realized with high performance in order to be able to implement the action-reactive live coupling under the required time requirements.
  • bots with the respective application logic makes it possible to communicate and react to different engineering systems as well as to implement or take into account cross-system functions (eg workflow monitoring) without the participating systems being aware of the existence of a need to have such bot-based functionality.
  • ⁇ Functions such as time-delayed responses to messages, eg.
  • As a result of temporarily not available partners engineering systems and the resulting need for updating the respectively existing level of knowledge for a "abwe ⁇ ence" are providing the infrastructure without any additional steps on the part of engineering systems need to be made ( "Presence Management").
  • Presence Management security, replication, and authentication mechanisms are inherited by the infrastructure, reducing engineering system overhead.
  • the concepts described may be used to enhance communication between the plant designer and his suppliers.
  • a frequently used case of application is a plant that is split into several technological components during planning, which are developed in parallel by different suppliers. The technological However see all components are embedded in a common context (the facility), so that here mechanisms Benö ⁇ be taken with which the synchronization between the technological components and the overall system warranty can be tet.
  • Another possible application is the Getechnike- and the development phase Cross communica ⁇ tion.
  • the concept presented can be used - for example, changes ⁇ a supplier to a technological component of the IMS communicated and with the help of bots "translated" to the respective ⁇ messaging client ES of the other Subcontractors. In the simplest case, this can be merely the notification that changes have been made in another technological component. However, it is also possible for the messaging client ES to automatically enter the change into the data of the notified supplier.
  • FIG. 5 An interaction using the example of concrete engineering systems (Automation Designer, STEP 7, Machine Simulator) is shown in FIG. 5.
  • a known representative of the instant messaging concept is XMPP (http://xmpp.org/):
  • the "Extensible Messaging and pre- sence Protocol" ( “extensible messaging and property ⁇ standardized protocol”) is a by the IETF as RFC 6120 - 6122 so as ⁇ 3922, 3923 published Internet standard for XML Routing. Among other things, it is characterized by the fact that the clients are of a very easy-to-implement structure.
  • IMS instant messaging system instant messaging support system

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Automation & Control Theory (AREA)
  • Computer And Data Communications (AREA)

Abstract

L'invention concerne un procédé d'échange de messages de données entre des outils d'étude et développement, ce que l'on appelle un système d'ingénierie ou un ensemble de systèmes de ce type dans le contexte d'un système d'automatisation. Dans l'échange de messages de données entre au moins deux outils d'étude et/ou développement par le biais d'un réseau de communication pour aider au développement de logiciels de commande d'un système d'automatisation selon l'invention, les outils d'étude et/ou développement échangent les messages de données par un mécanisme de messagerie instantanée et, en particulier, en utilisant des types de messages et des canaux spécifiques à la messagerie instantanée.
PCT/EP2012/066890 2012-08-30 2012-08-30 Procédé d'échange de messages de données entre des outils d'étude et développement dans un système d'automatisation et dispositif correspondant WO2014032720A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/EP2012/066890 WO2014032720A1 (fr) 2012-08-30 2012-08-30 Procédé d'échange de messages de données entre des outils d'étude et développement dans un système d'automatisation et dispositif correspondant

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/EP2012/066890 WO2014032720A1 (fr) 2012-08-30 2012-08-30 Procédé d'échange de messages de données entre des outils d'étude et développement dans un système d'automatisation et dispositif correspondant

Publications (1)

Publication Number Publication Date
WO2014032720A1 true WO2014032720A1 (fr) 2014-03-06

Family

ID=46845734

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/EP2012/066890 WO2014032720A1 (fr) 2012-08-30 2012-08-30 Procédé d'échange de messages de données entre des outils d'étude et développement dans un système d'automatisation et dispositif correspondant

Country Status (1)

Country Link
WO (1) WO2014032720A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20210382453A1 (en) * 2019-04-26 2021-12-09 Beckhoff Automation Gmbh Method for modifying a control software of an automation system

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
FR2835673A1 (fr) * 2002-02-01 2003-08-08 Schneider Automation Equipement d'automatisme communiquant par messagerie instantanee
EP1420316A1 (fr) * 2002-11-18 2004-05-19 Rockwell Automation Technologies, Inc. Communication par messages instantanés (Instant Messaging) pour notification d'événements et l'échange de données en milieu des automates programmables industriels
DE102005063080A1 (de) * 2005-12-29 2007-07-05 Endress + Hauser Process Solutions Ag Verfahren zum Instandhalten einer automatisierungstechnischen Anlage
US7539724B1 (en) 2002-06-04 2009-05-26 Rockwell Automation Technologies, Inc. Instant messaging for event notification and exchanging data in an industrial controller environment
US20100153771A1 (en) * 2005-09-30 2010-06-17 Rockwell Automation Technologies, Inc. Peer-to-peer exchange of data resources in a control system
US7760650B2 (en) 2006-12-22 2010-07-20 Ipnp Ltd. SCADA system with instant messaging

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
FR2835673A1 (fr) * 2002-02-01 2003-08-08 Schneider Automation Equipement d'automatisme communiquant par messagerie instantanee
US7539724B1 (en) 2002-06-04 2009-05-26 Rockwell Automation Technologies, Inc. Instant messaging for event notification and exchanging data in an industrial controller environment
EP1420316A1 (fr) * 2002-11-18 2004-05-19 Rockwell Automation Technologies, Inc. Communication par messages instantanés (Instant Messaging) pour notification d'événements et l'échange de données en milieu des automates programmables industriels
US20100153771A1 (en) * 2005-09-30 2010-06-17 Rockwell Automation Technologies, Inc. Peer-to-peer exchange of data resources in a control system
DE102005063080A1 (de) * 2005-12-29 2007-07-05 Endress + Hauser Process Solutions Ag Verfahren zum Instandhalten einer automatisierungstechnischen Anlage
US7760650B2 (en) 2006-12-22 2010-07-20 Ipnp Ltd. SCADA system with instant messaging

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20210382453A1 (en) * 2019-04-26 2021-12-09 Beckhoff Automation Gmbh Method for modifying a control software of an automation system

Similar Documents

Publication Publication Date Title
DE112017002494T5 (de) Multiprotokoll-feldgerät in prozessleitsystemen
WO2018162203A1 (fr) Procédé de paramétrage d'un appareil de terrain de la technique d'automatisation
EP3627800B1 (fr) Communication publication/abonnement de données de commande de machines
DE112014006483T5 (de) Managementsystem, Gateway-Vorrichtung, Server-Vorrichtung, Management-Verfahren, Gateway-Verfahren, Managementprozess-Ausführungsverfahren und Programm
DE102020112056A1 (de) Framework für den datenschutzrechtlichen austausch von big data mittels verteilter kontenbücher (distributed ledgers)
EP1472851A2 (fr) Systeme et procede pour analyser un reseau et/ou produire la topologie d'un reseau
DE102018008674A1 (de) Automatisierungsgerät mit integrierter Netzwerk-Analyse und Cloud-Anbindung
DE112010003638B4 (de) Öffentliche BOT-Verwaltung in privaten Netzwerken
DE112014004208T5 (de) Integrationsverfahren und -System
EP3814856B1 (fr) Dispositif d'automatisation en temps réel doté d'un bus de données en temps réel
EP3975502A1 (fr) Procédé et système de fourniture des services temporellement critiques au moyen d'un environnement de commande de déroulement
EP3528064B1 (fr) Système de commande et procédé associé de mise en marche, de commande et de surveillance pour des éléments d'alimentation électrique
WO2022022992A1 (fr) Commande de processus basée sur un jumeau numérique dans un réseau ido
WO2014032720A1 (fr) Procédé d'échange de messages de données entre des outils d'étude et développement dans un système d'automatisation et dispositif correspondant
WO2021093928A1 (fr) Procédé et dispositif de recherche d'abonnés au moyen du protocole opc ua pub/sub
EP3945702A1 (fr) Communication basée sur les canaux dans un réseau iot
EP3985532A1 (fr) Gestion des certificats pour installations techniques
EP4046340B1 (fr) Procédé de fonctionnement d'un système d'automatisation et infrastructure de données
EP3800864B1 (fr) Procédé de configuration d'un participant opc ua pubsub, système d'automatisation, programme informatique et support lisible par ordinateur
EP3614642A1 (fr) Procédé de réglage d'un flux, procédé de fourniture des informations d'identification du flux, utilisation d'un serveur de service nommé, appareil, programme informatique et support lisible par ordinateur
EP3903469B1 (fr) Identification de connexion sécuritaire fonctionnelle pour une connexion m2m
BE1027181B1 (de) Verfahren und System zum sicheren Bereitstellen von Daten eines Gegenstands über dessen gesamten Lebenszyklus
EP3907958A1 (fr) Procédé d'établissement d'un canal de transmission sécurisé destiné à la transmission de données dans un système d'automatisation industrielle
EP2224296A1 (fr) Procédé de mise à disposition de fonctions d'un système d'automatisation, programme de commande et système d'automatisation
EP3427143B1 (fr) Procédé de génération et de mise à jour d'une instance éloignée d'un affichage de l'écran

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 12758820

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 12758820

Country of ref document: EP

Kind code of ref document: A1