Processing installation data

Abstract

The present invention relates to a method (100) and a system (10) for processing installation data (D) and to a method (200) for creating an installation description (A). To this end, i) a description (A) of an installation (20) stored on a server (30) in a predetermined file format is accessed (S2) using a terminal (40); ii) the installation data (D), which characterises an operating state of the system (20), is retrieved (S3) by the server (30); and, iii) the installation description (A) stored on the server (30) is enriched with the retrieved installation data (D) and output (S4) via the terminal (40).

Description

[0001] Description

[0002] Processing of plant data

[0003] field of technology

[0004] The present invention relates to a method and a system for processing plant data and a method for creating a plant description.

[0005] State of the art

[0006] An essential component of the maintenance of technical equipment, for example, plants such as rolling mills for metal processing, or fault diagnosis is usually the determination of the current operating status based on current system data, such as actual values, deviations from target values, and / or the like. These values ​​must be able to be assigned by appropriate personnel to the correct system components, i.e., specific measuring elements, actuators, or other components of the respective system, in order to enable meaningful interpretation.

[0007] This plant data can usually be accessed in a control center or at control stations, so-called operator stations. However, the disadvantage here is that the allocation of the values ​​determined in this way to the various plant components may not be clear or at least difficult and cumbersome, especially for inexperienced personnel. In addition, it can be extremely time-consuming to have to repeatedly visit the control center or a control station when carrying out (maintenance) work directly on a plant in order to obtain current or, if necessary, updated values. In practice, the values ​​required are therefore often transmitted from the control center or a control station to personnel "in the field", i.e. at the plant, via radio.

[0008] Another option for providing the system data, or at least some of it, directly in the field is to output it via appropriate system displays. However, cost and space constraints generally prevent all potentially important data from being accessible in this way. In particular, setpoints are usually stored only in the system control system and can therefore only be accessed from the control center or a control station. Furthermore, assigning a value to the correct system component is also difficult.

[0009] EP 3 731 050 A1 discloses a visualization method for an image of an industrial technical plant, wherein a visualization device outputs the image during plant operation and represents the plant's sensors and actuators using process objects in an initial representation. The representation of the process objects changes whenever the visualization device receives a corresponding command from an operator.

[0010] EP 4 089 489 A1 discloses a control system for a technical installation, in which an operator station server has a visualization service for outputting image information to an operator station client. The operator station server is configured to generate visual representation information for at least one technical object of the installation during system runtime, which is then visually presented by the operator station client. Based on a monitoring trigger received from an operator, the operator station server can set up monitoring of the visual representation information.

[0011] DE 10 214 103 486 A1 relates to a mobile control center device for use in a process plant. Layout information of the process plant is stored in a database. A routine generates a graphic for display on a screen based on a determined relationship between the location of the mobile device and the layout of the plant.

[0012] Summary of the invention

[0013] Against this background, it is an object of the present invention to improve the provision of plant data, in particular to facilitate the accessibility of plant data, in particular in the field, and / or their interpretation.

[0014] This object is achieved by a method and a system for processing plant data and a method for creating a plant description according to the independent claims.

[0015] Preferred embodiments are the subject of the dependent claims and the following description.

[0016] According to a first aspect of the invention, in the particularly computer-implemented method for, in particular automatically, processing plant data, i) a description of a plant stored on a server in a predetermined file format is or are accessed with a terminal device, ii) plant data characterizing an operating state of the plant is retrieved by the server, and iii) the plant description stored on the server is enriched with the retrieved plant data, in particular in an automated manner, and output via the terminal device. A plant description stored in a predetermined file format within the meaning of the invention is preferably an already existing, in particular complete, description of the plant, for example documentation of the plant.The plant description may include, for example, circuit diagrams, operating instructions, characteristic values, site plans, piping and instrumentation diagrams (P&IDs), and / or similar information. Consequently, the plant description is preferably a standard technical document that provides details on the structure or function of the plant, for example.

[0017] One aspect of the invention is based on the approach of making plant data of a plant available on a preferably mobile terminal device. This enables a user to take the plant data "into the field", where work can be carried out on the plant without interruption, for example maintenance work or repairs can be carried out. The terminal device expediently serves only to output the plant data and therefore works as a client in a server-client structure. Consequently, it is preferred that the plant data be retrieved by a server with which the terminal can communicate. Since in modern plants the relevant plant data is usually recorded and processed in a plant control system anyway and is therefore available digitally, transferring it to the server via a suitable interface is generally possible without major effort.

[0018] The server can also process the plant data and / or convert it into a format that increases user readability and facilitates the interpretation of individual values ​​contained in the plant data. In particular, a plant description stored on the server in a predetermined file format can be enriched with the retrieved plant data, i.e., modified and / or supplemented by the plant data. The plant data can, for example, be integrated into a PDF document, in particular written. The use of PDF documents is preferred due to their widespread use and the possibility of device-independent document display. Other formats are also conceivable.

[0019] The plant description stored by the server, in particular the enriched one, is then output via the end device. The PDF document - or a document in another common file format - can therefore be opened on the end device. This allows the user to extract the current plant data it contains in conjunction with the plant-specific information contained in the plant description. As a result, the plant data no longer stands alone, but can be correctly interpreted and assigned through its integration into the plant description. By enriching the plant description stored on the server with the plant data, the user can be provided with a visualization of the plant data on the end device.This visualization conveniently includes displaying the system data for the corresponding system components—measuring elements, actuators, or other components—in the opened (enriched) system description. This allows the user to easily and intuitively understand the system data. Errors in assigning the displayed system data to the corresponding measuring elements, actuators, or other components can be avoided or at least minimized.

[0020] Preferred embodiments of the invention and their further developments are described below. These embodiments can be combined with each other and with the aspects of the invention described below, unless expressly excluded.

[0021] In order to display the most up-to-date information on the operating status of the system to a user of the end device, the enrichment of the system description stored on the server is preferably triggered by access from the end device. For example, the system data can only be integrated into the system description, in particular, written into it, when the system description is accessed, e.g., by opening the corresponding PDF document. Alternatively or additionally, it is conceivable to trigger the retrieval of the system data by the server through access from the end device. The "on demand" behavior of the server that can be implemented in this way can also prove advantageous in terms of reduced data traffic and reduced computing and memory usage.

[0022] An additional or alternative possibility of being able to provide the user with the most up-to-date information is to retrieve the plant data from the server essentially continuously, i.e. in real time, while the end device is accessing the stored plant description, in particular while the end device is outputting the enriched plant description. Accordingly, the plant description is expediently also enriched with the retrieved plant data essentially continuously, i.e. in real time, while the end device is accessing the stored plant description, in particular while the end device is outputting the enriched plant description. For example, the plant data displayed in a PDF document can be updated essentially in real time, for example at an update rate of approximately 1 second.Relevant measurement and other system-specific values ​​can thus be made available to the user live and at a glance in a display that is easy to understand. As already indicated, an easily interpretable display of the system data can be achieved by a user by assigning at least one piece of information contained in the system data to a specific system component described in the system description, for example, a measuring element, an actuator, or another component of the system, when enriching the system description, in particular automatically. It is therefore no longer up to the user to assign, for example, the abstract "output pressure 1" of a specific pump or the abstract "opening degree A" to a specific valve in the system.Rather, the user can obtain the relevant information directly in connection with the relevant part of the plant via the preferred assignment that is (automatically) carried out during enrichment.

[0023] Information contained in the system data within the meaning of the invention is preferably information associated with the system data, in particular information derivable from the system data, for example a measured value or setpoint. Consequently, the system data can contain or at least characterize parameter values ​​such as measured values, i.e. actual values ​​or control values, and / or setpoints or other state values. These parameter values ​​are expediently associated with a specific system component, e.g., with a measured value of a measuring element, an actual value or control value and / or a setpoint of an actuator, an operating state of a component (e.g., "on" or "off"), and / or the like.

[0024] To assign these parameter values ​​to specific plant components, it is useful to insert these parameter values ​​into the plant description during enrichment, particularly by adding them to the plant description. These parameter values ​​are preferably inserted into the plant description at predetermined positions. For example, the parameter values ​​can be inserted into the graphical representation of the corresponding plant component within a circuit diagram or P&ID. This allows a user to see at a glance how this plant component is currently operating, what measured values ​​it is providing, and what properties it has.

[0025] To assign the information contained in the plant data to specific plant components, especially to insert such information at predetermined positions in the plant description, for example, a PDF document, markers are used in the plant description stored on the server. This is described in more detail below.

[0026] As already described at the beginning, it is common for the plant data to be available in a control center or control station. Consequently, it is particularly useful with regard to implementing the method with existing plants if the server retrieves the plant data from a control system for process control via a first communication connection, for example via a first network, such as a LAN or similar. The term "control system" here preferably includes both the control center and any control stations. The server therefore does not have to communicate directly with the plant via a specific, plant-side interface, for example OPC-UA, or an intermediate server with this interface. Rather, it may be sufficient to integrate the server into a conventional network that encompasses the control system. This allows the server to be configured independently of the plant or environment.For example, the server can be set up as a virtual or physical Windows server.

[0027] Instead, direct communication with the plant via the specific interface can then remain with the control system. Accordingly, the plant data is expediently provided to the control system by the plant via a second communication connection different from the first communication connection, in particular via the specific interface specified by the plant.

[0028] According to a second aspect, the system for the, in particular automatic, processing of plant data comprises: i) a server on which a description of a plant is stored in a predetermined file format and which is configured to retrieve plant data which characterize an operating state of the plant and to enrich the plant description therewith, in particular in an automated manner; ii) a terminal device; and iii) a first communication connection between the server and the terminal device, via which the plant description stored, in particular enriched, by the server can be accessed with the terminal device.

[0029] This system allows users to take plant data "into the field," where they can work on the plant without interruption, for example, to carry out maintenance or repairs. This makes it easier to interpret individual values ​​contained in the plant data. Thanks to the enrichment of the plant description, the plant data no longer has to stand alone, but can, for example, be assigned to specific plant components. This makes the plant data easy to understand and intuitive for the user. Errors in assigning the displayed plant data to the corresponding measuring elements, actuators, or other components can be avoided or at least minimized.

[0030] In addition to the first communication connection, in particular the first network, between the terminal device and the server, the system preferably also has a second communication connection, which is different from the first communication connection and is in particular provided via the interface specified on the system side, between the server and the system. This allows the system data to be retrieved by the control system also mentioned above. Alternatively, it is also conceivable for the system data to be retrieved directly from the server via the second communication connection, in particular the interface specified on the system side, or at least to be made available for direct retrieval by the server. In other words, the second communication connection can represent a direct communication connection or an indirect communication connection via an intermediate server between the server and the system, via which communication connection the system data can be retrieved directly by the server.In this case, the system described here is independent of the control system.

[0031] As already indicated, the plant description stored on the server is enhanced using markers. For this purpose, the plant description contains several of these markers, on the basis of which the plant data can be integrated into the plant description. The markers can, for example, be contained in a plant description saved as a PDF document, perhaps in the form of an invisible text string. In this or a similar, or at least equivalent, manner, the markers can, for example, mark locations in the plant description where the plant data is or should be written into the plant description. Alternatively or additionally, the markers can also mark the information that is or should be included in the plant description – possibly at the specified location.

[0032] According to the invention, each marker defines a position within the plant description at which information contained in the plant data, in particular specific information such as a measured or setpoint value, is integrated into the plant description. In particular, the markers can be provided at precisely these positions in the plant description or inserted into the plant description. For example, the markers can be provided or inserted at representations of various plant components in a circuit diagram or P&ID. The information written into the plant description during enrichment based on such a marker can thus be associated by a user with the respective plant component intuitively and error-free.

[0033] In addition, each marker is expediently assigned an identifier that defines information contained in the plant data and to be integrated into the plant description. For example, the identifier can have a component identifier, such as an identification number, via which the corresponding information can be retrieved from the control system or directly from the plant via the second communication connection. If the plant data is provided via the OPC UA standard, for example, the identifier can also have a corresponding OPC variable, in particular a complete OPC UA address. Using this OPC variable, the value determined by the corresponding plant component can then be retrieved via the second communication connection.

[0034] Likewise, each marker can define one of several predefined display types for information contained in the plant data. For example, each marker can have a display identifier that identifies one of the predefined display types. Using the marker, the appearance of the plant data in the enriched plant description can thus be conveniently influenced. For example, the marker can specify the font, font size, color, and / or the like used to display the plant data in the enriched plant description.

[0035] Alternatively, the corresponding representation type of the information contained in the plant data can be determined using the identifier preferably assigned to the marker in a database also stored on the server, such as a corresponding configuration file. Using the identifier, which can contain, for example, a component identifier of the corresponding plant section, the representation type assigned to the identifier or component identifier in the database can be obtained from the database. Alternatively or additionally, the database can also contain address information for retrieving the plant data, in particular the specific parameter values ​​for the various plant sections.

[0036] Consequently, it is preferred that the server has the database, in particular the configuration file, in which each marker is assigned address information for retrieving the plant data and / or one of several possible representation types of the plant data when enriching the plant description. In the database, the markers or identifiers assigned to them, in particular component identifiers contained in the identifiers, can be assigned, for example, OPC UA addresses that allow retrieval of the corresponding parameter values. It is also conceivable that the database has a generic OPC UA address for different categories of plant components, each with a placeholder for the identifier assigned to the marker, e.g., a component identifier contained in the identifier. Such a database enables, in particular, automated creation of the plant description.

[0037] According to a third aspect of the invention, in the method for creating a plant description, in particular at least partially computer-implemented, i) a description of a plant is created, ii) at least one marker is inserted into the plant description, on the basis of which the plant description can be enriched with plant data that characterize an operating state of the plant, and iii) the plant description is stored in a predetermined file format on a server.

[0038] This makes it possible to enrich the plant description with plant data when the plant description stored on the server is accessed—for example, using a terminal device. This allows the plant data to be taken "into the field." For example, using markers, information contained in the plant data can be entered into a plant description saved as a PDF document when the PDF document is opened on the terminal device. This allows a user to directly capture the operating status of the plant and, if necessary, even individual plant components while studying the plant description, for example, a plant documentation.

[0039] Short description of the drawings

[0040] The above-described properties, features, and advantages of this invention, as well as the manner in which they are achieved, will become clearer and more readily understood in connection with the following description of an embodiment, which is explained in more detail in conjunction with the drawings.

[0041] Fig 1 an example of a system for processing plant data,

[0042] Fig 2 another example of a system for processing plant data,

[0043] Fig 3 an example of a plant description enriched with plant data,

[0044] Fig 4 an example of the marker-marked plant description from Fig 3,

[0045] Fig 5 shows an example of a method for processing plant data, and

[0046] Fig 6 an example of a procedure for creating a plant description.

[0047] Where appropriate, the same reference numerals are used in the figures for the same or corresponding elements of the invention.

[0048] Description of the embodiments

[0049] FIG 1 shows an example of a system 10 for processing plant data D, which characterizes an operating state of a plant 20. The system 10 has a server 30, a plurality of terminal devices 40, and a first communication connection 50 between the server 30 and the terminal devices 40. On the server 30, in particular a storage device 32 of the server 30, a plant description A of the plant 20 is stored in a predetermined file format. The server 30 is configured, for example programmed, to retrieve the plant data D and enrich the plant description A therewith. For example, the server 30 can retrieve the plant data D and write the information contained therein, such as measured values ​​and target values, into the plant description A.

[0050] To retrieve the plant data D, a second communication connection 60, different from the first communication connection 50, is provided between the server 30 and the plant 20. A plant controller 22, for example a programmable logic controller (PLC for short), is also to be understood as part of the plant 20. Via the second communication connection 60, the server 30 can access, particularly in real time, the variables of the plant controller 22 and thus the measured values ​​and setpoints of various plant components such as measuring elements, actuators, or other components of the plant 20. This plant data D can be retrieved from the server 30 via the second communication connection 60, preferably based on a standard, for example OPC-LIA.

[0051] In the example shown, the second communication connection 60 between the server 30 and the system 20, in particular the system controller 22, is a direct or immediate connection. However, it is also conceivable in principle for the second communication connection 60 to comprise an intermediate server, via which the server 30 is indirectly connected to the system 20, in particular the system controller 22, and can retrieve the system data D. Via such an intermediate server, the system data D of several systems 20, in particular, can be provided with minimal effort.

[0052] The terminal devices 40 are expediently suitable for accessing the system description A stored by the server 30 via the first communication connection 50, for example, a network. Individual terminal devices 40, for example, workstations or personal computers 42, can be connected to the first communication connection 50 via a cable. However, the terminal devices 40 are preferably portable or mobile, for example, a mobile phone 44, laptop 46, or tablet 48. In this case, individual terminal devices 40 are expediently connected to the first communication connection 50 via an air interface 52, for example, WLAN. This allows them to be easily carried along when working on the system 20.

[0053] To enable access to the plant description A enriched with the plant data D, the server 30 can host a website. This website can expediently be accessed from any terminal 40 that is located in the same network as the server 30, i.e., is connected to the first communication link 50. Preferably, the plant description A provided via the website, for example, a PDF document, can then be opened using a browser running on the terminal 40, in which the current plant data D is displayed. This is described in detail below in connection with FIG. 5.

[0054] FIG 2 shows a further example of a system 10 for processing plant data D. The system 10 essentially corresponds to the system shown in FIG 1 with the difference that in this case a control system 70 connected to the first communication connection 50 for controlling the plant 20 is shown and the server 30 is not directly connected to the plant 20, in particular the plant control 22, via the second communication connection 60.

[0055] Rather, the server 30 in FIG 2 is configured, for example programmed, to retrieve the plant data D via the first communication connection 50 from the control system 70, for example a control center or a control station 72. The control system 70 is used to control a process executed by the plant 20 and must therefore have access to the variables of the plant controller 22, i.e. to the plant data D. For this purpose, the plant 20, in particular the plant controller 22, is connected to the first communication connection 50. The control system 70 can then retrieve the plant data D via a standard, for example OPC-UA, from the plant controller 22 or, as shown in FIG 2, from an intermediate server 62.

[0056] FIG 3 shows an example of a plant description A enriched with plant data. In this case, the plant description A contains a piping and instrumentation diagram (P&ID); however, in principle, the plant description A can be any type of plant documentation. In particular, the plant description A can also contain one or more circuit diagrams, site plans, and / or the like, alternatively or in addition to the P&ID.

[0057] The P&ID shows, in addition to several lines and fluid control devices, two measuring elements in the form of pressure sensors 24a, 24b and a motor-driven pump 26. In the system description A, the pressure sensors 24a, 24b are identified as such by a label 80a. Pump 26 is also provided with a similar label 80b. The labels 80a, 80b indicate the type of the system component shown, unless this is already clear from the symbols used.

[0058] Additionally, an identification number 82a, 82b for the pressure sensors 24a, 24b is specified in the system description A. For convenience, each system component shown has such a unique identification number, even if it is not explicitly specified in the system description A.

[0059] The system data is represented within system description A in the form of framed data fields 84. These data fields 84 are arranged in the immediate vicinity of various system components shown in system description A and display parameter values ​​86a, 86b, 86c of the respective system component. In the present example, parameter values ​​86a, 86b correspond to the measured values ​​of pressure sensors 24a, 24b, and parameter value 86c corresponds to the operating state of pump 26 (e.g., "on" or "off"). In addition, the data fields 84 assigned to pressure sensors 24a, 24b also display a specific component identifier 88a, 88b, which determines which of the parameter values ​​86a-c is displayed at the corresponding location, i.e., within the corresponding data field 84, in system description A.These component identifiers 88a, 88b can, for example, be composed of the labels 80a, 80b and the associated identification numbers 82a, 82b and can be used as a basis for determining the corresponding parameter values ​​86a, 86b.

[0060] For example, plant description A can be enhanced with plant data retrieved via the OPC-LIA standard from a server on which plant description A is also stored. According to this standard, each control-relevant plant component of a plant, for example, each measuring element, actuator, and / or the like, is assigned an OPC variable. The current parameter values ​​86a-c associated with the plant components can be queried via the OPC variables.

[0061] In this case, the component identifiers 88a, 88b can correspond to the corresponding OPC variables of the pressure sensors 24a, 24b or at least be used as a basis for determining the OPC variables, e.g. by reading from a database.

[0062] FIG 4 shows an example of the plant description A from FIG 3 marked with markers M. While in FIG 3 the plant description A is shown as it is presented to a user, FIG 4 shows another level of the plant description A which is not visible to the user.

[0063] The markers M serve to enrich the plant description A with the plant data, in particular to display the data fields shown in FIG. 3 with the parameter values ​​and, in the case of the pressure sensors 24a, 24b, the component identifiers. In other words, the plant data can be integrated into the plant description A based on the markers M. Only when the plant data have been integrated into the plant description A using the markers M does the plant description A appear to the user as shown in FIG. 3.

[0064] For this purpose, the markers M expediently indicate the positions in the system description A at which the system data, ie, in this case, the parameter values, are to be displayed. At the same time, however, the markers M can also specify the system data that are to be displayed in the system description A, ie, which of the parameter values ​​is to be displayed at the corresponding location. For this purpose, each of the markers M is assigned a corresponding identifier 92a, 92b, 92c.

[0065] Optionally, the markers M or the identifiers 92a-c assigned to them can also define or predetermine the type of representation of the system data to be displayed in the system description A. In the present case, for example, the markers M can specify that the parameter values ​​are displayed in framed data fields and, in the case of the pressure sensors 24a, 24b, that the component identifiers are also displayed. Likewise, the markers M can generally also specify the font, color, size, and / or the like. Alternatively, the markers M or the identifiers 92a-c assigned to them can be used to determine the type of representation, for example if the identifiers 92a-c are assigned to the corresponding type of representation in a database - as explained in detail below in connection with FIG 6.

[0066] The plant description A containing the markers M is expediently stored on a server in a predetermined file format, for example, as a PDF document. The markers M can be provided as text fields 90 that remain invisible to a reader when the plant description A is displayed, for example, by selecting the font color of the text contained therein. The text fields 90 expediently contain the identifier 92a, 92b, 92c, in particular as a character string.

[0067] For example, to indicate the respective system data to be displayed, the text fields 90 can each contain an identification character, such as an asterisk *, followed by the component identifier, or they can already contain a complete OPC UA connection string (i.e., an OPC variable or an OPC UA address). In this case, the identification characters and the component identifiers together, or the OPC UA connection strings, serve as identifiers 92a-c.

[0068] FIG 5 shows an example of a method 100 for processing plant data that characterizes an operating state of a plant.

[0069] In a method step S1, a website hosted by a server is opened using a terminal device. For this purpose, the terminal device expediently connects to the server via a first communication connection, e.g., a network. To gain access to the website or content provided via the website, in particular to a system description stored in a predetermined file format, registration or authentication of the terminal device may be provided. For example, a password request or the verification of a certificate may be performed on the terminal device.

[0070] The website can be opened by a user manually entering a URL into a browser or via search or filter functions. It is also conceivable that the website can be opened in the browser, for example, by scanning a QR code or other machine-readable code such as a DMC attached to the system, or by receiving an identification signal provided by the system, such as RFID.

[0071] In a further process step S2, the terminal device accesses the system description, for example, by opening the corresponding file with a viewer (compatible with the specified file format). The system description can, for example, be stored on the server as a PDF document and opened with a PDF viewer. The file is conveniently opened in an inline frame (iFrame for short) by a predetermined viewer. Due to its configurability, it has proven advantageous to use the PDF viewer PDF.js for this purpose.

[0072] The predetermined display program, preferably PDF.js, is expediently configured to evaluate the stored system description, for example, the PDF document. The predetermined display program expediently outputs the system description as an HTML page, allowing markers contained in the system description or the PDF document, e.g., implemented as HTML tags, to be detected.

[0073] Such markers can, for example, be contained in the stored plant description in the form of text fields or text strings. These markers are expediently not visible when the plant description is displayed in the display program, for example by providing them with a corresponding font color. However, such text fields or text strings can be detected in HTML using an appropriate query, for example by marking them with a corresponding preceding identification character, such as an asterisk *. To detect such markers, the JavaScript library jQuery can be used, for example, and in particular integrated into the specified display program. The specified display program then expediently makes the read markers available for use by the server.

[0074] Based on the detected markers, in particular the text fields or text strings, the system data can then be retrieved by the server in a further process step S3. For this purpose, each marker is expediently assigned an identifier that specifies the system data to be integrated into the system description, for example, defining parameter values ​​to be displayed. The text fields can, for example, contain a complete OPC UA address, so that the server can retrieve the system data directly from the system or a control system using the OPC UA standard. In this case, the OPC UA address serves as the identifier. Alternatively, the text fields can contain component identifiers that are linked in a database, e.g., a configuration file, to OPC UA addresses of various system components, e.g., measuring elements, actuators, or other system components, that can be queried by the server.In this case, the identifiers are conveniently formed from the respective component identifier and a preceding identification character, such as an asterisk *.

[0075] In a further method step S4, the plant description is enriched with the plant data retrieved in this way. For this purpose, the predetermined display program is expediently configured to place text boxes over the displayed plant description at the position of the found markers and to write the plant data, in particular parameter values, queried in the background, for example via OPC-11A, into these text boxes. Thus, in method step S4, the plant description enriched with the plant data is simultaneously output via the terminal device. If necessary, the type of representation of the plant data within the plant description can be influenced by the respective marker, in particular the representation information contained therein, for example with regard to the font, color and / or the like.Alternatively, such display information can also be contained in the database already mentioned, for example a configuration file in which the component identifiers readable by the predetermined display program are linked to the OPC UA addresses to be queried by the server.

[0076] FIG 6 shows an example of a method 200 for creating a plant description.

[0077] In process step Z1, a description of a system is created, i.e., a documentation or similar technical document. The system description may, for example, contain, in addition to operating instructions, circuit diagrams, piping and instrumentation flow diagrams, and / or similar information.

[0078] In a further method step Z2, at least one marker is inserted into the plant description, on the basis of which the plant description can be enriched with plant data that characterizes an operating state of the plant. The markers can be subsequently inserted into the already created plant description. This is expediently done manually, but can in principle also be automated. Alternatively or additionally, the markers can also be integrated into the plant description when the plant description is created, i.e. as part of the creation process. This is particularly advantageous if the creation process is also at least partially automated, for example by exporting from a CAD program or the like.

[0079] To create the plant description with at least partially automated marker generation, it is preferable to categorize the plant components to be described in the plant description, such as pressure sensors, pumps, drives, and / or the like. For example, a specific marker type or at least a predetermined type of representation can be provided for each category of plant components, for example pressure sensors. For this purpose, it is expedient to specify in a database, for example in a configuration file, for each category of plant components how parameter values ​​of these plant components are to be represented in the enriched plant description. At the very least, however, information about how the parameter values ​​of these components can be retrieved can be stored in the database for each category. For example, a generic OPC UA address with a placeholder for a component identifier, i.e.identification information for an individual piece of equipment can be added.

[0080] When creating the plant description, a corresponding marker can be automatically inserted at predetermined locations for each component identifier that occurs, i.e., each plant section to be described in the plant description. For example, if a piping and instrumentation flow diagram to be displayed contains a pressure sensor, a text field containing the text string *PI_1234 can be created next to the pressure sensor symbol when creating the plant description. The asterisk * corresponds to the identifier, and the string Pl_1234 to the component identifier, which contains a unique identification number 1234 for this plant section in addition to the type or category of the plant section in question (PI = pressure sensor).

[0081] The plant description created in this way is expediently saved on a server in a further process step Z3. If the saved plant description is opened and the markers are read out as described in connection with FIG 5 and transferred to the server, the server can link the component identifiers with the information stored in the database if necessary and retrieve the plant data, for example, the corresponding parameter values, using the corresponding OPC UA addresses. The retrieved plant data can then be displayed at the corresponding locations in the plant description indicated by the markers.

[0082] Although the invention has been illustrated and described in detail by the preferred embodiments, the invention is not limited by the disclosed examples and other variations may be derived therefrom by those skilled in the art without departing from the scope of the invention.

[0083] List of reference symbols

[0084] 10 systems

[0085] 20 Appendix

[0086] 22 Plant control

[0087] 24a, 24b pressure sensor

[0088] 26 Pump

[0089] 30 servers

[0090] 32 storage device

[0091] 40 end devices

[0092] 42 PC

[0093] 44 Mobile phone

[0094] 46 laptops

[0095] 48 tablets

[0096] 50 first communication connection

[0097] 52 Air interface

[0098] 60 second communication connection

[0099] 62 intermediate servers

[0100] 70 guidance system

[0101] 72 control station

[0102] 80a, 80b labeling

[0103] 82a, 82b Identification number

[0104] 84 Data field

[0105] 86a, 86b, parameter value

[0106] 86c

[0107] 88a, 88b Component identifiers

[0108] 90 Text field

[0109] 92a, 92b, identifier

[0110] 92c

[0111] 100 procedures for processing plant data

[0112] S1 Open website 52 Access to system description

[0113] 53 Retrieve system data

[0114] 54 Enrich and output plant description

[0115] 200 Procedures for creating a plant description

[0116] Z1 Create plant description

[0117] Insert Z2 marker

[0118] Z3 Save system description

[0119] A Plant description

[0120] D Plant data

[0121] M Marker

Claims

Claims 1. Method (100) for processing plant data (D), wherein - a description (A) of a plant (20) stored on a server (30) in a predetermined file format is accessed (S2) with a terminal (40), wherein the plant description (A) contains several markers (M) on the basis of which the plant data (D) can be integrated into the plant description (A), - the server (30) retrieves system data (D) which characterise an operating state of the system (20) (S3), - the plant description (A) stored on the server (30) is enriched with the retrieved plant data (D), wherein each marker (M) defines a position within the plant description (A) at which a specific piece of information contained in the plant data (D) is integrated into the plant description (A), and - the system description (A) is output via the terminal (40) (S4).

2. Method (100) according to claim 1, wherein the retrieval of the system data (D) and / or the enrichment of the system description (A) is triggered by access with the terminal (40).

3. Method (100) according to claim 1 or 2, wherein the system data (D) are retrieved substantially continuously by the server (30) during access with the terminal (40) to the stored system description (A) and / or the system description (A) is enriched substantially continuously with the retrieved system data (D) during access with the terminal (40) to the stored system description (A).

4. Method (100) according to one of the preceding claims, wherein at least one piece of information contained in the plant data (D) is assigned to a specific plant part (24a, 24b, 26) described in the plant description (A) when enriching the plant description (A).

5. Method (100) according to one of the preceding claims, wherein the plant data (D) contain parameter values ​​(86a, 86b, 86c) which are inserted into the plant description (A) at predetermined positions during the enrichment.

6. Method (100) according to one of the preceding claims, wherein the server (30) retrieves the plant data (D) from a control system (70) for process control via a first communication connection (50), and the plant data (D) are provided to the control system (70) from the plant (20) via a second communication connection (60) different from the first communication connection (50).

7. System (10) for processing plant data (D), with - a server (30) on which a description (A) of a plant (20) is stored in a predetermined file format and which is configured to retrieve plant data (D) which characterise an operating state of the plant (20) and to enrich the plant description (A) therewith, - a terminal (40), and - a first communication connection (50) between the server (30) and the terminal (40), via which the terminal (40) can access the plant description (A) stored by the server (30), wherein the plant description (A) contains a plurality of markers (M) on the basis of which the plant data (D) can be integrated into the plant description (A), and wherein each marker (M) defines a position within the plant description (A) at which a specific piece of information contained in the plant data (D) is integrated into the plant description (A).

8. System (10) according to claim 7, with a second communication connection (60) between the server (30) and the system (20), which is different from the first communication connection (50), via which the system data (D) can be retrieved from the server (30) or at least made available for retrieval by the server (30).

9. System (10) according to claim 7 or 8, wherein each marker (M) defines a position within the plant description (A) at which a specific item of information contained in the plant data (D) is integrated into the plant description (A).

10. System (10) according to one of claims 7 to 9, wherein the server (30) has a database in which each marker (M) is assigned address information for retrieving the plant data (D) and / or one of several possible ways of displaying the plant data (D) when enriching the plant description (A).

11. Method (200) for creating a plant description (A), wherein - a description (A) of an installation (20) is created (Z1), - at least one marker (M) is inserted into the plant description (A), on the basis of which the plant description (A) can be enriched with plant data (D) that characterize an operating state of the plant (20), wherein each marker (M) defines a position within the plant description (A) at which a specific information contained in the plant data (D) is integrated into the plant description (A), and - the system description (A) is stored in a predetermined file format on a server (30) (Z3).

Images