Packaging Plant Data Exchange and Method for Operating a Packaging Plant Data Exchange

Abstract

Packaging plant data exchange comprising at least one buffer for packaging plant status data comprising status values, at least one data input interface, the data input interface communicating with at least one program module adapted to a packaging device of the packaging plant and receiving at least packaging plant status data, at least one data storage interface, the data storage interface communicating with at least one database module adapted to a database.

Claims

1. A packaging plant data exchange comprising, at least one buffer for packaging plant status data comprising status values, at least one data input interface, the packaging plant data exchange is arranged for communicating via the data input interface with at least one program module adapted to a packaging device of the packaging plant and for receiving at least packaging plant status data, wherein the data input interface is arranged for receiving, packaging plant status data, at least one data storage interface, wherein the packaging plant data exchange is arranged for communicating via the data storage interface with at least one database module adapted to a database characterized in that an access interface is arranged for communicating with the program module, the access interface is arranged for accessing packaging plant status data.

2. The packaging plant data exchange according to claim 1, characterized in that the buffer, the data input interface, the data storage interface and preferably an access interface form a common switching network, and in that program module exchanges packaging plant status data with the packaging plant data exchange exclusively via the switching network.

3. The packaging, plant data exchange according to claim 1, characterized in that the buffer, the data input interface, the data storage interface and preferably an access interface are operated independently of one another and/or in that the buffer, the data input interface and the data storage interface devices are connected to one another via a common message bus which is preferably integrated in the packaging plant data exchange system.

4. (canceled)

5. The packaging plant data exchange according to claim 1, characterized in that the data input interface is set up for communication with at least one program module which determines packaging plant parameters and/or in that an instance of a program module respectively implements a data input interface and/or in that the packaging plant data exchange implements a data input interface.

6. The packaging plant data exchange according to claim 1, characterized in that the buffer for exchanging packaging plant status data comprising metadata and status values is formed via the data storage interface.

7. The packaging plant data exchange according to claim 1, characterized in that the buffer has a buffer interface, in particular a read interface, the buffer interface being set up for at least one direct read access and/or write access to at least metadata in the buffer by at least one program module.

8. The packaging plant data exchange according to claim 1, characterized in that the access interface outputs at least one change message, in particular a change message to a program module, in the event of data changes in the packaging plant data exchange, in particular the buffer memory.

9. The packaging plant data exchange according to claim 1, characterized in that program modules receive change messages via the access interface in the event of status changes in packaging plant status data in the packaging plant data exchange.

10. The packaging plant data exchange according to claim 1, characterized in that program modules directly access the buffer for querying the availability of packaging plant status data, program modules accessing status values and/or metadata of the packaging plant status data via the buffer interface and/or preferably an access interface.

11. The packaging plant data exchange according to claim 1, characterized in that when an availability of packaging plant status data is queried, the buffer first searches internally for packaging plant status data and, if the search result is negative, it then searches in the database via the data storage interface for packaging plant status data.

12. The packaging plant data exchange according to claim 1, characterized in that accesses to the data storage interface are triggered only by the packaging plant data exchange and/or in that accesses to the data input interface and/or the access interface are triggered via a program module.

13. The packaging plant data exchange according to claim 1, characterized in that direct communication is prevented between at least two of the program modules and/or in that at least two of the program modules are anonymous to one another.

14. The packaging plant data exchange according to claim 1, characterized in that an access interface is set up to receive a unique identifier of a packaging plant status date from a program module and to signal data changes from packaging plant status data having the unique identifier to the program module.

15. The packaging plant data exchange according to claim 1, characterized in that the packaging plant data exchange is provided by one or more server devices and/or by one or more virtual servers.

16. The packaging plant data exchange according to claim 1, characterized in that the at least one first status value of the packaging plant represents a first measured value detected by a sensor of the packaging plant.

17. A method comprising: receiving first packaging plant status data via a data input interface of a packaging plant data exchange, wherein the first packaging plant status data represent at least one first status value of a packaging plant; storing and/or effecting storage of the at least one first status value represented by the first packaging plant status data in a database by a data storage interface of the packaging plant data exchange; wherein at least one program module adapted to a packaging device of the packaging plant communicates via the data input interface, and the data storage interface communicates with at least one database module adapted to the database, characterized in that an access interface communicates with the program module, accessing packaging plant status data via the access interface.

18. The method according to claim 17, characterized in that that the database is set up for the persistent storage of current and historical packaging plant status data.

19. The method according to claim 17 further comprising: detecting at least the first measured value by a sensor of the packaging plant; and communicating and/or effecting the communication of packaging plant status data to the data input interface via a program module.

20. A computer program comprising program instructions that cause a processor to execute and/or control the method according to claim 17 when the computer program is executed by the processor.

21. A server device or server system comprising a plurality of server devices and/or virtual servers arranged to execute and/or control the process according to claim 17.

Description

[0064] In the following, the subject matter is explained in more detail using a drawing showing embodiments. In the drawing show:

[0065] FIG. 1 a packaging plant data exchange according to a design example;

[0066] FIG. 2a-d the operation of a packaging plant data exchange with packaging equipment and databases.

[0067] The embodiment of the present invention described in this specification should also be understood as being disclosed in all combinations with each other. In particular, the description of a feature covered by an embodimentunless explicitly stated otherwiseshould not be understood in the present case to mean that the feature is indispensable or essential for the function of the embodiment. The sequence of the process steps described in this specification in the individual flow diagrams is not mandatory, alternative sequences of the process steps are conceivable. The process steps can be implemented in different ways, e.g. an implementation in software (by program instructions), hardware or a combination of both to implement the process steps is conceivable. Terms used in patent claims such as include, exhibit, include, contain and the like do not exclude other elements or steps. The expression at least in part covers both the case in part and the case in full. The wording and/or should be understood as meaning that both the alternative and the combination should be disclosed, i.e. A and/or B means (A) or (B) or (A and B). A plurality of units, persons or the like means, in the context of this specification, several units, persons or the like. The use of the indefinite article does not exclude a plurality. A single entity may perform the functions of several entities mentioned in the patent claims. The reference signs indicated in the patent claims are not to be regarded as limitations of the means and steps used.

[0068] FIG. 1 shows a packaging plant data exchange 2. Packaging plant data exchange 2 can be executed in a runtime environment, a server, a virtual server or the like. Here, in a switching network 4, which can be part of the packaging plant data exchange 2, a buffer memory 6, a data input interface 8, a database interface 10 and an access interface 12 can be implemented.

[0069] In addition, packaging plant data exchange 2 has an environment in which program modules 14.1, 14.2 as well as database modules 16 (or respective instances thereof) can be executed.

[0070] It can be seen that the program modules 14.1 can be configured as system program modules 14.1 and can each communicate with a packaging device 18a-c. In addition, a database module 16 can communicate with a database 20. The program modules 14.1 can also be configured as calculation modules and calculate and make available packaging plant parameters, e.g. from status values of the packaging plant.

[0071] Program modules 14.1 can be individually adapted to a wide range of packaging devices 18a-c. For example, a packaging device 18a may be a filling device provided by a first manufacturer, whereas a packaging device 18b may be a filling device provided by a second manufacturer. A packaging device 18c, for example, can be a tray packer or another device that can be operated within a packaging plant and that can output status data. The 18a-c packaging devices each have individual interfaces for outputting their status data. The status data can be retrieved from the packaging equipment 18a-c in various data formats via various interfaces and in different ways, so that uniform access to them is impossible. Changes may also occur at the interfaces of the packaging device 18a-c in the course of further developments, which must be mapped.

[0072] Program modules 14.1 are provided for this purpose. Each program module 14.1 can be individually adapted for a single 18a-c packaging device. Thus a program module 14.1 can be used to individually access a machine interface of a respective packaging device 18a-c and to read out the status data.

[0073] Using a defined data model, program modules 14.1 can output the status data received from the packaging equipment 18a-c as packaging plant status data. Both metadata and status values can be made available in a uniform data format. The data format can define variables, machines or lines. Depending on the data format, the status data can contain metadata and status values. For example, metadata can contain a name, an origin, a target, an origin, synonyms, or tags. This allows the various status data to be described in a uniform data structure.

[0074] Using variables, data points, in particular status values of various sensors, can be mapped. Machines can be used to map properties of machines and lines can be used to define links between machines and the layout of the packaging plant.

[0075] The uniformly formatted status data can be fed from the packaging equipment 18a-c into the switching network 4 via the program modules 14.1 and the data input interface 8.

[0076] The buffer memory 6 can store at least metadata of the status data, but preferably also has sufficient memory to store at least the current status values of status data. For persistent storage, it may be useful to store the status data in a database.

[0077] Similar to the packaging devices 18a-c, there are 20 different databases with different database protocols and access interfaces. In order to provide the highest possible flexibility for the packaging plant data exchange 2 or a system integrator, database modules 16 can be provided, which are individualized for each database 20. It goes without saying that both the program modules 14.1 and the database modules 16 must only be made available for the packaging equipment 18a-c and databases 20 available in the packaging plant. Individualisation can be based on the equipment, components and applications available in the packaging plant, so that program modules 14.1 and database modules 16 only have to support what is available.

[0078] In addition to the database modules 16 and the program modules 14.1, further program modules 14.2 can be provided with which, for example, information about the packaging plant can be calculated from status values. Such applications can also be provided as program modules 14.2 in packaging plant data exchange 2.

[0079] The data with which the program modules 14.1, 14.2, 16 communicate with the interfaces 8, 10, 12 and the buffer memory 6 can, for example, comply with the OMAC PackML standard or the Weihenstephan standard.

[0080] The program modules and/or the packaging plant data communication can provide an implementation of a data input interface. In particular, the Packaging plant data exchange may provide data input interfaces as functions, methods and/or classes. It may be possible for an instance of a program module to use a data input interface for communication.

[0081] Various additional functions can be made available within the switching network 4. For example, a safety function can be provided. This can be used to monitor write/read rights for various status data. It can be monitored which of the interfaces 8-12 can access status data. It is also possible to monitor which of the program modules 14.1, 14.2 can access data. Furthermore, a user management system is available with which access rights can be assigned to users and users can log in or log out. In addition, a logbook function can be provided for logging actions within the exchange network 4. In addition, standard functionalities can be provided, such as handling exceptions, loading program modules, debugging or the like.

[0082] FIG. 2a-d show how packaging plant status data is processed in plant data exchange 2.

[0083] After program modules 14.1 and database modules 16.1 have been implemented and/or instantiated and have logged on to the exchange network 4, they have access at least to the data input interface 8, the access interface 12 and the data storage interface 10 and/or, if applicable, the buffer memory 6 or the buffer memory interface 6a. The database module 16.1 preferably has access to the buffer memory 6 via the data storage interface 10. The program modules preferably have access to the buffer memory 6a via the buffer memory interface 6a, in particular read access.

[0084] If a machine parameter changes on a packaging device 18a, this can be registered by an appropriate sensor. The packaging machine 18a outputs the changed machine parameter, as shown in FIG. 2a, as a status value at its possibly proprietary machine interface.

[0085] Program module 14.1 is arranged to work with packaging device 18a. Program module 14.1 knows the machine interface of the packaging device 18a and can interpret the information accumulated there.

[0086] The program module 14.1 converts the received data into a data format for the packaging plant data exchange 2. In this data format, the data is preferably according to the OMAC PackML standard comprehensive metadata and status values. The data processed in this way are communicated from the program module 14.1 to the data input interface 8.

[0087] The data input interface 8 signals the program module 14.1 that the data has been received. In addition, information is transmitted from the data input interface 8 to the buffer memory 6. The buffer 6 checks whether information is already stored for this status date or not. If the status data are new, they are stored in the buffer 6 for the first time, if the status data are only value changes of known status data, these value changes are stored in the buffer 6.

[0088] In addition, the data storage interface 10 is used to store data in the database 20. For this purpose, the metadata as well as the status values are transferred from the data storage interface 10 in a uniform data structure to the database module 16.

[0089] The database module 16 is set up to communicate with a particular database 20 and transfers the corresponding data to the database 20 in the format suitable for the database 20. Thus the modified data are persisted by the packaging device 18a in the database 20 and are also stored in the buffer 6 for retrieval.

[0090] It can be seen that no direct communication between the database module 16 and the program module 14.1 is necessary for storing the data. It can also be seen that communication takes place exclusively via interfaces 8-12. The data input interface 8 is triggered by the program module 14.1, whereas the data storage interface 10 is triggered by the switching network 4.

[0091] FIG. 2b shows an example of how a program module 14.2, which, for example, evaluates machine parameters, can obtain information on the packaging plant data. In step A, a program module 14.2 can first request information on available packaging plant data via the buffer interface 6a of the buffer 6. The corresponding filter criteria can be specified by the program module 14.2. The query can preferably be based on metadata. The data format used in Packaging plant data exchange 2 is also used here.

[0092] In the buffer 6 such a request can first be processed internally. Here it can be checked in the buffer 6 whether corresponding data matching the query are available in the buffer 6. This internal search can only contain a search for metadata or can also retrieve status values.

[0093] In addition, in step B, the buffer 6 can check the presence of status values that match the filter set by program module 14.2 in step A via the data storage interface 10 in database 20. The corresponding data can then be transferred in step C from database 20 to buffer 6.

[0094] Preferably, the program module 14.2 receives information, in particular metadata on the available status data corresponding to the search query, from the buffer interface 6a. In the program module 14.2 a corresponding status date can then be selected and a subscription to this status date can be set in step D via the access interface 12. The program module 14.2 communicates the metadata, in particular a unique identifier of the date to be monitored, to the access interface 10. With the aid of the method described in FIG. 2b, each program module 14.2 can also retrieve a program module 14.1 of available status data and, by using a unique criterion which uniquely identifies status data, justify the interest in this data at the access interface 10.

[0095] FIG. 2c shows a data run if a status date has been changed according to the sequence in FIG. 2a and a program module 14.2 has subscribed to the corresponding status data at the access interface 12.

[0096] After a status value has been stored in the database 20 in the method according to FIG. 2a, the access interface 12 signals that a corresponding date has been changed. This signalling by the access interface 12 is performed for each program module 14.1, 14.2 that has registered interest (subscription) in the status date for the access interface 12.

[0097] The access interface 12 thus triggers all program modules 14.1, 14.2 that have an interest in a certain status date.

[0098] If the program module 14.2 detects that the status date has changed, status values can be retrieved. Two different options are possible.

[0099] On the one hand, it is possible for the program module 14.2 to retrieve 12 status values from the corresponding date after signalling a changed value via the access interface. Subsequently, the current status values are loaded from the buffer memory 6 by the access interface 12 and transmitted to the program module 14.2 via the access interface 12.

[0100] Here it is conceivable that if there is only one current value in the buffer memory 6, the buffer memory 6 also loads historical status values from the database 20 via the data storage interface 10 using the database module 16 and communicates them to the program module 14.2 via the access interface 12.

[0101] Another possibility is the direct access of the program module 14.2 to the buffer 6 via the buffer interface. The program module 14.2 can use the unique criterion to access a status date. Here, too, the buffer memory 6 can either provide locally, internally stored data, in particular status values, via a read interface, or alternatively or cumulatively query the database 20 via the data storage interface 10 and the database module 16 and, if necessary, also read out historical status values. These can then be made available to the program module 14.2.

[0102] It should be noted that access to cache 6 via program modules 14.1, 14.2, if immediate, can be read-only.

[0103] After a plant parameter has been calculated in a program module 14.2, the program module 14.2, as shown in FIG. 2d, can feed this changed plant parameter back into the system via the data input interface 8. The system parameter calculated by the program module 14.2 is transferred to the data input interface 8 in the uniform data format. From there, the value of the changed data is stored in the buffer 6 and in the database 20, as already shown for another status date in FIG. 2a.