WO2015150184A1

WO2015150184A1 - Production management system and method

Info

Publication number: WO2015150184A1
Application number: PCT/EP2015/056379
Authority: WO
Inventors: Marco LAMPE; Sebastian WREDE; Viktor SARTISON; Christoph DREYER
Original assignee: Harting Kgaa
Priority date: 2014-04-04
Filing date: 2015-03-25
Publication date: 2015-10-08

Abstract

The invention relates to a production management system for the automated manufacture of batches of products containing a multiplicity of end products. The production management system comprises: at least one production module (10) for producing an intermediate product from a starting product, a planning device (6) for storing a predefined production sequence and a coordination device (8) with at least one database (7) for controlling the at least one production module. In order to create a uniform manufacturer-independent and control-independent process model, data packets are transmitted between the at least one production module (10) and the at least one database (7) via a logical bus (14), wherein the data packets comprise parameters of the starting product and/or of the intermediate product and/or of the production module as useful data and an identification of the production module and of the database.

Description

Manufacturing management system and process

The invention relates to the automation of a modular production platform and a modular production platform. In particular, but not exclusively, the invention relates to the manufacturing management system according to the preamble of

Claim 1 and a corresponding method for the automated production of Produktlosen with a variety of end products.

In order to automate the production of product lots consisting of a large number of end products, production management systems are used. Such manufacturing management systems connect the actual production processes of the "Manufacturing Execution System" (MES) and the

Resource planning of the enterprise, "Enterprise Resource Planning" ERP with each other and play an increasingly important role within the production IT, whereby not only data from the production is collected, condensed and analyzed, but the production is supported on the basis of this data planing and controlling ,

A production management system for automated production of product lots with a large number of end products accordingly comprises one or more production modules, which in turn have one or more processing components. The processing components of the production modules produce intermediate products from one or more input products, which are further processed in a subsequent production module or ejected as an end product.

The planned and predetermined production sequence is stored in a planning facility of the production management system. The production modules are controlled by a coordination device. Between the scheduler and the coordinator, a scheduling coordination interface is provided, and between the scheduler and the manufacturing modules with their scheduling components is a scheduling interface

intended. The planning coordination interface is dependent on the predetermined production sequence generates a control sequence for each manufacturing module, and the coordination execution interface generates a processing sequence for each processing component in dependence on the control sequence.

G. Reinhard et al., "Lecture notes Technical Operations Management II", TU Munich, 1996, pp. 29 - 34, gives an overview of production management systems. There, a computer-integrated production CAM with planning computer and DNC computer is described.

DE 10 2006 027 669 A1 discloses a computer-implemented workflow machine for managing a work list. The machine contains a worklist server to provide services and to store a

A worklist entry, a task scheduler that breaks down the worklist entry stored by the worklist server, a task interpreter for receiving the worklist and separating the worklist into an action, and an actor and a task manager assigned to the task scheduler and actor the worklist is specified is coupled.

DE 102 06 903 A1 discloses a method for creating software applications, in particular for MES systems. Objects (with data, attributes, behavior, functions) for software applications, in particular MES applications, are linked with meta-information, structured as hierarchical trees (OB1, OB2) (whereby different representation forms are selectable) and interlinked (lateral and / or or horizontal). At runtime, the objects (K1 -K4, KV-K4 ') are combined into software applications, with the overall function of the software applications being derived from the structure of the hierarchical trees (OB1, OB2). It can be software applications for MES systems, for

Automation systems, for industrial controls (also

Motion control) and for office applications (office area).

An essential part of manufacturing management systems with a modular production platform are configurable autonomous manufacturing modules. They are equipped with plug-and-produce capabilities, their own PC-based real-time control, a central, module-independent man-machine interface and equipped with different process components. The process components include, for example, manufacturing, production and testing processes.

A disadvantage of the prior art is that the

Process model, which is assumed in a manufacturing management system, usually to specifications of the manufacturer of the manufacturing modules and the

appropriate controls must be adjusted.

The object of the present invention is therefore to provide a uniform manufacturer-independent and control-independent process model, which in all

System levels and process steps remain consistent and allow the description of a production process within a production line based on the capabilities of the configurable manufacturing modules.

This task is solved by the production management system for

automated production of product lots with a plurality of end products according to claim 1 or the corresponding method according to claim 9. Preferred embodiments are the subject of the respective subclaims.

The invention provides, in addition to the above-mentioned interfaces, a further data connection from the manufacturing modules to the coordination device, via the parameters of input product, intermediate product or end product and

Manufacturing module to be reported to the upper levels.

The generic manufacturing management system for automated production of product lots with a variety of end products includes:

at least one production module with at least one processing component for

Generating an intermediate product from at least one input product, a planning device for storing a predetermined production sequence, a coordination device with at least one database for controlling the at least one production module,

a scheduling coordination interface for generating at least one

Control sequence for each production module depending on the given production sequence, a coordination execution interface for generating a

Processing sequence for each processing component depending on the control sequence.

The production management system according to the invention is further developed by a logical bus between at least one production module and the at least one database for the transmission of data packets, wherein the

Data packets at least comprise: parameters of the at least one

Input product and / or the intermediate product and / or the

Manufacturing module as user data and an identification of the respective

Manufacturing module and the respective database, and wherein each manufacturing module has at least one listener module for retrieving predetermined parameters and for sending to databases registered with the listener module.

Preferred embodiments of the invention

Manufacturing management system have one or - as far as technically possible and meaningful - several of the following features:

A routine database for storing script and service task routines, wherein the coordination execution interface when generating the processing sequence at least one routine of at least one

Assigns real-time-capable basis function to a processing component;

• the real-time capable basic functions correspond to one or more PLC routines of a processing component;

• an enterprise service bus, via which the planning coordination interface is connected to a business IT, an ERP system and / or an MES system;

The data link comprises a Robotics service bus;

• a module bus connecting the production modules;

The at least one production module comprises a parameter database for storing the parameters of the at least one input product and / or the intermediate product and / or the production module via the Robotics service bus;

• the coordinator and / or the planning organization via the

Enterprise service bus has access to the parameter database. The corresponding method for the automated production of product lots with a multiplicity of end products by producing intermediates from in each case at least one input product by at least one production module having at least one processing component comprises the steps:

Storing a predetermined production sequence in a planning device,

Controlling the at least one production module by a

Coordination device with at least one database,

Generate at least one control sequence for each manufacturing module in

Dependence on the given production sequence by a

Planning coordination interface,

Generating a processing sequence for each processing component in

Dependence on the control sequence by a

Coordination execution interface and

Transmission of data packets via a logical bus between at least one production module and the at least one database, the data packets at least comprising: parameters of the at least one input product and / or the intermediate product and / or the manufacturing module as user data and an identification of the respective manufacturing module and the respective database and querying and sending to a database predetermined parameters by at least one Lister module of the respective manufacturing module, in the

at least one listener module of the respective production module is registered.

Preferred embodiments of the method according to the invention have one or - if technically possible and reasonable - several of the following features:

The production sequence is stored as an instruction set, and the scheduling coordination interface divides the instructions of the

Production sequence in user interface (HMI) instructions,

Activity instructions, inspection instructions;

The coordination execution interface assigns each activity instruction to at least one manufacturing module for executing one

A manufacturing step, each user interface (HMI) instruction of at least one user interface for adjusting the manufacturing steps by a user, each inspection instruction of at least one

Inspection unit for acquiring actual parameters and comparisons with desired parameters; The coordination execution interface assigns a script or a service task routine in a routine database to a real-time capable basic function of a processing component for generating a machine-specific processing sequence;

• The script or service task routines are called HyperCard or

JavaScript routines stored;

• The script or service task routines are plug-in routines

saved

The planning coordination interface communicates with a business IT, an ERP system and / or an MES system via an enterprise service bus;

• the coordination execution interface communicates with the manufacturing modules via a Robotics service bus;

• the production modules are connected to each other via a module bus,

A further step is to store the parameters of the at least one

Input product and / or the intermediate product and / or the

Manufacturing module in a parameter database of at least one

Manufacturing module via the Robotics service bus;

• the coordinator and / or the planning organization via the

Enterprise service bus has access to the parameter database.

In particular, the invention has the following advantageous property. Thanks to the data connection according to the invention, it is possible to track and monitor each individual workpiece during processing, so that an "individualized" production is achieved

different products or components in the modular production line is only by the individual assignment of the product or component to instanced production-related process models, an identification of the product or component in the transition between the manufacturing modules and the decoupling of the

Material flow from the specific production process.

Further features and advantages of the invention will become apparent from the following description of preferred embodiments, reference being made to the accompanying drawings. Fig. 1 shows the schematic representation of an embodiment of the manufacturing management system according to the invention.

Fig. 2 shows an example of the inventive implementation of a

Production sequence in a control sequence for manufacturing modules.

FIG. 3 shows an example of the formulation according to the invention

Processing sequence for the processing component of a production module as a function of the control sequence.

Fig. 4 shows the example of an activity diagram in the transition from the

Planning level for execution level.

According to the invention, a three-layer system architecture consisting of a planning level 1, a coordination level 2 and an execution level 3 was developed on the basis of architectural patterns from software / automation technology and robotics as well as the modularization levels identified in the project (production line and module, process component). This is shown in FIG. 1.

The planning level 1 includes a component 4 for resource planning (ERP) and a component 5 for execution routines (MES). The

Resource planning 4 and the execution routines 5 are jointly available to a planning device 6, which is indicated in FIG. 1 by a schematic production process formulated in BPMN. The planning device 6 communicates with one or more databases 7 and with the

Coordination Level 2 below. The communication paths and directions are indicated by single or double arrows.

In the coordination level 2, a coordination device 8 is provided for the control and monitoring of production modules, which can be combined into groups or lines. At this level, a user has the

Manufacturing modules via a user interface 9 (HMI) the ability to intervene in the running processes and modify them if necessary. The coordination level 2 is followed by the execution level 3, to which manufacturing modules 10 are logically assigned. The production modules 10

communicate via programmable logic controllers (PLC) 1 1 and in it

implemented functions 12 of the programmable controller, so-called. PLC functions, with at least one processing component 13 of the respective

Production module 10.

According to the invention, beyond the above architecture, a data connection 14 to higher level databases is provided. Via this data connection 14, parameters of the workpieces in the processing components 13 as well as parameters of the processing components 13 themselves are reported to higher instances, so that so-called "one-piece flow" processing of individual workpieces becomes possible.

In particular, the data link 14 comprises a Robotics Service Bus (RSB). The RS bus is an event-driven middleware system. The RS-Bus protocol provides for the transmission of data packets (events) in a predefined format. The data packets contain user data (payload) whose format can be freely specified by the user. Furthermore, an identification (ID) is given for each data packet, so that each data packet in the sense of a later

Tracking is easy to find. To every data packet will be

Additional information (metadata) is provided, which is an identification of the

Senders and include various times such as the conditions at occurrence of an event and user-specific information. Details of the triggers of the event (trigger vector) are also transmitted. Finally, an addressee is specified for whom the

Notification about the event is determined.

When transmitting the data packets (notification), the specification of the

Addressees in particular required if no dedicated point-to-point connection is made, but the data connection 14 is a logical bus that includes multiple layers. In such a case, several hang

Manufacturing module 10 as a transmitter on the bus 14. There may also be several

Databases 7 may be connected as a receiver to the bus 14, so that a (m: n) system with m manufacturing modules 10 (transmitters) and n databases 7

(Receivers) results. To establish the data connection 14 as a logical bus It must be ensured that they are compatible with different

Transport mechanisms is. Furthermore, different serialization types have to be executable. These requirements are preferably implemented by a "connector" concept in which each participant on the bus uses one or more "connectors" as an interface.

So that not every database receives 7 of all manufacturing modules 10 messages that u. U. are irrelevant from the outset for this database, preferably a pre-selection (observation) is made on both sides. Thus, 10 so-called "listener" modules are set up on the part of the production modules, which query certain, not necessarily all parameters of the production module 10. In these listener modules, each database 7 can register as the parameters monitored by the respective listener module The parameters of a specific listener module can then be used to filter out the particularly important parameters from other filters on the database 7. This results in a multi-level preselection system.

More specifically, execution level 3 includes invariant abstractions of

Manufacturing modules, i. Structured Programmable Controller (PLC) structures for implementing real-time basis functions, horizontal and vertical integration components, robot control, module monitoring and integration into the execution context of the production line. In addition, the contains

Execution level 3 Implementations of the basic functions for the specific process components, which are implemented in particular in the languages supported by IEC 61 131-3. These are, for example, screw or

Separation components in a (not shown) screw module. These

Basic functions are implemented independently and preferably without assumptions about their execution context, thus providing simple, often reusable basic elements. Uniform interfaces, which can be realized with the means of horizontal integration, can be used to "export" the basic functions to the module-specific control process executed outside the actual programmable logic controller, but on the PC-based control hardware.These unified interfaces form a module bus, via The production modules are connected to one another, ie horizontally, and the module-specific control process acts as an abstraction component, which also the integration of non-PLC components such as an RFID reader in the modular architecture allowed. In addition, the module-specific realizes

Control process the link between cyclic control in the PLC-based module control and event-based process control in the coordination level 2.

The coordination level 2 contains cross-module abstractions and

Software components that are needed in the execution context of the AssemblyLine but do not need to meet real-time requirements. Examples of this are the central man-machine interface 9 and components for

Cross-module coordination and execution of manufacturing processes as well as monitoring. The latter two functions are realized in a (not shown) coordination execution interface, with the

communicates with various modules in the execution level and passes these appropriate sub-processes to execution.

Planning level 1 includes components for connecting the production line to the business IT of the company, in particular existing ERP or MES systems. This connection not only allows the communication of the system statuses in the ERP / MES level, but also the transfer of production orders from the planning level via OPC UA to the planning device 6.

On the basis of the production sequence stored in the planning device 6, a control-independent description of the configuration and parameterization of the production line is achieved. As a consequence of this approach to flexible

Configuration became a part of the coordination level

Planning co-ordination interface developed, which interprets the production sequence and each relevant to a module shares the process models to the

Handover manufacturing modules for execution. The planning coordination interface is an integrated subcomponent that passes on the subprocesses or activities belonging to a specific module to the "appropriate" module by calling it via a horizontal integration middleware, using script or service task routines in a coordination execution interface which corresponds to the basic functions currently implemented at the execution level, so a complete process component of a module will be in this concept not only delivered with your PLC code, but also with the appropriate routine for the interface.

For the execution of one described in the production sequence

Manufacturing process is first a process model via OPC-UA to the

Pass interface. This process is "installed" in the interface and is available from this point in time, whereby it should be noted that the interface can execute several processes in parallel, in particular such a process is controlled by the RFID readers present in the modules As soon as a process is able to process this event, the further activities are processed in the logical process of the production process, and as soon as a process is completed, it is marked accordingly and entered into the

Transfer process database for later queries.

Through the user interface 9, the user can e.g. to remedy a

Problems or to configure the hardware. In this case, as part of the interface, the corresponding user roles and authorization concepts can also be implemented at the line level and directly in the production schedule, which are then correspondingly translated into calls to the user interface 9.

In Fig. 2 is an example of the implementation of a production sequence in one

Control sequence for manufacturing modules shown by the planning coordination interface.

First, the production process in the planning device 6 is broken down into event trajectories 15 and at least one output trajectory 16 for the output of events via the user interface 9. In each of the event lanes 15, calls 17 of activities are summarized, the same manufacturing modules or the same

Concern production module groups. By way of example, the calls 17 in the second lowest lane may relate to 15 screwing operations and the calls 17 in the second upper lane 15 may relate to embossing operations. In addition, are

Control bodies provided, e.g. for quality assurance in the top 15. When these calls are each an inspection of the previous

Result of the work. The calls 17 are each initiated by a corresponding event display 18. In the case of incomplete or incorrect steps, these are via the user interface 9

output, which is represented by a plurality of events 16 in the lowermost track 15.

FIG. 3 shows an example of the formulation of a processing sequence for the processing component of a production module as a function of the control sequence described above. At step 19, a new product enters the manufacturing module considered here. This is followed in step 20 by the identification of the product and in step 21 by the assignment or verification of the product type and of the individual identification. Based on this identification of the product and assignment of the product type, an individual and product-specific machining process is called in step 22. Should it be at the

Identification of the product and the allocation of product type have come to an error and this are detected in the processing process, in step 23, the transition to a standard process and in step 24 a

Corresponding error output via the user interface 9. However, if the identification and assignment of the product and product type has been carried out correctly, the product is transferred to the processing component in step 25 and processed there. The processing ends in step 26 with the completion of the processing and the transfer of the intermediate product to the next instance.

This concept of formulating a processing sequence for the

Processing component can be as follows in the inventive

Classify the entire system. In the coordination level is in each case for a

individual product creates and starts a new instance of a process model. The connection between the process instance and the product, ie the generation and

Specific parameterization of a process existing as a model takes place in the planning coordination interface, for example, at a special

Entry point into a manufacturing module (group) or production line in step 19 in Fig. 3. The process instance created here, e.g. one embodiment of the process model shown in FIG. 2 accompanies each product throughout its life cycle in the coordination plane. This property later allows a simple

Traceability of the production processes carried out in the here

desired flexible production environment. So are production errors noted directly in the process variables or can be annotated by the involvement of the operator via inquiries to the user interface 9 and possibly corrected.

The concept for creating separately active process instances for the products in each production plant allows the production of different products in one production line. Due to the specific process instances, all reproducible variants of products can be manufactured in a physically configured plant and thus a kind of "one-piece flow" can be achieved. "Imageable" means in this case that both the hardware in the modules must be correspondingly flexible Also, the necessary production functions must have parameterizable implementation in the execution level, which must be accessible from BPMN activities out. Another requirement is that only one product in a module may be actively processed at a time and after the product has been identified at the time of entry into a new one

Production module, the order must not be reversed. Given these requirements, several different products and process instances can be produced in one modular production line at a time.

The following are examples of these modularly described process parts at the coordination level:

• Interactions with users of the machine are described for more complex situations through separate process models, as explained above by error handling.

• In situations where there is no process model for an identified product, the unknown product can either be started user interaction or a standard process can be modeled, such as sending an error signal to the planning level, e-mailing to a responsible person, or evacuating of the product from the plant without further processing steps.

• The actual module-specific functions ("embossing", "screws", "checking") are described as separate processes for different product types. • The organization of the material flow in the plant does not appear in the module-specific processes, as it is "orthogonal" to the actual functions in a module.

• Logic and user interactions are provided to run in the

Configuration mode via the user interface to convert an incomplete into an executable production plan.

In the processes cited as an example, modeling via workflows allows the asynchronous interaction of the coordination and execution with the planning level and the processes defined there. Thus, e.g. Exceptions at the production level or delays arising here are transferred directly in messages that are handled at the planning level.

4 shows an activity diagram for the examples explained above, which describes the core of the processing and the division of stored production processes on the coordination level and the execution level.

At the start of manufacturing management, an (intermediate) product reaches a manufacturing module in step 27. This is acknowledged in Fig. 28 by sending a message containing the identification of the product to the coordinator. The actual processing in the production module line takes place in step 29 and includes in 30 the processing of the working section. The working section is completed in 31, the processing history is in 32 in a database

stored. Of course, this only applies if the final product has already been completed. If that is not the case, it will be processed in the

Production module line in step 33, the subsequent manufacturing module set and called in step 34, a new machining section. This is communicated in 35 a subsequent sub-process in the coordination device. Thus, the left column in Fig. 4 is completed.

In the coordinator, the steps listed in Fig. 4 in the middle column are carried out. In Figure 36, the coordinator and a PLC bridge are activated, in Figure 37 the product enters a manufacturing module. This is acknowledged in 38 with a message to the appropriate sub-process in the scheduler. The process started in the left column goes to Step 34, 35 with step 39 continued in a sub-process in the

Coordination device that is geared towards an individual product. This is followed in 40 by the processing in a production module. The actual processing takes place in 41 and is eventually completed in 42. The

Processing history is stored again in a database in 43 and the processing status is reported to the higher level (left column). This only applies in the event that the processing result produces the final product. Otherwise, i. in an intermediate, the actual processing in Fig. 41 is followed by a call of PLC functions in Fig. 44. This is associated with the setting of parameters of the PLC functions in Fig. 45. In step 46, the PLC functions are then started simultaneously with 47 in Start flag is set to the PLC function. In step 48, the PLC function is then completed and thus in step 49, the manufacturing module section, which is reported in step 50 as a report on the process status. Thus, this level and thus the middle column in Fig. 4 is completed.

At the lowest level, the execution level, the PLC routines are activated and registered in step 51. This is followed by the reading of PLC functions and flags in step 52 and, in step 53, the actual processing of PLC parameters and flags. 54, the PLC function parameters are evaluated and executed in 55. Finally, in Fig. 56, the PLC functions are completed, and thus the processes are at the lowest level, i. in the right column of Fig. 4, completed.

The work of the interfaces discussed above using examples can be summarized and ranked as follows.

Process plans (workflows), which are processed by the coordination level, embed themselves (dynamically) as product-specific sub-workflows in the

non-product specific business process workflows at the planning level. Function blocks of the business workflow, which refer to the execution of the production, are determined at runtime and depending on the product to be manufactured and interpreted by the coordination or execution level. It is therefore a multi-layered interface, which has three levels

(Planning level, coordination level, execution level) using a standard workflow notation language (eg BPMN) and interpreting them on a level-by-level basis.

A process plan for complete production of a specific product type may be at the planning level in a manner similar to that commonly used today

modeled logics of business processes, for example in the form of a BPMN2-based workflow. As a result, it can be treated at the planning level with the tools customary there, which in the long-term allows an integrated representation of the necessary activities for the production of an individual product from order entry to logistics. For the purpose of modularization and

Hierarchization, the detailed process plans for production in the modular production environment must be stored as sub-processes in their own process plans. These are made available to the coordination level as independent typed process models. If complete (in the sense of "executable") process models for the necessary product-specific production steps can not be used here, these production-related process models may also be underspecified and contain, for example, manufacturing activities without complete parameterization Process plans at the planning level can either be realized by means of appropriate start and termination signals or by direct call of subprocesses.The signals are preferably modeled, since this enables a more flexible execution on the production level is, finds the instantiation as well

Interpretation of these processes autonomously and ideally product-controlled in the coordination level instead.

From a technical point of view, the architecture does not necessarily have to have three levels with appropriate facilities. From a logical point of view, however, a hierarchical process modeling is carried out, which within a

comprehensive process plan contains conceptual activities for all three levels.

The instructions of the planning level must at least include the communication and transformation of order-specific information of the ERP system, communication with the workflow database and selection of the product-specific Include sub-workflows from the database. In addition, there are also instructions for sending the sub-plan to the coordination level and for receiving termination signals after successful completion or faulty termination

Completion from the coordination level required.

From the point of view of the coordination level, the production-related process models must contain information about the type of product to be manufactured as well as the production modules to be used for this product in the sense of a minimal line specification (in the simplest case currently about the specification of so-called "lanes" for the involved production modules). In particular, the applicability of the production-related process models to a list of EPC (Electronic Product Codes) IDs that are read in the execution level via RFID can be limited, in which case this information is transferred to the coordination level together with the type-specific process models. In addition to this information, the data of the sending process instance is embedded here, in order to facilitate the assignment of signals of the called processes on the coordination level with the abstractions for receiving signals contained in the higher level workflow The overall architecture features an update of

This function is of particular interest in cases where an incomplete production-related process plan is referenced at the planning level, which has been completed in the coordination level, and then this product type-specific knowledge can be used recourse to another production of the same product.

The instructions of the coordination level comprise at least the receipt of the sub-workflow of the planning level, the transmission of the termination signal to the planning level and the product-specific calls of the PLC basic functionalities (according to sub-workflows) which are required for the manufacturing process. Furthermore, there are instructions for the distribution of the manufacturing process to the modules of the execution level as well as for bidirectional communication with the

Execution level (submission of sub-workflows / receipt of

Termination signals) required. The production-related process is loaded in the coordination level from the set of processes available in a database, parameterized product-specifically and executed as a separate process instance by the controlling component on the line level and its embedded interface.

At the planning level, a business workflow engine is required that can interpret business processes of the business workflow. Furthermore, an "Enterprise Service Bus" (ESB) is used, which serves as interface and

In addition, a workflow database is provided which provides the product-specific sub-workflows, as follows:

1 . The product-unspecific business workflow is interpreted by the business workflow engine and expects a production order through the ERP system.

2. After the order has been completed, information from the ERP system is transformed by the ESB and ensures business process-specific enrichment of the business workflow, which contains information on the finished product.

3. The product-specific sub-workflow is selected from a workflow database and embedded in the business workflow. This sub-workflow specifies the function block for executing the production.

4. For the processing of the production process function block, the sub-workflow is sent to the coordination level where it is processed further.

Alternatively, the production-related workflows can be modularized, and the actual process plans of the planning level only refer to them or trigger by signal the deployment of the corresponding production-related process plans.

The coordination level contains one coordinating component for each production line. This component can, for example, retrieve product type-specific process plans from a database and execute them with an embedded interface in the context of the system architecture of the modular production line. The production-related process plans at the coordination level, in turn, primarily contain a sequence of sub-processes, which are executed under event control, as well as the assignment of the sub-processes to the production modules of the plant. In addition, other activities such as interactions with the Machine operators or setters as well as further intermediate steps complete the process plan.

The invention is not limited to the embodiments described in detail above. Various modifications can be made. One

However, the essential element is the data connection 14 between the production module 10 and the coordination device 8 for transmitting parameters of the

Input product, the intermediate product or the production module to the coordination device. The data as well as script and service task routines are stored in the routine database 7. On these and more

Databases have the coordinator 8 and / or the

Scheduler 6 via the enterprise service bus access.

reference numeral

1 planning level

2 coordination level

3 execution level

4 resource planning ERP

5 execution routines MES

6 Planning device with production process formulated in BPMN

7 database (s)

8 coordination facility

9 user interface

10 production module

1 1 programmable controller, PLC

12 programmable controller functions, PLC function

13 processing component

14 Data connection to databases at higher levels

15 event classes or courses

1 6 Output via user interface

17 activity call

18 Event Viewer

19 Entry of a new product in production module

20 Identification of product

21 Assignment of product type and individual identification

22 Call for product-specific machining process

23 Transition to standard process with error message

24 Error output via user interface

25 Transfer to processing component

26 Completion of processing, transfer of intermediate product to next instance

27 Start of planning and entry of product into production module

28 Sending Message with Identification to Coordination Facility

29 Editing in production module line

30 Editing Work Item

31 Completion of working phase

32 storing processing history in database Specify subsequent manufacturing module

Call of processing section

Communication to sub-process in coordination facility

Activation of the coordination device and PLC bridge

Entry of product into production module

Notification to sub-process in planning facility

Sub-process in coordination device for individual product Processing in production module

Edit work item

Completion of working section

Save processing history in database

Call of PLC function

Setting parameters of the PLC function

Start the PLC function

Set a start flag to PLC function

Completion of PLC function

Completion of manufacturing module section

Report of process status

Activation of PLC routines and registration of PLC functions Import of PLC functions and flags

Editing PLC parameters and flags

Evaluate PLC function parameters

Execute PLC function

PLC function completed

Claims

claims

1 . Manufacturing management system for the automated production of product lots with a large number of end products,

wherein the manufacturing management system comprises:

at least one production module (10) having at least one processing component (13) for producing an intermediate product from at least one

Input product,

a planning device (6) for storing a predetermined

Production sequence,

a coordination device (8) having at least one database (7) for controlling the at least one production module,

a scheduling coordination interface for generating at least one

Control sequence for each production module depending on the given production sequence,

a coordination execution interface for generating a

Processing sequence for each processing component depending on the control sequence,

marked by

a logical bus (14) between at least one manufacturing module (10) and the at least one database (7) for transmitting data packets,

wherein the data packets at least comprise: parameters of the at least one input product and / or the intermediate product and / or the

Manufacturing module (10) as user data and an identification of the respective

Manufacturing module (10) and the respective database (7), and wherein

each manufacturing module (10) at least one listener module for polling

predetermined parameter and for sending to registered with the Listener module databases (7).

2. Production management system according to claim 1 with a routine database (7) for storing script and service task routines, wherein the

Coordination execution interface when generating the processing sequence assigns at least one routine of at least one real-time capable basic function to a processing component.

3. A manufacturing management system according to claim 2, wherein the real-time capable basic functions of one or more PLC routines correspond to a processing component.

4. Production management system according to one of the preceding claims with an enterprise service bus, via which the planning coordination interface with a business IT, an ERP system and / or an MES system is connected.

A manufacturing management system according to any one of the preceding claims, wherein the data connection comprises a Robotics service bus.

6. Production management system according to one of the preceding claims with a module bus, via which the production modules are interconnected.

7. Production management system according to one of the preceding claims, wherein the at least one production module (10) comprises a parameter database for storing the parameters of the at least one input product and / or the intermediate product and / or the manufacturing module via the Robotics service bus.

8. A production management system according to claim 7, wherein the

Coordination device (8) and / or the planning device (6) via the

Enterprise service bus has access to the parameter database.

9. A method for the automated production of product lots with a multiplicity of end products by producing intermediate products from in each case at least one input product by at least one production module (10) having at least one processing component (13),

the method comprising the steps of:

Storing a predetermined production sequence in a planning device (6), Controlling the at least one production module by a

Coordination device (8) with at least one database (7),

Generate at least one control sequence for each manufacturing module in

Dependence on the given production sequence by a

Planning coordination interface,

Generating a processing sequence for each processing component in

Dependence on the control sequence by a

Coordination execution interface and

Transmission of data packets via a logical bus (14) between at least one production module (10) and the at least one database (7),

wherein the data packets at least comprise: parameters of the at least one

Input product and / or the intermediate product and / or the

Manufacturing module (10) as user data and an identification of the respective

Manufacturing module (10) and the respective database (7), and

Querying and sending to a database (7) predetermined parameters by at least one listener module of the respective manufacturing module (10), which is registered in the at least one listener module of the respective manufacturing module (10).

10. The method of claim 9, wherein the production sequence as a

Instruction set is stored and the scheduling coordination interface divides the instructions of the production sequence into user interface (HMI) instructions (16), activity instructions (17), inspection instructions (17).

1 1. A method according to claim 9 or 10, wherein the

Coordination execution interface assigns each activity instruction (17) to at least one manufacturing module (10) for performing a manufacturing step, each user interface (HMI) instruction (16) of at least one

Assigns user interface (9) for adjusting the manufacturing steps by a user, each inspection instruction assigns at least one inspection unit for detecting actual parameters and comparisons with target parameters.

12. The method of claim 10, wherein the coordination execution interface for generating a machine-specific processing sequence assigns a script or a service task routine in a routine database to a real-time capable basic function of a processing component.

13. The method of claim 12, wherein the script or service task routines are stored as HyperCard or JavaScript routines.

14. The method of claim 12 or 13, wherein the script or service task routines are stored as plug-in routines.

15. The method according to any one of claims 9 to 14, wherein the

Planning coordination interface via an enterprise service bus with a business IT, an ERP system and / or an MES system communicates.

1 6. The method according to any one of claims 9 to 15, wherein the

Coordination execution interface communicates with the manufacturing modules via a Robotics service bus.

17. The method according to any one of claims 9 to 1 6, wherein the manufacturing modules are connected to each other via a module bus.

18. The method according to any one of claims 9 to 17 with the further step:

Storing the parameters of the at least one input product and / or the intermediate product and / or the production module in a parameter database of the at least one production module via the Robotics service bus.

19. The method of claim 18, wherein the coordination device and / or the planning device via the enterprise service bus access to the

Parameter database has.