Method, device, system and computer readable medium for production monitoring

Abstract

The invention provides a method, a device, a system and a computer readable medium for production monitoring. A method for production monitoring, comprising: acquiring fault information relating to at least one production control device, each production control device being assigned to at least one functional device accordingly; acquiring a fault solution corresponding to the fault information; and sending the fault information and the fault solution corresponding to the fault information to the terminal equipment. Therefore, production faults can be found more timely, and the occurred production faults can be dealt with more efficiently.

Description

Technical Field

[0001] The present disclosure relates to the field of production monitoring, and in general to a method, an apparatus, a system and a computer-readable medium for production monitoring. Background Art

[0002] In the production workshop of a modern factory, there are usually a large number of production control devices, such as PLC (Programmable Logic Controller) devices. These production control devices can be configured to monitor the functional equipment they are responsible for. Usually, a dedicated staff member is required to monitor the industrial computer in the central control dispatch room in order to manually find fault information and manually notify the fault. The operating status of each functional device can be displayed on the interface of the industrial computer. When a functional device fails, the staff can find the fault information from the interface of the industrial computer and manually notify it. However, this solution relies entirely on manual monitoring by the staff, which is insufficient in efficiency, cost and / or reliability. Therefore, how to further improve production monitoring for production failures is a technical problem that needs to be solved urgently by those skilled in the art. Summary of the invention

[0003] The purpose of the present disclosure is to provide a method, device, system and computer-readable medium for production monitoring, which can detect production failures more promptly and deal with the occurring production failures more efficiently, thereby further improving production efficiency and / or production quality.

[0004] According to a first aspect of the present disclosure, a method for production monitoring is provided, comprising: obtaining fault information related to at least one production control device, each production control device being correspondingly assigned to at least one functional device; obtaining a fault solution corresponding to the fault information; and sending the fault information and the fault solution corresponding to the fault information to a terminal device.

[0005] In some embodiments, the step of acquiring a fault solution corresponding to the fault information includes: acquiring the fault solution corresponding to the fault information from a first database that pre-stores the fault solutions corresponding to the fault information.

[0006] In some embodiments, the method also includes: determining whether the fault information belongs to a predetermined type; wherein, when the fault information belongs to the predetermined type, obtaining a fault solution corresponding to the fault information, and sending the fault information and the fault solution corresponding to the fault information to a terminal device.

[0007] In some embodiments, the method further includes: storing the fault information determined to be of the predetermined type in a second database; the predetermined type of fault information is related to a fault that will cause the production line to stop operating.

[0008] In some embodiments, the fault information includes production control device identification data, functional equipment identification data and fault type data; the fault type data includes different types of fault states.

[0009] In some embodiments, acquiring fault information related to at least one production control device includes: acquiring fault information related to a plurality of production control devices involved in production operation of a main production line.

[0010] In some embodiments, obtaining fault information related to at least one production control device includes: periodically obtaining the fault information related to at least one production control device; wherein the fault information related to at least one production control device is periodically obtained during production and during non-production periods, wherein the period for obtaining the fault information during production is shorter than the period for obtaining the fault information during non-production periods.

[0011] In some embodiments, the method further includes: receiving an activation instruction, wherein the activation instruction indicates that new fault information related to the at least one production control device has been generated; and starting to obtain the fault information related to the at least one production control device based on the activation instruction.

[0012] In some embodiments, the fault information includes a fault information description including a fault description in the form of text information, and the fault solution includes a fault solution description including a fault solution description in the form of text information.

[0013] In some embodiments, the method further includes: determining an associated terminal device group based on the acquired fault information, wherein the determined associated terminal device group includes multiple terminal devices; wherein the fault information description and the fault solution description are provided to the multiple terminal devices included in the terminal device group.

[0014] In some embodiments, the terminal device includes a mobile terminal, and the step of sending the fault information and the fault solution corresponding to the fault information includes: sending the fault information and the fault solution corresponding to the fault information to the mobile terminal via text message, email, or application.

[0015] According to a second aspect of the present disclosure, there is provided an apparatus for production monitoring, comprising: a memory on which instructions are stored; and a processor configured to execute the instructions stored on the memory to perform the above method.

[0016] According to a third aspect of the present disclosure, a system for production monitoring is provided, comprising: a plurality of production control devices, each of which is correspondingly assigned to at least one functional device in a production area; a server, which is configured as the above-mentioned device; and a plurality of terminal devices, each of which is configured to communicate with the server to receive the fault information and the fault solution corresponding to the fault information.

[0017] According to a fourth aspect of the present disclosure, a non-transitory computer-readable medium is provided, on which computer-executable instructions are stored, and when the computer-executable instructions are executed by one or more computing devices, the one or more computing devices execute the above method.

[0018] According to the embodiments of the present disclosure, a method, device, system and computer-readable medium for production monitoring can be provided, which can detect production failures more promptly and deal with the occurring production failures more efficiently, thereby further improving production efficiency and / or production quality. BRIEF DESCRIPTION OF THE DRAWINGS

[0019] The above and other aspects and advantages of the present disclosure will become apparent from the following detailed description of exemplary embodiments in conjunction with the accompanying drawings, which illustrate the principles of the present disclosure by way of example. It should be noted that the drawings are not necessarily drawn to scale.

[0020] Figure 1 A schematic diagram of monitoring fault information on an industrial computer interface in the related art is shown;

[0021] Figure 2 A schematic block diagram of a system for production monitoring according to an embodiment of the present disclosure is shown;

[0022] Figure 3 An exemplary flow chart of a method for production monitoring according to an embodiment of the present disclosure is shown;

[0023] Figure 4 An example flow chart showing sub-steps of a method for production monitoring according to an embodiment of the present disclosure;

[0024] Figure 5 An example flow chart showing other steps of the method for production monitoring according to an embodiment of the present disclosure;

[0025] Figure 6An example flow chart showing other steps of the method for production monitoring according to an embodiment of the present disclosure;

[0026] Figure 7 An example flow chart showing sub-steps of a method for production monitoring according to an embodiment of the present disclosure;

[0027] Figure 8 An example flow chart showing sub-steps of a method for production monitoring according to an embodiment of the present disclosure;

[0028] Fig. 9 An example flow chart showing sub-steps of a method for production monitoring according to an embodiment of the present disclosure;

[0029] Fig.10 A schematic diagram showing a description of fault information and solutions in text form on a terminal device;

[0030] Fig.11 An example flow chart showing other steps of the method for production monitoring according to an embodiment of the present disclosure;

[0031] Fig.12 A schematic diagram of a server interface for grouping terminal devices is shown;

[0032] Fig.13 An example flow chart showing sub-steps of a method for production monitoring according to an embodiment of the present disclosure;

[0033] Fig.14 A schematic diagram showing a method of sending fault information to a terminal device and a fault resolution method;

[0034] Fig.15 An example flow chart of a method for production monitoring in a specific application example is shown;

[0035] Fig.16 An exemplary configuration of a computing device 105 is shown that may implement embodiments according to the present disclosure. DETAILED DESCRIPTION

[0036] The present disclosure will be described below with reference to the accompanying drawings, wherein the accompanying drawings illustrate several embodiments of the present disclosure. However, it should be understood that the present disclosure can be presented in a variety of different ways and is not limited to the embodiments described below; in fact, the embodiments described below are intended to make the present disclosure more complete and fully illustrate the scope of protection of the present 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 more additional embodiments.

[0037] It should be understood that the terms used herein are only used to describe specific embodiments and are not intended to limit the present disclosure. All terms (including technical terms and scientific terms) used herein have the meanings commonly understood by those skilled in the art unless otherwise defined. For the sake of simplicity and / or clarity, well-known functions or structures may not be described in detail.

[0038] Herein, the term "A or B" includes "A and B" and "A or B" rather than exclusively including only "A" or only "B", unless specifically stated otherwise.

[0039] As used herein, the term "exemplary" means "serving as an example, instance, or illustration". Any implementation described as an example herein is not necessarily to be construed as preferred or advantageous over other implementations. Furthermore, the present disclosure is not to be limited by any stated or implied theory presented in the above technical field, background technology, summary of the invention, or detailed description.

[0040] In addition, for reference purposes only, the terms "first", "second" and the like may also be used herein, and "first" and "second" may also refer to multiple "firsts" and "seconds". For example, the terms "first", "second" and other such numerical terms referring to structures or elements do not imply a sequence or order unless the context clearly indicates otherwise.

[0041] It should also be understood that when the term "include / comprise" is used in this article, it indicates the presence of the indicated features, integrals, steps, operations, units and / or components, but does not exclude the presence or addition of one or more other features, integrals, steps, operations, units and / or components and / or their combinations. Unless otherwise defined, all terms (including technical terms and scientific terms) are used in this article according to their general meaning in the field to which the examples belong.

[0042] The present application relates to a system for production monitoring, which can be deployed in various types of manufacturing plants to play a beneficial role in the production monitoring of the plant. In the present application, a manufacturing plant can be understood as an enterprise that can implement the production and / or processing of products or parts, and these manufacturing plants can, for example, involve various types of manufacturing industries. The following is an illustrative introduction to various aspects of the present application by taking a vehicle manufacturing plant, such as a complete vehicle manufacturing plant, as an example. It should be understood that various aspects of the present application can be applicable to other types of manufacturing plants, such as vehicle parts manufacturing plants, aircraft manufacturing plants, pharmaceutical plants, tool manufacturing plants, etc., and are not limited to the following specific embodiments.

[0043] Manufacturing plants, such as vehicle manufacturing plants, are usually located in a large area, and different process flows are usually scattered in different plant areas or workshops. For example, taking vehicle manufacturing as an example, vehicle manufacturing can usually include the following four major process flows: stamping production line flow, welding production line flow, painting production line flow, and final assembly production line flow. The wide distribution of different process flows poses a severe challenge to the daily production monitoring of the factory.

[0044] Various types of equipment failures may be involved in daily production monitoring. At present, some conventional practices are to rely mainly on buzzers to inform maintenance personnel that functional equipment is in a faulty state, and then rely on interactive screens to obtain specific fault information. However, this solution requires the installation of a large number of screens and buzzers in distributed locations within the factory, which is disadvantageous in terms of cost. In addition, for maintenance personnel, they need to first hear the alarm sound from the buzzer through their ears, and then obtain the fault information through the interactive screen, which is disadvantageous in terms of efficiency.

[0045] In addition, during production, a dedicated staff member is always required to monitor the industrial computer in the central control room in order to manually find fault information and manually notify the fault. The operating status of each functional device can be displayed on the interface of the industrial computer. When a functional device fails, the staff can find the fault information from the interface of the industrial computer and manually notify it. However, this solution relies entirely on manual monitoring by the staff, which is insufficient in efficiency, cost and / or reliability. This solution requires authoritative and complex processes to obtain results or use PCs for monitoring. Use a separate interface to view each PLC in the component.

[0046] Figure 1 It is a schematic diagram showing the monitoring of fault information on an industrial computer interface in the related art.

[0047] In addition, it may happen that some failures occur during non-production periods, and some of the failures may affect the production of the next shift. This is obviously undesirable. The above solution cannot monitor and decide in real time during non-production time.

[0048] Based on the above situation, the present application proposes a method, device, system and computer-readable medium for production monitoring, which can detect production failures more promptly and deal with production failures more efficiently, thereby further improving production efficiency and / or production quality.

[0049] Next reference Figures 2 to 14 Various aspects according to the present disclosure are described in detail.

[0050] First reference Figure 2 , showing a schematic block diagram of a system 100 for production monitoring according to some embodiments of the present disclosure.

[0051] like Figure 2 As shown, the system 100 for production monitoring may include a plurality of production control devices 10 , a server 30 and a plurality of terminal devices 40 .

[0052] Each production control device 10 may be configured to control the operation of a functional device. To this end, the production control device 10 may establish a communication connection with the corresponding functional device, by means of which the production control device 10 may obtain real-time operating parameters from the functional device and may send control instructions to the functional device.

[0053] In the present application, functional equipment should be broadly understood as any functional equipment involved in production. In some embodiments, functional equipment may include a variety of production process equipment and parts thereof installed at different stations of the production line. As an example, the functional equipment may be a lift or a motor for the lift. As an example, the functional equipment may be a compression device or a motor or valve for a compression device. As an example, the functional equipment may be a lubrication device or a flow sensor for a lubrication device. In some embodiments, the functional equipment may include functional equipment for auxiliary production, such as lighting equipment, air conditioning equipment, ventilation equipment, and / or smoke alarms, etc.

[0054] In the present application, the production control device 10 should be broadly understood as any control device involved in production. In some embodiments, the production control device can be configured as a controller, such as a PLC controller (i.e., a programmable logic controller) or a control host, so as to monitor the responsible functional devices. The production control device can be centrally stored in a central control room or distributedly deployed in control cabinets next to the corresponding controlled objects, i.e., functional devices.

[0055] In order to monitor the operating status of each functional device, such as fault information, in real time, each production control device can communicate with a database. The production control device can find out the fault information related to the functional device based on the operating parameters obtained from the functional device, and transmit the corresponding fault information to the database via a communication connection, such as wireless communication. The database can be set in the server described later, but is not limited thereto.

[0056] Fault information about production control devices and further about specific functional devices may be stored in the database 20. In some embodiments, the fault information may include production control device identification data that can univocally characterize the corresponding production control device, functional device identification data that can univocally characterize the corresponding functional device, and fault type data that can univocally characterize the corresponding fault type. The fault type data may include fault states of different types / levels.

[0057] In some embodiments, the fault type data may include a first fault type, a second fault type, a third fault type, and the like. Advantageously, simple identification data may be used in the message to univocally characterize different types. As an example, identification data "2" indicates "connection fault", identification data "3" indicates "communication fault", identification data "4" indicates "alarm fault", identification data "5" indicates "component fault", and the like. It should be understood that the division and characterization of fault type data may be flexible and non-limiting.

[0058] The server 30 can be configured, for example, as a cloud server to obtain corresponding fault information from the database 20. The server can be configured to obtain a fault solution corresponding to the fault information from the database 22 based on the acquired fault information, and send the fault information and the fault solution corresponding to the fault information to the terminal device 40. The databases 20 and 22 can be set on the server 30, but are not limited to this. Each terminal device 40 can be configured to communicate with the server 30 and receive fault information and a fault solution corresponding to the fault information. In some embodiments, the terminal device includes a mobile terminal. The terminal device 40 can be configured as a smart device, a smart phone, a smart watch, etc. carried by a staff member. As a result, the staff member can query the fault situation of the production site and the solution to the fault on the terminal device carried by him anytime and anywhere.

[0059] Next reference Figure 3 , introduces an exemplary flow chart of a method for production monitoring according to an embodiment of the present disclosure. It should be understood that the associated content described in the system for production monitoring according to an embodiment of the present disclosure can be applicable to the production monitoring method according to some embodiments of the present disclosure.

[0060] The production monitoring method according to some embodiments of the present disclosure may be implemented in a device for production monitoring according to some embodiments of the present disclosure, and the device may include a memory on which instructions are stored; and a processor configured to execute the instructions stored in the memory to execute the method according to the embodiments of the present disclosure. In some embodiments, the device for production monitoring may be configured as a server, such as a cloud server.

[0061] The steps of the method presented below are intended to illustrate. In certain embodiments, the method can be completed with one or more additional undescribed steps, and / or without one or more discussed steps. In addition, the order of the steps shown in the figures and described below of the method is not intended to be limited.

[0062] like Figure 3 As shown, the method for production monitoring may include the following steps:

[0063] S20: Acquire fault information related to at least one production control device, each production control device being correspondingly assigned to at least one functional device.

[0064] S30: Obtain a fault solution corresponding to the fault information.

[0065] S40: Sending fault information and a fault solution corresponding to the fault information to the terminal device.

[0066] Figure 4 is an example flow chart of sub-steps of a method for production monitoring according to an embodiment of the present disclosure.

[0067] like Figure 4 As shown, in some embodiments, the step of obtaining a fault solution corresponding to the fault information includes: S32, obtaining a fault solution corresponding to the fault information from a first database that pre-stores fault solutions corresponding to the fault information.

[0068] The database 22 may be equivalent to the first database, and may pre-store fault solutions corresponding to the fault information.

[0069] Figure 5 is an example flow chart of other steps of the method for production monitoring according to an embodiment of the present disclosure.

[0070] like Figure 5 As shown, in some embodiments, the above method also includes: S50, determining whether the fault information belongs to a predetermined type; wherein, when the fault information belongs to the predetermined type, obtaining a fault solution corresponding to the fault information; and transmitting the fault information and the fault solution corresponding to the fault information to the terminal device.

[0071] Figure 6 is an example flow chart of other steps of the method for production monitoring according to an embodiment of the present disclosure.

[0072] like Figure 6 As shown, in some embodiments, the method further includes: S60, storing the fault information determined to be of a predetermined type in a second database; the predetermined type of fault information is related to the fault that will cause the production line to stop running.

[0073] The database 20 may be equivalent to the second database, storing information determined to be of a predetermined type. The predetermined type of fault information may be, for example, high-level fault information related to a fault that causes the production line to stop running, but is not limited thereto.

[0074] In some embodiments, the fault information includes production control device identification data, functional equipment identification data and fault type data; the fault type data includes different types of fault states.

[0075] For example, it can be determined whether the fault information belongs to a high level according to the aforementioned fault type data. For example, the fault information related to "communication fault" indicated by the flag data "3" is classified as high level fault information, but it is not limited thereto.

[0076] Figure 7 is an example flow chart of sub-steps of a method for production monitoring according to an embodiment of the present disclosure.

[0077] like Figure 7 As shown, in some embodiments, obtaining fault information related to at least one production control device includes: S22, obtaining fault information related to multiple production control devices involved in the production operation of the main production line. To this end, the production line can be divided into a main production line and an auxiliary production line (such as a pre-installation production line, a maintenance production line, etc.). Generally, the main production line may involve a production line for assembling the vehicle body, while the auxiliary production line may involve a production line for assembling vehicle parts such as door lines, electrical components, and glass. It is advantageous to focus the scope of fault transmission to the main production line: first, usually the fault of the main production line will significantly affect the production efficiency, so focusing the scope of fault transmission to the main production line allows the fault involving the main production line to be handled in a timely manner; second, too much transmission content increases the difficulty of system design on the one hand, and increases the difficulty of user reception on the other hand.

[0078] Figure 8 is an example flow chart of sub-steps of a method for production monitoring according to an embodiment of the present disclosure.

[0079] like Figure 8 As shown, in some embodiments, obtaining fault information related to at least one production control device includes: S24, periodically obtaining fault information related to at least one production control device; wherein, the fault information related to at least one production control device is periodically obtained during production and during non-production, wherein the period of obtaining fault information during production is shorter than the period of obtaining fault information during non-production. By periodically obtaining fault information during non-production, it is advantageously possible to allow staff to grasp the fault information of the production site before officially starting the next production shift, so as to deal with the fault information as early as possible and avoid a greater impact on production. Nevertheless, the probability of a fault occurring during production is usually significantly higher than that occurring during non-production, so that the period of obtaining fault information during production is shorter than the period of obtaining fault information during non-production, which is beneficial to reducing system operating costs and / or energy consumption.

[0080] Fig. 9 is an example flow chart of other steps of the method for production monitoring according to an embodiment of the present disclosure.

[0081] like Fig. 9 As shown, in some embodiments, the method for production monitoring may further include the following steps:

[0082] S70: Receive an activation instruction, where the activation instruction indicates that new fault information related to at least one production control device has been generated.

[0083] S80: Start acquiring fault information related to at least one production control device based on the activation instruction.

[0084] The message sent from the production control device may include an activation instruction and fault information. After receiving the message sent from the production control device, the server may start to obtain fault information related to the predetermined production control device based on the activation instruction contained in the received message. This method step triggered by the activation instruction can further reduce the system operation cost and / or energy consumption.

[0085] Fig.10 The diagram is a diagram showing description of fault information and solutions in text form on a terminal device.

[0086] like Fig.10 As shown, in some embodiments, the fault information includes a fault information description, which includes a fault description in the form of text information, and a fault solution description, which includes a fault solution description in the form of text information.

[0087] Fig.11 is an example flow chart of other steps of the method for production monitoring according to an embodiment of the present disclosure. Fig.12 is a schematic diagram of a server interface showing grouping of terminal devices.

[0088] like Fig.11 As shown, in some embodiments, the method for production monitoring further includes: S90, determining an associated terminal device group based on the acquired fault information, wherein the determined associated terminal device group includes multiple terminal devices; wherein the fault information description and the fault solution description are provided to the multiple terminal devices included in the terminal device group. In some cases, some complex fault problems may involve multiple production control devices, which may involve multiple staff members. A staff member may be associated with multiple production control devices and be responsible for alarms issued by multiple production control devices. In order to further improve the solution mechanism for this type of fault, a work group (terminal device group / user group) can be automatically created, and a fault information description and a fault solution description are provided within the work group. The above-mentioned terminal device can be a terminal device held by a user, and the terminal device group can also be a user's group.

[0089] like Fig.12 As shown, the server may include an alarm server, a message server, and a fault solution server. For example, the message server divides the terminal devices into multiple groups.

[0090] Fig.13 is an example flow chart of sub-steps of a method for production monitoring according to an embodiment of the present disclosure. Fig.14 It is a schematic diagram showing a method of sending fault information to a terminal device and solving the fault.

[0091] like Fig.13 As shown, in some embodiments, the terminal device includes a mobile terminal, and the step of sending fault information and a fault solution corresponding to the fault information includes: S42, sending the fault information and a fault solution corresponding to the fault information to the mobile terminal via a text message, an email, or an application.

[0092] like Fig.14 As shown, for example, the sending method may include short messages such as SMS, emails such as E-mail, applications such as Joychat, etc., but is not limited thereto.

[0093] In some embodiments, feedback information from a terminal device is received. Advantageously, the feedback information from the terminal device may include location information or picture information sent by a staff member at the production site, so as to make it clear that the staff member has started to handle the relevant fault. Advantageously, the feedback information from the terminal device may include fault-solved information sent by a staff member at the production site, so as to make it clear that the staff member has solved the relevant fault.

[0094] In some embodiments, the feedback information from the terminal device includes the fault resolution start time point and / or the fault resolution end time point. Additionally or alternatively, the working time of the staff member handling the corresponding fault is determined based on the fault resolution start time point and the fault resolution end time point, and the corresponding work content and working time are automatically recorded in the work order of the relevant staff member.

[0095] In some embodiments, when no feedback information is received for a fault discovered during a non-production period within a predetermined time before the start of the next production shift or within a predetermined time after the start of the next production shift, a fault broadcast instruction is generated to trigger the broadcast of the corresponding fault within the factory and summon relevant maintenance personnel to the site as soon as possible for processing.

[0096] Fig.15 An exemplary flow chart showing a method for production monitoring in a specific application example.

[0097] For example, the alarm server collects the alarm information sent by the PLC. The alarm server then analyzes the received alarm information and classifies it into high-level alarms and other categories. The high-level alarms are stored in the second database, and the message server obtains the high-level alarm information from the database and pushes it to the user terminal. The push methods include: short message (SMS), e-mail (E-mail), phone (Cell phone), etc. In addition, the user terminal can be divided into multiple groups related to the fault and pushed separately. In addition, feedback information can be obtained from multiple groups. Multiple PLCs can also be divided into multiple groups according to their production areas.

[0098] In addition, the fault solution server searches the first database for a fault solution corresponding to the fault information according to the fault information. The message server obtains the fault solution from the first database and also pushes it to the user terminal.

[0099] Through the method, device, system and computer-readable medium for production monitoring disclosed in the present invention, production failures can be discovered more timely, and the production failures that occur can be dealt with more efficiently, thereby further improving production efficiency and / or production quality. It can be from passive alarm information discovery to active push reception. It can provide information transparency, alarm optimization selection, improve efficiency, and achieve experience accumulation. It can improve the utilization rate of PLC alarms, reduce preventive maintenance time, increase non-productive efficiency on-duty personnel, reduce the time for pre-production production equipment status inspection, and achieve transparent and convenient production monitoring.

[0100] Fig.16 An exemplary configuration of a computing device 105 that can implement embodiments according to the present disclosure is shown. The computing device 105 is an example of a hardware device to which the above-mentioned aspects of the present disclosure can be applied. The computing device 105 can be any machine configured to perform processing and / or calculations. The computing device 105 can be, but is not limited to, a workstation, a server, a desktop computer, a laptop computer, a tablet computer, a personal data assistant (PDA), a smart phone, a vehicle-mounted computer, or a combination thereof.

[0101] like Fig.16As shown, computing device 105 may include one or more elements that may be connected or communicated with bus 502 via one or more interfaces. Bus 502 may include, but is not limited to, Industry Standard Architecture (ISA) bus, Micro Channel Architecture (MCA) bus, Enhanced ISA (EISA) bus, Video Electronics Standards Association (VESA) local bus, and Peripheral Component Interconnect (PCI) bus, etc. Computing device 105 may include, for example, one or more processors 504, one or more input devices 506, and one or more output devices 508. One or more processors 504 may be any kind of processor, and may include, but is not limited to, one or more general-purpose processors or special-purpose processors (such as special-purpose processing chips). Input device 506 may be any type of input device capable of inputting information to a computing device, and may include, but is not limited to, a mouse, a keyboard, a touch screen, a microphone, and / or a remote controller. Output device 508 may be any type of device capable of presenting information, and may include, but is not limited to, a display, a speaker, a video / audio output terminal, a vibrator, and / or a printer.

[0102] The computing device 105 may also include or be connected to a non-transitory storage device 514, which may be any non-transitory storage device that can implement data storage, and may include, but is not limited to, a disk drive, an optical storage device, a solid-state memory, a floppy disk, a flexible disk, a hard disk, a tape, or any other magnetic medium, a compressed disk or any other optical medium, a cache memory, and / or any other storage chip or module, and / or any other medium from which a computer can read data, instructions, and / or code. The computing device 105 may also include a random access memory (RAM) 510 and a read-only memory (ROM) 512. The ROM 512 may store programs, utilities, or processes to be executed in a non-volatile manner. The RAM 510 may provide volatile data storage and store instructions related to the operation of the computing device 105. The computing device 105 may also include a network / bus interface 516 coupled to a data link 518. The network / bus interface 516 may be any type of device or system capable of enabling communication with an external device and / or network, and may include but is not limited to a modem, a network card, an infrared communication device, a wireless communication device, and / or a chipset (such as a Bluetooth TM equipment, 1302.11 equipment, WiFi equipment, WiMax equipment, cellular communication facilities, etc.).

[0103] Various aspects, embodiments, implementations or features of the foregoing embodiments may be used alone or in any combination. Various aspects of the foregoing embodiments may be implemented by software, hardware or a combination of hardware and software.

[0104] For example, the foregoing embodiments may be embodied as computer readable code on a computer readable medium. A computer readable medium is any data storage device that can store data that can thereafter be read by a computer system. Examples of computer readable media include read-only memory, random access memory, CD-ROM, DVD, magnetic tape, hard drive, solid state drive, and optical data storage device. The computer readable medium may also be distributed in a network coupled computer system so that the computer readable code is stored and executed in a distributed manner.

[0105] For example, the aforementioned embodiments may be in the form of hardware circuits. The hardware circuits may include any combination of combinational logic circuits, clock storage devices (such as floppy disks, flip-flops, latches, etc.), finite state machines, memories such as static random access memories or embedded dynamic random access memories, custom designed circuits, programmable logic arrays, etc.

[0106] In one embodiment, a hardware circuit according to the present disclosure may be implemented by coding a circuit description in a hardware description language (HDL) such as Verilog or VHDL. The HDL description may be synthesized from a library of cells designed for a given integrated circuit manufacturing technology and may be modified for timing, power, and other reasons to obtain a final design database that may be transmitted to a factory to produce integrated circuits through a semiconductor manufacturing system. The semiconductor manufacturing system may produce integrated circuits by depositing semiconductor materials (e.g., on a wafer that may include a mask), removing materials, changing the shape of the deposited materials, modifying the materials (e.g., by doping materials or modifying dielectric constants using ultraviolet treatment), and the like. The integrated circuit may include transistors and may also include other circuit elements (e.g., passive elements such as capacitors, resistors, inductors, etc.) and interconnections between transistors and circuit elements. Some embodiments may implement multiple integrated circuits coupled together to implement the hardware circuit, and / or discrete elements may be used in some embodiments.

[0107] Although some specific embodiments of the present disclosure have been shown in detail by examples, it should be understood by those skilled in the art that the above examples are intended to be illustrative only and do not limit the scope of the present disclosure. It should be appreciated that some steps in the aforementioned method are not necessarily performed in the order shown in the figure, but they can be performed simultaneously, in different orders or in an overlapping manner. In addition, those skilled in the art can add some steps or omit some steps as needed. Some components in the aforementioned system are not necessarily arranged according to the diagram, and those skilled in the art can add some components or omit some components as needed. It should be understood by those skilled in the art that the above embodiments can be modified without departing from the scope and essence of the present disclosure. The scope of the present disclosure is defined by the attached claims.

Claims

1. A method for production monitoring, comprising: Acquiring fault information related to at least one production control device, each production control device being correspondingly assigned to at least one functional device; Obtaining a fault solution corresponding to the fault information; as well as The fault information and the fault solution corresponding to the fault information are sent to a terminal device.

2. The method according to claim 1, wherein: The step of obtaining a fault solution corresponding to the fault information includes: A fault solution corresponding to the fault information is acquired from a first database that pre-stores the fault solution corresponding to the fault information.

3. The method according to claim 1, further comprising: Determining whether the fault information belongs to a predetermined type; Wherein, when the fault information belongs to the predetermined type, a fault solution corresponding to the fault information is obtained; and The fault information and the fault solution corresponding to the fault information are sent to a terminal device.

4. The method according to claim 3, further comprising: storing the fault information determined to be of the predetermined type in a second database; The predetermined type of fault information is related to a fault that will cause the production line to stop operating.

5. The method according to claim 1, wherein: The fault information includes production control device identification data, functional equipment identification data and fault type data; The fault type data includes different types of fault states.

6. The method according to claim 1, wherein: Acquiring fault information related to at least one production control device includes: acquiring fault information related to a plurality of production control devices involved in the production operation of the main production line.

7. The method according to claim 1, wherein: Acquiring fault information related to at least one production control device includes: Periodically acquiring the fault information related to at least one production control device; wherein the fault information related to at least one production control device is periodically acquired during production and during non-production periods, The period for acquiring the fault information during the production period is shorter than the period for acquiring the fault information during the non-production period.

8. The method according to claim 1, further comprising: receiving an activation instruction, the activation instruction indicating that new fault information related to the at least one production control device is generated; The fault information related to the at least one production control device is acquired based on the activation instruction.

9. The method according to claim 1, wherein: The fault information includes a fault information description, wherein the fault information description includes a fault description in the form of text information, The fault solution includes a fault solution description including a fault solution description in the form of text information.

10. The method according to claim 9, further comprising: An associated terminal device group is determined based on the acquired fault information, wherein the determined associated terminal device group includes multiple terminal devices; wherein the fault information description and the fault solution description are provided to the multiple terminal devices included in the terminal device group.

11. The method according to claim 1, wherein: The terminal device includes a mobile terminal, and the step of sending the fault information and the fault solution corresponding to the fault information includes: sending the fault information and the fault solution corresponding to the fault information to the mobile terminal via a text message, an email, or an application.

12. A device for production monitoring, comprising: a memory having instructions stored therein; as well as A processor is configured to execute instructions stored on the memory to perform the method for production monitoring according to any one of claims 1 to 11.

13. A system for production monitoring, comprising: A plurality of production control devices, each of which is correspondingly assigned to at least one functional device in a production area; A server, wherein the server is configured as the apparatus according to claim 12; as well as A plurality of terminal devices, each terminal device is configured to communicate with the server and receive the fault information and the fault solution corresponding to the fault information.

14. A non-transitory computer-readable medium having computer-executable instructions stored thereon, which when executed by one or more computing devices cause the one or more computing devices to perform the method according to any one of claims 1-11.

Images