TWI682334B - 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 process recipe monitoring method and process recipe monitoring system, and in particular to a method and system for flexible adjustment of recipe items.

With the advancement of process technology, the quality of process products not only depends on the process program, but the quality of the machine is also a key part of it. The machine can be set with specific control rules 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 manufacturing process and manufacturing conditions of the machine. However, the recipe file of the conventional PLC-controlled machine (user equipment) sets fixed control conditions for the production of a single product, so it lacks flexibility and cannot add or modify new control rules and parameter adjustments based on the characteristics of the process product. In addition, the control of the machine recipe is usually limited by the functions provided by the human-machine interface (user equipment). The control range 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 specific version of the recipe file. In addition, each version of the recipe file contains multiple recipe items and their corresponding recipe values. Under the current mechanism, there is no reply mechanism to let the recipe file be in a certain version for a specific recipe item and its Corresponding formula values can be restored separately. Moreover, if there are inconsistencies in the formula items in the formula files of different versions, the operator cannot respond more flexibly to the required formula file.

Therefore, how to improve and provide a "process recipe monitoring method and process recipe monitoring system" to avoid the above-mentioned problems is an urgent problem to be solved in the industry.

An object of the present invention is to allow the user to go back to the specific formula file required to improve the flexibility in the use of process recipes.

An embodiment of the present invention provides a method for monitoring process recipes that can be executed, including the following steps: receiving a connection request from a user device; and receiving a traceback command from a user device, including the following steps: determining whether a traceback can be performed Mode; enter a locked state to limit the control of only one database and one recipe description database for user equipment, where a current recipe file in the database contains a major version version data and a plurality of secondary recipe data, each recipe The data includes a recipe item, a recipe version data, and a recipe value. The recipe description database contains a recipe rule description file. The current recipe file is executed according to the recipe rule description file; a plurality of target secondary recipe items and a target master version data Multiple target sub-recipe values to restore the corresponding sub-recipe items and sub-recipe values in the current recipe file; record the main version version data and each sub-recipe version data in the current recipe file after backtracking; and access after backtracking The current recipe file 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 of a 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 traceback module. The database includes a current recipe file, and the current recipe file includes a major version and multiple data. For recipe data, each recipe data contains one recipe item, one recipe version data and one recipe value. The recipe description database contains a recipe rule description file, and the current recipe file is executed according to the recipe rule description file. When the data processing unit receives a backtracking command, the data processing unit determines whether a backtracking mode can be executed. If so, the data processing unit enters a locked state for the recipe data unit to restrict the user equipment control database and the recipe description database. Based on the multiple target sub-recipe items and the multiple target sub-recipe values of a target major version data, the traceback module restores the corresponding sub-recipe items and sub-recipe values in the current recipe file, and the data processing unit records the current status after the traceback The main version version data and each formula version data in the recipe file, and access the current recipe file after the traceback 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 previous specific version of the recipe file to restore the specific or all of the secondary recipe items in the current recipe file and corresponding The value of the next formula, thereby improving the flexibility of the process recipe.

Furthermore, since it can be restored for specific or all sub-recipe items and corresponding sub-recipe values, the present invention can be traced back to the main version mode or specific sub-recipe mode. In other words, the present invention can not only target a specific In addition to the restoration of the main version and version data of the version, it can also be restored for a specific sub-recipe item and its corresponding sub-recipe value, so that the user can trace back to the current recipe file required.

In addition, for the above-mentioned target recipe file after being backtracked or edited, the present invention will record the new major version version data and each recipe version data, instead of recovering all the major version version data and each recipe version data To a specific version of the previous recipe file.

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

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

FIG. 1 is a schematic diagram of a process recipe monitoring system of the present invention. 2A is a schematic diagram of the current recipe file of the present invention. FIG. 2B is a schematic diagram of a description file of a recipe rule of the present invention. 2C is a schematic diagram of the target recipe file of the present invention. FIG. 2D is a schematic diagram of an embodiment of the current recipe file after backtracking in 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 logic judgment through hardware (such as an integrated circuit), 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 of the user equipment 30 and waits to receive the command C of 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 ease of explanation, FIG. 1 only shows the command C. The name of the command C may be determined according to different needs 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 backtracking command C1 or the editing command C2 to the data processing unit 11, and the data processing unit 11 can transmit such as rejecting the command C3, locking command C41, unlocking command C42, rejecting the backtracking command C5, rejecting according to different situations The command C such as the edit command C6, the update command C7, and the notification command C8 is sent to the user device 30. In another embodiment, the data processing unit 11 can receive the connection request or command C of the user equipment 30 and another user equipment 40 simultaneously or at different times, so the data processing unit 11 can also communicate with another user The devices 40 transmit command C to each other. The user equipment 30 and the other user equipment 40 in this embodiment are, for example, Human Machine Interface (HMI), Manufacturing Execution System (MES), 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 traceback 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 a current recipe (Recipe) file RF (see FIG. 2A). The current recipe file RF includes a major version version data (Version) VM and a plurality of sub-recipe data SR, each recipe The data SR includes a sub-recipe item SRI, a sub-recipe version data SRV and a primary recipe value SRN, each sub-recipe item SRI corresponds to a sub-recipe version SRV and a sub-recipe value SRN, The sub-recipe items SRI are, for example, chemical liquid, pressure, process temperature, process time, heating time, cooling time or substrate thickness, etc. The sub-recipe items can be adjusted according to the actual machine and process requirements. The sub-recipe value SRN is based on the foregoing The sub-recipe item SRI is used to set the value, and each time the sub-recipe value is modified SRN changes the version information of the sub-recipe version SRV.

The recipe description database 123 stores a recipe rule description file RRDF (see FIG. 2B). The recipe rule description file RRDF is an Extensible Markup Language (XML) configuration file, which is executed according to the recipe rule description file RRDF. Recipe file RF. In this embodiment, the recipe rule description file RRDF sets the upper limit value, the lower limit value, and the preset value corresponding to the secondary recipe value SRN of each recipe item SRI in the current recipe file RF. In addition, the recipe rule description file RRDF also It can set the edit permission conditions, control conditions, communication conditions and compound conditions of each SRI in the current recipe file RF. The edit permission conditions refer to whether the user can read (Read), Write (Read Only) or Read Only (Visible or Invisible) modification authority; control conditions such as process recipe monitoring system 10 can be edited during operation; communication conditions allow specific conditions to be connected Line; Compound conditions are the limiting conditions for 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, the compound condition is to set the process temperature When it is greater than 120 degrees, the cooling time must be set to greater than 30 seconds.

The historical database 125 is for accessing historical data, which includes the current recipe file RF before the change and the target recipe file TRF as shown in FIG. 2C, where the target recipe file TRF contains the target master version data TVM and a plurality of target secondary 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, drug solution, pressure, process temperature, process time, temperature rise Time, cooling time or substrate thickness, etc., can adjust the target sub-recipe items according to the actual machine and process requirements. The target sub-recipe value TSRN is set according to the aforementioned target sub-recipe item TSRI, and the target sub-recipe version SRV is In order to modify the change version information of the secondary recipe value SRN. 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 recipe file RF to the historical database 125, and then, according to the plurality of target sub-recipe items TSRI and the plurality of target sub-recipe values TSRV in the target recipe file TRF, the traceback module 127 restores a specific number of the current recipe file RF or All sub-recipe items SRI and corresponding sub-recipe values SRN, for example, the target sub-recipe item TSRI in FIG. 2C corresponds to the sub-recipe item SRI in FIG. 2A, and the corresponding sub-recipe item SRI in FIG. 2A The secondary recipe value SRN is restored to the target secondary recipe value TSRN in FIG. 2C, which is the current recipe file RFB after the backtracking in FIG. 2D. In addition, the data processing unit 11 records the major version version data VMB and each minor recipe version data SRVB in the current recipe file RFB after the traceback, and accesses the traceback current recipe file RFB (as shown in FIG. 2D) to the database 121 . It should be noted that the data processing unit 11 processes the major version version data VMB and each minor recipe version data SRVB in the current recipe file RFB after the traceback, not the major version in the current recipe file RFB after the traceback The version data VMB and each recipe version data SRVB are recorded as the target master version data TVM and each target sub recipe data TSR in the target recipe file TRF, but the main version version data VMB in the current recipe file RFB after the update is updated For each recipe version data SRVB, for example, the major version VM in the current recipe file RF before the traceback shown in FIG. 2A is 10, the minor recipe version data SRV is 6, after the traceback shown in FIG. 2D The current version file RFB's main version version data VMB is 11 and the sub-recipe version data SRVB is 7. In this record version, the incremental version is used as an example. In another embodiment, the record version can be encoded in other ways or according to requirements. Set 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 recipe file RF and the recipe rule description file RRDF, and the current recipe file RF is executed according to the provisions of the recipe rule description file RRDF.

FIG. 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 of a user device in FIG. 3. FIG. 5 is a flowchart of starting the data processing unit in FIG. 4. FIG. 6 is a flowchart of receiving the traceback command of the user equipment in FIG. 3. FIG. 7 is a flowchart of FIG. 6 to determine whether the user equipment can execute the backtracking mode. FIG. 8 is a flowchart of determining whether the user equipment has authority in FIG. 7. FIG. 9 is a flowchart of FIG. 8 to check whether the recipe rule description file can be executed. FIG. 10 is a flowchart of receiving the edit command of the user device in FIG. 3. FIG. 11 is a flowchart of FIG. 10 to determine whether the user equipment can execute the edit mode. FIG. 12 is a flowchart of FIG. 11 to check whether the recipe rule description file can be executed. FIG. 13 is a flowchart of providing the current recipe file in FIG. 10 for editing by the user device.

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. Go to step S11 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 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, and the data processing unit 11 is used to obtain the current recipe file RF in the database 121 and the recipe rule description file RRDF in the recipe description database 123. Next, 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, proceed to step S22, read an original description file, the original description file 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, according to the original description file, compare whether the RRDF of the recipe rule description file in the recipe description database 123 matches. Taking FIG. 1 as an example, the data processing unit 11 first checks 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 original description file are correct Whether it can be executed, if not, the data processing unit 11 transmits a notification command C8 to the user equipment 30 to display an abnormality; otherwise, 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 recipe description database 123 and extract the recipe rule description file RRDF. The data processing unit 11 compares whether the original description file and the recipe rule description file RRDF can match. Whether the judgment can be matched is based on the recipe rule description file RRDF. In the current recipe file RF, each recipe item SRI corresponds to the upper limit value, the lower limit value, and the preset value of the secondary recipe value SRN, and the edit permission conditions, control conditions, communication conditions, and composite conditions of each recipe item SRI To determine whether the data corresponding to the original description file exists and is consistent. In an 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 device 30 to display normal and can continue execution. In another embodiment, if the data processing unit 11 determines that the original description file and the recipe rule description file RRDF cannot match, proceed to step S26. 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 Use the description file 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 notifies the user that the device 30 can continue to execute. This action ensures the original The description file conforms to the recipe rule description file RRDF in the recipe data unit 12. It should be noted that the above FIG. 5 compares the actions of the recipe rule description file RRDF according to the original description file. In addition to starting the process recipe monitoring system 10, when the user device 30 needs to be edited or traced back, it can also be based on the above FIG. 5 To determine whether the recipe 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, and then, the user equipment 30 transmits a command C to the data processing unit 11 according to user requirements. The command C is, for example, a Backtrack command C1 or an edit 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 of the user equipment 30 (step S12). Step S12 may include the following steps S121 to S129B, Referring to FIG. 6, in 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 At step S129, the user equipment 30 is rejected and the user equipment 30 is notified. In detail, step S121 may include the following steps S32 to S36. Please refer to FIG. 7 to 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 designated to edit the current recipe file RF is in use 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 the recipe rule description file RRDF is being edited by another user equipment 40 (including other user equipment), and 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 backtracking mode, so proceeds to step S36, rejects the user equipment 30, and notifies the user equipment 30. Therefore, the data processing unit 11 transmits a rejection traceback command C5 to the user equipment 30 and notifies the user equipment 30 to refuse to execute the traceback command C1. On the contrary, if the data processing unit 11 determines that the database 121 and the recipe description database 123 are not being controlled by another user equipment 40 (including other user equipment), step S34 is performed to determine whether it has authority, and if the data processing unit 11 It is determined that the user equipment 30 does not have the authority to perform backtracking, 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 authority may include steps S341 to S345. Please refer to FIG. 8 to proceed to step S341 to determine whether it is possible to log in. Taking FIG. 1 as an example, the data processing unit 11 is loaded Regarding the user account password of the user device 30, and check whether the user account password is correct, then the data processing unit 11 checks whether the user account password of the user has repeated login, that is, the account password of the same user is used by In addition to the login of the user device 30, it is checked whether other user devices log in with the same user account password. If the user's account password is incorrect after the check, or the user's account password is repeatedly logged in, the data processing unit 11 determines that the user device 30 cannot log in, proceeds to step S345, rejects the user device 30's login, and notifies the user device 30. Therefore, the data processing unit 11 transmits a rejection command C3 to the user equipment 30 to notify the user equipment 30. If it is determined in step S341 that the user device 30 can log in, proceed to step S342 to determine whether the recipe rule description file RRDF in the recipe description database 123 is locked. Taking FIG. 1 as an example, the data processing unit 11 determines the recipe description database 123 Whether the RRDF in the recipe rule description file is locked, the locking refers to whether the RRDF in the recipe description database 123 is controlled and used by another user device 40 (including other user devices), and 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 a rejection command C3 to the user equipment 30 and notifies the user equipment 30. In an embodiment, the data processing unit 11 further determines whether another user equipment 40 locks the recipe rule description file RRDF overtime. If not, the data processing unit 11 continues to provide another user equipment 40 to lock the recipe rule description file RRDF to Edit; conversely, if another user equipment 40 locks the recipe rule description file RRDF has expired for more than a specific time, the data processing unit 11 transmits a rejection command C3 and informs the user equipment 30 and another 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, and then proceeds to step S343, the data processing unit 11 obtains the recipe rule description file RRDF from 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 refuse the user device 30 to log in and notify the user device 30. Therefore, the data processing unit 11 transmits a rejection command C3 to use The user device 30 and notify the user device 30. In detail, step S344 may include steps S42 to S46. Please refer to FIG. 9 to proceed to step S42 to determine whether the user device 30 has permission to edit the recipe rule description file RRDF. Taking FIG. 1 as an example, the data processing unit 11 determines whether the user device 30 has permission to edit the recipe rule description file RRDF according to the editing permission condition. If the determination is negative, step S46 is performed, the user device 30 is denied login, and the user is notified of the use Device 30, therefore, the data processing unit 11 transmits a rejection command C3 to the user device 30 and informs the user device 30 that the recipe rule description file RRDF cannot be edited; otherwise, if it is judged as yes, the user device 30 has the authority to edit the recipe rule Describe the RRDF file and proceed to step S44 to check whether the user equipment 30 can edit the recipe rule description file RRDF. Taking FIG. 1 as an example, the data processing unit 11 judges whether the user equipment 30 can edit the recipe rule description file RRDF according to the control conditions and the communication conditions. If the judgment is no, proceed to step S46, reject the user equipment 30 from logging in, and notify The user equipment 30, therefore, the data processing unit 11 transmits a refusal command C3 to the user equipment 30 and informs the user equipment 30 that the recipe rule description file RRDF cannot be edited; otherwise, if the judgment is yes, the user equipment 30 is currently available for editing recipes Rule description file RRDF.

Please refer to FIG. 6 again, after determining in step S121 that the user equipment 30 can perform the backtracking mode, proceed to step S122 to enter a locked state to restrict the user equipment 30 to control only one database 121 and one recipe description database 123, Among them, a current recipe file RF in the database 121 includes a major version and minor data VM and a plurality of minor recipe data SR, each minor recipe data SR includes minor recipe items SRI, minor recipe version data SRV and minor recipe values SRN, recipe description The database 123 includes a recipe rule description file RRDF, and the current recipe file RF is executed 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, at this time, even if another user equipment 40 or other user equipment is connected to the data processing unit 11, the database 121 and the recipe The description database 123 has been controlled by the user equipment 30 to enter the locked state. At this time, the data processing unit 11 transmits a rejection command C3 and notifies 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 equipment 40 to control the database 121 and the recipe description database 123. Next, step S123 is performed to access the current recipe file RF before backtracking to a historical database 125. Therefore, the data processing unit 11 accesses the current recipe file RF before backtracking to the historical database 125. Next, step S124 is performed, based on the plurality of target sub-recipe items TSRI and the plurality of target sub-recipe values TSRN of a target master version data TVM, to restore the corresponding sub-recipe items SRI and sub-recipe values SRN in the current recipe file RF. For example, the sub-recipe item SRI in FIG. 2A corresponds to the target sub-recipe item TSRI in FIG. 2C, so the sub-recipe value SRN of the corresponding sub-recipe item SRI in FIG. 2A is restored to the target sub-recipe value in FIG. 2C TSRN, that is, the current recipe file RFB after the traceback in Figure 2D. In addition, since the current recipe file RF needs to be traced back 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 editing data of each secondary 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 next performed to record the major version version data VMB and each minor recipe version data SRVB in the current recipe file RFB after the traceback. Next, step S126 is performed to access the current recipe file RFB after 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 may be a reply to the main version mode or a reply to the specific minor recipe mode.

In one embodiment, the backtracking mode is a master version recovery mode. The master version mode refers to restoring the current recipe file RF to a specific version of the recipe file. The specific version of the recipe file is, for example, the target recipe file TRF, based on the target recipe In the file TRF, a plurality of target sub-recipe items TSRI and a plurality of target sub-recipe values TSRV, the traceback 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 traceback is 10, a certain recipe version data SRV is 6, another recipe version data SRV is 7, and you want to restore the current recipe file RF to the main version If the version number is 8, if the target master version data TVM of the target recipe file TRF is 8, the traceback module 127 responds correspondingly 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 in the current recipe file RF and the corresponding sub-recipe values SRN, and then, the data processing unit 11 accesses the current recipe file RFB after traceback 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 time in FIG. 2C The recipe value TSRN is the current recipe file RFB after the backtracking in Figure 2D. In addition, the data processing unit 11 records the major version version data VMB and each minor recipe version data SRVB in the current recipe file RFB after the traceback, and then, the data processing unit 11 accesses the traceback current recipe file RFB (as shown in FIG. 2D (Shown) to the database 121. It should be noted that the data processing unit 11 processes the major version version data VMB and each minor recipe version data SRVB in the current recipe file RFB after the traceback, not the major version in the current recipe file RFB after the traceback The version data VMB and each recipe version data SRVB are recorded as the target master version data TVM and each target sub recipe data TSR in the target recipe file TRF, but the main version version data VMB in the current recipe file RFB after the update is updated And the recipe data SRVB of each time, therefore, the main version data VM in the current recipe file RF before the traceback shown in FIG. 2A is 10, one recipe data SRV is 6, and another recipe data SRV is 7. , The main version version data VMB of the current recipe file RFB after traceback shown in FIG. 2D is 11, a certain recipe version data SRV is 7, and another recipe version data SRV is 8. In this record version, increment is taken as an example In other embodiments, the record version can be set by other encoding methods or according to requirements. It should also be noted that since the number of secondary recipe version data SRV in the current recipe file RF before the traceback may be different from the number of target secondary recipe items TSRI in the target recipe file TRF to be restored, the data processing unit 11 is based on The current recipe file RF is compared with the target recipe 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 for the corresponding sub-recipe item SRI, In the backtracking step, the current secondary recipe item SRI and the corresponding recipe value SRN in the current recipe file RF are retained. If there is a match for the corresponding secondary recipe item SRI, in the backtracking step, the corresponding secondary recipe item SRI can be matched and replaced as the target At the same time, the sub-recipe item TSRI also replaces the sub-recipe value SRV corresponding to the sub-recipe item SRI to the target sub-recipe value TSRV.

In another embodiment, the backtracking mode is to restore a specific sub-recipe mode. The specific sub-recipe mode refers to restoring a specific or several sub-recipe items SRI in the current recipe file RF to the target recipe file TRF. The target sub-recipe project TSRI. For example, the major version version data VM in the current recipe file RF before the traceback is 10, the SRV of a specific minor recipe version data is 6, and the other minor recipe version data SRV is 7. If the current recipe file RF is A specific sub-recipe item SRI and corresponding sub-recipe value SRN are restored to a corresponding sub-recipe item and sub-recipe value in a sub-recipe version. A sub-recipe version is, for example, the target master version data TVM, if the target formula The target major version data TVM of the file TRF is 8, and the target minor recipe version data TSRV is 5. Therefore, the traceback module 127 restores the current recipe file by matching the target minor recipe item TSRI and the target minor recipe value TSRV according to the target major version data TVM The secondary recipe item SRI in RF corresponds to the corresponding secondary recipe value SRN. In addition, the data processing unit 11 records the major version version data VMB and each minor recipe version data SRVB in the current recipe file RFB after the traceback, and then, the data processing unit 11 accesses the traceback current recipe file RFB (as shown in FIG. 2D (Shown) to the database 121. It should be noted that the data processing unit 11 processes the major version version data VMB and each minor recipe version data SRVB in the current recipe file RFB after the traceback, not the major version in the current recipe file RFB after the traceback The version data VMB and each recipe version data SRVB are recorded as the target master version data TVM and each target sub recipe data TSR in the target recipe file TRF, but the main version version data VMB in the current recipe file RFB after the update is updated SRVB with each recipe version data, and retain the SRVB of the sub-recipe version data without backtracking. Therefore, in one embodiment, the main version version data VM in the current recipe file RF before backtracking shown in FIG. 2A is 10 , A specific sub-recipe item SRI corresponds to a specific sub-recipe version data SRV of 6, another specific sub-recipe item SRI corresponds to another sub-recipe version data SRV of 7, to perform a specific sub-recipe mode, copy the current recipe file A specific sub-recipe item SRI in RF is restored to the corresponding target sub-recipe item TSRI in the target recipe file TRF without backtracking another specific sub-recipe item SRI. The current formula file RFB after the traceback shown in FIG. 2D The main version version data VMB is 11, and a specific secondary recipe item SRI corresponding to a specific sub-recipe version data SRVB is 7, that is, incrementing each retrospective recipe version data after retrospective, another specific sub-recipe item Since the SRI has not been backtracked, the SRV of another sub-recipe version is still maintained at 7. In this record version, the incremental version is taken as an example. In other embodiments, the record version can be set by other encoding methods or according to requirements. It should also be noted that since the number of secondary recipe version data SRV in the current recipe file RF before the traceback may be different from the number of target secondary recipe items TSRI in the target recipe file TRF to be restored, the data processing unit 11 is based on The current recipe file RF is compared with the target recipe 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 for the corresponding sub-recipe item SRI, In the backtracking step, the current secondary recipe item SRI and the corresponding recipe value SRN in the current recipe file RF are retained. If there is a match for the corresponding secondary recipe item SRI, in the backtracking step, the corresponding secondary recipe item SRI can be matched and replaced as the target At the same time, the sub-recipe item TSRI also replaces the sub-recipe value SRV corresponding to the sub-recipe item SRI to the target sub-recipe value TSRV.

Please continue to refer to FIG. 6, after accessing the backtracked current recipe file RFB to the database 121 in step S126, proceed to step S127 to determine whether there is another user device 40 connection request. Taking FIG. 1 as an example, the data The processing unit 11 judges whether there is a connection request of another user equipment 40 (or other user equipment). If not, proceed to step S129B to unlock the 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; otherwise, if the data processing unit 11 It is judged that there is a connection request of another user equipment 40 (or other user equipment), step S128 is performed, the other user equipment 40 is notified, and the current recipe file RFB after the traceback is updated, so 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 traceback 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 a command C to the data processing unit 11 according to user requirements. 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 of the user equipment (step S13). Step S13 may include the following steps S131 to S139, please Referring to FIG. 10, step S131 is performed to determine whether an editing mode can be performed. That is, after the data processing unit 11 receives the editing command C2 of the user equipment 30, it is determined whether the user equipment 30 can perform 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 to perform step S51 to determine whether login is possible. Taking FIG. 1 as an example, the data processing unit 11 loads the account password of the user about 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 present Repeated login, that is, except that the account password of the same user is logged in by the user device 30, check whether any other user device logs 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 is repeatedly logged in, the data processing unit 11 determines that the user device 30 cannot log in, proceeds to step S55, rejects the user device 30's login, and notifies the user device 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 recipe rule description file RRDF in the recipe 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 so, proceed to step S55, reject the user equipment 30 login, and notify the user equipment 30, therefore, the data processing unit 11 transmits a rejection command C3 to the user equipment 30 and notify the user equipment 30. In an embodiment, the data processing unit 11 further determines whether another user equipment 40 locks the recipe rule description file RRDF overtime. If not, the data processing unit 11 continues to provide another user equipment 40 to lock the recipe rule description file RRDF to Edit; conversely, if another user equipment 40 locks the recipe rule description file RRDF has expired for more than a specific time, the data processing unit 11 transmits a rejection command C3 and informs the user equipment 30 and another 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, and then 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 refuse the user device 30 to log in and notify the user device 30. Therefore, the data processing unit 11 transmits a rejection command C3 to use The user device 30 and notify the user device 30.

In detail, step S54 may include steps S542 to S546. Please refer to FIG. 12 to perform step S542 to determine whether the user device 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 condition, where the editing authority condition refers to whether the user equipment 30 can read the secondary recipe item SRI (Read), write (Write), read only (Read Only) or visible (Visible or Invisible) modification authority, if the judgment is no, proceed to step S546, reject the user device 30 login, and notify the user The device 30, therefore, the data processing unit 11 transmits a rejection command C3 to the user device 30 and informs the user device 30 that the recipe rule description file RRDF cannot be edited; otherwise, if the judgment is yes, the user device 30 has the authority to edit the recipe rule description File RRDF, and proceed to step S544 to check whether the user equipment 30 can edit the recipe rule description file RRDF. Taking FIG. 1 as an example, the data processing unit 11 determines whether the user equipment 30 can edit the recipe rule description file RRDF according to the control conditions and communication conditions, where the control conditions such as the process recipe monitoring system 10 are allowed to be edited during operation; the communication conditions It is allowed to connect under certain conditions. If the judgment is no, go to step S546, refuse to log in 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 notify the use 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 determining in step S131 that the user equipment 30 can execute the editing mode, proceed to step S132 to determine whether the user equipment 30 can be used to 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 being controlled by another user device 40, that is, the data processing unit 11 checks whether the database 121 is locked or specifies the current recipe for editing The file RF is in use, or the data processing unit 11 checks whether the recipe description database 123 is locked or whether 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 locks the recipe data unit 12 and the database 121 and the recipe description database 123 are locked to limit only the user device 30 to control the database 121 and the recipe description database 123; otherwise, if the data processing unit 11 It is judged that the user equipment 30 cannot be used by the user equipment 30 to control the database 121 and the recipe description database 123, and step S139 is performed 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 a refusal edit command C6 to the user equipment 30 and informs the user equipment 30 to refuse to execute the edit command C2, and if the user equipment 30 is editing the current recipe file RF, the data processing unit 11 recovers The current recipe file RF before editing is sent to the user equipment 30.

If the data processing unit 11 determines that the database 121 and the recipe description database 123 are not under the control of another user equipment 40 (including other user equipment), proceed to step S133 to enter the locked state to restrict access to 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, at this time, even if another user equipment 40 or other user equipment is connected to the data processing unit 11, the database 121 and the recipe The description database 123 has been controlled by the user equipment 30 to enter the locked state. At this time, the data processing unit 11 transmits a rejection command C3 and notifies 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 equipment 40 to control the database 121 and the recipe description database 123. Next, proceed to step S134 to provide the current recipe file RF for editing by the user device 30. After editing the current recipe file RF, proceed to step S135 to access the edited current recipe file RF to the database 121.

In detail, step S134 to step S135 may include step S61 to step S68, please refer to FIG. 13, proceed to step S61, write an edited data, the edited data may be an Extensible Markup Language (XML ) Setting file. Taking FIG. 1 as an example, the user device 30 writes edit data and transmits it to the data processing unit 11, and the data processing unit 11 reads the edit data written by the user device 30. In an embodiment, the data processing unit 11 further determines whether the user equipment 30 locks the database 121 and the recipe description database 123 overtime. If not, the data processing unit 11 continues to provide the user equipment 30 to lock the database 121 and the recipe description Database 123 for editing; on the contrary, if the user equipment 30 locks the database 121 and the recipe description database 123 has expired for more than 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 is unlocked. Therefore, the data processing unit 11 transmits an unlock command C42 to the user equipment 30. In other words, the database 121 and the recipe description database 123 are unlocked, so that the database 121 The recipe description database 123 may be controlled by another user equipment 40 or other user equipment.

After writing the editing data in step S61, next, proceed to step S62 to determine whether the editing data conforms to the recipe rule description file RRDF. Taking FIG. 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. 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 to display an abnormality; otherwise, if the data is edited The description format and setting conditions are correct and can be executed. Step S63 is performed to compare whether the edited data is consistent with the current recipe file RF. If the data processing unit 11 judges 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 the respective recipe version data SRV in the current recipe file RF to the database 121, in other words, Although the editing data of the user equipment 30 is consistent with the current recipe file RF, the data processing unit 11 will still update the edited current recipe file RF after editing the user equipment 30, the main version version data VM and each recipe Version information SRV. For example, the major version version data VM in the current recipe file RF before editing is 10, the minor formula 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 sub-recipe version data SRVB is 7. In this record version, the increment is taken as an example. In another embodiment, the record version can be set by 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, proceeds to step S64 to access the current recipe file RF before editing to the historical database 125. Therefore, if the main version version data VMB in the current recipe file RF before editing is 10, and the sub-recipe version data SRV in the sub-recipe data SR is 7, the data processing unit 11 saves the above-mentioned current formula file RF before editing Get to the historical database 125 of the recipe data unit 12.

Next, proceed to step S65 to update each recipe item SRI in the current recipe file RF with inconsistencies. Taking FIG. 1 as an example, the data processing unit 11 correspondingly updates each recipe item SRI that has inconsistencies after the comparison to the database 121. Next, proceed to step S66, record the edited major version version data VM corresponding to each recipe item SRI corresponding to each recipe item SRI, therefore, the data processing unit 11 accesses the edited current recipe file RF to Data base 121, and record the major version version data VM and each minor recipe version data SRV corresponding to each minor recipe item SRI. For example, the main version version data VM in the current recipe file RF before editing is 10, the respective formula version data SRV corresponding to each recipe item SRI is 6, and the main version version of the current recipe file RF after editing The secondary data VM is 11, and the sub-recipe version data SRVB is 7. Here, the record version is an increment. For example, in another embodiment, the record version may be set by other encoding methods or according to requirements.

Next, please refer to FIG. 10 again, and proceed to step S136 to release the locked state. Therefore, the data processing unit 11 transmits the unlock command C42 to the user equipment 30. In other words, the data processing unit 11 unlocks the recipe data unit 12 to release the restriction. Only the user equipment 30 controls the database 121 and the recipe description data. The library 123 enables the database 121 and the recipe description database 123 to be controlled by another user equipment 40 or other user equipment. Next, proceed to step S137 to notify and update the edited current recipe file RF. Therefore, the data processing unit 11 sends out a notification command C8 to the user equipment 30 and another user equipment 40, and the data processing unit 11 transmits an update command C7 to the user equipment 30 and another user equipment 40 to update the The edited current recipe file RF can be used by another user device 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 a previous specific version of the recipe file to restore the specific or all sub-recipe items and Corresponding to the value of the secondary formula, thereby improving the flexibility of the process recipe.

Furthermore, since it can be restored for specific or all sub-recipe items and corresponding sub-recipe values, the present invention can be traced back to the main version mode or specific sub-recipe mode. In other words, the present invention can not only target a specific In addition to the restoration of the main version and version data of the version, it can also be restored for a specific sub-recipe item and its corresponding sub-recipe value, so that the user can trace back to the current recipe file required.

In addition, for the above-mentioned target recipe file after being backtracked or edited, the present invention will record the new major version version data and each recipe version data, instead of recovering all the major version version data and each recipe version data To a specific version of the previous recipe file.

Although the present invention has been disclosed as above by the embodiments, it is not intended to limit the present invention. Anyone who has 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 the scope defined in the attached patent application.

10‧‧‧ process recipe monitoring system 11‧‧‧ data processing unit 12‧‧‧ recipe data unit 121‧‧‧ database 123‧‧‧ recipe description database 125‧‧‧ historical database 127‧‧‧ traceback module 13‧‧‧ Process unit 30‧‧‧ User equipment 40‧‧‧ Another user equipment C‧‧‧ Command RF, RFB‧‧‧ Current recipe file RRDF‧‧‧ Recipe rule description file S10‧‧‧ Process recipe Monitoring methods S11~S12‧‧‧Step S112~S116‧‧‧Step S121~S129B‧‧‧Step S131~S139‧‧‧Step S22~S26‧‧‧Step S32~S36‧‧‧Step S341~S345‧‧‧ Step S42~S46‧‧‧Step S51~S55‧‧‧Step S542~S546‧‧‧Step S61~S68‧‧‧Step SR‧‧‧Formulation data SRI‧‧‧Formulation item SRN‧‧‧Formulation value SRV‧‧‧recipe recipe version data TRF‧‧‧target recipe file TSR‧‧‧target recipe information TSRI‧‧‧target recipe formula item TSRN‧‧‧target recipe value TSRV‧‧‧target recipe formula data TVM‧ ‧‧Target main version data VM, VMB‧‧‧ Main version version data

FIG. 1 is a schematic diagram of a process recipe monitoring system of the present invention. 2A is a schematic diagram of the current recipe file of the present invention. FIG. 2B is a schematic diagram of a description file of a recipe rule of the present invention. 2C is a schematic diagram of the target recipe file of the present invention. FIG. 2D is a schematic diagram of an embodiment of the current recipe file after backtracking in the present invention. FIG. 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 of a user device in FIG. 3. FIG. 5 is a flowchart of starting the data processing unit in FIG. 4. FIG. 6 is a flowchart of receiving the traceback command of the user equipment in FIG. 3. FIG. 7 is a flowchart of FIG. 6 to determine whether the user equipment can execute the backtracking mode. FIG. 8 is a flowchart of determining whether the user equipment has authority in FIG. 7. FIG. 9 is a flowchart of FIG. 8 to check whether the recipe rule description file can be executed. FIG. 10 is a flowchart of receiving the edit command of the user device in FIG. 3. FIG. 11 is a flowchart of FIG. 10 to determine whether the user equipment can execute the edit mode. FIG. 12 is a flowchart of FIG. 11 to check whether the recipe rule description file can be executed. FIG. 13 is a flowchart of providing the current recipe file in FIG. 10 for editing by the user device.

S12‧‧‧ Receive backtracking command from user equipment

S121~S129B‧‧‧Step

Claims (32)

A process recipe monitoring method includes the following steps: receiving a connection request of a user equipment; and receiving a traceback command of the user equipment, including the following steps: determining whether a traceback mode can be executed; entering a locked state to limit Only a database and a recipe description database are controlled by the user equipment, where one of the current recipe files in the database contains a major version version data and a plurality of secondary recipe data, each of which contains a recipe item 1. One-time recipe version data and one-time recipe value, the recipe description database contains a recipe rule description file, and the current recipe file is executed according to the recipe rule description file; the plurality of target sub-recipe items and the plurality of target recipe data Target sub-recipe value, restore the corresponding sub-recipe item and the sub-recipe value in the current recipe file; the steps to restore the corresponding sub-recipe item and the sub-recipe value in the current recipe file include the following steps: Determine whether each sub-recipe item can correspond to the corresponding target sub-recipe item in the target master version data; if there is no corresponding sub-recipe item, keep the un-corresponding sub-recipe item in the current recipe file and the corresponding The formula value of the formula; and if there is a corresponding sub-formulation item, replace the formula value of the corresponding sub-formulation item with the target sub-formulation value of the corresponding target sub-formulation item; record the The current version data of the major version and each version of the current recipe file in the current recipe file; and access to the current recipe file after traceback. The process recipe monitoring method as described in item 1 of the patent application scope, wherein the steps of restoring the corresponding sub-recipe items and the sub-recipe values in the current recipe file include the following steps: Restore each sub-recipe item and the corresponding sub-recipe value to the target sub-recipe item and the target sub-recipe value corresponding to the target master version data. The process recipe monitoring method as described in item 1 of the patent application scope, wherein when the backtracking mode is a reply-to-subordinate recipe mode, the main version version data and each sub-formula version in the current formula file after backtracking are recorded The steps of data include the following steps: incrementing the data of each recipe version; and retaining the data of each recipe version without backtracking. The process recipe monitoring method as described in item 1 of the patent application scope, wherein the step of judging whether the traceback mode can be executed includes the following steps: judging whether the database and the recipe description database are in the locked state; and judging whether there is Permissions. The process recipe monitoring method as described in item 4 of the patent application scope, wherein the step of judging whether it has authority, if not, includes the following steps: denying the user equipment to log in, and notifying the user equipment. The process recipe monitoring method as described in item 4 of the patent application scope, wherein the step of judging whether it has authority includes the following steps: judging whether it is possible to log in; obtaining the recipe rule description file; and checking whether the recipe rule description file can be executed . The process recipe monitoring method as described in item 6 of the patent application scope, wherein the step of checking whether the recipe rule description file can be executed includes the following steps: judging whether the user equipment has the authority to edit the recipe rule description file; and Check whether the user equipment can edit the recipe rule description file. The process recipe monitoring method as described in item 1 of the patent application scope, wherein the step of judging whether the traceback mode can be executed, if not, includes the following steps: reject the user equipment, and notify the user equipment. The process recipe monitoring method as described in item 1 of the patent application scope, in which the step of accessing the current recipe file after traceback 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 so, notify the other user equipment and update the current recipe file after the traceback. The process recipe monitoring method as described in item 1 of the patent application scope, wherein the step of accessing the current recipe file after the backtracking to the database includes the following steps: accessing the current recipe file before the backtracking. The process recipe monitoring method as described in item 1 of the patent application scope, wherein the step of receiving the connection request of the user equipment includes the following steps: starting a data processing unit; obtaining the database by the data processing unit In the current recipe file and the recipe rule description file in the recipe description database; and the user equipment is connected to the data processing unit. The process recipe monitoring method as described in item 11 of the patent application scope, wherein the step of starting the data processing unit includes the following steps: reading an original description file; based on the original description file, comparing the recipe description database with the Whether the recipe rule description file matches; and if it does not match, update the recipe rule description file to the recipe description database. The process recipe monitoring method as described in item 1 of the patent application scope further includes: When receiving one of the editing commands of the user equipment, it includes the following steps: judging whether an editing mode can be executed; judging whether the user equipment can control the database and the recipe description database; entering the locked state to limit only For the user equipment to control the database and the recipe description database; provide the current recipe file for editing by the user equipment; access the edited current recipe file; release the locked state; and notify and update the The current recipe file after editing. The process recipe monitoring method as described in item 13 of the patent application scope, 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 rules Description file; compare whether the edited data is consistent with the current recipe file; if inconsistent, access the current recipe file before editing; update each recipe item in the current recipe file with inconsistencies; and record after editing The major version version data corresponds to each minor formula version data corresponding to each minor formula item. The process recipe monitoring method as described in item 14 of the patent application scope, where the step of comparing whether the edited data is consistent with the current recipe file, if it is consistent, includes the following steps: recording the major 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 device; and A recipe data unit, connected to the data processing unit, the recipe data unit includes a database, a recipe description database and a traceback module, the database storage contains a current recipe file, and the current recipe file contains a major version Version data and plural sub-recipe data, each of which contains a recipe item, a recipe version data and a recipe value, the recipe description database stores a recipe rule description file, which is executed according to the recipe rule description file The current recipe file; where the traceback module determines whether each of the sub-recipe items can correspond to the corresponding target sub-recipe items in the target master version data, if there is no corresponding sub-recipe item, the trace-back module retains the current The sub-recipe item and the corresponding recipe value in the recipe file that cannot be matched, if there is a corresponding sub-recipe item, the traceback module replaces the recipe value of the corresponding sub-recipe item with the corresponding target The target sub-recipe value of the sub-recipe item, where: when the data processing unit receives a backtracking command, the data processing unit judges whether a backtracking mode can be executed, and if so, the data processing unit enters a locked state for the recipe data unit, In order to restrict the user equipment to control the database and the recipe description database; according to a plurality of target minor recipe items and a plurality of target minor recipe values of a target major version data, the traceback module restores the corresponding in the current recipe file The sub-recipe item and the sub-recipe value, and the data processing unit records the major version version data and each sub-recipe version data in the current recipe file after the backtracking, and accesses the backtracked current recipe file to The database. The process recipe monitoring system as described in item 16 of the patent application scope, wherein the traceback module restores each sub-recipe item and the corresponding sub-recipe value to the target sub-recipe item corresponding to the target master version data The recipe value with the target time. The process recipe monitoring system as described in item 16 of the patent application scope, wherein when the backtracking mode is a mode for retrieving specific sub-recipes, the data processing unit retains the data of each sub-recipe version without backtracking. The process recipe monitoring system as described in item 16 of the patent application scope, wherein the data processing unit determines whether the traceback 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 determines whether it has authority. The process recipe monitoring system as described in item 19 of the patent application scope, wherein the data processing unit judges whether it has authority, including: the data processing unit judges whether the user equipment can log in, and if so, the data processing unit judges the recipe description Whether the recipe rule description file in the database is locked, if not, the data processing unit obtains the recipe rule description file from the recipe description database, and the data processing unit checks whether the recipe rule description file can be executed. The process recipe monitoring system as described in item 20 of the patent application scope, 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 permission to edit the recipe rule Description file, and the data processing unit checks whether the user equipment can edit the recipe rule description file. The process recipe monitoring system as described in item 20 of the patent application scope, wherein 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. The process recipe monitoring system as described in Item 16 of the patent application scope, wherein the data processing unit determines that the user equipment cannot execute the traceback mode, and the data processing unit transmits a reject traceback command to the user equipment. The process recipe monitoring system as described in item 16 of the patent application scope, wherein after the data processing unit accesses the traced back current recipe file to the database, the data processing unit determines whether there is another user device connected Online request, if not, the data processing unit The locked state of the recipe data unit; if it is, the data processing unit transmits an update command to the other user equipment and updates the current recipe file after the traceback. The process recipe monitoring system as described in item 16 of the patent application scope, wherein the recipe data unit includes a historical database, and the data processing unit accesses the current recipe file before the traceback to the historical database. The process recipe monitoring system as described in item 16 of the patent application scope, wherein the data processing unit receives the connection request of the user equipment, including: the data processing unit obtains the current recipe file and the recipe description in the database The recipe rule description file in the database, the user equipment is connected to the data processing unit. The process recipe monitoring system as described in item 16 of the patent application scope, 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 recipe rule description file to the recipe description database. The process recipe monitoring system as described in item 16 of the patent application scope, in which the data processing unit receives an edit command, including: the data processing unit judges whether the user equipment can perform an edit 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 The locked state, and the data processing unit notifies and updates the edited current recipe file to another user device. The process recipe monitoring system as described in item 28 of the patent application scope, 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 a refusal edit command to The user equipment, and the data processing unit restores the current recipe file before editing to the user equipment. The process recipe monitoring system as described in item 28 of the patent application scope, 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 recipe rule description file. If it matches, the data processing unit compares whether the edited data is consistent with the current recipe file. If not, the data processing unit accesses the pre-edit The current recipe file is to a historical database of the recipe data unit. The process recipe monitoring system as described in item 30 of the patent application scope, in which the data processing unit is consistent with the edited data and the current recipe file, and the data processing unit records the major version version data in the current recipe file Send the recipe version data to the database. The process recipe monitoring system as described in item 16 of the patent application scope 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