Classifications

• • G—PHYSICS
  • G05—CONTROLLING; REGULATING
  • G05B—CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
  • G05B19/00—Programme-control systems
  • G05B19/02—Programme-control systems electric
  • G05B19/04—Programme control other than numerical control, i.e. in sequence controllers or logic controllers
  • G05B19/042—Programme control other than numerical control, i.e. in sequence controllers or logic controllers using digital processors
  • G05B19/0423—Input/output
• • B—PERFORMING OPERATIONS; TRANSPORTING
  • B65—CONVEYING; PACKING; STORING; HANDLING THIN OR FILAMENTARY MATERIAL
  • B65G—TRANSPORT OR STORAGE DEVICES, e.g. CONVEYORS FOR LOADING OR TIPPING, SHOP CONVEYOR SYSTEMS OR PNEUMATIC TUBE CONVEYORS
  • B65G43/00—Control devices, e.g. for safety, warning or fault-correcting
  • B65G43/10—Sequence control of conveyors operating in combination
• • G—PHYSICS
  • G05—CONTROLLING; REGULATING
  • G05B—CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
  • G05B2219/00—Program-control systems
  • G05B2219/30—Nc systems
  • G05B2219/45—Nc applications
  • G05B2219/45048—Packaging

Definitions

• Packaging Equipment Data Switching and Method of Operating Packaging Equipment Data Exchange The subject matter relates to packaging equipment data exchange, a method of operating packaging equipment data exchange, a computer program and a server for packaging equipment data exchange.
• Packaging systems are known in which a variety of different devices and components are often used, such as
• Drinking straws, points, cardboard boxes and cartoners are mostly come from different manufacturers and provide packaging equipment data, such as packaging equipment status data representative of the condition of the respective equipment, in various data formats for processing by a packaging equipment data exchange and / or other equipment / components of the packaging equipment. Also, facilities from different manufacturers make different packaging equipment data, such as packaging equipment status data representative of the condition of the respective equipment, in various data formats for processing by a packaging equipment data exchange and / or other equipment / components of the packaging equipment. Also, facilities from different manufacturers make different packaging equipment data, such as packaging equipment status data representative of the condition of the respective equipment, in various data formats for processing by a packaging equipment data exchange and / or other equipment / components of the packaging equipment. Also, facilities from different manufacturers make different packaging equipment data, such as packaging equipment status data representative of the condition of the respective equipment, in various data formats for processing by a packaging equipment data exchange and / or other equipment / components of the packaging equipment. Also, facilities from different manufacturers make different packaging equipment data, such as packaging equipment status data representative of the condition of the respective equipment
• a problem with these packaging systems is therefore that the packaging system data made available by the facilities of the packaging installation can not be further processed and evaluated uniformly due to the different data formats, so that individual packaging plants can be customized
• Components is particularly easy to customize.
• This task is objectively by a
• Packaging installation data exchange device according to claim 1. Furthermore, the object is achieved by a method according to claim 15 and a
• a packaging installation can be understood as an installation for packaging goods such as, for example, foodstuffs.
• a packaging installation can be understood to mean a beverage filling installation and / or a part of a beverage filling installation.
• a variety of different components is often used such as filling machines, applicators for applying closures and / or straws, switches, boxers and cartoners.
• Devices run various applications (e.g., in the form of a computer program executed by a processor of this component)
• packaging plant data in particular packaging plant state data, state data or packaging packaging state parameter values
• various data formats and / or via various machine interfaces for processing by a packaging plant data exchange and / or other facilities and / or applications.
• Machine information exchanged information can be further processed with software interfaces, as described below.
• cardboard / plastic / metal composite packaging are known, which are used for different flowable or pourable products.
• the main field of application of corresponding cardboard / plastic / metal Composite packaging is the packaging of beverages and heat-treated, in particular pasteurized, foodstuffs.
• Packaging is available in different forms. These are typically cuboid, cubic and cylindrical. One big difference is e.g. still with regard to the packing head, which is predominantly designed as a so-called gable or sloping gable.
• Packaging can be done in different ways and in different ways
• Materials are produced.
• a widespread possibility of their production is to produce a blank from the packaging material, from which by folding and further steps, first a packing jacket is produced and one end thereof can be closed. Through the still at least partially open portion of the packaging jacket, the package can then be filled.
• a packaging blank is formed on a mandrel of a mandrel wheel.
• Packing coats are very flat and thus can be stacked to save space. In this way, the blanks or packing coats can be made at a different location than the folding and filling of the packaging coats done.
• a material composites are often used, for example, a composite of several thin layers of paper, cardboard, plastic or metal, especially aluminum.
• Such packaging can be found in particular in the
• a packaging equipment data exchange for example, one of a server device or a server system (e.g.
• Server device or the subject server system which may be both virtual and immediate) provided function for conveying packaging plant state data (packaging plant parameters and / or state data) between different applications and / or facilities / components of a packaging system.
• packaging equipment data exchange is provided by a computer program (eg, the subject computer program) executed by at least parts of a processor of the server device or the server system.
• the computer program is a middleware program and / or a service layer program.
• a buffer of packaging equipment data exchange contains
• an intermediate storage of the packaging system data exchange only includes current state values for different states of the packaging installation.
• a cache of packaging equipment data exchange may include a limited number of historical state values for the various states of the packaging plant in addition to the current state values for various states of the packaging plant.
• the state value of a state datum or a variable may be different at different times. It is possible for a variable or a status data in each case a current state value and possibly historical
• State values can be provided with a time stamp, so that a time assignment of a state value is possible and a temporal sequence of state values of a state datum can be reconstructed.
• the cache serves as a cache to prevent the packaging equipment data exchange from having to access the persistent storage to access each state value. Also, the cache can serve as a buffer to buffer downtime in the persistent data store.
• Caching can reduce downtime between the
• the buffer is formed as a bidirectional memory, which allows both read accesses and write accesses.
• the buffer of the packaging equipment data exchange is part of a memory (e.g., program and / or main memory) of the memory
• the packaging equipment data exchange in particular a program module, implements at least one instance of a data input interface for
• a data input interface Communicate with facilities / components and / or applications of the packaging plant via the program module ready. If a data input interface is mentioned below, this can also be understood as meaning an instance of a data input interface. In particular, a
• Program module or an instance of a program module provide methods for instantiating instances of data input interfaces, or a program module can provide a method as a data input interface. It is understood that the packaging equipment data exchange via the
• Data input interface with a program module of other devices / components and / or applications of the packaging system can communicate at least indirectly (for example, data from the other components and / or
• a program module may also include an instance of a
• the communication takes place when a packaging device or
• Components and / or application of the packaging system communicates using a program module (eg a plug-in) via the data input interface.
• a program module may, for example, be adapted to the device / component and / or application of the packaging system. For example, one is
• Program module set up by the device / component and / or
• Packaging system prepared data and / or convert (for example, convert it into a predetermined data format) and then output via the data input interface or through the
• Data input interface to communicate is set up, for example, via
• Data input interface received confirmation and / or
• the program module can communicate via a standardized data input interface.
• Data input interface can be implemented identically for all types of program modules.
• each program module may implement an instance of a data input interface to which the
• Packaging devices / components provide their data in highly different ways via partially proprietary machine interfaces and require a variety of data models and data structures.
• Packaging plant data transfer must be objectively to such
• a system integrator only has to be responsible for the respective Setup interface to create a suitable program module and then to the full functionality of the
• More complex state data and the calculation of system parameters can be provided individually in a program module.
• the access to status data or state values takes place via an access interface (preferably
• the packaging plant data exchange can receive packaging plant state data from facilities / components and / or applications of the packaging plant via the respectively adapted program module.
• the program module can be inserted at the data input interface
• the machine data object is suitable for describing a machine. Also, alternatively or cumulatively, the program module at the
• a state data object comprising at least metadata of the state object and create a state value of the packaging device.
• Creating can be understood as instantiating a data object and / or creating and / or creating a state data in an object
• the data input interface provides means by which the program module in the packaging equipment data exchange or at the Data input interface can create the state data object.
• the program module in the packaging equipment data exchange or at the Data input interface can create the state data object.
• first instances of a state data object / machine data object can be created at the data input interface, and in the instance of a state data object / machine data object, the program module can store the metadata of the
• the metadata of the machine data object preferably comprise
• the data fields may contain a unique identifier, a name, a serial number and / or a machine category. Furthermore, a name of a program module, an information whether the machine is connected to the program module and / or communicates with and / or a
• the data input interface provides means by which the program module in the packaging system data exchange or in the
• Data input interface can create a machine data object.
• instances of machine data objects can first be created at the data input interface and, in the instance of a machine data object, the
• Program module set the metadata.
• a packaging device can be made known in a standardized form of packaging equipment data exchange.
• a state data object can contain both state values and metadata, as well as functions.
• the functions can be used to execute rules on the state data object.
• a function may be the return of values that correspond to a filter criterion, and a function may, for example, equality with Check a transferred instance of another state value object and return a corresponding Boolean value.
• a state value of a packaging installation may, for example, be understood to mean a value which is characteristic for a current and / or a past state of the packaging installation and / or a component of the packaging installation. Examples of such a state value are, for example, by a sensor of the packaging system and / or a component of
• Packaging system recorded measured value and / or an index of the
• Packaging installation and / or a component of the packaging plant such as a plant and / or component performance [. Packaging / hour) and / or Overall Equipment Effectiveness (OEE).
• a state data object as well as a machine data object may include an instance of a unique identifier.
• the unambiguous connoisseur can likewise be a data object and in each case be loaded as an instance in an instance of a state data object and / or a machine data object.
• Unique connoisseur can contain functions and values.
• the functions allow e.g. serialize the data object, create a hash code for the data object, check for equality with a passed instance of another data object.
• Packaging device of packaging equipment data exchange store in a standardized form.
• Metadata of the state object allow to describe the state object. Using the metadata, a state object can be clearly identified. With the help of metadata, a state object can be found. With the help of metadata, a state object can be suitable
• the metadata of the state object preferably comprise different data fields.
• the data fields can be a unique connoisseur or an instance of a unique connoisseur object, a name, a name a program module, a unique identifier of the data source, or an instance of a unique identifier object, a unique identifier of the component / device or application from which the state object into the
• Packaging entity data exchange or an instance of a unique identifier object, a unique identifier of the component / device or application from which the state value originates or contains an instance of a unique identifier object, a category, a data type, a synonym and / or an identifier be.
• the state values can preferably be stored as word (integer), string or double word.
• the unit and / or the type of measurement can be stored in the category and data type metadata.
• Some packaging devices have a standard machine interface.
• the machine interfaces can be used to store data in particular according to the PackML
• the machine interfaces can preferably be addressed by the transport protocol OPC UA.
• the metadata of the packaging device can be understood as a "nameplate.”
• the metadata can be read out in a standardized manner and can be read by the program module of the
• Packaging device are adjustable, editable and in particular programmed and that the program module this metadata of the packaging device for the Provides machine data object.
• the system integrator needs for such
• Packaging facilities create a customized program module, which can specify the metadata of the machine data object independently.
• a packaging device can be integrated, which has a proprietary interface.
• Status data is at least partially not retrieved via the machine interface.
• Condition values via the machine interface of the packaging device assigns these state values and provided for the state data object.
• the system integrator must create a customized program module for such packaging devices, which contains the metadata of the
• Packaging device to be integrated which is a proprietary
• status data is the
• Program module the state value via the machine interface of the
• a state data object can be created at intervals, eg cyclically or when the state value changes, and made available to the data input interface in the standardized format by the program module.
• some packaging devices have a standard machine interface. These can be used to exchange data, in particular in the PackML standard. These machine interfaces can preferably be addressed by the transport protocol OPC UA.
• the program module can use metadata of the state data object via the
• the metadata can be read out in standardized form and made available in a standardized manner in a machine data object by the program module of the data input interface.
• identifier with which state data objects can be assigned to specific groups.
• Such an identifier also called day, can by the
• Program module can be specified.
• the data model can provide a list of available identifiers from which one can be selected. This leads to a uniform grouping of status data objects.
• Packaging equipment data exchange aims to facilitate a system integration of various packaging equipment. This is also achieved by using the data input interface to create instances of
• Machine objects and status data objects in a unified data model is set up. Through the unified data model, the processing of the data in the packaging plant data exchange by various components,
• Program modules and database modules can access a unified set of data (instances of data objects), though two or more
• a wide variety of packaging equipment to be integrated into the system can.
• Each packaging device and each state is uniformly represented in the system by at least one instance of a machine data object and / or a state data object. Integrating new packaging devices in the system is simplified because only one program module at a time
• Packaging device must be adjusted, the data input interface to the packaging system data transfer remains identical. Even new ones
• the status data are made available exclusively via a program module which follows the data model of the packaging system data exchange and is adapted on the other side for the respective field of application, in particular adapted to a machine interface of a packaging device.
• Examples of a state value are a measured value acquired by a sensor of the packaging installation and / or a component of the packaging installation and / or a characteristic number of the packaging installation and / or a component of the packaging system
• Packaging equipment such as plant and / or component performance (e.g., packages / hour) and / or Overall Equipment Effectiveness (OEE). This can also be understood as a system parameter.
• the at least one first state value represented by the first packaging plant state data is stored, for example, in a database (a persistent store) that need not be part of the packaging plant data exchange.
• a persistent store is part of the persistent store
• the persistent memory is used, for example, for permanently storing the state values obtained by the packaging system data exchange.
• state values obtained by the packaging system data exchange.
• historical and current state values are stored for different states of the packaging installation.
• a current state value is to be understood as a value representative of a current state of the packaging installation. For example, this is the state value for this state, represented by packaging plant state data that was last checked for that state by an instance of
• a state value can also be calculated and provided in particular by a program module.
• a historical state value for a state is, for example, a state value represented by packaging plant state data that was previously (i.e., prior to the most recently obtained state for that state
• Packaging equipment status data by the packaging equipment data exchange.
• State values can be stored in a state data (variable)
• the packaging equipment data exchange preferably provides one
• Data storage interface communicates with the persistent storage through a database module (e.g., send data objects to be stored to the persistent storage and / or receive storage failure and / or storage acknowledgment notifications from the persistent storage).
• a database module e.g., send data objects to be stored to the persistent storage and / or receive storage failure and / or storage acknowledgment notifications from the persistent storage.
• Data storage can work, in each case a database can be addressed by a specially adapted database module.
• the database engine can communicate with a standardized data storage interface.
• Datastore interface can be the same for all types of database engines.
• the data storage interface can also work with the same data model as the data entry interface. On the other hand, one each
• Database module for each configured at least one database. It was recognized that different databases provide their data in very different ways via partially proprietary interfaces or
• a system integrator only has to create a suitable database module for the respective database and can then access the full database
• Metadata may be, in particular, the condition data uniquely identifying criteria (unique connoisseur).
• a unique connoisseur may in particular be a name and a data source within the metadata
• Packaging plant data exchange thus ensures consistency of the data. To ensure that the cache, the data input interface, and the data storage interface can reliably and uniquely access the state data, they form a common switching network. In order to further ensure that data within the packaging plant data exchange is changeable exclusively via the said interfaces
• a program module can exchange state data with the packaging equipment data exchange exclusively via the switching network.
• the program modules are preferably transparent to each other and can not communicate with each other. Rather, all communication takes place
• Data input interface and the data storage section are operated independently of each other. This means that instances of program modules communicate independently via the one data input interface and one access interface. Between the interfaces is a communication
• Each instance of a program module carries the data communication with the associated one
• packaging plant parameters can be understood as state data objects.
• packaging equipment parameters such as OEE or other information related to the packaging equipment may be calculated from the packaging equipment condition data. Each of these calculations requires at least read access to the
• Packaging system state data results of the calculation can be considered new Packaging equipment status data are fed via the data input interface in the data exchange.
• a program module which is set up for the calculation of packaging installation parameters, first accesses the state data in read-only fashion, and then changes or changes
• Calculation of a packaging equipment status value feeds this condition value into the packaging equipment data exchange via the data input interface.
• packaging plant status data may be formed from metadata and state values.
• the status data can be clearly identified and assigned with the help of the metadata.
• the state values then describe certain states, in particular values detected by sensors or values calculated using algorithms.
• Access packaging equipment status data In order to initiate such access, the program modules must be aware of within the
• Latch preferably a read interface, via which an immediate read access to at least the metadata is made possible.
• the buffer is equipped so that it preferably stores state data, in particular in the form of a cache. It is not necessary for the buffer to permanently hold all status data. In particular, it is possible that the cache stores only metadata in parts. It is also possible that the cache is only a subset of all available
• the cache preferably retrieves metadata about all available state data from the persistent data store and for a
• the Latch be equipped so that it searches for the corresponding packaging equipment status data via the data storage interface in the database. If corresponding state data are found in the database, the metadata for this purpose can preferably first be made available to the intermediate memory via the data memory interface. According to one embodiment, it is proposed that accesses to the
• Data storage interface are triggered only by the packaging equipment data exchange, with accesses to the data input interface via a
• Program module are triggered.
• the data storage interface is preferably accessible only via the buffer, so that a consistent data storage is ensured in the database. Read accesses and / or write accesses to status data via the program modules preferably take place via the data input interface and / or the access interface.
• the program modules are transparent to each other. Immediate communication between two program modules is prevented. This ensures that any change to state data about the
• the persistent store is configured to communicate a corresponding store acknowledgment notification to the server A data storage interface when the at least one first state value represented by the packaging equipment status data has been stored in the persistent storage.
• the persistent memory is set up for
• the persistent memory is configured to permanently store current and historical state values of the packaging installation.
• the persistent store for example, historical and current state values for different states of the packaging plant will be stored.
• the persistent store for example, historical and current state values for different states of the packaging plant will be stored.
• a packaging plant data exchange is, for example, by a
• a state value of the packaging installation represents a measured value acquired by a sensor of the packaging installation.
• the state value may include the measured value and / or the
• Measured value correspond.
• the state value may also contain, for example, a count value and / or a truth value.
• a count value may represent, for example, the frequency that the measured value was detected by the sensor; such a truth value indicates, for example, whether the measured value is greater than a threshold value and / or less than a threshold value and / or equal to a threshold value.
• sensors for detecting the measured value are a temperature sensor, a light barrier sensor, a pressure sensor, a humidity sensor, a camera, a voltage sensor and / or a fill level sensor.
• a computer program may include program instructions that cause a processor to execute and / or control the subject method when the computer program is executed by the processor. In this case, either all steps of the method can be controlled, or all steps of the method can be executed, or one or more steps can be controlled and one or more steps can be executed. Under a processor are intended in this specification, among others
• Control units microprocessors, microcontrollers such as microcontrollers, digital signal processors [DSP], application specific integrated circuits (ASICs) or Field Programmable Gate Arrays (FPGAs) can be understood, for example, over a network such as the Internet, a telephone or mobile network and / or
• the computer program may be at least partially software and / or firmware of a processor, and may equally be implemented at least in part as hardware.
• the computer program may be on a computer readable
• Storage medium to be stored for example, a magnetic, electrical, optical and / or other storage medium.
• the storage medium may for example be part of the processor, for example a (non-volatile / persistent or volatile) program memory of the processor or a part thereof.
• the Storage medium for example, a physical or physical
• a server device may be used to execute and / or control the
• steps of the subject method may be controlled by the means, or all steps of the method of the invention may be performed by the means, or one or more steps controlled by the means and one or more steps performed by the means. Different steps may optionally be performed or controlled by different means.
• a server system with multiple server devices and / or multiple virtual servers may be configured to execute and / or control the subject method, or may include respective means for performing and / or controlling the steps of the subject method.
• server devices and / or the virtual servers are configured to jointly execute and / or control the subject method. It is understood that either all the steps of the subject method are controlled by the means of the server devices and / or the virtual servers, or all steps of the method according to the invention by the means of
• Server devices and / or the virtual server, or one or more steps are controlled by the resources of the server devices and / or the virtual servers, and one or more steps are performed by the resources of the server devices and / or the virtual servers.
• server devices and / or the virtual servers of the server system may be located at one or more different locations.
• Server devices and / or the virtual servers of the server system form, for example, a server cloud and / or a distributed system.
• Several virtual Servers can be run simultaneously on a server device. It should under a virtual server, the software and / or hardware replica of the hardware architecture of a (physical) server device through the
• the means of the disclosed server device may include hardware and / or software components.
• the means may for example comprise at least one memory with program instructions of a computer program (e.g.
• At least one server device should be understood as comprising at least one processor and at least one memory with program instructions, wherein the at least one memory and the program instructions are arranged, together with the at least one processor to cause the server device, the method according to At least partially (eg, alone or in conjunction with multiple server devices of the server system) execute and / or control.
• a system includes a subject server device or a subject server system; and a packaging plant.
• Fig. 1 a packaging equipment data exchange according to a
• Fig. 2 is a data model of a machine data object
• Fig. 1 shows a packaging equipment data exchange 2.
• Packaging equipment data exchange 2 may be executed in a runtime environment, a server, a virtual server, or the like.
• a switching network 4 which may be part of the packaging system data exchange 2, a buffer 6, a data input interface 8, a
• the packaging plant data exchange 2 also has a
• program modules 14.1 can be configured as system program modules 14.1 and can each communicate with a packaging device 18a-c.
• a database module 16 may communicate with a database 20.
• the program modules 14.1 can be customized to different
• Packaging devices 18a-c be set up.
• a packaging device 18a may be a filling device and a first Manufacturers may be provided, whereas a packaging device 18b may be a filling device of a second manufacturer.
• Packaging device 18c may be, for example, a tray packer or other device that can be operated within a packaging system and which can output state data.
• the packaging devices 18a-c each have individual machine interfaces in order to output their status data.
• the status data are very different from the packaging devices 18a-c in a wide variety of data formats
• Machine interfaces and in a different way retrievable, so that a uniform access to this is impossible. Also can contact the
• each program module 14.1 may be individually adapted for a single packaging device 18a-c.
• a program module 14.1 can individually access a machine interface of a respective packaging device 18a-c and read out its respective status data.
• the program modules 14.1 can read the status data received from the packaging devices 18a-c as
• Metadata and status values can be made available in a uniform data format.
• the data format can define variables, machines or lines.
• the state data may contain metadata and state values.
• metadata may include a name, an origin, a destination, an origin, synonyms, or tags. This allows the various status data to be stored in a uniform data format
• the cache 6 can store current instances of state data objects and machine data objects. For persistent storage, it may be useful to outsource the state data to a database 20. Similar to the packaging devices 18a-c, a very wide variety of databases 20 with a wide variety of database protocols and
• Database interfaces In order to provide as much flexibility as possible for the packaging equipment data exchange 2 or a system integrator, database modules 16 can be provided which are individualized for a respective database 20. It is understood that both the
• Program modules 14.1 as well as the database modules 16 must be made available only for the packaging facilities 18a-c respectively databases 20 present in the packaging installation. Customization may be based on the facilities present in the packaging plant,
• Condition values Information about the packaging system can be calculated. Such applications may also be provided as program modules 14.2 in the packaging equipment data exchange 2.
• Interfaces 8-12 can access state data. It is also possible to monitor which of the program modules 14.1, 14.2 can access data. Furthermore, a user management exists with which access rights can be assigned to users and users can log in or out. In addition, one can
• Logbook function be provided with the actions within the switching network 4 can be logged.
• standard functionalities can be provided, such as the handling of exceptions, the loading of program modules, debugging or the like.
• a packaging device 18a may be a machine having a machine interface through which data can be exchanged in a standardized format.
• this format works according to the PackML standard.
• the machine interface can support the transport protocol OPC UA.
• a first program module 14.1 may be provided, which communicates with the packaging device 18a via the known machine interface.
• the program module 14.1 can first retrieve information about the machine itself from the packaging device 18a.
• the program module 14.1 then creates an instance of a. Using the data input interface 8
• Packaging device 18a retrieved information. This can be done at the
• Data input interface 8 a corresponding method can be provided over which the instance of the machine data object can be created.
• a second packaging device 18b may also be in the
• Packaging plant data exchange 2 are connected.
• This can be a second Program module 14.1 be provided, which is adapted to the
• Packaging device 18b is. Since the packaging device 18b e.g. Unlike the packaging device 18a does not have a standardized machine interface, the second program module 14.1 also can not access machine parameters in a standardized form. In particular, the
• Packaging device 18b be such that on their machine interface no machine information can be retrieved.
• a coded, entered, parameterized and / or edited knowledge about the machine can be present in the second program module 14.1.
• the second program module 14.1 now also instantiate an instance of a machine data object and enter the coded information about the machine in this instance.
• an instance of a machine data object can be created for each type of machine or packaging device via the data input interface 8 by a program module 14.1.
• FIG. 2 shows a machine data object 22.
• the machine data object 22 may have various property fields defined in the data model.
• the data types of the property fields 24a-f are firmly defined. When instantiating an instance of a machine data object 22, these property fields 24a-f may be filled with values from the program module 14.1.
• a first property field 24a may be, for example, a name field having the data type "string.”
• a second data field 24b may be a string and contain a serial number
• a third data field 24c may be an object data field in which an object of the type "enumeration " is available. In such an object, for example, machines can be stored in categories.
• a data model of such enumeration object 26 is also shown.
• a wide variety of machine types can be predefined and an instance of such a data object can contain one of the predefined values.
• Values may, for example, describe packaging devices such as, for example, a filling device, applicator, storage table, conveyor belt, robot, tray packer, printer, switch, scanner or the like.
• Machine properties may be predefined in the data model.
• Another property field 24d may be, for example, the name of the
• Program modules and be specified as a string.
• additional property field 24e may indicate whether the machine is connected to the program module or not communicating with the program module, and may be coded as a boolean value, for example.
• another property field 24f may include a unique identifier and be defined, for example, as a "unique identifier" object.
• FIG. 3 shows a data model of an object "unique connoisseur" 28.
• a data object 28 can contain both functions 30 and properties 32. Possible functions of such a data object can be, for example, a
• Return value can be a boolean value.
• a function may include returning a hash code of the data object 28 whose value may be defined as an integer.
• a function may also include converting the data object 28 into a string, for example, for serialization.
• the properties Name and Type can be defined in a data object 28, where the name can be defined as a string and the type can be an object of the enumeration type.
• an enumerated data object for the Type property can be a machine, device, program module, or external system. This can be used to determine how the corresponding data object was inserted into the system.
• an instance of the data object 22 is created during the runtime of the packaging installation data exchange 2 and in this creation an instance of an enumeration object 26 having a corresponding value and an instance of an object "unique connoisseur" 28 having the corresponding values is instantiated in addition to the properties 24a d.
• This instance of the data object 22 then represents a machine or packaging device 18a, b.
• Packaging device 18. a the program module 14.1 first instantiate one or more data objects of the type state data. This instantiates that
• Program module 14.1 at the data input interface 8 a corresponding instance.
• Program module 14.1 both metadata of the state object and state data available. First, the metadata of the state object is read from the machine 18a and entered in the instance of the state data object. In addition, the program module 14.1 can create an identifier [Tag], which can also be read out via the machine interface of the packaging device 18a.
• a proprietary machine interface is available for the packaging device 18b.
• the program module 14.1 may be programmed to retrieve the states via the proprietary interface.
• the program module 14.1 at the instantiation corresponding state data objects via the data input interface 8 to pass this metadata or metadata of the respective instance.
• a set of. Can then be generated via a respective program module 14.1
• State data objects are instantiated while metadata are either provided via the machine interface or stored in a program module 14.1.
• 4 shows a data model of a state data object.
• a state data object may include a metadata object 34 with both functions 36 and properties 38.
• one method 36 may be checking for equality. This method can pass a state data object or an instance thereof, and a Boolean return value can indicate whether the transferring data object matches the actual data object.
• the properties 38 may include the name of the state data object as a string and the name of the program module 14.1 that instantiated the object as a string.
• instances of data objects 28 may be the source of the data object, namely who has introduced this data object into the system and the target of the data object, namely to whom
• Another property can be a value object that can contain an instance of an enumeration object.
• a value category may include a raw signal, a raw time series, a calculated time series, as well as a calculated signal.
• Another property can be a data type that comes from an enumeration data type and can be encoded as a word, double word, or string, for example.
• synonyms and identifiers may be provided, each of which may be instances of corresponding data objects.
• the synonyms may include, for example, descriptions for the measurement unit.
• the identifiers can be, for example, freely definable strings.
• a further data object 40 can be provided for the state value.
• This data object 40 may also include functions 42 and values 44.
• the functions 42 may include a parity check and include a return function of a value.
• the return function can be given a filter information about certain values and
• a value can be an object of an instance of a value object in which, for example, a time stamp and / or an actual measured value can be stored.
• a data object may also contain a function that can check for equality.
• a program module 14.1 detects a change in value at the machine interface of the packaging device 18a, the value can be changed via a corresponding method at the data input interface 8 using the corresponding instance of the state object. The same can be done through a second
• Program module 14.1 done, which on a proprietary packaging device 18b is connected.
• value changes can be transferred via corresponding methods to the data input interface 8 using the instances of the respective status data objects.
• the program modules 14.2 can, for example, a key figure OEE (Overall
• Access interface 12 and the buffer 6 can be provided.
• the program modules may instantiate a state data object having a tag (state) at the data input interface 8.
• the Target property of the respective state data object is created using the unique identifier of the respective machine.
• the program modules for each of the machines can address the state data objects with the type state.

Landscapes

• Physics & Mathematics (AREA)
• General Physics & Mathematics (AREA)
• Engineering & Computer Science (AREA)
• Automation & Control Theory (AREA)
• Testing And Monitoring For Control Systems (AREA)
• Stored Programmes (AREA)
• Computer And Data Communications (AREA)
• Programmable Controllers (AREA)

Applications Claiming Priority (2)

Publications (1)

Family

ID=60953882

Family Applications (1)

Country Status (6)

Families Citing this family (1)

Family Cites Families (9)

• 2017
  • 2017-02-15 DE DE102017103017.4A patent/DE102017103017A1/de not_active Ceased
• 2018
  • 2018-01-11 WO PCT/EP2018/050605 patent/WO2018149564A1/de active Search and Examination
  • 2018-01-11 US US16/485,590 patent/US20200004217A1/en not_active Abandoned
  • 2018-01-11 JP JP2019564580A patent/JP2020507876A/ja active Pending
  • 2018-01-11 CN CN201880012225.5A patent/CN110300935A/zh active Pending
  • 2018-01-11 EP EP18700215.9A patent/EP3583475A1/de not_active Withdrawn

Also Published As

Similar Documents

Legal Events