WO2023104300A1 - Outil de communication pour un système de développement et système de production pour échanger des messages standardisés - Google Patents

Outil de communication pour un système de développement et système de production pour échanger des messages standardisés Download PDF

Info

Publication number
WO2023104300A1
WO2023104300A1 PCT/EP2021/084772 EP2021084772W WO2023104300A1 WO 2023104300 A1 WO2023104300 A1 WO 2023104300A1 EP 2021084772 W EP2021084772 W EP 2021084772W WO 2023104300 A1 WO2023104300 A1 WO 2023104300A1
Authority
WO
WIPO (PCT)
Prior art keywords
production
development
tool
message
intermediary
Prior art date
Application number
PCT/EP2021/084772
Other languages
German (de)
English (en)
Inventor
Ralf Riemensperger
Jacob DECKER
Original Assignee
Festo Se & Co. Kg
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Festo Se & Co. Kg filed Critical Festo Se & Co. Kg
Priority to PCT/EP2021/084772 priority Critical patent/WO2023104300A1/fr
Publication of WO2023104300A1 publication Critical patent/WO2023104300A1/fr

Links

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/418—Total factory control, i.e. centrally controlling a plurality of machines, e.g. direct or distributed numerical control [DNC], flexible manufacturing systems [FMS], integrated manufacturing systems [IMS] or computer integrated manufacturing [CIM]
    • G05B19/4185—Total factory control, i.e. centrally controlling a plurality of machines, e.g. direct or distributed numerical control [DNC], flexible manufacturing systems [FMS], integrated manufacturing systems [IMS] or computer integrated manufacturing [CIM] characterised by the network communication
    • G05B19/4186—Total factory control, i.e. centrally controlling a plurality of machines, e.g. direct or distributed numerical control [DNC], flexible manufacturing systems [FMS], integrated manufacturing systems [IMS] or computer integrated manufacturing [CIM] characterised by the network communication by protocol, e.g. MAP, TOP
    • 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/31—From computer integrated manufacturing till monitoring
    • G05B2219/31367—MMS manufacturing message specification, rs511, iso9506
    • 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/31—From computer integrated manufacturing till monitoring
    • G05B2219/31395—Process management, specification, process and production data, middle level
    • 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/32—Operator till task planning
    • G05B2219/32099—CAPP computer aided machining and process planning

Definitions

  • the present invention relates to the exchange of data between a construction or planning system for the development of technical products, in particular products for use in an automation system, and a separate production system for the production of the products.
  • Construction/development/planning phase in which, for example, a CAD system, computer-aided design can be used
  • production phase in which the developed/designed technical product or production system is manufactured.
  • the production process is usually also supported by software tools. Since the development-side domain and the production-side domain are separate from each other, data exchange between the two domains has so far not been possible at all or only to a very limited extent.
  • the interaction and communication between development and production should be improved.
  • the manufacturing costs are to be reduced and the quality of the production is to be increased.
  • the time until the finished production of the workpiece or product to be produced is to be shortened.
  • the invention relates to a computer-implemented system for exchanging electronic messages between an electronic development tool (e.g. a CAD design/design/planning software tool) and a (usually separate) electronic production tool.
  • the system includes an intermediary (as a computer-based switching node with hardware and software) that communicates with the development tool and the production tool via a network (e.g. LAN, WLAN or other radio-based networks or wired networks).
  • the system and in particular the intermediary comprises: a development request interface, in particular to the development tool, a production request interface, in particular to the production tool, a production response interface, in particular to the production tool and an analysis message interface, in particular to the development tool.
  • the intermediary is used for standardized data exchange between the development tool and the production tool and is designed to receive a development request message via the development request interface and to convert or transform it into a production request message using a transformation algorithm in order to send the production request message to the production tool via the production request interface.
  • the intermediary is also trained to Production response interface to receive a production response message from the production tool and to generate an analysis message from it using an analysis algorithm and to send this analysis message to the development tool via the analysis message interface.
  • the development request interface and the analysis message interface can be integrated into a common interface. The same applies to the production request interface and the production response interface; these can also be combined or integrated in a common physical interface.
  • a production response message can be generated on the production tool from a production request message by extracting the requested information directly from a file stored in the production tool.
  • the requested information can be calculated from parameters of a system that is operated and/or managed with the production tool. For example, from a file that can be designed according to the specifications of the administration shell of the Industry 4.0 platform, solution spaces can be calculated according to an algorithm, which result from the capabilities (skills) of the respective machine and the requirements determined in the production request message be matched.
  • the production request message asks whether a product A with the dimensions 100x200x500mm can be labeled in process cell P1.
  • the capabilities of P1 are described in file D1.
  • process cell P1 has a processing area of max. 150x200x300mm.
  • the analysis algorithm compares the solution spaces of the process cell P1 using the information in the file D1 with the requirements of the development tool for the development of product A.
  • the development tool is then informed in the production response message that its product A cannot be manufactured on the process cell P1, since the dimensions in the Z dimension exceed the processing area of the process cell P1 by 200mm.
  • the developer saves a lot of communication and coordination effort and can make adjustments to a product immediately, in a very early phase of the development process, which ultimately have a very positive effect on the manufacturing costs.
  • the system is managed in the production tool. The only difference is that the capabilities are transmitted directly from the system to the production tool via a protocol or that they are entered manually in the production tool.
  • a recipient-based generation of the production response message is also possible, e.g. by a user of the production system making entries on a user interface (e.g. in an input mask).
  • the development request message can be generated on the development tool by executing an export function in order to extract the required data from the IT-based development tool (e.g. a CAD system) and process it into the development request message.
  • the IT-based development tool e.g. a CAD system
  • the individual components can be extracted from the overall CAD, a production/assembly sequence can be formed and/or the data can be structured and/or the respective characteristics can be grouped according to the individual components (dimensions, material, etc.). .
  • the development request message can be generated by providing an input mask on the development tool that requests parameters from which the development request message can be algorithmically synthesized and generated.
  • Important feature categories here are: geometry data, product data, process data, test data and/or machine data.
  • the exchanged messages and in particular the development request message can be provided and exchanged as a so-called STEP file or in a CAD product-specific format.
  • STEP stands for "Standard for the Exchange of Product model data” and the associated file format is ".STP".
  • STEP file it is possible to map the information of a product over its entire life cycle. Both the functional and the physical aspects are covered.
  • the use of the STEP format proves to be particularly advantageous for the description of computer-created 3D models (CAD, computer-aided design).
  • a digital model for the production-side equipment and its Keeping functionalities (skills) available and storing them in memory so that the system and preferably the intermediary can access them.
  • the digital model can preferably be stored directly on the intermediary and offers the possibility of checking the requirements defined on the development side to see whether they can currently (under the current conditions of the production system) also be realized on the production side.
  • clock times, cycle times and/or other time-based parameters as well as assembly (assembly) sizes and/or geometric, machine, product and/or process data, as well as test-specific sizes and their functionalities are included here.
  • the present invention relates to an intermediary for the standardized switching of electronic messages.
  • the intermediary thus serves as a central computer-based switching node between the development tool on the one hand and the production tool on the other.
  • the intermediary includes the development request interface, the production request interface, the production response interface and the analysis message interface to receive the development request message and the production response message (from different sending nodes) and to send the production request message and the analysis message (to different recipient accounts).
  • the exchange of messages that is mediated via the intermediary can be triggered or initiated by the development tool by generating a development request message on the development tool and sending it to the intermediary, who then carries out further data processing and algorithms in order to finally provide a final analysis message with the production-side or intermediary-side response to the development request message and send it back to the development tool as a response.
  • the intermediary can interact with the production tool.
  • a Kl tool can be implemented on the intermediary so that the intermediary can independently provide the necessary answers and analyzes (e.g. with access to historical data).
  • the exchange of messages can also be triggered by the production tool, in which a Production response message is sent from the production tool to the intermediary, which is then adapted to generate an analysis message in response to the received production response message and to transmit the analysis message thus generated to the development tool.
  • the production response message has the character of a status message to represent the current operating status of the production tool, in particular with the available resources and their functionalities, and optionally other production-related parameters, such as clock cycles, failsafety, reliability, security level and / or other production-related Metadata, etc.
  • the following data can be processed, for example: data on capacity utilization (eg OEE), a shift model, a plan assignment, machine cost rates, required employees ("workers”) per system.
  • OEE data on capacity utilization
  • workers required employees
  • Example 1 Based on current data on capacity utilization, the development tool can be used to draw conclusions as to whether a product can be produced in the planned quantity on a specific system or whether investment in a new system is necessary.
  • Example 2 The production tool sends changes in the machine cost rates so that the manufacturing costs can be adjusted in the development tool.
  • Example 3 The production tool provides information on the average utilization (N.O.K. rates/error rates, ...) of the process module to the intermediary. Based on this information, the development tool can draw conclusions about the process reliability and, if necessary, the suitability of a manufacturing technology and, if necessary, decide on alternative manufacturing processes.
  • a predefined event pattern can be stored in order to carry out the exchange of messages between the production tool and the development tool.
  • a time pattern can be stored that defines the point in time at which a corresponding request (for example a development request message) should be sent to the respective complementary system (here: production system).
  • an activity pattern can be stored that defines the situations in which a corresponding request or a data exchange is to be carried out.
  • the activity pattern can be deduced from a set of predefined, captured sensor data (for example after completion of a specific development activity, development phase and/or in the event of changes to the production tool).
  • REST API is to be understood as an application program interface (API) that is designed according to the REST paradigm.
  • API application program interface
  • Each REST message contains all the information that the server or client needs to understand the message. Neither the server nor the application should store state information between two messages.
  • the interface is preferably stateless in each case or is operated with a stateless protocol. HTTP or HTTPS, for example, can be used as application layer protocols.
  • Each request from a client (e.g. development tool and/or production tool) to the server (here in particular: intermediary) is self-contained insofar as it contains all information about the application state that the "server” needs to process the "client” request are required.
  • the messages to be exchanged can be provided and exchanged in a predefined format, which simplifies further processing.
  • the messages can be provided in a JSON format, which has the advantage of an easily readable text form and serves the purpose of data exchange between the applications.
  • the messages can also be formatted in an XML format (XML: Extensible Markup Language) so that they can be read by both humans and fully automated by a machine.
  • XML Extensible Markup Language
  • This embodiment has the technical advantage that the exchanged messages can be displayed on a user interface (for example a monitor) and processed further at the same time or directly (without intermediate processing) in a fully automated manner using appropriate algorithms.
  • the production response message can have at least two components or sections and, in particular, include an equipment section and an equipment functionality section.
  • the resources section refers on or represents the resources that are currently available in the production system and are accordingly marked as available in the production tool.
  • the resource functionality section refers to or represents the functionality of the respective resource.
  • the resource functionality section can include different sub-categories in which additional metadata is represented, such as cycle times, cycle times, execution conditions, environmental conditions, such as temperature, required lubricants and/or other physical variables.
  • additional metadata such as cycle times, cycle times, execution conditions, environmental conditions, such as temperature, required lubricants and/or other physical variables.
  • the transformation algorithm can automatically extract process parameters, which represent process requirements, from the development request message.
  • process requirements is to be understood as the technical or physical requirements that must be met in order to be able to run the process on the production system. Process requirements can therefore relate, for example, to temperature, pressure conditions, voltage and power supply and/or other physical or technical parameters.
  • the analysis algorithm is a computer-based process that generates an analysis message in response to the sensed conditions or state of the production system.
  • the purpose of the analysis message is to inform the development tool (or its user) about the current status of the production system and/or to answer its queries (particularly formalized as a development query message) as precisely and completely as possible.
  • the analysis algorithm can include different modules or functions.
  • geometry and process data can be compared.
  • a geometry requirement be derived from the development tool that requires a specific dimension of the installation space (e.g. values for the X/Y/Z axis must be at least 20/30/40 mm), this can be compared with the currently available production resources.
  • Corresponding alternative proposals for the development tool for the development of products with realizable production requirements can be generated automatically and offered to the user via a user interface.
  • the alternative proposals are usually generated on the intermediary and sent to the development tool for output there (preferably with the analysis message).
  • the training data comprises a set of different development requests (formalized as development request messages) in combination with production side state detections (which can be formalized as production response message, for example) and associated change messages related to the development side.
  • the change message characterizes which development-side changes must be made so that they can be realized and implemented in the current production-side state.
  • the changes on the development side should be designed in such a way that the originally desired development task can still be fulfilled. In other words, the question is answered here as to how the development process can be changed in order to continue to solve the development task on the one hand and to correspond to the production specifications on the other.
  • a suggested change could be: "Increase the number of available lasers [or other subsystems]" or "Design a narrower gutter by 1 mm so that sufficient installation space can be provided”.
  • the analysis algorithm can also include the generation of optimization suggestions.
  • the optimization suggestions can refer to an optimization of the development system or development tool, so that the production-side specifications can be met.
  • the optimization suggestions can also refer to an optimization of the production tool, so that the development-side specifications can be met.
  • an optimization message can be generated here that represents which development-side and/or production-side Changes and optimizations can be made so that the existing production system or development system can be used as optimally as possible. For example, additions to redundant equipment/subsystems to increase output and/or cycle time, a reduction in the variety of C-parts, e.g. different types of screws, in order to make maximum use of the capacity of the existing equipment (this reduces the necessary new -Invest in resources for new products.)
  • the intermediary is used to answer requests from the development side.
  • the implementation can take place according to the challenge-response principle.
  • the development tool sends a request (challenge) to the intermediary and receives a suitable answer (response) from them.
  • the response is preferably based on the responses that the production system has automatically supplied (without input from a user) to the request and/or that the intermediary has calculated on the basis of the production-side responses. This basically presupposes that the intermediary can also generate a production response message to the production request message. However, this is not always possible. There are also situations in which the production system cannot automatically provide satisfactory answers.
  • a forwarding assistant can be provided that "parses" the production request message according to certain criteria in order to automatically find a group of responsible recipients.
  • the parsing of the production request message can include a semantic analysis, in particular with regard to predefined keywords (keywords) based on historical data, a memory structure can then be used in which one or more keywords are assigned one or more responsible recipients. This can be, for example, e-mail addresses, telephone numbers or contact options for people who, based on historical data, can be assumed to be able to answer the question/enquiry. Their responses are then collected and routed back to the intermediary, who can then construct the analytics message in response to the data collected.
  • the intermediary can also use an electronic ticket system.
  • the ticket system is for development request messages of the development tool on the intermediary.
  • the intermediary can try to answer the recorded request from the development tool independently and without forwarding it to the production system. This can be based on historical requests and responses and/or access to an AI-based tool. If it is not possible to answer the question yourself, the query can be forwarded to a ticket system in a second step.
  • the ticket system is used to collect the requests—possibly from several different development tool-side senders—and forward them to the production system and in particular to at least one production tool-side recipient in a coordinated (and/or prioritized) manner.
  • the sender/receiver can be a machine (machine, bot) and/or a user who interacts with the system via a user interface.
  • the analysis algorithm can include an evaluation function.
  • the evaluation function is used to analyze the feasibility of predefined additional requirements that the development tool places on the production tool.
  • a mask to be provided on the development tool through which the developer can enter, for example, industry-specific information on requirements such as accuracy, cleanliness and/or speed, etc.
  • the data provided on this mask is forwarded to the intermediary, who then - and possibly with access to the production tool - evaluates whether the requirements set can be met in the current production system or not.
  • the analysis message can include a corresponding partial result as part of the analysis message as a response. This has the technical advantage that additional development-side requirements for the production system can be analyzed more precisely and specifically.
  • the development request message can include metadata about the workpiece or product to be manufactured.
  • the metadata can, for example, refer to "dependencies".
  • "Relationship knowledge” here means the knowledge about the (technical) connection between the workpiece and the equipment. This includes the following aspects: On which equipment can a specific workpiece be manufactured? How long is the processing time on the respective machine? In which order are the resources clocked? Examples of metadata are all information about the workpiece (CAD data, geometry data, material data, ).
  • an assembly plan can be automatically generated from the analysis message. In this way, the degree of automation of the development/production can advantageously be increased.
  • the assembly plan contains information on the assembly of the workpiece/component to be manufactured.
  • the intermediary creates the assembly plan.
  • the assembly plan contains, for example, throughput times, cycle times, as well as sequence and recipe data.
  • the analysis message can include a selection of production resources (production-side resources) recorded as available for the respective development request (represented in the development request message).
  • production resources production-side resources
  • the analysis message can include a selection of production resources (production-side resources) recorded as available for the respective development request (represented in the development request message).
  • the intermediary can include an input and output interface in order to output all or selected messages and/or to receive control data (e.g. can be entered on a mask of a user interface).
  • the output interface can be used to output the analysis message and/or the associated development request message.
  • the output interface can also be used to output a feasibility result message—specifically and locally generated on the intermediary.
  • the feasibility result message represents whether the requirements on the development side can currently be implemented on the production side.
  • the developer can advantageously be provided with more information about the existing production system very early on, namely still in the development process, so that the developer can possibly make changes in order to be able to develop better adapted to the current production-side resources.
  • the invention relates to a computer-implemented method for exchanging electronic messages between an electronic development tool and an electronic production tool.
  • the method is preferably carried out on an intermediary.
  • the method can include the following steps: optionally: providing a development request message via a
  • development request interface optional: transforming the development request message into a
  • production request message using a transformation algorithm; optional: sending the production request message via a
  • the production response message can firstly be generated autonomously on the intermediary and/or secondly can be generated with access to the production tool by receiving the production response message via a production response interface;
  • Mixed forms are also possible, in which part of the production response message is generated on the intermediary and another part on the production system;
  • Push operation is characterized by the fact that the intermediary becomes active independently according to a predefined scheme (time-based or event happens) and proactively informs the development tool or the developer about the current status of the production system without the developer having to direct specific inquiries to the intermediary .
  • the intermediary can also be operated in pull mode.
  • the three method steps identified above as “optional” must be carried out before the steps of providing or receiving, generating and sending are carried out.
  • Pull operation is characterized by the fact that specific development-side inquiries with regard to the production system are sent to the intermediary, which are then answered. As already mentioned, the inquiries can either be processed and answered directly on the intermediary or can be forwarded to the production system for answering.
  • a further solution to the problem consists in a computer program product that is or can be loaded into a memory of a computer or an electronic device with a computer program for performing the method described in more detail above when the computer program is executed on the computer or the device.
  • a further solution to the problem provides a computer program for carrying out all method steps of the method described in more detail above when the computer program is executed on a computer, an electronic device. It is also possible that the computer program is stored on a medium that can be read by the computer or the electronic device.
  • the development tool is to be understood as a software tool and is used for computer-aided construction and development.
  • it can be designed as a CAD tool. It includes interfaces for data exchange.
  • a user interface for inputting and outputting data can be provided.
  • the development tool can output a parts list for the product to be manufactured (BOM - Bill of Materials or MBOM - manufacturing bill of materials).
  • the production tool is also a software-based tool and is used for computer-aided manufacturing or production. It is designed with appropriate interfaces for data exchange.
  • the production tool can be designed, for example, as a computer-aided manufacturing (CAM tool).
  • the production tool can also be designed with a user interface. In principle, the possibility of an entry must be permitted and provided so that the creation and management of resources and their capabilities is possible. What is important is the interaction with product development.
  • the Production tool can also be understood as a mixture of MES (Manufacturing and Execution System) order planning and administration, detailed planning tool and PLM system.
  • MES Manufacturing and Execution System
  • the development request interface, the production request interface, the production response interface and/or the analysis interface are to be understood as logical and/or physical interfaces. They are used for the interaction of the intermediary with external computer-based instances or software tools.
  • the development request interface and the analysis message interface can be designed as two separate interfaces.
  • the aforementioned development tool-related interfaces can also be integrated into one interface. In particular, they serve to connect the intermediary to the development tool in terms of data technology.
  • the production request interface and the production response interface can also be designed as two separate interfaces. Alternatively, the production-related interfaces can also be integrated into one interface.
  • the production-related interfaces serve in particular to connect the intermediary with the production tool in terms of data technology.
  • the aforementioned interfaces of the processing instances involved form a distributed data processing system and keep algorithms and programs for data processing in memories (e.g. RAM, SRAM, CPU cache memory) and/or in non-volatile memories (e.g. ROM, PROM, EPROM etc.).
  • memories e.g. RAM, SRAM, CPU cache memory
  • non-volatile memories e.g. ROM, PROM, EPROM etc.
  • the volatile memory units can be used to temporarily store program files for executing program elements
  • the non-volatile memory units can include bootstrap code for the respective operating system of the data processing system.
  • the data processing system includes a computer-based processing unit or cluster of computers.
  • the data processing system can comprise at least one processor unit for data processing.
  • the processor unit usually includes a CPU and/or a GPU and a number of software modules that are each set up to carry out the method steps of the present application described above.
  • the processor unit can be set up to execute the transformation algorithm and/or the analysis algorithm.
  • the data processing system can be divided into different computer-based entities and thus part of the functionality according to the invention can be executed on the development tool, another part on the intermediary and another part of the functionality can be executed on the production tool.
  • the computer-based entities are beyond this at least one network (wireless or wired) in data exchange.
  • the data processing system may also include a network controller (NIC).
  • the network can, for example, be in the form of an intranet, the Internet or a mobile radio network.
  • the method executes several algorithms, in particular the transformation algorithm and the analysis algorithm.
  • An algorithm is a collection or a sequence of instructions for processing input data in order to calculate output data by machine.
  • the instructions of an algorithm can be implemented in software and executed on a processor of the data processing system. Alternatively or cumulatively, the commands of the algorithm can also be implemented in hardware on appropriate microprocessor modules (for example FGPA, ASIC).
  • the ticket system is an electronic system for processing data.
  • the term "ticket” is not to be understood here as a physical ticket, but as an electronic, digital and logical ticket.
  • the ticket can be implemented as code or data string, for example.
  • FIG. 1 shows, in a schematic overview, essential components of the data processing system according to a preferred embodiment
  • Fig. 2 is a sequence diagram showing the exchange of data between the entities involved according to a preferred embodiment of the invention
  • FIG. 3 shows an alternative data exchange compared to FIG. 2 between the entities involved according to a further preferred embodiment of the invention
  • FIG. 4 is an exemplary electronic component schematic of an intermediary
  • Figure 5 is a schematic representation of a production response message
  • 6 is a flowchart of a method according to an advantageous
  • the present invention is in the field of automation technology and relates to the standardized exchange of data between development and production via a corresponding digital platform, namely an intermediary.
  • the purpose of the present invention is to inform the developers at an early stage and as early as the development phase about the means of production and equipment available in production and to enable a standardized exchange of relevant information between the systems.
  • the interaction between design and production should be improved.
  • the production process is also to be improved in that means of production and/or production devices no longer have to be adapted and/or changed after development has been completed on the basis of development specifications, but are already taken into account in the development process. This saves time and money.
  • the exchange of data is to be standardized and formalized, in particular by providing certain information and messages as an option.
  • a data exchange according to a variable, preconfigurable scheme between the two systems is "forced". This can significantly improve the efficiency of the entire development and production process.
  • “Varably preconfigurable” means here that in a preparatory configuration phase it can be defined via a user interface from which entity which messages/information are requested. It can be specified here, for example, that a development request message ean is always awaited before the intermediary interacts with the production system or tool PT.
  • the developer should automatically receive the necessary, detailed knowledge about the capabilities/functionalities or skills of the existing resources and processes in the production tool in order to be able to adapt his design to the existing resources and processes.
  • Through better utilization can reduce costs for the procurement of additional equipment.
  • the transparency of the development-side and production-side processes can be improved.
  • the manufacturing costs can be lowered, since in many cases a new acquisition of production-side resources can be eliminated or at least minimized.
  • a further advantage can be seen in the fact that direct production-side feedback on the cycle times in the processes and the associated manufacturing costs can be provided.
  • the intermediary is preferably a cloud-based application.
  • the intermediary can be operated decentrally or centrally.
  • the operation of the intermediary or the execution of the corresponding algorithms can in principle be triggered from different entities.
  • the intermediary can be triggered by the development tool.
  • the intermediary or the algorithms implemented on it can be triggered by the production tool.
  • an execution scheme it is also possible for an execution scheme to be stored on the intermediary, which defines which messages are to be sent to which entity at what point in time.
  • a first execution scheme can be stored, which defines that an exchange between the development tool and the production tool takes place at the end of each working day or according to another time-based scheme.
  • the development tool should be informed about the current resources and conditions of the production tool.
  • FIG. 1 shows an overview of the data processing system with the entities involved, in particular with a development tool ET, an intermediary I and a production tool PT.
  • All three entities mentioned above are computer-based entities and can include software components and/or hardware components and are referred to collectively as a data processing system and interact via a network NW, which can be embodied as a WLAN, LAN or other radio network or digital network.
  • the development tool ET and the production tool PT include at least one processor P, a monitor M and a memory S.
  • the intermediary I includes at least one processor, which is also identified by the reference symbol P in the figures. All three computer-based instances are in data exchange via a network (wireless or wired).
  • the development tool ET can send a development request message ean to the intermediary I via a development request interface EAS.
  • the intermediary I applies a transformation algorithm TA to the received development request message ean in order to generate a production request message pafn and to send this to the production tool PT via a production request interface PANFS.
  • the production tool PT develops a production response message patn in response to the received production request message pafn and sends it to the intermediary I via a production response interface PANTS.
  • the intermediary I then applies an analysis algorithm AA to the received production response message patn in order to generate a response message and via a Return analysis interface ANS to the development tool ET.
  • the messages generated on the intermediary I can also be output via a user interface (not shown).
  • the messages generated can be transmitted to the development tool ET and/or to the production tool PT in order to be able to be displayed on the local monitors M there if the intermediary I is designed as a cloud-based application.
  • the intermediary I can also be designed as a server and directly include a user interface for inputting and outputting data.
  • the data exchange between the entities involved is shown in more detail in the form of a sequence diagram according to one embodiment.
  • the switching platform or the data exchange between the development tool ET and the production tool PT is triggered by the development tool ET.
  • An export function EF can be applied to the development tool ET in order to generate a development request message ean from a design data record of a design tool, for example a CAD tool.
  • the development request message ean is then sent to the intermediary I.
  • the intermediary I applies the transformation algorithm TA to generate the production request message pafn and send it to the production tool PT.
  • the production tool PT determines a production response message patn and transmits it to the intermediary I.
  • the intermediary I it is also possible to equip the intermediary I with additional intelligence, for example by installing intelligent algorithms, so that the intermediary I independently can generate a production response message patn from the production request message pafn without having to go to the production tool to do so PT needs access.
  • the analysis algorithm AA can use it to calculate an analysis message an in order to send it back to the development tool ET.
  • an output function AFE can be executed there in order to output the analysis message on a monitor M, for example. It is also possible to implement an output function on the intermediary I, which triggers an output on a set of determinable devices.
  • the analysis message can be transmitted to or at least a part of it also to a production-side output function AFP for display on an output unit to the production tool PT.
  • a production-side output function AFP for display on an output unit to the production tool PT.
  • an evaluation function can be implemented and executed.
  • the evaluation function (not shown separately in the figures) is used to evaluate whether predefined additional requirements for the production tool can be met, including e.g. time or other process requirements, qualitative requirements.
  • the evaluation function can be based on recorded metadata.
  • the evaluation function can also include a feasibility function to represent whether the requirements or the status (resources, status, circumstances) of the two systems ET, PT can be brought into agreement.
  • an assembly plan algorithm MPA can be executed, which automatically generates an assembly plan on the basis of the received analysis message.
  • the assembly plan can either be conveyed via the intermediary (indirectly) or transmitted directly to the production tool PT.
  • a further functionality can be implemented on the development tool, namely a geometry and process function GP for comparing geometry and process data between the development tool ET and the production tool PT.
  • the following data records in particular can be taken into account and offset here:
  • Equipment data such as manufacturer information and/or data on the year of manufacture, type designation, existing tools, etc.
  • Product data/properties such as data on housing type, material and/or weight, etc.
  • Geometry data such as data on dimensions (in all three spatial axes), diameter, symmetry and/or screw head shape, etc.
  • Process data and features such as data on holding current reduction, press-in force, mounting depth, type of labeling, pressure, etc.
  • Test data such as test holding current reduction, test medium, test voltage, test pressure, test current, etc.
  • Environmental data such as outside temperature, air pressure, humidity, vacuum etc.
  • Qualification data such as a certification, training data that represent whether the employees are sufficiently qualified and whether, for example, a predefined training course has taken place, etc.
  • FIG. 3 shows an alternative embodiment of the data exchange compared to FIG.
  • the data exchange is initiated by the intermediary I.
  • the development tool ET and/or the production tool PT first have to register with the intermediary I in order to participate in the data exchange.
  • Authorization data and authentication procedures can be carried out here in order to increase the security of the data exchange.
  • a data record init E is sent from the development tool ET to the intermediary I and/or a data record initp is sent from the production tool PT to the intermediary I. Since this is optional, these data transfers are shown in dotted lines in FIG.
  • the authentication procedure can, for example, be password-based or carried out according to a symmetric or asymmetric cryptographic method and/or according to a biometric method (intended for authenticated users of the tools ET; PT).
  • a modified transformation algorithm TA′ can be executed on the intermediary I, which generates a standardized, preconfigured production request message pafn without having received a development request message.
  • the modified transformation algorithm TA′ has a simpler design than the transformation algorithm TA and can, for example, request specific, preconfigured parameters from the production tool PT according to a time schedule.
  • the modified transformation algorithm TA' differs from the actual transformation algorithm TA in particular in that no development request message ean is necessary for its execution. The analysis message an can thus be provided autonomously.
  • the intermediary I thus acts as a self-sufficient node in the network NW.
  • the corresponding production response message patn is then converted back into an analysis message an via the analysis algorithm AA and sent to the development tool ET. Additional measures can also be initiated there, as have already been described, for example, in connection with FIG.
  • FIG. 4 shows schematically that the computer-based intermediary I, which serves as a switching node between the development tool ET and the production tool tool PT, includes at least one processor P.
  • the processor P is designed to execute the transformation algorithm TA or the modified transformation algorithm TA' and the analysis algorithm AA. If required, further software modules with further functionalities can be provided.
  • at least one memory S can be provided in order to store the intermediate results and outcomes. This proves to be particularly useful if an artificial intelligence algorithm is to be used to carry out further data processing.
  • Further data processing can relate, for example, to automatically generating suggested changes for the ET development tool if the requirements of the designer/developer cannot currently be met with the production means of the production system and it therefore makes sense to develop a modified workpiece or product, so that no further changes need to be made to the production system.
  • an artificial neural network ANN
  • the ANN may have been trained using stored training data.
  • the training data includes data that represents an advantageous or correct assignment of development request messages ean and production response messages patn or analysis messages an.
  • the ANN can be designed in particular as a deep neural network (DNN), as a convolutional network (CNN) or as a network with a different topology.
  • DNN deep neural network
  • CNN convolutional network
  • Other machine learning methods can also be used, such as a decision tree, random forest method, a support vector machine (SVM) or similar method.
  • SVM support vector machine
  • the aim of these approaches is to send a production response message and/or an analysis message based on the information available generate. For this purpose, historical data and/or training data can be evaluated.
  • a digital model DM of the production tool PT can be stored on the intermediary I in order to be able to perform automatic calculations for the analysis message.
  • the production response message patn has a pre-configured, specific structure. This is shown in FIG.
  • the production reply message patn can comprise at least two different sections, namely a resource section bma and a resource functionality section bmfa.
  • the resources section bma identifies the resources/production resources currently available in the production system PT. These are, for example, valves, switches, current/voltage supply modules, etc.
  • the resource functionality section bmfa identifies the functions that can currently be executed in the production system PT. Since the functionality usually depends on the respective operating and production resources, the operating resource functionality section bmfa can also be calculated from the operating resource section bma. For example, the functions can be "downloaded" via manufacturer-specific or manufacturer-neutral function databases via serial numbers or data matrix codes on the equipment.
  • FIG. 6 shows a flow chart of a method according to a first embodiment of the invention.
  • the procedure with all its steps is carried out on Intermediary I.
  • the production response message patn is received by the production tool PT in step S4. This is done via the PANTS production response interface.
  • the analysis message an is generated in step S5.
  • the generated analysis message is sent to the development tool ET via the analysis interface ANS.
  • the procedure can then end or be repeated according to a preconfigured scheme (time or event based).
  • the production response message patn which is used to trigger the data exchange between development tool ET and production tool PT, can be requested by intermediary I, preferably in a separate request message that is sent by intermediary I to production tool PT (Not shown).
  • the production response message patn (independently) can be made available to the intermediary I automatically and without request by the production tool PT according to a preconfigurable scheme.
  • the cloud-based mediation platform for data exchange between the development tool ET and the production tool PT is triggered here by the intermediary I or the production tool PT.
  • FIG. 7 shows a flow chart of a method according to a second embodiment of the invention.
  • the procedure with all its steps is carried out on Intermediary I.
  • the development request message ean is provided in step S1 by the development tool ET via the development request interface EAS.
  • the received development request message ean is transformed into the production request message pafn using the transformation algorithm TA.
  • the production request message pafn generated in this way can then be transmitted in step S3 to the production tool PT for further processing (steps S4 to S6).
  • steps S1 to S3 are also carried out in FIG.
  • the cloud-based switching platform is triggered by the development tool ET.

Landscapes

  • Engineering & Computer Science (AREA)
  • General Engineering & Computer Science (AREA)
  • Manufacturing & Machinery (AREA)
  • Quality & Reliability (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Automation & Control Theory (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)
  • General Factory Administration (AREA)

Abstract

L'invention concerne un système et un procédé d'échange de messages électroniques entre un outil de développement électronique (ET) et un outil de production électronique (PT), avec un intermédiaire (I) qui échange des données avec l'outil de développement (ET) et l'outil de production (PT) par l'intermédiaire d'un réseau et comprend à cet effet une interface de demande de développement (EAS), une interface de demande de production (PANFS), une interface de réponse de production (PANTS) et une interface de message d'analyse (ANS). L'intermédiaire (I) est conçu pour échanger des données de manière standardisée et pour calculer un message d'analyse (an) au moyen d'un algorithme d'analyse (AA).
PCT/EP2021/084772 2021-12-08 2021-12-08 Outil de communication pour un système de développement et système de production pour échanger des messages standardisés WO2023104300A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/EP2021/084772 WO2023104300A1 (fr) 2021-12-08 2021-12-08 Outil de communication pour un système de développement et système de production pour échanger des messages standardisés

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/EP2021/084772 WO2023104300A1 (fr) 2021-12-08 2021-12-08 Outil de communication pour un système de développement et système de production pour échanger des messages standardisés

Publications (1)

Publication Number Publication Date
WO2023104300A1 true WO2023104300A1 (fr) 2023-06-15

Family

ID=79164953

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/EP2021/084772 WO2023104300A1 (fr) 2021-12-08 2021-12-08 Outil de communication pour un système de développement et système de production pour échanger des messages standardisés

Country Status (1)

Country Link
WO (1) WO2023104300A1 (fr)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1923760A2 (fr) * 2006-10-20 2008-05-21 Rockwell Automation Technologies, Inc. Interface MES standard pour fabrication en série
EP2610697A2 (fr) * 2011-12-28 2013-07-03 Yokogawa Electric Corporation Système et procédé de gestion de cycle de vie de lot dans un système de commande de production en temps réel
DE102017119234A1 (de) * 2016-08-30 2018-03-01 Fanuc Corporation Produktionssystem mit einer funktion für das angeben der inspektionszeit für eine produktionsmaschine
EP3889714A1 (fr) * 2020-04-02 2021-10-06 Rockwell Automation Technologies, Inc. Environnement de conception d'automatisation industrielle collaborative en nuage

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1923760A2 (fr) * 2006-10-20 2008-05-21 Rockwell Automation Technologies, Inc. Interface MES standard pour fabrication en série
EP2610697A2 (fr) * 2011-12-28 2013-07-03 Yokogawa Electric Corporation Système et procédé de gestion de cycle de vie de lot dans un système de commande de production en temps réel
DE102017119234A1 (de) * 2016-08-30 2018-03-01 Fanuc Corporation Produktionssystem mit einer funktion für das angeben der inspektionszeit für eine produktionsmaschine
EP3889714A1 (fr) * 2020-04-02 2021-10-06 Rockwell Automation Technologies, Inc. Environnement de conception d'automatisation industrielle collaborative en nuage

Similar Documents

Publication Publication Date Title
EP3180666B1 (fr) Procédé de planification pour la fabrication d'un produit et module de production avec information d'autodescription
EP2476032B1 (fr) Procédé de configuration d'appareils d'automatisation à base soa et de développement d'un moteur d'orchestration, et procédé de fabrication
DE102004051179B4 (de) Einstellungsvorrichtung für ein Steuerungssystem, Verfahren zum Einstellen eines Steuerungssystems und Einstellungsprogramm
EP2555489B1 (fr) Procédé et dispositif de configuration de terminaux
DE112004000271T5 (de) Datenerfassung,-bündelung und -optimierung auf der Basis offener Netze zum Gebrauch in Prozess-Steuersystemen
DE102005008517A1 (de) Verfahren und System zum Integrieren von Alarmen in ein Prozeßsteuersystem
EP2555066A2 (fr) Amélioration d'imprimantes automatique
EP3646279B1 (fr) Procédé de planification de production
DE102019134312A1 (de) Systeme, verfahren und vorrichtungen zur verbesserung einer prozesssteuerung mit einem virtuellen assistenten
DE102007045926A1 (de) Schnittstelle zwischen einem Fertigungsmanagementsystem und einem Automatisierungssystem
DE112014003087T5 (de) Programm zur Common-Parameter-Schnittstellenerzeugung und Programm zum Lesen von Parametern
DE102017103830A1 (de) Maschinensystem, maschinensteuercomputer, basissoftwareanwendung, computerlesbares speichermedium, und maschinensteuerungsverfahren für die interkommunikation mit maschinen
DE102011055657A1 (de) Verfahren, System und Computer-Programm-Produkt zur Simulation eines Produktions-Automatisierungssystems mit service-orientierter Architektur
DE112004000349T5 (de) Betriebsverwaltungssystem
EP1490738A2 (fr) Machine de production dotee d'une commande integree dans un serveur web
DE102017124206A1 (de) Verfahren und vorrichtung zum konfigurieren eines fernzugriffs auf prozesssteuerungsdaten
DE102008061721A1 (de) Administrationssystem
WO2023104300A1 (fr) Outil de communication pour un système de développement et système de production pour échanger des messages standardisés
EP1444621A2 (fr) Gestion de processus et validation de processus
EP2713301A1 (fr) Procédé et système de liaison d'une commande pour une machine sur un système informatique placé en amont
DE102020124820A1 (de) Sicherer externer zugriff auf prozesssteuerungsdaten durch eine mobile vorrichtung
EP4154070A1 (fr) Commande de processus basée sur un jumeau numérique dans un réseau ido
EP1195664A1 (fr) Systeme de service avec optimisation
WO2002067151A1 (fr) Configurateur
WO2020200806A1 (fr) Procédé et dispositif de commande d'un appareil technique avec un modèle optimal

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 21834776

Country of ref document: EP

Kind code of ref document: A1