CN116862124A

CN116862124A - Production management system based on background robot

Info

Publication number: CN116862124A
Application number: CN202210303909.9A
Authority: CN
Inventors: 陈衡岳; 张文浩
Original assignee: BMW Brilliance Automotive Ltd
Current assignee: BMW Brilliance Automotive Ltd
Priority date: 2022-03-25
Filing date: 2022-03-25
Publication date: 2023-10-10

Abstract

The present disclosure relates to a production management system based on a background robot, comprising: a communication management module configured to manage communication between the production management system and the corresponding management object; a task scheduling module configured to manage task settings allocated to the respective management objects; a message management module configured to manage messages between the production management system and the respective message objects; a task configuration database in which task configuration data is stored; a message configuration database in which message configuration data is stored; and a set of background robots, each of the background robots being assigned a respective task and each of the background robots being configured to perform the assigned respective task in accordance with the task configuration data and/or the message configuration data. Thereby improving the management of the production systems.

Description

Production management system based on background robot

Technical Field

The present disclosure relates to the field of production management, and in general, to a production management system based on a background robot.

Background

In industrial production environments, such as those used in large scale manufacturing (e.g., the manufacture of aircraft, ships, vehicles, and large industrial machinery), highly complex machines, equipment, and systems, and highly complex workflows are involved, where numerous parameters, metrics, etc. must be considered in order to optimize the design, development, deployment, and operation of the different technologies, thereby improving the stability of the production system.

In the vehicle manufacturing industry, the types and numbers of production systems involved can be hundreds. Each production system has its own software solution installed on a different server or workstation, running on top of a variety of operating systems and having different interfaces and middleware. The diversity of such production systems provides flexible and advanced production capabilities for vehicle manufacturing, but at the same time places extremely high demands on the production management of the production systems. Because once a fault occurs in a complex production system environment, the production process is disturbed slightly, the repair workload is increased, the production cost is increased, and the production line is stopped seriously, so that a huge production risk is brought. In addition, product quality may be affected to affect brand image and even bring about a number of compliance and legal problems.

Therefore, how to improve the management of each production system is a technical problem to be solved by those skilled in the art.

Disclosure of Invention

It is an object of the present disclosure to provide a background robot-based production management system that overcomes at least one of the deficiencies of the prior art.

The present disclosure relates to a production management system based on a background robot, the production management system comprising: a communication management module configured to manage communication between the production management system and the corresponding management object; a task scheduling module configured to manage task settings allocated to the respective management objects; a message management module configured to manage messages between the production management system and the respective message objects; a task configuration database in which predefined task configuration data that can be called by the task scheduling module is stored, the task configuration data providing task settings assigned to corresponding management objects; a message configuration database in which predefined message configuration data is stored for invocation by the message management module, the message configuration data providing message settings assigned to corresponding message objects; and a set of background robots, each of the background robots being assigned a respective task and each of the background robots being configured to perform the assigned respective task in accordance with the task configuration data and/or the message configuration data.

In some embodiments, at least a portion of the set of background robots each have a robot account, the respective background robot configured to: the production management system is entered based on authentication of the robot account by the password login system, and a task list is acquired and ready to be executed upon entering the production management system.

In some embodiments, the at least a portion of the background robot is configured to: corresponding task instructions are sent based on the assigned task list.

In some embodiments, the at least a portion of the background robots generate respective task instructions by accessing and according to the respective task configuration data and/or message configuration data.

In some embodiments, the at least a portion of the background robot is configured to: receiving feedback data regarding task execution; evaluating the feedback data based on the corresponding evaluation logic; and determining a countermeasure based on the evaluation result.

In some embodiments, the at least a portion of the background robots determine respective evaluation logic and countermeasures by accessing and according to the respective task configuration data and/or message configuration data.

In some embodiments, a first part of the background robots in the background robot group maintain a login mode and wait for a next task after executing the corresponding task.

In some embodiments, a second part of the background robots in the background robot group log out after performing the corresponding task.

In some embodiments, the set of background robots includes a first background robot configured to periodically perform a respective first task and further monitor performance feedback regarding the first task.

In some embodiments, the set of background robots includes a second background robot configured to: the trigger of the real-time trigger performs a corresponding real-time task and further monitors the execution feedback regarding the second task.

In some embodiments, the second background robot is configured to: the external trigger interface can be accessed and triggered in real-time to perform a corresponding second task and further monitor execution feedback regarding the second task when a message from the external trigger interface is ascertained to satisfy a predetermined condition.

In some embodiments, the set of background robots includes a third background robot configured to: a task interface in the form of a database interface table can be accessed and triggered to execute a respective third task and further monitor execution feedback regarding the third task when ascertaining that the interface table of the database interface is populated with a respective data set.

In some embodiments, the set of background robots includes a fourth background robot configured to: based on the abnormality information in the execution feedback, a predetermined warning message is sent to the designated message object according to the task configuration data and/or the message configuration data.

In some embodiments, the production management system includes a configuration management module configured to manage a task configuration database and a message configuration database, preferably the configuration management module is configured to have a graphical user interface through which task settings assigned to respective management objects in the task configuration database and message settings assigned to respective message objects in the message configuration database are edited.

In some embodiments, the task scheduling module includes a task scheduling sub-module and a task logic sub-module.

In some embodiments, the task scheduling sub-module is configured to: find out whether the corresponding task setting is satisfied, trigger the corresponding task when the corresponding task setting is satisfied.

In some embodiments, the task logic sub-module is configured to: when the respective task is triggered, the respective task logic is provided to the respective background robot, preferably only a part of the tasks are assigned to the background robot group.

In some embodiments, the task settings include: a timed trigger setting configured to periodically trigger a task.

In some embodiments, the task settings include: a real-time trigger setting, the task scheduling module having an external trigger interface and a real-time trigger, wherein the real-time trigger setting is configured to: the task is triggered in real-time when the real-time trigger ascertains that the message from the external trigger interface satisfies a predetermined condition.

In some embodiments, the task settings include: an interface trigger setting, the task scheduling module having a task interface in the form of a database interface table, wherein the interface trigger setting is configured to: the task is triggered when the interface table of the database interface is populated with the corresponding data set.

In some embodiments, the production management system includes a feedback database in which first feedback data about management objects and second feedback data about message objects are stored, and when the feedback database identifies an anomaly based on the first feedback data and/or the second feedback data, the corresponding background robot is triggered to send an alarm message to a specified message object.

In some embodiments, the task scheduling module includes an exception management sub-module configured to: abnormality information is ascertained, and abnormality coping settings are generated based on the abnormality information, by which the message settings in the message configuration database can be adjusted.

In some embodiments, the anomaly management sub-module is configured to: transmitting the abnormality information and the abnormality coping setting to a feedback database; and the feedback database is configured to: the corresponding background robot is triggered to send an alarm message to the designated message object based on the anomaly information and the anomaly handling settings.

In some embodiments, the message management module includes a message generation sub-module, a transmission logic sub-module, and a connection management sub-module.

In some embodiments, the message generation sub-module is configured to: and calling message settings in a message configuration database to populate corresponding alarm message templates in a predetermined alarm message template library to generate alarm messages, and sending the messages by the corresponding background robots based on the generated alarm messages.

In some embodiments, the transmit logic sub-module is configured to: message settings in the message configuration database are invoked to determine the sending logic of the alert message, and the corresponding background robot performs message sending based on the determined sending logic.

In some embodiments, the transmit logic submodule includes an alert frequency manager configured to: the sending frequency of the alarm message is adjusted based on the message settings in the message configuration database, and the corresponding background robot sends the alarm message based on the adjusted sending frequency.

In some embodiments, the message management module includes a web page sub-module configured to: an alert web page is created based on the alert message generated by the message generation sub-module.

Drawings

The foregoing and other aspects and advantages of the present disclosure will become apparent from the following detailed description of exemplary embodiments, taken in conjunction with the accompanying drawings, illustrating by way of example the principles of the disclosure. It is noted that the drawings are not necessarily drawn to scale.

Fig. 1 illustrates a schematic block diagram of a production management system according to some embodiments of the present disclosure.

Fig. 2 illustrates a block diagram of a communication management module of a production management system, according to some embodiments of the present disclosure.

FIG. 3 illustrates a block diagram of a task scheduling module of a production management system, according to some embodiments of the present disclosure.

Fig. 4 illustrates a block diagram of a message management module of a production management system, according to some embodiments of the present disclosure.

Detailed Description

The present disclosure will be described below with reference to the accompanying drawings, which illustrate several embodiments of the present disclosure. It should be understood, however, that the present disclosure may be presented in many different ways and is not limited to the embodiments described below; indeed, the embodiments described below are intended to provide a more complete disclosure and to fully illustrate the scope of the disclosure to those skilled in the art. It should also be understood that the embodiments disclosed herein can be combined in various ways to provide yet additional embodiments.

It should be understood that the terminology herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the disclosure. All terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art unless otherwise defined. Well-known functions or constructions may not be described in detail for brevity and/or clarity.

In this document, the term "a or B" includes "a and B" and "a or B", and does not include exclusively only "a" or only "B", unless otherwise specifically indicated.

In this document, the term "exemplary" means "serving as an example, instance, or illustration. Any implementation described herein by way of example is not necessarily to be construed as preferred or advantageous over other implementations. Furthermore, this disclosure is not limited by any expressed or implied theory presented in the preceding technical field, background, brief summary or the detailed description.

In addition, for reference purposes only, the terms "first," "second," and the like may also be used herein, and the terms "first," "second," and the like may also refer to a plurality of the terms "first," "second," and the like. For example, the terms "first," "second," and other such numerical terms referring to structures or elements do not imply a sequence or order unless clearly indicated by the context.

It will be further understood that the terms "comprises" and/or "comprising," when used herein, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, and/or components, and/or groups thereof. Unless otherwise defined, all terms (including technical and scientific terms) are used herein to their ordinary meaning in the art to which examples belong.

The present disclosure provides a production management system based on a background robot, in particular for a vehicle. The production management system may also be referred to as a "production system stability integrated management system (Integrated Monitor & Warning Platform Solution)", which may centrally and uniformly manage, e.g., automatically monitor, automatically alert, etc., numerous production systems. In some cases, the production management system of the present disclosure may automatically address the problem and perform data collection and analysis of the stability elements of the individual production systems.

In the vehicle manufacturing industry, the variety and number of production systems are numerous. Each production system has its own software solution installed on a different server or workstation, running on top of a variety of operating systems and having different interfaces and middleware. Therefore, in order to efficiently perform unified management for each production system, the present disclosure proposes a production management system based on a background robot.

Background robots of the present disclosure may be understood as an application program that may be configured as a robotic flow automation system. The background robot may provide another way to automate the user manual process by mimicking the manual manner of operation of the user. The so-called "robot" concept is primarily characterized by its ability to work like a human. The flow, method, and external appearance of the work are similar to human operation. Whereby the manager can intuitively understand and supervise each working step of the background robot.

Aspects in accordance with the present disclosure are described in detail below with reference to fig. 1-4.

Referring to FIG. 1, a schematic block diagram of a production management system 10 according to some embodiments of the present disclosure is shown. The production management system 10 may include: a communication management module 20 that may be configured to manage communication between the production management system 10 and the corresponding management object 12; a task scheduling module 40 that may be configured to manage task settings assigned to the respective management objects 12; a message management module 90, which may be configured to manage messages between the production management system 10 and the corresponding message objects 70; a task configuration database 30, within which task configuration database 30 predefined task configuration data can be stored for invocation by the task scheduling module 40, the task configuration data providing task settings assigned to the respective management objects 12; a message configuration database 80, within which message configuration database 80 predefined message configuration data can be stored for invocation by the message management module 90, the message configuration data providing message settings assigned to the respective message object 70; and a set of background robots 100, each of the background robots being assigned a respective task and each of the background robots being configured to perform the assigned respective task in accordance with the task configuration data and/or the message configuration data.

According to the present disclosure, at least a portion of the background robots or all of the background robots in the background robot group 100 may each have a dedicated robot account prior to performing a task. The corresponding robotic account may enter the production management system 10 based on the authentication of the robotic account by the password login system. Upon entering the production management system 10, the corresponding background robot may ascertain the list of tasks to be performed and prepare to perform the list of tasks. In some cases, the respective background robot may periodically poll whether a task in the assigned task list is triggered, and once a task in the task list is triggered, begin executing the task.

During execution of a task, the respective background robot may generate respective task instructions by accessing the respective task configuration data and/or message configuration data and send the respective task instructions to the management object 12 or the message object 70. It should be understood that "access" of the present disclosure may refer to a call operation as well as a read operation. The corresponding background robot may obtain the task configuration data directly from the corresponding task configuration database 30 or may obtain the task configuration data from the task scheduling module 40. Similarly, the respective background robot may obtain message configuration data directly from the respective message configuration database 80, or from the message management module 90. These task configuration data and/or message configuration data may be sent together to the corresponding background robot when the task list is assigned. Alternatively, these task configuration data and/or message configuration data may also be accessed in real-time as the task is performed.

In some embodiments, the respective background robots may be configured to receive feedback data regarding task execution. For example, the respective background robot may receive feedback data directly from the respective management object 12 or message object 70, or may also receive feedback data from a feedback database described later. Further, the respective background robots may determine respective evaluation logic and countermeasures by accessing the respective task configuration data and/or message configuration data, and evaluate the feedback data based on the respective evaluation logic and determine the countermeasures based on the evaluation result. It should be appreciated that the respective background robots may obtain the evaluation logic and countermeasures directly from the respective task configuration database 30, or may obtain the evaluation logic and countermeasures from the task scheduling module 40.

After executing the task, the first part of background robots can keep a login mode and wait for the next task after executing the corresponding task, so that errors and faults caused by complex login and login-back operations of the part of background robots can be avoided. The second part of background robots log out after executing corresponding tasks, so that the occupation of resources can be saved.

Referring to fig. 1 and 2, a communication management module 20 of some embodiments of the present disclosure is described. As shown in fig. 2, the management object 12 may include, but is not limited to: production system, industrial sensor, printing equipment, message queue, PLC and database system.

As a production system IT is understood an IT system supporting production of whole vehicles and subassemblies, including a production control system and a product quality management system. In particular, the production system may for example comprise: the system comprises an engine cylinder casting control system, an engine machining control system, an engine assembly process production control system, an engine assembly process quality management system, a vehicle body stamping control system, a vehicle body welding control system, a vehicle assembly system, a vehicle quality management system, a vehicle electronic and electric appliance detection system and the like.

As industrial sensors, various types of detecting devices installed on a production line, such as temperature sensors, position sensors, light sensors, electromagnetic sensors, and the like, may be mentioned.

The printing equipment is critical equipment on a production line, and a corresponding work list or an assembly part list can be printed through the printing equipment so that an operator can know the work content which needs to be executed currently. Thus, failure of the printing apparatus can negatively impact the quality and efficiency of production.

A "message queue" is a container that holds messages during their transmission and can act as an intermediary in the relaying of messages from a source to a destination. The message is sent to a queue, the main purpose of which is to provide routing and to ensure delivery of the message; if the recipient is not available at the time the message is sent, the message queue will hold the message until it can be successfully delivered.

A PLC industrial controller, which may also be referred to as a programmable logic controller. PLCs are widely used as control devices on automated production lines. Therefore, the operation state of the PLC also affects the production efficiency and the production quality intimately.

Database system, which may be a system of databases and their management software. Typically, different database systems will exist in different production systems in order to manage the production data involved.

Since different management objects 12 may be installed in different workshops or factories, and different management objects 12 may employ different operating systems and/or communication protocols, the communication management module 20 of the present disclosure may have a connection management sub-module 22 and an information interaction management sub-module 24 for this purpose. As shown in fig. 1, the communication management module 20 may include a corresponding communication adapter for creating an adapted communication connection in accordance with the management object 12.

One or more of the following functions may be implemented as the connection management sub-module 22:

management object information registration function (e.g., IP address communication port of management object 12, etc.)

Authentication management function (login user, password management, etc.)

Connection function

Connection confirmation function (ensuring that a connection exists to ensure that communication can proceed normally)

Disconnect function.

One or more of the following functions may be implemented as the information interaction management sub-module 24:

send information

Receive information

Exception handling (to determine if sending or receiving information is successful or failed. If failure is returned to the calling side).

Because the production management system 10 of the present disclosure requires interactive operations with numerous management objects 12, scheduling management for these interactive operations is required to avoid causing system confusion and even failure. Referring to FIG. 1, a production management system 10 may include a task configuration database 30 and a task scheduling module 40. Within the task configuration database 30 may be stored predefined task configuration data that may be invoked by the task scheduling module 40, which provides task settings assigned to the respective management object 12, e.g., a list of management objects, a list of execution tasks, which may define an explanation of the operation performed with respect to the respective management object 12.

The task scheduling module 40 may be configured to manage task settings assigned to the respective management objects 12. The task scheduling module 40 may include a task scheduling sub-module 42 and a task logic sub-module 44. The task scheduling sub-module 42 may be configured to: find out whether the corresponding task setting is satisfied, trigger the corresponding task when the corresponding task setting is satisfied. It should be appreciated that in some embodiments of the present disclosure, only a portion of the triggered tasks are assigned to the respective background robots, while another portion of the triggered tasks may be assigned to script files or other applications. Logic regarding task allocation may be pre-defined in the task configuration database and arranged upon logging in of the corresponding robot.

The production management system 10 of the present disclosure provides a variety of task settings, such as a timing trigger setting, a real-time trigger setting, and an interface trigger setting, for a multitude of management objects 12.

For a portion of the managed objects 12, the production management system 10 of the present disclosure proposes a timed trigger setting that is configured to trigger tasks periodically, for example, once every 1 minute, 5 minutes, or 10 minutes, or even 30 minutes. When the first background robot 101 is assigned a timing task, the first background robot 101 may be configured to periodically perform the corresponding timing task. Preferably, the first background robot 101 may further monitor the execution feedback regarding the timed task. Advantageously, the first background robot 101 may also be configured to: the alarm message is sent to the designated message object by the exception information in the execution feedback.

For a portion of the managed objects 12, the production management system 10 of the present disclosure proposes a real-time trigger setting. To implement the real-time trigger settings, the task scheduling module 40 may have an external trigger interface 45 and a real-time trigger 47. The real-time trigger setting may be configured to: the real-time trigger 47 triggers a task when it ascertains that a message from the external trigger interface 45 satisfies a predetermined condition. When the second background robot 102 is assigned a real-time task, the second background robot 102 may be configured to: and the corresponding real-time task is executed under the triggering of the real-time trigger. Preferably, the second background robot 102 may further monitor the performance feedback regarding the real-time tasks. Advantageously, the second background robot 102 may also be configured to: the alarm message is sent to the designated message object by the exception information in the execution feedback. It is also possible that the second background robot 102 may be configured to: the external trigger interface can be accessed and triggered in real-time to perform a corresponding real-time task when it is ascertained that a message from the external trigger interface satisfies a predetermined condition.

As an example, the production management system 10 of the present disclosure specifies a real-time trigger setting for an engine manufacturing production system. In an engine manufacturing production system, when an engine passes through a predetermined first station, a first trigger signal is generated (via a communication management module if necessary) to be sent to an external trigger interface 45 of the production management system 10. Meanwhile, for the engine manufacturing production system, corresponding task settings including correspondence between trigger events and execution tasks are stored in the task configuration database 30. When the real-time trigger 47 ascertains that the message (i.e., the first trigger information) from the external trigger interface 45 satisfies one trigger event, then the execution task corresponding to the trigger event is triggered in real time. The respective background robot may perform real-time tasks according to predetermined task logic, e.g., send predetermined instructions to the respective management object and monitor task execution feedback from the management object. Advantageously, the respective background robot may further evaluate task execution feedback from the management object according to predetermined task logic and provide respective countermeasures. The corresponding countermeasures may include, for example, triggering an alarm message, etc.

When the real-time trigger 47 ascertains that the trigger event also requires a second trigger signal, it further waits for the second trigger signal to be reached without performing real-time triggering. When the engine passes through the predetermined second station, a second trigger signal is generated and sent to the external trigger interface 45 of the production management system 10. When the real-time trigger 47 ascertains that the messages (i.e., the first trigger signal and the second trigger signal) from the external trigger interface 45 satisfy the respective trigger events, the execution tasks corresponding to the trigger events are triggered in real time.

It should be appreciated that the corresponding task settings stored in the task configuration database 30 may include a combination of correspondence between a plurality of trigger events and a plurality of execution tasks, with the corresponding execution tasks being triggered in real-time once a particular trigger event is satisfied. In addition, a timing trigger setting and/or an interface trigger setting may be defined in parallel for the engine manufacturing production system.

For a portion of the management objects 12, the production management system 10 of the present disclosure proposes interface trigger settings. To implement the interface trigger settings, the task scheduling module 40 may have a task interface in the form of a database interface table. The interface trigger settings may be configured to: the task is triggered when the interface table is populated with the corresponding data set. When the third background robot 103 is assigned an interface task, the third background robot 103 may be configured to: a task interface in the form of a database interface table can be accessed and triggered to perform a corresponding third task when it is ascertained that the interface table of the database interface is populated with a corresponding data set. Preferably, the third background robot 103 may further monitor the execution feedback regarding the interface tasks. Advantageously, the third background robot 103 may also be configured to: the alarm message is sent to the designated message object by the exception information in the execution feedback.

As an example, the production management system 10 of the present disclosure specifies interface trigger settings for an engine manufacturing production system. In an engine quality management system, a database interface table may be utilized to implement task triggering. In some embodiments, the database interface table may be implemented within a feedback database 60 described later. For the engine quality management system, corresponding task settings are stored in the task configuration database 30, which task settings comprise an interface table and corresponding execution tasks, wherein when the interface table is filled with data, the corresponding execution tasks are triggered, for example, engine quality data extraction and inspection tasks are triggered. Quality management of the engine is thereby achieved in a reliable and efficient manner. Accordingly, a task may be triggered when an external trigger source sends a series of engine information and engine quality check information to a database such that the interface table is filled.

For example, the data of the interface table may include: engine number, engine type, detection station, detection ID, detection end time, detection type, flag of detection pass or not, detection cycle time, single evaluation ps_id, evaluation task_id, short curve evaluation ps_id, short curve evaluation task_id, long curve evaluation ps_id, and/or long curve evaluation task_id. When the interface tables within the database are populated with such data, the task scheduling sub-module 42 may trigger the corresponding task. The task logic sub-module 44 may then perform the corresponding operations based on these data based on the specific trigger task. In the case of performing a corresponding task by the background robot, the corresponding background robot may access the task logic sub-module 44 and perform the task based on the logic settings provided in the task logic sub-module 44.

It should be appreciated that the period of the timing trigger settings, the trigger events of the real-time trigger settings, and/or the interface table of the interface trigger settings for a particular management object 12 may be adjusted by compiling predefined task configuration data within the task configuration database 30. The adjustment of the task configuration data may be performed via a dedicated configuration management module 50. As shown in fig. 1, the production management system 10 may comprise a configuration management module 50 with a graphical user interface, which may be implemented as an application installed on the control terminal device, through which task settings assigned to the respective management objects 12 in the task configuration database 30 may be edited simply and efficiently. Advantageously, the production management system 10 may obtain the task setting adjustment feedback for the management object 12 from a dedicated message queue, and the corresponding task setting adjustment feedback may be provided to the configuration management module 50. The task setting adjustment feedback may be automatically generated from the management object or manually fed back by a dedicated operator.

Task logic submodule 44 may be configured to: when the corresponding task is triggered, corresponding task logic is provided to the background robot. The background robot based on task logic may be configured to: when a task is triggered, the corresponding management object 12 is accurately located, the control communication management module 20 establishes a connection with the corresponding management object 12, and communicates information with the corresponding management object 12 through task logic and performs a series of logic operations.

As shown in fig. 3, the task scheduling module 40 may interact with the communication management module 20, and when a respective task is triggered, the communication management module 20 may create a particular communication connection between the task scheduling module 40 and the management object 12 and send a series of logical operation instructions from the task scheduling module 40 to the respective management object 12 using the respective background robot in order to pertinently perform the respective task.

In some embodiments, the production management system 10 may include a feedback database 60 in which feedback data regarding the management objects 12 is stored in the feedback database 60. These feedback data may relate to response data generated when the corresponding task is performed with respect to the management object 12. It is advantageous to perform further evaluation on these feedback data so that the operation status of each management object 12 can be comprehensively grasped on the production management system 10 side. To this end, the production management system 10 may include a statistics module 62, which statistics module 62 may establish a data connection with the feedback database 60 in order to create a statistical model based on feedback data about the management objects 12. Advantageously, the production management system 10 may also include a web page module 64, which web page module 64 may establish a data connection with the statistics module 62 to generate a statistics report web page based on the created statistics model. Thus, the manager can clearly and visually understand the operation status of each management object 12 by logging in the corresponding web page.

Advantageously, when the production management system 10 identifies an anomaly, for example, after performing a task, the identified anomaly may be sent in the form of a message or an alert message to the message object 70, i.e., an external message recipient, in order to take countermeasures in a targeted manner. The feedback database 60 may be configured to: the message management module 90 is triggered to send an alert message based on the received abnormal feedback information. In some embodiments, the background robot may be configured to: the alarm message is sent to the designated message object by the identification of the anomaly information.

As shown in fig. 4, message objects 70 may include, but are not limited to: mail servers, worksheet system servers, mobile communication devices (short messages or automated voice), and/or enterprise-level messaging systems. The message object 70, after learning the alarm message, handles the abnormality that occurs according to the routine flow, so as to timely and accurately eliminate the abnormality. Because the production management system 10 of the present disclosure needs to interact with numerous message objects 70, there is a need for unified management of these message objects 70 to enable management of messages, and in particular triggering, generation and sending of alert messages, in a reliable and efficient manner. To this end, the production management system 10 of the present disclosure may include a message configuration database 80 and a message management module 90. Within the message configuration database 80 may be stored predefined message configuration data that can be invoked by the message management module 90, which provides message settings (e.g., message object list, message content, message sending frequency, etc.) assigned to the respective message object 70, which may define a description of the sending of messages for the respective message object 70. The message management module 90 may be configured to manage messages between the production management system 10 and the corresponding message object 70 in order to send problems identified by the production management system 10 in the form of messages to the message object 70, i.e., an external message recipient.

In some cases, the message management module 90 may have a variety of functions, such as providing a message queue function: for buffering messages to be sent; providing a messaging function: sending the message to the designated message object 70 according to the object defined by the message; providing a message recording function: after the message is sent, the message is recorded in the production management system 10 for later inspection.

As shown in fig. 1, the message management module 90 may include a message generation sub-module 92, a transmission logic sub-module 94, and a connection management sub-module 96. The message generation sub-module 92 may have a library of alert message templates. Upon receiving an alert trigger from the feedback database 60 or the anomaly management sub-module 55 described later, the message generation sub-module 92 may invoke message settings in the message configuration database 80 to populate a corresponding alert message template to generate an alert message and in some cases provide to the corresponding background robot. The transmit logic sub-module 94 may then be configured to: the message settings in the message configuration database 80 are invoked to determine the sending logic of the alert message and in some cases provide it to the corresponding background robot. The connection management sub-module 96 of the message management module 90 may include a message adapter for creating an adapted message connection in accordance with the message object 70. The background robot may be configured to: when a task is triggered, the corresponding message object 70 is located accurately, a control message adapter establishes a connection with the corresponding message object 70, and communicates information with the corresponding message object 70 via the sending logic.

For example, when feedback database 60 ascertains an abnormality, such as an unmatched crankshaft size parameter of the engine, based on feedback data from the engine quality management production system, feedback database 60 may send an alert trigger signal to message configuration database 80. The message configuration database 80 may trigger the message management module 90 to generate and send alert messages as specified to the corresponding message object 70, such as an engine design engineer or an engine production engineer, based on stored message settings (e.g., a recipient list of alert messages, i.e., a message object list, content of alert messages, such as a list of work listings that require the message object 70 to be communicated or executed, etc., sending logic of alert messages, such as a manner of sending or frequency of sending, etc.). The message generation sub-module 92 may invoke the message object list and the content of the alert message from the message configuration database 80 using the corresponding background robot and populate the corresponding alert message template based on such information to generate the alert message. The send logic sub-module 94 may invoke the send logic from the message configuration database 80 with the corresponding background robot to send the alert message to the corresponding message object 70 in a prescribed manner of sending, such as in the form of a mail or a short message. In some embodiments, the message management module 90 may include a web page sub-module configured to: an alert web page is created based on the alert message generated by the message generation sub-module 92. Thus, the message object 70 can clearly and visually understand the alarm message only by logging in the corresponding web page.

As an example, in the whole vehicle production line, all vehicles of a certain vehicle type need to complete the assembly work of the whole vehicle through the same assembly flow. However, some vehicles have a small probability of skipping certain assembly stations due to vehicle positioning signals and the like. To monitor and alert such "whole vehicle production line drop point" problems in time, the production management system 10 of the present disclosure implements monitoring of the vehicle production flow:

first, the production management system 10 may establish a communication connection with the entire vehicle manufacturing production system through the communication management module 20 using the background robot.

However, the production management system 10 can transmit the corresponding task settings via a communication connection to the entire production system by means of the task scheduling module 40 using the background robot.

Next, the entire vehicle manufacturing production system may perform a series of operations, such as monitoring the production status of each vehicle on the production line, based on the task settings from the production management system 10, and feeding back feedback data to the production management system 10. Specifically, after each vehicle passes through an assembly station, the whole vehicle manufacturing production system can generate detection data, so that a background robot can monitor the assembly station which the vehicle is currently subjected to, and record the result of each monitoring task.

Next, the production management system 10 may repeatedly monitor the entire vehicle production line by the timed execution of the tasks and obtain feedback data from the entire vehicle production line with the use of the background robot. After each time of executing the task, the whole vehicle production line checks whether the condition of 'the whole vehicle production line lost point' is found in the current execution, and if the condition of 'the whole vehicle production line lost point' is not found, the execution of the task is finished, and the task is waited for being called next time; if the "lost points of the whole production line" condition is found, the production management system 10 can trigger an alarm message and send the alarm message to corresponding production and operation maintenance personnel under the condition of utilizing the background robot. Furthermore, the production management system 10 may advantageously have a logging database for logging the alarm information for later statistical analysis.

In some embodiments, feedback database 60 may also store feedback data regarding message objects 70. These feedback data may relate to response data, advice data, or even complaint data from message object 70. It is advantageous to perform further evaluation on these feedback data so that the feedback of the individual message objects 70 can be comprehensively grasped on the production management system 10 side, and unified management across regions and departments can be better achieved. To this end, the production management system 10 may include a statistics module 62, which statistics module 62 may establish a data connection with the feedback database 60 in order to create a statistical model based on feedback data about the message objects 70. Advantageously, web page module 64 may establish a data connection with statistics module 62 to generate a statistics report web page based on the created statistics model. Thus, the manager can clearly and visually understand the feedback condition of each message object 70 by logging in the corresponding webpage.

In some cases, such as in the case of a timed trigger, such as in the case of a printer device jam, such as when the message queue exceeds a predetermined threshold, triggering of an alarm message may occur frequently. This is undesirable for message object 70. Advantageously, online adjustments may be made to the sending logic of the alert message when an anomaly occurs. To this end, the task scheduling module 40 may include an anomaly management sub-module 55, the anomaly management sub-module 55 may be configured to: the abnormality information is ascertained and abnormality coping settings are generated based on the abnormality information, and the message settings in the message configuration database 80 are edited by the abnormality coping settings determined by the abnormality management sub-module 55. In some embodiments, the anomaly management sub-module 55 may be configured to: the abnormality information and abnormality coping settings are sent to the feedback database 60. The feedback database 60 may be configured to: the message management module 90 is triggered to send an alert message based on the anomaly information and the anomaly handling settings.

The anomaly management sub-module 55 may adjust, e.g., reduce, the frequency of sending alert messages in the anomaly handling settings to avoid excessively frequent alert messages from causing a bad experience with the message object 70. Additionally or alternatively, the transmit logic sub-module 94 may include an alert frequency manager, which may be configured to: the frequency of sending the alert message is adjusted based on the message settings in the message configuration database 80.

As shown in fig. 1, the adjustment of the message configuration data may be performed via a configuration management module 50 with a graphical user interface. The message settings assigned to the corresponding message object 70 in the message configuration database 80 can be edited simply and efficiently through the graphical user interface. Advantageously, the production management system 10 may obtain message setting adjustment feedback for the message object 70 from a dedicated message queue, and the corresponding message setting adjustment feedback may be provided to the configuration management module 50.

The present disclosure achieves communication management, task logic management, and messaging management through the cooperative cooperation of the configuration management module 50, the task configuration database 30, and the message configuration database 80. Unlike common approaches implemented by cumbersome and error-prone programming code, the disclosed approach may more efficiently implement such a very large scale production management system 10.

Having thus described the present disclosure, it will be apparent that the present disclosure may be varied in a number of ways. Such variations are not to be regarded as a departure from the spirit and scope of the present disclosure, and all such modifications as would be obvious to one skilled in the art are intended to be included within the scope of the following claims.

Claims

1. A production management system based on a background robot, the production management system comprising:

a communication management module configured to manage communication between the production management system and the corresponding management object;

a task scheduling module configured to manage task settings allocated to the respective management objects;

a message management module configured to manage messages between the production management system and the respective message objects;

a task configuration database in which predefined task configuration data that can be called by the task scheduling module is stored, the task configuration data providing task settings assigned to corresponding management objects;

a message configuration database in which predefined message configuration data is stored for invocation by the message management module, the message configuration data providing message settings assigned to corresponding message objects; and

a set of background robots, each background robot being assigned a respective task and each background robot being configured to perform the assigned respective task in accordance with task configuration data and/or message configuration data.

2. The production management system of claim 1, wherein at least a portion of the background robots in the set of background robots each have a robot account, the respective background robots configured to: the production management system is entered based on authentication of the robot account by the password login system, and a task list is acquired and ready to be executed upon entering the production management system.

3. The production management system of claim 2, wherein the at least a portion of the background robots are configured to: and sending corresponding task instructions based on the assigned task list, wherein the at least one part of background robots generate the corresponding task instructions by accessing corresponding task configuration data and/or message configuration data and according to the task configuration data and/or message configuration data.

4. The production management system of claim 3, wherein the at least a portion of the background robot is configured to:

receiving feedback data regarding task execution;

evaluating the feedback data based on the corresponding evaluation logic; and

a countermeasure is determined based on the evaluation result,

wherein the at least a portion of the background robots determine the respective evaluation logic and the corresponding countermeasures by accessing the respective task configuration data and/or message configuration data and in accordance with the task configuration data and/or message configuration data.

5. The production management system of claim 2, wherein,

after the first part of background robots in the background robot group execute corresponding tasks, keeping a login mode and waiting for the next task;

And the second part of the background robots in the background robot group log out after executing the corresponding tasks.

6. The production management system of claim 2 or 3, wherein,

the set of background robots includes a first background robot configured to periodically perform a respective first task and further monitor performance feedback regarding the first task;

the set of background robots includes a second background robot configured to: the corresponding real-time task is executed under the triggering of the real-time trigger, and the execution feedback about the second task is further monitored; or the second background robot is configured to: an external trigger interface can be accessed, and when a message from the external trigger interface is ascertained to meet a predetermined condition, the corresponding second task is triggered to be executed in real time and execution feedback about the second task is further monitored; and/or

The set of background robots includes a third background robot configured to: a task interface in the form of a database interface table can be accessed and triggered to execute a respective third task and further monitor execution feedback regarding the third task when ascertaining that the interface table of the database interface is populated with a respective data set.

7. The production management system of claim 6, wherein,

the set of background robots includes a fourth background robot configured to: based on the abnormality information in the execution feedback, a predetermined warning message is sent to the designated message object according to the task configuration data and/or the message configuration data.

8. The production management system according to claim 1, characterized in that the production management system comprises a configuration management module configured to manage a task configuration database and a message configuration database, preferably the configuration management module is configured to have a graphical user interface by means of which task settings assigned to the respective management object in the task configuration database and message settings assigned to the respective message object in the message configuration database are edited.

9. The production management system of claim 1, wherein,

the task scheduling module includes a task scheduling sub-module and a task logic sub-module,

the task scheduling sub-module is configured to: ascertaining whether the corresponding task setting is satisfied, triggering the corresponding task when the corresponding task setting is satisfied;

The task logic sub-module is configured to: when the respective task is triggered, the respective task logic is provided to the respective background robot, preferably only a part of the tasks are assigned to the background robot group.

10. The production management system of claim 9, wherein the task setting comprises:

a timed trigger setting configured to periodically trigger a task;

a real-time trigger setting, the task scheduling module having an external trigger interface and a real-time trigger, wherein the real-time trigger setting is configured to: when the real-time trigger finds that the message from the external trigger interface meets the preset condition, the task is triggered in real time; and/or

An interface trigger setting, the task scheduling module having a task interface in the form of a database interface table, wherein the interface trigger setting is configured to: the task is triggered when the interface table of the database interface is populated with the corresponding data set.

11. The production management system according to claim 1, characterized in that the production management system comprises a feedback database in which first feedback data about management objects and second feedback data about message objects are stored, and when the feedback database identifies an abnormality based on the first feedback data and/or the second feedback data, the corresponding background robot is triggered to send an alarm message to a specified message object.

12. The production management system of claim 11, wherein the task scheduling module comprises an anomaly management sub-module configured to: ascertaining the anomaly information and generating anomaly handling settings based on the anomaly information, by which the message settings in the message configuration database can be adjusted,

preferably, the anomaly management sub-module is configured to: transmitting the abnormality information and the abnormality coping setting to a feedback database; and the feedback database is configured to: the corresponding background robot is triggered to send an alarm message to the designated message object based on the anomaly information and the anomaly handling settings.

13. The production management system of claim 1, wherein,

the message management module comprises a message generation sub-module, a sending logic sub-module and a connection management sub-module,

wherein the message generation sub-module is configured to: calling message setting in a message configuration database to fill a corresponding alarm message template in a preset alarm message template library so as to generate an alarm message, and sending a message by a corresponding background robot based on the generated alarm message;

Wherein the transmit logic sub-module is configured to: message settings in the message configuration database are invoked to determine the sending logic of the alert message, and the corresponding background robot performs message sending based on the determined sending logic.

14. The production management system of claim 13, wherein the transmit logic submodule includes an alert frequency manager configured to: the sending frequency of the alarm message is adjusted based on the message settings in the message configuration database, and the corresponding background robot sends the alarm message based on the adjusted sending frequency.

15. The production management system of claim 13, wherein the message management module comprises a web page sub-module configured to: an alert web page is created based on the alert message generated by the message generation sub-module.