Production control system

Abstract

A production control system (1) having an arrangement of manufacturer-specific modules, comprising modules for controlling production units, modules for controlling logistics units and/or modules for providing and/or processing product data (6). Proprietary data models of manufacturer-specific modules are linked via at least one ontology unit.

Claims

1. A production control system (1) having an arrangement of manufacturer-specific modules, comprising modules for controlling production units, modules for controlling logistics units and/or modules for providing and/or processing product data (6), wherein proprietary data models of the manufacturer-specific modules are linked via at least one ontology unit, wherein in the ontology unit ontology-forming class structures are provided, which have classes structured in hierarchies or groups, by means of which a semantic networking of the proprietary data models is feasible, wherein the ontology unit has a specified number of inference units by means of which classes of ontologies are linkable, and wherein the inference units form interface units for different proprietary data models.

2. The production control system (1) according to claim 1, wherein the semantic networking of the proprietary data models is configurable.

3. The production control system (1) according to claim 1, wherein the ontologies are described by means of standard protocols.

4. The production control system (1) according to claim 3, wherein an RDF (Resource Description Framework) is used as standard protocol.

5. The production control system (1) according to claim 1, wherein an ontology unit is provided in the form of a resource unit (2), which is configured to generate data that define production processes.

6. The production control system (1) according to claim 1, wherein an ontology unit is provided in the form of a process unit (3), which is configured to program production and/or logistics units.

7. The production control system (1) according to claim 1, wherein an ontology unit is provided in the form of a product unit (4), which is configured to process product data (6).

8. The production control system (1) according to claim 1, wherein a superordinate ontology unit is provided as ontology unit, which forms a control logic (11).

9. The production control system (1) according to claim 1, wherein self-learning sets of rules are provided.

10. The production control system (1) according to claim 1, wherein said production control system is integrated into a cloud computer network.

Description

BRIEF DESCRIPTION OF THE DRAWINGS

(1) The invention is explained below on the basis of the drawing. The figure shows:

(2) FIG. 1: A block diagram of an embodiment example of the production control system according to the invention.

(3) FIG. 2: Schematic representation of the production control system according to the invention

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

(4) FIG. 1 shows an embodiment example of the production control system 1 according to the invention. The production control system 1 serves to control production processes and logistics processes in a production facility. In the present case, the production facility is formed as a so-called smart factory, in which an arrangement of production cells and multiple autonomous driving vehicles, in particular AGVs (automated guided vehicles), are provided. Different production or assembly processes are executed in the individual production cells. Logistics processes are carried out with the autonomous driving vehicles. In particular, AGVs are used to transport materials, parts to be produced or assembled units.

(5) The production unit may be used in particular for the production of motor vehicles.

(6) According to the invention, the production control system 1 has an arrangement of ontology units by means of which proprietary data models of manufacturer-specific production cells, logistics units and also product development-specific data and processes are semantically networked.

(7) In general, an ontology unit provides ontology-forming class structures, which have classes structured in hierarchies or groups, by means of which a semantic networking of the proprietary data models is feasible.

(8) Appropriately, the semantic networking of the proprietary data models is configurable.

(9) Advantageously the ontologies are described by means of standard protocols.

(10) In particular, an RDF (Resource Description Framework) is used as standard protocol.

(11) As FIG. 1 shows, a resource unit 2, a process unit 3 and a product unit 4, which are controlled by a unit control logic 11 as superordinate ontology unit, are provided as ontology units. These ontology units form a virtual model of the processes carried out in the production facility.

(12) In the individual ontology units ontology-forming object models are provided, which are linked with each other via suitable ontological links 5, such as inference units, and thus manage a semantic networking of proprietary data models existing in the resource unit 2, the process unit 3 and the product unit 4.

(13) In the resource unit 2, ontologies are used to structure and digitally make available data that describe and define production processes. The data form production-specific proprietary data models, which are integrated via ontologies into a harmonized data stream that can flow across all units of the production facility.

(14) The production sequences generally include not only production processes but also logistics processes.

(15) In the process unit 3, specific production processes for production or work means such as robots are programmed in an executable program code (e.g. in a PLC code) in dependence on data from proprietary data models of the resource unit 2 and the product unit 3. The ontologies enable a harmonizing data transfer between the process unit 3 and the resource unit 2 and the product unit 4 without having to provide interfaces for that purpose at a system level.

(16) Product data 6 are provided and made available in the product unit 4. As FIG. 1 shows, in dependence on external, customer-specific product specifications 7 product data 6 are made available to the product unit 4 in proprietary data modules, for example as CAD data.

(17) These product data 6 are processed and made available in the product unit 4. In particular, the product data 6 are stored permanently, preferably non-volatilely, as persistence data 8 in a working memory as unchangeable storage means.

(18) Furthermore, using the ontologies of the product unit 4, digital models are generated from the product data 6, which are stored as so-called digital twins 9.

(19) The persistence data 8 and the digital twins 9 can be analyzed by means of an analysis unit 15.

(20) The resource unit 2, the process unit 3 and the product unit 4, which have ontologies, are controlled and coordinated by a superordinate ontology unit as control logic 11.

(21) On the whole, the resource unit 2, the process unit 3, the product unit 4 and the superordinate ontology unit form an ontology model with which all proprietary data models of the production unit are semantically networked, such that a standardized, harmonized data stream of all data of the overall system is achieved between all units of the production unit, without the need to use physical interfaces at a system level to adapt data to be transmitted.

(22) The resource unit 2 is used to prepare proprietary data from machine manufacturers who supply and provide work or production means such as processing machines and logistics units such as AGVs with defined functionalities.

(23) The product unit 4 is used to prepare and provide customer-specific proprietary product data 6.

(24) Finally, in the process unit 3 proprietary data are also generated by process designers by generating there executable program codes for production or work means.

(25) The data and programs generated in the resource unit 2, the process unit 3 and the product unit 4 are fed to a validation layer 12 and a programming layer 13.

(26) A check and validation of created program codes is performed in the validation layer 12. In particular, commissioning is carried out by checking whether the programmed processes are feasible, in particular whether they are collision-free.

(27) After successful validation, machine codes for the production and work means are generated using the programming layer 13.

(28) A normalization layer 14 is provided as a further component of the ontology model according to the invention. There, program code written in high-level languages is translated into application software such as PLC software.

(29) Finally, an adapter layer 15 is provided, which establishes the connection to communication units 16 such as mail, internet and the like. In addition, the adapter layer 15 is used to establish connections with external units 17 of suppliers, partner companies and the like.

LIST OF REFERENCE NUMERALS

(30) (1) Production Control System (2) Resource unit (3) Process unit (4) Product unit (5) Link (6) Product data (7) Product specification (8) Persistence data (9) Digital twins (10) Analysis unit (11) Control logic (12) Validation layer (13) Programming layer (14) Normalization layer (15) Adapter layer (16) Communication unit (17) External units (20) Ontology unit (21) Arrangement of manufacturer-specific modules (22) Modules for controlling production units (23) Modules for controlling logistics units (24) Modules for providing and/or processing product data (31) Proprietary data model (32) Proprietary data model (33) Proprietary data model (40) Production units (41) Logistics units