TWI726512B - Process recipe monitoring method and system thereof - Google Patents

Abstract

A process recipe monitoring method is provided. The process recipe monitoring method includes the following steps. First, receiving a request from a user equipment. Then, a recover command is received and includes the following steps. Determining whether the user equipment could perform a recover mode. Entering a locked state to restrict only the user equipment control a database and a recipe description database. Recovering a plurality of sub-recipe items and the corresponding sub-recipe values of a current recipe file according to a plurality of target sub-recipe items and the corresponding target sub-recipe values of target main version data. A main version data and a plurality of sub-version data of the current recipe file after recovering are recorded. Storing the current recipe file into the database after recovering. In addition, a process recipe monitoring system is also provided.

Description

Process recipe monitoring method and process recipe monitoring system

The present invention relates to a method and a system for monitoring a process recipe, and more particularly to a method and a monitoring system that can adjust recipe items flexibly.

With the advancement of process technology, the quality of process products not only depends on the process program, but the condition of the machine is also a key part of it. The machine can be set with a specific control rule to achieve the purpose of producing a specific product by a specific machine. In a substrate processing apparatus, a recipe file is usually used to set the machine's manufacturing process and manufacturing conditions. However, the recipe files of conventional PLC-controlled machines (user equipment) set fixed control conditions for single product production and use, so they lack flexibility and cannot add or modify new control rules and parameter adjustments for process product characteristics. In addition, the control of machine recipes is usually limited by the functions provided by the human-machine interface (user equipment), and the scope of control is not flexible. Once the wrong process control conditions are entered, there is no recovery mechanism to restore the machine to a previous one. A formula file of a specific version. Furthermore, the formula file of each version contains multiple formula items and their corresponding formula values. Under the current mechanism, there is no recovery mechanism to allow the formula file to be in a certain version for a specific formula item and its corresponding formula value. The corresponding formula values are restored individually. What's more, if the formula items in different versions of the formula files are increased or decreased and there are inconsistencies, it is not possible for the operator to restore the required formula files more flexibly.

Therefore, how to improve and provide a "process recipe monitoring method and process recipe monitoring system" to avoid the problems encountered above is a problem that the industry needs to solve urgently.

An object of the present invention is to allow users to go back to the required specific formula file, and to improve the flexibility in the use of process formulas.

An embodiment of the present invention provides a method for monitoring that a process recipe can be executed, which includes the following steps: receiving a connection request from a user equipment; and receiving a traceback command from the user equipment, including the following steps: judging whether a traceback can be executed Mode; enter a locked state to restrict only the user equipment to control a database and a recipe description database, where a current recipe file in the database contains a major version version data and multiple sub-recipe data, each recipe The data includes one-time formula items, one-time formula version data, and one-time formula values. The formula description database contains a formula rule description file. The current formula file is executed according to the formula rule description file; the multiple target sub-recipe items and multiple target sub-recipe items according to a target major version data Multiple target sub-recipe values, restore the corresponding sub-recipe items and sub-recipe values in the current recipe file; record the major version version data and the data of each sub-recipe version in the current recipe file after backtracking; and access after backtracking File the current formula to the database.

An embodiment of the present invention provides a process recipe monitoring system. The process recipe monitoring system includes a data processing unit and a recipe data unit. The data processing unit receives a connection request from the user equipment. The recipe data unit is connected to the data processing unit. The recipe data unit includes a database, a recipe description database, and a backtracking module. The database includes a current recipe file. The current recipe file includes a major version data and multiple times. Recipe data. Each recipe data includes a recipe item, a recipe version data, and a recipe value. The recipe description database contains a recipe rule description file, and the current recipe file is executed according to the formula rule description file. When the data processing unit receives a traceback command, the data processing unit determines whether a traceback mode can be executed. If so, the data processing unit enters a locked state on the recipe data unit to restrict the user equipment control database and the recipe description database. Based on a plurality of target sub-recipe items and a plurality of target sub-recipe values of a target major version data, the retrospective module restores the corresponding sub-recipe items and sub-recipe values in the current recipe file, and the data processing unit records the current after the retrospect The version data of the major version and the version data of each sub-recipe in the recipe file, and access the current recipe file after backtracking to the database.

Based on the above, in the process recipe monitoring method and process recipe monitoring system of the present invention, the current recipe file can be traced back to a specific version of the previous recipe file to restore specific or all sub-recipe items in the current recipe file. Secondly, the formula value is used to improve the flexibility of the process formula.

Furthermore, since it is possible to restore specific or all sub-recipe items and corresponding sub-recipe values, the present invention can be traced back to the major version mode or the specific sub-recipe mode. In other words, the present invention can not only target a specific previous In addition to recovering the version data of the major version of the version, it can also recover a specific sub-recipe item and its corresponding sub-recipe value, so that users can go back to the current recipe file they need.

In addition, for the above-mentioned target formula file that has been backtracked or edited, the present invention records the new major version version data and each sub-recipe version data, instead of restoring the major version version data and each sub-recipe version data. To the previous formula file of a specific version.

In order to make the present invention more comprehensible, the following embodiments are specially cited and are described in detail below in conjunction with the accompanying drawings.

The specific implementation of the present invention will be further described below in conjunction with the accompanying drawings and embodiments. The following embodiments are only used to illustrate the technical solutions of the present invention more clearly, and cannot be used to limit the protection scope of the present invention.

Figure 1 is a schematic diagram of the process recipe monitoring system of the present invention. Figure 2A is a schematic diagram of the current recipe file of the present invention. Figure 2B is a schematic diagram of the formula rule description file of the present invention. Figure 2C is a schematic diagram of the target recipe file of the present invention. 2D is a schematic diagram of an embodiment of the current recipe file after retrospective of the present invention. Please refer to Figure 1 first. In this embodiment, the process recipe monitoring system 10 includes a data processing unit 11, a recipe data unit 12 and a process unit 13.

The data processing unit 11 can realize the functions of communication connection and logical judgment through hardware (such as integrated circuits), software (such as program instructions executed by a processor), or a combination thereof, such as a computer or other computer devices. In this embodiment, the data processing unit 11 and the user equipment 30 can transmit a command C to each other. The data processing unit 11 receives the connection request from the user equipment 30 and waits to receive the command C from the user equipment 30. Data processing The unit 11 determines whether the user equipment 30 has the authority to execute the command, and transmits the command C to notify the user equipment 30. For the convenience of description, FIG. 1 only shows the command C. The name of the command C can be determined according to the different requirements of the data processing unit 11 and the user equipment 30 (or another user equipment 40). For example, the user equipment 30 It is for the user to input the traceback command C1 or the edit command C2 to the data processing unit 11, and the data processing unit 11 can transmit the reject command C3, lock command C41, unlock command C42, reject traceback command C5, reject according to different situations The commands C such as the edit command C6, the update command C7, and the notification command C8 are sent to the user equipment 30. In another embodiment, the data processing unit 11 can receive connection requests or commands C from the user equipment 30 and another user equipment 40 at the same time or at different times, so the data processing unit 11 can also communicate with another user. The devices 40 transmit commands C to each other. The user equipment 30 and another user equipment 40 in this embodiment are, for example, a human machine interface (HMI), a manufacturing execution system (MES), and a web graphic user interface (Web Graphical User Interface, Web GUI) or other communication interface.

The recipe data unit 12 is connected to the data processing unit 11. The recipe data unit 12 includes a database 121, a recipe description database 123, a historical database 125, and a retrospective module 127. Each database is designed according to user needs and can be mixed/combined or presented as a single data memory unit . The database 121 stores and contains a current recipe (Recipe) file RF (see Figure 2A). The current recipe file RF contains a major version (Version) data VM and a plurality of sub-recipe (Sub-Recipe) data SR, each recipe Data SR includes Sub-Recipe Item SRI, Sub-Recipe Version Data SRV and Primary Recipe Value SRN. Each Sub-Recipe Item SRI corresponds to the Sub-Recipe Item SRV and Sub-Recipe Value SRN. Sub-recipe items SRI, such as chemical liquid, pressure, process temperature, process time, heating time, cooling time or substrate thickness, etc., can be adjusted according to the actual machine and process requirements. The sub-recipe value SRN is based on the aforementioned The secondary recipe item SRI is used to set the value, and each time the secondary recipe value SRN is modified, the version information of the secondary recipe version SRV will be changed.

The recipe description database 123 stores and contains a recipe rule description file RRDF (see Figure 2B). The recipe rule description file RRDF is an Extensible Markup Language (XML) configuration file. Formula file RF. In this embodiment, the formula rule description file RRDF sets the upper limit, lower limit and preset value of the SRN corresponding to each sub-recipe item SRI in the current formula file RF. In addition, the formula rule description file RRDF also It can set the editing (Edit) permission conditions, control conditions, communication conditions and compound conditions of each sub-recipe item SRI in the current recipe file RF. The editing permission conditions refer to whether the user can read (Read), or not for the sub-recipe item SRI. Write, read only, or visible (Visible or Invisible) modification permissions; for example, the control condition is that editing is allowed when the process recipe monitoring system 10 is operating; the communication condition allows specific conditions and can be connected Line; compound conditions are for the restriction conditions between multiple sub-recipe items SRI, for example, a certain sub-recipe item SRI is the process temperature, another sub-recipe item SRI is the cooling time, and the compound condition is the set process temperature When the temperature is greater than 120 degrees, the cooling time must be set to be greater than 30 seconds at the same time.

The historical database 125 is for accessing historical data, which includes the current formula file RF before the change and the target formula file TRF as shown in Figure 2C. The target formula file TRF includes the target main version data TVM and multiple target sub-recipe data. TSR, each target sub-recipe data TSR includes a target sub-recipe item TSRI, a target sub-recipe version data TSRV, and a target sub-recipe value TSRN. The target sub-recipe items TSRI are, for example, chemical solution, pressure, process temperature, process time, and temperature rise. Time, cooling time or substrate thickness, etc., can be adjusted according to the actual machine and process requirements to adjust the target sub-recipe items. The target sub-recipe value TSRN is based on the aforementioned target sub-recipe item TSRI to set the value, and the target sub-recipe version SRV is To modify the version information of the SRN of the secondary recipe value. The traceback module 127 connects the database 121, the recipe description database 123 and the historical database 125. The traceback module 127 traces the current recipe file RF according to the traceback command C1. Before the traceback, the data processing unit 11 accesses the traceback. The current formula file RF is sent to the historical database 125. Then, based on the multiple target sub-recipe items TSRI and the multiple target sub-recipe values TSRV in the target recipe file TRF, the retrospective module 127 restores the specific number or values in the current recipe file RF. All secondary recipe items SRI and the corresponding secondary recipe values SRN, for example, the target secondary recipe item TSRI in Figure 2C corresponds to the secondary recipe item SRI in Figure 2A, and the corresponding secondary recipe item SRI in Figure 2A The secondary formula value SRN is restored to the target secondary formula value TSRN in Fig. 2C, which is the current formula file RFB after retrospective in Fig. 2D. In addition, the data processing unit 11 records the major version version data VMB and the sub-recipe version data SRVB in the current recipe file RFB after the traceback, and accesses the current recipe file RFB (as shown in Figure 2D) after the traceback to the database 121 . It should be noted that the data processing unit 11 processes the main version version data VMB and the sub-recipe version data SRVB in the current formula file RFB after the retrospect, not the main version in the current formula file RFB after the retrospect. The version data VMB and each sub-recipe version data SRVB are recorded as the target major version data TVM and each target sub-recipe data TSR in the target recipe file TRF, but the major version version data VMB in the current recipe file RFB after the update backtracking. With each recipe version data SRVB, for example, the major version version data VM in the current recipe file RF before the backtracking shown in Figure 2A is 10, the minor recipe version data SRV is 6, and the backtracking shown in Figure 2D The current recipe file RFB has a major version version data VMB of 11, and a minor recipe version data SRVB of 7. In this example, the record version is incremental. In another embodiment, the record version can be encoded in other ways or according to requirements. Set to it.

The processing unit 13 is connected to the data processing unit 11. The data processing unit 11 receives the current recipe file RF and the recipe rule description file RRDF transmitted by the recipe data unit 12, and the data processing unit 11 transmits the current recipe file RF and the recipe rule description file RRDF to the processing unit 13. The process unit 13 processes the substrate according to the current formula file RF and the formula rule description file RRDF, and the current formula file RF is executed according to the provisions of the formula rule description file RRDF.

Figure 3 is a flow chart of the process recipe monitoring method of the present invention. FIG. 4 is a flowchart of receiving a connection request from the user equipment in FIG. 3. Fig. 5 is a flowchart of starting the data processing unit in Fig. 4; FIG. 6 is a flowchart of receiving a traceback command from the user equipment in FIG. 3. FIG. FIG. 7 is a flowchart of judging whether the user equipment can execute the backtracking mode in FIG. 6. FIG. 8 is a flowchart of judging whether the user equipment has authority in FIG. 7. Fig. 9 is a flowchart of checking whether the recipe rule description file can be executed in Fig. 8. FIG. 10 is a flowchart of receiving an edit command from the user equipment in FIG. 3. FIG. FIG. 11 is a flowchart of judging whether the user equipment can execute the edit mode in FIG. 10. Fig. 12 is a flowchart of checking whether the recipe rule description file can be executed in Fig. 11. FIG. 13 is a flowchart of the current recipe file provided in FIG. 10 for editing by the user equipment.

Please refer to FIG. 3 first. The process recipe monitoring method S10 of this embodiment can be used in the process recipe monitoring system 10 shown in FIG. 1. The process recipe monitoring method S10 includes the following steps S11 to S13. Step S11 is performed to receive a connection request from the user equipment 30. Taking FIG. 1 as an example, the data processing unit 11 receives the connection request from the user equipment 30 and waits to receive the command C from the user equipment 30. Step S11 may include For the following steps S112 to S116, please refer to FIG. 4, and proceed to step S112 to activate a data processing unit 11 so that the data processing unit 11 can perform the functions of communication connection and logic judgment. After step S112, step S114 is performed to obtain the current recipe file RF in the database 121 and the recipe rule description file RRDF in the recipe description database 123 through the data processing unit 11. Then, in step S116, the user equipment 30 is connected to the data processing unit 11. In detail, step S112 may include the following steps S22 to S26. Please refer to FIG. 5, and proceed to step S22 to read an original description file. The original description file system is an Extensible Markup Language (XML) setting files. Taking FIG. 1 as an example, the data processing unit 11 reads the original description file of the process unit 13 to analyze the structure of the recipe of the process unit 13. Next, proceed to step S24 to compare whether the formula rule description file RRDF in the formula description database 123 matches according to the original description file. Taking Figure 1 as an example, the data processing unit 11 first checks whether the description format and setting conditions of the original description file (such as upper limit value, lower limit value, default value, editing authority condition, control condition, communication condition and compound condition) are correct And whether it can be executed, if not, the data processing unit 11 transmits a notification command C8 to the user equipment 30 to display abnormality; on the contrary, if the description format and setting conditions of the original description file are correct and can be executed, the data processing unit 11 is connected Go to the formula description database 123 and extract the formula rule description file RRDF. The data processing unit 11 compares whether the original description file and the formula rule description file RRDF can be matched. The upper limit, lower limit and default value of SRN corresponding to each recipe item SRI in the current recipe file RF, as well as the edit authority conditions, control conditions, communication conditions and compound conditions of each recipe item SRI To determine whether the data corresponding to the original description file exists and is consistent. In one embodiment, if the data processing unit 11 determines that the original description file and the recipe rule description file RRDF can match, the data processing unit 11 transmits a notification command C8 to the user equipment 30 to display normal and can continue to execute. In another embodiment, if the data processing unit 11 determines that the original description file and the recipe rule description file RRDF cannot match, step S26 is performed. If there is no match, the recipe rule description file RRDF is updated to the recipe description database 123, as shown in FIG. 1 For example, the data processing unit 11 locks the recipe description database 123 to prohibit another user device 40 (including other user devices) from reading and writing the recipe description database 123. Then, the data processing unit 11 is based on the original The description file is used to update the recipe rule description file RRDF to the recipe description database 123. After the update, the data processing unit 11 unlocks the recipe description database 123 and informs the user that the device 30 can continue execution. This ensures the original The description file system complies with the recipe rule description file RRDF in the recipe data unit 12. It should be noted that the action of comparing the formula rule description file RRDF according to the original description file in the above figure 5, in addition to starting the process recipe monitoring system 10, when the user equipment 30 needs to edit or backtrack, it can also be based on the above figure 5 The process of determining whether the formula rule description file RRDF matches the original description file of the process unit 13.

Please refer to FIG. 3 again. After step S11, the user equipment 30 is connected to the data processing unit 11. Then, the user equipment 30 transmits a command C to the data processing unit 11 according to the user's requirement. The command C is, for example, a Backtracking command C1 or an editing command C2. In this embodiment, the user equipment 30 transmits the traceback command C1 to the data processing unit 11, and the data processing unit 11 receives the traceback command C1 from the user equipment 30 (step S12). Step S12 may include the following steps S121 to S129B, Referring to FIG. 6, proceed to step S121. The data processing unit 11 determines whether a traceback mode can be executed, that is, after receiving the traceback command C1 of the user equipment 30, the data processing unit 11 determines whether the user equipment 30 can execute the traceback mode, if not , Proceed to step S129, reject the user equipment 30 and notify the user equipment 30. In detail, step S121 may include the following steps S32 to S36. Please refer to FIG. 7 and proceed to step S32. The data processing unit 11 determines whether the database 121 and the recipe description database 123 are locked, that is, the data processing unit 11 checks Whether the database 121 is locked by another user equipment 40 (including other user equipment) or the current recipe file RF designated for editing is being used by another user equipment 40 (including other user equipment), and the recipe description database 123 Whether it is locked by another user equipment 40 (including other user equipment) or whether the recipe rule description file RRDF is being edited by another user equipment 40 (including other user equipment), if so, the database 121 and the recipe description data The library 123 is locked, and the data processing unit 11 determines that the user equipment 30 cannot execute the retrospective mode, so it proceeds to step S36, rejects the user equipment 30, and informs the user equipment 30. Therefore, the data processing unit 11 transmits a backtracking rejection command C5 to the user equipment 30 and notifies the user equipment 30 to refuse to execute the backtracking command C1. Conversely, if the data processing unit 11 determines that the database 121 and the recipe description database 123 are not controlled by another user equipment 40 (including other user equipment), step S34 is performed to determine whether the data processing unit 11 is authorized. It is determined that the user equipment 30 does not have the authority to trace back, and step S36 is performed to reject the user equipment 30 and notify the user equipment 30. Therefore, the data processing unit 11 transmits a rejection command C3 to the user equipment 30 and informs the user equipment 30 . In detail, the step S34 for the data processing unit 11 to determine whether it has the authority can include steps S341 to S345. Please refer to FIG. 8 and proceed to step S341 to determine whether it is possible to log in. Taking FIG. 1 as an example, the data processing unit 11 loads Regarding the user’s account password of the user device 30, and check whether the user’s account password is correct, then the data processing unit 11 checks whether the user’s account password has been logged in repeatedly, that is, the account password of the same user is used In addition to the user device 30 logging in, check whether there is another user device logging in with the account password of the same user. If the user’s account and password are incorrect after the check, or the user’s account and password has been repeatedly logged in, the data processing unit 11 determines that the user equipment 30 cannot log in, and proceeds to step S345, rejects the user equipment 30 to log in, and informs the user equipment 30. Therefore, the data processing unit 11 transmits a rejection command C3 to the user equipment 30 to notify the user equipment 30. If the determination in step S341 is yes, the user equipment 30 can log in, and proceed to step S342 to determine whether the formula rule description file RRDF in the formula description database 123 is locked. Taking FIG. 1 as an example, the data processing unit 11 determines the formula description database 123 Whether the formula rule description file RRDF is locked in the middle, the lock refers to whether the formula rule description file RRDF in the formula description database 123 is controlled and used by another user equipment 40 (including other user equipment). If so, proceed to step S345, The user equipment 30 is refused to log in and the user equipment 30 is notified. Therefore, the data processing unit 11 transmits the refusal command C3 to the user equipment 30 and notifies the user equipment 30. In one embodiment, the data processing unit 11 further determines whether another user equipment 40 locks the recipe rule description file RRDF timeout. If not, the data processing unit 11 continues to allow another user equipment 40 to lock the recipe rule description file RRDF for Edit; On the contrary, if another user equipment 40 locks the recipe rule description file RRDF has expired and exceeded a specific time, the data processing unit 11 transmits the rejection command C3 and informs the user equipment 30 and the other user equipment 40 that the time has expired Time. In step S342, if the data processing unit 11 determines that the recipe rule description file RRDF in the recipe description database 123 is not locked, then step S343 is performed. The data processing unit 11 obtains the recipe rule description file RRDF in the recipe description database 123 . Next, proceed to step S344 to check whether the recipe rule description file RRDF can be executed. If not, proceed to step S345 to deny the user equipment 30 to log in, and notify the user equipment 30. Therefore, the data processing unit 11 transmits the refusal command C3 to the use The user device 30 and the user device 30 are notified. In detail, step S344 may include step S42 to step S46. Please refer to FIG. 9 and proceed to step S42 to determine whether the user equipment 30 has the authority to edit the recipe rule description file RRDF. Taking FIG. 1 as an example, the data processing unit 11 determines whether the user equipment 30 has the authority to edit the recipe rule description file RRDF according to the editing authority conditions. If the determination is no, proceed to step S46, deny the user equipment 30 to log in, and notify the user Therefore, the data processing unit 11 transmits the rejection command C3 to the user device 30 and informs the user device 30 that it cannot edit the formula rule description file RRDF; otherwise, if the judgment is yes, the user device 30 has the authority to edit the formula rule Description file RRDF, and proceed to step S44 to check whether the user equipment 30 can edit the formula rule description file RRDF. Taking FIG. 1 as an example, the data processing unit 11 determines whether the user equipment 30 can edit the formula rule description file RRDF according to the control conditions and communication conditions. If the determination is no, proceed to step S46, deny the user equipment 30 to log in, and notify The user equipment 30, therefore, the data processing unit 11 transmits the rejection command C3 to the user equipment 30 and informs the user equipment 30 that the recipe rule description file RRDF cannot be edited; on the contrary, if the judgment is yes, the user equipment 30 is currently available for editing the recipe Rule description file RRDF.

Please refer to FIG. 6 again. After it is determined in step S121 that the user equipment 30 can execute the retrospective mode, step S122 is performed to enter a locked state to restrict only the user equipment 30 to control a database 121 and a recipe description database 123. Among them, a current recipe file RF in the database 121 contains a major version version data VM and a plurality of sub-recipe data SR. Each sub-recipe data SR includes the sub-recipe item SRI, the sub-recipe version data SRV and the sub-recipe value SRN, formula description The database 123 includes a recipe rule description file RRDF, and executes the current recipe file RF according to the recipe rule description file RRDF. Taking FIG. 1 as an example, the data processing unit 11 transmits the lock command C41 to the user equipment 30. Therefore, even if another user equipment 40 or other user equipment is connected to the data processing unit 11 at this time, because the database 121 and the recipe Describe that the database 123 has been controlled by the user equipment 30 and enters the locked state. At this time, the data processing unit 11 transmits a rejection command C3 and informs another user equipment 40 or other user equipment that the user equipment 30 has locked the database 121 and The recipe description database 123 makes it impossible for another user device 40 to control the database 121 and the recipe description database 123. Then, step S123 is performed to access the current recipe file RF before the backtracking to a historical database 125. Therefore, the data processing unit 11 accesses the current recipe file RF before the backtracking to the historical database 125. Next, proceed to step S124 to restore the corresponding sub-recipe item SRI and sub-recipe value SRN in the current recipe file RF according to the plurality of target sub-recipe items TSRI and the plurality of target sub-recipe values TSRN of a target major version data TVM. For example, the secondary recipe item SRI in Figure 2A corresponds to the target secondary recipe item TSRI in Figure 2C, so the secondary recipe value SRN of the corresponding secondary recipe item SRI in Figure 2A is restored to the target secondary recipe value in Figure 2C TSRN, which is the current formula file RFB after retrospective in Figure 2D. In addition, since the current recipe file RF needs to be backtracked at this time, the data processing unit 11 can determine whether the original description file in the process unit 13 matches the recipe rule description file RRDF in the recipe description database 123 according to FIG. 5, It is judged as a match, and then, the data processing unit 11 judges whether the edited data of each sub-recipe data SR in the current recipe file RF conforms to the format and the recipe rule description file RRDF.

After the above step S124 is performed, step S125 is then performed to record the major version version data VMB and the sub-recipe version data SRVB in the current recipe file RFB after being traced back. Then, step S126 is performed to access the current recipe file RFB after the traceback to the database 121. Taking FIG. 1 as an example, the data processing unit 11 further determines the backtracking mode according to the backtracking command C1 transmitted by the user equipment 30. The backtracking mode can be a mode of returning to a major version or a mode of returning to a specific secondary recipe.

In one embodiment, the retrospective mode is the recovery master version mode. The master version mode refers to restoring the current formula file RF to a formula file of a specific version. The formula file of the specific version is, for example, the target formula file TRF, based on the target formula A plurality of target sub-recipe items TSRI and a plurality of target sub-recipe values TSRV in the file TRF, the retrospective module 127 restores all the sub-recipe items SRI and the corresponding sub-recipe values SRN in the current recipe file RF. For example, the main version version data VM in the current recipe file RF before the retrospective is 10, one recipe version data SRV is 6, and the other recipe version data SRV is 7. I want to restore the current recipe file RF to the main version If the version number is 8, if the target major version data TVM of the target recipe file TRF is 8, the backtracking module 127 responds according to the multiple target sub-recipe items TSRI and the multiple target sub-recipe values TSRV in the target recipe file TRF. All the sub-recipe items SRI and the corresponding sub-recipe value SRN in the current recipe file RF, and then, the data processing unit 11 accesses the current recipe file RFB that has been traced back to the database 121. In one embodiment, each target sub-recipe item TSRI in FIG. 2C corresponds to the sub-recipe item SRI in FIG. 2A, and the sub-recipe value SRN of the corresponding sub-recipe item SRI in FIG. 2A is restored to the target sub-recipe item in FIG. 2C The formula value TSRN is the current formula file RFB after retrospective in Figure 2D. In addition, the data processing unit 11 records the major version version data VMB and each sub-recipe version data SRVB in the current recipe file RFB after the traceback, and then the data processing unit 11 accesses the current recipe file RFB after the traceback (Figure 2D). Shown) to database 121. It should be noted that the data processing unit 11 processes the main version version data VMB and the sub-recipe version data SRVB in the current formula file RFB after the retrospect, not the main version in the current formula file RFB after the retrospect. The version data VMB and each sub-recipe version data SRVB are recorded as the target major version data TVM and each target sub-recipe data TSR in the target recipe file TRF, but the major version version data VMB in the current recipe file RFB after the update backtracking. With each recipe version data SRVB, therefore, the major version version data VM in the current recipe file RF before the traceback shown in Figure 2A is 10, one recipe version data SRV is 6, and the other recipe version data SRV is 7. , The main version data VMB of the current recipe file RFB after the retrospective shown in Figure 2D is 11, one recipe version data SRV is 7, and the other recipe version data SRV is 8. The record version is incremented as an example. In other embodiments, the record version can be set in other encoding methods or according to requirements. In addition, it should be noted that since the quantity of secondary formula version data SRV in the current formula file RF before the retrospect may be different from the quantity of the target secondary formula item TSRI in the target formula file TRF to be restored, the data processing unit 11 is based on The current formula file RF is compared with the target formula file TRF in the historical database 125 to determine whether each sub-recipe item SRI can correspond to the corresponding target sub-recipe item TSRI. If there is no match to the corresponding sub-recipe item SRI, In the traceback step, keep the secondary formula item SRI in the current formula file RF and the corresponding formula value SRN. If there is a matching secondary formula item SRI, in the traceback step, the corresponding secondary formula item SRI will be matched and replaced with the target The secondary recipe item TSRI, at the same time, also replaces and restores the secondary recipe value SRV corresponding to the secondary recipe item SRI to the target secondary recipe value TSRV.

In another embodiment, the retrospective mode is to restore a specific sub-recipe mode, and the specific sub-recipe mode refers to restoring a specific or a few sub-recipe items SRI in the current recipe file RF to the corresponding target recipe file TRF The target secondary formula project TSRI. For example, the major version version data VM in the current recipe file RF before the retrospective is 10, the version data SRV of a specific minor recipe is 6, and the other minor recipe version data SRV is 7. If you put the current recipe file RF in A specific secondary formula item SRI and the corresponding secondary formula value SRN are restored to the corresponding secondary formula item and secondary formula value in a certain secondary formula version. A certain secondary formula version is the target major version data TVM, for example, if the target formula The target major version data TVM of the TRF file is 8 and the target minor formula version data TSRV is 5. Therefore, the traceback module 127 uses the target major version data TVM to restore the target minor formula item TSRI and the target minor formula value TSRV to restore the current formula file. The sub-recipe item SRI in the RF and the corresponding sub-recipe value SRN. In addition, the data processing unit 11 records the major version version data VMB and each sub-recipe version data SRVB in the current recipe file RFB after the traceback, and then the data processing unit 11 accesses the current recipe file RFB after the traceback (Figure 2D). Shown) to database 121. It should be noted that the data processing unit 11 processes the main version version data VMB and the sub-recipe version data SRVB in the current formula file RFB after the retrospect, not the main version in the current formula file RFB after the retrospect. The version data VMB and each sub-recipe version data SRVB are recorded as the target major version data TVM and each target sub-recipe data TSR in the target recipe file TRF, but the major version version data VMB in the current recipe file RFB after the update backtracking. And each sub-recipe version data SRVB, and retain the non-retrospected sub-recipe version data SRVB. Therefore, in one embodiment, the main version version data VM in the current recipe file RF before the retracing shown in FIG. 2A is 10. , A specific sub-recipe item SRI corresponds to a specific sub-recipe version data SRV of 6, and another specific sub-recipe item SRI corresponds to another sub-recipe version data SRV of 7. Perform the specific sub-recipe mode and save the current recipe file A specific sub-recipe item SRI in the RF is restored to the corresponding target sub-recipe item TSRI in the target recipe file TRF without going back to another specific sub-recipe item SRI. Figure 2D shows the current recipe file RFB after the backtracking. The major version version data VMB is 11, the SRI of a specific sub-recipe item after the retrospect corresponds to a specific sub-recipe version data SRVB is 7, that is, the version data of each sub-recipe after the retrospect is incremented, and another specific sub-recipe item Since the SRI has not been backtracked, the data SRV of the other sub-recipe version is still maintained at 7. Here, the record version is incremented as an example. In other embodiments, the record version can be set in other encoding methods or according to requirements. In addition, it should be noted that since the quantity of secondary formula version data SRV in the current formula file RF before the retrospect may be different from the quantity of the target secondary formula item TSRI in the target formula file TRF to be restored, the data processing unit 11 is based on The current formula file RF is compared with the target formula file TRF in the historical database 125 to determine whether each sub-recipe item SRI can correspond to the corresponding target sub-recipe item TSRI. If there is no match to the corresponding sub-recipe item SRI, In the traceback step, keep the secondary formula item SRI in the current formula file RF and the corresponding formula value SRN. If there is a matching secondary formula item SRI, in the traceback step, the corresponding secondary formula item SRI will be matched and replaced with the target The secondary recipe item TSRI, at the same time, also replaces and restores the secondary recipe value SRV corresponding to the secondary recipe item SRI to the target secondary recipe value TSRV.

Please continue to refer to FIG. 6, after accessing the current recipe file RFB after the traceback in step S126 to the database 121, proceed to step S127 to determine whether there is another connection request from the user equipment 40. Taking FIG. 1 as an example, the data The processing unit 11 determines whether there is a connection request from another user equipment 40 (or other user equipment), and if not, proceeds to step S129B to release the locked state. Therefore, the data processing unit 11 transmits an unlock command C42 to the user equipment 30. In other words, unlock the database 121 and the recipe description database 123 so that the database 121 and the recipe description database 123 can be controlled by another user equipment 40 or other user equipment; on the contrary, if the data processing unit 11 It is determined that there is a connection request from another user equipment 40 (or other user equipment), and step S128 is performed to notify the other user equipment 40, and update the current recipe file RFB after the traceback. Therefore, the data processing unit 11 transmits An update command C7 is sent to another user equipment 40 to update the current recipe file RFB after being backtracked for use by another user equipment 40.

Please refer to FIG. 3 again. After step S11, the user equipment 30 is connected to the data processing unit 11, and then the user equipment 30 transmits the command C to the data processing unit 11 according to the user's needs. In this embodiment, the user equipment 30 transmits the editing command C2 to the data processing unit 11, and the data processing unit 11 receives the editing command C2 from the user equipment (step S13). Step S13 may include the following steps S131 to S139. Referring to FIG. 10, proceed to step S131 to determine whether an editing mode can be executed, that is, after receiving the editing command C2 of the user equipment 30, the data processing unit 11 determines whether the user equipment 30 can execute the editing mode, if not, proceed to step S138, The user equipment 30 is rejected and the user equipment 30 is notified. Therefore, the data processing unit 11 transmits a rejection command C3 to the user equipment 30 to notify the user equipment 30.

In detail, step S131 may include the following steps S51 to S55. Please refer to FIG. 11 and proceed to step S51 to determine whether it is possible to log in. Taking Fig. 1 as an example, the data processing unit 11 loads the user account and password of the user device 30, and checks whether the user’s account password is correct, and then the data processing unit 11 checks whether the user’s account password is correct. Repeat login, that is, in addition to the user device 30 logging in with the account password of the same user, check whether there is another user device logging in with the account password of the same user. If the user’s account password is incorrect after the check, or the user’s account password has repeated logins, the data processing unit 11 determines that the user equipment 30 cannot log in, and proceeds to step S55, rejects the user equipment 30 to log in, and informs the user equipment 30. Therefore, the data processing unit 11 transmits a rejection command C3 to the user equipment 30 to notify the user equipment 30.

If the determination in step S51 is yes, the user equipment 30 can log in, and proceed to step S52 to determine whether the formula rule description file RRDF in the formula description database 123 is locked. Taking FIG. 1 as an example, the data processing unit 11 determines whether the recipe rule description file RRDF in the recipe description database 123 is locked. The lock refers to whether the recipe rule description file RRDF in the recipe description database 123 is locked by another user device 40. (Including other user equipment) control the use. If yes, proceed to step S55, deny the user equipment 30 to log in, and notify the user equipment 30. Therefore, the data processing unit 11 transmits the refusal command C3 to the user equipment 30 and notifies the user equipment 30. In one embodiment, the data processing unit 11 further determines whether another user equipment 40 locks the recipe rule description file RRDF timeout. If not, the data processing unit 11 continues to allow another user equipment 40 to lock the recipe rule description file RRDF for Edit; On the contrary, if another user equipment 40 locks the recipe rule description file RRDF has expired and exceeded a specific time, the data processing unit 11 transmits the rejection command C3 and informs the user equipment 30 and the other user equipment 40 that the time has expired Time.

In step S52, if the data processing unit 11 determines that the recipe rule description file RRDF in the recipe description database 123 is not locked, then it proceeds to step S53, the data processing unit 11 obtains the recipe rule description file RRDF from the recipe description database 123. Next, proceed to step S54 to check whether the recipe rule description file RRDF can be executed. If not, proceed to step S55 to deny the user equipment 30 to log in, and notify the user equipment 30. Therefore, the data processing unit 11 transmits the refusal command C3 to the use The user device 30 and the user device 30 are notified.

In detail, step S54 may include step S542 to step S546. Please refer to FIG. 12 and proceed to step S542 to determine whether the user equipment 30 has the authority to edit the recipe rule description file RRDF. Taking Fig. 1 as an example, the data processing unit 11 judges whether the user equipment 30 has the authority to edit the formula rule description file RRDF according to the editing authority conditions, where the editing authority condition refers to whether the user equipment 30 can read the sub-recipe item SRI (Read), write (Write), read only (Read Only) or visible (Visible or Invisible) modification permission, if judged as no, proceed to step S546, deny the user device 30 to log in, and notify the user Device 30, therefore, the data processing unit 11 transmits the rejection command C3 to the user device 30 and informs the user device 30 that the device 30 cannot edit the formula rule description file RRDF; on the contrary, if the judgment is yes, the user device 30 has the authority to edit the formula rule description File RRDF, and proceed to step S544 to check whether the user equipment 30 can edit the formula rule description file RRDF. Taking FIG. 1 as an example, the data processing unit 11 determines whether the user equipment 30 can edit the formula rule description file RRDF according to the control conditions and communication conditions. The control conditions are, for example, that editing is allowed when the process recipe monitoring system 10 is operating; communication conditions The connection is allowed under certain conditions. If the judgment is no, proceed to step S546, deny the user equipment 30 to log in, and notify the user equipment 30. Therefore, the data processing unit 11 transmits the refusal command C3 to the user equipment 30 and informs the user equipment 30. The user device 30 cannot edit the recipe rule description file RRDF; on the contrary, if the judgment is yes, the user device 30 is currently available for editing the recipe rule description file RRDF.

Please refer to FIG. 10 again. After it is determined in step S131 that the user equipment 30 can execute the editing mode, step S132 is performed to determine whether the user equipment 30 can control the database 121 and the recipe description database 123. Taking FIG. 1 as an example, the data processing unit 11 determines whether the database 121 and the recipe description database 123 are controlled by another user equipment 40, that is, the data processing unit 11 checks whether the database 121 is locked or the current recipe designated for editing The file RF is being used, or the data processing unit 11 checks whether the recipe description database 123 is locked or the recipe rule description file RRDF is being edited. If it is determined that the user equipment 30 can control the database 121 and the recipe description database 123, The data processing unit 11 enters the locked state on the recipe data unit 12, and the database 121 and the recipe description database 123 are locked to restrict the user equipment 30 to control the database 121 and the recipe description database 123; on the contrary, if the data processing unit 11 It is determined that the user equipment 30 cannot provide the user equipment 30 to control the database 121 and the recipe description database 123, and proceed to step S139 to notify the user equipment 30, and restore the current recipe file RF before editing to the user equipment 30. Therefore, the data processing unit 11 transmits an editing rejection command C6 to the user equipment 30 and notifies the user equipment 30 to refuse to execute the editing command C2, and if the user equipment 30 is editing the current recipe file RF, the data processing unit 11 recovers The current formula file RF before editing is sent to the user device 30.

If the data processing unit 11 determines that the database 121 and the recipe description database 123 are not controlled by another user equipment 40 (including other user equipment), step S133 is performed to enter the locked state to restrict only the user equipment 30 Control database 121 and recipe description database 123. Taking FIG. 1 as an example, the data processing unit 11 transmits the lock command C41 to the user equipment 30. Therefore, even if another user equipment 40 or other user equipment is connected to the data processing unit 11 at this time, because the database 121 and the recipe Describe that the database 123 has been controlled by the user equipment 30 and enters the locked state. At this time, the data processing unit 11 transmits a rejection command C3 and informs another user equipment 40 or other user equipment that the user equipment 30 has locked the database 121 and The recipe description database 123 makes it impossible for another user device 40 to control the database 121 and the recipe description database 123. Then, step S134 is performed to provide the current formula file RF for editing by the user equipment 30, and after editing the current formula file RF, proceed to step S135 to access the edited current formula file RF to the database 121.

In detail, between step S134 to step S135 can include step S61 to step S68, please refer to FIG. 13, go to step S61, write an editing data, the editing data can be an Extensible Markup Language (XML) ) Configuration file. Taking FIG. 1 as an example, the user equipment 30 writes editing data and transmits it to the data processing unit 11, and the data processing unit 11 reads the editing data written by the user equipment 30. In one embodiment, the data processing unit 11 further determines whether the lock database 121 and the recipe description database 123 of the user equipment 30 are timed out. If not, the data processing unit 11 continues to allow the user equipment 30 to lock the database 121 and the recipe description. Database 123 for editing; on the other hand, if the user equipment 30 locks the database 121 and the recipe description database 123 and has timed out for a specific time, the data processing unit 11 transmits a rejection command C3 and informs the user equipment 30 and another The user equipment 40 has timed out and the locked state is unlocked. Therefore, the data processing unit 11 transmits the unlock command C42 to the user device 30. In other words, the locked state of the database 121 and the recipe description database 123 is unlocked, so that the database 121 The recipe description database 123 can be controlled by another user equipment 40 or other user equipment.

After the editing data is written in step S61, then step S62 is performed to determine whether the editing data conforms to the formula rule description file RRDF. Taking Figure 1 as an example, the data processing unit 11 first determines whether the description format and setting conditions (such as upper limit value, lower limit value, preset value, editing authority condition, control condition, communication condition and compound condition) of the edited data are correct and correct. Whether it can be executed, if not, proceed to step S67, reject the user equipment 30, and notify the user equipment 30. Therefore, the data processing unit 11 transmits a notification command C8 to the user equipment 30 that the display is abnormal; otherwise, if the data is edited If the description format and the setting conditions are correct and can be executed, step S63 is performed to check whether the edited data is consistent with the current recipe file RF. If the data processing unit 11 determines that the edited data is consistent with the current recipe file RF, step S68 is performed, and the data processing unit 11 records the major version version data VM and each sub-recipe version data SRV in the current recipe file RF to the database 121. In other words, Although the edited data of the user equipment 30 is consistent with the current formula file RF, the data processing unit 11 will still update the edited current formula file RF after editing the main version data VM and each recipe file. Version information SRV. For example, the major version version data VM in the current recipe file RF before editing is 10, the minor recipe version data SRV in the minor recipe data SR is 6, and the major version version data VM in the current recipe file RF after editing It is 11, and the secondary recipe version data SRVB is 7. In this example, the record version is incremented. In another embodiment, the record version can be set in other encoding methods or according to requirements.

If in step S63, the data processing unit 11 determines that the edited data is inconsistent with the current recipe file RF, step S64 is performed to access the current recipe file RF before editing to the historical database 125. Therefore, if the major version version data VMB in the current recipe file RF before editing is 10, and the minor recipe version data SRV in the secondary recipe data SR is 7, the data processing unit 11 stores the current recipe file RF before editing. Get to the historical database 125 of the recipe data unit 12.

Then, step S65 is performed to update the SRI of each recipe item in the current recipe file RF that is inconsistent. Taking FIG. 1 as an example, the data processing unit 11 correspondingly updates the SRI of each recipe item that is inconsistent after the comparison to the database 121. Then, proceed to step S66 to record the edited main version version data VM and each sub-recipe version data SRV corresponding to each sub-recipe item SRI. Therefore, the data processing unit 11 accesses the edited current recipe file RF to The database 121 records the major version version data VM and each sub-recipe version data SRV corresponding to each sub-recipe item SRI. For example, the main version version data VM in the current formula file RF before editing is 10, the sub-recipe version data SRV corresponding to each sub-recipe item SRI is 6, and the main version version of the current formula file RF after editing The secondary data VM is 11, and the secondary recipe version data SRVB is 7. Here, the record version is incremented as an example. In another embodiment, the record version can be set in other encoding methods or according to requirements.

Next, referring to FIG. 10 again, proceed to step S136 to release the locked state. Therefore, the data processing unit 11 transmits the unlock command C42 to the user device 30. In other words, the data processing unit 11 unlocks the recipe data unit 12 to release the restriction. Only the user device 30 can control the database 121 and the recipe description data. The database 123 allows the database 121 and the recipe description database 123 to be controlled by another user device 40 or other user devices. Next, proceed to step S137 to notify and update the edited current recipe file RF. Therefore, the data processing unit 11 transmits a notification command C8 to the user equipment 30 and the other user equipment 40, and the data processing unit 11 transmits an update command C7 to the user equipment 30 and the other user equipment 40 to update the user equipment 30 and the other user equipment 40. The edited current recipe file RF can be used by another user equipment 40.

In summary, in the process recipe monitoring method and process recipe monitoring system of the present invention, the current recipe file can be traced back to the previous recipe file of a specific version to restore specific or all sub-recipe items in the current recipe file. Corresponding to the secondary formula value, thereby enhancing the flexibility of the process formula.

Furthermore, since it is possible to restore specific or all sub-recipe items and corresponding sub-recipe values, the present invention can be traced back to the major version mode or the specific sub-recipe mode. In other words, the present invention can not only target a specific previous In addition to recovering the version data of the major version of the version, it can also recover a specific sub-recipe item and its corresponding sub-recipe value, so that users can go back to the current recipe file they need.

In addition, for the above-mentioned target formula file that has been backtracked or edited, the present invention records the new major version version data and each sub-recipe version data, instead of restoring the major version version data and each sub-recipe version data. To the previous formula file of a specific version.

Although the present invention has been disclosed in the above embodiments, it is not intended to limit the present invention. Anyone with ordinary knowledge in the technical field can make some changes and modifications without departing from the spirit and scope of the present invention. The scope of protection of the present invention shall be subject to those defined by the attached patent scope.

10: Process recipe monitoring system 11: Data processing unit 12: Recipe data unit 121: database 123: Recipe description database 125: Historical Database 127: Retrospective Module 13: Process unit 30: user equipment 40: Another user's device C: Command RF, RFB: current formula file RRDF: formula rule description file S10: Process recipe monitoring method S11~S12: steps S112~S116: steps S121~S129B: steps S131~S139: steps S22~S26: steps S32~S36: steps S341~S345: steps S42~S46: steps S51~S55: steps S542~S546: steps S61~S68: steps SR: Sub-formulation data SRI: Sub-formulation project SRN: Secondary formula value SRV: Sub-formulation version data TRF: target formula file TSR: target sub-formulation data TSRI: Target Sub-Formulation Project TSRN: Target secondary formula value TSRV: target sub-formulation version data TVM: target major version data VM, VMB: Major version version data

Figure 1 is a schematic diagram of the process recipe monitoring system of the present invention. Figure 2A is a schematic diagram of the current recipe file of the present invention. Figure 2B is a schematic diagram of the formula rule description file of the present invention. Figure 2C is a schematic diagram of the target recipe file of the present invention. 2D is a schematic diagram of an embodiment of the current recipe file after retrospective of the present invention. Figure 3 is a flow chart of the process recipe monitoring method of the present invention. FIG. 4 is a flowchart of receiving a connection request from the user equipment in FIG. 3. Fig. 5 is a flowchart of starting the data processing unit in Fig. 4; FIG. 6 is a flowchart of receiving a traceback command from the user equipment in FIG. 3. FIG. FIG. 7 is a flowchart of judging whether the user equipment can execute the backtracking mode in FIG. 6. FIG. 8 is a flowchart of judging whether the user equipment has authority in FIG. 7. Fig. 9 is a flowchart of checking whether the recipe rule description file can be executed in Fig. 8. FIG. 10 is a flowchart of receiving an edit command from the user equipment in FIG. 3. FIG. FIG. 11 is a flowchart of judging whether the user equipment can execute the edit mode in FIG. 10. Fig. 12 is a flowchart of checking whether the recipe rule description file can be executed in Fig. 11. FIG. 13 is a flowchart of the current recipe file provided in FIG. 10 for editing by the user equipment.

S12: Receive the traceback command from the user equipment

S121~S129B: steps

Claims (30)

A method for monitoring process recipes includes the following steps: receiving a connection request from a user equipment; and receiving a traceback command of the user equipment, including the following steps: judging whether a traceback mode can be executed; entering a locked state to restrict Only the user equipment controls a database and a recipe description database. One of the current recipe files in the database contains a major version version data and a plurality of sub-recipe data, each of the sub-recipe data includes a recipe item , One-time formula version data and one-time formula values. The formula description database contains a formula rule description file. The current formula file is executed according to the formula rule description file; a plurality of target sub-recipe items and a plurality of target sub-recipe items in a target major version data are executed according to the formula rule description file The target sub-recipe value, restore the corresponding sub-recipe item and the sub-recipe value in the current recipe file; record the major version version data and each sub-recipe version data in the current recipe file after backtracking; and save Get the current recipe file after the backtracking; wherein the step of receiving the connection request from the user equipment includes the following steps: activating a data processing unit; obtaining the current recipe file in the database by the data processing unit And the formula rule description file in the formula description database; and the user equipment is connected to the data processing unit. For example, in the process recipe monitoring method described in item 1 of the scope of patent application, the step of restoring the corresponding sub-recipe item and the value of the sub-recipe in the current recipe file includes the following steps: Restore each of the secondary formula items and the corresponding secondary formula values to the corresponding target secondary formula items and the target secondary formula values in the target major version data. For example, the process recipe monitoring method described in item 1 of the scope of patent application, wherein when the retrospective mode is a specific sub-recipe mode, the data of the major version and each sub-recipe version in the current recipe file after the retrospective are recorded The data steps include the following steps: increment the version data of each recipe; and retain the version data of each recipe that has not been backtracked. For example, in the process recipe monitoring method described in item 1 of the scope of patent application, the step of determining whether the retrospective mode can be executed includes the following steps: determining whether the database and the recipe description database are in the locked state; and determining whether they have Permissions. For example, in the process recipe monitoring method described in item 4 of the scope of patent application, the step of judging whether it is authorized, if not, includes the following steps: denying the user equipment to log in and notifying the user equipment. For example, the process recipe monitoring method described in item 4 of the scope of patent application, wherein the step of judging whether it has authority includes the following steps: judging whether it is possible to log in; obtaining the formula rule description file; and checking whether the formula rule description file can be executed . For example, the process recipe monitoring method described in item 6 of the scope of patent application, wherein the step of checking whether the recipe rule description file can be executed includes the following steps: judging whether the user device has the authority to edit the recipe rule description file; and Check whether the user device can edit the formula rule description file. For example, in the process recipe monitoring method described in the first item of the patent application, the step of judging whether the retrospective mode can be executed, if not, includes the following steps: rejecting the user equipment and notifying the user equipment. For example, the process recipe monitoring method described in item 1 of the scope of patent application, after the step of accessing the current recipe file after the retrospective to the database, includes the following steps: determining whether there is a connection request from another user device ; If not, release the locked state; and if yes, notify the other user device, and update the current recipe file after retrospective. In the process recipe monitoring method described in the first item of the scope of patent application, before the step of accessing the current recipe file after the backtracking to the database, it includes the following steps: accessing the current recipe file before the backtracking. For the process recipe monitoring method described in item 1 of the scope of patent application, the step of activating the data processing unit includes the following steps: reading an original description file; comparing the recipe description database with the original description file according to the original description file Whether the formula rule description file matches; and if it does not match, update the formula rule description file to the formula description database. For example, the process recipe monitoring method described in item 1 of the scope of patent application further includes: when receiving an editing command from one of the user equipment, it includes the following steps: judging whether an editing mode can be executed; judging whether it can be controlled by the user equipment The database and the recipe description database; enter the locked state to restrict only the user equipment to control the database and the recipe description database; Provide the current formula file for editing by the user equipment; access the edited current formula file; release the locked state; and notify and update the edited current formula file. For example, the process recipe monitoring method described in item 12 of the scope of patent application, wherein the step of providing the current recipe file for editing by the user equipment includes the following steps: writing an editing data; judging whether the editing data conforms to the recipe rule Description file; compare whether the edited data is consistent with the current formula file; if inconsistent, access the current formula file before editing; update each of the formula items in the current formula file that are inconsistent; and the record after editing The version data of the major version and the version data of the minor formula corresponding to each of the minor formula items. For example, the process recipe monitoring method described in item 13 of the scope of patent application, wherein the step of comparing whether the edited data is consistent with the current recipe file, if they are consistent, includes the following steps: recording the master version version data in the current recipe file And the version information of each recipe. A process recipe monitoring system includes: a data processing unit that receives a connection request from a user equipment, wherein the data processing unit receiving the connection request from the user equipment includes: the data processing unit obtains the database In the current recipe file and the recipe rule description file in the recipe description database, the user equipment is connected to the data processing unit; and a recipe data unit is connected to the data processing unit, and the recipe data unit includes a Database, a recipe description database and a retrospective module. The database storage contains a current recipe file. The current recipe file contains a major version version data and a plurality of sub-recipe data. The recipe data includes a recipe item, a recipe version data, and a recipe value. The recipe description database stores a recipe rule description file, and executes the current recipe file according to the formula rule description file, where: the data processing unit receives a traceback When ordering, the data processing unit determines whether a retrospective mode can be executed, and if so, the data processing unit enters a locked state for the recipe data unit to restrict the user equipment from controlling the database and the recipe description database; according to one Multiple target sub-recipe items and multiple target sub-recipe values of the target major version data, the retrospective module restores the corresponding sub-recipe item and the sub-recipe value in the current recipe file, and the data processing unit record is backtracked The version data of the major version and the version data of each of the sub-recipes in the current formula file are then accessed, and the current formula file after being backtracked is accessed to the database. For example, the process recipe monitoring system described in item 15 of the scope of patent application, wherein the retrospective module restores each sub-recipe item and the corresponding value of the sub-recipe to the corresponding target sub-recipe item in the target main version data And the target formula value. For example, in the process recipe monitoring system described in item 15 of the scope of patent application, when the retrospective mode is a mode for reverting to a specific sub-recipe, the data processing unit retains the version data of each sub-recipe that has not been retrospected. For example, the process recipe monitoring system described in item 15 of the scope of patent application, wherein the data processing unit determines whether the retrospective mode can be executed, including: the data processing unit determines whether the database and the recipe description database are in the locked state; And the data processing unit judges whether it has authority. For example, the process recipe monitoring system described in item 18 of the scope of patent application, wherein the data processing unit determines whether it has authority, including: The data processing unit determines whether the user equipment can log in. If so, the data processing unit determines whether the formula rule description file in the formula description database is locked; if not, the data processing unit obtains the formula from the formula description database. Formula rule description file, and the data processing unit checks whether the formula rule description file can be executed. For example, the process recipe monitoring system described in item 19 of the scope of patent application, wherein the data processing unit checks whether the recipe rule description file can be executed, including: the data processing unit determines whether the user equipment has the authority to edit the recipe rule Description file, and the data processing unit checks whether the user equipment can edit the formula rule description file. For example, in the process recipe monitoring system described in item 19 of the scope of patent application, the data processing unit determines that the user equipment does not have authority, and the data processing unit transmits a rejection command to the user equipment. For example, in the process recipe monitoring system described in item 15 of the patent application, the data processing unit determines that the user equipment cannot execute the traceback mode, and the data processing unit transmits a traceback rejection command to the user equipment. For example, the process recipe monitoring system described in item 15 of the scope of patent application, wherein after the data processing unit accesses the current recipe file after being backtracked to the database, the data processing unit determines whether there is another user device connected Online request, if not, the data processing unit releases the locked state of the recipe data unit; if yes, the data processing unit transmits an update command to the other user equipment and updates the current recipe file after the traceback. For example, in the process recipe monitoring system described in item 15 of the scope of patent application, the recipe data unit includes a historical database, and the data processing unit accesses the current recipe file before retrospective to the historical database. For example, the process recipe monitoring system described in item 15 of the scope of patent application, wherein the data processing unit reads an original description file, and according to the original description file, the data processing unit compares the recipe rule description file in the recipe description database Whether it matches, if not, the data processing unit updates the formula rule description file to the formula description database. For example, in the process recipe monitoring system described in item 15 of the scope of patent application, when the data processing unit receives an editing command, it includes: the data processing unit judges whether the user equipment can execute an editing mode, and if so, the data processing The unit determines whether the user equipment can control the database and the recipe description database. If so, the data processing unit enters the locked state for the recipe data unit to restrict the user equipment from controlling the database and the recipe description Database; the data processing unit provides the current recipe file for editing by the user equipment, and the data processing unit accesses the edited current recipe file to the database; the data processing unit releases the recipe data unit In the locked state, the data processing unit notifies and updates the edited current recipe file to another user device. For example, the process recipe monitoring system described in item 26 of the scope of patent application, wherein the data processing unit determines that the user equipment cannot control the database and the recipe description database, including: the data processing unit transmits an edit rejection command to The user equipment and the data processing unit restore the current recipe file before editing to the user equipment. For example, the process recipe monitoring system described in item 26 of the scope of patent application, wherein the data processing unit provides the current recipe file for editing by the user equipment, including: the user equipment writes an editing data and transmits it to the data processing Unit, the data processing unit judges whether the edited data conforms to the formula rule description file, if so, the data processing unit compares the edited data with the current formula file, and if it is inconsistent, the data processing unit accesses the data before editing The current recipe file is stored in a historical database of the recipe data unit. For example, the process recipe monitoring system described in item 28 of the scope of patent application, wherein the data processing unit compares the edited data with the current recipe file system to be consistent, and the data processing unit records the master version version data in the current recipe file And each of the recipe version data to the database. For example, the process recipe monitoring system described in claim 15 further includes: a process unit connected to the data processing unit, and the data processing unit transmits the current recipe file and the recipe rule description file to the process unit.

Images