Production system control method, electronic device and storage medium

Abstract

The invention provides a control method of a production system, electronic equipment and a storage medium, and relates to the technical field of semiconductor sealing and testing systems. The production system comprises a plurality of process sites, and the control method of the production system comprises the steps that a technological process is edited according to operation of a first user, the technological process comprises a plurality of sub-processes, and each sub-process relates to at least one process site; in response to the fact that one process station in the process flow completes product processing, determining the next process station after the process station in the process flow is completed; and allowing the product to enter the next process station in response to the condition that the staying duration of the product at one process station meets the preset limiting condition.

Description

Production system control method, electronic device, and storage medium Technical Field

[0001] The present disclosure relates to the technical field of semiconductor packaging and testing systems, and in particular to a control method, electronic equipment, storage medium, and computer program product for a production system. Background Art

[0002] Process management controls the connections between production sites, ensuring that products can accurately find their way to the next site after completing production at one site. Furthermore, process management ensures that a site is capable of producing a product. In the semiconductor packaging and testing industry, process flow configuration for products is typically performed using spreadsheets. However, due to the large variety of products in the industry, each with its own unique process, configuring processes using spreadsheets can be complex and tedious.

[0003] Summary of the Invention

[0004] The present disclosure provides a control method for a production system, an electronic device, a storage medium, and a computer program product.

[0005] According to one aspect of the present disclosure, a method for controlling a production system is provided, wherein the production system includes a plurality of process sites, and the method includes:

[0006] Editing a process flow according to an operation of a first user, wherein the process flow includes a plurality of sub-flows, and each sub-flow involves at least one process site;

[0007] In response to a process station in the process flow completing processing of the product, determining a next process station after the process station in the process flow is completed; and

[0008] In response to the length of time a product stays at a process station meeting a predetermined restriction condition, the product is allowed to enter the next process station.

[0009] According to an embodiment of the present disclosure, editing includes at least one of the following: creating, modifying, removing, cloning, upgrading, setting a frozen state, and setting an activated state, wherein the frozen state indicates prohibiting editing or allowing editing, and the activated state indicates allowing use or prohibiting use.

[0010] According to an embodiment of the present disclosure, editing includes creating, and editing the process flow according to the operation of the first user includes:

[0011] determining a candidate sub-process selected by the first user from a plurality of candidate sub-processes as a sub-process of the process flow;

[0012] An execution order among the determined multiple sub-processes is determined according to the dragging operation of the first user to obtain a process flow, wherein the execution order is represented by the direction of the connecting line.

[0013] According to an embodiment of the present disclosure, determining a candidate sub-flow selected by a first user from a plurality of candidate sub-flows as a sub-flow of a process flow includes:

[0014] In response to the first user inputting basic information of the process flow, displaying a plurality of candidate sub-processes;

[0015] In response to the first user dragging at least one candidate sub-flow from the plurality of candidate sub-flows to the display area, the candidate sub-flow dragged to the display area is determined as a sub-flow of the process flow.

[0016] According to an embodiment of the present disclosure, determining a candidate sub-flow selected by a first user from a plurality of candidate sub-flows as a sub-flow of a process flow includes:

[0017] In response to the first user dragging a blank sub-process to the display area, displaying a plurality of candidate sub-processes;

[0018] The blank sub-process in the display area is replaced with a candidate sub-process selected by the user from multiple candidate sub-processes to obtain a sub-process of the process flow.

[0019] According to an embodiment of the present disclosure, editing includes modifying, and editing the process flow according to the operation of the first user includes:

[0020] In response to the first user selecting a process flow from a plurality of created process flows, displaying a plurality of sub-processes included in the process flow and connection lines between the plurality of sub-processes;

[0021] Sub-processes and connection lines are added to the displayed process flow according to a drag operation of the first user, and / or sub-processes and connection lines are removed from the displayed process flow according to a removal operation of the first user.

[0022] According to an embodiment of the present disclosure, in response to receiving a start editing instruction, editing of the process flow according to the operation of the first user begins; in response to receiving an end editing instruction, editing of the process flow according to the operation of the first user ends, wherein during the time period after receiving the start editing instruction and before receiving the end editing instruction, users other than the first user are prohibited from editing the process flow.

[0023] According to an embodiment of the present disclosure, the method further includes: after editing the process flow according to the operation of the first user, verifying at least one of the following in response to receiving a verification instruction:

[0024] Whether each sub-process is connected by at least one connection line;

[0025] Whether the path formed by each connecting line complies with the predetermined rules.

[0026] According to an embodiment of the present disclosure, each sub-process of the process flow includes a data model of at least one process site and a connection model between the process sites, wherein the data model of each process site includes basic information of the process site, and the two process sites corresponding to each connection model are the source process site and the target process site, respectively. The connection model includes source site information, target site information, and the conditions for process transfer from the source site to the target site.

[0027] According to an embodiment of the present disclosure, in response to a process station in a process flow completing processing of a product, determining the next process station in the process flow of the process station includes:

[0028] In the process flow, a process site that has completed product processing is used as the current process site. The target process node corresponding to the connection model with the current process site as the source process node is found as the downstream process site of the current process site.

[0029] The next process site of the current process site is determined from the downstream process sites according to the type of the connection model between the current process site and each downstream process site and the conditions included in the connection model.

[0030] According to an embodiment of the present disclosure, the method further includes: responding to a query request from a second user corresponding to a process site specified in the plurality of sites,

[0031] Determine the next process station in the process flow for the designated process station; and

[0032] The determined next process station is presented to the second user.

[0033] According to an embodiment of the present disclosure, in response to a stay time of a product at a process station meeting a predetermined restriction condition, allowing the product to enter the next process station includes one of the following:

[0034] If the dwell time is longer than the preset lower limit, the product is allowed to enter the next process station, otherwise it is prohibited to enter the next process station;

[0035] If the dwell time is less than the preset upper limit, the product is allowed to enter the next process station; otherwise, the product is prohibited from entering the next process station.

[0036] If the residence time is between the preset upper and lower limits, the product is allowed to enter the next process station; otherwise, the product is prohibited from entering the next process station.

[0037] According to an embodiment of the present disclosure, the above method further includes:

[0038] In response to a stay time of the product at a process site not meeting a predetermined restriction condition, issuing an alarm to a second user corresponding to a process site; and

[0039] In response to the duration of the alarm exceeding the preset alarm duration, the alarm is cancelled.

[0040] According to an embodiment of the present disclosure, the above method further includes:

[0041] The restriction information between any two adjacent process sites in the process flow is configured according to the input information of the first user, wherein the restriction information includes at least one of the following items: an upper limit value of the stay time, a lower limit value of the stay time, the type of the start time and the end time of the stay time, and the alarm duration, wherein the type of the start time and the end time includes the entry time or the exit time.

[0042] According to another aspect of the present disclosure, an electronic device is provided, including a memory and a processor, wherein the memory stores instructions executable by the processor, and when the instructions are executed by the processor, the processor executes the method described above.

[0043] According to another aspect of the present disclosure, a non-transitory computer-readable storage medium storing computer instructions is provided, wherein the computer instructions are used to enable the computer to execute and implement the method described above.

[0044] According to another aspect of the present disclosure, a computer program product is provided, comprising a computer program, which implements the method described above when executed by a processor.

[0045] It should be understood that the contents described in this section are not intended to identify the key or important features of the embodiments of the present disclosure, nor are they intended to limit the scope of the present disclosure. Other features of the present disclosure will become readily understood through the following description. BRIEF DESCRIPTION OF THE DRAWINGS

[0046] The accompanying drawings are provided to facilitate a better understanding of the present invention and do not constitute a limitation of the present disclosure.

[0047] FIG1 is a flow chart of a control method for a production system according to an embodiment of the present disclosure;

[0048] FIG2 is a schematic diagram of an operation interface for creating a process site according to an embodiment of the present disclosure;

[0049] FIG3 is a schematic diagram of an operation interface for creating a process flow according to an embodiment of the present disclosure;

[0050] FIG4 is a flow chart of a process flow editing method according to an embodiment of the present disclosure;

[0051] 5 is a schematic diagram of an operation interface for selecting a candidate sub-process from multiple candidate sub-processes according to an embodiment of the present disclosure;

[0052] 6 is a schematic diagram of an operation interface for selecting a candidate sub-process from multiple candidate sub-processes according to another embodiment of the present disclosure;

[0053] FIG7 is a flowchart of a method for determining a next process site according to an embodiment of the present disclosure;

[0054] FIG8 is a flowchart of a method for determining a next process site according to another embodiment of the present disclosure;

[0055] FIG9 is a schematic diagram of a configuration interface for restriction conditions according to an embodiment of the present disclosure;

[0056] FIG10 is a flow chart of a process flow verification method according to an embodiment of the present disclosure;

[0057] FIG11 is an architectural diagram of an operation interaction interface for editing a process flow according to an embodiment of the present disclosure;

[0058] FIG12 is a diagram of a business function architecture of a production system according to an embodiment of the present disclosure;

[0059] FIG13 is a system technical architecture diagram of a production system according to an embodiment of the present disclosure;

[0060] 14A and 14B are application architecture diagrams of a production system according to an embodiment of the present disclosure; and

[0061] FIG15 is a block diagram of an electronic device suitable for implementing a control method for a production system according to an embodiment of the present disclosure. DETAILED DESCRIPTION

[0062] In order to make the purpose, technical solutions and advantages of the embodiments of the present disclosure clearer, the technical solutions in the embodiments of the present disclosure will be clearly and completely described below in conjunction with the drawings in the embodiments of the present disclosure. Obviously, the described embodiments are part of the embodiments of the present disclosure, not all of them. Based on the described embodiments of the present disclosure, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present disclosure. It should be noted that throughout the drawings, the same elements are represented by the same or similar figure marks. In the following description, some specific embodiments are only for descriptive purposes and should not be understood as any limitation to the present disclosure, but are only examples of the embodiments of the present disclosure. Conventional structures or configurations will be omitted when they may cause confusion in the understanding of the present disclosure. It should be noted that the shapes and sizes of the components in the figures do not reflect the actual size and proportion, but only illustrate the contents of the embodiments of the present disclosure.

[0063] Unless otherwise defined, technical or scientific terms used in the embodiments of the present disclosure shall have the same general meaning as those skilled in the art. The terms "first," "second," and similar terms used in the embodiments of the present disclosure do not denote any order, quantity, or importance, but are merely used to distinguish different components.

[0064] FIG1 is a flowchart of a method for controlling a production system according to an embodiment of the present disclosure.

[0065] A production system may include multiple process stations, each of which may include specific processing steps for a product in a production line. A product may pass through multiple process stations throughout the entire production process, and the multiple process stations that the product passes through during production form the product's process flow. The production system control method may include operations S110 to S130 as shown in FIG1 .

[0066] In operation S110 , a process flow is edited according to an operation of a first user, wherein the process flow includes a plurality of sub-flows, and each sub-flow involves at least one process site.

[0067] According to an embodiment of the present disclosure, it should be noted that a user forms a data model of a process site by editing the basic information of the process site. A sub-process may include a data model of at least one process site and an association relationship between the data models. For example, after constructing the data models of each process site, an association relationship between the data models can be established based on the operation of the first user to obtain a sub-process. In some embodiments, the data model of the process site can be displayed in the form of a graphic, such as a rectangular box or other shaped box containing process site information (e.g., the ID of the process site). The first user connects the graphics of the process site with connecting lines in the operation interface, and the computer establishes an association relationship between the data models of the process site based on the first user's operation of adding connecting lines, thereby forming a sub-process. Then, in a similar manner, the first user adds connecting lines between the graphics representing the sub-process in the operation interface, and the computer establishes an association relationship between the data models of the sub-process based on the first user's operation of adding connecting lines, thereby forming a process flow. By establishing a data model and allowing the user to establish an association relationship between the data models by dragging and dropping, the user can edit the process flow in an intuitive way without having to search and set values ​​in a complex data table, thereby improving the editing efficiency of the process flow.

[0068] According to an embodiment of the present disclosure, editing a process flow may include, for example, creating a process site, modifying a process site, removing a process site, cloning a process site, upgrading a process site, setting the frozen state of a process site, and setting the activated state of a process site. Editing a process flow may also include creating a sub-flow, modifying a sub-flow, removing a sub-flow, cloning a sub-flow, upgrading a sub-flow, setting the frozen state of a sub-flow, and setting the activated state of a sub-flow.

[0069] According to an embodiment of the present disclosure, editing a process flow based on an operation by a first user may, for example, include the first user clicking to enter an operation interface for editing the process flow and then clicking a corresponding edit button in the operation interface to edit the process flow. Specifically, for example, the first user clicks an edit button for creating a process site on the operation interface for editing the process flow, and the operation interface displays basic information for the process site that needs to be filled in. After the first user fills in the basic information for the process site, the process site is created.

[0070] In operation S120 , in response to a process station in a process flow completing processing of a product, a next process station after the completion of the process station in the process flow is determined.

[0071] According to embodiments of the present disclosure, during the manufacturing process, products are processed sequentially according to the processing order of each process station in the process flow. When a product is processed at a process station, the next process station is determined based on the processing order in the process flow. For example, in one embodiment, the process flow of product A includes process stations 1, 2, 3, and 4, which are connected in sequence. After product A is processed at process station 2, the next process station is determined to be process station 3 according to product A's process flow.

[0072] In operation S130 , in response to the length of time the product stays at a process station meeting a predetermined restriction condition, the product is allowed to enter the next process station.

[0073] According to an embodiment of the present disclosure, the dwell time may be the absolute value of the difference between the time a product enters a process station and the time a product leaves a process station immediately after the process station, or the absolute value of the difference between the time a product leaves a process station and the time a product leaves a process station immediately after the process station. In some embodiments, the dwell time may also include the absolute value of the difference between the time a product enters a process station and the time a product leaves a process station.

[0074] For example, if product B enters process station 1 at time T1 and enters process station 2 at time T2, the duration of product B's stay at process station 1 can be the absolute value of the difference between T2 and T1. For another example, if product C exits process station 1 at time T3 and exits process station 2 at time T4, the duration of product C's stay at process station 2 can be the absolute value of the difference between T4 and T3. For another example, if product D enters process station 1 at time T5 and exits process station 1 at time T6, the duration of product D's stay at process station 1 can be the absolute value of the difference between T6 and T5.

[0075] According to embodiments of the present disclosure, in some embodiments, the restriction condition includes but is not limited to a time limit, which may be less than an upper limit, greater than a lower limit, or between an upper limit and a lower limit.

[0076] According to the embodiments of the present disclosure, by editing the process flow of each product based on the first user's operation, the process flow can be visually configured, simplifying the process flow configuration process and reducing the difficulty of process flow configuration. After a process station in the process flow completes the processing of a product, the next station in the process flow can be logically determined based on the process flow. In addition, by determining whether the length of time a product stays at a process station meets the predetermined time limit, it can only move on to the next process station if the length of time meets the predetermined time limit, which helps to ensure the processing quality of the product at the current process station.

[0077] According to an embodiment of the present disclosure, editing may include at least one of the following: creating, modifying, removing, cloning, upgrading, setting a frozen state, and setting an activated state, where the frozen state indicates prohibiting editing or allowing editing, and the activated state indicates allowing use or prohibiting use.

[0078] According to an embodiment of the present disclosure, creation may include, for example, creating a process site, which may include filling in basic information of the process site. The basic information of the process site may include, for example, the site name, site version, site activation status, site freeze status, basic information of the operator, etc.

[0079] FIG2 is a schematic diagram of an operation interface for creating a process site according to an embodiment of the present disclosure.

[0080] As shown in Figure 2, the first user clicks the "Create" button, and the interface displays the basic information of the process site that needs to be filled in, such as the factory name, process site name, site description, editing status, creation time, end editing time, and end editing user. After filling in the corresponding information in the information column, the first user clicks the "Confirm" button to complete the creation of the process site.

[0081] According to an embodiment of the present disclosure, creation may also include, for example, creating a process flow, which may include filling in basic information about the process flow. The basic information about the process flow may include factory name, process flow name, process flow version, activation status, freeze status, process flow type, basic operator information, etc.

[0082] FIG3 is a schematic diagram of an operation interface for creating a process flow according to an embodiment of the present disclosure.

[0083] As shown in Figure 3, the first user clicks the "Create" button. The interface displays the basic process information that needs to be filled in, such as the factory name, process name, process version, activation status, freeze status, process type, and creation time. After filling in the required information in the information fields, the first user clicks the "Confirm" button to complete the process creation.

[0084] According to an embodiment of the present disclosure, the modification may include, for example, modifying the information of the process site. The user clicks the "Modify" button to modify the information of the process site as shown in Figure 2, and clicks the "Confirm" button after the modification is completed. It should be noted that a process site in a frozen state cannot be modified, and only a process site in an unfrozen state can be modified. The modification may also include, for example, modifying the information of the process flow. The user clicks the "Modify" button to modify the information of the process flow as shown in Figure 3, and clicks the "Confirm" button after the modification is completed. It should be noted that a process site or process flow in a frozen state cannot be modified, and only a process site or process flow in an unfrozen state can be modified.

[0085] According to an embodiment of the present disclosure, removing may include, for example, clearing a selected process site and clearing a selected process flow.

[0086] According to an embodiment of the present disclosure, cloning may include, for example, cloning a new process site based on an existing process site. Specific operations may include, for example, selecting a row of process sites, then right-clicking the "Clone" button, at which point a name naming window will pop up, and then the name of the cloned process site will be entered in the name naming window, and then clicking "Confirm" to obtain a new process site. Cloning may also include cloning a new process flow based on an existing process flow. Specific operations may include, for example, selecting a row of process flows, then right-clicking the "Clone" button, at which point a name naming window will pop up, and then the name of the cloned process flow will be entered in the name naming window, and then clicking "Confirm" to obtain a new process flow.

[0087] According to embodiments of the present disclosure, upgrading a version may, for example, include upgrading an existing process site version by one version. Specifically, for example, selecting a row of process sites and right-clicking a "New Version" button will automatically upgrade the version. Upgrading a version may also include upgrading an existing process flow version by one version. Specifically, for example, selecting a row of process flows and right-clicking a "New Version" button will automatically upgrade the version.

[0088] According to an embodiment of the present disclosure, setting a frozen state may include, for example, temporarily freezing a process site, and preventing it from being modified or subjected to other operations. Specific operations may include, for example, selecting a row of unfrozen process sites, such as process site A, right-clicking the "Freeze" button, and then clicking "Yes", so that process site A changes from an unfrozen state to a frozen state. Setting a frozen state may also include, for example, temporarily freezing a process flow, and preventing it from being modified or subjected to other operations. Specific operations may include, for example, selecting a row of unfrozen process flows, such as process flow 1, right-clicking the "Freeze" button, and then clicking "Yes", so that process flow 1 changes from an unfrozen state to a frozen state.

[0089] According to an embodiment of the present disclosure, setting the activation state may include, for example, reactivating a frozen process site. Specific operations may include, for example, selecting a row of inactivated process sites, such as process site B, right-clicking the "Activate" button, and then clicking "Yes," whereupon process site B changes from an inactivated state to an activated state. Setting the activation state may also include, for example, reactivating a frozen process flow. Specific operations may include, for example, selecting a row of inactivated process flows, such as process flow 2, right-clicking the "Activate" button, and then clicking "Yes," whereupon process flow 2 changes from an inactivated state to an activated state.

[0090] According to an embodiment of the present disclosure, the control method of the production system further includes a query function. The query function can filter information and query historical information by selecting information such as factory name, process site type, process site activation status, process site freeze status, and process site name.

[0091] According to the embodiments of the present disclosure, the control method of the production system provides version control, cloning, activation and other operations for process sites and process flows, which simplifies the problem of repeated production processes as a whole. At the same time, version control controls processes more securely and records historical processes, while also increasing the flexibility of process configuration, so that each process site can have its own version.

[0092] According to an embodiment of the present disclosure, editing includes creating. Editing the process flow based on an operation by a first user includes: determining a candidate sub-flow selected by the first user from multiple candidate sub-flows as a sub-flow of the process flow; and determining an execution order among the multiple sub-flows based on a drag operation by the first user to obtain the process flow, wherein the execution order is represented by the direction of a connecting line.

[0093] FIG4 is a flowchart of a process flow editing method according to an embodiment of the present disclosure.

[0094] As shown in FIG. 4 , the process flow editing method of this embodiment includes operations S410 to S480 .

[0095] In operation S410, in response to the editing operation of the first user, the type of the editing operation is determined. If the type of the editing operation is a creation operation, operations S420 to S440 or operations S450 to S460 are performed; if the type of the editing operation is a modification operation, operations S470 to S480 are performed.

[0096] In operation S420 , in response to the first user inputting basic information of the process flow, a plurality of candidate sub-flows are displayed.

[0097] In operation S430 , in response to the first user dragging at least one candidate sub-flow from the plurality of candidate sub-flows to the display area, the candidate sub-flow dragged to the display area is determined as a sub-flow of the process flow.

[0098] In operation S440, the execution order of the multiple sub-processes determined by the first user's drag operation is determined to obtain a process flow, where the execution order is represented by the direction of the connecting lines. By adding connecting lines between the sub-processes, an association relationship is established between the sub-process data models, thereby determining the execution order of each sub-process and obtaining a process flow.

[0099] In operation S450 , in response to the first user dragging a blank sub-process to the display area, a plurality of candidate sub-processes are displayed.

[0100] In operation S460 , the blank sub-flow in the display area is replaced with a candidate sub-flow selected by the user from the plurality of candidate sub-flows to obtain a sub-flow of the process flow.

[0101] In operation S470 , in response to the first user selecting a process flow from a plurality of already created process flows, a plurality of sub-flows included in the process flow and connection lines between the plurality of sub-flows are displayed.

[0102] In operation S480 , a sub-process and a connection line are added to the displayed process flow according to a drag operation of the first user, and / or a sub-process and a connection line are removed from the displayed process flow according to a removal operation of the first user.

[0103] According to an embodiment of the present disclosure, the basic information of the process flow may include, for example, the factory name, process name, process type, process version, activation status, freeze status, basic information of the operator, etc.

[0104] FIG5 is a schematic diagram of an operation interface for selecting a candidate sub-process from multiple candidate sub-processes according to an embodiment of the present disclosure.

[0105] As shown in Figure 5, the user interface for selecting a candidate sub-process from multiple candidate sub-processes may include a basic information area on the left side of the interface, a display area in the middle, and an identification area on the right side. By selecting or filling in the factory name, process type, and process detail type in the basic information area, the user will be presented with the corresponding main process, such as process 1, and multiple candidate sub-processes corresponding to the main process, such as sub-process 2 and sub-process 3. The user can select either sub-process 2 or sub-process 3 and drag it to the display area of ​​the interface. The candidate sub-process, such as sub-process 2, that has been dragged to the display area will be determined as a sub-process of the process flow.

[0106] According to embodiments of the present disclosure, the user interface can also preview the designed process flow. Specifically, the user interface can select or fill in the factory name, process flow type, and process detail type, then select a selected main flow to display in the display area. If the main flow displayed in the display area is not frozen and inactive, it can be edited; otherwise, it cannot be edited.

[0107] FIG6 is a schematic diagram of an operation interface for selecting a candidate sub-process from multiple candidate sub-processes according to another embodiment of the present disclosure.

[0108] As shown in Figure 6, the interface for selecting a candidate sub-process from multiple candidate sub-processes may include a basic information area on the left side of the interface, a display area in the middle, and an identification area on the right side. The user selects or fills in the factory name, process type, and process detail type in the basic information area to display the corresponding main process (e.g., process 1), multiple candidate sub-processes (e.g., A200, A300), and multiple repair processes (e.g., B100, B200). The user can select a sub-process from the multiple candidate sub-processes displayed in the basic information area and drag it to the display area to complete the sub-process selection. The user can also drag a blank sub-process (e.g., the repair process) in the identification area to the display area. A list of candidate repair process names (e.g., B100, B200, etc.) will pop up near the repair process. The user can select a name for the blank sub-process from the list and determine the repair process as a sub-process of the process flow.

[0109] According to an embodiment of the present disclosure, determining a candidate sub-process selected by a first user from multiple candidate sub-processes as a sub-process of a process flow can be implemented in the above-mentioned different ways. By providing multiple drag-and-drop methods, it is convenient for users to perform different operations according to different needs, thereby increasing the flexibility of the process flow creation process.

[0110] As shown in Figures 5 and 6, once all sub-processes in the process flow have been determined, the user can connect the sub-processes from the start node to the end node, adding connecting lines between the sub-processes to indicate the execution order of the sub-processes. This connection operation can be performed manually, but other connection methods are also possible. It should be noted that the start node S and end node E in Figures 5 and 6 have no actual physical meaning and only identify the sub-processes that serve as the start and end nodes in the process flow.

[0111] According to an embodiment of the present disclosure, each sub-process of a process flow includes a data model of at least one process site and a connection model between the process sites. The data model of each process site includes basic information about the process site, and the two process sites corresponding to each connection model are a source process site and a target process site. The connection model includes source site information, target site information, and the conditions for process transfer from the source site to the target site.

[0112] According to an embodiment of the present disclosure, after creating basic information for a process site using the above method, a site component is added to generate a data model corresponding to the process site, and the data model is saved to a database. After creating a process flow using the above method, a connection component can also be added to generate a connection model representing the connection data between the process sites, and the connection model is saved to a database.

[0113] According to an embodiment of the present disclosure, source site information may include, for example, the source site's name and version information. Target site information may include, for example, the target site's name and version information. Conditions for process transfer from the source site to the target site may include, for example, the duration of stay and the number of products processed.

[0114] FIG7 is a flowchart of a method for determining a next process site according to an embodiment of the present disclosure.

[0115] As shown in FIG. 7 , the determination method of this embodiment includes operation S710 and operation S720 .

[0116] In operation S710, in the process flow, a process site that has completed product processing is used as the current process site, and a target process node corresponding to a connection model with the current process site as the source process node is searched as the downstream process site of the current process site.

[0117] In operation S720 , a next process site of the current process site is determined from the downstream process sites according to the type of the connection model between the current process site and the downstream process sites and the conditions included in the connection model.

[0118] According to an embodiment of the present disclosure, during the product processing process, in addition to automatically finding the next process site for product circulation according to the process flow, it is also possible to respond to the query request of the second user corresponding to the specified process site among multiple sites, determine the next process site of the specified process site in the process flow; and display the determined next process site to the second user.

[0119] According to an embodiment of the present disclosure, the second user can specify a process site through the client and query the next process site of the process site in the process flow, and display it to the second user through the client, so that production personnel can query the next process site and transfer the product to the next process site for processing.

[0120] FIG8 is a flowchart of a method for determining a next process site according to another embodiment of the present disclosure.

[0121] As shown in Figure 8, first determine all downstream sites connected to the current site based on the data model information of the current site; then, for each downstream site, query the connection line information through the process flow information in the product, and determine the next site based on the type and conditions of different connection lines. If the site obtained is not an ordinary site, continue the iterative loop until a site is found; then judge based on whether the conditions are met. If so, go to the site reached by the conditional line; if not, go to the site reached by the ordinary line or the repair line.

[0122] According to an embodiment of the present disclosure, after the next process station is determined, it is necessary to determine whether the product's residence time at the process station meets predetermined restrictions. If the residence time meets the predetermined restrictions, the product is allowed to proceed to the next process station; if the residence time does not meet the predetermined restrictions, the product is prohibited from proceeding to the next process station.

[0123] According to embodiments of the present disclosure, the constraint condition may include a time limit. For example, the time limit may include being greater than a preset lower limit, less than a preset upper limit, or between a preset upper limit and a preset lower limit. Depending on the type of the predetermined time limit, different methods may be used to determine whether the length of time a product remains at a process station complies with the predetermined time limit.

[0124] In one embodiment, the predetermined time limit adopts a preset lower limit value, and judging whether the length of time a product stays at a process station meets the predetermined time limit based on the predetermined time limit may include: if the length of time stays longer than the preset lower limit value, allowing the product to enter the next process station, otherwise prohibiting the product from entering the next process station.

[0125] In another embodiment, the predetermined time limit adopts a preset upper limit value, and judging whether the length of time a product stays at a process station meets the predetermined time limit based on the predetermined time limit may include: if the length of time is less than the preset upper limit value, the product is allowed to enter the next process station, otherwise the product is prohibited from entering the next process station.

[0126] In another embodiment, the predetermined time limit is between a preset upper limit and a preset lower limit, and judging whether the length of time a product stays at a process station meets the predetermined time limit based on the predetermined time limit may include: if the length of time is between the preset upper limit and the lower limit, the product is allowed to enter the next process station, otherwise the product is prohibited from entering the next process station.

[0127] According to an embodiment of the present disclosure, by setting restriction conditions, it is possible to determine whether the length of time a product stays at a process site meets the predetermined restriction conditions, and intercept products that do not meet the restriction conditions to avoid production problems.

[0128] According to an embodiment of the present disclosure, the above method also includes: configuring restriction information between any two adjacent process sites in the process flow according to the input information of the first user, wherein the restriction information includes at least one of the following items: an upper limit value of the stay time, a lower limit value of the stay time, the type of the start time and the end time of the stay time, and the alarm duration, wherein the type of the start time and the end time includes the entry time or the exit time.

[0129] FIG9 is a schematic diagram of a configuration interface for restriction information according to an embodiment of the present disclosure.

[0130] As shown in Figure 9, after entering the restriction information configuration interface, the user can select or enter the process name and process version in the left area of ​​the configuration interface. The sub-processes and process sites corresponding to the process name and process version will be displayed on the configuration interface. To configure restriction information, the user can click the "Create" button in the right area of ​​the configuration interface to display the required information. Restrictions can include time limits. In this case, the required information may include the start event, end event, process name, site name, time limit type, alarm duration, time limit length, alarm name, time limit status, etc. After completing the information, the user clicks the "Confirm" button to complete the configuration of the time limit for one of the process sites. Process sites with time limits configured are displayed in the time limit list in the center area of ​​the configuration interface. To modify the time limit of a process site, select a row in the time limit list and click the "Modify" button in the right area of ​​the configuration interface to modify the time limit information for that process site. To remove a process site, select a row in the time limit list and click the "Remove" button in the right area of ​​the configuration interface to remove the process site from the time limit list.

[0131] According to an embodiment of the present disclosure, the above method also includes: in response to the length of time a product stays at a process site not meeting a predetermined restriction condition, issuing an alarm to a second user corresponding to a process site; and in response to the duration of the alarm exceeding a preset alarm duration, canceling the alarm.

[0132] As shown in Figure 9, the preset alarm duration can also be configured in the configuration interface. By issuing an alarm to the second user, the second user is prompted to promptly handle the product that does not meet the predetermined restriction conditions to ensure that the product can be processed smoothly.

[0133] According to an embodiment of the present disclosure, the operation interface shown in Figures 5 and 6 may further include a "Start Editing" button and a "End Editing" button. Before editing, the first user can click the "Start Editing" button to edit the process flow. During this period, users other than the first user are prohibited from editing the process flow. After the first user completes editing, clicking the "End Editing" button indicates that the first user has ended editing the process flow, and other users can now edit the process flow.

[0134] According to an embodiment of the present disclosure, by setting "Start Editing" and "End Editing" buttons, only one user is allowed to edit the process flow in the same time period, avoiding the situation where multiple users editing at the same time cause process errors.

[0135] According to an embodiment of the present disclosure, the operation interface shown in FIG. 5 and FIG. 6 may further include a verify and save button. After the user completes editing the process flow, the user may click the verify and save button to verify the process flow.

[0136] According to an embodiment of the present disclosure, the process design may further include a query function. Right-click in the display area of ​​the operation interface, and then click "Display Data" to enter the process query interface.

[0137] FIG10 is a flow chart of a process flow verification method according to an embodiment of the present disclosure.

[0138] As shown in FIG. 10 , the process flow verification method of this embodiment includes operations S1010 to S1040 .

[0139] In operation S1010 , in response to receiving a start editing instruction, the process flow starts to be edited according to an operation of a first user.

[0140] In operation S1020, in response to receiving the verification instruction, verify that each sub-process is connected with at least one connection line. If it is determined that each sub-process is connected with at least one connection line, operation S1030 is performed; if it is determined that there is no connection line between the sub-processes, operation S1010 is performed.

[0141] In operation S1030, it is checked whether the paths formed by the connecting lines meet the predetermined rules. If it is determined that the paths formed by the connecting lines meet the predetermined rules, operation S1040 is performed; if it is determined that there are paths formed by the connecting lines that do not meet the predetermined rules, operation S1010 is performed.

[0142] According to an embodiment of the present disclosure, the predetermined rules may include, for example, that the blue line requires a single path from the starting site to the ending site and cannot be forked; the red line is a conditional line, which is used to determine whether the attribute or data meets the conditions. If so, the red line is followed. The red line can be forked, and the process site that is branched out must have a green line to other process sites or return to the original process site.

[0143] In operation S1040 , in response to receiving the end editing instruction, editing of the process flow according to the operation of the first user is ended.

[0144] According to an embodiment of the present disclosure, the production system is a production system for semiconductor packaging and testing. The production system can adopt the MES manufacturing execution system. MES is the abbreviation of Manufacturing Execution System. MES is a production information management system for the execution layer of the workshop of a manufacturing enterprise.

[0145] FIG11 is an architectural diagram of an operation interaction interface for editing a process flow according to an embodiment of the present disclosure.

[0146] As shown in Figure 11, the interactive operation interface 1100 of this embodiment includes a basic information construction module 1110 and a process creation module 1120. The basic information construction module 1110 includes a site configuration 1111 and a process configuration 1112. The site configuration 1111 mainly configures the basic information of the process site. By maintaining the basic information of the process site in the basic information construction module 1110, it represents the processing site in the actual processing process. The process configuration 1112 mainly configures the basic information of the process flow. The basic information of the process site and the basic information of the process flow configured in the basic information construction module 1110 can be saved in the basic table of the database. The process creation module 1120 includes a main process creation 1121 and a sub-process creation 1122. The process creation module 1120 mainly associates the process site and the process flow in a visual manner by dragging and dropping connections. The direction of the connection line between the process sites represents the actual processing site name and processing sequence of the product. The main process and sub-process created in the process creation module 1120 can be saved in the process table in the database. Users can calculate the next process site information of the product by querying the relevant information of process sites and process flows stored in the database, thereby determining which site the product should be processed at in actual production.

[0147] FIG12 is a diagram of a business functional architecture of a production system according to an embodiment of the present disclosure.

[0148] As shown in Figure 12, the production system 1200 according to an embodiment of the present disclosure includes a basic data module 1201, a process flow management module 1202, a production plan module 1203, a work-in-progress management module 1204, a batch management module 1205, an engineering management module 1206, a process menu management module 1207, an equipment management module 1208, a machine limit management module 1209, a carrier management module 1210, a material management module 1211, a fixture management module 1212, and a packaging management module 1213.

[0149] The Basic Data Module 1201 provides basic system data modeling for the MES system, including plant modeling, equipment modeling, system status modeling, package modeling, user permission modeling, recipe basic data modeling, material basic data modeling, process step flow modeling, strategy modeling, data collection basic data modeling, and alarm basic data modeling. The Basic Data Module 1201 is a unified basic data model platform. As a standard framework, it provides the basic common functions required by customers and offers a series of customizable extensions, such as unified naming conventions, unified data enumeration types, and unified business management, facilitating the rapid development of applications. Furthermore, the Basic Data Module 1201 standardizes object definitions across multiple applications, supporting multiple languages ​​and units. With many elements customized, the system becomes more flexible and scalable. Specifically, the plant modeling supports the maintenance of plant basic data, multi-plant models, and the creation of factory zones. The equipment modeling supports the creation of equipment master data and the maintenance of equipment port data. The system status modeling supports the maintenance of batch status, equipment status, material status, carrier status, and fixture status. Package modeling is used to maintain package-related attribute data and centrally manage different package types. User permission modeling supports the creation and maintenance of users, user groups, and user roles, as well as password verification for user menus and user interface interfaces. Recipe basic data modeling supports the creation and maintenance of process menu data and the maintenance of recipe-equipment data relationships. Material basic data modeling supports the creation and maintenance of material basic data. Process step flow modeling supports the creation and maintenance of basic data for steps, processes, sections, and procedures, as well as visual interface editing of procedures, the creation and maintenance of branch processes, and the creation and maintenance of rework processes. Strategy modeling supports product-level, process-level, and step-level flow modeling. Based on different policy configurations, the system selects different equipment and recipes for business operations during actual production. Data collection basic data modeling supports the creation and maintenance of data collection details and the maintenance of data collection rules. Alarm basic data modeling supports the maintenance of alarm system information, the management and maintenance of alarm trigger conditions, and the management and maintenance of subsequent actions triggered by alarms.

[0150] The process management module 1202 is a new set of process management specifications provided by the MES system. The process management module 1202 allows users to define products and their corresponding process flows, including each step type and related process control strategies.

[0151] In terms of version control, the MES system provides a complete version control mechanism. All active in-progress processes within the MES system must strictly adhere to this version control system to prevent production accidents caused by errors in production process data. Regarding process definition, the process flow management module 1202 supports multiple path selection and can automatically select a path based on pre-set conditions during on-site operations. The process flow management module 1202 also supports the control of various product process rules, enabling different process controls based on different product and process conditions. Conditions can be broken down into various levels, such as work step, process, process, product, and batch.

[0152] Process step flow modeling supports the creation and maintenance of basic data of work steps, processes, sections, and flows, supports visual interface editing of flows, supports the creation and maintenance of branch flows, and supports the creation and maintenance of rework flows.

[0153] Product process configuration can configure different process flows according to different products. Different recipes and equipment can be selected according to different strategies for the same product and process.

[0154] The production planning management module 1203 manages the production plan orders and work orders of the MES system. Users can create new production plan orders in the MES system and then create new work orders based on the planned orders. Users can also set the priority of corresponding planned orders and work orders in the MES system, as well as related information such as the planned time for the corresponding planned orders and work orders, to facilitate tracking of order completion during the production and manufacturing process. Planned orders can create and maintain planned orders for different factories, and can control priority and final delivery time. Work orders can create different work orders based on different planned orders, and can specify special attributes on the work orders such as priority, owner, and process notes.

[0155] The product management module 1204 is used for product processing management, guiding operators to process products according to pre-set process requirements, and tracking and recording processing information in detail. Among them, the most important operation management function of the product management module 1204 is to allow multiple batches to be processed simultaneously and provide historical traceability of batches. In addition to the commonly used batch creation, entry and exit, other functions of the product management module 1204 include: batching, batch combination, pause, release, skipping, future actions, rework within the station, rework outside the station, batch scrapping, batch cancellation and scrapping, batch-specified carriers, special business batch exit, batch exit, multi-core bonding entry, integrated editing and testing entry and exit, etc.

[0156] The main functions of the batch management module 1205 include batch division, batch merging, batch scrapping, batch cancellation and scrapping, carrier designation, batch suspension, batch cancellation and suspension, etc.

[0157] The engineering management module 1206 manages engineering-related businesses within the MES system. The functions of this module include work permit management, QTime management, BOM management, process card management, and batch reservation. Among them, work permit management provides users with information to configure work permit related information and set the expiration time. It is used to control whether the system user has the corresponding authority when operating the OIC (Operator Interface Client) system. QTime management is used to set QTime rules and perform rule control when the batch passes the station. BOM management supports BOM maintenance and is used to control the material verification of equipment materials. Process card management supports the creation and maintenance of process cards within the system. Production can generate corresponding process card information based on different process cards for production circulation paper vouchers. Batch reservation supports batch reservation production function.

[0158] The process menu management module 1207 contains process menu information for all process flows and can create and update process menus. The setup and use of process menus are version-controlled, including functions such as creation, activation, freezing, and cancellation. The process menu management module 1207 supports the configuration of both logical and actual process menus, such as processing parameters. It can also automatically select process menus based on process conditions and previous-layer measurement results. The process menu management module 1207 also supports the maintenance of relationships between equipment and process menus.

[0159] The equipment management module 1208 defines basic equipment information, provides the creation and tracking management of equipment status models, and supports equipment permission management, equipment inspection, maintenance, repair reporting, and repair process management. Equipment basic data maintenance is used to maintain basic equipment data. Equipment inspection supports the maintenance of equipment inspection items and supports regular equipment inspection control. Equipment maintenance supports the setting of equipment maintenance and maintenance cycles and controls equipment maintenance. Equipment repair reporting supports equipment repair reporting. Equipment maintenance supports tracking of equipment maintenance processes. The equipment ledger supports querying equipment-related archival data.

[0160] The machine limit management module 1209 provides the control function of the MES machine limit. The machine limit management module 1209 supports setting limit conditions in different scenarios to control whether the batch can support production.

[0161] According to the equipment settings: You can set the rules for a certain scenario according to the specific situation of the equipment. When a batch encounters this rule during production, it cannot be produced through the machine limit.

[0162] According to product settings: You can set rules for a certain scenario based on the specific situation of the product. When a batch encounters this rule during production, it cannot be produced through this machine limit.

[0163] Set according to the process flow: You can set rules for a certain scenario based on the specific circumstances of the process flow. When a batch encounters this rule during production, it cannot be produced through this machine limit.

[0164] Positive and negative item settings: You can set positive rules, for example, production is allowed only under this rule; negative rules, production is not allowed under this condition.

[0165] The vehicle management module 1210 supports the management of vehicle-related services, including vehicle creation, vehicle cleaning, vehicle binding, vehicle unbinding, vehicle pausing, and vehicle release. The vehicle management module 1210 also supports vehicle lifespan management, vehicle usage count management, and vehicle type management. Vehicle creation is used to create vehicle data. Vehicle cleaning is used to clean new vehicles and used vehicles. Vehicle binding supports the binding of vehicle data and batches. Vehicle unbinding supports the unbinding of vehicle and batch data. Vehicle pausing controls the suspension of a vehicle. Vehicle release resumes a paused vehicle.

[0166] The Materials Management Module 1211 manages raw materials, semi-finished products, and product data, as well as warehouse, storage, and shelf management. This module can be used independently or as an extension of the Warehouse Management Module within ERP, implementing interface functions or providing independent management and control. The Materials Management Module 1211 supports common warehouse management functions: material maintenance, material receipt, material loading and unloading, finished product warehousing, finished product shipment, returns, and transfers.

[0167] The fixture management module 1212 supports the management of fixture-related operations, including fixture creation, fixture cleaning, fixture loading, fixture unloading, fixture suspension, fixture release, fixture storage, fixture removal, fixture transfer, fixture scrapping, fixture cancellation and scrapping, and fixture withdrawal from the production line. The fixture management module 1212 also supports fixture lifespan management and usage count management, as well as fixture type management. Among them, fixture creation is used to create fixture data. Fixture cleaning supports fixture cleaning operations. Fixture loading supports binding fixtures to equipment. Fixture unloading supports unbinding fixtures from equipment. Fixture suspension supports fixture suspension operations. Fixture release supports fixture release operations. Fixture storage supports fixture storage operations. Fixture removal supports fixture removal operations. Fixture transfer supports fixture replacement operations. Fixture scrapping supports fixture scrapping. Fixture cancellation supports the restoration of scrapped fixtures. The fixture return line and side warehouse support the fixture return line and side warehouse operation.

[0168] The packaging management module 1213 supports the management of packaging-related operations, including packaging warehousing, packaging outbound, box code generation and printing, packaging unpacking, packaging scrapping, and packaging cancellation and scrapping. Packaging warehousing is used for the incoming warehousing of batches after packaging. Packaging outbound is used for the outbound shipment of batches after packaging. Box code generation and printing supports the generation and printing of box codes for packaging. Packaging unpacking allows for the unpacking of already packaged batches. Packaging scrapping allows for the scrapping of already packaged batches. Packaging cancellation and scrapping allows for the restoration of scrapped packaging batches.

[0169] FIG13 is a system technical architecture diagram of a production system according to an embodiment of the present disclosure.

[0170] The technical architecture of the production system according to the embodiments of the present disclosure is based on a Client-Server (C / S) architecture. The server is responsible for data management, while the client is responsible for user interaction. The client module is divided into two parts: one for basic data modeling, named FactoryModeler (Modeler), and the other for the user interface, named Operator Interface Client (OIC).

[0171] As shown in Figure 13, the technical architecture of the production system according to an embodiment of the present disclosure includes a presentation layer, an access layer, an application layer, a CICD (continuous integration / continuous deployment) layer, and a resource layer. The presentation layer is based on WinForms and the Infragistics ziOIC development framework, developed in C#. The access layer's message middleware uses Tibco Rendezvous / RabbitMQ. The application layer includes communication, data, technical components, and languages / frameworks. Communication serialization uses XML / JSON, and protocols use REST API, TRDP / RVCM (Tibrv), and AMQP (RabbitMQ). Data connections use HikariCP / DBCP2, mapping uses Mybatis / ziORM, logging uses Log4j2, and relational uses Oracle / Gauss. Technical components use Tibrv / RabbitMQ for message queuing, and ziFlow Designer & Engine for business processes. The language / framework uses Spring Boot 2 for development, Java 8 for development, and Spring Scheduler / Quartz for timers. The CICD layer includes compilation, packaging, and release, monitoring, and application containers. Maven / Jenkins is used for compilation, packaging, and release; Zabbix is ​​used for monitoring; and the built-in Tomcat is used for application containers. The resource layer includes compute, storage, and operating systems. Compute uses physical machines or cloud virtual machines (VMs) such as RDS; storage uses physical disks or cloud VM storage; and the operating system uses HPUX, Linux, or Windows.

[0172] 14A and 14B are application architecture diagrams of a production system according to an embodiment of the present disclosure.

[0173] As shown in Figures 14A and 14B, the CS architecture is used for the application architecture of the production system according to the embodiment of the present disclosure. The OIC client engineering page is developed in C#, primarily implementing operations on user interaction page data and displaying query page data. The main business interface code is located in the mes-be-oic\MES.Module\Views file, and common components are located in the mes-be-oic\MES.Common file. The server-side engineering encapsulates the unified development framework ziFrame, which includes ORM, ESB (TibcoRV), BPEL Engine, Exception mechanism, log logging, internationalization, Common-Utils, transactions, JDBC pool, Message (XML parsing), etc., and supports XML message format for message communication with the front-end. Due to the characteristics of the semiconductor industry's production process, the server-side mes-core layer implements core business logic processing, and the mes-solution layer provides business entry and customer customization function implementation. The core layer functional code modules on the server side are: zisemi-mes-be-boot (main system framework, SpringBoot), zisemi-mes-be-query (all query modules for directly obtaining data in the OIC system, unified request XML format on the front end, unified data response XML format on the back end, the only difference: different businesses have different request data), zisemi-mes-be-policy (module code for production strategies in the system's basic data configuration module), zisemi-mes-be-schedule (timer function in the system), and the solution code modules on the server side are: zisemi-mes-code (OIC business core code area, so all businesses need to enter this module for business processing), zisemi-mes-data (all data models in the OIC system, JavaBean objects), and zisemi-mes-be-solution (the entry point for the OIC business code, so the XML obtained from the front-end request is classified and processed according to the TibcoRV message middleware mechanism, and then corresponds to different sub-files under the module code, entering the entry point for the corresponding business code on the back end). The mes-framework code modules are: zidm-dependencies (java project files corresponding to dependency package configuration), zidm-flow (corresponding to the process flow module code in the basic data module of the system), zidm-frame, and zidm-parent.

[0174] FIG15 is a block diagram of an electronic device suitable for implementing a control method for a production system according to an embodiment of the present disclosure.

[0175] As shown in Figure 15, the electronic device 1500 according to an embodiment of the present disclosure includes a processor 1501, which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 1502 or a program loaded from a storage portion 1508 into a random access memory (RAM) 1503. The processor 1501 may, for example, include a general-purpose microprocessor (e.g., a CPU), an instruction set processor and / or a related chipset and / or a dedicated microprocessor (e.g., an application-specific integrated circuit (ASIC)), etc. The processor 1501 may also include an onboard memory for caching purposes. The processor 1501 may include a single processing unit or multiple processing units for performing different actions of the method flow according to an embodiment of the present disclosure.

[0176] RAM 1503 stores various programs and data required for the operation of electronic device 1500. Processor 1501, ROM 1502, and RAM 1503 are connected to each other via bus 1504. Processor 1501 executes the various operations of the method flow according to the embodiment of the present disclosure by executing the programs in ROM 1502 and / or RAM 1503. It should be noted that the programs may also be stored in one or more memories other than ROM 1502 and RAM 1503. Processor 1501 may also execute the various operations of the method flow according to the embodiment of the present disclosure by executing the programs stored in one or more memories.

[0177] According to an embodiment of the present disclosure, electronic device 1500 may further include an input / output (I / O) interface 1505, which is also connected to bus 1504. Electronic device 1500 may further include one or more of the following components connected to I / O interface 1505: an input portion 1506 including a keyboard, mouse, etc.; an output portion 1507 including devices such as a cathode ray tube (CRT), a liquid crystal display (LCD), and speakers; a storage portion 1508 including a hard disk; and a communication portion 1509 including a network interface card such as a LAN card or a modem. Communication portion 1509 performs communication processing via a network such as the Internet. A drive 1510 is also connected to I / O interface 1505 as needed. Removable media 1511, such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, etc., is installed in drive 1510 as needed, so that computer programs read from the removable media can be installed into storage portion 1508 as needed.

[0178] The present disclosure also provides a non-transitory computer-readable storage medium, which may be included in the device / apparatus / system described in the above embodiments, or may exist independently and not be incorporated into the device / apparatus / system. The computer-readable storage medium carries one or more programs, and when executed, implements the method according to the embodiments of the present disclosure.

[0179] According to an embodiment of the present disclosure, a computer-readable storage medium may be a non-volatile computer-readable storage medium, for example, it may include but is not limited to: a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination thereof. In the present disclosure, a computer-readable storage medium may be any tangible medium containing or storing a program that can be used by or in combination with an instruction execution system, apparatus, or device. For example, according to an embodiment of the present disclosure, a computer-readable storage medium may include the ROM 1502 and / or RAM 1503 described above and / or one or more memories other than ROM 1502 and RAM 1503.

[0180] Embodiments of the present disclosure also include a computer program product comprising a computer program containing program code for executing the method shown in the flowchart. When the computer program product is executed in a computer system, the program code is used to cause the computer system to implement the method for verifying process data of a product provided by the embodiments of the present disclosure.

[0181] The computer program executes the above functions defined in the system / device of the embodiment of the present disclosure when the computer program is executed by the processor 1501. According to the embodiment of the present disclosure, the system, device, module, unit, etc. described above can be implemented by a computer program module.

[0182] In one embodiment, the computer program may be stored on a tangible storage medium such as an optical storage device or a magnetic storage device. In another embodiment, the computer program may be transmitted and distributed in the form of a signal over a network medium, downloaded and installed via communication portion 1509, and / or installed from removable media 1511. The program code contained in the computer program may be transmitted using any appropriate network medium, including but not limited to wireless, wired, or any suitable combination thereof.

[0183] In such an embodiment, the computer program can be downloaded and installed from a network via the communication section 1509 and / or installed from the removable medium 1511. When the computer program is executed by the processor 1501, the above-described functions defined in the system of the embodiment of the present disclosure are performed. According to the embodiment of the present disclosure, the systems, devices, means, modules, units, etc. described above can be implemented by computer program modules.

[0184] According to an embodiment of the present disclosure, the program code for executing the computer program provided by the embodiment of the present disclosure can be written in any combination of one or more programming languages. Specifically, these computer programs can be implemented using high-level procedural and / or object-oriented programming languages, and / or assembly / machine languages. Programming languages ​​include, but are not limited to, languages ​​such as Java, C++, python, "C" or similar programming languages. The program code can be executed entirely on the user computing device, partially on the user device, partially on a remote computing device, or entirely on a remote computing device or server. In cases involving a remote computing device, the remote computing device can be connected to the user computing device through any type of network, including a local area network (LAN) or a wide area network (WAN), or can be connected to an external computing device (for example, using an Internet service provider to connect via the Internet).

[0185] The flowcharts and block diagrams in the accompanying drawings illustrate the possible implementation architecture, functions and operations of the systems, methods and computer program products according to various embodiments of the present disclosure. In this regard, each box in the flowchart or block diagram can represent a module, program segment, or a part of code, and the above-mentioned module, program segment, or a part of code contains one or more executable instructions for implementing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the box can also occur in an order different from that marked in the accompanying drawings. For example, two boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each box in the block diagram or flowchart, and the combination of boxes in the block diagram or flowchart, can be implemented with a dedicated hardware-based system that performs the specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.

[0186] Those skilled in the art will appreciate that the features described in the various embodiments and / or claims of this disclosure may be combined and / or coupled in various ways, even if such combinations and / or couplings are not explicitly described in this disclosure. In particular, the features described in the various embodiments and / or claims of this disclosure may be combined and / or coupled in various ways without departing from the spirit and teachings of this disclosure. All such combinations and / or couplings are intended to fall within the scope of this disclosure.

[0187] The embodiments of the present disclosure are described above. However, these embodiments are for illustrative purposes only and are not intended to limit the scope of the present disclosure. Although each embodiment has been described separately above, this does not mean that the measures in each embodiment cannot be used in combination to advantage. The scope of the present disclosure is defined by the appended claims and their equivalents. Without departing from the scope of the present disclosure, those skilled in the art may make various substitutions and modifications, which should all fall within the scope of the present disclosure.

Claims

1. A method for controlling a production system, wherein the production system comprises a plurality of process sites. include: Editing a process flow according to an operation of a first user, wherein the process flow includes a plurality of sub-flows, each sub-flow involving at least one process site; In response to a process station in the process flow completing processing of a product, determining a next process station in the process flow after the one process station is completed; as well as In response to the length of time the product stays at the one process station meeting a predetermined restriction condition, the product is allowed to enter the next process station.

2. The method according to claim 1, in, The editing includes at least one of the following items: creating, modifying, removing, cloning, upgrading, setting a frozen state, and setting an activated state, wherein the frozen state indicates prohibiting editing or allowing editing, and the activated state indicates allowing use or prohibiting use.

3. The method according to claim 2, in, The editing includes creating, and the editing of the process flow according to the operation of the first user includes: Determining a candidate sub-flow selected by the first user from a plurality of candidate sub-flows as a sub-flow of the process flow; The execution order among the determined multiple sub-processes is determined according to the dragging operation of the first user to obtain the process flow, wherein the execution order can be represented by the direction of the connecting line.

4. The method according to claim 3, in, The step of determining the candidate sub-flow selected by the first user from a plurality of candidate sub-flows as the sub-flow of the process flow comprises: In response to the first user inputting basic information of the process flow, displaying a plurality of candidate sub-processes; In response to the first user dragging at least one candidate sub-flow from the plurality of candidate sub-flows to the display area, the candidate sub-flow dragged to the display area is determined as a sub-flow of the process flow.

5. The method according to claim 3, in, The step of determining the candidate sub-flow selected by the first user from a plurality of candidate sub-flows as the sub-flow of the process flow comprises: In response to the first user dragging a blank sub-process to the display area, displaying a plurality of candidate sub-processes; The blank sub-flow in the display area is replaced with a candidate sub-flow selected by the user from the multiple candidate sub-flows to obtain a sub-flow of the process flow.

6. The method according to claim 2, in, The editing includes modifying, and the editing of the process flow according to the operation of the first user includes: In response to the first user selecting the process flow from a plurality of already created process flows, the process flow is displayed. The process flow includes a plurality of sub-processes and connecting lines between the plurality of sub-processes; Adding sub-processes and connecting lines to the displayed process flow according to the dragging operation of the first user, and / or removing sub-processes and connecting lines from the displayed process flow according to the removing operation of the first user.

7. The method according to any one of claims 1 to 6, in, In response to receiving the start editing instruction, starting to edit the process flow according to the operation of the first user; In response to receiving an end editing instruction, the editing of the process flow according to the operation of the first user is ended, wherein during a period of time after receiving the start editing instruction and before receiving the end editing instruction, other users except the first user are prohibited from editing the process flow.

8. The method according to any one of claims 1 to 7, further comprising: include: After the process flow is edited according to the operation of the first user, at least one of the following is verified in response to receiving the verification instruction: Whether each sub-process is connected by at least one connection line; Whether the path formed by each connecting line conforms to the predetermined rules.

9. The method according to any one of claims 1 to 8, in, Each sub-process of the process flow includes a data model of at least one process site and a connection model between the process sites, wherein the data model of each process site includes basic information of the process site, and the two process sites corresponding to each connection model are a source process site and a target process site, respectively, and the connection model includes source site information, target site information, and conditions for process transfer from the source site to the target site.

10. The method according to claim 9, in, In response to a process station in the process flow completing the processing of the product, determining the next process station of the process station in the process flow comprises: In the process flow, the process site that has completed product processing is used as the current process site, and a target process node corresponding to a connection model with the current process site as a source process node is searched as a downstream process site of the current process site; According to the type of the connection model between the current process site and each downstream process site and the conditions included in the connection model, the next process site of the current process site is determined from each downstream process site.

11. The method according to claim 9, further comprising: include: In response to a query request from a second user corresponding to a process site specified in the plurality of sites, Determining the next process station of the designated process station in the process flow; as well as The determined next process station is presented to the second user.

12. The method according to any one of claims 1 to 11, in, In response to the length of time the product stays at the one process station meeting a predetermined restriction condition, allowing the product to enter the next process station includes one of the following: If the dwell time is longer than a preset lower limit, the product is allowed to enter the next process station; otherwise, the product is prohibited from entering the next process station; If the residence time is less than the preset upper limit, the product is allowed to enter the next process station, otherwise the product is prohibited from entering the next process station; If the residence time is between the preset upper limit and lower limit, the product is allowed to enter the next process station; otherwise, the product is prohibited from entering the next process station.

13. The method according to claim 12, in, The dwell time is the absolute value of the difference between the entry time of the product at the process station and the next process station of the process station, or the absolute value of the difference between the exit time of the product at the process station and the previous process station of the process station.

14. The method according to claim 12 or 13, further comprising: include: In response to the length of time the product stays at the one process site not meeting a predetermined restriction condition, sending an alarm to a second user corresponding to the one process site; as well as In response to the duration of the alarm exceeding a preset alarm duration, the alarm is cancelled.

15. The method according to any one of claims 12 to 14, further comprising: include: The restriction information between any two adjacent process sites in the process flow is configured according to the input information of the first user, wherein the restriction information includes at least one of the following items: an upper limit value of the stay time, a lower limit value of the stay time, the type of the start time and the end time of the stay time, and the alarm duration, wherein the type of the start time and the end time includes an entry time or an exit time. 16 . An electronic device comprising a memory and a processor, wherein the memory stores instructions executable by the processor, and when the instructions are executed by the processor, the processor executes the method according to claim 1 .

17. A non-transitory computer-readable storage medium storing computer instructions, in, The computer instructions are used to cause the computer to execute the method according to any one of claims 1 to 15.

18. A computer program product comprising a computer program, which, when executed by a processor, implements the method according to any one of claims 1 to 15.

Images